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

Service assignment for Secure Agent groups

Service assignment for Secure Agent groups

By default, when you create a Secure Agent group, all services that your organization uses can use the group. If your organization uses multiple services, the demand on the Secure Agent group can be high. To reduce the potential demand on a Secure Agent group, you can enable and disable specific Secure Agent services for the group.
The services that you enable and disable for a Secure Agent group are the Secure Agent services, which are different from the
Informatica Intelligent Cloud Services
. For example, if you want to use the agents in a group only for Operational Insights, enable the OI Data Collector service for the group and disable all other services. For more information about Secure Agent services, see Secure Agent services.
You can perform the following actions:
Enable services for a Secure Agent group.
Enable services when you want the agents in the group to run the connections, tasks, processes, or product features associated with a service or set of services. When you enable a service, the service starts on each agent in the Secure Agent group.
Disable services for a Secure Agent group.
Disable services when you do not want the agents in the group to run the connections, tasks, processes, or product features associated with a service or set of services. When you disable a service, the service stops on each agent in the Secure Agent group. Any connection, task, process, or product feature that uses the Secure Agent group as the runtime environment no longer runs.
Enable or disable services for a Secure Agent group on the
Runtime Environments
page.
The following image shows the
Runtime Environments
page:
The Runtime Environments page shows all runtime environments including the Hosted Agent and all Secure Agent groups. If you expand a group, you can see the agent details including the status, enabled services, host name, operating system platform, agent version, upgrade status, and last updated date and time.
The Enabled Services column indicates which services are enabled for the Secure Agent group. The Enabled Services column for the Hosted Agent lists all Secure Agent services that your organization is licensed to use. To enable or disable a service, expand the
Actions
menu for the Secure Agent group, and select
Enable or Disable Services
.
After you make service assignments for a Secure Agent group, you might add or remove agents. When you add a Secure Agent to a group, the agent inherits the service assignments of the group that you add it to.

Example

Your organization uses
Data Integration
and has licenses for mass ingestion and for Enterprise Data Catalog data discovery. The organization uses the following Secure Agent groups:
  • Group 1: Secure Agent 1, Secure Agent 2 , Secure Agent 3
  • Group 2: Secure Agent 4
  • Group 3: Secure Agent 5
By default, users in your organization can select any group as the runtime environment for any connection or any task, including
mass ingestion
tasks. An administrator can also select any group as the runtime environment for integration with Enterprise Data Catalog.
To balance the load across Secure Agent groups, you want might want to reserve Group 1 for
Data Integration
tasks except
mass ingestion
tasks, Group 2 for
mass ingestion
tasks, and Group 3 for data catalog discovery.
Therefore, you enable and disable the following Secure Agent services:
Secure Agent Group
Enabled Services
Disabled Services
Group 1
Data Integration Server
Mass Ingestion, EDC Search Agent
Group 2
Mass Ingestion
Data Integration Server, EDC Search Agent
Group 3
EDC Search Agent
Data Integration Server, Mass Ingestion
To avoid task and feature failures, you must also verify the following settings:
  • All
    Data Integration
    tasks except
    mass ingestion
    tasks use Group 1 as the runtime environment. All connections that these tasks use also use Group 1 as the runtime environment.
  • All
    mass ingestion
    tasks use Group 2 as the runtime environment. All connections that these tasks use also use Group 2 as the runtime environment.
  • On the
    Organization
    page in
    Administrator
    , the Enterprise Data Catalog integration properties use Group 3 as the runtime environment.


Updated August 03, 2020