I am working on a project in which customer is planning to implement HCI PI and intent is to develop custom iflows development. As part of POC few interfaces were selected from existing SAP PI landscape. In one of the interface, an outbound proxy is sent from ECC to make a call via PI and get a response back to SAP ECC. In SAP PI it would be a straightforward synchronous interface but when it comes to HCI PI everything is a web service call. In this blog will show you the steps to expose outbound proxy as web service and then bind the endpoints from HCI so that transactions can be passed through HCI PI by retaining the same proxy program. This configuration steps can be used if you’re exposing FM as web-service.

To build this iflow in HCI-PI I have used a request-reply pattern in which sender is ECC and receiver system is a third party web service. The idea is when data is triggered from SAP, a synchronous WSDL which contains both request and response has to make a request and get back the response and post it to ECC through HCI PI iflow.

If you are familiar with SAP ECC. The data structure was created in SAP PI and made it available in SAP ECC under SPROXY transaction to which the proxy program was developed. In my scenario in HCI PI when developing iflow I used the same data structures in the mappings so that I can leverage same proxy program in ECC. I have downloaded the WSDLS from PI and used them in my message mappings.

Once the iflow is created and deployed it looks as below.

Steps to bind endpoints created in HCI PI and outbound proxy from ECC in SOAMANGER.

Step1: Login into SAP ECC and execute T-code SOAMANAGER

Step2: A new UI window opens in the default browser as shown in the screenshot below.

Step3: Click on Web Service Configuration tab as shown in the screenshot above

Step4: Select the consumer proxy from the drop-down menu and type the search pattern for the proxy according to the landscape naming convention and click GO button as shown in the screenshot below.

Step5: Select the proxy which needs to be exposed as web service and click apply as shown in the screenshot below.

Step6: Click on configuration tab as shown in the screenshot below and click on create button

Step7: Provide the details of logical port and description and choose the manual configuration and click on apply settings.

 

Step8: New configuration window opens as shown in the screenshot below.

Step9: Choose the method of authentication from following options. In this document have selected a basic authentication. Note: If you choose basic authentication (User ID/ Password) then you need to provide HCI tenant credentials as it does not allow to any service users. Follow the steps shown in the screenshot below and save the configuration.

When providing computer name of access URL provide runtime URL with no https:// and part after /CXF/* as this is not needed in access URL.

Step10: After saving the manual configuration it is activated automatically and can be seen under configuration tab as shown in the screenshot below.

Hope this helps!

See you in my next blog!

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply