Adding a new message mapper for procurement

Procurement systems that use the XML/HTTP protocol need to have a message mapper in order to communicate successfully with WebSphere Commerce.

To add a new message mapper do the following:

  1. If necessary, create a class that implements the com.ibm.commerce.programadapter.messagemapper interface.
  2. Manually add the new message mapper to the group of message mappers in the instance configuration XML file:
    <MessageMapper messageMapperId="#"
    classname="class implementing MessageMapper interface"
    enable="true"
    name="Name of MessageMapper">  
    <configuration
    ECSystemTemplateFile="mapping.xml" EcTemplatePath="e:\newmappingfilepath"
    ECInboundMessageDtdFile="newmwssage.dtd" ECInboundMessageDtdPath="e:\newmessages\dtd" />
    </MessageMapper>
    

    For the Ariba cXML Message Mapper, the configuration entry would look like the following:

    <MessageMapper messageMapperId="-3"
    classname="com.ibm.commerce.messaging.programadapter.messagemapper.ecsax.ECSAXMessageMapper"
    enable="true"
    name="WCBE.ARIBA">
    <configuration
    EcSystemTemplateFile="ariba_sys_template.xml"
    EcTemplatePath="H:\ariba"
    EcInboundMessageDtdFiles="cXML.dtd"
    EcInboundMessageDtdPath="H:\ariba"
    />
    </MessageMapper>
    
  3. Create a mapping file for the procurement protocol messages. Place the file in the directory specified by the EcTemplatePath in the configuration section of the configuration XML file.