Authentication of SOAP Sender Communication

Dear XI gurus,
I have scenario , where i am exposing an Message interface as webservice from XI, which will be consumed by a web portal and send the messages to XI. When sending messages to XI, the XI SOAP Sender needs an authentication with user id and password. My problem is i want to disable this authentication. Because when sending the message to XI from portal., they dont have provision to suppy user id and password. Can anybody advice how to disable the authenticaion for an XI exposed webservice? i.e i want to send the messages to XI exposed webservice with out userd id and password. or else there is any other alternate to give the user id and password alond with the SOAP URL.
Regards
Vijayanand Poreddy

Hi,
Please see the below links so that you can have clear Idea..
/people/saravanakumar.kuppusamy2/blog/2005/02/07/interfacing-to-xi-from-webdynpro
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/integrating%20web%20dynpro%20and%20sap%20xi%20using%20jaxb%20part%20ii.article
Thanks
Vikranth

Similar Messages

HTTPS with Client Authentication in SOAP sender Adapter

Hi All,
In SOAP Sender communication channel. When I generate WSDL with HTTP Security Level = HTTP: it works when third party tries to send data to XIwebservice.
But when I tried with HTTPS with Client Authentication option its giving error
InfoPath either cannot connect to the data source, the service has timed out, or the server has an invalid certificate.
Please guide how to use HTTPS with Client Authentication option, and what all configuration need to apply in XI & in third party to use this.
Regards

Rohan,
With spy you can trace the entire route, since you are using client authentication using certificate, it would be a better option to verify with the certificate.
You also have the option of using a username/pwd combo though that is not advocated as it lowers security levels and is permeable to passive sniffing.
So the answer to your question is yes, after importing the certificate with sender and third party reciever a test would reveal the complete scenario along with any issues that you could encounter..
Regards
Ravi Raman

Using common SOAP Sender Communication Channel.

Hi,
Env: PI 7.1
Scenario: Same SOAP Sender communication channel is used in more than one scenario.
Properties "Use Encoded Headers" and "Use Query Strings" are checked.
Problem: SOAP channel is getting binded with the first interface/call. Subsequent calls from other interface proxies fails. It always shows the interface which used this channel for the first time.
My aim is to use the common channel in multiple scenarios and do not want to create separate channel for each.
This was working fine in PI 7.0.
Please help.

A workaround would be creating multiple sender agreements using the same channel. For this while creating the sender agreement, use the option "Sender uses virtual receiver". This was u may use same set of sender service and sender interface with same channel.
Regards,
Prateek

HTTPS with Client Authentication in SOAP sender Adapter --SSL

We have an interface SOAP to file..which was working fine...now we recently switched to F5 load balancer and hence we were asked to chnage the settings in Communication channel.
After changing the communication channel to u201CHTTPS with Client authenticationu201D..client trggerd the some data but nothing seems to be coming in PI..
No trace in communication channel either.where else can we check for the incoming data ?
Is there any other setting required? why the data s not coming to PI?
Regards

Hi,
here is the flow: Bank>F5-->PI.
when the Bank client send the message
they are getting the message below. Could you please tell me what could be the reason?
<?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.aii.af.ra.ms.api.DeliveryException: Invalid SSL message, peer seems to be talking plain!</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
regards

Error in SOAP Sender Communication Channel

Hello Gurus,
I am trying for a SOAP (Axis) -> PI -> IDOC scenario and getting an error while sending message to SOAP Channel.
Message structure used
<?xml version="1.0" encoding="UTF-8"?>
<MaterialData>
<field1>value</field1>
more fields
</MaterialData>
Basically a XML message.
I am getting below error message for Axis (channel monitoring):
MP: exception caught with cause org.xml.sax.SAXException: Bad envelope tag: MaterialData
Can you please let me know what should be the message format when testing Axis? I do not intend to use any SOAP envelope.
I have already referred: Re: SAP PI 7.0 Receiver SOAP Axis (Bad envelope tag: html)
Please help.
Thank you!

