SOAP RECEIVER SCENARIO PORT ISSUE

Hi gurus,
we are testing a proxy to soap synchron scenario and cannot get response from receiver. We have a firewall issue and need to open required ports.
Which ports should we open? 50000? 80?
Kind Regards,
PM

Hi Peter,
SOAP communication uses HTTP protocol, so messages are transferred over 80 or 443 port by default, depending on whether you use HTTP or HTTPS communication, correspondingly.
Hope this helps,
Greg

Similar Messages

Connection closed by remote host on SOAP Receiver Scenario

Hi Experts,
I implemented a RFC to SOAP Receiver scenario, consuming an external
Web Service with SSL security, using SAP PI 7.1. I configured the SOAP
Receiver Adapter with Proxy e Proxy User, and it shows the
message u201CConnection closed by remote hostu201D. I have checked with
Network team, about the firewall restrictions, and they told me it was
pass by firewall. I installed the SOAP UI on the PI DEV Server to test
the SOAP Requets and it worked. Only on the PI it shows this error
message. I traced log at SLL service in the Sap Netweaver Administrator
and I didnu2019t get success.
Long text error:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
java.io.EOFException: Connection closed by remote
Please, could you help me about this error?
Fábio Ferri

Hi Fabio,
You need to set higher trace level in order to get more information in your trace file.
If you think it is related to security then set logging level of components com.sap.aii.security.lib and com.sap.aii.af.security to DEBUG in Visual Admin's log configurator. Also set com.sap.aii.af.mp.soap and com.sap.aii.messaging to DEBUG level.
And then try sending messages and see whether you have received more informaiton in trace file, but don't forget to revert back the change once you finish testing otherwise it will filled up your diskspace.
Best regards,
Pinkle

Differentiating Soap receiver scenarios

Hi,
I need to test a webservice scenario(PI consuming a webservice). We dont have the test environment set up for webservice providing system.
I have configured everything in PI, i have the endpoint URL but no valid hostname.
So my question is:
1) if i shoot a request with an arbitrary host name in the URL in Soap receiver channel; Will PI consider that the end system is down and how will it behave?
2) Is there any difference between giving an arbitrary host name and giving a valid hostname which is actually down. how does pi behave in both of these cases?.
3) I believe the time out value which we provide in receiver channel(XMBWS.Timeout) works only when the request has successfully reached the end system and the end system is taking time to respond. If the end system is down then this parameter doesnot make any difference, the time out considered will be the one which we set in NWA - xiadapter.inbound.timeout.default. Is my understanding correct?
Regards
Shailesh

1) if i shoot a request with an arbitrary host name in the URL in Soap receiver channel; Will PI consider that the end system is down and how will it behave
everything will go fine till SOAP receiver channel.....then in RWB the channel will report an error saying receiver not found (or similar)
2) Is there any difference between giving an arbitrary host name and giving a valid hostname which is actually down. how
does pi behave in both of these cases?.
Valid URL --> message transferred to the receiver without error
Invalid URL --> message does not leave XI/ PI and marked as an error in AE.

SOAP receiver adapter configuration issue

Hi Everyone,
When I am trying to excute a sync scenario from SAP<>XI<>Webservice from Integration engine , I am getting the below error message.
Error while sending message: com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.
In the receiver SOAP adapter, I have configured Transformation module where I kept the MessageTransformationBean in processing sequence as a priority and also provided the module configuration.
ModuleKey: transform
ParameterName: Transform.ContentType
Parameter Value: application/soap+xml;charset=utf-8.
But still get the above error message in the communication channel. I am using certificates in my configuration that were deployed in visual Admin.
In the adapter configuration, I have just provided the Target URL, Configured User Authentication, certificate authentication and SOAP action.
Can anyone help me.. how to rectify the issue.....
Thanks in advance,
Hareen

HI Hareen,
I decided to give SOAP1.2 using the standard SOAP Adapter a try
There are a few noticeable differences between the request message of SOAP1.1 and SOAP1.2
1.) SOAP 1.1 uses a different namespace from SOAP 1.2. For SOAP 1.1 it is "http://schemas.xmlsoap.org/soap/envelope/" while for SOAP 1.2 it is "http://www.w3.org/2003/05/soap-envelope".
2.) SOAP 1.2 does not use SOAPAction in its header.
3.) Content type is also different, for SOAP 1.1 it is "text/xml" while for SOAP 1.2 it is "application/soap+xml"
So a sample request for SOAP 1.1 would be like this:
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://sampleaction"
While for 1.2 it is:
Content-Type: application/soap+xml;charset=UTF-8;action="http://sampleaction"
The SOAP action is moved to the content type (experts please correct me on this).
Based on the differences, you need:
1.) Construct the correct SOAP Envelope for request message mapping and remove it for the response mapping
2.) Use MessageTransformBean to change content type
3.) Leave SOAPAction as blank
I think dynamic soap action is no longer possible because the action is hardcoded in the module configuration (please correct).
Hope this helps,
Mark

