eG CLI Commands for Automating Target Environment Configuration
The eG CLI supports commands for performing the following administrative activities on the eG manager:
- Adding/Modifying/Removing a Component
- Managing/Unmanaging Components
- Adding/Removing External Agents
- Adding/Removing Remote Agents
- Assigning/Disassociating agents from managers in a redundant setup
- Adding/Modifying/Deleting Quick Maintenance Policies
- Assigning Quick Maintenance Policies to Components/Hosts/Tests
- Adding/Modifying/Deleting Independent Policies
- Adding/Modifying/Deleting Maintenance Policy Groups
- Assigning Independent Policy to Maintenance Policy Groups
- Associating Maintenance Policy Groups with Infrastructure Elements
- Enabling/Disabling Tests
- Displaying the Remote agents
- Displaying the External agents
- Displaying the Components
- Displaying the test names for a Component Type
- Include/Exclude Components for Test
- Include/Exclude Tests for Component
- Displaying the Maintenance Policies
- Displaying the details of the Maintenance Policies
- Displaying the details of the Tests
- Adding/Modifying/Deleting a User
- Associating Components to a User
- Adding/Modifying/Renaming/Deleting a Zone
- Adding/Modifying/Renaming/Deleting a Group
Other administrative tasks will be supported in future versions of the CLI.
- Once you install the Admin CLI, you will need to reboot the system on which the Admin CLI is installed. This is required for the installation directory of the Admin CLI to be in the system’s path. Otherwise, you will need to prepend <EGADMINCLI_DIR>\bin to the commands you want to execute.
- Similarly, if you have built scripts into which the eG CLI commands have been bundled, then make sure that each command invocation in the script is pre-fixed by the full path to the command (i.e., <EGADMINCLI_DIR>\bin). To avoid this, you will have to reboot the Admin CLI host after installation, and then proceed to write the scripts.
- The eG CLI commands can support multi-byte characters - i.e., the component names and agent nick names used in the command line can include multi-byte characters. However, to enable the eG CLI to support multi-byte component names/nick names, you need to install and configure the eG CLI on the corresponding multi-byte operating system.