Contents Overview
- What is SAP CPI?
- Why is SAP CPI used?
- Key Components of SAP CPI?
- Key Benefits?
- Sender and Receiver
- Adapters
- Types of Integration Process
- Events
- Synchronous and Asynchronous
- Content Modifier
What is SAP CPI?
It’s a tool that facilitates seamless communication and integration between different applications system and data sources within an organization.
SAP CPI enabling Cloud, integrates data Cloud services, integration across on-premise and mobile applications by consolidating, processing and publishing data quickly and securely.
Why is SAP CPI used?
- Cloud Integration
- simplified connectivity
- Data transformation and Mapping
- Real-time Monitoring and Analytics
- security and compliance
- Scalability and Flexibility
Key Components of SAP CPI?
- Integration flow Design
- Pre-built Adapters
- Monitoring and Administrator tools
- Graphical Mapping tool
- Deployment options
Key Benefits?
- Reduced integration costs
- Improved Productivity
- Enhanced Agility and Analytics
- Real time Monitoring
Sender and Receiver:
The sender represents the system that initiates the data transmission while the receiver is the system that receives the data.
The sender is the source of the message, and the receiver is the target system where the message is delivered.
The sender is connected to the start of the Iflow and sends data to the integration process. While the receiver is connected to the end of the Iflow and receives the processed data.
Sender is act like our outbound message and receiver is inbound message.
Adapters:
Adapters are used to connect different systems and applications.
HTTPS Adapter: A lightweight adapter that can exchange data between systems over HTTPS protocols. It supports various message formats, including XML, JSON and plain text.
IDOC: The IDOC adapter enables SAP Cloud integration to exchange intermediate document (IDoc) messages with systems that support web communication via SOAP services.
OData: Allows users to communicate with an OData API using the OData protocol.
SFTP (Secure File Transfer protocol): The SFTP Adapter connects an Integration tenant to a remote system using the SSH (Secure Shell) file transfer protocol system to write files to the system.
Definition - SFTP adapter to encrypt and exchange sensitive business data between trading partners.
(RFC) Remote Function Call: It is a standard SAP interface that allows communication between SAP systems and other systems. It enables the exchange of data and execution of functions in remote systems.
SOAP(Simple Object Access Protocol) Adapter: It allows you to exchange SOAP messages between remote clients or web services server and the integration server and supports security setting for signing and verifying the SOAP body.
- SOAP Adapter is based on XML.
- We can use SOAP Adapters to consume web services that are secured by a Security Token Service (STS).
When selecting the SOAP Adapter, it provides us with two options-
1) SAP RM ( Connect SAP system)
2) SOAP 1.x (Connect third party application)
SOAP Processing Setting:
- Robust : If you want to get request and response. once you send the request you want the response then to go for robust.
- WS Standard: If you don't want to see any response to the client to go for the WS Standard.
WSDL:
Web Services Description language (WSDL) file for a SOAP Call, SOAP is the standard format for web services.
CSRF:
For fetch the token we’ve to use HEAD in postman.
|
HEAD |
API will be written here |
|
Key |
Value |
|
x-csrf |
fetch |
Why have we expose endpoint?
Exposing an endpoint allows external applications or systems to access and interact with an integration flow.
Types of Integration Process:
Integration process: To define the steps to process the message transfer between sender and receiver system.
Local Integration process: To simplify the integration process we can break down the main integration into smaller fragments by using local integration process.
Exception subprocess: To catch any exceptions thrown in the integration process and handle them.
Events:
Start Message and End Message: “Start Message” event marks the beginning of a message processing flow. While an “End Message” event indicates the end of the flow, sending the processed message to the receiver.
Error Start and Error End: “Error Start and Error End” can be used only within an exception sub-process.
Timer Start: An integration flow to automatically start and run on a particular schedule.
Terminate Message: A Terminate Message event stops further processing of a message.
Synchronous and Asynchronous:
Synchronous: The message flow waits for a response from the adapter.
(Acknowledge receive to sender)
Asynchronous: The SAP application does not wait for a response from the adapter.
(Acknowledge does not receive to sender)
Content Modifier:
We use the Content Modifier step to modify the content of the incoming message by providing additional information in the header or body of the message.
Data type: java.lang.String
Headers: Headers can be access outside of the CPI. We can use headers to provide authorization.
Exchange Property: We can create property to use values within the Iflow.
from rss.livelink.threads-in-node https://ift.tt/CJdGjb2