Using CA Application Test › Using the Workstation and Console with CA Application Test › Advanced Features › In-Container Testing (ICT) › Testing your ICT Installation

Testing your ICT Installation

After the server-side portion of ICT is up and running, you should test that you can connect from DevTest Workstation.

To accomplish this:

1. Open DevTest Workstation.
2. Create a new test case named ICT Connection Test.
3. Inside of this test case, create a new Dynamic Java Execution test step.
4. In the editor for the new test step, select the Remote option.
5. Set the Remote Container Type drop-down list to your connection protocol, either EJB or RMI.

Remote Container Type is EJB

If you are using EJB as the connection protocol, click Configure to enter the configuration settings for your protocol.

For example, fill in the Configure EJB Server dialog with host name or IP address and port number of the J2EE container running ICT.

Remote Container Type is RMI

If you are using RMI as the connection protocol, here is an example of the Configure RMI Server dialog that you can use for RMI settings.

After you have successfully tested the connection to the ICT Server, enter java.util.Date in the Make New Object of Class field and click Construct/Load Object to create a new in-container instance of the java.util.Date class.

Your installation is complete and you are ready to use ICT.

Dependencies

The ICT Server-side classes depend on the following third-party libraries:

• BeanShell 2.0b4 (bsh-2.0b4-lisa-remote-object-manager.jar).

  Note: The original JAR file has been modified so that .bsh scripts are removed. These scripts are known to cause problems with J2EE containers that inspect JAR files and automatically execute them.

• XStream 1.1.2 (xstream-1.1.2.jar)
• Log4j 1.2.13 (log4j-1.2.13.jar)
• Jakarta Commons Logging 1.0.2 (commons-logging.jar)

These dependencies are intentionally distributed as separate files with DevTest ICT JAR files to make ICT integration easier. Because the application that you are testing may already include some or all of these libraries in its classpath, adding these dependencies to the classpath may not be necessary.