How does the eG CLI Work?
The eG CLI is currently supported on Windows, Linux, and Solaris environments.
By default, the eG CLI is bundled with the eG manager. Accordingly, once the eG manager is installed, the CLI-related files automatically get installed into the <EG_INSTALL_DIR>\egcli directory (on Windows; on Unix, this will be the /opt/egurkha/egcli directory). You can then proceed to issue the CLI commands from the Windows command prompt / Unix shell prompt on the eG manager host, and easily administer the eG Enterprise system.
On the other hand, to install eG CLI on a remote Windows/Linux/Solaris host, you will have to run a special set-up program that is provided. This is called eGCLI.exe on Windows environments, iCLI_linux on Linux and iCLI_solaris on Solaris. If an automation tool is in use in your environment, the setup program has to be executed on the host on which the automation tool (say, HPOO) operates. On the other hand, if no orchestration engine is in use in your environment, then, you can run the setup program on any remote host in your environment, so that eG CLI gets installed on that host.
Once installed, you need to configure the CLI to access the eG manager in the target environment, so that the CLI can execute commands/scripts on it to setup the environment for monitoring.
Where an automation tool pre-exists, soon after CLI installation, you will have to explicitly configure the tool with the commands supported by the CLI. Chapter 3 provides a detailed list of commands and their syntax. If a user then logs into the tool and invokes any of the configured commands, the CLI establishes an HTTP/HTTPS connection with the eG manager indicated by the command, and automatically executes the issued command on that manager.
If the eG CLI has been installed on a remote client instead, you can either directly issue the eG CLI commands from the command prompt of the client or can bundle the commands into a script that can be executed from the prompt. The command/script will then establish an HTTP/HTTPS connection with the indicated eG manager and perform the configuration / database-related tasks on that manager.
Figure 1 : How the eG CLI works
In a redundant eG manager setup on the other hand, the eG CLI should be configured to communicate with the primary manager alone, as administrative operations can be performed only on this manager. Once this is done, the redundant manager architecture will ensure that the configuration changes effected on the primary manager are automatically replicated to the secondary manager(s).
The next chapter will discuss how to install the eG CLI and how to configure it to communicate with individual managers.