Cloud Application Integration
Informatica Cloud Application Integration
• Informatica’s event-driven and service-oriented application
integration capabilities encompass event processing, service
orchestration, and process management.
• These are built on Informatica’s business process management
technology.
• Its use within Integration Cloud, embedded within the Cloud Secure
Agent, makes it possible to create and consume APIs, orchestrate
data services and business services, integrate processes, and offer
data and applications services inside and outside an organization.
• Informatica’s cloud application integration capabilities are ideally
suited for service-oriented integration when you need:
• Long-running transactions that maintain state
• Short-running or transactional system integration processes requiring
integration sequences, different execution paths, or composite
transactions
• Rich semantics for parallel execution
• Timers and event triggers
• Rich event, fault, and error-handling systems that control how and
what to compensate through automated compensation to roll back a
transaction if all required steps are not completed successfully
Components
• This section describes the components of CAI’s service-oriented architecture,
including the Cloud Process Server, the Cloud Secure Agent’s embedded Process
Server, and the technologies and capabilities of the platform.
Process Server
• Process Server is a run-time and process management engine that scales to
meet the needs of the cloud and enterprises of any size.
• Execution is carried out by Process Server.
• Process Server provides several sophisticated features to ensure business
continuity and can be deployed as a cluster in failover mode to ensure high
availability.
• When deployed within Cloud Application Integration, Process Server is
used to securely partition users into discrete tenants, or IICS organizations.
• With this multitenant architecture, each IICS organization (or tenant)
shares hardware and software resources but has its own private and secure
access to CAI’s Process Server.
Process Console
• Process Console provides a central location from which to manage
and configure Process Server instances and its deployed resources
whether in the cloud or embedded within Secure Agent.
• Process Console provides a means to schedule processes and deploy
new or updated processes.
Process Designer
• Cloud users demand an easy-to-use web interface for creating their
integrations and automating processes.
• Process Designer provides unparalleled ease of use for citizen
developers to create and deploy processes to the cloud’s and Secure
Agent’s Process Server.
• Process Designer is intended to be used by a technical power user—
an automation designer’—who may or may not be a developer, but
knows the business processes and services used to accomplish them.
• This designer is designed to be easy to use yet powerful and
expressive to create any business process
Working With Assets
• If you run a Data Integration asset from the Explore
page, the Data Integration service opens in a new
window.
• The asset runs in the read-only mode.
• If you select a Data Integration asset on the Explore
page, the Data Integration service opens in a new
window.
• The asset appears in the editable mode.
Adding Web services to a process
• Process Designer exposes web services through an automatically generated WSDL
interface that you can access and use as a SOAP endpoint.
• Each web service you interact with contains a set of methods, also called
operations, hosted on an application server.
• You can invoke these operations remotely in the cloud or over a network.
• When you invoke a process that is deployed to the Cloud Server by using the
SOAP Service URL, the SOAPAction Header is set to the process name by default.
WSDL -- (Web Services Description Language) is an XML format that describes the functionality of a web service
SOAP -- Simple Object Access Protocol is the communications protocol for web services. It defines the format for
web service request, response, and fault messages. The Data Integration Service can process SOAP 1.1 and SOAP
1.2 messages with document/literal encoding.
• When you invoke an operation, you create a SOAP message and send it to the
web service, typically over HTTP/ HTTPS. SOAP is a commonly used XML-based
messaging protocol used to exchange information.
• A web service has a WSDL (Web Services Definition Language) document, an
XML description of the operations and how to invoke them. Every web service
you want to interact with must have a service name and an endpoint URL
• The caller of the web service need not know anything about the internal
details, as the SOAP interface publishes the available operations.
• For each call, the web service returns a response message.
• The response contains either the information requested or fault information,
in case of an error.
Fault handling
Guides designer
The following image shows the guide design process:
CAI and CDI integration
Informatica's Cloud Application Integration (CAI) and Cloud Data Integration (CDI) are designed to work together, enabling
seamless integration of various applications and data. CAI facilitates application integration, process automation, and real-time
connectivity, while CDI handles data integration and transformation tasks.
Here's a more detailed explanation:
1. Cloud Application Integration (CAI):
•Purpose:
•CAI enables integration between different applications, including those in the cloud and on-premises.
•Key Features:
•Application Integration: Connects disparate applications to automate workflows and exchange data.
•Process Automation: Automates business processes by connecting various systems.
•Real-Time Connectivity: Enables real-time data exchange and synchronization between applications.
•RESTful APIs: Uses RESTful APIs to interact with applications and services.
•Integration with CDI: CAI can be invoked from CDI taskflows to perform specific actions or tasks.
•Example:
•A CAI process could be triggered by a CDI task to send an email notification after a successful data load.
2. Cloud Data Integration (CDI):
•Purpose:
•CDI focuses on data integration, transformation, and management within the cloud.
•Key Features:
•Data Integration: Connects various data sources and targets, including databases, cloud platforms, and flat files.
•Data Transformation: Cleanses, transforms, and enriches data before loading it into target systems.
•Data Loading: Loads data into target systems in a structured and efficient manner.
•Taskflows: CDI uses taskflows to define and execute data integration processes.
•Integration with CAI: CDI can call CAI processes to perform specific actions or tasks.
•Example:
•A CDI mapping can be invoked from a CAI process to load data from a flat file into a database.
3. Integration between CAI and CDI:
•IntegrationOps Task Step:
•CDI taskflows can use the IntegrationOps Task step to invoke CAI processes.
•REST API:
•CAI processes can use the Informatica Intelligent Cloud Services (IICS) REST API service connector to interact
with CDI.
•Dynamic Mapping Tasks:
•CDI and CAI can be used together for dynamic mapping tasks, allowing for flexibility and reusability in data
integration processes.
•Example:
•A CAI process could be triggered by a CDI mapping to send an email notification upon successful data completion
or failure.
