Environment
Situation
Resolution
Clustering the NetIQ AppManager Command Queue Service for AppManager V7.0 and above ===================================================================================
Customers may find it beneficial to cluster the AppManager Command Queue Service in high availability configurations. The Command Queue Service (CQS) is responsible for issuing commands (such as job start and stop, or event close) to the AppManager Repositories from Control Center. In V7, the CQS is also responsible for spawning a process named NQSyncQDB that synchronises data between repositories and the Control Center database (NQCCDB).
At present, the normal installation of Control Center does not allow for the CQS service to be clustered, but use of the Microsoft Generic Service Resource in a Cluster allows this. The instructions below give guidelines on achieving this.
Assumptions
===========
A Windows Cluster has already been configured, and has at least one Cluster Group available. The Cluster Group has at least one Disk Resource, one Network Name Resource and one Network Address (IP Address) Resource, all running correctly.
At least one AppManager Repository and Management Server (V7.0 or above) has been installed and is available.
Control Center (V7.0 or above, minus the CQS Service) has been installed and is available.
The AppManager agent (V7.0 or above) has been installed to a local disk on each Cluster node.
Installing the CQS on the First Node
====================================
Ensure that the Cluster Group you will be using for the CQS Service is failed across to the first node, and that the disk drive in that group is on-line.
Launch AMSetup.exe from the AppManager V7.0 (or above) distribution. When prompted, select ONLY the Control Center installation (the agent should already have been installed).
When the Control Center installation begins, change the destination directory to ensure that the disk drive selected for the installation is the disk drive that is in the Cluster Group you intend to use for the CQS service. Then when offered a selection of Control Center components, ensure that ONLY the Command Queue Service option is checked. When prompted for a service account, ensure that a Domain account is specified - one with Administrative rights to each node in the cluster.
Continue the installation until completion (making sure that the server holding the NQCCDB is specified when prompted). After the install completes, use service control manager (services.mmc) to select the CQS service (NetIQ AppManager Control Center Command Queue Service). Stop the service and change the startup type to manual.
Installing the CQS on Each Subsequent Node
==========================================
Ensure that the Cluster Group being used for the CQS is failed over to each node in turn and follow the setup instructions for the first node. Make sure that the service is stopped and set to manual startup after each installation.
During the setup on the subsequent nodes, you may get a warning specifying "Failed to create config file". This can be ignored.
Cluster Steps
=============
Once the installation is complete on all nodes in the cluster that will capable of running the service, you need to create a new Cluster Resource to be available in the Cluster Group. Use Cluster Administrator to do this, and select the Cluster Group. Then select "New Resource" and follow the steps below:-
New Resource Name: NetIQ CQS
Description: AppManager Command Queue Service Resource Type: Generic Service Cluster Group: <The Cluster Group you have been using for the installation>
Possible Owners: <Specify all nodes that have had the CQS installation performed>
Dependencies: <Specify the installation disk, and the network name>
Service Name: NQCQS
Check (select) the option for "Use Network Name for Computer Name"
There is no requirement to enter information regarding registry keys
Once the resource is created, you should be able to bring it on line.
Final Steps
===========
You should now be able to go to the Control Center Console and in the status panel, verify that the status for the CQS is OK, and that the system name used for the CQS is the Network Name (ie the virtual server name) assigned to the Cluster Group used during the setup process.