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) integration
DOM integration enhances the shopping flow in the Aurora starter store, while enhancing backend system integration with WebSphere Commerce. This integration provides comprehensive coverage of the order lifecycle across channels, from capture to fulfillment.
Building a WebSphere Enterprise Service Bus mediation module for DOM integration
Building a simple, yet functional, WebSphere Enterprise Service Bus mediation module for DOM integration by using WebSphere Integration Developer introduces you to several key concepts. These concepts include working with WebSphere Integration Developer as a development platform, working with mediation flows, and using XSL transformation primitives in mediation flows to transform WebSphere Commerce OAGIS BOD messages to and from messages in the backend system's format.
Importing custom XSL files and extension functions into the WESB mediation module
The custom XSL files and extension functions are imported into the WESB mediation module. The custom XSL files are utilized by XSL Transformation primitives in mediation flows to transform WebSphere Commerce OAGIS BOD messages to and from External OMS Simulator messages. The custom XSL files use the extension functions to extract parameters from XPath expressions in WebSphere Commerce OAGIS BOD messages.

Importing custom XSL files and extension functions into the WESB mediation module

The custom XSL files and extension functions are imported into the WESB mediation module. The custom XSL files are utilized by XSL Transformation primitives in mediation flows to transform WebSphere Commerce OAGIS BOD messages to and from External OMS Simulator messages. The custom XSL files use the extension functions to extract parameters from XPath expressions in WebSphere Commerce OAGIS BOD messages.

Procedure

Download the custom XSL files:
- CustomXSLFiles.zip
These custom XSL files are utilized by XSL Transformation primitives in mediation flows to transform WebSphere Commerce OAGIS BOD messages to and from External OMS Simulator messages.
Extract the custom XSL files into a temporary directory, for example, C:\TEMP\ExtOMSSimMediationModuleTutorial\CustomXSLFiles.
In WebSphere Integration Developer, select File > Import.
Select General > File System.
Click Browse and locate the temporary directory selected in step 2.
Select all the files and select ExtOMSSimMediationModule/xslt/custom as the target directory. Create the directories if they do not already exist.
Click Finish.
Select File > Import.
Select General > File System.
Click Browse and locate the WebSphere Commerce EAR directory:
- WC_eardir
- WCDE_installdir/workspace/WC
Select Foundation-Core.jar and Foundation-Server.jar and select ExtOMSSimMediationModuleas the target directory.
Click Finish.
Download the custom XSL extension functions JAR file to a temporary directory, for example, C:\TEMP\ExtOMSSimMediationModuleTutorial:
- MediationUtil.jar
These custom XSL files use the extension functions to extract parameters from XPath expressions in WebSphere Commerce OAGIS BOD messages.
In WebSphere Integration Developer, select File > Import.
Select General > File System.
Click Browse and locate the temporary directory selected in step 13.
Select MediationUtil.jar.
Click Finish.