Scribd
Upload
7 views3 pages

Lesson1 - Introduction

The document discusses the key features and capabilities of CPI including data security, compliance through logs, master data synchronization, ease of implementation and cost, ability to handle upgrades, end-to-end monitoring, support for non-SAP and customized systems, and end-to-end monitoring capabilities.

Uploaded by

Anjani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views3 pages

Lesson1 - Introduction

The document discusses the key features and capabilities of CPI including data security, compliance through logs, master data synchronization, ease of implementation and cost, ability to handle upgrades, end-to-end monitoring, support for non-SAP and customized systems, and end-to-end monitoring capabilities.

Uploaded by

Anjani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Data security is a major challenge.

We can’t expose data to any public network because there might be


attacks on the system and the data might be stolen. First we encrypt the data, then transfer it and then
decrypt it and use it for further processing. CPI provides full data security.
Compliance is storing the logs. Suppose we are developing any integration solution and after the
development an audit will happen. In that audit the integration solution should have the the complete log
that all things have been performed. The integration solution should be able to show the logs about the
actions happened in the IFlow.
Master data synchronization – In an eco system there can be different types of systems. There can be
master data like Material master data, etc. This master data should be synchronized with every other
system because transaction data is created based on master data. If the master data is not synchronized
then we face problems while creating transaction data. Master data is not frequently created. It is created
one time. Transaction data is created on a daily basis like SO number, receipt number, etc. CPI provided
very good facility in synchronizing master data.
Time to implement and cost to implement – Any integration should be time and cost effective. CPI
takes very little time to implement. Compared to other integration solutions, CPI is also cost effective.
Upgrade Suppose we have established an integration between systems A and B. Suppose either system A
or B gets upgraded, your integration solution should be robust such that it should be adapting the upgrade.
Like, the desigh of the integration solution should not be effected by the upgrade. Also, if the integration
solution is upgraded, the system should not be affected. CPI is capable in handling and adapting to the
upgrades.
Monitoring Suppose we are sending a message from system A to system B, we should be able to see
what is getting transferred. This is called monitoring. CPI provides end-to-end monitoring facility. We can
debug IFlow as well.
Non-SAP systems, Customized SAP and Cloud Integration – it is very rare that in an eco system all
the systems are SAP systems. The integration solution should be able to communicate with non-SAP
systems, customized SAP and cloud systems. CPI is able to handle non-sap systems, customized SAP
systems and cloud systems as well.
Support There might be scenarios that requires daily base monitoring wherein a dedicated team has to
provide support to the IFlow. The team shouldn’t be too big. CPI doesn’t need big teams to provide
support.
End-to-End Monitoring Suppose we are sending data from one system and it is going to another system
and so on. CPI provides a facility to monitor data or message transferring from one system to another.
Integration technology Apache Camel. Good integration framework. The backend of CPI is Apache
camel.

You might also like