Posts

IRT 2.2 Release notes Testing of SAP PI, Cloud Integration and Changemanagement

/0 Comments/in /by

Yesterday we release the IRT 2.2 to make testing even easier. This release contains a lot of new functionality that makes it a lot easier to test your system.

One of our visions is to make an all round change management tool that allow you to find errors, fix them, document the changes, and test it. We have added the first part of this which is to support the change management, this will allow you to document what is going on in the landscape.  So now we have a link form ICO all the way to message mapping. This will allow us to ensure that you test the interfaces before you make any release.

You can see the video for a presentation here.

 

Cloud Integration. We have now added the option to start testing SAP Cloud Integration (CPI aka HCI) . It is made possible by the new option to trace information so we don’t need to make modifications to your iflows to test it. We can do a regression test with the HTTP adapter now, and hopefully will be able to add some more adapters in next release. For other messages, you need to use the baseline testing, where you will be sending the same message again. We will add more functionality to this testing to make it easier to do regression test for all adapters.

Baseline test cases. This is to make integration with Workflow tools like HPE UFT that already creates a set of number of messages to the SAP PI/PO system. So instead of IRT is sending test messages the sending system is creating the messages. The test would then compare that the same messages are sent and compare that they are processed in the same order. This is also a function we are using when testing with SAP Cloud Integration.

Change Tracking Tool. In the change tracking tool we have added the ability to see all repository objects and what is changed. So you can see where in an object it changed, we will add the option also to do a comparison in UDF and Message mapping in a future version. The cool thing is that you now can see where a message mapping is used and in which ICO/iFlows it is used. This will give users the option to run test report that covers the things that have been changed. We still have to add a few links.

 

If you are ready to start testing your SAP PI/PO/CPI solutions better then have a look at the Figaf IRT tool that allow you much better testing.

Retiring the SAP PIDocumenter and Diff tools

/0 Comments/in , , , , , , , , /by

I have retired my documentation tools.

The reason is that they used an old form for documentation and SAP PI/PO did no longer support the use of XIM files. It was therefore not as much the tool was used anymore.

I have created a short guide to how you can export your mappings to an Excel sheet with NWDS. I’m not to found of the layout of it but it does support standard and also export UDFs. So it is an easier way to make the documentation.

How to document SAP PI/PO Mappings using NWDS

How to use the SAP PI Message Mapping documenting tool

/0 Comments/in , , /by

For a couple of years I have been developing on a tool for making it much easier to document mappings. The tool is available as open source, so you can try to use it for yourself.

There is also a running version available on figaf.com that allows you to test out how it works and get instant results back. This is the preferred way to use the tool because you don’t need to install PHP and the project. It is though useful if you want more control of what you are putting into your documents, or don’t want to send your mappings to my server. I do delete the mappings every 15 minutes, so I don’t keep them longer.

I don’t think that I have created a video that shows what the tool can. So that is why that I’m creating this video now. It is really simple to use.

The only thing you need to care about it to export the mapping this is done my pressing CTRL + SHIFT + =, and then you can download the mapping.

There are 3 features with the tool that is useful.

  1. To make documentation simply upload the XMI file.
  2. To copy the comments that you have filled out in a document, you can upload the old excel document and then it will be possible to see the comments.
  3. Find the difference between two different mappings or versions. The tool will show what is different between the documents.

The difference tool is really useful when you don’t know what a person did last time or what a patch contained.

Check out the video, which will guide you thru the process of steps of the documentation.

Start using it now http://figaf.com/services/pi-documenter 

Presentation on Easy documentation in Belgium

/0 Comments/in , , , /by

I will be hosting a presentation on how to do easy documentation in Belgium. SAPience.be the Belgian SAP User Group is having a meeting on the 29 September 2011. It is the day just after the Global Special Interest Group for SAP PI is having their meeting. It is nice to be able to combine two events with each other.

The agenda can be found at

http://www.sapience.be/event/sapiencebe-technology-commission-topic-pi

I’ll be talking about how to document SAP PI scenarios and message mappings.

I hope to see you in Belgium otherwise; we may meet in Teched in Madrid.

SAP PI documentation kit

/0 Comments/in , /by

It may not have been something that we have promoted a lot from this page.

We have created the SAP PIArchitecture page where we will deliver different products relating to how organizations use SAP PI. We plan to make more products availed in that space.

The current project that we are promoting is the SAP PI Documentation Template a package that allows you easy to get started with documenting your SAP PI documents. The price of the product is only 97$, which is probably the cheapest prices product in the SAP space. I’m considering raising the price soon, I have gotten so much great feedback on the post that I can justify a higher price.

This package will improve your documentation of SAP PI/XI scenarios. The bonus is that it is much easier to create the documents and to keep them updated.

The goal is to make the most actionable document and only write the content that really makes a lot of sense.