Installing the external OMS simulator
The external OMS simulator is installed as an enterprise application and tested using a Web services client. It is used to simulate the behavior of a DOM system, where generic inventory levels are generated and used in the storefront to display stock availability.
Procedure
-
Install ExtOMSSim as an enterprise application.
- Install ExtOMSSim as an enterprise application using the WebSphere Application Server Administrative Console:
- Start the WebSphere Commerce Server.
- Open the WebSphere Application Server Administrative Console.
- Navigate to .
- Install ExtOMSSim.ear, contained in the
.zip file archive, as an enterprise application with the following properties:
Property Value Map modules to servers server1 Map virtual hosts for Web modules ExtOMSSimWeb
- Install ExtOMSSim.ear
as an enterprise application project using WebSphere Commerce Developer:
- Launch WebSphere Commerce Developer.
- Import ExtOMSSim.ear, contained in the .zip file archive, as an EAR file into the workspace, and add the resulting ExtOMSSim enterprise application project to the server.
- Start the WebSphere Commerce test server.
- Install ExtOMSSim as an enterprise application using the WebSphere Application Server Administrative Console:
-
Create the ExtOMSSimWeb virtual host, if it has not been created automatically during the
preceding step.
-
In the WebSphere Application Server Administrative Console, navigate to .
-
Restart the following servers:
- Restart the WebSphere Commerce server.
- Restart the WebSphere Commerce test server.
- Ensure that the external OMS simulator has been successfully enabled by navigating to the following URL: http://hostname:9980/ExtOMSSimWeb/services/ExtOMSSim?wsdl
-
Use a Web services client, for example, Rational Application Developer's Web Services Explorer,
to test the external OMS simulator.
The following request tests its getInventory Web services operation:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:q0="http://test" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SOAP-ENV:Body> <q0:getInventory> <skuArray> <string>FULO-0101</string> </skuArray> <ffmcIdArray> <string>Aurora Home</string> </ffmcIdArray> </q0:getInventory> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
<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> <p316:getInventoryResponse xmlns:p316="http://test"> <getInventoryReturn> <Inventory> <sku>FULO-0101</sku> <fulfillmentCenterId>Aurora Home</fulfillmentCenterId> <quantityOnHand> <value>100.0</value> <uom>C62</uom> </quantityOnHand> <expectedInventory> </expectedInventory> </Inventory> </getInventoryReturn> </p316:getInventoryResponse> </soapenv:Body> </soapenv:Envelope>
- Close the Administration Console.
- Stop the following servers: