CA Client Automation - 14.0

PDF
English

How to Optimize the Manager Concurrency

cla140
cla140
Contents
Software delivery optimizes the process of handling multiple tasks by improving the Task Manager and Installation Manager concurrency. Software delivery provides configuration policies that let the Task Manager and Installation Manager run in concurrent mode to handle multiple tasks at the same. This multiprocessing approach that concurrent mode provides helps you optimize manager concurrency, and consequently performance of the software delivery engine.
The Task Manager and Installation Manager are components of the domain manager.
Concurrent Mode and Non-Concurrent Mode
The concurrency behavior of the Task Manager and Installation Manager is independent of each other. You can run the Task Manager, Installation Manager, or both in concurrent or non-concurrent mode, depending on your requirements. The Task Manager and Installation Manager behave differently in these two modes. However, for optimal performance, you must run both the manager components (Task Manager and Installation Manager) in concurrent mode. Before you configure these two manager components to run in concurrent mode to optimize manager concurrency, make sure you understand how the two manager components behave in both the modes.
You can run the Task Manager and Installation Manager in concurrent or non-concurrent mode only on the domain manager. On the enterprise manager, only non-concurrent mode is available.
After you change the concurrency setting for the Task Manager or Installation Manager, make sure that you restart the appropriate plug-in to reflect the changes.
Concurrent Mode
In concurrent mode, the Task Manager and Installation Manager create additional manager processes. These two manager components are split into multiple separate processes with each process dedicated to perform a specific set of tasks on the domain manager. Each process works independent of the other process. The tasks are assigned to the appropriate process based on the type of the task a process is supposed to handle. As a result, the Task Manager and Installation Manager can cater to several tasks at the same time when run in concurrent mode.
Task Manager Processes in Concurrent Mode
The Task Manager creates two additional manager processes in concurrent mode, Policy Manager and Replication Manager. These additional processes run as CAF plug-ins. As a result, a total of three independent Task Manager plug-ins run in parallel. Each individual plug-in is dedicated to handle a specific set of tasks independent of the other plug-in. The tasks are prioritized for each plug-in, and the priority of a task belonging to one plug-in does not have any relationship with the priority of a task belonging to the other plug-in. For example, priority of a policy task does not affect the priority of a job container task because these two tasks belong to two separate plug-ins and follow the priority specified in their specific plug-in.
The following are the three Task Manager plug-ins that run in concurrent mode:
  • Task Manager (TM)
    Handles the Maintenance, Data Transport Monitor, and job container tasks. The log file for the Task Manager process in concurrent mode is TRC_USD_TASKMAN.log.
  • Policy Manager (PM)
    Handles the Scheduled Policy Evaluation and Ad-hoc Policy Evaluation tasks. The log file for the Policy Manager process in concurrent mode is TRC_USD_POLMAN.log.
  • Replication Manager (RM)
    Handles the Distribution Receiver, Distribution Acknowledgement, and Computer Mover tasks. The log file for the Replication Manager process in concurrent mode is TRC_USD_REPMAN.log.
The System Delivery Engine represents the Task Manager, Policy Manager, and Replication Manager plug-ins combined together in the case of concurrent mode and only the Task Manager plug-in in the case of non-concurrent mode.
Installation Manager Processes in Concurrent Mode
In concurrent mode, the Installation Manager creates an additional manager process, Notification Manager. As a result, a total of two independent plug-ins run in parallel as CAF plug-ins.
The following are the two Installation Manager plug-ins that run in concurrent mode:
  • Installation Manager (IM)
    Handles the update of the job status messages and software records in the database. The log file for the Installation Manager process in concurrent mode is TRC_USD_INSTMAN.log.
  • Notification Manager (NM)
    Handles the notifications and the actions occurring as a result of the notifications. The log file for the Notification Manager process in concurrent mode is TRC_USD_NOTMAN.log.
Non-Concurrent Mode
In non-concurrent mode, the Task Manager and Installation Manager run as single processes, and perform the tasks as follows:
  • The Task Manager handles one task at a time and processes the tasks in a sequential manner based on the priority. The log file for the Task Manager process in non-concurrent mode is TRC_USD_TASKMAN.log.
  • The Installation Manager alternates between handling notifications and updating the database with the job status from the agent. The log file for the Installation Manager process in non-concurrent mode is TRC_USD_INSTMAN.log.
Configure the Task Manager and the Installation Manager Concurrency
Configure the common configuration policies for the Task Manager and the Installation Manager to enable the concurrent mode for these two manager components.
These policies are applicable only for the domain manager.
To configure the Task Manager and the Installation Manager concurrency
  1. Navigate to Control Panel, Configuration, Configuration Policy,
    policy name
    , DSM, Software Delivery, Manager.
    A list of configuration policies appears.
  2. Double-click the following policies, and enter appropriate values in the Setting Properties dialog:
    • Manager Concurrency: Task Manager Concurrency enabled
      Controls the Task Manager concurrency behavior. You can set the parameter value to True or False. When set to False, the Task Manager runs as a single process and performs the tasks in a sequential manner. When set to True, the Task Manager creates additional manager processes, Policy Manager and Replication Manager, to perform the policy evaluation tasks and the replication tasks. For optimizing manager concurrency, set the value to True.
      Default:
       True
    • Manager Concurrency: Installation Manager Concurrency enabled
      Controls the Installation Manager concurrency behavior. You can set the parameter value to True or False. When set to False, the Installation Manager runs as a single process and performs the notification processing and the database updates alternately. When set to True, the Installation Manager creates an additional manager process, Notification Manager, to handle notifications and messages related to the notifications. For optimizing manager concurrency, set the value to True.
      Default:
       True
  3. Click OK.
    The concurrency behavior for the Task Manager and the Installation Manager is enabled.
Configure the Cache Cleanup Interval for the Concurrent Processes
You can configure the common configuration policies to control the intervals at which you want to perform the cache cleanup for the concurrent processes. The intervals specify the time in minutes after which you plan to perform the cache cleanup for the concurrent processes. You can specify different values for different processes.
To configure the cache cleanup interval for the concurrent processes
  1. Navigate to Control Panel, Configuration, Configuration Policy,
    policy name
    , DSM, Software Delivery, Manager.
    A list of configuration policies appears.
  2. Double-click the following policies, and enter appropriate values in the Setting Properties dialog:
    • Internal: Installation Manager cache cleanup interval
      Controls the frequency at which you want to perform the cache cleanup for the Installation Manager.
      Default:
       5
      Limits:
       0 to 10080
    • Internal: Notification Manager cache cleanup interval
      Controls the frequency at which you want to perform the cache cleanup for the Notification Manager.
      Default:
       60
      Limits:
       0 to 10080
    • Internal: Policy Manager cache cleanup interval
      Controls the frequency at which you want to perform the cache cleanup for the Policy Manager.
      Default:
       60
      Limits:
       0 to 10080
    • Internal: Replication Manager cache cleanup interval
      Controls the frequency at which you want to perform the cache cleanup for the Replication Manager.
      Default:
       60
      Limits:
       0 to 10080
    • Internal: Task Manager cache cleanup interval
      Controls the frequency at which you want to perform the cache cleanup for the Task Manager.
      Default:
       30
      Limits:
       0 to 10080
  3. Click OK.
    The cache cleanup interval is configured for the concurrent processes.
Confirm the Concurrency Status of the Task Manager
To confirm whether the Task Manager is running in concurrent mode or non-concurrent mode, you need to run the
caf status
 command on the domain manager to check the status.
If the
caf status
 command displays the Task Manager (sdmgr_tm), Policy Manager(sdmgr_pm) and Replication Manager (sdmgr_rm) plug-ins in the running state, it implies that the Task Manager is running in concurrent mode.
You can also view the concurrency status of the Task Manager in the DSM Explorer by looking at the status of the System Delivery Engine.
View the Status of System Delivery Engine
You can use the Information portlet available on the System Delivery Engine page to view the status of the System Delivery Engine. The same status represents the current concurrency status of the Task Manager.
To view the status of the System Delivery Engine
  1. Navigate to Control Panel, Engine, All Engines, System Delivery Engine.
    The System Delivery Engine page opens.
  2. View the message in the Information portlet.
    The Information portlet displays the status of the System Delivery Engine.
    Typically, the information is displayed in the portlet within a minute of selecting the System Delivery Engine node; however, in some cases, it might take some time depending on the load on the System Delivery Engine.
Confirm the Concurrency Status of the Installation Manager
The DSM Explorer user interface does not display information about the concurrency status of the Installation Manager. To confirm whether the Installation Manager is running in concurrent mode or non-concurrent mode, you need to run the
caf status
 command on the domain manager to check the status.
If the
caf status
 command displays the Installation Manager (sdmgr_im) and Notification Manager (sdmgr_nm) plug-ins in the running state, it implies that the Installation Manager is running in concurrent mode.