Table of Contents

Search

  1. Preface
  2. Introducing Administrator
  3. Organizations
  4. Licenses
  5. Ecosystem single sign-on
  6. SAML single sign-on
  7. Source control and service upgrade settings
  8. Users and user groups
  9. User roles
  10. Permissions
  11. Runtime environments
  12. Serverless runtime environments
  13. Secure Agent services
  14. Secure Agent installation
  15. Schedules
  16. Bundle management
  17. Event monitoring
  18. File transfer
  19. Troubleshooting

Administrator

Administrator

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.
Use the Secure Agent group configuration to distribute requests if you process stateless requests or use the Secure Agent only to serve OData requests.
In a Secure Agent group,
Informatica Intelligent Cloud Services
dispatches incoming requests to available Secure Agents in a round-robin manner.
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 also use a custom load balancer by setting the
load-balance-url
Process Server property. For more information, see Process Server Properties .
For more information about Secure Agent groups, see Secure Agent Groups with Multiple Agents .
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.


Updated August 03, 2020