User`s guide

Installing MarkVision Professional
20
MarkVision Server
/usr/mv_pro/bin (executable files)
/usr/mv_pro/etc (configurable files)
/usr/mv_pro/lib (archive/library (JAR) files)
Setting up the MarkVision Professional UNIX Server
Once the MarkVision Professional package is installed on a system, a setup script must run to
complete the installation process. This script is installed at:
<install-dir>/setup.mjserver
The MarkVision Server must be run as a standard system daemon. It collects information about
network attached devices, such as printers and print servers. For security reasons, this daemon must
be run as a normal user with no special privileges. Therefore, we recommend using an existing user
ID or to create a special user ID for this daemon to run as.
The default user ID is user nobody. Most modern UNIX systems ship with this ID pre-installed. If you
want to change it and use a different ID (for example markvision), create the user ID before running
the setup script.
The setup script checks if the MarkVision Server is currently running, and if so will exit, prompting the
user to stop the server using the appropriate command. If the server is not running, it prompts for the
user ID and verifies its validity. Once the user ID is verified, the MarkVision Server starts.
The following shell scripts are used during the MarkVision Server setup and startup process:
• /usr/mv_pro/bin/findJava
• /usr/mv_pro/bin/MvService
• /usr/mv_pro/bin/MvWebService
FindJava
This script is used by multiple scripts to locate the appropriate version of Java Virtual Machine on the
system. This script attempts to find the path to the “java” binary in standard system locations. If the
JVM is not found in standard system locations, it tries to search the PATH environment variable for
the JVM. If the search for the appropriate JVM fails, it exits with an error message informing the user
that a suitable JVM was not found. It also indicates the appropriate JVM version(s) required to run
the MarkVision Server software.
If you believe a suitable JVM is on the system, make sure it is in your PATH and run the /usr/mv_pro/
bin/findJava script again. This creates a symbolic link from /usr/mvp_java to the Java home directory
(JAVAHOME).
For example, if the full path to the appropriate “java” binary is:
/usr/local/java/bin/java
The Java home directory is “/usr/local/java.”