on 08-16-2005 4:08 AM
I have a scenario where the vendor requires certain fields and values to be present in the envelope in order to process the message. The envelope has to look as such and an HTTP Post has to be used as the communication.
<?xml version="1.0" encoding=UTF-16?>
<Envelope version="01.00">
<Sender>
<Id>EID001</Id>
<Credential>Test</Credential>
</Sender>
<Recipient>
<Id>http://dev.brassring.com/..etc </Id>
</Recipient>
<TransactInfo transactType="data">
<TransactId>0037</TransactId>
<TimeStamp>2000-10-09T14:14:11Z</TimeStamp>
</TransactInfo>
<Packet>
<PacketInfo packetType="data">
<PacketId>1</PacketId>
<Action> SET</Action>
<Manifest>REQUISITION</Manifest>
</PacketInfo>
<Payload>
.....
</Payload>
</Packet>
</Envelope>
How would one go about manipulating the envelope header information in an HTTP post to match this example? This is apparently some HR-XML standard specification.
Regards,
Chris
Hi Richard,
You can define this XML structure as a Data Type in XI. or You could import the XSD into 'External definitions'.
Use that for your mapping. The output of this map will give you this XML, which can be sent to the target via HTTP Post.
This entire envelope (including its header & payload) acts as a message payload for XI. So you could manipulate the Header or Payload of the envelope during the XI Mapping.
The HTTP adapter can POST the output XML as it is to the target system.
Hope this clarifies.
regards,
Pops V.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
9 | |
8 | |
6 | |
6 | |
6 | |
5 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.