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.
Integration XML messages
WebSphere Commerce offers support for inbound and outbound messages that use the XML format. Each inbound message invokes specific behaviors within the WebSphere Commerce Server by executing a controller command. Each controller command in turn performs operations on the WebSphere Commerce database and subsystems. Some controller commands can be executed by more than one XML message. In addition, some messages can invoke different commands, depending on the content of the message.
Back-end integration messages
Update_NC_ProductInventory message
The Update_NC_ProductInventory message is an inbound message that contains inventory information for a product. A back-end application generates this message and sends it to the WebSphere Commerce inbound message queue, where the WebSphere Commerce system receives the message. WebSphere Commerce updates the INVENTORY table with the new inventory information.

Update_NC_ProductInventory message

The Update_NC_ProductInventory message is an inbound message that contains inventory information for a product. A back-end application generates this message and sends it to the WebSphere Commerce inbound message queue, where the WebSphere Commerce system receives the message. WebSphere Commerce updates the INVENTORY table with the new inventory information.

The Update_NC_ProductInventory message uses the XML message format and follows Update_NC_ProductInventory_10.dtd.

Note: It is recommended that you use the Update_WCS_ProductInventory message in place of Update_NC_ProductInventory as it is an improved version. When using the Update_WCS_ProductInventory message, the ProductNumberByMerchant field can be optionally replaced by ProductSKU.

The format and the source of the XML element values are described in the following table. For a description of the database column, follow the link to its associated table. Fields are optional unless otherwise noted. The tag value length in the XML message for database fields of type INT, BIGINT and DOUBLE should be CHAR (10), CHAR(19), and CHAR(16) respectively.


Level	XML Element	Comment	Table Name	Column Name
1	ProductNumber ByMerchant	Mandatory	INVENTORY	CATENTRY_ID
2	MerchantID	Mandatory	INVENTORY	STORE_ID
3	Quantity	Mandatory	INVENTORY	QUANTITY
4	UserData		N/A	N/A

Behavior:

The WebSphere Commerce product reference number (which references CATENTRY_ID in the INVENTORY table) and the merchant reference number (STORE_ID) are used to update a row in the INVENTORY table.
If the row in the table INVENTORY does not exist, an exception occurs.