WebSphere Commerce EnterpriseWebSphere Commerce Professional

Mapping a modified Business Object Document message to a new or existing command

This section explains how to map a modified BOD message to a new or existing command.

About this task

Note: If the addition to the BOD message is in the User data element, then the default command mapping will transfer the name/value pairs to the request properties of the controller command automatically, and the steps on this page are not necessary.

Procedure

  1. Identify the current mapping file and make a new copy of it. The IBM Sales Center mapping files are by default located in the XML Configuration Directory as follows:
    • SolarisLinuxWindowsAIXFor IBM i OS operating system WC_eardir/xml/messaging
    • WebSphere Commerce Developer workspace_dir\wc\xml\messaging

    The file naming convention used by the IBM Sales Center is <noun><verb>BODMapping.xml, for example, CreateCustomerBODMapping.xml. The copy of the file will need to be in the same directory as the original, and should be uniquely identified as a file used for extensions, for example: ExtendedCreateCustomerBODMapping.xml

  2. Add the modified attributes of the BOD information to the copied version.
  3. WebSphere Commerce uses the !ENTITY declarations to include different files for each of the document command mappings, and has extended the message mapper declaration to include a file for extensions called webservice_SOABOD_template.extension.xml. You can update this file to easily include your own extensions and this will allow you to easily create your own message mapper file and include those documents that you want to leave alone and any additional or changed mappings that you want to define. The message mapper files are located in the XML Configuration Directory:
    • SolarisLinuxWindowsAIXFor IBM i OS operating system WC_eardir/xml/messaging
    • WebSphere Commerce Developer workspace_dir\wc\xml\messaging

    The new extension file will need to be included in webservice_SOABOD_template.extension.xml. This is done using the !ENTITY directive. For example, after you modify the file to add the webservice_SOABOD_template.extension.xml definition, the would be as follows:

    
    <!DOCTYPE ECTemplate SYSTEM 'ec_template.dtd' [ <!-- Source
    comment: this [ is required, do not remove -->
    
    <!ENTITY ExtendedCreateCustomerMappingDefinition SYSTEM
    'ExtendedCreateCustomerBODMapping.xml'>
    
    ]> <!-- Source comment: this ]> is required, do not remove
    -->
    
    <ECTemplate>
    
    &ExtendedCreateCustomerMappingDefinition;
    
    </ECTemplate>
    
    Note: To update files in the XML Configuration Directory, you must deploy them in the WebSphere Application Server Administration Console.