SOAP Receiver Adapter Certificate issue

Hello Gurus,
i m working on RFC to SOAP scenario on SAP PI 7.3 and need help about SSL credentials.
We have been testet with SOAP UI Tool successfully (without Certifcates). Why not with PI?
Now we are facing an issue like
"iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier".
What should we do to solve this issue?
Target SOAP Url; https://www.xxx.com/PartnerCard/Partner.asmx
Kind Regards,
PM

Hi,
One more thing to check: while testing the connection from SOAP UI, did you use the same URL with https? Because, for instance for the web services generated in PI, you get two separate bindings: for http and https connections. So if using the secure https channel is not your requirement, you could just use the http binding from PI in your scenario.
Hope this helps,
Greg

Syncronous SOAP Receiver Message: APPLICATION_ERROR

Hi Experts,
I am facing a application error in SXMB_MONI for syncronous messages in a SOAP receiver scenario.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In RWB the SOAP adapter shows me that the message was delivery successfully however the guys from the third party application said to me that the message didn't reach it.
I would like to know if you have any idea where the error is.
Have you already faced something like this?
<< Moderator message - Please do not offer points >>
Thanks in advance,
Daniela
Edited by: Rob Burbank on Oct 15, 2010 4:42 PM

Hello,
Based on the exception, this is really not as descriptive as possible. Can you try the following:
1. Execute the WSDL via SOAP UI and let us know of the results.
2. Under SXI_MONITOR, can you double click the response message payload? The response message payload should more or less give an idea as to why this error occurred.
Hope this helps,

Getting error in SOAP receiver in RWB

Hi Experts,
we have some problem in soap receiver.
scenario name is PROXY TO SOAP.
firewall is open already
WEB service team not able to get the message from PI. wHEN WE MONITOR Receiver soap communication channel we are getting the below error.
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: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The message with Action '' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None)..
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The message with Action ' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).
when we load the receiver url(webservice url) we are getting the the xml message.
please help us.
thanks
Elton
Edited by: eltonsaranya on Feb 23, 2012 12:47 PM

Hi Elton,
Most probably you need to type the SOAP Action in the receiver Communication Channel. You can find it in the .wsdl file for your scenario in the following tag:
<wsdl:operation name="SaveShipment">
<wsdl:input wsdl:Action="http://namespace.com/Integration/SomeAction" name="SomeAction"/>
</wsdl:operation>
In this case, you would use the following SOAP Action in your receiver channel: http://namespace.com/Integration/SomeAction.
Hope this helps,
Greg

Handling SOAP HEADER using SOAP Receiver Adapter

Hi Experts,
I need to implement SOAP Receiver Scenario and passing ( Header fields User, Password and token) I have seen a lot of scenario using a XSLT Mapping, to handling the SOAP Header. So need to help to understand some details:
Suppose I need to implement the SOAP Header below? In this case I need add only the fields u201CUsername, Password and AuthenticationTokenu201D. I created the XSLT Transform, the source XML? Where I put it? Or can create it into Message Interface?
Is it possible to do this in Java Mapping?
Thanks!
Best Regards
Fábio Ferri
<soap:Header>
      <v1:ExecutionHintHeader>
         <v1:Name></v1:Name>
         <!Optional:>
         <v1:Arguments>
            <!1 or more repetitions:>
            <v1:Argument Name="?" Value="?"/>
         </v1:Arguments>
      </v1:ExecutionHintHeader>
      <v1:CredentialsHeader>
         <!Optional:>
         <v1:Username>pi</v1:Username>
         <!Optional:>
         <v1:Password>jhjhjjhjhjius</v1:Password>
         <!Optional:>
         <v1:AuthenticationToken></v1:AuthenticationToken>
      </v1:CredentialsHeader>
   </soap:Header>

You need to put XSLT mapping in 2° step mapping in request.
SourceMessageRequest -> Message Mapping -> XSLT Mapping -> DestinationMessageRequest
If you test mapping program, this should be working fine.
In adapter module, put localejbs/AF_Modules/MessageTransformBean with parameter value text/xml; charset=utf-8 and correctly set Conversion Parameter "Do not use Soap Envelop"
XSLT Request Mapping
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header>
<ServiceAuthHeader xmlns="http://WIND.WEBSERVICES.DMS/">
<Username>USER</Username>
<Password>PASSWORD</Password>
</ServiceAuthHeader>
</soap:Header>
<soap:Body>
<xsl:copy-of select="*"/>
</soap:Body></soap:Envelope>
</xsl:template>
</xsl:stylesheet>

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

Issue in Dynamic configuration in SOAP receiver channel

Hi All,
My scenario is file to SOAP. At receiver side I want to generate URL dynamically.
To proceed step by step, I started with passing a constant URL to Dynamic configuration UDF.
mapping:
Dynamic conf. UDF
Channel Configuration:
From testing, I found that channel always takes the url given in Target URL field and dynamic URL in TserverLocation is been ignored by the channel.
That is dynamic configuration is not working completely.
I went through a lot of blogs and also tried a lot of trial and error methods, but none helped. Every thing I configured looks perfect for me, but still not working. I don't understand where I went wrong. Please help me.

Hi Experts,
I am facing similar issue,
URL --> UDF --> @dynamicvariable
I have created a variable underparent node eg: DESADV-->dynamicvariable
passed complete URL to UDF, below is the UDF
& configured SOAP Receiver Channel as well. This is IDOC to IDOC scenario, using IDOC_AAE on sender side and SOAP on receiver in single stack.
--> Checked ASMA
--> Checked Variable Transport Binding and given "TServerLocation" without quotes in XHeaderName1
--> Target URL: http://
But when I am running this interface, nothing is coming in Dynamic configuration.
Ref: Message Log:
MM and OM is also perfect in ESR.
Any suggestions? Please advice.
Regards
Singh

Issue with SOAP receiver

Hi,
I'm using PI 7.0, SP13 and I'm sending a message to a MS webservice, using BURP as a proxy in between to avoid NTLM authorisation issues.
The problem is that it's perfecly possible to send a message using soapUI, but sending the exact same message ends up in an error:
"SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request"
I already configured the MessageTransformBean by setting the ContentType to text/xml; charset=utf-8. Here are the settings of my communication channel:
Target URL: http://<correct URL on local network>
User authentication: false
Certificate authentication: false
Proxy: BURP proxy and BURP port
Proxy user authentication: false
Secutiry profile: false
Do not use SOAP envelope: false
Keep headers: false
Keep attachments: false
Use encoded headers: false
Use query string: false
SOAP action: <correct SOAP action>
I also played with the parameters "Do not use SOAP envelope", "Keep headers" and "Keep attachments", without any success. The only difference that I can think of is that soapUI runs on Windows, and the PI system runs on Linux.
Ideas, anyone?

@Baskar Gopal: I didn't generate a WSDL: I'm using the SOAP receiver to post a message to an existing webservice.
@sdnuser: the endpoint URL is 100% correct. I also added the MessageTransformBean like I stated before.
@Chirumamilla Sukarna: HTTP adapter doesn't work because I need the SOAP envelope.
The payload is in both cases (soapUI and PI) the same. Here's the part that's different:
soapUI (working part):
POST /DynamicsNAV/WS/Rendon%20Voorburg/Codeunit/Webservice HTTP/1.0
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "urn:microsoft-dynamics-schemas/codeunit/Webservice:ContractorOrderInSync"
User-Agent: Jakarta Commons-HttpClient/3.1
Host: 192.168.1.8:7049
Proxy-Connection: Keep-Alive
Content-Length: 4292
Connection: Keep-Alive
SAP PI (not working part):
POST /DynamicsNAV/WS/Rendon%20Voorburg/Codeunit/Webservice HTTP/1.0
Accept: /
Host: 192.168.1.8:7049
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Authorization: Basic aGFhZ3dvbmVuQGJpbTpRYnFyRU84IQ==
content-id: <soap-C89FD74E68782E13E1000000C0A8E010 @ sap.com>
Content-Type: text/xml;charset=UTF-8
Content-Length: 4292
SOAPACTION: "urn:microsoft-dynamics-schemas/codeunit/Webservice:ContractorOrderInSync"
Connection: Keep-Alive
I know the content type looks correct here, but the SOAP adapter gives an error about this nevertheless.

SOAP receiver starting the integration scenario

Hello experts,
I am searching for a way to start an integration scenario with a SOAP receiver in the same way it is possible with JDBC sender (with a pool interval).
The scenario is: I need to execute a webservice, getting information from it, and send this information to an abap proxy on ECC side.
I thought about creating a ccBPM with a loop (with no end) and a wait step for doing it... although it works, I think it is not the best way for doing it.
Thanks for your suggestions!
regards.
Roberti

