Complimentary Access to Figaf to run your SAP PI/PO, CPI or API Mgt

Companies are closing down. You will be affected by your work habits.

Today Denmark is closing down, and I expect a lot of other countries follow. 

You probably will not get less Integration work. Probably you will need to implement some new integrations fast. 
We want to help you make your work easier for the coming period, so you can focus on creating integration and not having to use time on manual work. 

We have made tools to simplify your SAP PI/PO, CPI, and API management processes, and it will help you with your projects.
We can help with:

  • Monitoring
  • Transports
  • Documentation
  • Tests
  • Migrations from PI to PO (To migrate from <7.5 to 7.5
  • Git integration for CPI and API mgt

Until 30 May 2020 you can use our DevOps package to test and transport up to 100 ICOs, Iflows or API proxies. 100 Tickets to register changes and 50 Migrations from PI to PO. And use the other functionality to document, and monitor your integration. 

The tools can be set up really fast. In just one hour you can get started. For the on-prem, you can use your laptop. In most cases, you will be able to use your normal PI or S-user for the tool. There are video instructions on how to get started, and we have also improved our manual. The biggest challenge will be to get the optional agent installed on your SAP PI environment to improve the testing.

You can use Figaf on-prem or the Figaf Cloud for the duration. 

Signup here

We do hope you will find the tools so useful you will continue to use them after the complementary period. 

Please use responsible and not overload our systems, otherwise, we may need to change something. Please use your company email. We will be providing support via email or remote sessions.

I expect to conduct some free training sessions (Online of course) next week for the people that have signed up for the trial. 

There will also be a webinar on Thursday 19, with the topic of how Figaf can help you manage SAP CPI.

SAP CPI Testing, now with Mock and secured data

Testing is not really fun. But you need to perform it.

Making a good unit test for SAP CPI and testing full iflows is one of the more complicated processes. You could create some test cases but it became pretty difficult to manage

1) Testing with mock services. This is if you have SuccessFactors systems you cannot call once you want to run regression tests. Then the Figaf tool will replace calls to SuccessFactors and replace them with an HTTP call to Figaf. In the request, it will inject the expected response. So you can get to test scripts, routing, and flows.

2) Secured testing. The best test data you have is from production. This is in many cases confidential like HR data. You, therefore, do not want all your developers to see the information. That is why we have added secured testing. This ensured the payloads are masked in the Figaf tool, so normal developers only see masked data. So they will be able to determine something is wrong but to get the name of the person.

We have written a lot more about the secured testing that also is for SAP PI/PO.

You can see how this works in the following video.

3) Groovy unit tests based on the Figaf test cases you have. This is a simple way to test all your groovy scripts in an Iflow. We have bundled this with the Git integration to make it possible to run the development process simpler. This allow you to run and debug your groovy scripts and it is a lot faster to develop in that way.

Try it out

There is free trials of the tools at https://figaf.com/irt. You can get started in less than 60 minutes to try out what the tool is able to.

If you any questions email info@figaf.com and we will answer your concerns.

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.


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.