SAP Cloud Platform Integration (CPI) Part 6 – SAP CPI Helper Chrome Extension for Easy Debugging

The JSON response is returned. Now, we will use the SAP CPI Helper Chrome Extension for easy debugging to analyze the message step by step using the artifact editor. This extension simplifies the debugging process by providing additional tools and insights directly within your Chrome browser.

As you can see there is a section.JSON reaction is returned. Presently we will go to the antiquity proofreader to break down the message handling bit by bit.

As you can see there is a section.

In this post, we will explore how to enable the SAP CPI Helper Chrome Extension for easy debugging and get acquainted with its features.

Outline of this blog series:

  1. SAP CPI Introduction
  2. SAP BTP tools and features overview (BTP, Global Account, Sub-Account, Entitlements, Connectivity, Security)
  3. SAP CPI Web IDE overview
  4. Registering a trial account and enrolling to SAP CPI service
  5. Deep dive into Cloud Integration features with real world scenario example
  6. Use cases of palette functions
  7. Adapter configurations
  8. Using Cloud connector for connecting to backend SAP systems
  9. Overview on API Management & Open Connectors
  10. Integration using Open Connectors with real world example

In short, below is the content we will elaborate in this tutorial:

  1. Use case of CPI Helper Extension
  2. Installing CPI Helper Extension
  3. Testing with CPI helper Extension

 

  1. Use case of CPI Helper Extension

On the off chance that you don’t have the foggiest idea about the CPI Partner, it is an open-source Chrome Program module that broadens the Cloud Stage Mix for certain cool new elements that helps you during improvement of Joining Streams. Commonly, we will be empowering the follow in the oversee joining content window and that also normally gets changed to Data log level after 10mins.

To stay away from this volatile development of empowering the follow level and furthermore seeing the payload, properties and header data in the different screen, we can utilize the CPI Partner expansion which tackles this large number of issues.

In the past post, in the curio proofreader I showed you a few connections/buttons in the upper right side where we had Follow, Messages, Log joins.

On empowering the augmentation, you would get these extra connections/buttons.

2. Installing CPI Helper Extension

This augmentation is just accessible in CHROME program. Chrome – > SAP CPI Aide.

CPI Assistant symbol will get added to the program expansion list. After reviving your program, you will actually want to see the extra connections/buttons.

The main 2 choices which we will utilize frequently in this CPI assistant is, Follow and Messages.

Rather than turning ON the follows in the Oversee mix content window for that IFlow, we can do likewise in the antique proofreader itself. By tapping on the Follow choice, it will get empowered.

When you communicate any message from the source framework or from any apparatus, you will actually want to see those messages in the message choice.

In the event that you have not empowered Follow choice, then, at that point, you will not have the option to see the last symbol in the message popup, which you can see the distinction in the first and second message featured.

3. Testing with CPI helper Extension

IFlow developed:

We are passing the source payload to the substance modifier, where we are adding the substance type header and setting it to application/json, and we are passing the source payload for all intents and purposes.

Then the equivalent is shipped off a switch. We have 2 courses.

Highway 1 – has a condition which whenever fulfilled, the XML payload is shipped off XML to JSON converter, and the message is finished.

Route 2- default route.

Each switch should have a default course, where in the event that other course didn’t fulfill the condition, the default course will get executed.

For this situation, default course is planned to end message.

Highway 1 is coordinated to XML to JSON converter.

The prefix is utilized as colon (:) and stifle JSON root component isn’t empowered. On the off chance that its empowered, the root hub of the JSON design will be smothered.

On the off chance that streaming choice is chosen, assuming the payload needs exhibit structure, it is conceivable. Presently let us consider bigger XML payload where we have different youngster hubs and each kid hub require [ ]. Either pick All or Determined ones (for indicated ones, we really want to specify the XPath for which exhibit design to be given).

That is all there is to it. We will begin testing the IFlow.

Prior to tapping on SEND, empower the Follow choice in the curio. Then click on SEND.

JSON reaction is returned. Presently we will go to the antiquity proofreader to break down the message handling bit by bit.

As you can see there is a section.

Click on the last symbol.

After tapping the inline follow symbol, the IFlow will be featured with green tone (if totally fruitful) on the message stream way.

You can likewise see that the default course isn’t displayed in green tone, in light of the fact that the highway 1 condition got fulfilled, consequently the highway 2 isn’t called.

Along these lines, we can perceive how the message got handled.

The second most significant thing is the survey the bit by bit data in the message stream. By tapping on each step, you will actually want to see the header, properties and payload data at that Particular step.

Note: In the event that you click on the substance modifier (as in above model), you will actually want to see header, properties and payload data of the past step. To see the substance modifier step data, then click on the subsequent stage.

Tapping on Satisfied modifier:

As I have added the Substance type header in the substance modifier, how about we check in the event that it got passed. To actually look at it, double tap on the subsequent stage of the substance modifier. Double tap on the Switch step.

Presently we will tap on the End 1 occasion to check whether the source payload got effectively switched over completely to JSON.

By doing so, we will be able to check the logs at each step effectively. This will be incredibly useful, especially for complex interfaces. You can also use the SAP CPI Helper Chrome Extension for Easy Debugging to copy, decorate, or download the payload for your reference. That’s all there is to it. I hope you have learned something new here.

 

YOU MAY BE INTERESTED IN

Future of ABAP on Cloud

Building Cloud-Native ABAP Applications: A Guide to Modern SAP Development

ABAP Applications for the Cloud: Modernizing for the Future

 

WhatsApp WhatsApp us