SOAP with Sender agreement

Hi all,
Is it possible to send a SOAP message directly to Integration Engine skipping AE.
If yes, then what will be the URL format for IE.
As per my understanding , the URL for Adapter Engine is :
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Thanks
Soumya

Here you find the answer:
Using the SOAP inbound channel of the Integration Engine
A sender agreement is not needed.

Similar Messages

Problem with Sender Agreement for EDI File to Idoc scenario

I'm configuring PI for EDI with Seeburger Adapter (Calling as a Module) and I'm having an issue with the Sender Agreement using File Adapter.
Process used is File to IDOC. EDI data will be picked up from VAN (Using existing FTP process rather than using Seeburger FTP) and stored in a folder which is being accessed by PI to send to R/3 to create orders.
All my inbound EDI will be stored in same folder which should be picked up by XI and distribute the same depending upon the respective scenario's in ID and respective mapping/config in IR.
The whole process IR & ID works fine and also creates Idoc in R/3, if I configure for one customer for EDI 850, but when I try to configure for second customer for same EDI 850 having same ANSIX12 version (V4010) as previous customer, I get stuck at the Sender Agreement part for this second customer because I use the same CC for File read for both the customers (Scenarios) and since there is a limitation with File Adapter "sender channel must not be assigned to more than one sender agreement ".
How can I create the Sender Agreement using the same CC for my other scenario?
I tried creating multiple CC for different scenario but when I place a test file for customer A, I see that its being picked up by both CC's.
Pl Advise.
Thanks!
PSR

You need to configure splitter as module in sender file adapter (classifier->bic->splitter) as well as define a message splitter(with partner number and Seeburger mapping) in Seeburger workbench.
Thank you for the reply Aamir,
Do you have any document which can guide me through the process?
Does Seeburger Workbench play any role here? because I'm not using See FTP adapter to connect to my VAN. We get the data from the VAN using FTP process but not using See FTP. I'm using BIC to generate an XSD and SDA file, rest everything is in XI using File to idoc and IDOC to file process.
Thx
PSR

Problem with sender agreement

Hi,
We are trying to send a file from the file system (using file channel) to XI. However we are getting the error as " No suitable sender agreement" found error in the communication channel monitoring in RWB. However the sender agreement is very much there and is activated also.
Any idea on this ?
Regards
Ganesh

Hi,
try creating your scenario with a integration directory wizard
it will make sure that everything is correct
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Problem with sender agreement in rfc

My scenary is RFC -> XI -> FILE.
I created one message interface with atribute asyncronous and output message the rfc.
I created one interface mapping and message mapping
In integration directory I created one chanel of comunication,the receiver determination, the interface determination, the receiver agreement and the sender agreement. In the sender agreement in interface I put the same name of message interface and then I activated all.
When i execute the rfc i have one dump. This dump is "senderAgreement not found: lookup of binding via CPA-cache". But i declarated and activated the sender agreement.
Somebody knows the problem.
Thank's for all.

Hi Antonio,
A few things that you should know:
1) You need not create a message interface for RFC, as RFC iself is an interface.
2) You need to create one inbound message interface for file message.
3) You will need two message mapping, one for request message and one for response message in case yours is a synchronous scenario. But only one message mapping (request) in case of asynchronous scenario.
4)One interface mapping both for sync and async scenario.
In Integration Directory:
1) 2 communication channels: sender RFC and receiver File.
2) 1 Receiver determination, interface determination and sender aggrement.
Regards,
Ashish

No suitable sender agreement found !!!

Hi,
I have created a sender file adapter and associated it with sender agreement. Now Im getting the error "No suitable sender agreement found".. I have activated all the associated objects and did complete cache refresh using SXI_CACHE..
Any thoughts..
- Ramani

Hi,
Performed below steps:
1. Checked all the MI, namespaces,etc in Sender Agreement.. Sender File Adapter.
2. The Sender File Adapter is activated and associated with Sender Agreement.
3. Did Complete refresh using SXI_CACHE.
Still I can see the error message "No suitable sender agreement found" under the Comm Channel.
Thanks
Ramani

How to use HTTPS with sender SOAP Adapter

