Issue with Receiver SOAP adapter for synchronous scenario

Hello All,
We are facing a strange issue with the SOAP adapter in the interface we have setup. This is the 1st time we are using SOAP adapter in our system (PI 7.11 SP7). We are making a synchronous HTTP call to the web service exposed by another system in our landscape. The payload is send with SOAP envelope and there are no credentials to be maintained in PI settings.
The issue is that we are always getting timeout exception in PI audit logs after sending the request (3 minutes - standard timeout value, no additional config for this). But target system has confirmed that they are sending the response back. We tested from our server OS level and have received the response back in the same screen (to verify there is no firewall/port issue in between the systems). But when tried from RWB, it is always giving the timeout exception and we are not able to see any other log.
We have tried checking in the NWA logs as well after increasing the logging level to ALL for com.sap.aii.adapter.soap. But surprisingly, we didn't get any logs at all for the outgoing SOAP call or incoming response and hence we are unable to trace the issue.
We have setup another synchronous inbound SOAP interface (PI exposing the webservice) and it is working fine. We are also able to trace the logs in both audit log and NWA logs.
Is there anywhere else we can check for the logs? Audit logs is showing timeout error and we are not able to see anything in NWA logs.
Does the target system need to maintain PI credentials in the header when they send the synchronous response back?
Are there any specific settings which should be checked to enable the sync communication? (this should not be the case since the inbound interface is working fine)
Please help.
Thanks
Justin

Hi Amit,
Thanks for the reply.
Yes we had tested successfully via SOAP UI as well (forgot to mention that). We are getting back the expected response in SOAP UI without using any credentials. We got the same response when we tested it through OS commands from PI server.
The WS is hosted by the target system and they haven't maintained any credentials at their end. So when PI is trying to access, we don't need to provide any credentials. My question is, whether the target system should keep any credentials to send the synchronous response back to PI (java stack). We have tried that as well but since there aren't any logs, we are unable to verify whether the credentials are coming correctly.
The service interfaces are correct and PI configuration are OK. I will try the XPI inspector for logs as you have suggested.
Thanks
Justin

Similar Messages

Issue with Receiver MDM Adapter - Integrated Configuration

Hi Experts,
My scenario is I need to pick a file from PI Directory and push it into MDM Ready folder.
The source file structure is ~ delimiter text file and at the receiving end , I need to push the same file as it is.
At the receiving side I have used MDM Adapter.
The issue at receiving side is:
I am receiving file with .xml extension with the same content as of source file but my requirement is .txt file.
Please advise on this.
I am using SAP PI 7.31.
P.S.- I have not used FTP at the receiver side due to some other concerns.
Thanks,
Vivek Jain

Hi Amit,
Thanks for the reply.
Yes we had tested successfully via SOAP UI as well (forgot to mention that). We are getting back the expected response in SOAP UI without using any credentials. We got the same response when we tested it through OS commands from PI server.
The WS is hosted by the target system and they haven't maintained any credentials at their end. So when PI is trying to access, we don't need to provide any credentials. My question is, whether the target system should keep any credentials to send the synchronous response back to PI (java stack). We have tried that as well but since there aren't any logs, we are unable to verify whether the credentials are coming correctly.
The service interfaces are correct and PI configuration are OK. I will try the XPI inspector for logs as you have suggested.
Thanks
Justin

Error in Receiver Soap Adapter for Google API

Hi,
I am working on HTTP-XI-Soap scenario which on the receiver side calls google API for spell check.
I get the following error : No Deserializer found to deserialize a ':key' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
However if I try calling the webservice individually using SOAP Client it works fine and do get desired response.The soap message that is sent by the client to the target URL is :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:GoogleSearch" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <urn:doSpellingSuggestion soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
 <key xsi:type="xsd:string">qXWD4x1QFHIo/dePqlYOLwT7kMmkv80E</key>
 <phrase xsi:type="xsd:string">Bratney</phrase>
 </urn:doSpellingSuggestion>
 </soapenv:Body>
</soapenv:Envelope>
However if i remove the "xsi:type="xsd:string" part from the element 'phrase' and 'key' it returns the same error as it does while using with XI.
Hence I am assuming that that the outgoing soap message elements need to have the above highlighed attribute.
Now I want to have this attribute(xsi:type="xsd:string) in the soap message that is sent from XI.
My question is , Is there any setting using which I can add the attributes in the above form to the outgoing message from XI.I do not want to use a adapter Module.
Thanks & Regards,
Sidharth

Hi Sidharth,
You post here the soap message that is sent by the client to the target URL, but did you look to the soap message that is sent by XI?
Try the AF monitor http://<host>:<j2ee-port>//MessagingSystem/monitor/monitor.jsp?
Because XI soap adapter doesn't support all tags of wsdl rpc-based, we need to adjust them...
Look to the SOAP FAQ (SAP note number 856597) under question "Can I convert an RPC styled WSDL to a document styled WSDL?"... Look at last but one paragraph ;o)
So, you need to change this attribute to one that it is compatible...
Go to http://service.sap.com/xi > Media Library > Documentation and there you will find this xls document -> SAP XI 3.0 (SP11) - Supported XML Schema and WSDL (EN) in this document you have all the compatible elements of wsdl for XI.
One more thing, you can adjust your soap request and change or add the required tags You can do it with xslt-mapping or create your won data types in XI without import the WSDL generated by google.
Hope it helps,
Ricardo.
Message was edited by: Ricardo Quintino

Send attachment with receiver SOAP adapter

Dear Guru's,
We have created a scenario SAP ERP (ABAP Proxy) -> PI 7.0 -> (Webservice) OSB.
In the ABAP Proxy have we attached a file (jpg). In the SXMB_MONI we see first the file (named attach), and second the MainDocument. It seem's this is the wrong sequence.
We tried to correct this with AF_Modules/PayloadSwapBean in the receiver SOAP adapeter, but it does not work.
There are blogs who tells about how to configure the parameters. We did it as follows:
AF_Modules/PayloadSwapBean swap1
AF_Modules/PayloadSwapBean swap2
swap1: swap.keyName = payload-name
swap1: swap.keyValue = attach
swap2: swap.keyName = payload-name
swap2: swap.keyValue = MainDocument
In the communication channel audit log the swap is processed succesfully, but we don't see nothing changing in the message sequence.
Can somebody please help me with this issue?
Kind regard,
Jeroen Jung

