Skip to Content

HCP IS / HCI – Enabling Integration Flow Trace Capability – Do It Yourself From Now On!

One of the most used features of HCI during the Development of your Integration Flows is the Trace Feature of your HCI. This has been described in multiple blogs and locations and if you are new to HCI would suggest reading through this blog on how HCI Tracing Works – Blog 1: Tracing Capability in SAP HANA Cloud Integration (HCI-PI)

If you have used this feature or tried to use this previously, the biggest frustration for this had been that you had to raise a Ticket to SAP to your HCI Tenant Operations Team and wait for the Tracing to be enabled. Also, over the past few months, SAP Tenant Operations Team had also enabled this feature for only 24 hours which meant, you would need to raise another ticket after 24 hours or use other alternates like the one described in my other blog – HCI – Payload Logging using Groovy Scripts – Part 1

Well, the good news is that SAP has listened to this frustration among HCI Developers and has provided the power back to the Developers. From now on you can enable the Trace of your Integration Flows directly and no need for SAP Support to get involved.

Enabling this is as simple as below steps,

  • Make sure your Tenant Node and your Eclipse Tools are updated to the latest versions.
  • Go to your Node Explorer and double click on your node.
  • You will now see a New Tab called –Trace Configuration. Select this Tab
  • Select your Integration Flow ( CurrencyConvertorSOAP2SOAP in my case ) and select the option Enable.

That’s it, with this you have enabled Trace for your Integration Flow and you can now monitor your Integration flow and view the Trace of your Integration Flow. Do note that your Trace is enabled only for 10 Minutes and post this your trace will expire.Documentation on this feature and the roles required etc are available on this link : Trace Configuration Editor

This is an excellent feature to use when you perform your HCI Development and one that I think will make everyone’s life easy. Do note that the Trace is enabled only for 10 minutes and the payloads are deleted post the 10 minutes. Hence, for any long term payload logging it makes sense to follow the method discussed in my other blog : HCI – Payload Logging using Groovy Scripts – Part 1

You must be Logged on to comment or reply to a post.
  • Thanks bhavesh for posting this.

    Good to Know that no additional support/ticket is required to enable this feature..

    In case if we require more than 10 we need to again relay on support team for enabling for longer period ? Any clue on this ?

    Thanks & Regards



    • Hello Rajesh,

      Assume Activated Trace at 00:00 Hours

      • Any messages received from 00:00 to 00:10 Hours ( for 10 minutes ) will have the Trace Enabled.
      • Assume Message 1 received at 00:01 Hours, this message will have the trace data till 00:11 Hours
      • Assume Message 2 received at 00:05 hours, this message will have trace data till 00:15 hours. and so on.
      • Message received at 00:11 Hours will not have the trace enabled.

      Is there a way to increase this duration from 10 minutes to XX minutes, I would say - it would be a ticket with your HCI Operations team and a difficult fight post that.

      For any long term logging, I would suggest using the Groovy Method I have posted as a link in this blog.



  • Bhavesh, you mentioned above "Make sure your Tenant Node and your Eclipse Tools are updated to the latest versions". How do we update our Tenant Node? Is there a cost associated with this?