SAP PI to SAP CPI migrations
The SAP Cloud Integration Kit is the Swiss Army Knife for SAP Integration. Make sure that most of what you need as a developer is effective for development.
A key part of cloud platform integration. So you have
API management for external access and security
Open the connector for easy connection to all types of platforms
You can use enterprise messaging to use messaging services.
Integrated content consultants accelerate business-based mapping
After the migration, there is a solid platform for consolidation.
The correct time to migrate
It varies by roadmap and the right platform plan.
For more information about which platform to choose, check out the SAP PI/PO and SAP CPI posts.
In many cases, SAP CPI is a better choice than SAP PI/PO.
Technology flow in the afternoon
When ipc is not currently supported
From prep to prep. Built-in cells have been published, allowing users to run on the server in their own environment. If your integrated system is hosted in the cloud anyway, it may not matter.
B2B consolidation: TPM and EDI support is a bit late. There is an intelligent content advisor that can perform new B2B mapping functions faster. However, feature monitoring, archiving, and partner configuration are missing.
If you have a small number of interfaces of the last two types, this is not a big deal. If you plan to migrate EDI partners from the 100s, CPI may not be the right platform right now.
If the interface is less than 50, it may be useful to perform a migration. After that, you will have one less processing platform.
If you are currently using SAP PI/PO 7.5, it may not be worth the forced migration, but it makes sense to migrate to see the benefits more quickly. You can then check that the platform is available.
The migration step
As with any migration, there are steps you should take to ensure that you are performing the correct migration and preparing it correctly.
Use integrated mapping
You must understand the interface you are currently using and the patterns it follows. You should be familiar with the possibilities of the set of interfaces you are using.
You can start with an overview of message monitors and see what’s used.
Build a migration PoC
You must create a PoC for several different types of interfaces so that you know how to control each interface and migrate it.
- Test the error handling process.
- How do I use different types of groove modules and scripts?
- Learn how to test the interface
- Create some templates to use from this template.
- Learn how to support it in the future
Redesign the i style
SAP CPI is a new platform that provides a new model for consolidation. SAP PI/PO requires the development of non-standard traffic to support certain business requirements. It can be designed to better support this process.
BPM (e.g. ccBPM/BPMN) is used to process technical processes. It can be mainly condensed into a stream
Search tasks to retrieve additional data or set status.
Can be replaced with an “adapter” that opens the connector
The location where the bridge or pi is transferred to the PI.
Other places with PI that can be bounded as a standard.
There are other situations where you can look at different levels of processes to improve integration.
Then, in some places, it no longer makes sense, which greatly reduces the credibility of the integrated system. Well, you don’t need to create integrations, but there may be new ones that CPI can support.
Network scheduler or reverse agent
If you have a soap or rest interface, go. Instead of sending data to SAP PI, you can modify the web data distributor and transfer it to SAP CPI.
You need to find a way to override authentication.
The idea is to simplify communication with partners and reduce friction with them.
It can also be used if you have another reverse proxy or API management.
- New Cloudiness
Such a migration is a big task. Cf is the platform of the future, so it’s a good idea to migrate directly instead of migrating again within a year or two.
The only best place for Neo is a license for small installations.
- Plans to learn
Migration is a learning journey. You need to know how the platform supports your integration needs and where it doesn’t. Next, you need to be able to resolve these parts.
The way the integration is performed and monitored is different, and it makes sense that it takes time to improve the process.
- What is your version?
Migrating by wave or version. Some versions must be scheduled so that content can be published along the way.
First edition: This must be an iteration. It has several different interfaces and covers several different patterns.
For internal systems, it’s better, so it’s easier to come back when something fails. And there will be things that don’t meet expectations.
Then, in terms of risk, create a meaningful version where changes usually occur.
The outside world needs to be involved so that integration continues to work. To manage integrations, you must search for system owners and internal system partners.
Some of the information you need is:
- IP range used to send data
- Server IP and authentication
- Performance changes
- Go on a live date
- Reverse the program
- Depending on their relationship, some couples may have difficulty accessing it.
Protected by API management
If you have a public URL, we recommend that you use API management to ensure proper access and security. This allows you to monitor partner transactions and ensure that the integrated system is not overloaded. Switching between CPI platforms is also easier if changes are required.
Create a repository
You must create a repository for all the artifacts that you want to reuse. This is a standard XSD or slot script that is used in multiple locations.
Figaf tool has the concept of SAP CPI for stocks. This allows you to track all the places where the object is used, and if you change the object, you can update it on other platforms.