not able to connect to salesforce in PI

[former_member217945]

Hi experts,

I working on SFDC - PI- Idoc scenario. , i have done configurations steps and provided wsdl to Salesforce team. From salesforce they are unable to hit to PI. getting 503 service unavailable error.

Does requires any authentication?

Can any one help me n this

Thanks,

Reddy

[Muniyappan]

first check if you are able to send the message to PI using soap ui.

can you open the url in browser?

[former_member217945]

hi,

while testing in SOAP UI , i am unable to get response.

if ill open url in browser, its showing below message.

[Muniyappan]

i think it is asynchronous scenario. you wont get any response.

have you checked in pi? communication channels? any message received?

[former_member217945]

Hi Muni,

yes , this is Asyn

im not getting any message  in PI and C channel.

How would i check this scenario?

thanks,

Reddy

[former_member186851]

Reddy check sending the message to ur PI system and check,Client is unable to send message to PI right?

[Muniyappan]

could you please share us the soap ui screen shot after you run?

i hope you have provided username and password in soap ui.

if message is reaching pi then you can see the messages in communication channel and message monitoring.

Regards,

Muni

[former_member217945]

Muni,

i have given username  & PW , but still same error.

here i am communicating with salesforce.

Does an session Id required for this sender SFDC scenario?

When i connect with this url in browser im getting below message

[Muniyappan]

>>from soap ui test, looks you can send the message to your SAP PI system.

are you using ICO? if yes, please enable logging.

>>ask your salesforce team to do telnet from their system.

command

telnet hostname port

>> you need session id only when SFDC comes at receiver side. if it comes at sender side, no session id needed.

[former_member186851]

Hello Reddy,

Check whether PI system is up and running.

Check whether any port/firewall/proxy to be enabled at PI server.

Ping your channel and check if everything is fine.

If everything is fine try restarting your java stack