Table of Contents

Search

  1. Preface
  2. Secure Agent services
  3. API Microgateway Service
  4. CMI Streaming Agent
  5. Common Integration Components
  6. Database Ingestion service
  7. Data Integration Server
  8. Elastic Server
  9. File Integration Service
  10. GitRepoConnectApp
  11. IDMC Data Gateway Service
  12. Mass Ingestion (Files)
  13. Metadata Foundation Application
  14. Metadata Platform Service
  15. Process Server
  16. SecretManagerApp
  17. Configuring Secure Agent service properties

Secure Agent Services

Secure Agent Services

Deploy to a Secure Agent group

Deploy to a Secure Agent group

A Secure Agent group contains multiple agents. You can deploy an asset to a Secure Agent group.
Depending on the business requirements, you can use the Secure Agent groups to deploy Process Server services using the following Secure Agent configurations:

Secure Agent load balanced configuration

Use the Secure Agent load balanced configuration to distribute requests if you process stateless requests or use the Secure Agent only to serve OData requests.
When you deploy an asset to a Secure Agent group, you use a load balanced configuration.
Informatica Intelligent Cloud Services
performs the load balancing. You can add multiple Secure Agents to a group to balance the distribution of tasks across Process Servers. At run time,
Informatica Intelligent Cloud Services
dispatches incoming requests to available Secure Agents in a round-robin manner.
You can also use a custom load balancer by setting the
load-balance-url
Process Server property. For more information, see Process Server Properties.
All Secure Agents in a group use individual PostgreSQL databases. When you deploy an asset to a Secure Agent group, all Process Servers within the group receive details about new or updated asset definitions. However, the other Process Servers in the group do not receive details about the execution activity of an asset. For example, if a Secure Agent within the group fails during process execution, the process does not continue to execute on another Secure Agent within the group.
The following image shows a sample configuration where process X is deployed to Secure Agent group A:
This figure shows process X deployed to Secure Agent group A. Group A has three Secure Agents with individual PostgreSQL databases.
If you modify and re-publish process X, all three Secure Agents receive the updated definition. Any Secure Agent can execute the process.
For example, if the process is invoked and Secure Agent 1 and Secure Agent 2 are unavailable, the load balanced configuration ensures that Secure Agent 3 executes process X. However, Secure Agent 1 and Secure Agent 2 do not receive information about whether the process has faulted or completed successfully. If Secure Agent 3 stops while executing the process X, the process does not execute further.

Secure Agent Cluster configuration

Use the Secure Agent Cluster configuration if you are processing long-running processes and need to perform recovery of payload processing from one node to another. A clustered configuration shares a single database server with all the cluster nodes.
A Secure Agent Cluster is an agent group with a master Secure Agent. You can deploy an asset to a Secure Agent Cluster.
When you deploy an asset to a Secure Agent Cluster, all Process Servers receive information about process execution activity. The master Secure Agent receives information and informs the other Secure Agents. If a Secure Agent fails during process execution, the process continues to execute on another Secure Agent within the cluster.
To enable the cluster configuration for a Process Server, click the
Runtime Environments
tab in Administrator. In the
System Configuration Details
section, set the
cluster-enabled
Process Server property value to
true
as shown in the following image:
This image shows the cluster configuration enabled for the Process Server.
All Process Servers in a cluster share the PostgreSQL database of the master agent.
To define the master Secure Agent, use the
primary-node
Process Server property. For more information, see Process Server Properties.
The following image shows a sample configuration where process X is deployed to Secure Agent Cluster A:
This figure shows process X deployed to Secure Agent cluster A. Cluster A has three Secure Agents, with Secure Agent 2 as the master. All Secure Agents in cluster A use PosgtreSQL database 2.
If Secure Agent 3 starts executing process X but stops midway, either Secure Agent 1 or Secure Agent 2 continues to execute the process.
For more information about Secure Agent groups, see
Runtime Environments
.

0 COMMENTS

We’d like to hear from you!