Hello,
Can you please let me know what should be the message format when testing Axis? I do not intend to use any SOAP envelope.
Correct me if I'm wrong, but I think you will only be able to plain message to the Axis sender when using REST. See SAP Note 1039369 FAQ XI Axis Adapter, under Sender Adapter General Question 35.
35. Can I post a plain no-soap request (REST) to the sender adapter servlet?
Yes. You need to include a query parameter rest in the request URL, as http://host:port/XIAxisAdapter/MessageServlet?...&rest. For the availability of this feature, refer to Note 1448849.
All the other messages require a SOAP Envelope.
Hope this helps,
Mark

Soap sender communication channel is not shown in RWB

Dear Experts,
We had a recent installation of Xi and after that i m attemting a Soap to rfc syn scenario and i have created both the soap and rfc communication channel on a abap business system.
and now im not able to see the Soap communication channel in the RWB .even the soap icon is shown as disable..
can u tell the reason for this.Or is it bcos i have not sent any soap request to it.
All ur efforts will be greatly respected.
Thx
jeevan

hai prabhu....
thxs for the hint,,,,.
i did that and its throwing the following error...
pls help
<?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[
java.lang.Exception: invalid channel (party:service:channel) = <null>
 at com.sap.aii.af.mp.soap.web.HelperServlet.processFindChannel(HelperServlet.java:363)
 at com.sap.aii.af.mp.soap.web.HelperServlet.doGet(HelperServlet.java:125)
 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:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
]]>
</text>
</s:SystemError>
</detail>
</SOAP:Fault>

XIProxy:PARSE_APPLICATION_DATA , error in soap sender communication channel

HI
I am having soap toABAP proxy synchronous interface , when i test from soap UI tool i am getting the below errro . can any body help me with this error
<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>ADAPTER.JAVA_EXCEPTION</code>
 <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
 at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1178)
regards
sandeep
Edited by: pendyalas on Jul 27, 2011 5:01 PM

Hello,
can you check the message format defined in repository.
Regards
Vivek

Anonymous authentication requests via SOAP Sender adapter?

Hi,
Can someone please tell me whether it is possible to call the SOAP Sender adapter anonymously?
We can set user credentials for the receiver system adapter but looking at the options in the SOAP Sender communication channel I can't see how it is possible to send messages though SAP PI without a user who has authorisations to process messages.
Any advice greatly appreciated.
Thanks,
Alan

can't see how it is possible to send messages though SAP PI without a user who has authorisations to process messages.
The source system needs to use a user-id to send message to XI/ PI via SOAP.
If you do not want to use any authorization there is a way to switch off the authentication for the entire SOAP adapter (i.e. for all the SOAP scenarios)....not advisable.
This method was actually described in a discussion ages back
Regards,
Abhishek.

Enabling HTTPS level authentication in SOAP adapter (PI 7.1)

Hi,
I am using SOAP to SOAP scenario using HTTPS level authentication in PI 7.11
As per the SAP Note https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=891877
We have enabled HTTPS level authentication in sender communication channel using SOAP adapter (version 7.0).
But We are not able to have the HTTPS level authentication option in sender communication channel using SOAP adapter (version 7.1) while selecting the adapter type.
Please suggest on this

Hello Gabriel,
You are right, that option is still available in PI 7.1
http://help.sap.com/saphelp_nwpi71/helpdata/EN/fc/5ad93f130f9215e10000000a155106/frameset.htm
But disappeared in PI 7.11
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/3555240bea31c3e10000000a42189d/frameset.htm
The closest seems to be under Security Profile S/MIME. And when you use the sender cc in sender agreement, you are given the choice for validation/decryption/decryption and validation/validation and decryption.
Hope this helps,
Mark

Variable Transport Binding - Soap Sender

