Moving a Scalability Server Collect job from one Engine to another using the command line.

book

Article ID: 52824

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER CA Server Automation CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Description:

The default System Engine is overloaded with multiple Scalability Server collect tasks. Is there a way to move the collect job to a different engine instance using the command line without being on the Domain Manager?

Solution:

The following command specifies the Engine name that you want to assign a Scalability Server collect job to:
cserver config -g <engine name>

To actually move the existing collect job to the new engine run the command:
cserver register -a

NOTE: If the engine name is misspelled, the command will still be executed but the collect job will not be moved. There is NO validation when you run the above commands and therefore care should be taken while entering the engine instance name. The above commands have to be run on the Scalability Server and are not case-sensitive.

Environment

Release: UASIT.99000-11.2-Asset Intelligence
Component: