Receiver Soap channel

Dear All,
My scenario is IDOC to SOAP.
I need to provide the user authetication details say only the username and password in the communication channel .
My target is a Sieble system .Can anyone suggest me whether we should do any settings in the Sieble system to caputure these user authetication details.
Thanks in Advance,
Lavanya .B

Hi All,
Thanks for the replies.
As of now ,the Sieble team have provided the userid and password along with the URL,ie,say example
"https://abcd101.xyz.com:80/enu/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=test&Password=test"
But now , I need to configure the channel without giving the user id and password in the url but by selecting the " Configure User Authentication" check box. ie ,url will be, "https://abcd101.xyz.com:80/enu/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute"
When I tested ,got the following below error,
"HTTP 500 Internal server error"
so for this should the Sieble team should do some settings to capture these id and password?
Can anyone suggest me on this.
Thanks and regards,
Lavanya Balanandham.

Similar Messages

Target URL in the Receiver SOAP channel in PI 7.11

Hi
I have designed integrated Configuration in PI 7.11 and i have SOAP sender and SOAP receiver. SOAP sender is fine but for SOAP receiver i have an issue with the target URL that i selected.
Initially the receiver was ABAP proxy with HTTP connection as we dont have ABAP related adapters in AAE i used SOAP. But i have used the same URL that is the Target host configured in the HTTP ABAP connection to the target system. Then i am getting the following error at the receiver comm channel
Message processing failed. Cause: com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme
I am sure i am doing a mistake, the URL i am using is wrong as it is not meant for SOAP calls. Please suggest me what needs to be done here.

..I am sure i am doing a mistake, the URL i am using is wrong as it is not meant for SOAP calls. Please suggest me what needs >>to be done here
You are using Integrated configuration with PI 7.1 EHP1 version. That means SOAP supports as PI native protocol (XI) for PROXY scenario. So, you have to create soap receiver adapter and choose message protocol as XI.
Integrated configuration occurs in java stack engine and XI adapter(proxy) not exists there. Only if you do classical processing (IE) then you can use XI adapter at the receiver side. Thats the reason you dont find XI adapter in the integrated configuration.
Hope I answered your question

Receiver SOAP channel error-- Cant parse the document; HTTP 200 OK

Hi All,
I am facing below error in SOAP receiver communication channel
SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 200 OK
If I use "Do Not se SOAP Envelop" in receiver communication channel then it shows successfully delivered in message monitoring but never reached to target application. And if I uncheck "Do Not se SOAP Envelop" then the error is as I mentioned above.
Both ways it not working foe me.
Please advice.
Thanks
Shivi

Hi
I had a similar issue recent times and I have enablede the xpi inspector to check the logs of the request and the response sent and received...
Based on that you can check whether your payload is able to sent to receiver in proper format or any other issues..
Also try to check the payload format using the SOAPUI whether the ws is working fine for that or not.
HTH
Rajesh

Receiver SOAP channel error: Communication over HTTPS. Unable to create a socket

Hi,
I am getting following error while sending message from PI (7.1) to SalesForce system:
'SOAP: call failed: java.io.IOException: Communication over HTTPS. Unable to create a socket'
Scenario: Sending Customer data from SAP via Async proxy to PI which is sent further to SalesForce system via SOAP webservice call.
When I am trying to Post data to the same webservice via SOAP UI it is working fine and data is getting updated in SalesForce system.
XPI inspector logs for the channel suggest the following:
client [103965] RequestImpl.initSslAttributes(): Initially sslAttributes = null
client [103965] RequestImpl.initSslAttributes(): Cannot find SSL headers in the request.
client [103965] RequestImpl.initSslAttributes(): No SSL attributes: not found in headers and not searched in FCA, because connection.isSecure() = false; sslAttributes = null
I have checked the following SAP Note and requested for updation of SSL icm parameters
891877 - Message-specific configuration of HTTP-Security
I checked the following discussions:
http://scn.sap.com/message/8910518#8910518
http://scn.sap.com/message/6244674#6244674
http://scn.sap.com/thread/2100000
http://scn.sap.com/thread/1632114
which are suggesting a different approach. Kindly suggest a way forward.
Thanks,
Vishwajeet

This is related network issue.
Did you do telnet in pi server with target system ip and port?
If you use https then you need to install certificates.
Check below threads
http://scn.sap.com/thread/190299
Unable to create socket error

Err "Couldn't retrieve binding for the given channelId" in receiver SOAP CC