Hi,
I am implementing a synchronous SOAP- proxy scenario and on the sender communication channel I have to use the Http Security Level as "HTTPS with client Authentication".
Where from I get the certificates to be used in sender Agreement.
Please give me a step by step approach to achieve this.
Regards,
Nitin

Nitin,
Kindly go through the below links ...
http://help.sap.com/saphelp_nw04/helpdata/en/1f/7e2441509fa831e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm
Also, make a search on the SDN as this question has been answered many a times on the forum.
Regards,
Neetesh

Problems using access control in sender agreement for SOAP adapter 7.1

I am trying to use Access Control Lists to restrict user access to web services/interfaces which are exposed via PI. This can be configured via the Integration Builder Directory using the u201CAssigned Usersu201D tab of both Communication Components (Business System) and Sender Agreements.
The configuration is via the above mentioned components. However, I understand that itu2019s the adapters which at runtime are responsible for actually applying these checks.
I have been having problems getting the access control to work using a setup involving a SOAP adapter of type SAP BASIS 7.10.
The symptom of the problem is that although the access control works as expected at the Business System level, any settings at the Sender Agreement level appear to have absolutely no effect whatsoever.
I have confirmed that I have no problems if I use an adapter of type SAP BASIS 7.00. However, I really need to get this working on 7.1.
I have looked on the SAP support portal but can not find any notes that relate to this.
Has anyone else had a similar problem? And have you found a fix for it?
Any suggestions would be welcome.
Edited by: Malcolm Dingle on Jun 17, 2009 1:08 PM

Hi Shai,
Please have a look at the following link and see if it helps you .
It deals with SOAP adapter installation and activation
Re: SOAP adapter installation and activation
Best Regards
Edited by: Prakash Bhatia on May 8, 2009 11:51 AM

Certificate based authentication with sender SOAP adapter. Please help!

Hi Experts,
I have a scenario where first a .Net application makes a webservice call to XI via SOAP Adapter. Then the input from the .Net application is sent to the R/3 system via RFC adapter.
.Net --->SOAP -
>XI -
>RFC -
R/3 System
Now as per client requirement I have to implement certificate based authentication in the sender side for the webservice call. In this case the .Net application is the "client" and XI is the "server". In other words the client has to be authenticated by XI server. In order to accomplish this I have setup the security level in the SOAP sender channel as "HTTPS with client authentication". Additionally I have assigned a .Net userid in the sender agreement under "Assigned users" tab.
I have also installed the SSL certificate in the client side. Then generated the public key and loaded it into the XI server's keystore.
When I test the webservice via SOAPUI tool I am always getting the "401 Unauthorized" error. However if I give the userid/password for XI login in the properties option in the SOAPUI tool then it works fine. But my understanding is that in certificate based authentication, the authentication should happen based on the certificate and hence there is no need for the user to enter userid/password. Is my understanding correct? How to exactly test certificate based authentication?
Am I missing any steps for certificate based authentication?
Please help
Thanks
Gopal
Edited by: gopalkrishna baliga on Feb 5, 2008 10:51 AM

Hi!
Although soapUI is a very goot SOAP testing tool, you can't test certificate based authentication with it. There is no way (since I know) how to import certificat into soapUI.
So, try to find other tool, which can use certificates or tey it directly with the sender system.
Peter

Issue with WSDL created for sender agreement

Hi,
Can you please help me why I am getting the erroe with WSDL that has been created from directory Sener agreement in PI 7.1 EHP1?
My interface is a SOAP to file ASYNC scenario and we have been given 5 XSDs that are referencing one each other ,5 XSDs are imported successfully and referenced properly,no errors/issues found.
Created all ESr and directory objects and I tried creating WSDL from sender agreement for my Source/outbound inteface that is created with XSDs in ESR.
When I try to import WSDL into SOPA UI to validate ,the import process stuck for ever while trying to import "http://www.w3.org/2001/xml.xsd" and finally throws me error.
After that I tried importing WSDL created in Directory into AltovaXML spy to created the webservice request,I am getting the following error""invalid XML Schema:"xml:lang" is already declared in the schema dcument C:|..my WSDL.
Even our partner who wants to make Webservice calls using this WSDL,they are not able to develop their Webservices they are getting errors something related to schema not found /not defined etc.
Please let me know,what might be the issue?I verified several times with my XSD imports and referencing properly and configuration objects.
Thank you for your help in advance.
Regards,
Prem

