Chapter 7. Scenario: Data transformation and security 201
XML
The XML message format is called XML_SAM730. It contains message
definitions that are created by using the Create Message Definition from... wizard
(Figure 7-33). The message definitions were created from the bank.wsdl file
(BankPortType interface) and from both the service definitions schema,
bank_definitions.xsd, and legacy-service (plain XML service definitions) schema,
legacy.xsd.
Figure 7-33 Create new message definition from a WSDL wizard
When the MRM domain receives a SOAP message through an input node, the
HTTPInput node, it parses the message using the Envelope message type that
was created automatically by the wizard. Therefore, the broker cannot parse
business elements inside the SOAP Body tag.
MRM domain: The following steps are necessary only if you are using the
MRM domain as the message structure parser.
202 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
To resolve this issue after the wizard completes:
1. Open the soapenv11.mxsd definition in the
org.xmlsoap.schemas.soap.envelope namespace.
2. Select the soapenv11.mxsd file in the navigation view and then select the
Properties view. See Figure 7-34.
Figure 7-34 Properties view of soapenv11.mxsd
3. Right-click Imports and select Add Import.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.