Hello.
We have increase the support package level of our XI 3.0 system from level 17 to 23. After this "upgrade" all interfaces using a receiver SOAP channel communication are getting the next error:
SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldnt retrieve binding for the given channelId: Binding:CID=8cb6335a548730ea9ca27aaa78034109; at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBindingByChannelId(AbstractLookupManager.java:361) at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:421) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
We have done the next steps:
- Run SXI_CACHE and start a complete cache refresh,
- http://<Host>:<portNo.>/CPACache/refresh?mode=full
- Restart J2EE server.
The problem isn't solved.
any idea?

Probably you need to ask your BASIS team if they have done it or not.
Secondly you can just see if something has been done under SWCV SAP BASIS --- http://sap.com/xi/XI/System --- Adapter Metadata, just by oping any adapter and then by looking at Properties or Hisotry from menu "Adapter Metadata". Here you can see the date under "Changed on", so if this matches with your upgrade date then something has been done. But this check will not help you know about the SP level. So better to ask with BASIS.

Dynamic username and password for UsernameToken in Receiver Soap Adapter.

Hi All,
I am using AXIS Frame work for WS Security Authentication in Receiver SOAP channel. I deployed AXIS and used WSDoAllSender handler. I want to set the username and password parameters in the module dynamically. These have to be extracted from the payload.
kindly give me pointers to dynamically assign Username and Password.
Regards,
Saipriya.

continued from the previous entry
1. configure the following four handlers in the request chain
Handler dc
Handler xireq
Handler wssec
Handler trp
For the xireq and trp handler, you can use the default setting.
For the dc and wssec handlers, you use the following setting:
dc: handler.type = java:com.sap.aii.axis.xi.XI30DynamicConfigurationHandler
dc: key.1 = write http://sap.com/xi/axis username
dc: value.1 = user
wssec: handler.type = java:org.apache.ws.axis.security.WSDoAllSender
wssec: action = UsernameToken
wssec: passwordType = PasswordText
wssec: passwordCallbackClass = com.sap.aii.axis.security.DefaultPasswordCallbackHandler
2. Create an external password file with user password pairs. For example, if you have three users: orange, banana, and apple, with their passwords: orange, yellow, red, you create a file with content:
orange:orange
banana:yellow
apple:red
You name this file to ".password" and place it at the engine's classloader directory (e.g.,
/usr/sap/E07/JC90/j2ee/cluster/server0)
3. Prepare the input message containing the user name in the dynamic configuration header that looks like:
<ns3:DynamicConfiguration xmlns:ns3="http://sap.com/xi/XI/Message/30">
<ns3:Record name="username" namespace="http://sap.com/xi/axis">orange</ns3:Record>
</ns3:DynamicConfiguration>
The namespace and name must match the value used in the key.1 property of the dc handler. As long as they match, you can use any names.
In this example, the user name value "orange" will be extracted by the dc handler and inserted into the message context.
4. Send a test message.
Best regards, Yza

SOAP Channel - ADAPTER.HTTP_EXCEPTION

Hi,
I have a receiver SOAP Channel and when i tried sending messages.
Am getting an adapter exception.
Please guide if someone has faced with the same kind of error
Thanks
Sebin
The error response is pasted below.
<?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="HTTP">ADAPTER.HTTP_EXCEPTION</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>HTTP 401 Access Denied</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Sebin

hi
Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Description: The request requires user authentication
Possible Tips:
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
source :: /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
regards
Ramesh P

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.

Error in the SOAP Receiver communication channel

Hi ,
My scenario is RFC - to -SOAP (synchronous ) i have specified the TARGET URL inthe SOAP receiver comminication chanel.. but while testing the interface by providing the test data from R/3 .. I'm not getting any Respose.. ..
If I check in the SXMB_MONI in i'm getting the following message .. but the URL whicjh i provided that is fine.. but my doubt is through XI may be it's not able to connect the Target System... .. so, please suggest me...
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: www.webservicex.net</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
regards
Jain

By default, the SOAP adapter sends the SOAP message with the content type text/xml.
When you check "Do not use SOAP envelope", the default contnet type is application/xml.
You can change the content type like this: Go to the SOAP receiver communication channel module tab. Add the module "localejbs/AF_Modules/MessageTransformBean" before the standard module. Add the parameter name Transform.ContentType and value text/xml.
Check out this
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
One way of testing ur scenario
/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible
Also have a look here
SAP Note 856597
reward points if solution found helpfull
regards
chandrakanth

SSL in Soap receiver communication channel

Hi,
I have a webservices that works fine in Soap UI. The webservice provider uses the SSL, but works like a web browser, doesn´t need to install a certificate before access the webservice.
But when i try to use SAP PI using the soap receiver communication channel, the soap adater return the follow message:
"Peer certificate rejected by ChainVerifier"
I read some thing about using axis to solve this problem but I can´t find anything to configure this scenario.
If someone had this problem and solved it, i will apreciate the help.
Thanks
Fabricio

