This procedure describes how to create a centralized connection profile in the Configuration domain of Control-M. Centralized connection profiles are stored in the Server database and are available to all of your Agents in your environment. It saves you time and resources and there is no need to define connection profiles for each Agent.
From the Configuration domain, click and then select Centralized Connection Profiles.
The Centralized connection profile tab appears.
From the Add connection profile drop-down list, select the required Plug-in.
The Add connection profile pane appears.
The drop-down list shows only plug-ins that you have installed.
Do the following:
In the Connection profile name field, create a name for the connection profile.
In the Description field, describe the purpose of the connection profile.
For each field, type the required value, as described in one of the following:
- Informatica Connection Profile Parameters
- AWS Connection Profile Parameters
- Azure Connection Profile Parameters
- Databases Connection Profile Parameters
- Databricks Connection Profile Parameters
- MFT Connection Profile Parameters
- NetBackup Connection Profile Parameters
- Power BI Connection Profile Parameters
- SAP Connection Profile Parameters
- Hadoop Connection Profile Parameters
Review the connection profile details, click Test, select an Agent to test the connection profile, and then click Test.
If the test completed successfully, the connection profile is validated and you can now define an application plug-in Job. If the test failed, review the error message and test it again.
The centralized connection profile was created successfully.
Verify that you have installed Python 3.8.0 on the computer where you are running the script.
Verify that you have the Requests Python package installed on your computer by running pip install requests.
It is recommended to save a backup of your local connection profiles.
The local connection profiles file is located on the Agent computer under the cm/<plugin>/data directory accounts.dat or accounts.xml.
If the certificate is not signed by a CA, a warning message appears. The script continues to run.