Running the Adapter

1. Update your property list in the LDAP directory or (if applicable) the ie.properties file.

In order to run the sample adapter in standalone mode, set the Port property to a non-zero value using the Generic Adapter property editor.

2. If you start the Info*Engine server using a script file, you need to add the jadk.jar file to the classpath of your script to ensure the adapter is started with the rest of the system.

3. Copy the JSP pages into a directory accessible to your servlet engine.

4. Copy the HTML and XML files from the sample directory to the template root and task root directories, respectively. (These directories are defined in your LDAP.)

5. Make sure the files and local paths referenced from the XML files match the files for testing, and update them if necessary.

6. If you need to test the sample adapter in standalone mode, update the startJADK.sh or startJADK.cmd file to use appropriate values for the environment variables (such as JAVA_HOME, WEB_APP_HOME, CLASSPATH, and so on.) and for the service and package names associated with the adapter. After making the required changes, run the startJADK.sh or startJADK.cmd file.

If you are using the adapter on Linux machine, you should first use the dos2unix command to ensure that the startup script is converted to Unix format. For example:

dos2unix<startup script>

When configuring the sample adapter as an out-of-process adapter with Info*Engine on a different host, complete the following steps to copy required files to the sample adapter host and determine the value for WEB_APP_HOME variable:

1. Run the following command from the <Windchill>/bin/infoengine directory on the Info*Engine server (where <Windchill> is the Info*Engine installation directory):

Executing the above command results in the creation of IeAdapter.zip under <Windchill>/temp/ie_adapter_install.

2. Copy the newly-created IeAdapter.zip file to an arbitrary location on the adapter server (for example, copy it to the adapter installation directory) and run the following command from that location:

3. The WEB_APP_HOME variable is now the directory location from which you ran the jar command. For example:

4. Encrypt the LDAP administrator password stored on the host where the adapter is installed. For more information, see Encrypting the LDAP Administrator Password.

Password encryption should be performed only while installing the adapter out of process with Info*Engine on a different host.