Configuring integration between Sterling Configurator, WebSphere Commerce, and Sterling Order Management

You can configure an end-to-end integration between WebSphere Commerce, Sterling Configurator, and Sterling Order Management.

1. Set the Catalog Organization in Sterling Configurator.
   1. As an administrator, log on to Sterling Configurator by pointing your browser to http://<hostname>:<port>/smcfs/console/login.jsp (or start.jsp) where,
      • hostname is the computer name or IP address of the computer where Sterling Configurator is installed.
      • port is the listening port of the computer where Sterling Configurator is installed. You can obtain the port from the HTTP transport port line in <Configurator_profiledir>/logs/AboutThisProfile.txt.
      The browser displays the Sign in window. Enter your login ID and password and choose the Sign In button.
   2. Log into the Applications Manager. In the Console Home Page, choose Configuration > Launch Applications Manager.
      Note: To run the Applications Manager, use Internet Explorer with the required Java plugin and ensure that the pop-up blocker in Internet Explorer is turned off.
   3. Click Applications > Application Platform. From the tree in the application rules side panel, choose Participant Modeling > Participant Setup.
   4. Create a new enterprise organization with the same name as the Sterling organization. The Sterling organization is the organization that you created when integrating WebSphere Commerce and Sterling Order Management. For example, if your Sterling organization is named, AuroraESite, ensure that you name the new enterprise, AuroraEsite.
   5. After creating the enterprise organization, locate the Sterling organization that you are using for the WebSphere Commerce and Sterling Configurator integration. To locate the Sterling organization, in the Organization Search window, click the Search icon on the right, choose the organization, and then double-click the organization.
   6. On the right-hand side, click Roles & Participation > Advanced Attributes > Catalog and then click the Catalog tab. Select the Catalog Organization. The selected Catalog Organization is the enterprise organization that you created in step 1d.
   7. Click Save.
2. Configure Sterling Configurator locations in Sterling Order Management:
   1. In the Applications Manager, click Applications > Application Platform. From the tree in the application rules side panel, choose System Administration and select Sterling Configurator.
   2. Set the model repository, rule location, and the location of property files. An example of the model repository is /home/wasuser/vm_oms/configurator/model; an example of the rule location is /home/wasuser/vm_oms/configurator/rules; and an example of the property file directory is home/wasuser/vm_oms/configurator/properties.
   3. Manually create the locations from step 2b.
3. Configure Sterling Order Management security:
   1. In the Applications Manager, click Applications > Application Platform > Load Rules for Organization, and then choose the organization, WCIntegrationOrg, from the Organization list. Click OK. The organization name on the left navigation bar is updated to show your selection.
   2. Click Security > Groups. From the group list, double-click the WCIntegrationGroup group.
   3. Enable grant permissions to services by clicking Permissions on API Security. Click Services, choose SCWC_SDF_getOrderLineDetails, click Grant Permission, and then Save.
4. Copy the Sterling Configurator JAR files and model repository to Sterling Order Management:
   1. In Sterling Order Management, copy the following JAR files to the rule location that you created in step 2c:
      • <OMS_installdir>/jar/smcfs/current_version/cmgt-configurator.jar
      • <OMS_installdir>/jar/smcfs/current_version/cmgt-configuredItem.jar
      • <OMS_installdir>/jar/smcfs/current_version/cmgt-rulesEngine.jar
   2. Copy models from Sterling Configurator to Sterling Order Management. Copy all contents from the Sterling Configurator model repository to the Sterling Order Management model repository that you created in step 2.
5. Disable BOM validation in Sterling Order Management:
   1. Open <OMS_installdir>/repository/xapi/template/merged/xsl/scwc/ProcessOrderToCreateOrderInput.xsl.
   2. Locate the <xsl:attribute name="BypassPricing">Y</xsl:attribute> element.
   3. Add <xsl:attribute name="SkipBOMValidations">Y</xsl:attribute> after <xsl:attribute name="BypassPricing">Y</xsl:attribute>.
   4. Build the resources.jar file. Run the deployer.sh (or deployer.cmd on Windows) utility from the <OMS_installdir>/bin directory. For example,

      ./deployer.sh -t resourcejar

   5. Rebuild and deploy the EAR. Run the following command:

   ./buildear.sh -Dappserver=websphere -Dwarfiles="smcfs,sbc,sma" -Dnowebservice=true -Dnodocear=true -Dsupportmultiwar=true -Ddevmode=true -Dearfile=smcfs.ear

6. Use Sterling Business Center (http://sc_hostname:sc_port/sbc) to create a configurable item in Sterling Order Management. Table 1 shows item mappings between WebSphere Commerce and Sterling Order Management.

   Table 1. WebSphere Commerce and Sterling Order Management item mappings

   WebSphere Commerce name	Sterling Order Management name
   Dynamic Kit Predefined Dynamic Kit	Configurable bundle

   For more information, see Creating a configurable item in IBM Sterling Business Center .

   .