Database Reference
In-Depth Information
If this is for a windows host installation, set the JaVa_home in the environment variables and not at the
session level. oracle installs invariably call secondary sessions that may not carry over the session-level variables, which
can cause a failure in those secondary processes.
Note
Execute the installation step with the following command, replacing emcli_install_dir with the directory
associated with the installation path:
> java -jar emcliadvancedkit.jar client -install_dir=<emcli_install_dir>
As before, the following message will return upon successful installation:
The EM CLI client is installed in <emcli_install_dir>
Post-Installation
Once the installation is complete for any kit, on host or remote host, synchronization with the OMS should be performed.
You first need to configure the EM CLI client or remote host information with the existing OMS before
synchronizing with it.
Change over to the EM CLI home directory and set up a local user with local configuration information. You can
easily collect information on the setup verb by typing in the following command:
> emcli help setup
Setting up a local user requires the following command syntax:
Standard Kit:
> emcli setup -url=http://<local_host_name>:<port>/em -username=em_user
Advanced (Scripting) Kit
> emcli setup -url=http://<local_host_name>:<port>/em -username=em_user -trustall
> emcli login -username=sysman
Once set up, you need to synchronize it with the OMS:
> emcli help sync
Patching and Upgrades
Although patching and upgrades may not first appear to be part of installation, they are a very important aspect of
it. Considering that we stress the importance of applying any and all bundle patches upon installation, the inclusion
of checking for these during the installation process should relay how important this step is in the installation of any
OEM environment.
 
 
Search WWH ::




Custom Search