Use of SOAP adapter in PI7.11 - migration from PI7.0

Hello everybody,
We are migrating from PI7.0 to PI7.11.
we have a scenario RFC => PI => SOAP
in PI 7.0 that work perfectly for 2 years
in PI 7.11 that doesn'"t work. That gives the error message "com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.EOFException: Connection closed by remote host" .
the SOAP is under https with a certifcate X509 imported by visual admin for PI7.0 and imported by NWA in 7.11.
The output message from the 2 environments are the same.
I intercept them in clear format ( non crypted) thru a gateway except for the PI 7.11 there is a line more before the soap envelop. (CallingType: SJM).
The certificates are places in TrustedCAs for the 2 environments
In log there is the message:
#2.0 #2010 03 01 09:56:10:788#+0100#Error#com.sap.aii.af.sdk.xi.net.HTTPClientConnection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#0026B9737AE51CA50000000100001090#5022851000000004#sap.com/com.sap.aii.adapter.soap.app#com.sap.aii.af.sdk.xi.net.HTTPClientConnection.getInputStream(Socket)#J2EE_GUEST#0##4EEA9DA0250F11DFBBEC0026B9737AE5#4eea9da0250f11dfbbec0026b9737ae5#4eea9da0250f11dfbbec0026b9737ae5#0#XI SOAP[rcv_SOAP_Login/SV_TME/*]_16058#Plain##
failed to get the input stream from socket: java.io.EOFException: Connection closed by remote host.#
#2.0 #2010 03 01 09:56:10:788#+0100#Error#com.sap.aii.af.sdk.xi.net.HTTPClientConnection#
#BC-XI-CON-AFW#com.sap.aii.af.lib#0026B9737AE51CA50000000300001090#5022851000000004#sap.com/com.sap.aii.adapter.soap.app#com.sap.aii.af.sdk.xi.net.HTTPClientConnection.call(Object)#J2EE_GUEST#0##4EEA9DA0250F11DFBBEC0026B9737AE5#4eea9da0250f11dfbbec0026b9737ae5#4eea9da0250f11dfbbec0026b9737ae5#0#XI SOAP[rcv_SOAP_Login/SV_TME/*]_16058#Plain##
additional info ssl_debug(6): Starting handshake (iSaSiLk 4.1)...
ssl_debug(6): Sending v3 client_hello message, requesting version 3.2...
ssl_debug(6): IOException while handshaking: Connection closed by remote host.
ssl_debug(6): Sending alert: Alert Fatal: handshake failure
ssl_debug(6): Shutting down SSL layer...
PI7.0 is installed on windeows server 2003 32 bits
PI 7.11 is installed on windows server 2008 64 bits
Is there someone who can help me ?
Thanks in advance.
E. Koralewski.
Edited by: Eric Koralewski on Mar 1, 2010 12:04 PM
Edited by: Eric Koralewski on Mar 1, 2010 12:04 PM

Hi Christain,
Thanks for the information
I received a new version of that certificate to be sure that was not a problem of version .
I imported it in old system ( version 7.0 ) in a new keystore , I did the same thing on the new system ( PI 7.11).
The scenario works in the old system with that keystore and not in the new system (7.11).
The only one log I found is the log which is in the begining of my post.
Kind Regards

Similar Messages

Principal Propagation Using Sender SOAP adapter in PI7.1

Hi,
I am trying to configure principal propagation using SOAP sender adapter. In that, I am trying to generate the assertion ticket in SAP only but it is using PIAFUSER as the user that is being passed and not the user which we are using to logon.
Please tell me how an assertion ticket can be generated in this case , and the User that is being used for logging on is propagated. Is there any other way in which SOAP adapter can be used to propagate principally.

Hi,
Have you come across this link?
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce95b718d3424be10000000a421937/content.htm
Regards,
Ravi

ABAP Proxy without SOAP adapter in PI7.3

Hi All,
We have dual stack implementation of PI7.3 but we do not wish to use the SOAP adapter for configuring an ABAP proxy scenario.
Is this possible? Is the Javastack only configuration in NW Admin available for use in dual stack implementation also?
Thanks and Regards,
Diptee

Hi All,
So it essetially means that only the below 2 options are available for ABAP proxy scenarios in PI7.3 for a ABAP+Javastack installation
- use of SOAP adapter over XI protocol
- use of conventional proxy configuration of the ABAP Integration Server
And the only Javastack config cannot be used for a dual stack implementation.
Please confirm if above is correct.
Regards,
Diptee
Edited by: diptee s on Sep 21, 2011 4:48 PM

WHAT IS THE BEST WAY TO CREATE AN XSD FILE (TO BE USED BY SOAP ADAPTER)

