If you are the administrator of a parent organization, you can share a Secure Agent group with sub-organizations. When you share a Secure Agent group, all of the sub-organizations can run data integration or ingestion and replication jobs on the Secure Agents within the group.
Note: Share a Secure Agent group when all agents in the group run only one of the following services: the Data Integration Server service (for Data Integration jobs), Mass Ingestion service (for file ingestion and replication jobs), or Database Ingestion agent service (for application ingestion and replication jobs and database ingestion and replication jobs). For other agent services, you cannot run jobs on a shared Secure Agent group.
Share a Secure Agent group to optimize the use of available Secure Agent resources. For example, your organization contains separate sub-organizations for departments in different time zones. Each sub-organization runs data integration tasks at different times of the day. If you create one Secure Agent group for each sub-organization, some Secure Agent groups might be used heavily at certain times of the day while others remain idle. To distribute the tasks more evenly, add the Secure Agents to a Secure Agent group, and share the Secure Agent group with the sub-organizations.
When you share a Secure Agent group, the group appears on the Runtime Environments page in all sub-organizations. The sub-organization administrators cannot view the Secure Agents within the group. They cannot perform management tasks on the group such as adding or deleting Secure Agents, renaming, deleting, or unsharing the group, or changing the group permissions.
When a user in the sub-organization creates a connection or task, the user can select the shared Secure Agent group as the runtime environment.
Flat file connections in shared Secure Agent groups
If a shared Secure Agent group contains multiple Secure Agents and the group is used as the runtime environment for a flat file connection, the directory used in the connection must be accessible by all Secure Agents in the group.
If the directory is not accessible by all Secure Agents, tasks that use the connection fail if they are assigned to a Secure Agent that cannot access the directory.