Sender Agreement - Display WSDL

Hi,
We have a sender agreement with a communication channel of type WS.
When we try to do Sender Agreement --> Display WSDL, we get the following error:
Cannot determine HTTP information (protocol, host, port) of current application server (RC=1-)
Our system is configured for SSL and we have disabled the ICM HTTP service, leaving only HTTPS service on.
If we activate the ICM HTTP service, then we can display the WSDL. But in the WSDL URL field, it says "http://ourdomain.com:50000/..........", which explains why it failed when we deactivate the HTTP service.
How can we make this functionality working with HTTPS? We would like to have a WSDL URL like "https://ourdomain.com:50001/......."
Thanks in advance

By the way, when I start transaction SOAMANAGER, it open the browser with the URL http://server.domain.com:0/....... (we have configured ICM HTTP service with port 0).
How I can make SOAMANAGER open the URL https://server.doamin.com:50001/..... (50001 is our ICM HTTPS port) ?

Similar Messages

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

Error when trying to Display WSDL for Sender Agreement

Hi,
I'm getting an error when trying to display WSDL for a sender agreement. The error message is as follows:
Adapter Engine af.xxx.yyy for communication channel not registered in SLD Unable to find the SLD element (SAP_XIAdapterFramework, [CreationClassName, SAP_XIAdapterFramework, string, Name, af.xxx.yyy, string], [AdapterType, SOAP, string])
The SOAP adapter being used is from the non-central AE. I I immediately checked for inconsistent SLD components per note 746176 but everything is in order there. I tried re-registering manually the non-central AE manually as well.
Anyone else ever had the same error? Any hints much appreciated!

Hi Luqman,
go to the sender channel and replace the Adapter Type.
Select the type as SOAP from SWCV SAP BASIS 7.xx or SAP BASIS 3.0
The channel is referring to a swcv which is not present in esr.
As you might know, the adapter metadata is fetched from ESR/IR, so if the SWCV containing the metadata inside namespace http://sap.com/xi/XI/System etc, is not available then it will throw error.
If you do not want to change the Adapter Type in the channel, import the swcv from SLD to ESR and create/import the respective adapter metadata.
Should resolve your issue.
Cheers!
Souvik

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,

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.

Display WSDL in ID with difference URL for send SOAP scenario

Hi Experts,
I have one question here about Display WSDL tool in ID.
The first step is to specify the Integration Server SOAP Inbound Channel (URL).
Refering to the help document this URL can be either the Integration Server or an Adapter Engine.
However by simply click Propose URL option, the URL given automatically is pointing to the Integration Engine only.
http://<host>:<port>/sap/xi/engine?type=entry
Does this mean in this case, no sender SOAP adapter channel is required?
And the further question is what is the difference between URL to IE and AE.
Here i know the URL format are different, my question is what is the major difference in the processing process?
And what are the pros and cons of giving different URL when Display WSDL?
Thanks in advance. Any inputs will be appreciated.
Best Regards,

Hello,
Does this mean in this case, no sender SOAP adapter channel is required?
If it will be connecting directly to the integration engine, yes. No sender adapter is required.
And the further question is what is the difference between URL to IE and AE.
Here i know the URL format are different, my question is what is the major difference in the processing process?
And what are the pros and cons of giving different URL when Display WSDL?
The advantages and disadvantages are summed up in Stefan's blog below:
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Hope this helps,
Mark
Edited by: Mark Dihiansan on Sep 8, 2011 5:43 AM

Problem in Display WSDL

Hi All,
I have transported my development from one environment to another. When i go to Sender agreement and display WSDL i am getting the follwing error
" Problem updating the object id <obejctid> : ICF"
The adapter used in sender agreement is WS adapter with HTTPS Transport channel security in communication security and authentication method as "usedid and password(transport channel authentication".
Kindly help me in resolving thid issue as it is stopping us from testing as well moving to another environment.
Regards,
Sujata

Does anyone can help me???

Display WSDL in PI 7.0

Hi folks,
In PI 7.0 Where i can get "Display WSDL" option.If it is not there ,may i know the alternative .Please suggest me
Thanks,
Dileep

Hi Dileep,
WSDL file generated in Integration Builder
Steps are as given below:
1. Under tools -> select Display WSDL.
2. Give URL as : http://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:<sender Business system>:<sender communication chanel name>
3. Specify the service interface name to be used.
4. Then save it on your local machine. Which can be consumed later.
please go through below blog,
http://wiki.sdn.sap.com/wiki/display/Community/Generating+WebService+FromPI
Second approach is you are using PI 7.1
go to Sender Agreement -> menu-> display wsdl

Display WSDL with HTTPs end-point

Hi.
I'm working SOAP-PROXY scenario, when I display WSDL in Integration Builder (sender agreement), the result is a HTTP_PORT and HTTPS_PORT, like the following:
HTTP_PORT...location: HTTP:host:port/xxxxxxxxxxxxxxxxxx and
HTTPS_PORT...location: HTTPs:host:/xxxxxxxxxxxxxxxxxx (without port)
Where Can I configure the port HTTPs to show in "Display WSDL" funcionality, please?
Ps.: The HTTPs is funcioning well.
Thanks.
Bruno

