If you plan to deploy the components you will test through Integrated Test Environment then you must modify the start_server.bat batch file so that the InterChange Server Express instance starts in design mode. This is because Integrated Test Environment may deploy the components in such an order that dependencies are not immediately resolved. For the deployment to succeed in such a situation, the server must run in design mode.
As described in InterChange Server modes, you typically start InterChange Server Express in design mode by passing the -design option at the command line or in the Target field of the shortcut. When you use Integrated Test Environment, you start the server through the Integrated Test Environment perspective, and it does not use the shortcut, so even if you modify your InterChange Server Express shortcut to use the -design option the server will not start in design mode.
To start the server in design mode when using Integrated Test Environment, you can either add the -design option to the start_server.bat batch file, or have Integrated Test Environment use a temporary batch file to which it adds the option itself. Follow the instructions in one of the following sections depending on your preference:
Do the following to edit the start_server.bat batch file yourself and add the -design option to it:
%CWJAVA% -Djava.ext.dirs=%JRE_EXT_DIRS%;"%MQ_LIB%";"%DB2_LIB%" -Duser.home="%CROSSWORLDS%" -mx%CW_MEM_HEAP%m -DTEAgent=1200 -DCW_MEMORY_MAX=%CW_MEM_HEAP% %ORB_PROPERTY% -classpath %JCLASSES% ServerWrapper -s%SERVERNAME% -design %2 %3
You can configure Integrated Test Environment to start InterChange Server Express in design mode automatically. With this approach, Integrated Test Environment reads in the start_server.bat file and determines if the -design option has been specified properly or not. It then creates a file named start_server_ite_tmp.bat as a copy of the start_server.bat file and adds the -design option if it has not been properly specified. If you start the server from within Integrated Test Environment then it uses this temporary file.
Do the following to configure the Integrated Test Environment preferences to create a temporary batch file:
Figure 58 shows the Test Server preferences.
If you do not plan to use the custom batch file that Integrated Test Environment can create, leave the Verify server launch script (start_server.bat) checkbox disabled and be sure to follow the instructions in Setting the RMI port in start_server.bat to add the configuration information yourself.