cancel
Showing results for 
Search instead for 
Did you mean: 

which is the user to logon to the WAS? PISUPER?

Former Member
0 Kudos

type the URL: http://host:HTTPport/sap/xi/engine?sap-client=100 into the browser, the authority is required in the web application server. And I use the ID pisuper but the answer is name or password is invalid. I am sure the name and the password is exactly right and I have no idea which user that I should use to logon on to the WAS is suitable.

Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Use the user PIISUSER amd its password.

---Satish

Former Member
0 Kudos

exactly PIISUSER is okay. Thank you.

Further question:

I sent soap message to XI and I got the error message which is described as below in the adapter engine.

Transmitting the message to endpoint http://xidev:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout

As I mentioned before the URL http://xidev:8000/sap/xi/engine?type=entry is okay with the user PIISUSER. However the XI IS still can not receive the SOAP message yet.

Former Member
0 Kudos

HI,

From SAP help.

The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel

http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm

Regards,

Sudheer.

Former Member
0 Kudos

Hi,

The error is timeout. It is not problem with userid and password.

Refer SAP Note - 856597 Question No1 , 893713 ( for Receiver timeout)

ALso look into this blog

/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts

Also Check the following thread with similar problem:

There are many reasons for connection timeout. Especially check your proxy settings.

>>Channel started but Inactive

Make a small check if the CC is active in ID.

Also have you tried connecting to that Web Service directly fome a WS client. Check whether you can connect it without any problem. If its accesible from browser then its ok. Check in the Message monitoring for more details on the error and post it, that might help to solve the issue. And also in Communication Channel monitoring.

...Satish

Former Member
0 Kudos

I miss configuring the Integ. Server URL in XI. It's ok rightnow. The SOAP message can send to XI.

However, using http://xidev:50000/XISOAPAdapter/HelperServlet?action=FindChannel&; channel=P:S:C to varify the channel, still can not return right result, only invalid channel.

Former Member
0 Kudos

Hi,

I think you are giving you are giving wrong url address. It should be:

http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>.

If you use party give party. Give your sender service and sender communication channel.

Check this document on how to use soap adapter:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a2202...

Also see this weblog for some help:

/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi

...Satish

Answers (0)