MarkVision components
10
plug-in for UNIX and other platforms, go to: http://java.sun.com/products/plugin/
index.html.
The MarkVision Client application and the Web Client are essentially the same program. All
information that is being managed by the MarkVision Server is available to users of either the
application or Web Client. The only differences are that the application does not require installation of
the Java plug-in and may require less startup time because some files are stored locally on the
user’s workstation. However, anyone who does not run MarkVision Professional on a regular basis,
or who is not currently working from their workstation, should use the Web Client version of MVP. In
this case, there is no need to install any MarkVision files in order to use the client.
MarkVision Messenger
MarkVision Messenger works with MarkVision Professional to provide technicians with e-mail
notification or command line execution when a network printer triggers a pre-defined event (such as
Paper Tray Missing, Toner Low, and many more). The heart of MarkVision Messenger is a “service”
that runs inside the MarkVision Server. To use this service, the user creates “actions” using a
browser-based interface. Users can access MarkVision Messenger either by launching it from the
Action menu in the MVP application, or by using the URL http://<yourserver>/messenger in your
browser. For more information, see the MarkVision Messenger section of this User’s Guide.
MarkVision Server
The MarkVision Server is the engine that powers MarkVision. The MarkVision Server is the single
point of contact between an instance of the MarkVision Client and all of the devices that MVP
manages. The first time a client requests information, the MarkVision Server gathers the new
information from the device and stores it in a cache. Each subsequent request for the same
information is then retrieved from the cache. This saves valuable network resources by eliminating
redundant network traffic from duplicate requests.
The MarkVision Server also eliminates the complexity of talking to a wide variety of network devices.
Client programs only need to send a single protocol to the server, which in turn knows how to
communicate with the devices.
In order for the system architecture to work, at least one MarkVision Server must exist on a network.
It is possible to install multiple instances of the MarkVision Server on a network, however, a client
can only connect with one server at a time.
MarkVision Web Server
MarkVision Professional provides a web server for the browser-based components of the product
(MVP Web Client and MarkVision Messenger) as part of the MarkVision Professional package. The
MVP Web Server is automatically installed along with the MarkVision Server.
During installation, you are given the option to make the MarkVision web server the default server on
the machine. This allows the browser-based application to access the server from the standard port
(80), which requires no additional numbering in the URL. If this option is not selected, the MVP Web