Database Reference
In-Depth Information
This changes the contact details to the
psharman
user ID for all 500 databases in one fell swoop.
One of the main advantages of using EMCLI over EMCTL, though, is that EMCLI has a client that can be installed
on any system that can reach the OMS. That means it can be executed anywhere in your managed environment.
Many Cloud Control administrators install EMCLI on their local machine, for example. EMCLI also allows you to call
custom scripts such as TCL, Perl, SQL, or OS scripts.
From an architectural perspective, there are two parts to EMCLI. There is the EMCLI client (the part that you
install where you want to) and an OMS extension, which is automatically installed in the OMS. The Java-based client
sends command requests using
emcli
verbs to the OMS extension, which passes them on to the OMS to action. These
verbs are plug-in extensions that contain the relevant command and options.
Installation of the EM CLI client is done by first downloading the EMCLI kit to the location where you want to
install it. The kit can be downloaded from the EM console, by choosing Command Line Interface from the Setup
menu, as shown in Figure
3-10
.
Figure 3-10.
Accessing the EM CLI kit
Once you have downloaded and installed the EM CLI kit, you have access to only a few of the basic verbs, such as
help
,
login
,
logout
, and
setup
. To set up the client completely, you need to execute the command
emcli setup
.
At a minimum, you need to pass parameters for the EM console and username that you want to use for logging in with
emcli
(this username is the one you normally log into the console with), but I find it useful sometimes to include the
-autologin
parameter. This parameter ensures that you are automatically logged back in if your session times out.
■
Use the
-autologin
parameter only if the workstation you are installing the client on is secured, particularly
if the username you also pass in has Super administrator-level access.
Caution
