Develop > Controller layer > Integrate with back-end systems and external applications > Distributed Order Management (DOM) integration > Configure Distributed Order Management (DOM) integration with the external OMS simulator
Configure the external OMS simulator mediation module on WebSphere Integration Developer
The external OMS simulator mediation module is configured to communicate with WebSphere Integration Developer (WID).
Procedure
- Launch WebSphere Commerce Developer and start the WebSphere Commerce test server.
- Launch WebSphere Integration Developer and create a new workspace.
- Import ExtOMSSimMediationModule.zip as a project interchange into the workspace.
- Navigate to the Business Integration view, expand ExtOMSSimMediationModule and double-click Assembly Diagram to open it.
- In the diagram, right-click the ExtOMSSim and select Show in Properties.
- In the Properties view, select the Binding tab and change the endpoint address to the following URL:
- Save the changes.
- Select the Servers view. Right-click WebSphere ESB Server 6.1 and select Start.
- Once the server starts and synchronizes, right-click the server and select Add and Remove Projects.
- Add the mediation module to the server by selecting ExtOMSSimMediationModuleApp and clicking Add. Click Finish and wait for the mediation module to publish and the server to synchronize.
- Navigate to the Business Integration view, expand Web Service Ports > wsdl.
- Right-click InventoryServices_InventoryServicesPortTypeHttpPort and select Web Services > Test with Web Services Explorer.
- Navigate to the Actions view and select the GetInventoryAvailability web services operation.
- Switch to the source view by clicking Source.
- Replace the message body with the following code snippet:
<q0:GetInventoryAvailability> <q1:ApplicationArea> <q1:CreationDateTime>2008-10-24T20:13:37.750Z</q1:CreationDateTime> </q1:ApplicationArea> <q0:DataArea> <q1:Get> <q1:Expression expressionLanguage="_wcf:XPath">{_wcf.ap=IBM_Store_Details}/InventoryAvailability[InventoryAvailabilityIdentifier/ExternalIdentifier[CatalogEntryIdentifier/ExternalIdentifier[(PartNumber='FULO-0101')] and OnlineStoreIdentifier/ExternalIdentifier[(NameIdentifier='Madisons')]]]</q1:Expression> </q1:Get> </q0:DataArea> </q0:GetInventoryAvailability>
Click Go.
- Navigate to the Status view and switch to the source view by clicking Source.
Confirm that the SOAP response envelope appears similar to the following code snippet:
soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header /> - <soapenv:Body> - <xinv:ShowInventoryAvailability xmlns:_wcf="http://www.ibm.com/xmlns/prod/commerce/9/foundation" xmlns:oa="http://www.openapplications.org/oagis/9" xmlns:udt="http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1" xmlns:xinv="http://www.ibm.com/xmlns/stdwip/commerce/9/inventory" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> - <oa:ApplicationArea> <oa:CreationDateTime xsi:type="udt:DateTimeType">2008-10-24T20:15:37Z</oa:CreationDateTime> </oa:ApplicationArea> - <xinv:DataArea> - <xinv:InventoryAvailability> - <xinv:InventoryAvailabilityIdentifier> - <xinv:ExternalIdentifier> - <xinv:CatalogEntryIdentifier> - <_wcf:ExternalIdentifier> <_wcf:PartNumber>FULO-0101</_wcf:PartNumber> </_wcf:ExternalIdentifier> </xinv:CatalogEntryIdentifier> - <xinv:OnlineStoreIdentifier> - <_wcf:ExternalIdentifier> <_wcf:NameIdentifier>Madisons</_wcf:NameIdentifier> </_wcf:ExternalIdentifier> </xinv:OnlineStoreIdentifier> </xinv:ExternalIdentifier> </xinv:InventoryAvailabilityIdentifier> <xinv:InventoryStatus xsi:type="xinv:InventoryStatusEnumerationType">Available</xinv:InventoryStatus> <xinv:AvailableQuantity uom="C62">100.0</xinv:AvailableQuantity> </xinv:InventoryAvailability> </xinv:DataArea> </xinv:ShowInventoryAvailability> </soapenv:Body> </soapenv:Envelope>
- Stop the WebSphere ESB server.
- Stop the WebSphere Commerce test server.
Results
After completing the steps in order, you have successfully configured the external OMS simulator mediation module on WebSphere Integration Developer.
Previous topic: Configure the external OMS simulator mediation module on WebSphere Enterprise Service Bus
Next topic: Configure the DOM integration feature