ITX pack deployment scenario 2: Install pack runtime components directly on server

Use this approach to industry pack deployment if you are using the ITX Pack for Supply Chain EDI only and using Sterling maps only.

Before you begin

This procedure assumes that you have installed the following on the runtime server (any supported platform):
  • ITXA common components
  • One or more industry packs

About this task

Draft comment:
Includes all info from old 'Deploying packs to a runtime SPE server (WTX not installed)." sgz
This procedure performs pack configuration and imports business rules and code lists, but does not deploy maps. It applies in either of these situations:
  • You are using the ITX Pack for Supply Chain EDI only and using Sterling maps only.
  • You prefer to install industry packs on each runtime system. You are using IBM® Transformation Extender maps and related files, but prefer to deploy them separately.

If you are using the ITX Pack for Healthcare Payers, the ITX Pack for Financial Payments, or IBM Transformation Extender validation maps, see Scenario 3.

Procedure

On each of your runtime servers, perform these steps:
  1. Start the ITXA database.
  2. Deploy and configure the pack or packs by running the spedeploy-packs command:

    (Linux™ and UNIX™) spedeploy-packs.sh -j nojar -d nowtx

    (Windows™) spedeploy-packs.bat -j nojar -d nowtx [-t=tenant_ID]

    -j
    Path to the resource bundle file. Valid value: nojar to specify that only pack server components are deployed.
    -d
    Destination directory. Value for this scenario: nowtx to specify that IBM Transformation Extender validation maps are not used.
    -t
    Indicates the tenant ID under which resources should be imported. If not specified, it defaults to the DEFAULT tenant. Optional.

    This command extracts the files, loads the database, and updates the configuration.

    When the script completes successfully:
    • The database is initialized, and ITX and pack configuration files and resources (code lists, generic acknowledgment envelopes, and so on) are loaded.
    • A message is displayed. Example: Pack files were deployed, configured, and loaded successfully.
    Draft comment:
    Unnecessary map extraction and setup is omitted.
  3. Stop and restart any applications that use ITXA, including the ITXA console window. This allows the application or console window to detect the updated environment.
    Draft comment:
    You can use same console window for HC/EDI, but not SWIFT.