Activating a Direct Integration

Side-by-side integration is done after Sterling Order Management and WebSphere Commerce are installed, and involves running two scripts. The process activates event handlers, event templates, and user exit implementations. Existing data are validated to ensure that no existing configurations are overwritten.

Before you begin

The Organization or Organizations that map to your WebSphere Commerce Store or Stores should already be created in Sterling Order Management. To integrate more than one enterprise, you must run the enterprise activation script (procedure Step 3) once for each enterprise code. Before running the script a second or subsequent time, manually remove any startup files (files with the extension .xml.restart).

About this task

This procedure covers an integration that is done after a new installation, at a later date, or after a Sterling Order Management upgrade. Integration startup files are in the <INSTALL_DIR>/repository/factorysetup/scwc_integration/install/ directory.

To disable an activation, manually disable the user exits configured for the integration.

To activate the side-by-side integration:

Procedure

  1. (Default enterprise only; not required for non-default enterprise.) To activate integration for the DEFAULT enterprise:
    1. Navigate to the <INSTALL_DIR>/repository/factorysetup/scwc_integration/XMLS/ directory.
    2. Open SCWC_ACT_YFS_GRAPH_UI.xml for editing.
    3. Remove the attribute GraphUIKey by removing the line GraphUIKey="#{EnterpriseCode}_GUI1" from the following records in the XML:
      GraphRefKey="DEFAULT_EVENT_KEY_224"
GraphRefKey="DEFAULT_EVENT_KEY_219"
GraphRefKey="2002081502"
GraphRefKey="DEFAULT_EVENT_KEY_01"
  2. Run the non-enterprise activation script from the <INSTALL_DIR>/bin directory:
    • UNIX./sci_ant.sh -DFunctionality=SCWC-SDF installnonenterprise -f integration_load_defaults.xml -logfile logfile
    • Windowssci_ant.cmd -DFunctionality=SCWC-SDF installnonenterprise -f integration_load_defaults.xml -logfile logfile
  3. Run the enterprise activation script from the <INSTALL_DIR>/bin directory:
    • UNIX./sci_ant.sh -DFunctionality=SCWC-SDF -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml -logfile logfile
    • Windowssci_ant.cmd -DFunctionality=SCWC-SDF -DEnterpriseCode=enterprise_code -f integration_load_defaults.xml -logfile logfile
  4. Remove any startup files (files with the extension .xml.restart) from the <INSTALL_DIR>/repository/factorysetup/scwc_integration/install/ directory at this time. If not removed, the presence of these files interferes with integration activation for subsequent enterprise codes.
  5. Invocation of Event Actions for the Hub Organization is not required for Direct Integration, so there is no need to configure these actions. Accordingly, configure this 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 Sterling Order Management.

    If the activation script fails, you can refactor the factory default eventhandler with the existing eventhandler, or run the activator script in override mode to use the eventhandler provided with this integration.