HTTP Receiver - need ENV:Envelope TransactionID......

I need the following, and I don't know what this ENVELOPE is.
If my mapping doesn't provide these tags, I know I can use a XLST mapping. But I'm horrible in XLST.
<?xml verison="1.0" encoding="utf-8" ?>
<ENV:Envelop TransactionID='12345abcde' xmlns:ENV="schemas-hiwg-org-in:EnvelopeV1.0">
<ENV:SenderID>Sender</ENV:SenderID>
<ENV:RecipientID>Recv</ENV:RecipientID>
<ENV:DocumentCount>2</END:DocumentCount>
<Document>
</Document>
<Document>
</Document>
</ENV:Envelope>
Does anyone know an easy way to accomplish this?
<Document>...</Document> is easy. They are part of my Message Type. How do I get these ENV tags in? If XLST is the only answer, does anyone have a quick example?
<ENV:DocumentCount> is a variable.

okay, I have made some progress.
I have <ns0:MT_DocType>.
I can replace ns0 with ENV inside XMLAnonymizer.
As for renmaing MT_DocType to Envelope, I will have to use XSLT.
Does this sound right?
anyone have any inputs?
Thank you
Bill

Similar Messages

Hi! I need steps for HTTP Receiver adapter

My scenario is like this:
HTTP(HTTP Sender adapter)->XI->File(File adapter).
For this Iam sending the data as payload in the body of HTTP. Now What am i going to do is the opposite of above scenario:
File(FileAdapter)->XI->(HTTP Receiver Adapter)HTTP.
I would like to know what are the steps to transfer a file(xml) from File adapter to XI and from there to Http.
How to send the data using File adapter. Please suggest me some steps.
Hoping a quick response!!!
Thanks in advance!

Hi Datta,
For a HHTP -> XI -> FILE Scenario:
DESIGN:
1. Create DataTypes for source and Destinations. Create elements for all the text fields of your HTTP Client so that they can all be mapped into the destination file
2. Create MessageTypes for the two datatypes.
3. Create Message Interfaces. The One for HTTP is the sender, Asynchronous ( as no response is expected) and one for File is receiver, asynchronous.
4. Do the mapping. It will be mostly a one to one mapping of the fields.
5. Create the Interface Mapping.
Configuration:
1. Import your Business System under your Configuration Scenario.
2. Create 2 communication channels. One for Http as a sender and one for File as a receiver.
Check these links for the configuration part.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
3. Do the Receiver Agreement for file. HTTP doesnt need a sender agreement.
4. DO the Receiver Determination and Interface Determination.
Weblog which talk about the same scenario:-
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
(use case) and explained it...
Check this SDN tv demo, it has detail of HTTP adapter setup.
https://media.sdn.sap.com/SDNTV/main.asp?mediaId=107
Refer to this link for adapter settings.
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
You should also have a HTTP client to send message to XI. In the connecting parameters to XI u have to use the URL in the pattern mentioned by Alex. U have to give all the configuration details in the URL.
Regards,
Abhy
Message was edited by: Abhy Thomas

Receive complete SOAP Envelope as message

Dear all
I have a web service that I have to consume which has a signature value in the SOAP header. In order that I can validate the signature with the message I would like to receive the complete SOAP envelope as (XML) message (<envelope>...<soap-env:header>...</soap-env:header>...<soap-env:body></soap-env:body></envelope>).
I couldn't find a solution for this.
Currently I use the WCF-Custom adapter to receive the multi part message (xml schemas created with svcutil) and receive the body as XML file. I also know how to access the SOAP header in the message but I would like to know if its possible to receive the
complete envelope as message.
Best regards
Jerome

Orchestration subscription includes value for BTS.MessageType context property, this mean you can't start orchestration with the soap envelope message type because the XmlDisassembler Component will discard the soap:Envelope content and the messaging engine
will only get the soap:Body content – so at the end of the process, BTS.MessageType context property will be set to the actual message type of content under soap:Body section and the orchestration will never start with the type soap:Envelope.
In case you need to process the entire soap:Envelope inside orchestration:
Use PassThruReceive pipeline.
Define message of type BTS.soap_envelope_1__1 message inside the orchestration (Message Type > schemas > from referenced assembly > Microsoft.BizTalk.GlobalPropertySchemas).
Use Xml Document as the incoming message.
Assign the incoming Xml Document message to the BTS.soap_envelope_1__1 message.
Reference :
http://pinhask.blogspot.in/2008/06/processing-soap-envelope-within-biztalk.html
Thanks
Abhishek