Hello all,
I'm trying to retrieve a parameter from the HTTP header of a SOAP request.
I have created a SOAP sender communication channel, checked "Set Adapter-Specific Message Attributes" and "Variable Transport Binding", and entered the name of the parameter in Variable Header (XHeaderName1).
When I send the SOAP request, DynamicConfiguration exists with all standard parameters, but there is no XHeaderName1...
If I try the same with sender HTTP adapter, it works fine.
In the other way, if the dynamic configuration parameter XHeaderName1 already exists, and I try to add it in a HTTP header parameter in a receiver SOAP CC, that works.
Does somebody know why this doesn't work in the sender one?
Thanks,
Greg
PS: I'm using PI7.0 SP14

Hello,
I can see in dynamic configuration, with the namespace http://sap.com/xi/XI/System/SOAP, the standard HTTP parameters like SServerHost, SRemoteUser, etc...
But if I add a HTTP header parameter in the SOAP request, and I try to retrieve it with the SOAP sender CC, the parameter is not added in the dynamic configuration. If the name of the added HTTP header parameter is "TestParam", I put "TestParam" in the XHeaderName1 field of the sender CC, but the value is not added in the dynamic configuration. This is my problem.
Thanks,
Greg

SAP PI 7.1 SOAP sender 500 internal server error

Hello!
We would like to receive messages from our business partner. As the partner sends EDIFACT we have to use the conversion from EDIFACT-text to EDIFACT-xml. That's why we have to use SOAP instead of plain HTTP.
As the partner already sent messages over X.400 we just added a SOAP communication channel and used this channel in the sender agreement instead of the X.400 communication channel.
We sent the following link to the customer:
http://<server>:<j2ee port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<SOAP sender communication channel>
One question: is the <service> the communication component used for the partner?
At the moment the partner receives a 500 error message. Due to our network partner the message reaches the PI system.
Due to the information I found that also a message parsing error can cause a 500 error message I would like to add the processing sequence:
Does anyone have an idea how to solve this problem?
Thanks a lot!
Regards
Christian

Hi Christian
You can refer to the following SAP Library link on how to configure the SOAP sender.
Configuring the Sender SOAP Adapter - Configuring the SOAP Adapter in the Integration Directory/PCK - SAP Library
For the URL, the <service> is the Communication Component that the SOAP channel belongs to.
Using the example below, the value would be P_B2B_:BC_:CC_S_SOAP_
Actually SAP recommends a new alternative for the URL. If you scroll right to the end of the library link above.
You have configured the sender SOAP adapter. You can trigger a call to the sender SOAP adapter using either of the following URLs. However, SAP recommends you to use the second option.
http://hostname:portname/XISOAPAdapter/MessageServlet?channel=partyname:service name:channelnameIf you have not created a party, enter channel=servicename:channelname.
http://hostname:port name/XISOAPAdapter/MessageServlet?senderParty=name of the sender party<&senderService>=name of the sender service<&interface>=name of the interface<&receiverParty>=name of the receiver party<&receiverService>=name of the receiver service<&interfaceNamespace>=name of the interface namespace
You can get this by generating the WSDL from the Sender Agreement object (Sender Agreement -> Display WSDL). The generated URL will be at the last section of the WSDL.
Also, please note that modules cannot be added to the SOAP sender adapter, also mentioned in the link.
You cannot add your own modules to this adapter.
An alternative would be to receive the EDIFACT Flat file as it is, and write it to at temporary File/FTP location. Then have a second channel pick it up, you can configure the second channel with module to convert it to EDIFACT XML.
Lastly, regarding the issue about the partner getting HTTP 500 error. Please check if you are able to see any error logs in the communication channel. It might give you some pointers as to what might be wrong - invalid sender agreement, etc, etc.
Rgds
Eng Swee

SOAP Sender to RFC Scenario WSDL File

Hi,
I am working on SOAP -> PI -> RFC Scenario. I generated WSDL from sender agreement and gave to the client that can consumed by the third party system. But client is not ready to consume the WSDL. He provided WSDL and asking me to use that. Could you please suggest whether WSDL given by the client can be used in SOAP -> PI -> RFC Scenario. If it is possible, could you please provide steps how it can be done?
Thank you.
Regards,
Cdr.

