Skip to Content
Former Member
Jan 05, 2011 at 04:38 PM

successfully configured http receiver adapter, unable to post the payload



After searching lots of sdn forums and blogs, I was able to configure the HTTP receiver adapter which will ping the remote client system from the PI system. The configuration I have followed:

Creation of RFC destination of type G in SM59 of PI system

Technical settings -> the details of host, port and path prefix of the remote client system

Configuration of the certificate in strust and using the same under SSL status of logon and securities as the url is of https.

After the connection test we are getting a http 200 which means successfully pinged the remote client system.I am using the RFC destination while configuration the HTTP receiver adapter in the ID configuration part.

During the end-to-end testing, in RWB -> Message Monitoring

It shows that the message has been successfully send to the remote client. However, when we logon to their system we find none of the message that we have send.

so i guess the current configuration is unable to post the payload(message) into the clients server.

We are unable to trace what has gone wrong.

Any kind of reply will be greatly appreciated.

Kindly help on this.