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

Similar Messages

PI 7.1 URL for SOAP Sender incorrect

Hello experts,
I have a SOAP sender agreement and generated the WSDL from the "Display WSDL..." option on ID, now the problem is that the soap address tags for HTTP_Port and HTTPS_Port are being created with the hostname of my PI server without domain, but all other url's in the wsdl file and including the WSDL URL of the wsdl file have the correct server name and domain, so when somebody gets the wsdl file from the file location and upload it to even Eclipse or just consume it from any other composite cannot reach the service exposed in PI, so I was wondering if any of you experts can help me with where can I find the parameters that Integration Directory use to create the soap address urls fro HTTP and HTTPS automatically, I've checked all the exchange profile and all the reference to server have the domain, I'm not a basis consultant and our basis team cannot find the problem, if anyone can help me with where can I find these parameters would be really appreciated, thanks in advance for your answers.
Rergards,
Julio

HI JULIO,
SOAP sender agreement and generated the WSDL from the "Display WSDL..." option on ID
Q. HOW TO CHECK THE JTTP SENDER SIDE URL........WE HAVE ONE OPTION IN ID.....CHECK THE BELOW PROCESS FOR REF.....
ID-->TOOLS>DEFINE WEB DERVER->CONTINUE->PROPOS URL (CLICK)>CONTUNUE-->SELECT THE INTERFACE
NAME (NAME NAME SPACE SOFTWARE COMPONENT NAME)---->CONTINUE --->(THEN SERVICE , INTERFACE
NAME ,INTERFACE NAME SPACE)-->CONTINUE->OVERVIEW
THIS IS THE PROCESS TO GET THE SENDER SIDER URL
REGARDS,
KESAVA

Sender Agreement endpoints URL - is it configurable?

Hello All
I have two PI servers: DEV and QA. DEV works ok, but after transporting objects from DEV I've noticed, that SOAP Sender Agreement gives WSDL which contains service endpoint url from DEV system. Main WSDL Url is correct - from QA.
Are those endpoinds somehow configurable? How to make this WSDL correct, that QA serves those services?
TIA
Best Regards
Maciej

Hi Maciej,
answering your question indirectly
it's not PI that you're looking for right now but your sender application
it's the sender application that needs to be able to determine the URL (server) correctly (for dev,qa, prd)
as you only generate a proxy for it once (on the dev system), right ?
so it should be possible to change it in the sender app and not in the receiver I believe - at least that's how it works in simplest cases (no SR etc.)
Regards,
Michal Krawczyk

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

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 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.

Error while publishing Service from Sender Agreement

Hello Experts,
I have Enterprise Service Scenario in which i am publishing Enterprise Service from Sender agreement (using SOAP Sender adapter).
When i am trying to publish this Enterprise Service i am getting below Error.
Adapter Engine XXXX for communication channel XXXX not registered in SLD.
Can someone please help me solve this error?
Thanks,
Hetal

Hi.
Pleas check the following threads
how to check adapter engine was registered in SLD or not?
No Adapter Registered for this channel
Regards
Lucho.

Sender agreement not updated in XI cache after commit

Hi all,
somehow none of my created sender agreements appears in the XI cache after commit. I also did a complete refresh of the XI chache.
Any ideas?
Thanks!
Denis

Hmm,
I have created sender agreements for SOAP channels, this would explain why I could not see the agreements...
Actually I am wondering why the 'test configuration' tool in the ID brings up an 'java.io.IOException' in the receiver determination. Prior to that the sender agreement lookup fails. So I thought it's the XI Cache...
I restarted the J2EE engine but the problem remains.
Any other ideas?
Thanks so far!

What's the usage for WSDL of sender agreement?

Hi gurus,
Our scenarios are using soap sender adpater, and we find in PI 7.11 there is a functionality to display the wsdl of sender agreement.
It seems xmlspy can create soap request based on the url format of wsdl, but we can't send the soap request to PI as it gave the error message as below " Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=;AN=null;ANS=null;".
Do we have to use the "TOOLS->display wsdl" menu to get the wsdl file to local and then provide it to 3rd party system? If so, we have to export wsdl again whenever data structure changes.
Thanks in advance.

