Cloud Integration – New Visualization for Adapter Endpoints of Integration Artifacts
Previous releases of SAP Cloud Integration showed the endpoints of IDoc and SOAP adapters in the Manage Integration Content view of the Web application. An improved visualization of adapter endpoints is released with 2.40 version of SAP Cloud Integration. This blog gives an overview of the new endpoint visualization.
New Endpoint Visualization
An endpoint specifies where a service or resource can be located and how it can be accessed. The shown endpoint information allows the integration developer to check if the configured endpoints of an integration artifact are exposed. Administrators of remote systems require the endpoint information to connect their systems to the runtime nodes.
The new adapter endpoint visualization enhances its visualization by extending the representation of endpoints in the Manage Integration Content view in the Web application.
Following is an example of the new visualization:
With the new 2.40 release of SAP Cloud Integration the endpoint visualisation has been extended as follows:
- Sender channels of an Integration Artifact using a SOAP adapter also show its endpoint definition, i.e., WSDL definition. The definition can be downloaded, or its access URL can be copied to the clipboard
- Endpoints of channels using the AS2 or HTTP adapters are shown.
Endpoints of sender channels using a SOAP adapter are shown together with its definition, i.e., WSDL definition.
The following screenshot shows its updated representation:
The next screenshot shows the new endpoint representation of Integration Artifacts using the HTTP adapter for a sender channel.
The endpoint of sender channels using the AS2 adapters is shared across multiple Integration Artifacts. The message routing of the Integration Artifact is determined by the AS2 system identifiers plus the message subject. Therefore, we show this information together with the endpoint URL.
The following screenshot shows the new endpoint representation:
The endpoint information is used to access a service running on a runtime node. Following are examples of testing the endpoints.
Test a service
An endpoint can be tested using e.g. curl, Postman or SoapUI.
To test an endpoint, copy the endpoint URL to the clipboard via the Copy entry point URL to clipboard button in the Manager Integration Content view of the Web application. Then execute the following curl command to execute the HTTP request and print its result to the terminal window:
// // curl command line options: // -u : user id for access the runtime node // -X : HTTP method of the request // -d : file containing the SOAP message // curl -u "p12345" -X POST -d "@soap-payload.txt" https://<runtime-node>.hcisb.int.sap.hana.ondemand.com/cxf/test/cxf
Access WSDL via URL
To test the access of a WSDL definition, copy the definition URL to the clipboard via the Copy definition URL to clipboard button. Then execute the following curl command to print the endpoint definition to the terminal window:
// // curl command line options: // -u : user id for access the runtime node // curl -u "p1234" "https://<runtime-node>.hci.int.sap.hana.ondemand.com/Operations/api/WSDLDownload?artifactName=<artifact>&servicePath=/test/cxf&domainName=hcisb.int.sap.hana.ondemand.com&includePolicies=true"
I hope this blog is useful and helps you to consume the new endpoint representation offered in the Web application. If you have any questions or feedback, don’t hesitate to comment on this blog post.
Thanks for the update, Marco. Glad to see that the HTTP endpoints are now available.
Thanks for coming on to blog, Marco, and sharing this info! Looking forward to more from you!
This is really helpful information. Thanks for sharing.