cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP Client unable to send SOAP Request

Former Member
0 Kudos

Hi ,

I am trying to send SOAP request using ALTOVA SOAP client .

Using Pi 7.1 , I have published Sender Agreement in Services Registry and i am able to test the service without any errors from SR.

But when i try to test it using SOAP client i get following error.

<!-- see the documentation

-->

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

- <![CDATA[

com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=null;TS=;AN=null;ANS=null;

at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:237)

at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:167)

at com.sap.aii.af.service.cpa.InboundRuntimeLookup.<init>(InboundRuntimeLookup.java:88)

AND SO ON.

Any solution to this ?

I have tried it with different users , combination of URLs and also by directly importing the WSDL. None of them is working.

Please suggest!

Regards

Sayali

Accepted Solutions (0)

Answers (16)

Answers (16)

Former Member
0 Kudos

Can you please provide the answer on how you solved this issue with XML Spy?

Former Member
0 Kudos

This has been ressolved.

Former Member
0 Kudos

Hi Suraj ,

Last question .

We are testing this using SOAP client and it is working but it asks for username and password everytime .

Now when we give this wsdl for client to test it will ask them for username and password everytime they try to test it.

Any thing which you can suggest to avoid this ?

Regards

Sayali

former_member187339
Active Contributor
0 Kudos

Hi Sayali,

>>Last question .

Great this thread was going into record books for views and replies

>>We are testing this using SOAP client and it is working but it asks for username and password everytime . Now when we give this wsdl for client to test it will ask them for username and password everytime they try to test it.

This itself is another discussion. I would suggest you to search sdn you will get many responses on this topic. also the SOAP Note which I mentioned before will be able to give you more insight.

And also check these blogs on how to handle it in the source end (or the requester of this wsdl end)

https://weblogs.sdn.sap.com/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken]

https://weblogs.sdn.sap.com/pub/wlg/1334 [original link is broken] [original link is broken] [original link is broken]

Regards

Suraj

Former Member
0 Kudos

Dear Sayali,

You can create a generic user ID for this purpose and provide it to the consumer to access PI.

OR

You can also incorporated the use of encoded string in the service consumer proxy at the client where a combination of Key Value paires will be used for USER ID, PASSWORD and Decryption.

UserID and Password key value pairs will be maintained in the machine.config file of the server and the Decryption key value pair will be at the web.config file of the application which is consuming the service.

Warm Regards,

Anshul

Former Member
0 Kudos

Hi Suraj ,

Thanks a ton! "*" Worked!!

Now i have two questions :

1. I am trying to publish sender agreement. But the URL generated in sender agreement has to be changed manually. So how do i go about this ?

2. I tried saving wsdl directly from "Display WSDL " option and by entering the URL

"http://roysappi01.royston.jmadir.com:50100/XISOAPAdapter/MessageServlet?channel=*:CRS_BS:SOAP_CRS_SENDER"

How do i publish this URL in Services Registry ?

Thanks again for your help!!

Regards

Sayali

former_member187339
Active Contributor
0 Kudos

Hi Sayali,

>>1. I am trying to publish sender agreement. But the URL generated in sender agreement has to be changed manually. So how do i go about this ?

This cannot be done, instead try to create a sender agreement and sender communication channel with Party value as blank instead of star.

Regards

Suraj

Former Member
0 Kudos

Earlier i had pasted wrong link from the WSDL which was https so the port was 50101...

We are using HTTP and port is 50100

There is no error in Integration directory cache.

Regards

Sayalee

former_member187339
Active Contributor
0 Kudos

Hi Sayali,

Try this url

>>http://roysappi01.royston.jmadir.com:50100/XISOAPAdapter/HelperServlet?action=FindChannel&channel=*:CRS_BS:SOAP_CRS_SENDER

I have put a star in place of party... If this works then you need to change the url in wsdl accordingly and test your interface

Regards

Suraj

Former Member
0 Kudos

Hi Suraj ,

I created a new channel but it is still giving the same error.

Is there anything missing in my URL ?

URL

http://roysappi01.royston.jmadir.com:50100/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:C...

Regards

Sayali

Former Member
0 Kudos

Dear Sayali,

You Mentioned 50101 as the prot number in your earlier comments.

Please check if you are using the correct port number to generate the WSDL is ID.

Warm Regards,

Anshul

former_member187339
Active Contributor
0 Kudos

Hi Sayali,

The url is correct, check the point mentioned by Anshul.

Also did you checked

>>2. Check if any error entry in present in Integration Directory Cache.

Regards

Suraj

Former Member
0 Kudos

Hi Anshul ,

No luck !

Regards,

Sayalee

Former Member
0 Kudos

HI Suraj

I am using following URL to test if the channel exist but it is giving following error.

URL

http://roysappi01.royston.jmadir.com:50100/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:C...

The channel is visible in RWB and is activated and CPA cache is also refreshed.

Error :

<?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: Channel not found for :CRS_BS:SOAP_CRS_SENDER in SOAP

at com.sap.aii.adapter.soap.web.HelperServlet.processFindChannel(HelperServlet.java:421)

Can you suggest whats going wrong ?

Former Member
0 Kudos

Dear Sayali,

Check if this blog helps, its on the same issue:

[Blog|;

Warm Regards,

Anshul

former_member187339
Active Contributor
0 Kudos

Hi Sayali,

Try these:

1. Try to do a full cache refresh

http://server:port/CPACache?refresh=full

2. Check if any error entry in present in Integration Directory Cache.

3. If nothing works try to delete the communication channel and re-create a new one (with a new name)

Regards

Suraj

Former Member
0 Kudos

Hi Suraj ,

I am crosschecking the list with my scenario one by one.

And "https" link was posted by mistake. We are testing with http url itself.

Thanks,

Sayali

Former Member
0 Kudos

Dear Sayali,

Please try to use the below given URL while generating your WSDL in PI:

http://<servername>:<Portno>/XISOAPAdapter/MessageServlet?channel=:<BusinessSystem>:<Communication Channel>

Then try and test this wsdl using XMLSpy and see if this works.

Your end point URL of the WSDL should look like the below given URL:

http://<PI Server>:<Port No.>/XISOAPAdapter/MessageServlet?channel=:<Business System>:<Communication Channel>&amp;version=3.0&amp;Sender.Service=<Business System>&amp;Interface=http%3A%2F%2Finxxxx.com%2Fhxx%2Fpayxxxxx%5E<Service Interface NAme>

Warm Regards,

Anshul

Former Member
0 Kudos

Have u tried SOAP UI ?

Regards ,

Former Member
0 Kudos

Hi Abshishek ,

Special characters appear as i have posted the URL from published Sender Agreement.

We have manually written the URL and tried making that work without special characters but that doesnt help.

Regards,

Sayali

Former Member
0 Kudos

Hi Suraj ,

We have already used this other URL . This is format prior to 7.1 but its still not helpful and the format / URL which i have specified is generated after publishing the Sender Agreement in SR.

Thanks,

Sayali

former_member187339
Active Contributor
0 Kudos

Hi Sayali,

Few things:

1. Both the URL formats (mentioned by you and me) can be used with PI7.1.

2. There is no need for using interface name in the ur, you can try removing that.

3. Try to find if your soap sender channel can be successfully found by using this url

http://host:port /XISOAPAdapter/HelperServlet?action=FindChannel& channel=p:s:c

4. Even if you are not using parties in sender or receiver they should not be removed from the url

http://host:port /XISOAPAdapter/MessageServlet?senderParty=& senderService=FS& interface=IF&receiverParty=&receiverService=TS&interfaceNamespace=IFNamespace

5. If nothing works try to check the reason of the error. check the question Q: How can I trace the whole message? in note Note 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter. And try to do as mentioned there.

6. Still why https is used? WSDL will provide both HTTP and HTTPS url use the http one

Regards

Suraj

Former Member
0 Kudos
former_member187339
Active Contributor
0 Kudos

Hi Sayali,

try changing the url in wsdl to

>>https://roysappi01.royston.jmadir.com:50101/XISOAPAdapter/MessageServlet?channel=:CRS_BC:<channel>

<channel> replace with sender communication channel's name

Also you are using https protocol is the port information correct? Re-confirm that

Regards

Suraj

former_member200962
Active Contributor
0 Kudos

When you are not specifying the party why to have the party variable?

remove special characters that appear in the namespace......use the WSDL format that I provided in the earlier reply.

Regards,

Abhishek.

Former Member
0 Kudos

Hi All,

Almost everything mentioned above has been tried and tested.

Seems to be a problem with WS Runtime.

I tried to develop same scenario with HTTP client and it works fine.

Regards

Sayali

former_member187339
Active Contributor
0 Kudos

Hi Sayali,

>>I tried to develop same scenario with HTTP client and it works fine.

It works because the message is directly sent to the Integration engine (rather going through the sender agreement and the sender communication channel)

In the WSDL file which you got from PI what is the url mentoned? Can you paste it here? I guess there is a problem with that.

Regards

Suraj

Former Member
0 Kudos

Sayali ,

I am trying to send SOAP request using ALTOVA SOAP client .

Using Pi 7.1 , I have published Sender Agreement in Services Registry and i am able to test the service without any errors from SR.

But when i try to test it using SOAP client i get following error.

1. Try with SOAPUI once

2. else there will be issue with SOAP string..

Regards ,

former_member200962
Active Contributor
0 Kudos

Try sending the request with the below URL format:

http://<IPAddress OR ServerName>:<PORT_No>/XISOAPAdapter/MessageServlet?channel=:<SenderBusinessService>:<SenderSOAPCC>&version=3.0&Sender.Service=<SenderBusinessService>&Interface=<SenderInterfaceNamespace>%5E<SenderMI>

The above error occurs when either proper ID objects are not maintained (or maintained with incorrect/ insufficient data) OR when the cache is not properly updated......try making some dummy changes to the ID objects and again activate (check the Cache Status Overview to confirm that activation is successful) and then again test the scenario.

Also try testing the scenario from some other tool like SAP SOAP Client (or even RWB --> Integrartion Engine --> Test Message), this is to confirm that at least all the objects are in place.

Regards,

Abhishek.

former_member212816
Participant
0 Kudos

Hi,

(a) Please check if the SOAP URL that you created is working fine, by entering the same in the internet explorer or any other browser. When you enter the URL and hit enter, it should request for your user name and password. And on entering the user details it should display some message as "Message OK". If this is working then your URL is correct, else try to correct your URL as per the above post and re-generate the web service.

(b) If the URL is correct. I would suggest you to go to "Advanced" tab in SOAP adapter. Select the checkbox "Set Adapter-Specific Message Attributes". Save and Activate the channel. Regenerate the webservice and try. Hopeful this should solve your problem.

Thanks,

Manohar Dubbaka.

VijayKonam
Active Contributor
0 Kudos

Check you Web Service Endpoint URL in the WSDL. You should have the Party, Business System and the communication channel filled in that URL.

VJ