Hi Mark,
I am not getting issue while displaying/Exporting as WSDL in ESR.I am getting issue while trying import WSDL that is generated out of Service Interface into SOAP UI or Altova XML Spy.
I don't think PI created the WSDl out of W3 standards.
This is the error I am getting in XML Spy:
File C:\Documents and Settings\Prem\Desktop\SI_XYZ_O.wsdl is not valid
Invalid XML schema: ''xml:lang' is already declared.
Error location: schema / attribute++
and in SOAP UI:It is trying to import the WSDL and it stuck for ever while trying to import http://www.w3.org/2001/xml.xsd and never imprts the WSDL into SOAP UI project.
Please let me know,if you have any ideas.
Thank you,
Prem.

Why we do not need sender agreement for Mail and SOAP adapter

Hi SDN,
I know, we do not need sender agreement for IDOC ,HTTP,XI adapters. As these three adapters will run in Integration engine of the abap stack.
In our scenario if sender is other than IDOC or HTTP or XI .
By Refering Sivamni's blog.
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
message will be pickedup by communication channel with the help of sender agreement and prepare XI message header by performing cpa cache lookup. then message will go to module processor etc.
In our scenario if sender is IDOC or HTTP or XI .
As these 3 adapters are run in Integration engine.
Doubt 1:
how the integration engine will create the xi message header like sender interface sender system name etc...
Doubt 2:
I believe SOAP and mail adapter will run in adapter engine.but i came to know that we do not need sender agreement and sender comm channel for these two adapters too...then how the XI message header will create...
Please do correct me if i am wrong
and throw some light on the same..
Appreciate your help....
Regards,
Reehan.

Reehan,
Thanks for pointing me to that link. Guess I was wrong .,But,let me try to put to you why you need a sender agreement for a Sender SOAP Adapter,
1. In the sender SOAP adapter , the Sender Interface and the Interface Namespace as provided in the fields Default Interface Name and InterfaceNamespace. The Name of the Sender Service is provided in the WSDL when you ceate the WSDL in the Integration Directory. So, as all details are available in either the Sender SOAP adapter or in the WSDL url you do not need a Sender Agreement. It is not obligatory but you can always create the Sender Agreement.
2. For the mail adapter , if you select the option XIPAYLOAD, you will have the option to mention the Interface Name and Interface Namespace under XI Parameters and so in this case as once again the details provided in the sender agreement are available in the Sender Adapter itself the sender agreement is not needed for the mail adapter when you have select option XIPAYLOAD.
If you have selected XIALL then you need a sender agreement.
Regards
Bhavesh

SOAP Axis sender with CSV file attachment

Hi Experts,
I have a requirement where I receive a CSV file attachment from a Web Service post ( i.e a SOAP sender with attachment). I decided to use SOAP with Servlet(Axis) protocol, since standard SOAP sender does not allow modules to be used.
I am able to test this interface through SOAPUI with attachment to the point where I can get the attachment payload as my main payload in IE, but it fails in mapping since CSV needs to be converted to XML. I have following queries for proceeding ahead with this scenario:
1. How do I convert the CSV attachment to XML inorder for mapping to be used in IE. Is there a standard axis handler available for this ???? Also where should this handler be called in the sequence of Axis modules ???
2. Can I use MessageTransformationBean for converting plain to XML ??? If yes where should this module be called in the sequence of Axis modules. I tried using this module between the CallSapAdapter and the first AdapterBean but it returns exception in SOAPUI saying " Messaging exception: No Main"
3. Is there a blog available which illustrates about using additional modules/handlers in Axis. I have had a look at the FAQ note of Axis but it just gives the overview.
Thanks.
Siddhesh S.Tawate

Solved :).
1     AF_Adapters/axis/HandlerBean                     Local Enterprise Bean                              xireq
2     AF_Adapters/axis/AFAdapterBean                     Local Enterprise Bean                              afreq
3     localejbs/AF_Modules/MessageTransformBean    Local Enterprise Bean                     Plain2XML
4     CallSapAdapter                                          Local Enterprise Bean                              sap
5     AF_Adapters/axis/AFAdapterBean                    Local Enterprise Bean                             afresp
6     AF_Adapters/axis/HandlerBean                    Local Enterprise Bean                             xires
Above sequence worked. I guess I was missing some parameter in content conversion earlier.
Thanks.