PI 7.11 - Sync HTTP receiver adapter with response XML file

Hi
We have a File to HTTP scenario in which we need a sync HTTP interface. We send a file to the HTTP address and receive a XML acknowledge. As I read in this forum: sync HTTP interfaces are not possible with the "standard" HTTP adapter. So I found an entry which recommended to use the SOAP adapter instead.
I configured it:
- Do Not Use SOAP envelope
- modules: RequestResponseBeans, CallSapAdapter, ResponseOneWayBean
If i use this scenario, i get following error in the RWB - Message Display Tool:
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException: while trying to invoke the method com.sap.engine.interfaces.messaging.api.Message.getMessageId() of an object loaded from local variable 'message1'.
I testet this scenario using CURL and it worked properly. Should this kind of scenario work with the SOAP adapter or do I need to buy/develop an own adapter? Is in NW7.3 possible to configure sync HTTP scenarios?
Thanks in advance
Michael

Hi
actually i use a simple HTTP receiver CC with the setting "XI Payload in HTTP Body" to send a XML datafile to a webpage (java servlet). This part works fine by now. But, this servlet would also send back a status information to the state of the received datafile, which I like to catch.
e.g. HTTP response from the servlet (catched using CURL):
HTTP/1.0 403 Forbidden
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548)/Tomcat-5.5
Set-Cookie: JSESSIONID=OALHMomjR9TVgIATi8SrPQ**.ajp13_ls_1; Path=/ls
Content-Type: text/xml
Date: Tue, 06 Mar 2012 16:19:56 GMT
X-Cache: MISS from proxy.xxxx.com
Via: 1.0 proxy.xxxx.com:xxxx (http_scan/4.0.2.6.19)
Proxy-Connection: close
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><!DOCTYPE transportordersfromls [ <!ELEMENT transportordersfromls (userid, clntid, msgid, (transportorderfromls+ | error))> <!ATTLIST transportordersfromls vers CDATA #REQUIRED> <!ELEMENT userid (#PCDATA)> <!ELEMENT clntid (#PCDATA)> <!ELEMENT msgid (#PCDATA)> <!ELEMENT transportorderfromls (refid, status)> <!ELEMENT refid (#PCDATA)> <!ELEMENT status (ok | error+)> <!ELEMENT ok EMPTY> <!ELEMENT error EMPTY> <!ATTLIST error reason (XMLError | SystemNotAvailable | ApplicationError | OTHER) #REQUIRED message CDATA #REQUIRED> ]>
<transportordersfromls vers="1.0">
    <userid/>
    <clntid>XXXXX</clntid>
    <msgid>0</msgid>
    <error reason="OTHER" message="Access denied"/>
</transportordersfromls>
Michael

HTTP Receiver interface returns with error code 110

Hi All,
We are posting the document from XI to a external server as HTTPS request.
We are able to sucessfully post the request to external server using HTTP destination as address type but not able to post sucessfully with URL as address type.
Here goes the details -
We are able to post the HTTPS request successfully on the external server using the HTTP destination as address type in HTTP receiver adapter setup.
When we setup address type as HTTP destination , we need to provide the following details -
IN SM59 , Connection type G
Target Host : host name ( with out "https://" as prefix)
Service No : 443
Path prefix : query string
SSL : Active
Certificate : Select the certifacte from the client certificate list.
We can post the request to external server using URL as address type in HTTP receiver adapter setup.
When we setup address type as URL , we need to provide the following details -
Address type : URL Address
Target Host : host name ( with out "https://" as prefix)
Service Number : 443 ( HTTPS port setup on XI)
Path : query string.
When we post the same request as we did with HTTP destination as Address type , we are getting a HTTP response code as failure HTTP response code 110
Please find the details about the return code -
If a cache returns a stale response, either because of a max-stale directive on a request, or because the cache is configured to override the expiration time of a response, the cache MUST attach a Warning header to the stale response, using Warning 110 (Response is stale).
110 Response is stale
MUST be included whenever the returned response is stale.
Please find the error message from SXMB_MONI
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please let me know if some one has faced this issue.
Regards,
Reddy
Edited by: Nanda kishore Reddy Narapu Reddy on Mar 11, 2008 12:35 PM

Hi All,
Is some one can confirm that - We can use HTTPS with Address type as URL address in HTTP receiver adapter setup.
I can confirm that using HTTP destination as Address type in HTTP receiver adapter setup we can attain HTTPS communication with external server.
If some one who has tried HTTPS communication using HTTP receiver adapter using URL address as Address type can guide me what are the steps need to be done.
Address type is a parameter in HTTP adapter setup .
Regards,
Reddy

HTTP Receiver Adapter

Hi,
I am working on a scenario, where I am posting xml message on https url, for which I am using HTTP receiver adapter.
I have created RFC destination of type 'G' in sm59 to make an https call, where I have provided following details:
In Technical Settings:
Target Host - <Hostname>
Service No. - 443
Path Prefix - <url path>
Logon Security:
SSL - Active
SSL Client Certificate - Default SSL Client (Standard)
UserName - <Username>
Password - <Password>
I have used this RFC destination in 'HTTP Destination' of HTTP receiver adapter.
When I test this interface, I am getting this error.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client. Code 110 reason</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Can you please help me resolve this issue. Please let me know, if I am following the right steps.
Thanks in advance
Regards,
Amit

Hi -
Since you're using the http destination option in the channel, you just specify the user/pwd in the destination.
Regarding the issue, first, for the Logon/Security option in the destination, unless you'll be using a client certificate to authenticate, you should choose option ANONYM SSL Client (Anonymous) - you still provide the user/pwd in the Logon section. Make sure you have imported the root cert of the CA verifying the server's identity into the client certificate list within STRUST (node SSL Client (Anonymous)).
Also, for some hints on the issue, look at the ICM trace - tcode SMICM->Goto->Trace File... you may need to increase the trace level - SMICM->Goto->Trace Level... After resolving the issue, make sure to set the trace level back to default.
Regards,
Jin

ICM_HTTP_TIMEOUT error in HTTP Receiver adapter

Hi
I am doing HTTP Receiver adapter and File Sender adapter for my scenario.
I am getting the following error in SXMB_MONI.
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>402</SAP:P1>
<SAP:P2>ICM_HTTP_TIMEOUT</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client. Code 402 reason ICM_HTTP_TIMEOUT</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error
Help needed,

Hi Ganesh,
Check this weblog...
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Check this thread with similar issue...
ICM_HTTP_TIMEOUT
Regards,
Sridhar

Service Number/Port Number in HTTP receiver adapter

Dear Experts,
I have a scenario where I am to do HTTP Post to a 3rd party web application via a url in the following format:
https://x.y.info/abc/sap/customer.cgi
The HTTP Post data is submitted to the CGI script which is then processed further by the web application. The URL works ok via IE or even PI soap receiver adapter is able to post XML message to the URL but using SOAP.
But I have to do only HTTP Post and now my problem is that the URL dont have a so called port number that I can fill in the "Service Number" field in HTTP receiver channel or in SM59.
Does SAP always need a service number or how to deal with this case where server doesnot expose the port.
Thanks in advance.
Br
Suman

Hello,
The HTTP Post data is submitted to the CGI script which is then processed further by the web application. The URL works ok via IE or even PI soap receiver adapter is able to post XML message to the URL but using SOAP.
By definition, the SOAP Adapter is also using HTTP POST as its HTTP method the only difference is that there is a SOAP Envelope that is being sent.
But I have to do only HTTP Post and now my problem is that the URL dont have a so called port number that I can fill in the "Service Number" field in HTTP receiver channel or in SM59.
Service number is the port number of the URL that you will be connecting to, if it is not shown, it is assumed that it is 80 for http and 443 for https (as Gzegorz mentioned). Since you are using HTTPs, you should use HTTP Destination that points to an SM59 configuration.
Hope this helps,
Mark

Queue error in HTTP receiver

I have a HTTPS receiver set up to send a file to the targer HTTP URL (external), file has been picked up but it's in queue with SYSFAIL status and message
XI Error ATTRIBUTE_CLIENT.PLAINHTTP_ADAPTER: Queue
Do I need to create a service in SICF for the web address?
Thanks,
Menaga

Hi, tahnks every one for your answers but I am still not able to get to it.
Checked with the customer and they didn't receive it, the same works with webmethods fine. I changed the communication channel with RFC destination type G instead providing the URL direct. I am gettign the below error.
Do I need any thing specific for HTTPS communicaiton in PI or doest the HTTP adapter handles HTTPS? I think receiver doesnt want a soap envelope. I am sending a text file which has ras edi data and that's what the receiver needs.
xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>USBANK</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while creating the HTTP client with destination USBANK</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Menaga

Why is this differenceSOAP-ENV:Envelope soapenv:Envelope

Hello i am creating soap message with Axis 1.3 my soap message structure is like this <soapenv:Envelope but i need this structure <SOAP-ENV:Envelope Kindly help..
Why is this difference

Read here:
http://alliosnews.com/2014/09/email-handoff-ios-8/

HTTP RECEIVER QUERY

hello everyone,
I have to develop a synchronous scenario, SOAP Sender to HTTP Receiver.
Soap sender will be passing suppose 2 fields Name and Employeeid and the Http receiver will be replying back the
response with entire employee details (name, id, address, dateofbirth, etc).
Http receiver has to be accessed via a URL like
https://abc.com/test/servlet/ServletInterface?command=getdetails&emp_name=<Name>&emp_id=<Employeeid>
This is an https request, henc an RFC destination needs to be configured in XI and SSL has to be activated but how will i add the parameters Name and Employeeid to the URL mentioned in the RFC destination.
i went through many blogs on SDN, but i could not figure out how to append the URL mentioned in the Http Destination. Is it possible to do dynamic configuration with SSL enabled.
i tried passing URL https://abc.com/test/servlet/ServletInterface?command=getdetails in the HttpDestination and also configured a mapping for dynamic configuration but with no success.
please let me know if i am on the right track. if not please suggest.
thanks in advance.
Edited by: praveen kalwa on Feb 22, 2008 1:33 PM

Hi,
XI supports only PUT method of http request. While adding parameters to the addr string is considered as a GET method.
Refer following blog in this regard.
/people/amol.joshi2/blog/2006/06/28/must-fire-a-http-get-from-xi---try-this
-Kavita

Https for SOAP and HTTP Receiver adapters in PI 7.1

Hi,
We need HTTPS Transport protocol is required to send the message to receiver systems.
Currently we are using below procedures for https:
1) HTTP with SSL (= HTTPS) without client authentication
2) HTTP with SSL (= HTTPS) with client authentication
But client donu2019t want this procedure.
Here my question is How to enable the https Transport protocol in SOAP and HTTP Receiver adapters.

