Part 3; Understanding the Power of SAP HCI: SOAP2SOAP Scenario Configuration
Configure the Systems, Security Artifacts and Communication Channel
Introduction: In Parts 1 and 2 of this series of blogs, issues relating to setting up the modeling environment with necessary tools as well as the security artifacts necessary for configuring a working scenario have been discussed. In this blog, a sample working scenario will be further developed (configured), deployed as well monitoring features examined. So, let’s get started. Below is the diagram of the working scenario discussed here before configuration;
Top down approach will be adopted in configuring this scenario; the following steps need to be performed;
- Configure sender system, receiver system (name of the sender and receiver system, this is optional) and Sender authorization (this is the Public Key pair )
- Import WSDL file from SAP PI repository or locally
- Parameters file for reference to Artifacts
- Mapping between Sender and Receiver system or import existing mapping object from SAP PI Repository
- Sender and Receiver communication channels
Configuring the Scenario
1) Configure Sender and Receiver Systems: Click on the sender system as seen in the diagram, check the property area and enter appropriate name for your sender system without whitespaces between names. Under sender authorization, click on the browse option to import your Public SSL Key from where it stored as shown in the diagram below and this is usually in the case of certificate based authentication;
Follow the above steps to configure the receiver system name as well but there is no need to browse Public Key on the receiver side.
2 Import WSDL file from SAP PI or local file system; For this blog, existing service interface from SAP PI is imported. To do, right click on the name of the Integration project in the explorer and choose the “Import PI Content” option and choose the option of the type of artifact to be imported and in this case, service interface. Tip: your WSDL file should have at least one operation, a service name and port name. When you export a WSDL from the integration builder Directory it will contain the necessary elements. Proceed to import the WSDL/service interface for both the sender and the receiver system and this will be used during mapping. Right Click Integration project à Import PI Content. The WSDL file could also be imported from a local file system, so it is not always mandatory to have SAP PI to use SAP HCI.
3 Create Parameters file for reference to parameters: This parameter file to be created will contain the reference parameters to be used in this this scenario, this parameters include, the location of the WSDL file, endpoints during the configuration of the communication channels. To create the parameter file, right click on the Integration Project, choose New, Other, General, file. Name the file as “parameters.prop” , follow the wizard and make sure it is saved in this directory “src.main.resources” and click the finish button.
The parameters.prop file is created and the entries for the location of the WSDL files and the endpoints can be entered as seen in the figure below;
To reference this parameters during configuration of the channels, the values on the right handside before the “=” sign is enclosed the double curly braces, e.g {{SOAPSender_WSDL_URL}}.
4. Mapping between Sender and Receiver system: To implement the mapping, two options arepossible, an existing mapping that meets the requirement for passing data from the source system to the target system can be imported from SAP PI using the same steps for importing service interfaces. However, the mapping used in this scenario is defined locally within the integration designer. To create a new mapping, right click on the integration project, click new, other, then under SAP HANA Cloud Integration, choose message mapping and follow the wizard.
Choose the source and target element (these are the WSDL file imported from SAP PI ESR earlier, it could also be WSDL file imported from a local file system) and switch to the definition tab to do your graphical mapping and use all the functionalities in SAP PI graphical mapping. However, there is no possibility for creating user defined functions for now, and only graphical mapping is supported. In this demo, the concatenation function has been used and the drag and drop functionalities of the graphical mapping displayed in the figure below;
Go to the modeling area, and right click on the mapping artifact, choose the option “assign mapping” and select the mapping was created earlier.
5. Sender and Receiver communication channels: The communication channels will be configured in this step. Right click on the channel artifact on the sender side and choose the SOAP Adapter as the adapter type.
Choose the Adapter specific icon to configure the endpoint and link to WSDL URL, here the parameters defined in the “parameters.prop” file will be used.
Repeat the steps above to configure the receiver communication channel as well. Save all the changes to the Integration project and you should the screen below;
Deploying the Integration Project
Once all the configurations are done and all the changes saved, then it is time to deploy. If the red marker appears on the integration project after saving, then it shows the configuration is not complete check the problem console to fix this. To deploy the project to the Cloud, right click on the project and choose the option “Deploy Integration Content”. A pop up is shown, asking for the tenant ID, once this is provided the deployment will be completed, if there is a problem or an error, a pop up will indicate this.
Click on ok and the deployment will be complete.
Testing
This scenario will be tested by triggering a message from SOAP UI (SOAP UI 4.0.1 other versions may give problems). To do this, the WSDL file will be loaded into SOAP UI, and the SSL settings will be done by uploading the Private Key of the Public Key (loaded into Sender System) into SOAP UI. This is done using these steps;
- File ---Preferences---SSL settings and uploading the Private Key from the Key store and the password if any.
Of great importance is the URL to be called from SOAP UI. After the WSDL file (WSDL file used on the sender side) is loaded into SOAP UI, click on the edit endpoint option and construct your endpoint in this format
https://<serverurl>/cxf/<path-defined-in-the-sender-communication-channel-endpoint>
- e.g https://<servername>/cxf/demo/blog/meterbilling
Once all this is done, then messages can be sent from SOAP UI to SAP HCI.
Monitoring
After messages have been sent, then monitoring can be done in SAP HCI. Switch to Integration Operation perspective to monitor the messages being received by HCI. The diagram below shows the sample messages received by SAP HCI and further details and different search functionalities can be used from the monitoring tool.
The monitoring screen shows different messages that have been received, some failed and some were successfully processed. Monitoring is also possible by Integration Designer/Developer using the SAP HCI WebUI interface for processed messages in the cloud!
Conclusion:
In understanding the Power of SAP HCI, these sets of 3 blogs provides a complete walk-through scenario for using SAP HCI as an iPaaS (integration platform as a service). SAP Hana Cloud Integration makes it easy! You are now able to setup the environment and configure an iFlow. We have seen that SAP HCI is a, light weight, cloud based solution which provides possibilities to use prepackaged integration content out-of-the-box and re-use existing SAP PI content. If you have questions, do not hesitate to contact me. I’m looking forward to update you in my next blogs where I will describe the new connectivity options and additional features of SAP HCI.
Written By; Abidemi Olatunbosun, Rojo Consultancy BV, The Netherlands
Contributor; Geert van den Reek, Rojo Consultancy BV, The Netherlands
- SAP Managed Tags:
1 Comment