Dear friends
I have a simple scenario.
OUTBOUND DATA --> SOAP ADAPTER --> ( XI ) --> RFC ADAPTER --> INBOUND DATA
The XML file that I got from mapping area of IR (Design) is as follows
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_NAME_SOURCE xmlns:ns0="http://test3.com">
<FIRSTNAME>DAVE</FIRSTNAME>
<LASTNAME>SMITH</LASTNAME>
</ns0:MT_NAME_SOURCE>
If you notice, there are only 2 fields.
I need to create an XSD file and import it as an external object, which I can use for SOAP Adapter.
Which is the best way to create it.
Also, I need to know if there is any step by step of sending a message from XML SPY. I have downloaded this software, but am not able to undertand how to use this.
Hope to hear from any experts on this forum.
Thanks in advance
Ram

Hi Ram,
See the below blog..
It shows how to send SOAP message using XML Spy.
It also shows how to generate wsdl.
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
Regards,
Sumit

IOException: invalid content type for SOAP: TEXT/ using Sender SOAP adapter

Hi all,
When I am using Sender SOAP adapter, i am getting (MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML using connection SOAP_http://sap.com/xi/XI/System) exception.
From my RWB I can see:
2009-05-25 16:18:39 Information The message was successfully retrieved from the call queue.
2009-05-25 16:18:39 Information The message status was set to DLNG.
2009-05-25 16:18:39 Error Failed to parse the XI system response.
2009-05-25 16:18:39 Error The message was successfully transmitted to endpoint com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML using connection SOAP_http://sap.com/xi/XI/System.
2009-05-25 16:18:39 Error The message status was set to FAIL.
2009-05-25 16:18:39 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIMessage creation failed (inbound). Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage. Reason: java.io.IOException: invalid content type for SOAP: TEXT/HTML
Please help if possible! Thanks!
Mayank

Hi,
Check in SLD your integration engine business system have the following
pipeline url : http://server:httpport/sap/xi/engine?type=entry
check Http port also
After that go to TCODE - SXMB_ADM - integrationn engine configuration and check if your server is configured as HUB with the same url or not.
Thanks
Kasturika Phukan

SOAP Adapter Sender PI7.1: 400 Bad HTTP request

Hello,
I have a problem with a SOAP adapter sender communication channel.
I'm trying to migrate a scenario from XI 3.0 to PI7.1 SP6 (PI_BASIS 2006_1_710 SAPKIPYN06).
I can send messages successfully to the old system using the URL
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BC_Name:CC_SOAP_Sender
On PI7.1 I get
    400 Bad HTTP request
    Error: -21
    Version: 7010
    Component: HTTP_PLG
    Module: http_plgrt_mt.c
    Line: 5226
    Error Tag:
    Detail: illegal request version
I have created a Sender Agreement, generated the wsdl from that and tried the URL in there.
Surprisingly it has the old format, namely
    http://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_Name&receiverParty=&receiverService=&interface=myInterface&interfaceNamespace=urn:my.Interface:ns
although the 7.1 documentation describes the ?channel=party:service:channel style only.
Anyway, the result remains the same.
I tried some other approaches like escaping the colons in the URL without success.
The user has the role SAP_XI_DEVELOPER_J2EE assigned.
Any idea what's wrong here?
Thanks in advance
Rainer

>>In RWB the channel appears as "started but inactive".
Yeah,it will be like that because you are posting messages directly to Integration server."Propose URL" does that.You are bypassing the adapter engine when you use the URL generated by "Propose URL" button.
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
The above blog gives the reason for this,if you want to bypass the adapter engine,then generate the URL as given in the above blog
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
This blog explains how to post message to adapter engine,here you need to change the URL,don't click on "Propose URL" button.You can monitor SOAP adapter in RWB only if you generate the URL as given in second blog
The URL which is working for you in XI 3.0 is posting messages to adapter engine,so generate the URL in PI 7.1 in the same way,by following the second blog i have mentioned.
Thanks
Aamir

Error in using XI-SOAP adapter, but no error with SAP-BC

Hi,
I am working on RFC->XI->Webmethod (.asp) scenatio.
I am using SOAP adapter.
Whin I am not using "Do not use SOAP Envelop".
I am getting "com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML" Error in SXMB_MONI.
But when I am using "Do not use SOAP Envelop" then I am not getting any error. in SXMB_MONI status showing Successfully Processed. But the responce i am getting is "You are not authorized to view this page // HTTP 401.1 - Unauthorized: Logon Failed"
But same web-service is working fine while connected with SAP-BC.
Please Help why scenario is working with BC, but not with XI.
Thanks & Regards

Hi Bhavesh,
Thanks for reply.
I am getting all success in message monitoring, but still web-services sying they are not getting any message.
I am attaching all 4 logs for one synchronous communication of message monitoring.
I am not able to understand where message going and why XI showing success every where.
********1st(Sent Messages)
Success SOAP: response message leaving the adapter
Success Application attempting to send an XI message asynchronously using connection AFW.
Success Trying to put the message into the send queue.
Success The response message for message cf4fd921-4a74-11db-9312-001279933263(INBOUND) was successfully transmitted to the calling application.
Success The message status set to DLVD.
Success The application sent the message asynchronously using connection AFW. Returning to application.
********2nd (Sent Messages)
Success RFC adapter received sRFC for Z_PA_SAP_TO_Webservice from D02/230. Attempting to send message synchronously
Success Application attempting to send an XI message synchronously using connection AFW.
Success Trying to put the message into the call queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the call queue.
Success The message status set to DLNG.
Success The message was successfully transmitted to endpoint http://XYZ.com:8000/sap/xi/engine?type=entry using connection AFW.
Success The application sent the message synchronously using connection AFW. Returning to application.
Success The message status set to DLVD
**********3rd (Received Messages)
Success Using connection AFW. Trying to put the message into the receive queue.
Success The XI response message for message d0372be1-4a74-11db-91d7-001279933263(INBOUND) was successfully returned to the calling application.
Success The message status set to DLVD.
**********4th (Received Messages)
Success The message was successfully received by the messaging system. Profile: XI URL: http://XYZ.com:50000/MessagingSystem/receive/AFW/XI
Success Using connection AFW. Trying to put the message into the request queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the request queue.
Success The message status set to DLNG.
Success Delivering to channel: IF_O_502_WebserviceBusService_SOAP_In_02
Success SOAP: request message entering the adapter
Success SOAP: completed the processing
Success SOAP: response message received d0372be1-4a74-11db-91d7-001279933263
Success The message status set to DLVD.
Success The message was successfully delivered to the application using connection AFW.

Enabling HTTPS with Client Authentication for Sender SOAP Adapter on PI7.1

Hello All,
We are currently building up a HTTPS message exchange with an external client.
Our PI 7.1 recieved over HTTPS messages on an already configured Sender SOAP Adapter.
The HTTPS (SSL) connectivity works fine and was completely configured on the ABAP Stack at Trust Manager (TC=STRUSTSSO2)
Login to Message Servlet "com.sap.aii.adapter.soap.web.MessageServlet is required and works fine with user ID and password.
Now we have to configure the addtional Client Authentication.
At SOAP Adapter (Sender Communication Channel) under "HTTP Security Level"you are able to configure "HTTPS with Client Authentication".
But what are the next steps to get this scenario successfully in place?
Many thanks in advance!
Jochen

Hi Colleagues,
following Steps still have to be done:
- Mapping public key to technical user at Java Stack
As preparation you have to activate value "ume.logon.allow.cert" with true under "com.sap.security.core.ume.service" under Config Tool. At NWA under Identity Management at for repecively technical user the public key certificate
- Be sure CA root certivicate at Database under STRUSTSSO2
- Import intermediate Certificate under Certificate List at Trast Manager for the Respecive Server Note
- use Login Module "client_cert" which you have to configure under NWA\Configuration Management\Authentication for Components "sap.com/com.sap.aii.adapter.soap.app*XISOAPAdapter".
Many thanks to all for support!
Regards,
Jochen

Error using Sender SOAP adapter over HTTPS

Hi experts,
Few weeks ago, i developed an interface as follows: SOAP <-> XI <-> RFC.
I tested the functionality using Altova and everything went well, with HTTP.
However, when i use HTTPS it fails throwing these error messages (pop ups):
"HTTP error: could not post file"......
"Error sending the soap data"
I have reviewed the SSL certificates installation and everything seems to be ok, but currently i am stuck and do not know how to fix this.
I have also change the ID comm channel from HTTP to HTTPS with client aut.
Is there any special service i have to activate? (XI services and SPIGATE are already done)
Could you please assist?
Thanks in advance and best regards,
David

David,
have a look @ these threads...u may get some help!!!
Sender Soap with HTTPS
https Soap Adapter
Regards
Biplab

Using receiver SOAP Adapter

Hi,
I have the following Scenario:
I want to send an AuthenticateUSer method request to a WebService using SOAP receiver adapter synchronusly, and receive the Response.
I've found the following error in monitoring:
 <?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="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PARSING">ADAPTER.SOAP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>soap fault: Server was unable to process request. --> Object reference not set to an instance of an object.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any ideas?
How do I say to the SOAP adapter wich method I want to Invoke?
Thanks and Regards.

Hi Moorthy,
I've test the WebService with WebService Studio 2.0 and it is working.
I've test the SOAP Adapter with
http://<host>:<port>//XISOAPAdapter/HelperServlet?action=GetChannelInfo&channelID=<Object%20version%20ID>
and others and found the following log:
<?xml version="1.0" ?>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
- <detail>
- <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.SOAP_EXCEPTION</code>
- <text>
- <![CDATA[
com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Channel object with Id Channel:<Object version ID> not available in CPA Cache.
 at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getCPAObject(AbstractLookupManager.java:172)
 at com.sap.aii.af.mp.soap.web.HelperServlet.processGetChannelInfo(HelperServlet.java:455)
 at com.sap.aii.af.mp.soap.web.HelperServlet.doGet(HelperServlet.java:131)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 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>
In RWB, the SOAP Adapter Monitoring looks green, and in http://<host>:<port>//XISOAPAdapter/MessageServlet
Message Servlet is in Status OK
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#11 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0
ModuleProcessorRemote not instantiated
Is the Adapter working properly?
Thanks and Regards.

Role for the user used in SOAP adapter

Hi,
What are the roles required to the user used for user authentication in a soap adapter.

hi,
if you want to be more specific this is the only role required:
xi_adapter_soap_message (on the adapter engine)
Regards,
Michal Krawczyk

Invoking a Webservice using a SOAP adapter

Hi,
I have the following scenario.
SAP ABAP outbound proxy <-> SAP XI <--> External webservice.
The above call is a synchronous call from SAP R/3 and a receiver soap adapter is configured for the Webservice.
I am getting the following error messages when I try to run the scenario.
1)ADAPTER.SOAP_EXCEPTION.
2)<SAP:AdditionalText>
soap fault: Server did not recognize the value of HTTPHeaderSOAPAction
</SAP:AdditionalText>
What could be the possible reasons for the error message?
In the target URL of the soap adapter I am specifying the path till .asmx.
Thanks,
Leo

Hi,
There are 2 pieces of data that must be provided in the SOAP receiver adapter. Both of them can be obtained from the WSDL of the soap service provider.
1. Target URL, which can be obtain from the attribute "location" of the "address" element in the WSDL.
2. SOAP Action, which can be obtain from the "soapAction" attibute of the "operation" element in the WSDL.
Regards,
Bill

Soap Adapter not Picking up files from sender

Hello All,
I have configured a SOAP Adapter and started it. When i place a file in the appropriate directory, it is not getting picked up. Are there any reasons this could happen ?
I would really appreaciate it if someone can help me with this !!!
Below is the log:
17:26:27 (3812): Enabling service ToWS
17:26:27 (3812): Enabling service FromWS
17:26:27 (3823): SOAP adapter initialized
17:26:27 (3830): Starting the server at 8660:/XIservices/MXS/xmb
17:26:27 (3830): Starting the server at 4444:/XIservices/MXS/ws
17:26:27 (3807): SOAP adapter started
Below is part of the config file:
The port and path where the adapter waits for web service messages from clients.
XMBWS.WSPort=4444
XMBWS.WSPath=/XIservices/MXS/ws
XMB.SenderBusinessSystem=WLX_100
#XMB.ReceiverBusinessSystem=MD1_400
XMB.User=XIAPPLUSER
XMB.Password=********
XMB.Client =100
XMB.Language=EN
XMB.SenderInterfaceNamespace=http://xi.sap.com/wlx
XMB.ReceiverInterfaceNamespace=urn:sap-com:document:sap:idoc:messages
XMB.SenderInterfaceName=ProcesseFT
XMB.ReceiverInterfaceName=Z_SERVICE_ENTRY.ZSERVICEENTRY01
XMB.TraceLevel=0
XMB.LoggingLevel=0
XMB.QualityOfService=EO
XMB.ContentType=text/xml

Hi,
If you are using a Stand-alone J2SE Adapter Engine, you can create a SOAP adapter to pick a SOAP message from a file system and send it to the Integration Server. This is available with the XI3.0.
The configuration will look like this.
Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble
This adapter instantiates a bubble bag for supporting
a soap file upload and sender. A bubble bag is a collection of Bubble
instances that form some processing chain of message objects.
Below parameter Bubble.Helper specifies the helper class that implements
the ModuleBubbleHelper interface. This class is used to instantiate
a bubble bag for this adapter.
Sets the bubble module helper that can instantiate your bubble bag
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperSOAPFileSenderImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Below this line are the parameters specific to the ModuleBubbleHelperSOAPFileSenderImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
This module loads files from the local file system, consruct SOAP messages
(or SOAP with Attachments messages), and send them to the specified Web Service target URL.
Upon successful completion, response messages are stored in the file system.
Files stored can represent a plain payload, a SOAP envelope, or a SOAP with Attachments.
Plain payload files and SOAP envelope files may be packaged in MIME using some MIME headers.
SOAP with Attachments files must be packaged in MIME.
Specifies the type of the file. The available values are:
plain for plain; soap for soap envelope; swa for soap with attachments
SFSender.ContentMode=soap
Specifies the packaging
true for MIME packaged file; false for bare content
SFSender.MIMEPackaged=true
log everything (4-digit binary, where the bits indicate which
information is logged: req message, req context, resp request, resp context)
SFSender.Log=1111
The target URL to which messages are sent.
SFSender.TargetURL=http://p28848:4040/mysoaphandler
The upload directory on the local file system
This directory has six sub directories with names 0, 1, 2, 3, 4, 5, and 6. (they will be created)
The meaning of each sub directories are:
0 = inbox where you place messages to be sent
1 = trash box
2 = work box
3 = successfully completed (original) messages go in
4 = response messages come in (if any)
5 = undelivered (original) messages go in
6 = error messages come in (if any)
In these directories, the file names are used as key and there can be only one file with
the same name except in the trash box. So, when you place in the inbox a file with
the name identical to one of the files stored in another directory, it will not processed.
SFSender.Directory=/tmp/sfsender
The polling interval in milliseconds (default is 5000)
#SFSender.PollingInterval=5000
The retry delay after each failure in milliseconds (default is 5000)
#SFSender.RetryDelay=5000
The maximal retry count upon failures (default is 3)
After the maximal retry count is reached, the message is moved as undelivered.
#SFSender.RetryCount=3
The number of dispatchers to send requests (default is 3)
SFSender.DispatcherCount=1
END
Hope this helps.
@Ravi: You may call me at +91 9844167672.
Warm regards,
Venki.

Testing a "Receiver SOAP Adapter" - Calling a remote webservice from PI

Hi ,
I am trying to call a remote webservice from PI 7.0.
The WSDL file is successfully imported to PI to create the required message types.
The "receiver SOAP adapter" is configured as the communication channel.
I would like to know the ways of testing the remote webservice from PI 7.0.
Thank you,
Panda

Hello there!
I think this link should help you
https://help.sap.com/saphelp_nwpi71/helpdata/en/46/793034608c0ad3e10000000a11466f/frameset.htm
Thanks and regards,
Caio Cagnani

What would be the web servendpoint for a scenario using sender SOAP adapter

Hi,
I have setup a scenario to consume a Service interface in SAP namespace. This is a asynch inbound SI which is not point to point enabled which means the WSDL we get are only the definitions with no endpoints. So I exported it as an external definition which I will then use as sender interface so the scenario looks like this:
Third Party -> SOAP Sender Adapter -> Outbound SI(Imported WSDL) -> XI Box (Mapping etc) -> Inbound SI -> XI Receiver Adapter -> ABAP box
Once all has been setup, for SOAP sender adapter for third party to send data the URL looks like this.
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
But I dont think so this is the endpoint beacuse if I give this in browser I only get an OK status from XI box, what should I give to third party they can use as WSDL endpoint to generate the proxy/stub on their side to send data to SAP.
Regards, Shadab

This is a asynch inbound SI which is not point to point enabled which means the WSDL we get are only the definitions with
no endpoints. So I exported it as an external definition which I will then use as sender interface so the scenario looks like this:
Third Party -> SOAP Sender Adapter -> Outbound SI(Imported WSDL) -> XI Box (Mapping etc) -> Inbound SI -> XI Receiver
Adapter -> ABAP box
Inbound (receiver-end) Service Interface is to be developed from an imported WSDL......not the Outbound (Sender-end) Service Interface.....you actually did the procedure which needs to be done when SOAP is at receiver-end.
If you are clicking the WSDL tab in Service Interface and then taking it as the required WSDL then note that this is not the one.....it is to be generated from ID --> Tools --> Display WSDL (it will be based on the outbound SI)......this will have the end-point which you you mentioned
Now you give this WSDL to the sender application (it will have the end-point) and ask them to develop their coding accordingly.
If you need to view that WSDL in explorer, then you have to publish it somewhere....like in Service Registry (or WSnavigator)
Regards,
Abhishek.

Use of SOAP adapter in PI7.11 - migration from PI7.0

Similar Messages

Maybe you are looking for