ITP/Server configuration

It is possible to run ITP Models on ITP/Server 3.2.19 or higher from within the ITP/MDK Repository. Refer to the section Test Model tab for more information on configuring the ITP/MDK Repository project. The ITP/Server itself also needs some configuration for this to work.

1. Only perform this step when using an ITP/Server version prior to 3.2.19. Version 3.2.19 and later already contains this script.
   Copy the ITPRun.dss script from the folder Resources in the ITP/MDK Repository Server installation to the subfolder scripts/system in the work folder of the ITP/Server installation.
2. Only perform this step when using an ITP/Server version prior to 3.5.3. Version 3.5.3 and later already contains this script.
   Copy the RepTestMdl.dss script from the folder Resources in the ITP/MDK Repository Server installation to the subfolder scripts in the work folder of the ITP/Server installation. Add this script as a service in the ITP/Server Administrator, and set the following parameters on the Service tab of this service:
   RepHost - $1
   RepPort - $2
   Model - $3
   Revision - $4
   RepUser - $5
   Result - $6
   Keys - $7
   Extras - $8
   Environment - $9
   MetaData - $10
3. In the ITP/Server Administrator, select the services node and the tab Constants. Set the constant AllowRepositoryModelRun to the value Y. Add it if it is not already present.
4. Recompile the scripts from within ITP/Server Administrator, and click Save & Apply.

The constant AllowRepositoryModelRun determines if ITP/Server will accept model run requests from the ITP/MDK Repository. If not set to 'Y', ITP/Server will deny running models from within the ITP/MDK Repository. By explicitly having to configure an ITP/Server installation to accept ITP/MDK Repository runs, it can be avoided that ITP/MDK Repository runs are run accidentally or unauthorized on a particular ITP/Server installation.