Develop > Controller layer > Integrate with back-end systems and external applications > Distributed Order Management (DOM) with Sterling Selling and Fulfillment Suite (SSFS) > Install, Configuring and Deploying

Install, Configuring and Deploying: WESB Mediation Module

The method of integration between WebSphere Commerce and Sterling Selling and Fulfillment Suite is a WebSphere Enterprise Service Bus (WESB) mediation module. This module requires WebSphere Integration Developer (WID) 7.0.0.3 and WESB 7.0.0.3.

To extend or modify the Mediation Module, import the project into a WID workspace.

Procedure

1. Import the Mediation Module into WID:

   1. Select File > Import.

   2. Select General > Existing projects into Workspace.

   3. Select the Mediation Module project archive file. The project can be either a JAR or folder. The mediation module project can be found in WCDE_INSTALL/components/sterling-integration/wid with the name WCToSSFSMediationModule.

      The Mediation Module has some dependencies from WebSphere Commerce. Add the following libraries:

      • Foundation-Core.jar

      • Foundation-Server.jar

2. Make any necessary changes to the Mediation Module:

   1. Once the mediation module has been imported into the WID workspace, you can modify it as necessary so that it will work within the specific environment.

   2. Once you have made the desired changes, modify the Mediation Module according to the following steps:

      1. Set the WebSphere Commerce Order Services Endpoint URL.

         For the WESB mediation module to communicate correctly with WebSphere Commerce, it must be configured with the proper hostname and port.

         1. Open up the assembly diagram in the WCToSSFSMediationModule.

         2. Open the Properties View.

         3. Click on the WCOrderServicesImport.

         4. Choose the Binding tab in the properties view.

         5. Enter the correct Address.

      2. Set the WebSphere Commerce Order Services Security Information.

         WebSphere Commerce uses the standard WS-Security to provide security for its web services. The WESB mediation module must be configured to utilize this security correctly.

         1. Launch the WESB integrated solutions console and logon.

         2. Navigate to Services > Policy set > Application policy sets > and select Import > From selected location.

         3. Select the following file:

            • WCServicesPolicySet.zip

            Click OK.

         4. Navigate to Services > Service clients and select OrderServices.

         5. Select OrderServices and select Attach Client Policy Set > WCServicesPolicySet.

         6. Select OrderServices and select Attach Binding > New Application Specific Binding.

         7. Enter WCServicesBinding as the name of the binding configuration and select Add > WS-Security.

         8. Navigate to Authentication and protection and select request:token_auth.

         9. Click Apply.

         10. Navigate to Callback handler.

         11. Enter the wcsadmin username and password and click OK.

         12. Save the WESB configuration changes.

      3. Adjust the SSFS Organization Code in the Mediation Flows.

         Most calls to the SSFS APIs require an Organization Code. As this code is global in nature, specify it in the WESB mediation module.

         To change this code to fit the environment:

         1. Open the WCToSSFSMediationModule component in WID.

         2. For each of the services listed below, adjust the value set in the OrganizationCodeSetter element:

            • ProcessOrder

            • GetInventoryAvailability

            • ProcessInventoryRequirement

      4. Enable/Disable Mediation Flow Tracing

         Trace primitives are used all over the mediation flows to log messages in the server's SystemOut.log. For example, the incoming GetInventoryAvailability BOD and the resulting findInventory input message. In WID, you can enable and disable these traces by opening the mediation flows. The enablement of these traces are also set as promoted properties with aliases in the form of *Trace.enabled. For example, GetInventoryAvailabilityTrace.enabled and FindInventoryInputTrace.enabled. They can be enabled and disabled in WESB using the Administration Console. See Promoted properties for more information.

3. Deploy the Mediation Module to WESB:

   Once changes have been made and tested using WID and the WESB test environment, you can export the mediation module as a deployable resource. You can then deploy the ear into a standalone WESB install.

   To export a deployable resource from WID:

   1. Right click on the WCToSSFSMediationModule project and click Export.

   2. Select Integration Modules and Libraries.

   3. Ensure Files for Server Deployment is selected and click Next.

   4. Select the location of the generated EAR file and click Finish.
   To install the generated EAR into a WESB server:

   1. Log into the WESB administration console.

   2. Navigate to Applications > SCA Modules.

   3. Click Install.

   4. Click Browse and select the mediation module EAR.

   5. Select the server or cluster to install the module into and click Next.

   6. When the install completes, click Save.

   See the WID and WESB Information Centers for more information:

   • WID Information Center

   • WESB Information Center

4. Configure JMS for WESB:

   As WESB communicates to SSFS via JMS, our environment must be configured to enable this. In our case, we are using the default messaging implementation of our WESB server as our JMS provider. When the WESB mediation module is deployed to the server, most of the necessary configuration is completed automatically for us. After the module is deployed, the only thing we have to do ourselves is create a JMS Queue Connection factory:

   1. Log into the WESB administration console.

   2. Navigate to Resources > JMS > Queue Connection Factories.

   3. Select New.

   4. Select Default Messaging Provider and click Next.

   5. Enter the following required information:

      Name

      WCToSSFSMediationModule.SSFSAPIsImport_QCF

      JNDI Name

      WCToSSFSMediationModule/SSFSAPIsImport_QCF

      Bus Name

      SCA.APPLICATION.CELL_NAME.Bus

      Provider Endpoints

      SERVER_HOSTNAME:7276:BootstrapBasicMessaging, SERVER_HOSTNAME:5557:BootstrapSecureMessaging

   6. Click OK, then click Save.

What to do next

Install, Configuring and Deploying: SSFS

+

Search Tips   |   Advanced Search