HP Systems Insight Manager 7.0 Command Line Interface Guide

• The mxinitconfig, or mxinitconfig –l commands display the configuration status,
including kernel parameter checks, database setup, web server setup, and thirteen other items.
• The –a parameter configures Systems Insight Manager starting the web services and Systems
Insight Manager services, and initializes the database.
• The –r parameter removes all configuration information from Systems Insight Manager by
stopping all services and removing the database.
If you are using an Oracle database, run the mxoracleconfig command before running
mxinitconfig, because mxinitconfig initializes the database and the database must be in place
before initialization. To configure the database, use the following command:
# mxoracleconfig –h host [–n port] –d db –u 6 –p pw [–j jar] [–f ]
• The –h host specifies the host name where the Oracle database is installed.
• The –d db specifies the instance name of the database Systems Insight Manager will use.
This should be a database created for the exclusive use of Systems Insight Manager, created
to use the Unicode character set, AL32UTF8.
• The –u user option specifies the user authorized to log in to the Oracle database instance.
• The –p pw option specifies the password for user.
• The –n port option specifies the Oracle TCP/IP listener service port. If not specified, the
default port 1521 is used.
• The –j jar option (optional) specifies the location of the thin client jar file containing the
jdbc driver, typically ojdbc14.jar.
• The –f option (optional) reruns this command.
Typically, you only need to run the mxoracleconfig command once. To rerun initialization, use
the –f option.
Systems Insight Manager services
There are two commands that enable you to stop and start the Systems Insight Manager services.
The mxstop command stops all the Systems Insight Manager services and the Tomcat web server.
The mxstart command starts all the Systems Insight Manager services and the Tomcat web server.
Neither command uses any options. After running mxstop, HP recommends that you do not run
mxstart until all the services and related processes are stopped.
On HP-UX and Linux operating systems, run the ps –ef | grep mx command until all processes
that start with mx are stopped. If after several minutes, there are mx processes still running, manually
kill the processes using the kill PID command, where PID is the process ID displayed using the ps
–ef|grep mx command.
Systems Insight Manager log
The mxlog command enables you to create an entry in a log file, or to print a log entry to stdout.
The basic forms of the command are:
# mxlog –l [–r result] [–a action] [–o object_type] [–n object_name]
[–u user] [–s sessionID] [–t transactionID] [–v verbosity] [–m message]
# mxlog –p[–r result] [–a action] [–o object_type] [–n object_name]
[–u user] [–s sessionID] [–t transactionID] [–v verbosity] [–m message]
• The –l option logs the entry to the log file.
• The –p option prints a preview of the log entry to stdout.
The –l or –p options are mutually exclusive and use the following options. Some of the options
listed have a default value if the option is not specified in the command.
152 Infrastructure management using CLI