BPM Send Step with acknowledgment: ID: sender agreement?

Hello everybody,
I have a send step in BPM and I expect a acknowledgement from the receiver.
Do I have to configure a sender agreement?
Thanks a lot
Regards Mario

mario,
I have tried to use a Sen Synchronous Step to a JDBC adapter from a BPM and it works fine.
After changing the send step in BPM from async to sync with acknowledgement, I get not response message.
When you select MODE as SEND SYNCHRONOUS in your Send Step, there is no option to Select ACKNOWLEDGEMENT.
When you select the MODE as SEND ASYNCHRNOUS , you can have acknowledgements.
But, as you are using a RECEIVER JDBC adapter , you need to have a SEND SYNCHRNOUS step that will get the response back from the JDBC adapter. This response will double up as Acknowledgemet.
You can surround this Send Synchrnous Step with an Exceptuion Handler to handle any exception that might occur.
Regards,
Bhavesh

Sending SOAP with null/nil problems

Hi,
we are strungling with sending SOAP messages to an server. With a standalone JAVA-Script we were able to send a SOAP-Message to the server.
When this worked, we wanted to change the script so it could be called from a PL/SQL Function. We intercepted the messages and have discovered differences for the null-value. When we send it from the client it sends NIL. When sending from the Database (Oracle (9IAS R2)) it sends NULL. See examples below:
Client:
<dateCardDistribution xsi:type="xsd:dateTime" xsi:nil="true"/>
Database:
<dateCardDistribution xsi:type="xsd:dateTime" xsi:null="true"/>
Has anyone seen this before?
Thanks in advance, Roel.

IMHO, the implementation that is sending the NULL has not been updated to reflect new xml schema standard. According to XML schema, nodes that can be "empty" i.e. possess no value for business data need to be marked as 'nil'. If memory serves me right, it used to be 'null' in "old" schema.
You should be able to confirm this from w3c.org
Best Regards

SOAP sender agreement

Hi All,
In case of SOAP scenario's,
The sender agreement contains 2 options here.
1.Assigned Users 2. Propogate Principal.
Are these 2 are related/dependent each other?
Regards,
Naresh

Hi!
Prinicipal Propagation::
In the Integration Directory, sender and receiver agreements can be configured to propagate user identities. The Propagate principal checkbox is available for this purpose. Since one sender agreement and one receiver agreement is used for each message to be processed, the checkbox must be selected in both the corresponding sender agreement and the corresponding receiver agreement when principal propagation is to be active for this message.
[http://help.sap.com/saphelp_nw70/helpdata/EN/45/341a19e1a21ba3e10000000a155369/frameset.htm]
[http://help.sap.com/saphelp_nw70/helpdata/EN/45/341a19e1a21ba3e10000000a155369/content.htm]
[http://help.sap.com/saphelp_nw70/helpdata/EN/45/0f16bef65c7249e10000000a155369/frameset.htm]
Assigned Users::
[http://help.sap.com/saphelp_nw70/helpdata/EN/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm]
For sender services of type Business Service or Business System, you can now restrict access to the runtime environment to particular (service) users. An authorization check is run at runtime to ensure that messages that have the particular service entered as the sender in the message header can only be executed on the Integration Server or in the Adapter Engine by the specified users.
You specify the access control when you configure the corresponding (sender) service in the Integration Directory.
[http://help.sap.com/saphelp_nw70/helpdata/EN/42/f3d07f074e1bcae10000000a11466f/content.htm]
In addition, you can restrict the access control to a particular interface of the sender. You specify the authorized users in the configuration of the relevant sender agreement, which contains the interface in the object key.
This function was specially designed for the configuration of business-to-business processes. You and your external business partner agree on a special user to be used for communication by using SAP Exchange Infrastructure. You assign all services that the external business partner uses to send messages to your Integration Server to this user. The external business partner must include this user when configuring their receiver channels (or when configuring their HTTP destinations).
Regards::
Amar Srinivas Eli

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

SOAP with Sender agreement

Similar Messages

Maybe you are looking for