This document focuses on the technical issues surrounding MarkVision Professional (MVP)’s
database support. The intent of this document is to cover the structure of the data and provide
details concerning the content.
Edition: December 2002
The following paragraph does not apply to any country where such provisions are
inconsistent with local law: LEXMARK INTERNATIONAL, INC., PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow
disclaimer of express or implied warranties in certain transactions; therefore, this statement may
not apply to you.
This publication could include technical inaccuracies or typographical errors. Changes are
periodically made to the information herein; these changes will be incorporated in later editions.
Improvements or changes in the products or the programs described may be made at any time.
Comments about this publication may be addressed to Lexmark International, Inc., Department
F95/032-2, 740 West New Circle Road, Lexington, Kentucky 40550, U.S.A. In the United
Kingdom and Eire, send to Lexmark International Ltd., Marketing and Services Department,
Westhorpe House, Westhorpe, Marlow Bucks SL7 3RQ. Lexmark may use or distribute any of the
information you supply in any way it believes appropriate without incurring any obligation to you.
You can purchase additional copies of publications related to this product by calling 1-800-553-
9727. In the United Kingdom and Eire, call +44 (0)8704 440 044. In other countries, contact your
point of purchase.
References in this publication to products, programs, or services do not imply that the
manufacturer intends to make these available in all countries in which it operates. Any reference
to a product, program, or service is not intended to state or imply that only that product, program,
or service may be used. Any functionally equivalent product, program, or service that does not
infringe any existing intellectual property right may be used instead. Evaluation and verification of
operation in conjunction with other products, programs, or services, except those expressly
designated by the manufacturer, are the user’s responsibility.
This software and documentation are provided with RESTRICTED RIGHTS. Use, duplication or
disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of
the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and in
applicable FAR provisions: Lexmark International, Inc., Lexington, KY 40550.
Trademarks
Lexmark and Lexmark with diamond design, MarkVision, and Optra, are trademarks of Lexmark
International, Inc., registered in the United States and/or other countries.
Other trademarks are the property of their respective owners.
5.3 Field Relationships ....................................................................................................... 54
MarkVision Professional 10.1 Page 3
MarkVision Professional 10.1 September 2, 2003
6. Data Type Conversion ........................................................................................................ 54
MarkVision Professional 10.1 Page 4
MarkVision Professional 10.1 September 2, 2003
1. Overview
MarkVision Professional allows you to collect comprehensive data on the physical devices
(Printer Inventory) and on submitted jobs to the devices (Job Statistics). The MarkVision
Professional database consists of a number tables, each prefixed with the word RAW. The next
prefix determines the table’s function:
JA Job Statistics
PI Printer Inventory
DS Device Status
DeviceStatus Device Status
PRN Master Printer data table
Device Master Device data table
2. Configuring Database Driver
2.1 Supported Databases
2.1.1 Windows
• Oracle (8.0.3)
• SQL Server (6.5, 7.0, 2000)
• Microsoft Access (97, 2000, 2002)
• Comma-separated variable (CSV)
NOTE: The ‘Oracle’ database option is only available after installing the Oracle JDBC Driver plugin.
2.1.2 UNIX
• Oracle (8.0.3)
• Comma-separated variable (CSV)
NOTE: The ‘Oracle’ database option is only available after installing the Oracle JDBC Driver plugin.
2.2 Creating Windows System DSN
Before you can enable MarkVision Professional to collect printer inventory or Job Statistics
information on windows systems, you must first configure the ODBC data source. The system
ODBC settings can be accessed from the system control panel.
Example 1: Start→Settings→Control Panel →Data Sources (ODBC) for Windows NT 4.0
Example 2: Start→Settings→Control Panel →Administrative Tools→Data Sources (ODBC for
Windows 2000 and beyond
Once in the ODBC settings dialog box, click on the System DSN tab. The following box should
appear.
MarkVision Professional 10.1 Page 5
MarkVision Professional 10.1 September 2, 2003
2.2.1 Microsoft Access
From the System DSN dialog box, click “Add” and the following dialog box will appear. Select
Microsoft Access Driver (*.mdb) and click “Finish.”
After clicking “Finish”, the following dialog box will appear. Think of a name for your connection
and type it into the “Data Source Name” (DSN) field, and then type a description for the data
MarkVision Professional 10.1 Page 6
MarkVision Professional 10.1 September 2, 2003
source. For the example, MVP has been chosen for the name, and the description is “connection
for MVP printer inventory”.
After the name and description for the connection has been entered, you must specify a database
in which to store the data coming from MarkVision Professional. You may either “Select” a
database already created for this purpose, or choose “Create” to define a new database and
location. Click on “Create” and the following dialog box will appear.
Browse to the desired directory, and specify a name to be used for your database. Make a note
of the name and location; you may need this information to configure MarkVision Professional or
to design reports in MS Access later. NOTE: “Format” depends upon which version of
Access you will be using to view the database. Version 4.x is for Access 2000 and higher,
Version 3.x is for Access 97 and 95. Click “OK” and a confirmation dialog box should appear.
MarkVision Professional 10.1 Page 7
MarkVision Professional 10.1 September 2, 2003
Click “OK” for the confirmation, and then “OK” again on the ODBC Microsoft Access Setup dialog
box to return to the ODBC Data Source Administrator.
The name you specified for your connection (DSN) is now listed under System DSN. Click “OK”.
You are now ready to configure MarkVision Professional to start sending the data.
In MarkVision Professional, after selecting the “Access” database selection, the URL field should
become enabled.
In the URL field, type the name of the System DSN you created earlier. It is not necessary to
specify the path to the actual database file; this was defined while creating the connection. For
the example just described, enter jdbc:odbc:MVP. If you have enabled security features while
creating the database, enter the user name and password and click on “OK.”
2.2.1.1 Locating an Access Database on a Different Server
It is possible to store an Access database on a different server than the machine on which the
MarkVision server resides. By default, the MarkVision server service accesses network resources
using the Administrator account. You may have to alter the account used to enable the
appropriate network access. To enable the MarkVision server to access the alternate location,
some changes must be made to the MarkVision Server service. On the services dialog box,
select the MarkVision Server service.
MarkVision Professional 10.1 Page 8
MarkVision Professional 10.1 September 2, 2003
Access the properties of the service by either double-clicking the service in Windows NT, or
clicking the properties button in Windows 2000 and beyond.
Select “This Account” to log on to the new machine as a user with appropriate network access
privileges and click “OK.”
2.2.2 SQL Server
The method for creating a DSN under Windows for Microsoft’s SQL Server is nearly identical to
Access. Simply substitute “SQL Server” for the system DSN. See Microsoft Access
for more
information.
MarkVision Professional 10.1 Page 9
MarkVision Professional 10.1 September 2, 2003
2.3 Oracle
MarkVision Server’s install package no longer contains an Oracle JDBC driver by default. As a
result of modified licensing agreements, Lexmark is no longer able to directly distribute Oracle
JDBC (database) support. If out-of-date drivers existed on your system from a previous release of
MarkVision Professional, they have been removed. If you require Oracle support, you will need to
register and download the Oracle JDBC Driver v1.0.mvp plug-in from the following web page:
http://www.markvisionprofessional.com.
After downloading and installing in the appropriate plug-in, the “Oracle” database selection will
become available. In MarkVision Professional, after selecting the “Oracle” database selection, the
URL field should become enabled.
In the URL field, change the “localhost” value to the hostname or IP address of the machine
running your Oracle database. The URL must use the following format:
<database driver>@<database server's IP address>:<database port>:<database instance
(memory area)>
For example: jdbc:oracle:thin:@157.184.46.113:1521:orcl. If you have enabled security
features while creating the database, enter the user name and password and click on “OK.”
2.4 CSV
Users may elect to export database information to a CSV format. In MarkVision Professional,
after selecting the “CSV” database selection, the ‘Directory’ field should become enabled.
Due to the multi-dimensional aspect of the data being collected, multiple CSV files are generated.
Each file represents a table and the primary/foreign key relationship, as described below, is how
information in these files should be correlated.
Database insertions (including CSV file manipulation) are handled by a separate thread to reduce
I/O impact of such insertions on the rest of the system. This thread, by default, has a 2 minute
time-out, so database insertions and CSV file manipulation will not occur immediately after task
completion. In other words, the printer inventory task may say complete, but the CSV files will not
be modified until the database insertion timeout is breached. Modify the
queueWriter.pollingRate parameter to change the default behavior of this thread.
3. Printer Inventory
You can use the MarkVision Server to gather and store information about the devices in your
organization. You can then view the collected information (printer inventory) using a database tool
or an application, such as MarkTrack, specifically designed to interpret and display the
information. See Configuring Database Driver for a description of supported databases.
MarkVision Professional 10.1 Page 10
MarkVision Professional 10.1 September 2, 2003
Use the information gathered by the printer inventory process to answer questions such as:
• How many printers do we have on our server(s) / network?
• What types of printers do we have?
• What options are installed on our printers?
• What is the lifetime page count of our printers?
• What are the addresses of our printers?
MarkVision Professional 10.1 Page 11
MarkVision Professional 10.1 September 2, 2003
3.1 Configuring MarkVision Professional
Open the MarkVision Professional client. Select “Actions” on the toolbar and then “Printer
Inventory” from the drop-down list, or “Printer Inventory” from the “All Tasks” list.
MarkVision Professional 10.1 Page 12
MarkVision Professional 10.1 September 2, 2003
The Printer Inventory screen should be displayed.
Select the appropriate database. Follow database specific instructions in the Configuring
Database Driver section.
3.2 Table and Field Descriptions
The tables and descriptions of each field are listed below. The data types listed for each field
listed are specific to Oracle databases. Please reference the Data Type Conversion section for
converting to Microsoft Access or SQL Server data types.
MarkVision Professional 10.1 Page 13
MarkVision Professional 10.1 September 2, 2003
3.2.1 RAWPRNINV
This is the master table for Printer Inventory. It contains data such as address, protocol, capability
of the device, revision level, RAM size, etc.
Supported
Field Name Data Type
Note: All printers may not support some fields. For more specific information, please contact Lexmark
Customer Support at
http://support.lexmark.com.
MVP Release
Description
Time at which this printer
inventory was initiated, in
seconds elapsed since
0:00:00, Jan 1, 1900,
START_TIME_UTC NUMBER(10) MVP 7.1
GMT.
String identifier Granite
uses to identify this
DEVICE_ID VARCHAR2(255) MVP 7.1
device.
Version of the data format
VERSION NUMBER(5) MVP 7.1
used in this table.
Year in which this device
YEAR NUMBER(4) MVP 7.1
inventory was initiated.
Month in which this
device inventory was
MONTH NUMBER(2) MVP 7.1
initiated.
Day of the month in which
this device inventory was
DAY NUMBER(2) MVP 7.1
initiated.
Day of week on which
this device inventory was
DAY_OF_WEEK NUMBER(1) MVP 7.1
initiated.
Hour of the day in which
this device inventory was
HOURS NUMBER(2) MVP 7.1
initiated.
Minute of the hour in
which this device
MINUTES NUMBER(2) MVP 7.1
inventory was initiated.
Seconds of the minute in
which this device
SECONDS NUMBER(2) MVP 7.1
inventory was initiated.
Offset from GMT of the
current time zone, in
seconds. This is an
integer from -43200 to
GMT_OFFSET_IN_SECONDS NUMBER(5) MVP 7.1
43200.
Does the current time
zone use Daylight
Savings Time? Possible
values = "Y" for true, "N"
IS_USING_DST VARCHAR2(1) MVP 7.1
for false.
Offset from Standard
Time of the current time
DST_OFFSET_IN_SECONDS NUMBER(4) MVP 7.1
zone, in seconds.
Where did this record
come from? Possible