Create a message map with a SOAP message as input and a
SOAP message as output.
This scenario demonstrates how to create a message map
within one operation of a service.
If
you want to use your own application, you can follow the same steps.
The difference is that you create the map in a message flow or subflow
within the application or library referenced by the application.
Complete the following steps to create a map in the IBM® Integration Toolkit:
- Start the New Message Map wizard.
- Identify the SaveAddress operation.
- Double-click the SaveAddress operation
and drag and drop a Mapping node.
- In the Mapping node
properties, select the Description tab, and
enter Normalize_AddressBook_Transform as the Node
name.
- Connect the Normalize_AddressBook_Transform Mapping node
between the two nodes where the message transformation is required.
- Double-click the Normalize_AddressBook_Transform Mapping node
to start the New Message Map wizard.
- Optional: Edit the Map name field
and enter your map name.
You can keep the default name
provided by IBM Integration Bus.
In
the scenario, the map name that you use is the default name SaveAddress_Request_Response_Mapping.map.
- Enter the broker schema name AddressBook in
the field Schema to create a new broker schema.
To organize your resources, and to define the scope of resource
names to ensure uniqueness, you create broker schemas.
For more information about how to create a broker schema in
the IBM Integration Toolkit,
see Creating a broker schema.
After you enter AddressBook as
the name of the broker schema, the
window looks as follows:
- Click Next.
- Select the map inputs and outputs.
- Select the map input SOAP_Domain_MSG{}.
- Select the map output SOAP_Domain_MSG{}.
In the scenario, you have a SOAPInput node
that produces a SOAP_Domain_MSG. A Mapping node
is connected to the SOAPInput node,
and receives as input a SOAP_Domain_MSG message.
Note: In
IBM Integration Bus, you
can choose from multiple inputs and multiple outputs in a message
map. However, you can only select one input and one output for a message
map.
- If you use a SOAPInput node,
you must map the SOAP_Domain_Msg in the SOAP
domain.
- If you use a SOAPInput node
followed by a SOAPExtract node,
you must map the schema associated with your operation in the XMLNSC
domain. You use the SOAPExtract node
to remove SOAP envelopes, allowing just the body of a SOAP message
to be processed.
- If you use HTTP nodes or MQ nodes, you must map the SOAP 1.1 or
the SOAP 1.2 schema as the root model of the map in the XMLNSC domain.
The following figure shows you the options you have
as potential map inputs and map outputs in the scenario:
The following
figure shows what the Select map inputs and outputs window
looks like after you have selected your map input and map output for
a SOAP message transformation:
- Click Next.
- Select the output domain SOAP.
Note: The only domain option available is the SOAP domain.
The following figure shows what the New Message
Map - Select the domain to create the output window looks
like after you have selected the domain.
- Click Finish.
The message map SaveAddress_Request_Response_Mapping.map is
created in the Application Development view,
within the folder Maps located under your AddressBookProvider service project.
The map is created under the AddressBook schema.
The map opens
in the Graphical Data Map editor. The following figure shows what
the map looks like when it is first opened.