Back-end integration messages

• Order notification
  An outbound back-end message is a WebSphere Commerce-generated request that can be sent to an external system. WebSphere Commerce can be configured to generate the Report_NC_PurchaseOrder XML outbound message that allows us to communicate to back-end systems that an order has been placed. The XML message is generated and sent out by the outbound messaging system, encoded in Unicode UTF-8 format. We can also use the legacy Order Create message, which performs a similar function.

• Report_NC_PurchaseOrder message
  The Report_NC_PurchaseOrder message is an outbound message that contains order details for a completed order. The WebSphere Commerce outbound messaging system generates this message using the OrderCreateXML.jsp composition template and sends its data to an outbound message queue, where a back-end system receives the message. This application takes the message and continues any back-end business processes required to complete the specified task for the order. Use Report_NC_PurchaseOrder to fulfill the order process of orders that begin with the WebSphere Commerce system, but also require some additional or back-end work by a separate system.

• Create_WCS_Customer message
  The Create_WCS_Customer message is an inbound message that contains customer information for a customer. 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 adds information for a new customer by calling the UserRegistrationAdd command.

• Create_NC_Customer message
  The Create_NC_Customer message is an inbound message that contains customer information for a customer. 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 information for a new customer by calling the UserRegistrationAdd command.

• Update_WCS_Customer message
  The Update_WCS_Customer message is an inbound message that contains customer information for a customer. 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 information for a customer by calling the UserRegistrationUpdate command.

• Update_NC_Customer message
  The Update_NC_Customer message is an inbound message that contains customer information for a customer. 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 information for a registered customer by calling the UserRegistrationUpdate command. Since the message invokes the same WebSphere Commerce controller command, the message is identical to the Create_NC_Customer message.

• Update_WCS_OrderStatus message
  The Update_WCS_OrderStatus message is an inbound message that contains status information for a WebSphere Commerce order. The message has four possible forms. Although each form of the message has the same XML elements, each one is associated with a different Command. The mapping of message forms to commands is as follows:

• Update_NC_OrderStatus message
  The Update_NC_OrderStatus message is an inbound message that contains status information for a WebSphere Commerce order. 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 OrderStatus command updates the tables ORDSTAT and ORDISTAT with the new order status information.

• Update_WCS_ProductPrice message
  The Update_WCS_ProductPrice message is an inbound message that contains price information for a product. A back-end application generates this message and sends it to the WebSphere Commerce inbound message queue. When the WebSphere Commerce system receives the message, it runs a controller command. The controller command that is run depends on the type of message. The following table shows the two types of messages that can be sent, along with their associated controller commands.

• Update_NC_ProductPrice message
  The Update_NC_ProductPrice message is an inbound message that contains price 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. The system then invokes the ProductOfferPriceUpdate command which updates the OFFERPRICE table with the new price information.

• Update_WCS_ProductInventory message
  The Update_WCS_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.

• Update_WCS_InventoryReceipt message
  The Update_WCS_InventoryReceipt message is an inbound message that contains information for adjusting the inventory for an item. A fulfillment center application generates this message and sends it to the WebSphere Commerce inbound message queue, where the WebSphere Commerce system receives the message. After WebSphere Commerce receives the message, the InventoryAdjust command is invoked.