Activating an integration

After Sterling Order Management System Software and JDA are installed, run the activation. The activation process activates the event handlers and event templates. Existing data is validated to ensure that no existing configurations are overwritten.

Before you begin

Ensure that the organization or organizations that map to your JDA organizations are already created in Sterling Order Management System Software. For information about creating organizations in Sterling Order Management System Software, see the Creating and Modifying an Organization topic. To integrate more than one enterprise, you must run the enterprise activation script (procedure Step 1) for each enterprise code. Before you run the script a second or subsequent time, manually remove any start files (files with the extension .xml.restart).

About this task

This procedure covers an integration that is executed after a new installation or later or after a Sterling Order Management System Software upgrade. Integration start files are in the <INSTALL_DIR>/repository/factorysetup/ibmjda_integration/install/ directory.

To activate the integration:

Procedure

  1. Run the enterprise activation script from the <INSTALL_DIR>/bin directory:
    • UNIX ./sci_ant.sh -DFunctionality=IBMJDA -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml -logfile logfile
    • Windows sci_ant.cmd -DFunctionality=IBMJDA -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml -logfile logfile

    Where,
    enterprise_code is the code for a specific enterprise or, if no code is supplied, is DEFAULT.

    The script activates the event handlers and event templates. Existing data is also validated to ensure that no existing configurations are overwritten.

    If validation fails, the script exits, and an error message is logged in the log file that specifies what might be overwritten.

    Note:

    If your activation script fails due to an OnReleaseOrderOrChange event handler factory setup error, you can attempt the following to correct it:

    • Refactor the factory default event handler with the existing event handler.
    • Run the activator script in override mode to use the event handler that is provided out of the box with the integration.
    Optionally, you can run one of these scripts:
    Table 1. Activation scripts
    To perform this task: Run this script from <INSTALL_DIR>/bin:
    Override the validation UNIX ./sci_ant.sh -DFunctionality=IBMJDA -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml overrideinstall -logfile logfile

    Windows sci_ant.cmd -DFunctionality=IBMJDA -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml overrideinstall -logfile logfile

    Where,
    enterprise_code is the code for a specific enterprise or, if not supplied, is DEFAULT.
    Install factory defaults without overriding the validation UNIX ./sci_ant.sh -DFunctionality=IBMJDA -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml -logfile logfile

    Windows sci_ant.cmd -DFunctionality=IBMJDA -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml -logfile logfile

    Where,
    enterprise_code is the code for a specific enterprise or, if a code is not supplied, is DEFAULT.
    Install only nonconflicting activator data UNIX ./sci_ant.sh -DFunctionality=IBMJDA -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml nonconflictinginstall -logfile logfile

    Windows sci_ant.cmd -DFunctionality=IBMJDA -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml nonconflictinginstall -logfile logfile

    Where, enterprise_code is the code for a specific enterprise or, if a code is not supplied, is DEFAULT.
  2. Remove any start files (files with the extension .xml.restart) from the <INSTALL_DIR>/repository/factorysetup/ibmjda_integration/install/ directory now. If not removed, these files interfere with integration activation for subsequent enterprise codes.
  3. Invocation of Event Actions for the Hub Organization is not required for integration, so there is no need to configure these actions. Thus, set the following property to false in the customer_overrides.properties file:

    yfs.invoke.default.event.handler=false

    For information about configuring this property, see Defining integration properties in IBM OMS.

    If the activation script fails, you can refactor the factory default event handler with the existing event handler. Or, to use the event handler that is provided with this integration, run the activator script in override mode.