In part one of these series; I discussed how to set up a modeling environment for creating iFlows and other artifacts in SAP HCI in the eclipse-based modeling environment. In this part 2, I will describe on a high level how to implement a simple SOAP2SOAP scenario. In this blog, SOAP UI will be used to trigger our client web service. So, let’s get started.
Modeling in eclipse is done in two perspectives:
Integration Designer: Creating iFlows, mappings, importing WSDL files and other existing SAP PI artifacts from the ESR, configuring communication channels and security artifacts.
Integration Operations: Deploying iFlows, monitoring the runtime.
Launch eclipse, go to Windows à Perspectives à SAP HANA Cloud Integration and enter the necessary details to connect to the operations server (tenant) and Enterprise Service Repository for importing SAP PI objects and artifacts such as Message mappings, operation mappings, WSDL.
To create an iFlow, first create an integration project, click on the project explorer palette, select New à Other à SAP HANA Cloud Integration à Integration Project
Follow the wizard through and the integration project will be created, follow the steps above to create an Integration Flow in the Integration Project and the following screen is shown:
This section describes the security Artifacts that will be necessary to configure the sender and the receiver systems for security. Follow the steps described below;
1) SSL Certificate CA, Public and Private Keys
1)internet options - 2)content- 3)certificates- 4)personal- 5)export
2) SOAP UI Settings: Load the Private Key into SOAP UI through the following steps
3) Deploy Java Key Store
4) Set up SOAP UI
Call the service exposed via SAP HCI using SOAP UI. The endpoint to be used in your SOAP UI can be constructed in the following manner: https: //<operations server name>/cxf/<path defined in the sender channel>.
5) Monitoring:
Check in SOAP UI to be sure the message is sent successfully and monitor it through the SAP HCI Eclipse IDE, Integration Operations perspective.
After all the security artifacts have been made available, the configuration for the systems to communicate will be done. The details about the configuration steps are described in part 3 of this blog. At this point you are able to configure a simple SOAP2SOAP scenario. If you have questions thus far, please do not hesitate to contact me.
Written By; Abidemi Olatunbosun, Rojo Consultancy BV, The Netherlands
Contributor; Geert van den Reek, Rojo Consultancy BV, The Netherlands
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
9 | |
5 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |