Setting up the TCP/IP listener for a called non-J2EE application

If you want a caller to use TCP/IP to exchange data with a called non-J2EE Java program, set up a TCP/IP listener for the called program.

If you are using TCP/IP to communicate with a called non-J2EE Java program, configure a standalone Java program called CSOTcpipListener for that program. Specifically, do as follows:

• Make sure that the classpath used when running CSOTcpipListener contains fda6.jar, fdaj6.jar, and the directories or archives that contain the called programs; and

• Set the Java run-time property tcpiplistener.port to the number of the port at which CSOTcpipListener receives data.

You can start the standalone TCP/IP listener in either of two ways:

• To start the listener from the workbench, use the launch configuration for a Java application. In this case, you can specify the name of the properties file in the program arguments of the launch configuration. Alternatively, if you are using the file tcpiplistener.properties as a default, that file should not be in a folder, but should be directly under the project that you specified when you created the launch configuration.

• To start the listener from the command line, run the program as follows:

  java CSOTcpipListener propertiesFile

  propertiesFile

  The fully qualified path to the properties file used by the TCP/IP listener. If you do not specify a properties file, the listener attempts to open the following file in the current directory:

    tcpiplistener.properties

Related tasks
Providing access to non-EGL jar files