Setting the profile name in the database and configuration files for an alternative/virtual host name

This procedure describes how to set the profile name in the database and configuration files for environments that have a different interface than the local hostname. This is primarily used for cluster configurations and utilizes the BMC_EM_PROFILE_NAME environment variable. The script updates all hostname configurations in the Control-M/EM database and configuration files with this value.

To set the profile name:

1. Stop all Control-M/EM processes in the secondary intallation environment and then in the primary and distributed installation environments.
2. From a command line type one of the following:
   • UNIX: em restore_host_config –profile_name [-silent] [-name <new profile name>] [-internal_only [-host_port] [-ctm_name] [-sync_files] [-clients]] [[-password <dbo password>] or [-password_file [<file_path>]]]
   • Windows: restore_host_config –profile_name [-silent] [-name <new profile name>] [-internal_only [-host_port] [-ctm_name] [-sync_files] [-clients]] [[-password <dbo password>] or [-password_file [<file_path>]]]

   NOTE:

   • <new profile name> is the new profile name to configure. This parameter cannot be specified if the BMC_EM_PROFILE_NAME environment variable is already defined with the required name.
   • If the -silent flag is not specified and optional parameters are not defined in the command line, the script asks for the relevant input interactively.
   • If the environment is running with a local (dedicated) PostgreSQL database server, that requires modification to the database server host name, define the -reconf_db parameter and then define the -profile_name parameter.
   • If the setting is for the computer's internal communication processes only,then the -internal_only flag must be specified. Otherwise all communication configuration is affected by the new profile name. This might occur if the profile name is not configured with the DNS name of the computer. The following exception flags refer to rare usage cases where the -internal only flag is defined:
   • Use the –host_port flag when the CTL communication parameters, configured by the HostPort system parameter, need to be customized with the new profile name.
   • Use the –ctm_name flag when the Control-M/Server running on the specific host needs to be customized with the new profile name.
   • Use the –sync_files flag when there are distributed Control-M/EM installations on other hosts where the file synchronization needs to be customized with the new profile name.
   • To see specific details on the exception flag, define the -profile_name -internal_only -help flag.