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.
Back-end integration legacy messages
The WebSphere Commerce offers support for messages which use the legacy message format. Unless you are migrating from a previous version of WebSphere Commerce Suite, it is recommended that you use the XML messages instead, since they accomplish the same function, and are easier to read and maintain.
Customer New message
The Customer New message is a legacy format 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 controller command.
DATUSR_DATA for inbound messages
The inbound messages Order Status Update, Customer New, and Customer Update, include the DATUSR_DATA data segment. Include the DATUSR records in these messages to receive additional data. You can customize the fields to pass extra data that is not included in the messages. DATUSR_DATA can be repeated multiple times.

DATUSR_DATA for inbound messages

The inbound messages Order Status Update, Customer New, and Customer Update, include the DATUSR_DATA data segment. Include the DATUSR records in these messages to receive additional data. You can customize the fields to pass extra data that is not included in the messages. DATUSR_DATA can be repeated multiple times.

The format and the source of the fields for DATUSR_DATA are described in the following table:


Field Name	Field Type	Description
NC_FieldName	CHAR (8)	Name of the new field to be added.
NC_FieldLength	CHAR (10)	Length of the NC_FieldValue field.
NC_FieldValue	CHAR (variable)	Text string for the value of the new field.