Integration at #Impuls18 and IFG for Integration, you missed out

I’m on my way home from IFG for Integration/Impuls18 in Stockholm. IFG is the international focus group for Integration and consists of users in a lot of the European countries, I’m member. I think it was one of the more exciting conferences regarding SAP Integration that I have been to in a long time.

So SAPSA the Swedish SAP user group wanted to host us for the event and gave two rooms that we could use for presentations. So for most of the 2 days, there were two parallel sessions on SAP Integration. Most of the time it was stuff that people was implementing.

One big topic was about the Integration architecture, from design concept and implementation.

We did get some roadmap presentations of the SAP PI/PO and cloud integration products from SAP. Users and consultants were also contributing to what they have been doing for integration.
One of the big areas that are challenging at the moment is the hybrid integration that everybody is going thru to understand what to take away. In XI 3.0 days we had one tool that could solve all the challenges at that point in time.
How it is a lot different you have the option to use PI and then new iPaaS solution from SAP Cloud Integration Suite. One of the presentations cited Gartner, that the hybrid platform was that it is a toolbox and you should use the ones that make the most sense.

It does make a lot of sense to understand the architecture part beccause otherwise you will be focusing on the wrong thing, and probably ending up with something less optimal.
On a big QA session, we got talking around how rogue IT is causing challenges in the landscape. I created a video on it here

I did share a presentation on Open Connectors, which i believe is a pretty cool tool for integration. It takes a lot of effort away for doing integration and understanding what is going on in the landscape. I hope to get some time to record a video of it, because I don’t think my slides makes a lot of sense.

The other presentation was about how you can speed up your integration development on SAP PI/PO or CPI with the Figaf IRT tool. I got some good feedback on it after the presentation and interest.

I did make the mistake of going into the wrong room for a presentation and was stuck on one of the first rows in the middle. So I missed one of the Integration keynotes.

The only problem with the event was the vine at the party was 100 SEK (10 EUR), and it did not even taste good.

I do think that I need to update my guidelines for the SAP Integration webinar that I’m doing next week. You can signup for free to learn how you can implement a better integration .

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.

 

 

IRT 2.0 released you can now test SAP PI/PO for free

Ever since I started with developing SAP PI/PO testing was a big thing. There has not been any tool provided by SAP for it.

Over the last two years, we at Figaf has been working on creating a testing tool for testing SAP PI/PO. We got some customers using it, and it is improving their operations. Both when applying support packs or when checking that their new transports work as expected.

I thrilled to announce that we now support a free version of our testing tool. I guess it is also kind of scary to give away something that has cost this much to develop for free. There is some limitation on this free version but you will be able to test some of your interfaces and ensure they work. You can only test 10 ICO(Integration Objects) and save 100 test cases.

IRT is a tool that allows you to collect messages from your productive SAP PI/PO system and then process them on your development system. This is the fastest way to create a validation that your scenarios work.

See a short demo of IRT below.

It is fairly simple to install and run IRT. Install an SCA file on the SAP PI/PO system, create a user and you are ready to run it.  You can get it working in 1 hour if you got the access required.

Download IRT today and start testing your SAP PI/PO systems.

 

7 steps to a SAP PI to PO migration

Some time ago I created a webinar about SAP PI to PO migrations. I wanted to use the content and share it because it is quite useful for everybody working on a migration. I can see that it is some of the questions that I got on my latest webinar was also about the process. I do hope that this gives a better understanding of what is happening.

As with all things, there are 7 steps to make a good SAP Migration. So if you are in the process this is the steps that I would recommend that you take. It is assumed that you will migrate to a new system because it will make it easier to migrate a single interface at the time. If things does not work you will always have a backup plan.

The 7 steps are the following:

  1. Goals
  2. Current integrations
  3. Pattern mappings
  4. Resource consumption
  5. Migration phases
  6. Development
  7. Testing

The process should be very iterative because you learn a lot in the process that you can use to migrate other interfaces. I the current integration you are going to map out all your existing interfaces together with what types of pattern they are using. This information will then be used in the migration phase and how it is going you may get input on how the next interfaces can be migrated.

You can view this in two different ways. Either you can watch my Screen recording video of it.

Or view the slides here and download them if you want to be using them.

I have also created a longer article about some of the SAPs you need to consider more in details in the blog SAP XI/PI to PO migration.  It is not the same and the two have a lot in common.

Tool to get BPM context data from a SAP PO BPM

One of the benefits to having a team of developers at your disposal like I do to create my SAP PI/PO test tool is, the ability to create cool applications to solve problems. So I’m really happy that I can give a free tool away to the people that have the same challenge as I ran into.

I have a client where we were using BPM to have some user actions in. Sometimes they wanted to restart the BPM process with the same data or minor changes. I could see the payload in the BPM monitor as on below.

This did not give any information about how I could download the message. I know if the process is failed I’m able to edit the payload of a message, but this is obvious, not true if the process is completed.

There was no API for getting the data from my research at the point.

So we had to create our own tool to handle the queries.

We found the table in the database that housed the Context Data and then started understanding how it worked. The context data was encoded in an XML structure with base64. Then it was just to build a simple user interface on top of it.

It should be easy to find the correct document and so we added a function to make xpath in the data to get the correct data. So we ended up with the following UI.

 

If you want to get it. You can get it for free at http://figaf.com/tools/figaf-bpm-extractor/.

The build includes sources so you can optimize it your self.