HI,
Do we have to use the "TOOLS->display wsdl" menu to get the wsdl file to local and then provide it to 3rd party system? If so, we have to export wsdl again whenever data structure changes.
---->yes ,we have to export wsdl again whenever data structure changes.
and
we have 2 approaches for generating WSDL FILE
1. in sender Agreement
2. from memu bar-> tools
but we have to generate WSDL file Through Menu bar "TOOLS" because there is chance to provide url and sender details after change the Structure..,..
thanks,

Default namespace in the SOAP sender adapter

Hi All!
Sorry for the following really easy question but what is the default interface name and default namespace in the SOAP sender Adapater? The name of the interface to where the adapter should forward the received SAOP message?
it means that for every soap message a new communication channel should be created. Or only one channel is enough?
And in the receiving case only one is enough or for every web services a new receiving communication channel need to be created?
Thank you for your answer.

Hi,
q) what is the default interface name and default namespace in the SOAP sender Adapater?
Ans) Soap Sender does not have any default namespace and interface. That can be set at Sender Agreement.
q) The name of the interface to where the adapter should forward the received SAOP message?
Ans : That message is forwarded to Adapter Engine and then to integration Engine. That takes interface in sender agrement and Namespace.
it means that for every soap message a new communication channel should be created. Or only one channel is enough?
Ans: For sender, 1 communication channel is enough. For Receiver, if you have 10 different systeems, then you need to create those many receiver communication channels .
And in the receiving case only one is enough or for every web services a new receiving communication channel need to be created?
Ans : Same as above
Note Soap message is not criteria for creating channels.... Please note that .. soap communication channels creates soap messagae.
-Subbu

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.

Using SOAP Sender adapter in PI 7.1

Hi Guys,
I've created a sync scenario with SOAP sender adapter, but I have troubles with calling it.
I use following URL: http://<host>:50000/XISOAPAdapter/MessageServlet?channel=:BS_Bus_Sys:CC_SOAP_Test as I did in XI 3.0, but I'm getting error HTTP 400 Bad Request. I'm using the request generated from the IR Configuration.
Has something changed in 7.1 for this type of scenario?
Thanks guys,
Olian

Hi! Olian,
I think u r going in a wrong way. The above given URL is wrong and incomplete one.
The above url comes only after generating the WSDL. You ill gives that URL to ur source team to post their data at which this URL itselfs acts as an Gateway to enter into SAP XI/PI.
The generated WSDL contains URL like this>>
"http:// Host:Port/XISOAPAdapter/MessageServlet?senderParty=&senderService=Business Service&receiverParty=&receiverService=&interface=SenderInterfaceI&interfaceNamespace=http://XXXXXXXX" />
Also follow the below procedure for generating the WSDL.
Except generating WSDL remaining all development steps are same as creating File to Proxy Scenario.
CREATING THE WEBSERVICE IN XI :
1) In Integration Directory, go to Tools tab --> Define Web Services.
2) Now one Wizard window will opens and follow the below steps:
Here donu2019t go for the u2018 Proposed URLu2019, instead specify the URL as::
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=:<service>:<channel>
If there is party then ::
http://host:port/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>.
3) Specify the Source Messageu2019s Message Interface.and remaining other input parameters.
4) Specify the Sender Business Serviceu2019s details:
5) Here, Cross check the details displayed and then click on u2018Finishu2019 button to create the Web Service
document(WSDL)
6) Now Save the WSDL code to the local system. At the bottom u ill get URL based on the above input
URl:
Note: Here in XI there is no XML Testing tool or SOAP client tool to test SOAP messages. That is why most of the people prefer either ALTOVA XML SPY Tool or SOAP CLIENT TOOL or INFO PATH.
If your working on PI 7.1 means::
1) Simply after creating Sender Agreement go to options above to that sender agreement instead of tools menu... and there you can observe 2 options at the bottom side.
a) PUBLISH in SR
b) Generate WSDL.
2) Once after activating your ID componenets just Press or go for option Publish in SR. Then automatically it will generate WSDL and publish that WSDL in the SERVICE REGISTRY. which is latest concept in PI 7.1.
3) Now by entering authentification details you can able to enter into service registry.
There are 4 tabs::
a) Service definitions
b) Publish
c) classifications
d) Manage.
Go for Service definitions::
4) Enter your sender SOAP interface and press GO or enter.
5) Select your interface and then at the bottom u can observe again 4 tabs:
a) General b) End Points c) classifications d) System Details.
6) In the general you can able to see your WSDL URL by again entering Authentification details.
7) Now Click End Points>Test Button>Enter Authentification details-->Seelct your Interface
Note:: Now you can test your scenario in this WEB SERVICE NAVIGATOR.
8) There you can enter you can pass your Input data parameters in your SOAP interface and execute or test your scenario here itself without any using of external tool like Altova XML or SOAP client tool.
I hope the above information will give you a detailed information in generating and testing webservice right.
Regards::
Amar Srinivas Eli

