Database Reference
In-Depth Information
If using Jython, Java must be installed and set before installing the EM CLI advanced kit (emcliadvancedkit.jar).
Windows 8 and 8.1 will experience errors unless Java version 1.7.0.17 is present. Compatibility matrices are available
at My Oracle Support.
windows servers will often recommend uninstalling older versions of Java once new ones are in place. to avoid
registry issues, ensure that:
Tip
no other oraCle_home is utilizing the Java version in its path, and
the older version of Java is uninstalled
before installing the newer version to prevent any impact to the
new installation.
Path and Environment Variables
To execute EM CLI verbs, no matter if they are Python or otherwise, you will need a connection to the OMS. This will
require environment variables to be set (also known as client properties) as part of the EM CLI scripting environment.
You can inspect all possible client properties by utilizing the help option in the EM CLI:
> emcli>help('client_properties')
EMCLI_OMS_URL
EMCLI_USERNAME
EMCLI_AUTOLOGIN
EMCLI_TRUSTALL
EMCLI_VERBJAR_DIR
EMCLI_CERT_LOC
EMCLI_LOG_LOC
EMCLI_LOG_LEVEL
EMCLI_OUTPUT_TYPE(status())
Client or Remote Target Installation
There are various reasons for installing the EM CLI on a remote target. You must decide if there is a significant need to
do so or if a task that needs to be run from the remote target can be accomplished with an emctl command instead.
Here are two reasons for not installing the EM CLI on a remote target or client:
1.
Security: The EM CLI will be configured to access the OMS, and the security risk of doing
so should be justified. Any person using the EM CLI on the remote target or client will still
be required to log in as they would from the OMS installation of the EM CLI, but this does
pose an added security risk versus a solely OMS-installed configuration.
2.
Efficiency: Enterprise Manager Control (EMCTL) command can accomplish several of the
same tasks as EM CLI at the command line, such as issuing a remote blackout of a target
and so forth. In those cases, there is no need to go through a full remote installation and
configuration of EM CLI. EMCTL uses the existing EM agent to perform those tasks, using
its standard connections without the need for additional passwords or authentication
tokens.
 
 
Search WWH ::




Custom Search