Thank you guys.
Let me explain the scenario in a better way.
The scenario is:
1 - Automatically execute a partner webservice sync call with constant parameters.
2 - Get the webservice response.
3 - Map the response to get required information.
4 - Send this information to an Abap proxy.
5 - Process the information to proper abap objects.
Note: This scenario needs to be automatically executed every 30 minutes.
The purpose of this scenario is to GET documents (xml) from a partner web service and import the information to ECC, continuously, each 30 minutes. So, no one is supposed to start the process, it should be automatically triggered. The goal is exactly the same we have with JDBC or file sender adapter, where we can set a 30 minutes interval to automatically execute an sql statement in the database or read a file in a path.
JAVAGUY and Stefan Grube, I did it in this way. But, scheduling an Abap job to start the proxy -> webservice -> proxy scenario, the Abap job is the RESPONSIBLE for the scenario. If something wrong occurs with that job schedule, the integration will stop working. I would prefer PI as responsible for the process, so I can have alerts and other execution guarantees.
Abhishek Salvi and Pratik_du, I think that the scenario is clear now, don't it? About the ccBPM, this is another way I implemented the solution. I created a ccBPM with
1 - A receiver that I execute just once
2 - One loop with a condition 1 = 1 (infinite)
2a (Into the loop) - A send step to execute the webservice sync call
2b (Into the loop) - A receiver step to get the webservice response
2c (Into the loop) - A map step to transform the information I need
2d (Into the loop) - A send step to send the information to the Abap proxy
2e (Into the loop) - A wait step to wait 30 minutes until execute the next step of the loop
IIn this case, I will have a ccBPM running continuously and doing the job.
I posted the question because I'm not sure which solution is better, and check if you can see another way to make PI the responsible for starting a scenario with a soap receiver like this.
Thank you again.
Roberti

Issue while passing Target URL dynamically in SOAP Receiver Adapter

Experts,
I am stuck with an issue while passing the Target URL dynamically.
The UDF required for this works just fine. I can see the Target URL in Dynamic Configuration header(The Key is TServerLocation) in SXMB_MONI but the request that I am sending is not reaching the web service.
Some posts have suggested to hard code the Target URL as http://.
Below is the error that I am getting when I hard the Target URL as http://:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>RecoverableException</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:453)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:834)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
When I hard code the Target URL as Test (any dummy value), the error that I get is different. (Detailed error shown below)
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>RecoverableException</code>
               <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: no scheme
     at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:453)
     at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:131)
     at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:834)
     at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</text>
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
I've referred the post [Dynamic URL for SOAP receiver adapter;.
I am on PI 7.0.
Any help in this regard is highly appreciated.
Best Regards,
Vijay

Issue resolved... by doing this:
DynamicConfigurationKey key2 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "TAuthKey");
conf.put (key2, "username");
In the advanced tab of the communication channel, set the flag "View Authorization keys", and then added "username" (user to access the dynamic target url) and the password (2 times).
That's it...

SOAP Receiver Adapter / Scenario calling WebServices

Hi Experts,
I am trying to call a web service. Configured a SOAP Receiver adapter. Message to Web Service goes fine but not shown with Checkered flag, but with icon with description "Log Version".
In response message for the request Error Category - MAPPING and Error ID "Cannot Read Payload".
Any ideas to clear this problem. I do have response mapping assigned to Message Interface. Message Interface is Synchronous.
Thanks in advance for any solutions.

can you verify that you are getting a response..try re-routing that to tcpgw and check if content is in line with expected response.
Regards
Ravi Raman

SOAP Receiver Adapter issue

Hello there,
I am using a SOAP receiver adapter. The URL contains the format - https://<XYZ.com>/car/soap/Sync?login=username&pass=password
Now, if I configure the channel by using the "Configure User Authentication", the data is not getting posted at target.
But if I provide the user id / pwd in the URL, it gets posted.
I don't want to use the user id / pwd in the URL but at the sametime, the WS team is not ready to change the format of the URL.
Can I use "Query String" to handle that? If yes, how? If no, what options I have?
Thanks for your precious input and time.
Abhi

Thanks Suraj!
Have you tried this:
url : https://<XYZ.com>/car/soap/Sync
and Configure User Authentication option set
I haven't tried it that way. I am not sure whether that will work, as WS team told me that I am required to put in the whole URL. But thanks for your suggestion, I will give it a try that way.
also try specifying the SOAP action as per your wsdl file
SOAP Action is not Mandatory, so I am not using that.
Thanks,
Abhi

SOAP RECEIVER SCENARIO PORT ISSUE

Similar Messages

Maybe you are looking for