"Channel started but inactive" in RWB Monitor for SOAP sender channel

Dear XI specialists,
I have configured a communication scenario involving SOAP Adapter (sender) usage, but I'm facing the issue when testing the scenario. The problem is that none of messages are coming into the SOAP Adapter (checked via TCode SXI_MONITOR in XI) when using 3rd party SOAP-clients (XML Spy, soapUI) based on WSDL-file generated and exported from XI.
I checked the sender communication channel for SOAP Adapter - it is activated in Integration Builder's Directory. SOAP Adapter itself is also started.
I checked Runtime Workbench monitors and in the Communication Channels Monitor of the Components Monitor received the warning saying "Channel started but inactive" for my configured channel as well as for other channels working on SOAP Adapter.
Activities which were performed (in the order in which they were performed and results tested):
1. the configuration channel restart;
2. the communication channel re-activation and further re-start;
3. SOAP Adapter restart;
4. XI system's Java instance restart.
All mentioned activities didn't give any positive effect in part of this issue resolution.
On the other hand, if I use test message functionality of the Runtime Workbench (Component Monitor), then messages are seen in SXI_MONITOR and expected response messages are also returned to XI from integrated business system.
Would you please advise what can be checked else here and where the root of the problem may be detected?
All your answers and feedback will be greatly appreciated and awarded accordingly.
Many thanks in advance and my regards,
Vadim

Dear all,
Thank you for your input! Unfortunately, the problem still exists after testings and checkings which you suggested.
TO Seshagiri:
I checked message monitor and found only several messages for the required sender/receiver services pair in the used namespace - all of them were successfully processed (these are messages which I sent by means of RWB Component Monitor's test message functionality).
TO Sarvesh:
Yes, sender agreement is configured properly. I configured it when configuring communication scenario in the Configuration Wizard and then manually re-checked its definition. Moreover, when performing Test Configuration in ID, I received positive results.
TO Nallam Guna:
I cleared Data Cache in Integration Builder, but this didn't help.
TO Gujjeti:
I'm on SAP NetWeaver 2004s PI 7.0. Service Pack level for PI is 13.
TO Durga:
Thank you for provided links! I have already had a look at them - but proposed solutions doesn't seem to be working in my situation.
Thank you all once again for your prompt answers! I really appreciate your attempts in helping me!
I would appreciate if you could share any further ideas on this issue.
My best regards,
Vadim

Default XI parameters in 7.1, soap sender.

Hi,
I have a quick question about Default XI Parameters in Soap sender adapter in PI 7.1.
Why are they not present in PI 7.1( sender interface and sender NS )?
which are mandatory parameters in 7.0.
I was guessing that , this ways we can create a generic soap sender CC.
Does anyone have a exact answer as why it was removed?
Regards,
Venkat..

> Even in PI 7.0 we will add interface name and CC to the URL.
> 1. Do you mean that we are supposed to have NS too along with above entries?
Yes, you should add interface and namespace as it is mentioned in SAP Note 856597
> 2. What do you mean by aligning behavior of SOAP adapter with other adapters?
Other adapters (File, JMS) get interface and namespace from a sender agreement connected to a sender channel. The behaviour of the SOAP adapter was different before.
I was told by development that migrated channels from 7.0 work without any change. If this is not the case, open an OSS ticket for this.
For new channels you have to call the SOAP adapter always with interface name and namespace. The online help is not correct.
Regards
Stefan

SOAP sender agreement

Similar Messages

Maybe you are looking for