Understanding MarkVision terminology

Within this document:

• Printers and print servers are sometimes simply called devices.

• MarkVision Client is referred to as either MarkVision Client Application or MarkVision Web Client, depending on the context and how it is launched.

• MarkVision Client Application refers to MarkVision Client as a standalone application installed locally on a user workstation.

• MarkVision Web Client refers to MarkVision Client when it is accessed through a Web browser.

MarkVision Client

MarkVision Client Application—The standalone application can be installed locally on a user workstation.

MarkVision Web Client—The browser-based client is a Java applet version of the client that can be accessed through a supported Web browser by way of the following URL: http://<yourserver>/markvision. If the MarkVision Server is not the default server on the machine, access the client through a supported Web browser by way of the following URL http://<yourserver>:9180/markvision.

The MarkVision Application and MarkVision Web Client are essentially the same program. All folders, filters, devices, and so on that are managed by the MarkVision Server are available to users of either the application or Web client. The two versions are functionally equivalent.

The only differences between the application client and the Web client are:

• The application does not require the installation of the browser plug-in; and

• the web client requires a Web browser and loads more slowly.

Notes:

• Enable the Web browser to support Sun’s Java Runtime Environment (JRE) by installing the Java plug-in. In Windows environments, the plug-in is provided and the user will automatically be prompted to install it the first time they run the MarkVision Web Client.
• For information on the Java plug-in software and to download available versions of the plug-in for UNIX and other platforms, visit http://java.sun.com.

MarkVision Messenger

MarkVision Messenger works with MVP to provide e-mail notification or command line execution when conditions on a network printer (such as Paper Tray Missing or Toner Low) trigger a pre-defined event. 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 open MarkVision Messenger from the Action menu in the MVP application, or by visiting the URL http://<yourserver>:9180/messenger or https://<yourserver>:8443/messenger by way of a Web browser.

MarkVision Web Server

The MarkVision Web Server supports the browser-based component of MarkVision Web Client and MarkVision Messenger. The MarkVision Web Server is automatically installed with the MarkVision Server. The MarkVision Web Server uses the standard HTTP port (80) if it is selected as the default server during installation. Otherwise, it accepts HTTP requests on a non-standard port (9180), and HTTPS requests at TCP port 8443.

MarkVision Server

The MarkVision Server is the engine that powers MVP. 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 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 knows how to communicate with the devices. At least one MarkVision Server must exist on a network. While it is possible to install multiple instances of the MarkVision Server on a network, a client can only connect with one server at a time.

One exception to this architecture is that, for devices that implement remote operator panel support using VNC, the MarkVision Client will establish a remote operator panel session directly with the printer.