Posts

Virtual SAP CPI landscapes

Some SAP CPI customers do not have a full 3 tier system landscape for their SAP CPI. But you may want to experience having all the systems connected and be able to test the flow. You can do it manually, with using the copy functionality, but it requires a lot of governance to keep the QA updated.

We did originally create the virtual landscape just to test, how our transport system worked because we did only have one CPI system. Now we have improved the functionality because it enables customers to take advance of our transport and leverage using one CPI system. We did earlier change Sender system to match with having a prefix with the system name.

We have now improved the functionality so the system is added to the Process Direct adapter. Here we are adding the prefix in the URL to both sender and receiver channels. You will thereby have the option to run it in a “QA environment”.

You can see a demonstration of how this works in the video.

Updated: If you import a package it will be auto deployed.

The transportation system also provide option to create Iflow documentation, and you can test the impact of a change. You can also make modification of Externalize Parameters across the landscape, so you can specify that the target URL on QA is this. Then IRT will handle the configuration once it deploys.

Try it out the Figaf IRT tool as an onpremish or use our cloud for it.

Watch the full flow of Figaf to handle SAP CPI Change Management

We have an integrated approach for handling Change Management for SAP CPI (Cloud Platform Integration aka HCI). In this video (25 minutes) I show how the full application is connected. It is a way to have a central place to manage all your SAP Integration development.

In the video I show how you can get a good change management process for SAP CPI with

  • Full traceability for all modifications made for the development, and linking with business request
  • Ability to view differences between objects and understand how they have been changed because of a business request
  • Test the process have been developed correctly
  • Configuration of Iflows across the landscape, so there are no manual steps for the transport
  • Transport of individual iflows in the landscape
  • Document all changes in the process

There is also part of the monitoring that makes monitoring of the CPI easier and enables you to setup alerting if a message is in a specific state.

If you like it and want to see how we are able to support the change management process in SAP PI/PO.

If you want to try it out then try our cloud offering for Figaf IRTCloud

How do you Document your SAP CPI Iflows

Documentation of integration has always been a strange thing. It has been pretty difficult to make sure we documented the details correctly and had enough information with. Normally you will just get some document designed to document some other thing and then try to adapt it to your integration. That will never give a good result. You may be compliant but just a waste of time if the documentation is not useful.

For SAP PI/PO we have for ages been using a Word template for the documentation of each interface. We support that with the Figaf IRT tool, so you can generate it fast. You can see an example of the SAP PI documentation here. The inspiration was to avoid having the documentation that was never updated and always had the initial version.

SAP Best practive

I did find an example of a SAP CPI template in the best practice guide. I did not like if for a few assumptions:

  • It was focusing on the wrong things that were a bit to detailed and too generic. Like a file conversion, or mapping it just has empty tabs that users need to fill in.
  • It could not be automated every well, which ment it did require a lot of user governance to host the information
  • It was juggling 3 different adapters and not showing the required details

I wanted to improve the process and make it even easier to capture the most important part of a CPI Iflow. It ended up with the following information:

  • Overview of the iFlow header information like name and description
  • History of changes logged with business requirements
  • Connection sender and receiver together with information
  • Test cases you have created for the tool
  • Flow description which is a table representation of the iflow. It will give some overview of how the different steps are connected
  • Configuration parameters configured in the full landscape, so you got some information on what is being used and the relavant resources.
  • Resources and the lat change data for them.

You can download an example of the document here for the SF to AD iflow.

There are ways to improve the document with more information. If you have anything that you think will provide value and make it easier to understand the documentation. Do let us know.

Automated documentation does have some limits like being able to update it different places, and add the extra information that makes sense.

You can try it own on your own iflows and see how it performs in your landscape.

Figaf now improves your SAP PI/PO CTS transports

SAP PI/PO Change management and documentation have not developed much. And the full cycle of development is the same. It is really a manual process that requires people are spending a lot of time on documentation.

Is your Integration Important. Do you want to minimize the downtime and failures? Then the documentation and QA important.

If you are doing spending too much time on documentation, and if you are not you don’t have enough documentation of the changes made.

We have automated the full process from start to end designed to optimize SAP PI/PO. So you can get the transport documented with all integration objects have been changed.

This means that all your SAP PI/PO transports will be

  • Documented all your development objects
  • Changed link to a business reason, so you know how have approved the change and why.
  • Tested and validated in the QA system with same set of test cases, so you know that everything works as expected.
  • Configured in once place so developers do not need access to configure production system
  • Linking with the incident system so you can get information about what is wrong with your system faster

Check out the video

Because of the above reason, you will be able to:

  • Deliver integrations faster because of an automated delivery process with less time consumption
  • Happier employees because they do not need to perform documentation manually
  • Your QA process will be a lot faster because you don’t have everything delivered automatically
  • Higher quality with fewer errors because you are able to test all integrations fast
  • Fewer differences in the productive system because people are not doing modifications in other systems

Try IRT

We also support the same change management process for SAP CPI

The future of SAP Integration PI, CPI and how to prepare your self

So yesterday, Tuesday, November 13. 2018, I just hosted a webinar about the key takeaways from SAP Teched and how to implement things based on it. It thinks it was one of my own webinars with most viewers (40). So it is an important topic. I think I missed the Gartner quote that 50% of the development budget will be about integration or something in that line.

When we were starting to see some cloud applications I did not see so many integrations. Lately, I have seen quite a number of a project involving some cloud application. I had seen that SAP would be able to provide some of the content as pre-delivered, but there are going to be so much more than you will need to develop. I just got an email from an SAP customer that they got a tsunami of cloud integration, so it is other areas as well.

Understand where you are going

On the webinar, I do cover how you can understand your own integrations and try to plan what integration you should be doing. I recommend that you take a look at the Integration Solution Advisor – Methodology. It has been updated and I have talked with quite a few architects using it and it gave them a good understanding of what they should be doing.

Roadmap

Then I cover the current state of the SAP PI roadmap, which will affect your existing integration. I do see the CPI on your SAP PI system as a good option to run some of your content. You probably want to start a migration if you are on a dual stack system, I have some resources on how you can do an SAP PI migration project. If you have Seeburger and want to migrate to B2B Add-on I created a webinar on how you can automate the migration. I also recorded a podcast on how a customer did a migration of Seeburger to B2B Add-on.

After you have been going thru your ISA-M you will have some integration patterns that you need new tools for. I’m covering SAP Cloud offerings for integration and their full iPaaS product. I think it would be wise to use the SAP tools first to see if they suit your needs and if not then you can find a better vendor for the solution. SAP will be adding new functions to the Cloud Offering to address the customers needs.

Operations

There is a need to make more integration at a faster pace. And you are probably not able to get more people on your team. So it is about making them as effective as possible. At Figaf we have created solutions to enable the development process to be a little easier from development, documentation, testing and supporting. You can check our tool Figaf IRT that can support the full lifecycle. I think it will help you improve your development of new features, so you will be more flexible and develop things faster.

Next week I’m hosting a webinar where I’ll cover how you can use the Figaf IRT tool to optimize your SAP PI and CPI development process.

 

You can watch the full video here.