I Have 2 communication channel:
1) This works fine
Adapter Type: SOAP
Receiver
Transport Protocol: HTTP
Message Protocol: SOAP 1.1
Adapter Engine: Integration Server
Target URL: https://gw-homologa.serasa.com.br/wsacheixml/wsacheixml.asmx
SOAP Action: https://sitenet05.serasa.com.br/WSAcheiXML/WSAcheiXML/ConsultaAchei
2) This doesn´t work
Adapter Type: SOAP
Receiver
Transport Protocol: HTTP
Message Protocol: SOAP 1.1
Adapter Engine: Integration Server
Authentication: Basic
User/Password
Target URL: https://treina.spc.org.br/spc/remoting/ws/consulta/consultaWebService
SOAP Action: blank
Both are https and the certificate is sent at communication time (There isn´t a certificate to install in the Key Store in Visual Administrator)
I read that Axis manage this kind of integration with webservices, because the certificate must be installed at the moment of sending http request.
I don´t know why the first interface works fine an the another doesn´t work, then I´m trying with Axis.
In the SOAP UI both interfaces work fine.
Thanks

Content type in SOAP receiver communication channel

Hello,
so far I thought that the SOAP receiver adapter always sets the content type to text/xml. However now I found out the following strange thing:
If you check the option "without SOAP envelope" then the content type is application/xml. Is there any way to influence this as the receiver of the message only accepts text/xml.
Have you had any similar experience?

hi,
- open SOAP receiver communication channel - module tab
- add the module "localejbs/AF_Modules/MessageTransformBean" or AF_Modules/MessageTransformBean" before the standard SOAP module
- add the parameter = Transform.ContentType with value = text/xml
I'm just not sure if you need to add value = text/xml or "text/xml" so try the second one if the first one will not work
does it work now?
Regards,
Michal Krawczyk

Receiver SOAP Communication Channel Error

Hi,
I am trying to post a file to a WebService but facing the below error in the communication channel :
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> Object variable or With block variable not set.
Has anyone encountered such an error?
Please let me know.
Regards,
Anuradha.

Hi,
First of all check the URL in your receiver SOAP adapter. The error comes from the web service server. It says that the request message is wrong.
1.fill field SOAPAction in the receiver soap adapter
2.fPlease find the related information here
http://help.sap.com/saphelp_nw2004s/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
Please check this one also:
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
There are multiple soap actions listed there.
Regards,
Divya

Receiver SOAP Comm Channel Settings with TServerLocation

Hello All,
We are working on using Dynamic Configuration of Receiver SOAP. We are using the following scenario
*Can anyone please guide us on Receiver SOAP Comm Channel settings*
1) Value to be used in Target URL
Which parameters need to be checked ?
Currently we are getting the following error
<?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>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.af.sdk.xi.util.URI$MalformedURIException: no scheme</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Truly apprecaite your help
Thanks.
Kiran

Hello
Can anyone guide me on the settings in receiver Comm Channel which uses dynamic configuration in TServerLocation ?
Thanks.
Kiran

Creating SOAP Receiver comm.channel for axis web service

Hi,
I created Soap Receiver comm. channel fro Axis web service like below:
*Target URL* : http://<IP>:<Port>/<x>/service
*User:* <user>
*Password :* <password>
*SOAP Action:* <target namespace>/method
when i drive PI Message that use Soap Receiver it get error below
I do same method for .Net web service, it runs properly.
How can i solve this problem?
Error
<?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>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B3004965647F340C997B5F2CC9EA7E22 Software Component 4CF44F80503211DEB2A0D3F40A194B29</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B3004965647F340C997B5F2CC9EA7E22 Software Component 4CF44F80503211DEB2A0D3F40A194B29</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi,
I did all but nothing changed?
I have doubt about axis side. Because respose like below.
<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>
May be Soap Receiver setting for axis web service must be different.
Thanks.

Receiver SOAP Communication channel -- Target URL

Hi Experts,
Can anyone provide some inputs for my below question?
How the receiver SOAP Communication channel internally calls the Target URL?
What is the internal process behind this call?
I would really appreciate you all if could provide answers.
Thanks & Regards,
Prabu Muthu

Hi...
To be able to send SOAP messages from the Integration Server/PCK to remote clients or Web service servers, you must first configure the receiver SOAP adapter. The receiver adapter supports system acknowledgments but not application acknowledgments
Find the below link .
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Regards,
Leela

Receiver Soap channel

Similar Messages

Maybe you are looking for