Posts

Webinar replay: How to develop and release faster on SAP CPI

So, Tuesday 5., March I did a webinar on how you can make an SAP CPI development flow much faster with the use of Figaf IRT. The goal was to show how much faster using Figaf IRT would be when working with SAP CPI.

I did get some pretty good feedback on the tool and the flow we support, and that it could be useful in a number of different projects. It was pretty fast-paced but demos to show all functionalities.

In the webinar, I show how the tool can make it a lot easier to do some common tasks a lot faster. 

The support part of the process

For the support part of the process, I covered:

  • A preview of our upcoming message monitoring solution that will allow you to give monitor access to individual users and query multiply iflows at the same time.
  • Our alerting mechanism that downloads failed messages or messages marked with a specific sender/receiver. 
  • Setup rules on the alerts so you can notify a business user that something is wrong or sent the message to Jira for people to follow up.
  • How you from the monitoring tool can setup reprocessing of CPI messages where you just interduce two scripts steps into the process

Many options with DevOps

For the DevOps parts I’m covering how:

  • You can document what is changed in an iflow
  • Run an existing test case on the iflow to see nothing is impacted
  • Add new test cases to solve your problem
  • Configure the system across your landscape
  • Transport the individual iflow to your different systems

It takes just 36 minutes but will give you a different of how you are developing SAP CPI.

Are you ready to try IRT Cloud?

So, after reading this blog and perhaps watching the demo video as well, I hope you are ready to try IRT Cloud. That is when you fully understand what the platfrom is able to do for you.

If you have any questions about how to get started or other things about IRT Cloud, do not hesitate to contact me. We are eager to understand which customer requirements that we can solve.

Doing SAP CPI Transports with IRT

Once I started to make my first SAP CPI transports I did not like that you needed to transport the full package. I wanted just to transport a single Iflow and log what was changed with it, then I knew what was being changed. But it was a rather difficult process to make sure you did correctly. So I thought we could optimize the process to make it easier to apply transports for single iflows.

So we have created a flow for developers where they will make the normal changes.

  1. Save it as a version in the development CPI system after normal development
  2. Syncronize the IRT with the CPI system (by clicking the button or wait for the scheduled synchronization job)
  3. Create a ticket and assign the object version to the ticket. A ticket can correspond to a Service Request or Incident. It is possible to update the version if you have multiple attempts to fix the problems
  4. From the ticket, you then create transport with one of the Iflow on the systems
  5. IRT can then import that QA/production system. It will delete the existing iflow and upload the new version.

I have recorded a demonstration video you can see how it works

The following are we working on before it will be released.

  • Fix some of the few bugs we have seen in our test environment
  • Have a way to get the configuration in a global table, so once you import an iflow on QA it will apply the configured configuration from IRT
  • Investigate if we can upload the new iflow without removing the old version.

There may also be other ways we can integrate this both with our testing application part and make a flow that better fits with a DevOps focus of development.

We expect this functionality to be released within the next few weeks both in our cloud application as well as the on-prem deployment of IRT.

Want to try it on your own system

Try out IRT

Try IRT Cloud

News for Figaf IRT – January 2019 Improving SAP CPI and PI development and monitoring

Enhanced SAP CPI Monitor, Web integration and PI create test form error

So, lately I have been working with development of Figafs Integration Regression Tool, and I think the new stuff is pretty cool. Hopefully, it will be something that is useful for you to improve the ability to develop and run SAP CPI/PI content even faster and give you less support. If you have ideas for improvements I’ll like to hear.

Improved SAP CPI monitoring

We have improved the logging of errors. So it will download the attachments for the failed flows. Then it will be a lot easier for you to monitor and process the alerts. We have also improved the OData filter, so you can specify filters for messages that do not fail. So if you are using sender and receiver information you can setup a filter like Sender = ‘Salesforce’ and Receiver = ‘LOG’ that way you can get the payloads even if there are no errors on the CPI flow.

Support tool with webhooks

The IRT Support desktop is not the only one in your organization. This way you can setup integration with Jira, Paparduty or Solution manager. We configure to receive Jira notifications in about 1 hour with the information we got from the rules using zapier.com but you can use SAP PI/CPI for it.

 

Used Mappings report

Understand what is used on your SAP PI system of mappings, we have now added an option to show also Java Mappings, XSLT and also Message Mappings. Just use the Excel export of your configuration scenario.

In December 2018 I published a blog about this topic: SAP PI/PO Used message mapping.

Create a test case from a failed message

If your message fails because of a message mapping, you can set up a new test case to cover that case. This way it becomes a lot faster to validate that you have fixed the mapping once you have fixed the problem.

 

Want to ease your work?

I do believe that these improvements will make your work a lot easier. If you want to learn more please watch this video:

 

The last details

I also cover my newest insight about IRT in this slideshow:

 

You can try the features now on your own SAP PI/CPI system.