Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Controller layer
The Controller layer is the conductor of operations for a request. It controls the transaction scope and manages the session related information for the request. The controller first dispatches to a command and then calls the appropriate view processing logic to render the response.
Integrating with back-end systems and external applications
External systems integration is a key feature of the WebSphere Commerce solution. In WebSphere Commerce business logic is enabled for integration and built-in adapters and interfaces are provided for common integration points. Additionally, the WebSphere Commerce integration solution leverages integration standards by using various IBM connectivity solutions.
Distributed Order Management (DOM) with Sterling Selling and Fulfillment Suite (SSFS)
WebSphere Commerce can interact with an external Distributed Order Management (DOM) solution. You can use WebSphere Commerce DOM integration with Sterling Commerce and Sterling Selling and Fulfillment Suite (SSFS) as a starting point and as building blocks for your integration scenarios.
Integration flows
The supported integration flows are implemented considering several assumptions. Assumptions such as a single ship node per store (physical or online), WebSphere Commerce handling payments, and the catalog not containing bundles or kits are considered. Additional assumptions can be enabled with further customization.
Sync order fulfillment status
The sync order fulfillment status communication map is a push from SSFS to WebSphere Commerce. It maps the SSFS getOrderDetails and SSFS getShipmentDetails APIs to the WebSphere Commerce SyncOrder message. As both WebSphere Commerce and SSFS are customizable, assumptions are made with the mapping from one system to the other.

Feature Pack 4

Feature Pack 2

Feature Pack 3

Sync order fulfillment status

The sync order fulfillment status communication map is a push from SSFS to WebSphere Commerce. It maps the SSFS getOrderDetails and SSFS getShipmentDetails APIs to the WebSphere Commerce SyncOrder message. As both WebSphere Commerce and SSFS are customizable, assumptions are made with the mapping from one system to the other.

The assumptions made for this call are:

getOrderDetailsRequest
WebSphere Commerce path	Source
_ord:OrderIdentifier/_wcf:UniqueID	@OrderNo The "WC_" is removed from the beginning if needed
_ord:OrderStatus/_ord:Status	@MaxOrderStatus The following will choose the status: WebSphere Commerce status: R. SSFS order status: >= 3200 and < 3700 WebSphere Commerce status: B. SSFS order status: 1300 or 1400

getShipmentDetailsRequest
WebSphere Commerce path	Source
_ord:OrderIdentifier/_wcf:UniqueID	Shipment/ShipmentLines/ShipmentLine/@OrderNo
_ord:OrderStatus/_ord:Status	S
_ord:OrderItem/_ord:OrderItemIdentifier/_wcf:UniqueID	Shipment/ShipmentLines/ShipmentLine/@PrimeLineNo And Shipment/ShipmentLines/ShipmentLine/@SubLineNo If the "@SubLineNo" is not empty, append it to "@PrimeLineNo" with "-" as a separator
_ord:OrderItem/_ord:OrderItemStatus/_ord:Status	D

Feature Pack 3

To disable the deposit action when WebSphere Commerce receives the SyncOrder message with orderitems status of "D", add the following snippet to the order component's wc-admin-component.xml file:


<_config:configgrouping name="SyncOrder">
  <_config:property name="finalizePayment" value="false"/>
</_config:configgrouping>

That is, Sterling DOM might have already deposited the payment and WebSphere Commerce does not need to deposit the payment again once the order shipment is confirmed.