>>Here my question is How to enable the https Transport protocol in SOAP and HTTP Receiver adapters.
What I see is your client wants PI to send communication via HTTPS transport protocol. That means you have to apply for trusted certificate and import that certificate root node in Netweaver keystore.
Then change the transport protocol from http to https in soap and http receiver communication channel and communicate to client via certificate authentication.
Plenty of documents available in sdn about https certificate authentication. Please go through those links.
check this thread.. might be helpful
Client Certificate for PI authentication when Web Dispatcher terminates SSL

HTTP Receiver Adapter payload as single line plain text with out any tags.

Hi PI experts,
I have a strange problem in http receiver adapter.
Sender RFC (SAP) Receiver: HTTP.
Receiver system expects the output from XI in the below format in a single line plain text with out any tags in the payload. and the content type should be application/x-www-form-urlencoded
Group=Test&Sentinel=Web%20Server&Facility=5345&Order Number=XT-XWHM-Y-NA&Serial Number=123456&@LABEL_QUANTITY=5&@LABEL_NAME=111114_Q
Is there any way to achieve this using http receiver adapter. Business is not ready to accept the output from XI not even in a single element instead they only need it as a JUST a plain text.
Appreciate early response on this.
Thanks in Advance,
Jitender

Dear Ola,
Could you elaborate how you achieved in catching the response data from the receiver in case of HTTP receiver adapter?
The target service is not a WebService but some python script that must to receive some paramters via POST request.
HOW can I post this parameters?
Here you entered the fields of the message type of the request in the header parameters of the receiver adapter? Thats fine.
But what about the message type and vice versa of the response from the receiver?
Regards
Rebecca