Hi Everybody.
My problem is solved. Re-started the Server PI and now it's fine.
Thanks
Bruno

Sender Agreement Endpoint Creation

Hi,
I have a SOAP - PI - Proxy scenario where I want to call the sender agreement to initiate the message. In the Integration Builder, I see that I can display the WSDL for the Sender Agreement. If I take that URL and put it into WS Navigator, I can successfully get the entire message flow (sync).
My question is, how do I create my own/secondary binding for this agreement? It seems like they generate one for you automatically and you have no control over the configuration for it.

Hey
When you are using SOAP on the sender side,you need to generate WSDL file in Integration directory and provide to the sender system,in this WSDL you have option to specify the URL,this URL is used by the sender system to the post file.
if you want to post the message directly to Integration engine of XI,then you can just click on "Propose URL" button which you get while creating WSDL file(this wont use sender agreement).
The below blog will help you in that.
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
But if you want to post to the adapter engine,then you need to generate the URL in the format as described in the below blog.don't click on "Propose URL" in this case(this will use sender agreement).
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
Thanks
Aamir

Regd. error in sender agreement(when to check sender uses virtual receiver)

hi Experts,
I am doing a file( SFTP adapter ) to IDOC scenario.
I got an error :
Couldn't retrieve inbound binding for the given P/S/A values:FP=XYZ;TP=;FS=XXXX;TS=XXXX;AN=XXXXXX;ANS=;
I checked my sender agreement and saw some "*" symbol displayed at the end on SA name.
To quick fix it and remove the star symbol'', i have just created SAgreement again and this time i checked "Sender uses virtual receiver " and revomved thestar symbol '' and saved without mentioning anything there.
When i tested it worked! but i want to know what made it work, is it the right practice.
i did a lilttle search on when to use "sender uses virtual receiver" option.i came to an understanding that it is mainly used to handle multiple input file formats in a single configuration scenario.
one more qns:
What are marketplace adapters,is this error comes when we use adapters which are not inbuilt or bought from external vender.
Regards,
Anika
Edited by: Anika Gulati on Jun 10, 2009 1:23 PM

Here are few ways for it...
SAP Process Integration: When to Use u201CSender Uses Virtual Receiveru201D in a Sender Agreement
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40cb67f7-6464-2b10-bcb9-8edb9a3569f9
SAP Network Blog: Virtual Receiver - Why do you 'really' need it?
/people/shabarish.vijayakumar/blog/2008/09/16/virtual-receiver--why-do-you-really-need-it
-SM

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

Sender Uses Virtual Receiver - Receiver Determination & Sender Agreement

Hello all,
There is a Checkbox with Sender Uses Virtual Receiver while creating Receiver Determination & Sender Agreement.Could anyone tell when one shall use that checkbox & diffrence of using the same in Rx Determination & Sender agreement ? And Lastly What is the significance of using * in Party &
Service in that Sender Uses Virtual Receiver part ?

Hi,
we will use it when we are using B2B scenario......
More details... please check this.............
/people/shabarish.vijayakumar/blog/2008/09/16/virtual-receiver--why-do-you-really-need-it
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/virtual%252breceiver%252buse%252bin%252breceiver%252bdetermination%252bb2b(Idoc%252bto%252b(File%252cIdoc%252bor%252bany%252bother%252bsystem))
http://help.sap.com/saphelp_nw04/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a423a8e5430e10000000a42189b/content.htm
Thanks

PCK Sender agreement

Hi mates,
At <a href="http://help.sap.com/saphelp_nw04/helpdata/en/db/73e03fc2269615e10000000a155106/content.htm">help.sap.com</a> I see that Sender agreements are not required in cases of proxies, SOAP & Mail adapter.
Since there is no Receiver Determination Step in PCK and receiver has to be mentioned in the Sender Agreement, If Sender agreement is not required for proxies, SOAP & MAIL, how are the receiver party & service mentioned?
Do they have to be sent by the client programs of proxy, SOAP & Mail? If yes, the WSDL generated has to contain the details of the receiver psrty and service too. Is that true?
Please clarify.

As for RD in XI i am pasting lines from sap.help
To forward the message, the following objects are required in the Integration Server:
· Party and service of party A, which sends the message. If there is a signature and you want it to be validated, you must also define a communication channel of type Sender and XI. In this case, you must also create a corresponding sender agreement (SA2).
· Party and service of party B, which receives the message. You must define a communication channel of type Receiver and XI.
· A receiver determination (RD) to determine the receiver of the message.
· An interface determination (ID) to define the inbound interface for the outbound interface of the sender.
· A receiver agreement (RA3) to transfer the message from the Integration Server to the PCK of party B.
Hope it helps.

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 - Display WSDL

Similar Messages

Maybe you are looking for