In this blog we will look at the monitoring and error handling part of HANA Cloud Integration Process Integration (HCI-PI).

Monitoring

Monitoring can be done both from Eclipse based IDE as well as via the web based user interface.

Eclipse IDE

From Eclipse IDE open perspective Integration Operations ->Node Explorer (View). Double clicking on the tenant node opens up the message monitoring for the respective tenant. Clicking on a particular message will open up the message processing log (MPL) in the Properties view.

Now we can gather some interesting facts to do an end to end trace of our message using the MPL.

Let’s take the example of a particular message (SOAP->IDOC) and examine various aspects.

As shown above the HCI CXF service end point is https://iflmapc4cts1avtc4cd-ts1.bsn.neo.ondemand.com/cxf/ERP/COD/ADR3MAS.ADR3MAS03, where the consumer sends the message

Here we can see the message ID from the sender system in this case a SAP cloud system and using this message ID we can search the consumer message in the SAP Cloud system

Here we can see three message mappings are getting executed one after another (An analogy is the message mapping steps in operation mapping in PI)

Here we can see the destination URL to which HCI is sending the message and the URL configured in the receiver IDOC adapter

Here we can see the IDOC number from the destination system and with this we can track the message end to end at a technical level.

Another interesting fact about the monitoring is we can see the all the deployed artifacts and their runtime status as shown below (I have used filter to narrow down the search)

Also we can see all the services for the iFlow artifacts which have runtime status as started as shown below

Web UI

Web UI offers a more navigation friendly UI based monitoring view and can be navigated using the URL

https://<HCI tenant URL>/itspaces/#shell/monitoring

Here we get a consolidated view for runtime status of both Integration artifacts and Messages in a single shell and can be navigated using the hyper links for more detailed analysis. (To keep the blog short I am not getting into the navigation details)

Note: Not all features are currently available via the web ui for example we can not see all the services deployed to the specific tenant using the web ui.

Error Handling

Below I have provided some frequently occurring exception in HCI and their possible resolutions.
Couldn’t parse stream.” caused by “Invalid UTF-8 start byte 0x8b (at char #2, byte #-1)
Solution : The Compress message option should be checked in iFlow sender

CreateSequence was not recognized (For asynchronous messages)
Solution: Make sure the RM-Protocol is set to SAP-RM and Data transfer scope is set to Basic in SOAMANAGER on the back end system.

NullPointerException:while trying to invoke the method java.lang.Class.newInstance()
Solution: This error usually occurs in request response (synch) scenarios, reason is the message mapping jar files are missing in the iFlow Project

MustUnderstand headers … are not understood (For synchronous messages)
Solution: Message ID protocol should be set to SAP message ID or Suppress ID transfer in SOAMANAGER under messaging     for the Consumer proxy

With this we come to the end of the HCI Application Edition Learning series. Thanks for all the valuable feedback and happy learning!!!