Posts

Test your SAP PI/PO transports

SAP PI/PO development is not just about creating interfaces, map the documents and configure the interface. There is the full change management part about ensuring you know what is transported and ensuring it is tested correctly. This is something that normally requires a lot of paperwork and manual steps. It is one of the critical things about the process, to ensure that nothing else is broken.

We have been working on a tool for making sure that the testing works better and is a lot faster to set up. We have now implemented a functionality that allows you to run the same test on your QA environment with a click of a button. We have had the option earlier but it required some manual work, now you can just select which system to run the test on and it will happen.  You can also run the tests with the key of your transports.

Check out the video on the tool and how easy it is to run the same tests again on your Test system.

 

 

The solution is designed to work together with the SAP Transport (CHARM) you just need to implement a call once the transport has been imported to ensure that the test is called with the correct system.

We have a free version that allows you to start testing your system really fast and then it has the option to also support in your development process.

It is really fast to implement the solution and get it up and run. It will probably take 15 minutes to get it running on your system.

 

 

Catch 22 for testing now fixed. Supporting test on all SAP PI/PO systems 7.31+

We got trapped in a Catch 22

We need a feature released 1½ year ago to be able to test SAP PI/PO system, without installing our modules. To upgrade customers need to test their system, but they will have to do the test manually. It would save them a lot of time to use our tool.

We can test the systems if they install one of our components, but it is not something all customers that can install non-SAP components on their PI system. That was the reason we were looking for alternatives. And to make it a lot easier to get to use our tool.

We found the web service was able to give us the payloads of the logs. We got the solution working on our development. When we tried to test it on the older PI system the web service method we wanted was not there. After some digging, we found the solution was released with a patch 1½ years ago. So we could not assist in upgrading without them having to install our component. 

I want to help the customers to use our tool, especially if they have not patched for 1½ year, so they can test better. Then it makes even more sense to test.

This is the screen we web scraping to get message payload

So now we have made an option to use a WebDynpro agent that is able to connect to the screen users are seen and downloading the messages. It will use this if the web service method for downloading content is not available. It is by no means the best solution but it is a way to solve a pressing issue.

The way we did it was to use the Chrome Developer tool to see the different request required to select the correct line, switch the tabs to the payload page and then download the message. Then find the output message and download it. There is a number of requests to view each different page, and we even had to scroll table of payload to view it all.

Check out the video on the topic.

 

If you want to try it out on your own system check http://figaf.com/irt . We even have free version so you can use it to test your systems from your laptop.

Other features added

We have been moving some functionality making the application run faster when you activate new recordings of test cases. So it should start a lot faster.

We have also been improving the functionality to recording/testing or bridges async/sync and sync/async for the Figaf IRT modules. We are also adding the function later to use the SAP logging module.

Whitepaper of what Figaf IRT can do for your SAP PI/PO or CPI integrations

Over the last 6 months, our IRT application has expanded from just being an application that facilitates SAP PI/PO testing to deal with more of the full development process for SAP Integration.  We have added the following capabilities.

  • Filter your SAP PI/PO alerts so you can see new errors and document how old errors can be resolved
  • Enable you to test SAP Cloud Platform Integration(CPI)
  • That you don’t need to install anything at the PI system to use the tool
  • Enable you to track all development objects on SAP PI/PO and CPI so you can see the difference on each one
  • Create Ticket to log which objects you have changed for any specific use cases, so you can document what you have done to solve a ticket.

    Download the Figaf IRT white paper now

    • Test all the ICOs where an object is used like a message mapping

We have had some challenging trying to communicate all of the functions that we are supporting in the process and how it worked. So now I finally was able to create a document that tries to explain all the capabilities we have in an easy to read manner.

We have tried to make it as appealing to the business but also explain what we are doing to make the life easier for integration developers.

You can download it here

If you have any idea on how to improve it, please share.

Get FIGAF IRT and start using it for free here

 

 

 

Support for you SAP PI/PO development process

I’m pretty thrilled about our latest development of the Figaf IRT tool for SAP Integration.

When I started doing XI 3.0 work I was really frustrated with the way things were documented. It was a really manual process that users needed to follow. The documentation was never updated. Now 14 years later I can see that we got a tool that can help in the cases. We can now help you really document what has changed automatically.

So a month ago I found that we could leverage the tools we had created for the IRT tool to support the full development lifecycle. Today we are releasing the first version of it. It is not perfect and there are some holes but it clearly shows which direction we can do with it. Hopefully, you will also be able to see the benefit of it.

The different steps in the process are the following:

  • Alerts are raised from a PI Message using standard alerting.
    • Create rules for how to handle alerts
  • Perform your development in Repository/NWDS
  • Create a ticket to with a link to the incident
    • Assign the changes to the ticket
    • You can see the differences I the mappings
  • The test is performed to ensure it works
    • Base on the Figaf IRT test tool that allows users to create test case fast based on i.e. production data

I have created a video to show what we are able to do with the tool.

We still have a few things to work with to with making it better and cover more of the development cycle, but it is always better with customer feedback. So if you have any things that would help in your process do let us know.

You can download the tool for free at https://figaf.com/irt

 

 

The future of SAP PI/PO development

SAP PI/PO developer are normally spending a lot of time documenting what they have been making of changes. We want to make the process much simpler for the end to end development. And capture the correct information. Not just information that cannot be used.

We have created a mock prototype of a feature we are working on. We would really appreciate some input about if this fits your organization. Please share a comment or write to dgr@figaf.com

We have the following process.

  • An incident that is triggered by the component based message alerting in SAP PI. You can easily setup rules to handle the different alerts and how to react to them.
  • Then we create a ticket, which is a new concept in the IRT tool. A ticket is what you could refere to as an Incident, Change Request, Service Request or Gap. It can have a list of status like, in development, in testing or done. You will be able to configure the list and if there should be auto numbers or you have the values in a separate helpdesk system. You can create tickets without an incident if it, for instance, is a business requirement
  • The ticket can get PI object assigned. So you can add any PI Repository or Repository object to the ticket, for instance, a message mapping or channel that has been changed for solving the ticket. When you look at a message mapping you can see which ticket it has been assigned to and thereby get information about why something was changed.
  • Testing from the ticket. It is then possible to calculate which Interfaces/ICOs to do testing on. If you are missing some tests you can add them. And then run all the tests.

You can get more information of the future of the tool by signing up for it at http://figaf.com/irt 

I have two videos about the concept. One that features the overall perspective and along with more explanation along the way.

The short direct to the point video

 

The long version with more explanation

You can get more information of the future of the tool by signing up to it at http://figaf.com/irt