Terminology and Basics - Oracle Enterprise Manager 12c Command-Line Interface - page 42

Listing 3-29. Create the uname_a.job and uname_r.job library job properties files
[oracle ~]$ cat uname_r.job
# Current status of the job is ACTIVE.
name= UNAME_R
type=OSCommand
owner=SYSMAN
kind=library
# Credential Usage: defaultHostCred
# Description:
cred.defaultHostCred.<all_targets>:host=SET:HostCredsNormal
# Description: (Optional) Comma separated list of parameters to the command.
variable.args=/bin/ uname -r
# Description: (Optional) Command to run on the target.
variable.command=%job_default_shell%
schedule.frequency=IMMEDIATE
[oracle ~]$ emcli create_library_job -input_file='property_file:uname_r.job'
Creation of library job "UNAME_R" was successful.
Exporting jobs gives one the ability to easily duplicate jobs (both active and library), as well as to keep an external
backup of that job in a generic format. This backup can serve as a method of restoring the job to another system,
building a duplicate or test system, and producing an audit record if necessary.
Summary
The terminology of EM CLI can be confusing for someone who is not a regular user. Verbs define the functionality
of what you want to do with EM CLI. The “flavors” of how you make changes with EM CLI are known as modes.
Command-line mode is also known as classic mode, where one command is executed at a time. Interactive and
scripting modes use Python syntax and can additionally use the mature functionality of that powerful programming
language.
Given its size and complexity, it is impossible for someone to memorize everything about EM CLI. Even the
most advanced user will need the assistance of documentation on a regular basis. Fortunately, EM CLI is loaded with
help. From the excellent documentation found online to the manual pages contained within the command-line and
interactive modes of the tool itself, all of the information one needs is easily and readily available.
No one likes an error message, but when they pop up in EM CLI, they are descriptive and usually easy to read and
interpret. The syntax of errors in many products can be tricky, especially with all of the different tools administrators
have to switch between on a daily basis. The error syntax in EM CLI is intuitive and simple when compared to many of
those other tools.
EM CLI will already be fully configured and ready to use on each installed OMS. It is also easy to download,
install, and set up on any other machine that is capable of running Java. The method of communication between the
EM CLI client and the OMS is almost identical to the communication that takes place between the browser and the
OMS. Both are highly secure and use standard, mature technologies.