Skip to Content

Hi Dear friends,

After very long time I´m here to share something interessting that you can find similar in the blog https://blogs.sap.com/2014/02/20/michals-po-tips-how-to-send-messages-directly-to-aex-ico-adapter-independent-soapui-version/.

I will show more step by step that can be used for any case (situation with others plataforms also, it´s just for dont wait finish all backend part for test point-to-point), my current case its related with SalesForce using REST adapter to send via RFC data about login dinamic to receive the tokenid or sessionid from SalesForce Clould Plaform.

As you can see on integration diagram below –  The start point will be SoapUI instead off SAP ECC.

 

To make this test you must have ESR and DIR done and as a sender one adapter SOAP – HTTP as the image below – DUMMY adapter:

  • Configuration of Sender SOAP – HTTP:

PS:. Do not forget do mark Best Efforce Service

The end point is Sales Force with dinamic adress that data will comes from SAP ECC via RFC depend of the user.

https://test.salesforce.com/services/oauth2/token?grant_type=password&client_id={client_id}&client_secret={client_secret}&username={username}&password={password}

The adapter for Sales Force in this case is not SOAP, will be rest with many configuration, the first will be to show how to make this adress above correct via data inside XML file.

Those values will be insert on the adapter enginne at runtime via xpath configuration as you can see below:

client_id={client_id}&

client_secret={client_secret}&

username={username}&

password={password}

When we are talking about JSON, it´s not XML file so we need configurate also in the adapter:

  • Adapter receiver channel REST – Method POST:

Now a verry important part of the adapter REST configuration, the asnwer of Sales Force will be:

  • Json Message Sales Force Response:

{

access_token“: “00D3B000000DWav!AQsAQIiLveS6.7rE0MA8kmdkE.eHx.OqicB4WMVVEDHMjycMhpZ6WVXVz9Rk7_5MssLs2FZXiIKIJSAA4n1E05wv1dTFVa2p
instance_url“: “https://cs50.salesforce.com
token_type“: “Bearer
issued_at“: “1509140645799
signature“: “UIL3ieCiGg2DMvM5engIhoTN4ruyWkzYF4c9CCYQDZM=

}

I did the convertion using the online tools to XML and create a very similar stucture at SAP PI

  • Message Type Response:

So as you can see above there are JSON format and XML format, it means that the sturcture are different because one there is no PepTokenResponseLogin as root, so we need make this configuration at channel also in the button – “Add Wapper Element”:

In the blog of Michal Krawczyk he shows the address:

http://<server_host>:<j2ee_port>/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_Michal_Krawczyk&receiverParty=&receiverService=&interface=SI_Michal_Out&interfaceNamespace=urn:michal.krawczyk.com

This adress you can generate via ICO:

  • Right click on the ICO Scenario and generate WSDL:

Soap format of adress of start point:

Import the WSDL into SOAPUI Software, in my case show the RFC structure, remeber the scenario here its RFC to JSON

  • Test:

Don´t forget to adapt this to your project perspective and I hope somehow help you to test messages/interfaces in SAP PI AEX 7.31+ without waiting Basis missing configurations or abap development.

Kind Regards,

Ricardo Viana.

 

 

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply