Create new application to post xml to an existing SAP PI interface. SSL Cert and general procedure

[Former Member]

I'm creating an application that will POST an xml file to an SAP PI interface that was originally created for a legacy application. I have the endpoint URL as well as all the parameters such as; service, namespace, interface, qos.

I also have a username and password. Today I made my first test call to the DEV instance of SAP PI, and received and SSL cert error.

Is it correct that in order to POST to an SAP PI interface that my app needs an SSL cert?

Should what I am attempting work in theory, replicating the XML file and using the exact same interface as a legacy application?

[Former Member]

Hi,

Instead of using/creating an application to post xml data..you can use either HTTP test tool or SOAP UI..which can ease the things...provided your sender adapter in PI is HTTP/SOAP..

In brief its possible to post data to PI via tools rather than awaiting request from exact source applications..

HTH

Rajesh

[Former Member]

If I use a test tool to post the data it would require me to be present each time data needs sent. The app I am creating will act as a service layer between another app and PI.

When data is ready is the ultimate source app, it calls my application when then handles the POSTing of the data to PI, it will also retry the post if there is a failure. It will also gather up changes at regularly scheduled intervals and handle the POST without human intervention.

I have one test tool: http://sappihttpclient.codeplex.com/   But, I do not see any configuration options for a certificate. Is there a more comprehensive test tool or one better suited?

When I pass the username and password, should this be part of the URL params?

[markangelo_dihiansan]

Hello,

I also have a username and password. Today I made my first test call to the DEV instance of SAP PI, and received and SSL cert error.
Is it correct that in order to POST to an SAP PI interface that my app needs an SSL cert?

Only if the protocol starts with https would you need to present a certificate. The Certificate Authority and Intermediate Certificate Authority would also need to be "trusted" in the PI system via STRUST.

Regards,

Mark

[Former Member]

The URL is indeed HTTPS.