Installing, Configuring, and Deploying

Integrating WebSphere Commerce and Sterling Selling and Fulfillment Suite (SSFS) involves three relatively complex tasks. Use WebSphere Commerce, WebSphere Enterprise Service Bus Mediation Module, and SSFS to complete these tasks.

Important: Review the following information for your version of WebSphere Commerce:

Review information about APAR fixes for integration of IBM WebSphere Commerce and IBM Sterling Order Management. For more information about integrating IBM WebSphere Commerce Version 7 Feature Pack 8 (or later) with IBM Sterling Order Management Release 9.3, see WebSphere Commerce integration with Sterling Order Management. For more information about integrating IBM WebSphere Commerce Version 7 Feature Pack 5 (or later) with IBM Sterling Order Management Release 9.2.1 (or later), see WebSphere Commerce integration with Sterling Order Management.
You can integrate Sterling Order Management with WebSphere Commerce using either Direct Integration or IBM® WebSphere Enterprise Service Bus (WESB) integration. With Direct Integration, the functions to convert message content and format are performed by services in the Sterling Order Management Service Definition Framework (SDF). For information about using Direct Integration to integrate Sterling Order Management with WebSphere Commerce, see Direct Integration with WebSphere Commerce.

The following software versions are supported:

WebSphere Commerce version 7 with Feature Pack 2
WebSphere Commerce version 7 with Feature Pack 3
WebSphere Integration Developer version 7.0.0.3
WebSphere Enterprise Service Bus version 7.0.0.0
Sterling Selling and Fulfillment Suite (SSFS) version 9.0
Sterling Selling and Fulfillment Suite (SSFS) version 9.1

The interim fix for the following WebSphere Commerce APAR is required for Sterling Order Management and Sterling Configure, Price, Quote to work together. For example, for dynamic kit integration:

JR41313

Note: If your are integrating WebSphere Commerce with both Sterling Order Management and Sterling Configure, Price, Quote, you must deploy Sterling Order Management on a different WebSphere Application Server instance than Sterling Configure, Price, Quote. The WebSphere Commerce integration with both Sterling Order Management and Sterling Configure, Price, Quote does not work if they are deployed on the same WebSphere Application Server instance.

The following Sterling Selling and Fulfillment Suite (SSFS) fix are required for integration with WebSphere Commerce:

312986: For a GMT format, the application must support the character 'Z' as the timezone identifier for all date and time fields that are passed as API input.
349948, 351054: The Real-Time Availability Monitor (RTAM) agent computes and publishes OnhandAvailableQuantity attribute as zero (Required for support of the Infinite inventory configuration).

To obtain these fixes:

For Sterling Selling and Fulfillment Suite (SSFS) version 9.1: Use Fix Pack 35 or higher, which includes these fixes.
For Sterling Selling and Fulfillment Suite (SSFS) version 9.0: Contact Sterling Support and request them to provide fixes for the previously listed defects.

A high-level list of tasks to complete to perform correct integration functionality:

Configure WebSphere Commerce to use an external order management system (OMS).
Modify the WebSphere Enterprise Service Bus mediation module so that the data is translated correctly between WebSphere Commerce and SSFS.
Deploy the WebSphere Enterprise Service Bus mediation module.
Configure SSFS to respond to JMS API requests.
Configure SSFS to send order status updates to WebSphere Commerce.
Synchronize data between WebSphere Commerce and SSFS.