Configure Gateway Server for the Connect:Direct local node

To use Sterling Commerce® Connect:Direct® as a transfer method, Connect:Direct must be installed, configured, and running within the private network of the financial institution. This Connect:Direct instance is referred to as a Local Node. Another Connect:Direct instance is in the private network of another financial institution and it is called the Remote Node. FTM communicates only with the Local Node, which in turn communicates with Remote Node.

The prerequisites in the following list are needed to configure Gateway Server for Connect:Direct local node.
  • A Connect:Direct instance must be created in the private network of the financial institution. It is called the Local Node.
  • You must have the following information for the Connect:Direct Local Node instance.
    • The name of the primary node.
    • The IP address of the host where Connect:Direct was installed.
    • The host port on which Connect:Direct is listening.
    • The Connect:Direct user ID.
    • The password for the Connect:Direct user ID.
    • The communication protocol to use. For example, TCP/IP.
  • The CDJAI.jar file from the Connect:Direct installation
Use the following steps to configure Connect:Direct to work with FTM.
  1. Get the CDJAI.jar file from the Connect:Direct installation. This file is needed to generate the Connect:Direct configuration file and make the JAR file available to the Gateway Server container. Check the Connect:Direct documentation for the file path.
  2. Connect:Direct requires a CDDEF.BIN file for applications that interface to its API functions. Use the following steps to create the file.
    1. Open a command prompt.
    2. Use the cd command to go to the directory where the CDJAI.jar file is located.
    3. Run the following command.
      java -classpath CDJAI.jar com.sterlingcommerce.cd.sdk.JCU
    4. Provide the following information when prompted:
      Table 1. Configuration fields
      Field Description
      Node Name of the primary node
      Address The IP address of the host where Connect:Direct was installed.
      Port The host port on which Connect:Direct is listening. By default, the port is 1363.
      UserId The Connect:Direct user ID.
      Password The password for the Connect:Direct user ID.
      Protocol The communication protocol to use. For example, TCP/IP.
    5. Move the CDDEF.BIN file to a known location.
  3. Use the <ftm-instance>-gw-server-config ConfigMap to make the CDDEF.bin file available to the Gateway Server.
  4. To make the CDJAI.jar available to the Gateway Server, you must access the root path of the persistent volume pv-ftm-application. Create a folder j2se-gw-config/jars under the root path and copy the CDJAI.jar file into it.
  5. Update the following properties in the Gateway Server configuration.
    • dtaMsgMode
    • cdLocalConfigFile
    • cdLocalReceiveDir
    • cdRemoteNode
    • cdRemotePassword
    • cdTimeout
    For more information about how to customize the Java™ Platform, Standard Edition components, see Customizing the configuration files in a ConfigMap.