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.


Fetching SAP PI Test messages from Dual-stack system

If you are planning an SAP PI/PO migration from a Dual-Stack system to a Single stack then this update is for you.

We have seen a lot of customers wanting to migrate from a 7.1 system to a 7.5 system. The biggest hurdle is how do you get test data for it?

We have solved the problem now. So we can fetch messages from a 7.1-7.4 SAP PI dual-stack system and convert them to a test case you can use for your ICOs. If you have a pre 7.31 system some functionality of the Figaf tool will not work, but you will be able to create test cases for your migration.

We have tested with

  • BE / Sync messages
  • Async messages that are split
  • Async messages

You can view a short demo of it here. It will take data from a dual-stack system and run the test on our new SAP PI7.5 ICO/IFlow based system.

You don’t need to install anything on the SAP PI system. You just need to ensure that you are logging both in and output messages for the flows. Then Figaf will just connect and find the messages that you have selected. In most cases, you can also use your normal SAP PI user.

You only need to add the JCO files into the libs folder where you run Figaf IRT.

We know that you may have confidential data in your SAP PI system, so we have added options to mask the test data in this release also. That way you can let contractors handle your testing, without giving them access to view your salary information.

Try it your self

You can signup to try the Figaf tool. It takes a few minutes to get started and connect to a dual-stack system.

You can signup and try it out at Figaf IRT.

Sharing SAP CPI resources

A common use case when using SAP CPI is that you want to share scripts with multiply CPI iflows. Currently, now you have to manage this your self by copy or upload scripts in all the places it is used. It makes it pretty difficult to have a good shared repository of resources.

With shared resources, you will get a repository of all the different scripts that you have and can easily check the status of them. If the resource version, you can update all iFlows where that resource is used. If you make a modification of an object it should be possible to test to validate that nothing has happened with your processing.

You can watch a presentation of the flow here.

The flow is as the following

  1. From an iFlow Resource, you select create a resource
  2. Enter a name for the resource. Shared_ will be added as a prefix to make it easier to see what is shared
  3. IRT will then add the new resource to your Iflow
    1. Make manual changes to start using it
  4. On other iFlows you can add the shared resource
  5. If a user changes a resource in an iflow the shared resource will have a new version
  6. Use can then apply the shared version to iFlows where it is used
  7. Test that the modification does not affect processing

Limitations

There is some challenge with the current setup. You cannot share message mappings primarily because they rely on the source and target schema and possible groovy scripts, that they also need to be shared. We can probably find some way to get around it. If it becomes a requirement, we can find a solution that allows you to share message mappings also.

A standard solution from SAP

It is a common request and it may be possible that SAP will implement something similar to a standard part of the development. One thing that is required for this to work is the ability to test that the change does not affect other iFlows. It should be possible to adopt our solution, so it will enable version and support testing of the shared resources.

Want to try it out

The feature will be released in the next version of Figaf IRT probably in the week of 17 June. But you can already now signup and try all the other great functions we have to make your SAP CPI life easier.

Links to your SAP Cloud Landscape

As a developer one of the things that I often struggle with is to understand what system I need to login to to develop. With PI your learn to remember that PIT is the test system. But with CPI you just have some seemingly random numbers and it can be difficult to remember. I have received my fair share of emails with links in that I often go search for. I need to create a long series of bookmarks. And all new developers need to do that. Now we have made it easier for you to access the different pages.

I also normally added new tab names for each system so I can remember which system I’m currently have open in my tab.

With the new release of Figaf IRT 2.8 we are adding a function to allow you to configure your full landscape so you from the Figaf home page can go to all the relevant systems. Since we support transport and monitoring in your landscape you will anyway need to configure all your systems in Figaf IRT. You can also register all instances to a landscape so you will get links to all the entries in your environment.

The new homepace of Figaf IRT now look like this.

New Figaf IRT homepage with links to all your SAP Integration tenants or systems.

From each landscape you can then go to the relavant tennant and links. You can have multiply landscapes of each.

  • For API management it is both the developer portal and the API portal.
  • For PI it is /dir, Netweaver Administrator, PI monitor and B2B Add-on homepage
  • For CPI it is design, monitoring and IRT monitoring page.

If you have ideas to more then let me know.

We may add links to SAP sites like status pages or Cloud Platfrom links.

This feature will be rolled out to Figaf IRT Cloud and Figaf IRT around 14 May. You can get free access on either link. We also have some other cool features making your development process a lot easier.