Scenario 1: Installing ITXA and Sterling B2B Integrator as a new installation

In this scenario, ITXA and Sterling B2B Integrator are installed for the first time.

Procedure

  1. Use IBM Installation Manager to install ITXA V10.0.1.5 or higher and verify your configuration.
  2. Install Sterling B2B Integrator V6.1.1 or later, completing the following options:
    1. Select the b2bi4spe installation option.
    2. When prompted, specify the SPE installation directory, the SPE Trading Partner UI port, and the WebSphere® Transformation Extender installation directory.
  3. In the SPE customer_overrides.properties file, uncomment (but do not edit) the following lines:
    HostApplication.name=SBI
HostApplication.migrationStylesheet=ie_si_to_spe_hosted
HostApplication.driverName=InvokeSIBP
HostApplication.driverClass=com.ibm.spe.core.drivers.DriverInvokeSIBusinessProcess
# the port should be set to the value of the REST_HTTP_SERVER_PORT in sandbox.cfg above.
# the ip address is that of the SBI install which should be installed on same machine as SPE.
HostApplication.restURL=https://server:port
    Draft comment: 
    9.55.53.88:13060
    /restwar/restapi/v1.0
  4. Verify your integrated installation:
    1. In the B2Bi_install_dir/bin directory, execute the run.sh command.
      The Trading Partner UI server starts.
    2. When the Sterling B2B Integrator server is up, log in to the Sterling B2B Integrator dashboard.
    3. In the Administration menu, click the link to the Trading Partner UI.
      • The Trading Partner UI server is started, and the Trading Partner UI is displayed.
      • On the Envelopes advanced properties page, the product name reflects that Sterling B2B Integrator is running. It displays as IBM Standards Processing Engine (Hosted Mode B2Bi).
      You can also verify a successful installation by checking for these entries and files:
      1. In Sterling B2B Integrator, the following SPE-specific entries are present in b2bi_install_dir/properties/sandbox.cfg:
        SPE_INSTALL_DIR=/path/to/spe
WTX_INSTALL_DIR=/path/to/wtx
SPE_UI_PORT=14009
REST_HTTP_SERVER_PORT=13060   # this entry is laid down by the b2bi4spe install jar I add it here for clarity.
      2. The b2bi_install_dir/properties/dynamicclasspath.cfg contains SPE files and associated jars: 
        # spe2 and wtx jars, note we need the translator.jar from spe2
VENDOR_JAR=/path/to/spe/jars/log4j-1.2-api-2.17.1.jar
VENDOR_JAR=/path/to/spe/jars/10x-core-2.3.0.15.jar
VENDOR_JAR=/path/to/spe/jars/commons-codec-1.13.jar
VENDOR_JAR=/path/to/spe/jars/event-publisher-sdk-2.0.3.jar
VENDOR_JAR=/path/to/spe/jars/gson-2.2.4.jar
VENDOR_JAR=/path/to/spe/jars/icu4j-55.1.jar
VENDOR_JAR=/path/to/spe/jars/jt400.jar
VENDOR_JAR=/path/to/spe/jars/openjpa-all-2.4.0.jar
VENDOR_JAR=/path/to/spe/jars/spe-10.0-core.jar
VENDOR_JAR=/path/to/spe/jars/spe-10.0-standardsbase.jar
VENDOR_JAR=/path/to/spe/jars/translator.jar
VENDOR_JAR=/path/to/spe/jars/derbyclient.jar
VENDOR_JAR=/path/to/spe/jars/jval2021.jar
VENDOR_JAR=/path/to/spe/jars/spe-10.0-edifact.jar
VENDOR_JAR=/path/to/spe/jars/spe-10.0-rnd.jar
VENDOR_JAR=/path/to/spe/jars/spe-10.0-swift.jar
VENDOR_JAR=/path/to/spe/jars/spe-10.0-tradacoms.jar
VENDOR_JAR=/path/to/spe/jars/spe-10.0-x12.jar
VENDOR_JAR=/path/to/wtx/WTX-DTX/libs/dtxpi.jar
VENDOR_JAR=/path/to/wtx/WTX-DTX/libs/m4spe.jar
VENDOR_JAR=/path/to/wtx/WTX-DTX/libs/xds4j.jar
      3. The b2bi_install_dir/properties/SPEHostingApplication.properties file contains these entries:
        HostApplication.name=SBI
HostApplication.migrationStylesheet=ie_si_to_spe_hosted
HostApplication.driverName=InvokeSIBP
HostApplication.driverClass=com.ibm.spe.core.drivers.DriverInvokeSIBusinessProcess
HostApplication.restURL=https://
        Draft comment: 
        9.55.53.88.116
        server:13060/restwar/restapi/v1.0
      4. The run.sh (Linux or UNIX) or run.cmd (Windows) file includes the entry
        Draft comment:
        near the bottom
        that starts the Trading Partner UI server:
        echo "Starting SPE Server on port 14009 ..."
/path/to/spe/wlp/bin/server start
      5. The hardstop.sh or hardstop.cmd (Windows) file includes the entry
        Draft comment:
        near the bottom
        that stops the Trading Partner UI server: 
        echo "Stopping SPE Server on port 14009 ..."
/path/to/spe/wlp/bin/server stop