Posts

SAP PIT sp 17 first look and compared with Figaf IRT

We now have gotten SAP PIT the test tool for SAP PI/PO upgraded to SP 17. 

SP 17 was released Thursday 27 February you can see the release notes here

It contains the following updates

  • PIT: Developments & bugfixes for SP17
  • PIT: new UI5 based web interface for PI Test tool
  • PIT: Scheduled Test Execution and Verification

I did not have a look at SP16, we skipped that one. You can also create test suites, which is a collection of test executions. (Probably added in SP 16). Now it becomes interesting because you can schedule them at specific times. Like each night. Then you can see if something has happened to your test/development system. 

You have the WebUI now where business users can run the test and see if everything is okay with the test executions. They can see which fields there is something wrong with.

You can see my video of the tool here

Why Figaf IRT can save you money comparing to SAP PIT.

PIT is free and you get it with all SAP PI 7.5 installations above SP 14. 
At Figaf we do have some benefits that you will enable you to save time on your testing. 

We do have the following features that makes testing much simpler.

  1. Creating of multiply cases of many ICOs at one time and no need to edit ICO to enable the correct logging
  2. Comparison on module level, so you can see the payloads after EDIComparison so you can get to test the full flow. 
  3. Managing the test cases and update changed items
  4. Generate Excel Reports of your test cases
  5. Secure testing, so normal developers will not be able to see confidential messages but can still run tests with them. 
  6. With our tracing of changes are you able to run the tests on what is changed? And an embedded transport system.
  7. A faster release cycle, so we can deliver new functionality to make your SAP Integration easier.

To view it in real life see.

Try Figaf IRT

You can get started in less than 60 minutes with the Figaf IRT tool. In most cases, you can use your current computer to run Figaf at and use your SAP PI user to connect with.

Figaf IRT 2.12 release, Secure SAP PI Testing, Dual stack and more

In this release, we have added two quite interesting approaches for testing SAP PI/PO. 

Dual stack

If you have SAP PI dual-stack with Classical Scearnios and want to test your migration. Now we can fetch messages from the dual-stack, and want to create test cases. This is perfect for migration projects, where you want to test if everything works as expected. We have developed on our 7.4 dual-stack system, and successfully fetched data from clients 7.1 system. There will be some issues with older systems, but you can create test cases.  You can read more about the dual stack option here.

Secure messages

This is the big challenge with Record Replay scenarios. Where you take production data and rerun it on your development system. 

We created Figaf based on the assumption that real production data is what needs to be used for testing because it contains the difference in the data. Unforntaly most of it is sensitive and it could have implications of SOX and GDPR. 

That means everybody with access to Figaf can get access to the messages, so it creates a loophole in the SAP security. This means that ie externals may be able to get access to sensitive data. 

We already have an approach for handling the anonymization of data. It does require the developer to understand what is sensitive and it can be multiple values, and it will not work to test migration.
For potential clients with many confidential data that wanted to perform a migration, but it would be difficult to anonymize all interfaces. They wanted a solution to ensure end to end anonymization without external developers would have access to the payload. 

If you create test data on your productive system, Figaf IRT will ensure that all developers will only see the data scrambled data. This way they are able to see if there is something wrong with a specific field. They can see what field is affected and may be able to drive some information. They will not be able to see the specific data. If there is something they don’t understand they can ask an admin to view the difference. 
We are adding some functions over the next few weeks to 

  • Handle synchronize testing so data is not sent to the real system. 
  • Enable the user to access other SAP PI message payloads in the monitor. 
  • Enable same testing option on SAP CPI

I think this security will make it a lot easier to outsource regression testing because you don’t have the challenge if they get access to some secret data.
Improved Synchronization process

For customers with a lof of SAP standard components, our synchronization did not work. The simple query API we used timed out when listing datatypes etc. We are now only syncronizing the SAP objects that are referenced from any other objects. That way you only synchronize the real used objects. 

You can read more and see the demo here.

Improved comparison of SAP CPI iflows

We have improved the algorithm to show what objects were used in an SAP CPI iflow. You can now see which artifacts have been modified between two versions. 

Java 11 /OpenJDK

If you don’t want to use the Oracle Java license, we now also support Open JDK 11. You, therefore, don’t have to use a Java License. We will support Oracle Java for some time, it is really useful for PoC to test the Figaf tool because all SAP PI developers have it. 

Try it now

You can signup to try the Figaf IRT here.


Figaf saves Christmas SAP PI/CPI support

Christmas is the time when you would like to be with your loved ones. And not work on a support case to manage SAP Integration.

This is why we want to help you. We can give you a free 30-day trial of the Figaf tools to making monitoring of your SAP PI and CPI system much easier.

At Figaf we want to make it easier for you to support your SAP PI/CPI and API Mgt system, so you can get time to be with your loved ones and not spending time on finding and solving bugs that somebody else already have solved before. The Figaf has one generic way to handle alerts, so it is much easier for you to handle the support of the system.

We have created a little video that shows you how fast you can get started with the tool.

Try Figaf

As you have seen in the video it is pretty simple to start Figaf IRT.

You can download the on-prem version here or if you want to monitor CPI and API mgt then use the Figaf Cloud.

Governing SAP CPI with Figaf Tools Webinar replay

Managing and running an SAP CPI system can be easy. You can if you don’t have any quality control and can move everything. I have examples on fixing a feature request and move it to production in 30 minutes. No governance was made in this process. Which was not optimal nobody would know what was going on.

If you want to be able to govern the approach then you need it will take some longer. Govern is about managing the process to ensure there is proper audit trail for all changes, testing, and documentation is in place. This is something that can take a lot of manual hours to get working. With the Figaf tool we have automated the full process, so you developers, architects, and business experts no longer need to spend as much time on the tasks.

You can see the replay of a webinar below. This covers a lot of the process around change management and it even shows what is possible with the development process.

Try the Figaf tool

You can try the Figaf tool you can signup here

Figaf 2.11 is out, enabling DevOps for SAP PI and CPI

Now we are able to deliver Figaf IRT 2.11, it will enable automation of SAP Integration never seen before. It contains 150 tasks or bugs and 55k new lines of code. So it is a massive improvement we have worked on. It contains two main areas.

  • Transport and governance system
  • Migration of SAP PI/PO if you are still missing to migrate to 7.5

Transport and governance process

When we have talked with clients of the Figaf tool and our integration with CTS+. It seems like only 50% of the customers were using it. I could configure it on our system without much knowledge in 4 hours. So it should be possible for all SAP users to use it.

My these on why CTS+ it has not been implemented as much is that it is not adding much value, and is just complicating the process. You cannot really see what is in the transports and once you have imported the directory you anyway needed to perform manual steps to configure it.

That is the reason I’m stoked we have created our own transport approach. It is really simple to configure and make it possible to improve the delivery of SAP Integration. This is the way transports are supposed to be handled in the modern world.

The process is as follows, in most cases:

  1. Create a Ticket that links to the business requirement or failure created
  2. Add the objects that you have changed
  3. Figaf will then know what objects need to be tested and can test the flows
  4. You can create transport with all the objects.
  5. You then configure what channels will be like on other systems in the landscape
  6. A user can then approve the transport and allow you to transport in the landscape
  7. You can import the transport in the landscape, and it will then configure the communication channel
  8. You can create an Excel report of the change and upload it to Jira, Service now

You can see how this enables DevOps for SAP PI/PO in this video.

Migration of SAP PI/PO

The new release also enables users to help optimize the migration process. A lot of users still need to perform migration projects. It is quite a labor-intensive process that you need to perform. That is why it would make sense to automate the process. If you are looking for a migration project, recommend to check out the migration option. I have created a video of the process

Roadmap

There are still areas that we would love to improve, depending on what customers see as most important. Like how to perform validations on the QA system. Does it require running the test on that platform, or are there other functions that could make sense. A lot of the configuration on how transport should be imported is now possible it just requires users to figure out what they need to be.

For the migration support of Classical scenarios is also on the which list, but will require we can work with a customer to enable it.

If requested we can incorporate it with CTS+ so it will still run your transports and Figaf would handle configuration and documentation.

Get Started now

You can start using the Figaf tool for free. Just go to Figaf.com/IRT and signup. Then you will get a free license key you can use for the migration.