Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Integration Server Deployment Checklist | Stage 6: Preparing Clients for Communication with the Server
 
Stage 6: Preparing Clients for Communication with the Server
If you have applications (for example, Java or C/C++ programs) that you want to be Integration Server clients, you must prepare the clients for communication with Integration Server.
Step
Action
Done?
1.
The Integration Server client.jar file contains classes that clients need to communicate with Integration Server. If you have clients on the same machine as Integration Server or Designer, set the classpath on the machine to include the wm-isclient.jar file. The wm-isclient.jar file is located in the common\lib directory, so set the classpath to %CLASSPATH%; Software AG_directory \common\lib\wm-isclient.jar.
2.
If you have clients on machines that do not also host either Integration Server or Designer, do the following for each machine:
1. Navigate to the Software AG_directory \common\lib directory and copy the wm-isclient.jar file to any directory on the client machine.
2. If you want the client to use SSL to communicate with Integration Server, navigate to the Software AG_directory \common\lib\ext directory and copy the enttoolkit.jar file to any directory on the client machine.
3. Set the classpath on the client machine to include the wm-isclient.jar file and, if applicable, the enttoolkit.jar file. For example, if you put the wm-isclient.jar file and the enttoolkit.jar file in the c:\myapp directory, you would set the classpath to %CLASSPATH%;c:\myapp\client.jar;c:\myapp\enttoolkit.jar.