HTTP RECEIVER Stopping on CALL ADAPTER

Hi All,
I'm having a problem with HTTP Receiver adapter, It's an IDOC that need to send to a HTTP Listener. Everything works until send the XML to the http listener, I have made a single listener in java to verify how this XML is coming from adapter.
I got the follow information:
POST /?msgguid=45ECD392770B0046020000000AA00D4B&service=MYSERVICE&namespace=urn%3amynamespace%3atest%3aintegration&interface=MI_ED_MYIDOC_IB&qos=EO HTTP/1.0
content-type: text/xml
content-length: 1550
connection: close
accept: */*
user-agent: SAP Web Application Server (1.0;640)
host: 10.10.10.10:5556
accept-encoding: gzip
<?xml version="1.0" encoding="UTF-8"?>
It stops on first line of XML <b><?xml version="1.0" encoding="UTF-8"?></b> and stay stoped until I break the connection.
The server is SAP XI 3.0 SP15.

Hi Renjith, yes it's a custom java program and I'm trying to write on the console the stream on the console.
What I need to do is certify if SAP XI is delivering the message to the legacy system. So, I know that all configuration on scenario for integration between this legacy system and SAP R/3 is correct. And I'm almost sure that error is on the legacy system side that I don't have credentials to verify.
Look at the source code below:
import java.io.*;
import java.net.*;
class SocketServer {
   ServerSocket server = null;
   Socket client = null;
   BufferedReader in = null;
   PrintWriter out = null;
   String line;
   SocketServer(){ //Begin Constructor
     this.listenSocket();
   } //End Constructor
public void listenSocket(){
    try{
      server = new ServerSocket(5556);
    } catch (IOException e) {
      System.out.println("Could not listen on port 5556");
      System.exit(-1);
    try{
      client = server.accept();
    } catch (IOException e) {
      System.out.println("Accept failed: 5556");
      System.exit(-1);
    try{
      in = new BufferedReader(new InputStreamReader(client.getInputStream()));
      out = new PrintWriter(client.getOutputStream(), true);
    } catch (IOException e) {
      System.out.println("Accept failed: 5556");
      System.exit(-1);
    try{
      int i = 0;
      while((line = in.readLine()) != null){
        line = in.readLine();
     System.out.println(i+":"+line);
        i++;
      //this.finalize();
    } catch (IOException e) {
      System.out.println("Read failed");
      System.exit(-1);
protected void finalize(){
//Clean up
     try{
        in.close();
        out.close();
        server.close();
    } catch (IOException e) {
        System.out.println("Could not close.");
        System.exit(-1);
public static void main(String[] args){
        SocketServer frame = new SocketServer();
Thanks,
Daniel

RFC TO HTTP receiver scenario.Adding file name to HTTP receiver

Hi All,
Scenario is ZBAPI ->XI-> HTTP conncetivity to EXternal Partners .
ZBAPI sends the Partner data informtaion to XI . I need to create a Partnerdata xml in XI and pass it to HTTP Connectivity (Certificates ) to External Partners
Connectivity is working but I need to add the time stamp to the Partner data xml in the HTTP Receiver .
I dont get the time stamp in ZBAPI
I checked many blogs to create UDF of getfilename, dynamic configuration , but here there is no FTP sender channel .
Can someone help me in giving ideas as hope to assign the time stamp in runtime to HTTPS Receiver Channel .
Thank you ,
Best Regards,
Vara

Hi Vara,
In your question you actually mentioned three different communication methods (HTTP, HTTPS and FTP), but only one of them can really work with files and it is the FTP adapter. Moreover, what you need is the Receiver FTP Communication Channel, not the Sender one (as you need to deliver your message to an external system, not to collect it from there). What you need to do is find your Receiver Communication Channel, go to Advanced tab and mark "Use Adapter-Specific Message Attributes", as well as the File Name (that appears once you mark the first one). Then, in your message mapping, you just put the current timestamp to the respective dynamic configuration parameter. Find an example of how to make the whole change [here|http://www.****************/Tips/XI/ASMA/Index.htm].
However, if I misunderstood you and you need to use the current timestamp in the message body instead of the file name, it will be even simpler. In this case, just go to your Message Mapping and in the target field, put the "currentDate" function from the "Date" group, then double click on it, click the "extended view" button and put your expected date and time format.
Hope this helps,
Grzegorz

HTTP Receiver - need ENV:Envelope TransactionID......

Similar Messages

Maybe you are looking for