|
|
|
|
|
Introduction to CTM client components installed on a Citrix machine
This best practice includes information and required steps for installing and setting up CTM client components on a Citrix machine.
For Citrix hardware settings for CTM client components, see Control-M/Server & Control-M/EM Hardware Sizing Template.
Before proceeding with CTM support, ensure that the latest fix packs are installed.
The following list includes references to setting up Control-M in a Citrix environment.
Security settings
Firewall
The firewall configuration for the Citrix client-server communication is done in Citrix.
In case the Control-M client and server components are separated by a firewall, make sure that the communication is set to a bidirectional mode (default mode).
When Control-M/ Workload Automation is configured to work in bidirectional mode, all communication channels are initiated by the client components, and callback actions are returned to the clients using the existing network sessions, rather than on new channels. In such a mode, there is no need to set any specific ports of incoming connection on the client side since no communication channels will be initiated by the server components.
SSL
The following list of directories/files must have read only permissions when non-admin users connect their client components to servers over SSL:
CTM/EM permissions
All users, regardless if admin or not can access Control-M components on the Citrix machine.
The following table lists the Control-M/EM directory permissions settings on the Citrix machine. Make sure the following permissions are set accordingly.
Local path |
Permissions |
|---|---|
<EM DIR> |
Read NOTE: Ensure that it is inherited by all its children. |
<EM DIR>\log |
Read and Write |
<EM DIR>\data |
Read and Write Includes templates and ApplicationForms directory TimeZone.dat file includes time zone definitions NOTE: Ensure that it is inherited by all its children. |
<EM DIR>\bin\plugin |
Read and Write |
[HKEY_LOCAL_MACHINE] |
Read |
Login profile settings
Settings are stored per machine user (the user that logged into the Citrix client) and not per EM user.
When logged in for the first time, the directory %APPDATA%\BMC Software\ Control M Enterprise Manager\X.0.0.0\<Instance Name> is created. The directory includes the ClientUserSettings.xml file and another directory named Layout. The ClientUserSettings.xml file includes all user settings.
Log settings
You can configure log settings for specific Control-M components to collect information for troubleshooting purposes.
The table includes a list of the components and the corresponding log file setting:
Component |
Log file setting |
|---|---|
CCM and XML utilities |
<EM_DIR>\ini\xxx_DiagLvls.ini (xxx is component name) NOTE: To prevent two processes from writing into the same file, set IsPIDUsed parameter to 1 in the ini file. |
CMWA automation client |
File > Options > Diagnostics The debug level is saved in the file user.config in %LOCALAPPDATA%\BMC Software. Each user has their own settings |
Corba settings on a Citrix machine:
The procedure describes how to configure Corba settings to support multi-user environment:
HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
EM_DOMAIN_NAME in the registry:
[HKEY_CURRENT_USER\Software\BMC Software\
Control-M\Control-M/Enterprise Manager\8.0.X\<Instance name>]
"EM_DOMAIN_NAME"="config_user"
or
[HKEY_LOCAL_MACHINE\Software\BMC Software\
Control-M\Control-M\Enterprise Manager\8.0.X\<Instance name>]
"EM_DOMAIN_NAME"="config_machine"
Parent Topic |