ConfiguringSterling Selling and Fulfillment Foundation to use WebSphere default messaging

Configure Sterling Selling and Fulfillment Foundation to use the WebSphere® Default Messaging queues.

About this task

To configure WebSphere Default Messaging:

Procedure

  1. Set the shared library path for UNIX and LINUX system as follows:
    set <Shared_Library_Path_Name>=<dm_java_install_path>/lib 

    where <Shared_Library_Path_Name> is the shared library path environment variable for your operating system.

    For example:

    • On AIX® it is: LIBPAT
    • On Linux it is: LD_LIBRARY_PATH
  2. If Agent or Integration Servers communicate with the WebSphere Default Messaging, install the WAS client. The WAS client needs to be the exact version, including fix pack as the WAS server.
  3. Add the following command to the startIntegrationServer.sh script prior to the java line:
    ${WAS_CLIENT_HOME}/bin/setupClient.sh

    where ${WAS_CLIENT_HOME} is the installation location of the WAS client.

  4. Edit the startIntegrationServer.sh script to run the Agent or Integration Server to add the following system property:

    -Djava.ext.dirs=$WAS_EXT_DIRS $SERVER_ROOT $CLIENTSAS.

  5. Ensure that the following changes are made to the startIntegrationServer.sh (or cmd) startup script located in the <INSTALL_DIR>/bin directory to include the changes made in 3 and 4.

    WAS_CLIENT_HOME=<path of where WAS client installation>

    export WAS_CLIENT_HOME
    ${WAS_CLIENT_HOME}/bin/setupClient.sh

    java -Djava.ext.dirs=$WAS_EXT_DIRS $SERVER_ROOT $CLIENTSAS

    ${BOOTCLASSPATH} ${JAVA_OPTIONS}  -cp ${CLASSPATH}
    com.yantra.integration.adapter.IntegrationAdapter "$1"