Thank you Hareesh & Divya,
When we generate WSDL from PI, it gives soap action and soap address location based on the interface we use for SOAP -> PI -> RFC.
When we import WSDL given by the client as external definition, we get messages(Structures). But where do we pass the soap action or address location. I do not see any option in the soap sender communication channel. I am not visualize the link.
Can somebody share their knowledge if they have done in this way.
Thank you.
Regards,
Cdr.

Error in SOAP sender CC. Channel stopped by administrative task.

I am getting an error in my SOAP sender communication chanel as follows;
com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Channel stopped by administrative task.
The channel is Active but still gets the same error. Any help would be appriciated.

RWB ---> Component Monitoring ---> Adapter Engine ---> Communication Channel Monitoring ---> Choose your CC and check its properties....check if it shows Channel Stopped...if yes then restart it.
Channel should be Active in ID and Started in RWB to work properly.
Regards,
Abhishek.

SOAP Sender URL for Default XI parameters

Hi,
In my scenario i want to use same SOAP sender communication channel for many webservices.So i selected USE QUERY STRING OPTION . But i am not sure about the parameters in URL. I referred SOAP Adapter how to guide. it was helpful to some extent but would be grt if u guyz confirm the URLfor sending the different default XI Interface parameters .https://server:port/XISOAPAdapter/MessageServlet?channel=:<sender service>r:<sender comm channel>&version=3.0&Interface=<????>
Basically i do not know what shud be given for interface name
Regards
Vish

Hi Viswanath -
You're on the right track for your purpose of using one channel and dynamically setting the interface name. The SOAP FAQ Note 856597 spells it out well:
 "Q: Can I set the interface name dynamically from the client?
 Yes. You can overwrite these XI parameters from the client. To
 activate this overwriting mode, you need to turn on option "Use
 Encoded Header" and "Use Query String" in the channel. Then your
 client can append the interface name using parameter Interface.
 For example, interface namespace http://sap.com/test and
 interface Test can be represented by the url-encoded form of
 http://sap.com/test^Test as in
 #&version=3.0&Interface=http%3A%2F%2Fsap.com%2Ftest%5ETest"
I see you already have some of this. Don't forget to check both the "Use Encoded Header" as well as the "Use Query String" option.
>>>>In that case whatz the relevance of namespace in the URL. You mean we can ignore that .Pls advice
When you dynamically set the interface name, yes, you need both the interface name and the namespace. All this information (including the namespace) is needed for the receiver determination step once it reaches XI.
If you're having trouble with the URL, generate a WSDL using the "Define Web Service" option in the Int. Directory with the relevant interface information.
Jin

"NO_RECEIVER_CASE_BE" error with SOAP Sender assigned to a Business Service

Hi all,
we have a strange error with XI3.0
We created a configuration scenario where the initial step is done by a Business System, that uses a SOAP Sender communication channel to send its request. And this works great when testing it with XMLSpy.
But we then needed to shift from a Business System to a Business Service, as the machine sending the SOAP request changed and was not anymore part of the landscape, but elsewhere.
Hence we recreated a SOAP sender which we assigned to this new business service, doing absolutely the same configuration work as for the other soap sender of the former business system.
Yet when testing it through XMLSpy, we everytime get a NO_RECEIVER_CASE_BE error back, stating that "No receiver could be determined". Yet when checking in sxi_cache, receiver determination is clearly there. All the blogs I went into are only refering to Business System for a SOAP sender, so I was wondering if any of you already managed to assign a SOAP sender to a business Service.
Regards,
Cedric

hi,
so you sue SOAP to make a query ? (sync)
or to send the data to XI ? (async)?
if async then make sure
you use Quality of Service other then BE
in your soap adapter channel
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Authentication of SOAP Sender Communication

Similar Messages

Maybe you are looking for