Today on the show I’m going to do something a little different. Instead of inviting a guest to join me today I’m going to talk a little about OPI or Operational Process Intelligence. SAP OPI is a product that…
“offers real-time end-to-end process monitoring combined with pattern detection, analytics, alerting, and response management. It gives business users real-time visibility into processes and the ability to respond swiftly – enabling better, faster decision-making to achieve greater agility in business operations.”
OPI is helping out with BAM(Business Activity Monitoring). I first encountered BAM back in 2006, when I was working on writing a bachelor assignment. The goal is to give better information into what is happening an organization. Which processes were taking too long time and where to improve them and give real-time monitoring if anything was failing. This is the goal of SAP OPI. So it was only in 2015 that I got a chance to work with OPI in practice at a customer site.
I also created a video on them as an alternative to the podcast. Same content just saved on youtube.
In this podcast I will cover the following things.
- BPM and show how runs
- Process phases and to identify what needs to be done
- Getting BPM process information – You need a Solman role in SAP PRO
- Reporting information from BPM requires the use of data source in the BPM flow
- Some KPI easy to use like a number of processes or duration of steps.
- Complex take bit more work like % of processes that worked.
- HANA development you will need to learn a lot of HANA to be a good developer
- No SP for 1½ year, so it does not seem like a tool that has a lot of future.
- It would make sense for SAP to move it to Cloud Platform in some form and then have integration tools to get data
- Process Miner – Celonis is SAP tool to understand what is going on in a process.
Today we are going to discuss API management with Bram Keijers who works as an SAP Integration Consultant with Proxellence. Most of the company’s clients are using integration middleware and so API management is just starting to be backed up by customers. It’s still a relatively new feature having only been released by SAP three years ago.
Bram tries to convince clients to use the API management feature for any services exposed to an SAP gateway. Suppose a customer has an SAP backend system like ECC that is providing employee data to third parties. If another third party needs to access the same data the old method was to create an entirely different interface and another integration flow. What you can do with API management is to create a central interface and there you can govern access to all third parties. That means it’s going to be a lot cheaper and easier to get your end point exposed.
The price is fairly affordable. There is a cloud platform pricing calculator that you can access here. €180 per month will cover a million calls per month. Bram really likes the new consumption based pricing. It’s cheap enough that new customers can try it out for a few months and experiment with it. SAP’s strategy is to allow customers to try different parts of the platform at a low price.
Recommended places to get started with SAP API management
API management overview:
Building & Consuming API’s:
part 1, configuration and API portal: https://blogs.sap.com/
part 2, Developer portal: https://blogs.sap.
OData services discovery in API Management:
If you have any other questions about SAP API management you can contact Bram here:
Today we’re going to return to the subject of testing and look at another case study. This time we’re joined by Pieter Atling who recently worked on the SAP PI/PO and webMethods upgrade at AkzoNobel As the test manager Pieter executed several kinds of testing including regression testing. At the beginning of the project, Pieter was asked to find a tool that could handle some automated testing.
At AkzoNobel testing middleware is a huge task as this is for most of the companies. Over the last couple of years many interfaces have been implemented. The company uses SAP PI mainly for application to application A2A interfaces. 500 interfaces are being run over the system. The company needed to implement automated testing in order to better improve the system. Pieter downloaded one of the earliest versions of Figaf’s IRT to implement regression testing.
Besides regression testing with the IRT tooling also end-to-end testing is done to make sure the interface is working as it should work. The expectation is that with the help of the tool upgrades could be done more frequently so that only regression tests have to be done combined with some manual testing done by the technical teams and that the user is not involved or just limited involved. But Pieter thinks as the use of this tool becomes more commonplace there will be more confident in it’s use.
The approach how regression testing is done with IRT, is more or less the same as the approach followed for regression the webMethods platform that is also used by AkzoNobel.
Pieter feels the tool is really useful for fast growing companies who depend on SAP PI for their delivery process. Without a good regression testing tool problems with SAP PI can become a bottleneck. Convincing the development team to use the IRT was fairly easy because of it’s ease of use.