Application Plug-ins bring Control‑M functionality to your external, packaged application environment. Control‑M provides application plug-ins that enable Control‑M/Agents to interface with the external applications.
Before you can define a Job, you need to create a connection profile in the Configuration Domain, which enables you to connect to the required application server. A connection profile contains the connection parameters to a specific application server, such as hostname, username, password, and application specific parameters. This enables your users to connect to the required application server with only the connection profile name.
In Control-M, you can manage the following connection profile types:
Centralized connection profiles: Enables you to store all connection profiles in the Control-M/EM database and are available to all of your Control-M/Agents in your environment. It saves you time and resources and there is no need to define connection profiles for each Control-M/Agent. For example, instead of updating the username and password for each local connection profile on each Control-M/Agent, update the centralized connection profile, sync, and it’s available to all relevant Control-M/Agents. In addition, if a Control-M/Agent host is no longer available, you don’t need to recreate the connection profile. Connection profiles are synced continuously to Control-M/Server. During job execution, Control-M/Server sends the required connection profile details to the Control-M/Agent.Centralized connection profiles are unique by name and application type.
Local connection profiles: Enables you to view and edit existing connection profiles that were created for each Control-M/Agent.