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.

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.

The following data describes the Customer New message:


<ECEDOC>
<PROLOG>CUSTOMER_UPDATE_PROLOG_DATA</PROLOG>
<HEADER>
    <HDR010>CUSTOMER_UPDATE_HDR010_DATA</HDR010>
    <USRLST>
        <DATUSR>DATUSR_DATA</DATUSR>                   
.                  
.DATUSR repeated loop                    
.
        <DATUSR>DATUSR_DATA</DATUSR>
    </USRLST>
</HEADER>
</ECEDOC>

Notes:

All records are in sequential order in the buffer. Indentation is used here for readability; it does not appear in the buffer.
All fields in the data segments are left-justified and padded to the right with spaces in the buffer.

Data Segments for Customer New

CUSTOMER_NEW_PROLOG_DATA Specifies the type of message the application data defines. In this case, the message is Customer New.
CUSTOMER_NEW_HDR010_DATA Specifies customer information within the Customer New message.
DATUSR_DATA Specifies optional information to be added to the Customer New message. DATUSR_DATA appears in the <HDR> section of this message.