Hi Stefan,
The main thing at this moment is to change the sequence of the payload and attachement. PI puts the attachement first and than the payload and in that sequence the receiver application can't deal with it.
This is a multipart related message and in the header it refers to the image (image/jpeg) first instead of the payload (application/xml).
As you can see in the first message we have used PayloadSwap Adapter module in the receiver SOAP Communication Channel to change this sequence and in the Audit Log of the SOAP CC we can see that it does SWAP functionality succesfully but the result is the same and nothing happens.
Here below you can see the result of a http snapper grabber:
POST /EnterpriseContentManagement/ProxyServices/PS_EnterpriseContentManagement_v1 HTTP/1.0
Accept: */*
Host: localhost:8090
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
CallingType: SA
Content-Type: multipart/related; boundary=SAP_00e371ef-3ca3-11df-9503-001f2966194a_END; type="image/jpeg"; start="payload-9A6BAB4B2FE1273DE10000000A503151 @ sap.com"
Content-Length: 939196
SOAPACTION:
--SAP_00e371ef-3ca3-11df-9503-001f2966194a_END
content-id: payload-9A6BAB4B2FE1273DE10000000A503151 @ sap.com
Content-Type: image/jpeg
*********binary attachment data************
--SAP_00e371ef-3ca3-11df-9503-001f2966194a_END
content-id: payload-9B6BAB4B2FE1273DE10000000A503151 @ sap.com
Content-Type: application/xml
<?xml version="1.0" encoding="utf-8"?>
*********XML Message************
--SAP_00e371ef-3ca3-11df-9503-001f2966194a_END--
Do you have an idea how we can switch the sequence of payload and the attachment? Or why the SWAP functionality doesn't have any result?
Kind regards,
Danke
Jeroen Jung

Issue with Third Party Adapter for custom JCA Connector in Oracle 11g.

Hi,
For a proof of concept, I have created my own JCA Connector. I have deployed this connector in Weblogic and it works as expected.
Now I am trying to call the JCA Connecter from the SOA Bus. For this I have create a SCA Composite with a simple Web Service to expose the composite, a Third Party Adaptor to wrap the JCA Connector and a Mediator to wire the Web Service and the Third Party Adapter together. For the Third Party Adapter I have created both the needed *.wsdl and _3P.jca file my self. The problem is that I could not find any documentation about the _3P.jca file, and it looks like it that this file is new for 11g.
After some puzzling and debugging I am able to deploy the SCA Composite with the Third Party Adapter. Though when I test the exposed Web Service with the Enterprise Manager I get errors and a stack trace. The problem is that the Record Converter I have created receives the default XMLRecord implementation (oracle.tip.adapter.fw.record.XMLRecordImpl) and not the implementation of the XMLRecord I have created my self.
So the question is does anybody know how to configure the Third Party Adapter so that it will use my custom implemenation of the XMLRecord interface (oracle.tip.adapter.api.record.XMLRecord) instead of the default implementation of the XMLRecord (oracle.tip.adapter.fw.record.XMLRecordImpl).
I would suspect that it should be configured in the _3P.jca file, though I don't know how. The following is the content of the current _3P.jca file I am using.
<adapter-config name="DiskAdapter" adapter="Disk Adapter" wsdlLocation="JCADiskConnector.wsdl"
 xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<record-converter className="com.osc.jcaadapter.convert.DiskRecordConverter"/>
<connection-factory location="jndi/diskcf" adapterRef=""/>
<endpoint-interaction operation="Send" portType="Send_ptt">
 <use-record-converter addonNamespace="http://somecomp.com/DiskAdapter"/>
 <interaction-spec className="com.osc.jcaadapter.impl.DiskInteractionSpecImpl">
 <property name="FunctionName" value="do-it"/>
 </interaction-spec>
</endpoint-interaction>
</adapter-config>So I am hoping that some one knows how you should configure the Third Party Adapter so it uses my own implementation of the XMLRecord interface.

Hi Simeon,
That is a good suggestion, and I would certainly try to do that if I was not making a proof of concept. It would solve my problem of not getting the sub class of the XMLRecord.
Though for making my proof of concept I found a 10g example that used sub classes of the XMLRecord, and that is why I wanted to get the same example to work on 11g.
The alternative of passing a parameter through with InteractionSpecs, is an interesting though can not solve this problem. I don't have a problem with the javax.resource.cci.Record, I can determine the implementation of that in the conversion class it self.
The problem is the XMLRecord generated by the Oracle SOA Adapter Framework, some how I need a way to influence that to generate the correct implementation of the XMLRecord.
So your post is certainly helpfull if I was not trying to get this specific problem to work :).
But I am afraid that I will end up in implementing your sugestion.
Regards
Maikel.
Edited by: M. Dierdorp on 13-aug-2010 6:34

Production Issue with Receiver FTP Adapter

Hi all,
We have so many interfaces with ECC To FTP via XI, working fine.
We had problem with one particular Interface, FTP Owner is saying that we did not received any files since last night for this interface. But that receiver channel's log is saying clearly that file has been written to folder with given name.
Nearly 140 files needs to be received at FTP site. Suddenly they told that received all 140 files at a time with time all with stamp 11:40am
What might be the cause for this?? has any one faced this kind of issues??
Please share your thoughts
Regards
Suman

Hi rajesh,
Thnx for replying, there is no receiver channel on scheduled
Receiver communication channel time stamp is showing as same as time ecc generated with idoc.
But received at FTP is different time( more time difference)
Checked with FTP Admin, and there is no issues or downtime with FTP at that time.
>>use messaging system and search with message id for knowing this step time stamp.
How to check this, please let me know the link.
Regards

SOAP error in synchronous scenario for ABAP Proxy with Oracle D/B

Dear Experts,
I am working in Sender ABAP Proxy <====>SAP PI 7.31 JAVA only <====> Oracle Database. My proxy configuration are working successfully.
Apart from that, I have maintained a SOAP sender communication channel under the ECC business system with
Transport Protocol as HTTP
Message Protocol as XI 3.0
Adapter Engine as Central Engine
When I am testing from ECC at Tx SPROXY, I am receiving following error.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:746) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:505) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at
1. In XI3.0 protocol, I can not select BE but when selected HTTP 1.0 as Message protocol then I can find the BE.
2. No Response message is shown in ECC when testing the message.
3. How do Receiver JDBC adapter for Oracle Database is configured
4. What would be Message Protocol for Oracle Database i.e. XML SQL Format or Native SQL format for Select operation.
Please guide.. All your inputs will be appreciated......
Regards
Rebecca

Dear Indrajit,
Appreciate your inputs.. Yes I have configured all the ABAP proxy configurations and there no question of missing any thing as Tx SLDCHECK in ECC is working perfectly fine.
But still to go, some of the queries needs more input.
1.In ID, i have created a Sender SOAP communication channel with listed details.
Transport Protocol as HTTP
Message Protocol as XI 3.0
Adapter Engine as Central Engine
Is there any parameters which I may be missing from Module tab of Synchronous SOAP Cc ?
2. In the Cc monitoring, the JDBC receiver status shows "Database operation successfully completed" but I could not find any response data from database. The Message monitoring should have 2 messages for 1 trigger, but I could find only 1 message by SOAP only?
Sorry to bother experts...Please answer in sequence...
Regards
Rebecca

WSDL url for sender and receiver SOAP adapter

Dear Experts,
I am working on SOAP --> SAP PI --> SAP ECC synchronous scenario. That means I have to create 2 Cc for SOAP i.e. Sender as well as Receiver adapter. I am responsible for creating the Request as well as Response structure in SAP PI. The sender application team is dependent on me to get the WSDL file.
Please provide the suggestions on the below.
Sender SOAP adapter.
1. I will create the WSDL from Sender Aggreement. How to get the url and what is the navigation step? Should I provide the same url to sender application team to call the service.
Receiver SOAP adapter:
2. In the receiver SOAP adapter , Should I have to get the web service parameter of the sender application. As mentioned , I am creating the response structure as well. That means I can not import the WSDL from the sender application. How to get target url in the receiver SOAP Cc.
I refered to the forum SOAP SENDER - test in soapui but its not clear.
Regards
Alice Rebecca
Edited by: Alice@xi on Dec 20, 2011 5:48 PM

Dear Bhaskar,
For synchronous scenario
 Request
MS Application (SOAP)<--> SAP-PI <--
> SAP ECC.
 Response
I am creating the Request as well as Response structure in SAP-PI and its agrreement for both
the ways.
So for the MS appl team, I will give the WSDL url from the sender agreement to make the request to SAP-ECC.
Now for receiving the response from SAP ECC, from where I should find the value to enter in the target url of SOAP
receiver channel.
1.Should I take the target url value from the MS Application team?
2.How to know whether the MS Application or SAP ECC is hosting the web service?
Regards
Alice

SOAP adapter works synchronously with EO !??

Hello,
I configured Sender SOAP Adapter with EO. The SOAP adapter follow the message to a BPM.
All of this process work fine with the HTTP Adapter (that I use for test) but when I use the SOAP Adapter I receive a strange error message :
BPE_ADAPTER.SYNCHONOUS_MESSAGE
The process does not support the given synchronous interface or does not support synchronous messages
Does anybody know how to sovle this ?
Thanks
Regards
Chris

I always have the return code 0. This process work with the HTTP Adapter but not with the SOAP Adapter.
The only thing I change was the adapter in the sender agreement.
This is the begeening of the XI Message :

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SOAP:Header>
<SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>1CCC5F0F-F2BB-BC49-BDC3-A6C2F209A645</SAP:MessageId>
<SAP:TimeSent>2006-12-26T11:50:36Z</SAP:TimeSent>
<SAP:Sender>
<SAP:Service>TOFFStaging</SAP:Service>
<SAP:Interface namespace="http://t.be/xi/TOFF/LeadCreation">MIOA0001_Offer</SAP:Interface>
</SAP:Sender>
<SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>BP0001_ToffLeadCreation</SAP:Service>
<SAP:Interface namespace="http://t.be/xi/PI/LeadCreation">MIAA0001_Offer</SAP:Interface>
<SAP:Mapping notRequired="M">
<SAP:ObjectId>rrEYQC3BMRyBTROgtt+SaQ==</SAP:ObjectId>
<SAP:SWCV>g2bqoJATEdu/Gvy1rBATzQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://t.be/xi/PI/LeadCreation">MIAA0001_Offer</SAP:Interface>
</SAP:Main>
<SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
Regards,
Chris

Target url for receiver soap adapter

Hi everybody
where will I get the target url to enter in the receiver soap adapter parameters? I got the link from wsdl under "address location"..But when I open the link from the internet explorer I could see an empty wsdl
<faultstring xml:lang="en">SRT: Wrong Content-Type and empty HTTP-Body received</faultstring>
thanks
Ramya

Hi Ramya,
When you try opening the URL using web browser, you are not sending any data and hence in response you get an empty message.
But at the same time, the message shows you that the service corresponding to that URL is invoked, activated and running.
Give the same URL in your receiver communication channel and try execcuting the scenario, as far as receiver URL is concerned, it should work.
-Tanaya.

Configure Client Authentication for Receiver SOAP Adapter

Hi,
Can you please tell me what i should give in receiver soap channel for KeyStoreEntry and KeyStoreView after checking Configure Client Authentication checkbox,as I have got certificate from third party.
Thanks in advance
Best Regards,
Harleen Kaur Chadha

Hi,
Keystore Entry:
Login to Visual Admin --> Server --> Services --> KeyStorage --> TrustedCAs --> Load --> Select the location where you have stored the certificate on your local system
Load function is used as you have already got the certificate....
Once this is done you will find an entry for your certificate in the Entries tab of your TrustedCAs section.
This is your Keystore Entry...in other words it the name of your certificate.
Keystore View:
http://help.sap.com/saphelp_webas630/helpdata/en/16/c0503e1dac5b46e10000000a114084/content.htm
Are you going to consume Logon tickets of the Third party system (which is other than SAP J2ee engine of your XI)? If yes, then you may also need to do some more settings in the J2ee Engine.
Regards,
Abhishek.

SAP PI conceptual best practice for synchronous scenarios

Hi,
 Apologies for the length of this post but I'm sure this is an area most of you have thought about in your journey with SAP PI.
 We have recently upgraded our SAP PI system from 7.0 to 7.1 and I'd like to document best practice guidelines for our internal development team to follow.
I'd be grateful for any feedback related to my thoughts below which may help to consolidate my knowledge to date.
 Prior to the upgrade we have implemented a number of synchronous and asynchronous scenarios using SAP PI as the hub at runtime using the Integration Directory configuration.
No interfaces to date are exposes directly from our backend systems using transaction SOAMANAGER.
 Our asynchronous scenarios operate through the SAP PI hub at runtime which builds in resilience and harnesses the benefits of the queue-based approach.
 My queries relate to the implementation of synchronous scenarios where there is no mapping or routing requirement. Perhaps it's best that I outline my experience/thoughts on the 3 options and summarise my queries/concerns that people may be able to advise upon afterwards.
 1) Use SAP PI Integration Directory. I appreciate going through SAP PI at runtime is not necessary and adds latency to the process but the monitoring capability in transaction SXMB_MONI provide full access for audit purposes and we have implemented alerting running hourly so all process errors are raised and we handle accordingly. In our SAP PI Production system we have a full record of sync messages recorded while these don't show in the backend system as we don't have propogation turned on. When we first looked at this, the reduction in speed seemed to be outweighed by the quality of the monitoring/alerting given none of the processes are particularly intensive and don't require instant responses. We have some inbound interfaces called by two sender systems so we have the overhead of maintaing the Integration Repository/Directory design/configuration twice for these systems but the nice thing is SXMB_MONI shows which system sent the message. Extra work but seemingly for improved visibility of the process. I'm not suggesting this is the correct long term approach but states where we are currently.
 2) Use the Advanced Adapter Engine. I've heard mixed reviews about this functionaslity, there areh obvious improvements in speed by avoiding the ABAP stack on the SAP PI server at runtime, but some people have complained about the lack of SXMB_MONI support. I don't know if this is still the case as we're at SAP PI 7.1 EHP1 but I plan to test and evaluate once Basis have set up the pre-requisite RFC etc.
 3) Use the backend system's SOAP runtime and SOAMANAGER. Using this option I can still model inbound interfaces in SAP PI but expose these using transaction SOAMANAGER in the backend ABAP system. [I would have tested out the direct P2P connection option but our backend systems are still at Netweaver 7.0 and this option is not supported until 7.1 so that's out for now.] The clear benefits of exposing the service directly from the backend system is obviously performance which in some of our planned processes would be desirable. My understanding is that the logging/tracing options in SOAMANAGER have to be switched on while you investigate so there is no automatic recording of interface detail for retrospective review.
 Queries:
 I have the feeling that there is no clear cut answer to which of the options you select from above but the decision should be based upon the requirements.
 I'm curious to understand SAPs intention with these options -
 - For synchronous scenarios is it assumed that the client should always handle errors therefore the lack of monitoring should be less of a concern and option 3 desirable when no mapping/routing is required?
 - Not only does option 3 offer the best performance, but the generated WSDL is ready once built for any further system to implement thereby offering the maximum benefit of SOA, therefore should we always use option 3 whenever possible?
 - Is it intended that the AAE runtime should be used when available but only for asynchronous scenarios or those requiring SAP PI functionality like mapping/routing otherwise customers should use option 3? I accept there are some areas of functionality not yet supported with the AAE so that would be another factor.
 Thanks for any advice, it is much appreciated.
 Alan
Edited by: Alan Cecchini on Aug 19, 2010 11:48 AM
Edited by: Alan Cecchini on Aug 19, 2010 11:50 AM
Edited by: Alan Cecchini on Aug 20, 2010 12:11 PM

Hi Aaron,
I was hoping for a better more concrete answer to my questions.
I've had discussion with a number of experienced SAP developers and read many articles.
There is no definitive paper that sets out the best approach here but I have gleaned the following key points:
- Make interfaces asynchronous whenever possible to reduce system dependencies and improve the user experience (e.g. by eliminating wait times when they are not essential, such as by sending them an email with confirmation details rather than waiting for the server to respond)
- It is the responsibility of the client to handle errors in synchronous scenarios hence monitoring lost through P-P services compared to the details information in transaction SXMB_MONI for PI services is not such a big issue. You can always turn on monitoring in SOAMANAGER to trace errors if need be.
- Choice of integration technique varies considerably by release level (for PI and Netweaver) so system landscape will be a significant factor. For example, we have some systems on Netweaver 7.0 and other on 7.1. As you need 7.1 for direction connection PI services we'd rather wait until all systems are at the higher level than have mixed usage in our landscape - it is already complex enough.
- We've not tried the AAE option in a Production scenarios yet but this is only really important for high volume interfaces, something that is not a concern at the moment. Obviously cumulative performance may be an issue in time so we plan to start looking at AAE soon.
Hope these comments may be useful.
Alan

Receiver SOAP Adapter error

Hi All,
 I am getting this response error message in my receiver SOAP Adapter while invoking a synchronous webservice.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <ProcessMessageResponse xmlns="http://Sleek.Integrator.Messaging" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProcessMessageResult>Value cannot be null. Parameter name: Request string is a null reference.</ProcessMessageResult>
</ProcessMessageResponse>
Thx in advance
Ravijeet

Hi All,
 I am still getting the same error value is null. I am not able to track what could be the cause of the error. If I am taking the message from SXMB_MONI and using it in a client tool it is successfully calling the webservice.
Do we need to explicitly mention in some configuration that content type is soap/xml. SOAP header is omitting the content type or is not specifying "soap/xml" as the content type.
I am interacting with a WAF websevice, is there any compatibilty issue with Windows Webservice and SAP XI?
Also what should I pick as the SOAP Action from this wsdl file definition
<wsdl:portType name="IMessageProcessor">
 <wsdl:operation name="ProcessMessage">
 <wsdl:input message="tns:IMessageProcessor_ProcessMessage_InputMessage" wsaw:Action="XXX.Messaging/ProcessMessage"/>
 <wsdl:output message="tns:IMessageProcessor_ProcessMessage_OutputMessage" wsaw:Action="XXX.Messaging/ProcessMessageResponse"/>
 </wsdl:operation>
 </wsdl:portType>
 <wsdl:service name="MessageProcessor">
 <wsdl:port name="BasicHttpBinding_IMessageProcessor" binding="i0:BasicHttpBinding_IMessageProcessor">
 <soap:address location="http://XXX.com/cardax/provisioningservice"/>
 </wsdl:port>
Thx in advance
Ravijeet

In what QOS does the receiver SOAP adapter work BE or EO?

Hi,
In what QOS does the receiver SOAP adapter work BE or EO?
My guess is that it is by default EO, if so how do i make it work like synchronous?
There is no option to set it explicitly.
Thanks]
Shakthi

Siva,
In receiving adapter you can't set the status. The receiving QOS is set in the pipeline by using the Sender Comm.channel QOS.
So for example in SOAP to SOAP scenario, if you set the Sender comm.channel as BE, then through out the Pipeline till it reaches the Receiver Comm.channel the QOS will be considered as BE only( Even though you didn't explicitly said to the Receiver comm.channel).
Hope it helps!
raj.

Error in Adapter engine of receiver soap adapter

Hi All,
There is one production issue i am currently facing in receiver SOAP adapter while interacting with third party web service(Asynchronous call).
Below is the description i am getting in audit logs.
Success SOAP: completed the processing
Error SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Success SOAP: sending a delivery error ack ...
Success SOAP: sent a delivery error ack
Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Invalid Session ID or Session Expired.
Error The message status set to NDLV.
Moreover this is a production issue and interface was running fine till last friday.
Has someone ever faced this issue ?
Please provide your valuable inputs on this.
Thanks
Anku

Hi,
Search in sdn with your error message string,you will find ton of links.
HTTP401 error occurs for many reasons.
still no solution let us know..
Regards,
Raj

Issue with Receiver SOAP adapter for synchronous scenario

Similar Messages

Maybe you are looking for