Océ Administrator s Guide. Océ PRISMAaudit V3.02 Device Manager

Transcription

1 Océ Administrator s Guide Océ PRISMAaudit V3.02 Device Manager

2 Copyright Océ Printing Systems GmbH 2000 All rights reserved, including rights of translation, reprinting, reproduction by copying or any other method. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Delivery subject to availability; right of technical modifications reserved.

3 Contents 1 Overview PRISMAaudit PRISMAaudit Device Manager About this Manual Hardware and Software Software Concept First-time Installation of the Device Manager Installation Checklist Installing MS SQL Server (Phase 1) Setting Up the PRISMAaudit Database Settings in ODBC Installing the Device Manager (Phase 2) Installing Intel DMI Installing the Device Manager Database Login Océ License Manager (Phase 3) Restricted License License Installing the License Manager Settings in the PRISMAaudit Database Assistant (Phase 4) Configuring the Device Manager (Phase 5) Deinstalling the Device Manager Visio Link Starting and Operating the Device Manager Starting the System Logging On and Off Monitoring Connections User Administration Managing Profiles Creating a Profile A29247-X68-X

4 5.1.2 Editing a Profile Deleting a Profile Managing Groups Creating a Group Editing a Group Deleting a Group Managing Users Creating a User Changing User Data Deleting Users Settings following Installation Device Manager Administrator Basic Considerations DMI / SNMP The MIF File Terms Used Device Manager Administrator Interface Device Manager Administrator Window Device Manager Administrator Menus Functions on the Tabs Description of Button Functions Online Manual Device Types and Devices Creating a Device Type Compiling the MIF File Assigning Attributes Defining Filters Assigning Icons and Images Defining Physical States Mapping Physical States to Logical States Assigning the Service State Concluding the Process for Creating a Device Type Installing a New Device Other devices Configuring the DMI Converter Deleting Devices / Device Types Deleting the Attribute History Configuration Devices Device Types Changing Icons A29247-X68-X

5 8.2.2 Changing the Service State Editing Physical States Making Mapping Assignments Logical States Twin Mode Service Filter Standard Attributes Nodes Device Configuration Hosts Visio Link Configuration Program Entering Parameters Database Converter Device Manager Client History Taker Statistics Traces Instructions and Actions to take in the Event of Errors A29247-X68-X

6

7 Overview 1 Overview 1.1 PRISMAaudit PRISMAaudit is a modular solution for managing and controlling the digital workflow and is compatible with various makes of equipment. The following figure shows the PRISMAaudit components: This Administrator's Guide describes the PRISMAaudit Device Manager (DM). A29247-X68-X

8 Overview First, a brief word on the various components of Océ PRISMAaudit: The Océ PRISMAaudit TM Systems Manager monitors the entire production workflow. It operates by means of predefined check points, which enable it to track every single document. The Océ PRISMAaudit TM Reprint Manager ensures that damaged or illegible documents are automatically reprinted. The Océ PRISMAaudit TM Verification Manager monitors the print quality of the documents. The Océ PRISMAaudit TM Enterprise Resource Manager is a production planning and material management utility for the production centre. The Device Manager is a tool that you can use to detect technical weaknesses and flaws in the organisation of the production process. The data that is collected relating to capacity utilisation, the temporal distribution of the workload and the states of devices is the basis for initiating targeted measures to correct the weak points. 1.2 PRISMAaudit Device Manager The task of the Device Manager is to collect the machine data in the production centre. The Device Manager evaluates this data and provides statistics. Functions Modular and scalable system based on a shared SQL database. This provides a central data repository, central evaluation, search and archiving of all the available machine data. Central MDA (machine data acquisition) for all the devices on the production lines in the print and mailing centre. Central and decentral representation of current device states in views that can be customised by users. Standard evaluations such as utilisation statistics, error and performance statistics relating to all the devices being monitored. Possibility of exporting data and evaluations to external systems such as MS Excel. 2 A29247-X68-X

9 Overview 1.3 About this Manual Target Group This manual is for all users of the Device Manager who wish to obtain an overview of the system in order to work with the Device Manager. For your convenience, the following conventions and symbols are used in this manual. Convention/Symbol Italics <Angle brackets> Note Description The names of tabs, dialog boxes, windows and fields are printed in italics. The names of buttons are preceded and followed by angle brackets. Notes appear as displayed at left. You should always read the notes because they contain important information. 1 st step How to" instructions, for example, steps you have to take when filling out a tab, are shown as a numbered list. The manual also includes a table of contents and an index. You can also display this manual online when you are working with the Device Manager. For details, refer chapter "Online Manual", page 81. How the manual is organised Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 contains a brief introduction to the Device Manager and explains the structure and contents of this manual. describes the required hardware and software. describes the installation procedure. It is important to check the requirements and have the requisite information on hand before beginning work. See also Chapter 3.1 "Installation Checklist", page 11. explains the basic principles for launching and working with the Device Manager. describes procedures for managing users. A29247-X68-X

10 Overview Chapter 6 describes the user interface of the Device Manager Administrator, introducing the basic elements of the interface. Chapter 7 explains how to set up (install) new device types and devices. Chapter 8 describes how to configure devices. This chapter describes the steps you need to complete in order to have the Device Manager monitor your devices. Chapter 8 describes the commands in the order they appear in the Device Manager Administrator menus, and is chiefly intended for reference. You should read Chapter 7 before you set up a device for the first time. Chapter 9 describes the configuration program, which you use to set parameters for the Device Manager. Chapter 10 contains notes on troubleshooting. 4 A29247-X68-X

11 Hardware and Software 2 Hardware and Software The figure below shows the architecture of the Device Manager: The Device Manager enables you to monitor devices such as printers and inserters. The Device Manager and the devices it monitors exchange information by way of converters. A29247-X68-X

12 Hardware and Software 2.1 Software Concept The Device Manager is subdivided into Clients Database Processes Components The client is your desktop PC. You use this PC to work with the Device Manager. The Device Manager is implemented as an SQL database application (type: MS-SQL). The database contains all the information relating to the Device Manager. The Device Manager works with the processes DMI Converter and History Taker for DMI and History Taker for SNMP. DMI Converter Devices monitored by the Device Manager deliver their information to the Device Manager via DMI (Desktop Management Interface). If a device does not support DMI, a DMI converter has to be connected between the device and the Device Manager to convert the information to DMI format. The DMI Converter is a utility installed in Windows NT / Windows It is possible to have more than one DMI Converter, each installed on a separate PC. SNMP compatible devices send their information directly to the History Taker for SNMP, bypassing the need for a converter. History Taker The History Taker is a utility installed in Windows NT / Windows The main task of the History Taker is to collect information about the devices connected to the system. This information is stored in the PRISMAaudit database and can be used for evaluation. Two types of History Taker can be installed: History Taker for DMI Gathers information, with help from the DMI Converter, about the connected devices. There can only be one History Taker for DMI per PC. History Taker for SNMP Calls the information directly from the selected device(s). There can be more than one History Taker for SNMP per PC. When the Device Manager has to monitor a large number of SNMP compatible devices, performance can be increased by adding more History Taker for SNMP services. 6 A29247-X68-X

13 Hardware and Software Components of the Device Manager The Device Manager consists of the following components: Device Manager Administrator Device Manager Client Device Manager Data Fetcher Device Manager Configuration DB Assistant Device Manager Administrator The Device Manager Administrator serves to configure devices with their respective properties in the Device Manager, map physical states according to device type to logical states and colours, assign names to devices according to their configuration, define twin configurations, define device types and devices and delete data. Device Manager Client The Device Manager Client provides graphical user interfaces in order to display devices in colours that match their operating states, generate statistics and export them to other applications for further processing. Device Manager Data Fetcher The Device Manager Data Fetcher is a utility to collect statistical information about devices and export this information to other applications for further processing. Device Manager Configuration Program With the Configuration Program, the local configuration of the different Device Manager components is carried out. The necessary parameters can added, changed or also deleted with the configuration program in a simple way. DB Assistant You use the Database Assistant to establish the connection with the PRISMAaudit database and to configure the tables for the Device Manager. A29247-X68-X

14 Hardware and Software 8 A29247-X68-X

15 Installation 3 First-time Installation of the Device Manager This chapter summarises the tasks you perform to install the Device Manager, and should be read by every user who intends to perform a first-time installation. You will find the checklist in Chapter 3.1 useful in preparing for the installation. The installation of the Device Manager comprises five phases: Phase 1: Install MS SQL Server 7.0 / 2000 Phase 2: Install the Device Manager Phase 3: Licensing for the Device Manager Phase 4: Make entries in the Database Assistant Phase 5: Make entries in the Device Manager configuration program Requirements The prerequisites for the installation are: The operating system is already installed (Windows NT V4.0 with Service Pack 6 or Windows 2000, Service Pack 1, Service Pack 2) The network is configured There is an SQL database with a ready-configured PRISMAaudit database There is at least one database user with the full set of access rights to the PRISMAaudit database Intel DMI Service Provider ODBC If ODBC is not installed or a version < 3.5 is, install the ODBC version found on the Device Manager Installation-CD. There is an ODBC driver for SQL (V3.5 or higher) Internet Explorer If the Internet Explorer version installed is < 5.0, install the Internet Explorer version found on the Device Manager Installation-CD. Version check All PRISMAaudit products installed on the PC must be the same version, so the versions are checked to verify a match when you install a product. A29247-X68-X

16 Installation The following version checks are performed: At installation time: A warning message will be issued if there is already a PRISMAaudit Manager installed and the Systems Managers you now wish to install does not match the versions already on your PC You can then choose whether or not to go ahead with the installation of the Systems Manager. PRISMAaudit Database: The database assistant checks whether the versions of the PRISMAaudit database and installed PRISMAaudit Managers match up. A warning message will be issued in the event of a mismatch. Note: The database tables (and the tables of the installed PRISMAaudit Manager) have to be updated following the installation of a new version of a PRISMAaudit product. Version check during system operation: The versions of the services and client are also checked. In the event of problems with the versions of services, the details are recorded in the trace file and ODM_Event database table. If a problem is encountered with the client version, the system will issue a warning message to notify you. Procedures As a rule, the installation is a five-phase process: Phase 1: The PRISMAaudit database requires the program MS SQL Server 7.0 / You must install this software if you have not already done so. The entries you have to make for PRISMAaudit are described in Chapter 3.2 "Installing MS SQL Server (Phase 1)", page 12. Once you have installed MS SQL Server 7.0 / 2000, you can set up the PRISMAaudit database with the SQL Enterprise Manager (see page 21), and make the appropriate entries in ODBC (see page 24). Phase 2: This phase begins the actual installation of the Device Manager. It comprises two steps: Installing Intel DMI 2.0 (see Chapter "Installing Intel DMI 2.0", page 32) Installing Device Manager (see Chapter "Installing the Device Manager", page 34) 10 A29247-X68-X

17 Installation Phase 3 Installing and enabling the licenses of the Systems Manager (see Chapter 3.6 "Océ License Manager (Phase 3)", page 40). Phase 4: With the help of the database assistant, you establish the connection to the PRISMAaudit database and configure the tables for the base system and Device Manager (see Chapter 3.7 "Settings in the PRISMAaudit Database Assistant (Phase 4)", page 46). Phase 5: In the last phase, you make your entries in the Device Manager configuration program (see Chapter 9 "Configuration Program", page 141). Phases 1 to 4 are described in detail in the sections that follow. Phase 5 is described in Chapter Installation Checklist You should be prepared to answer a few questions during the installation process. The checklist gives the questions which the installation program will ask you. By filling in the table before beginning the installation, you will have the correct entries on hand when they are needed. One filled in, the list is also useful when re-installing or updating the program. Checklist Question SQL server User name and password Licensing mode PRISMAaudit database Database name ODBC Name Server Login Device Manager Path Components Server Database Database authorisation Entry A29247-X68-X

18 Installation Question ID and password for all PCs in the PRISMAaudit system ID and password for DM services Name and/or IP address for servers and converter PCs ID and password for PRISMAaudit user License key Entry 3.2 Installing MS SQL Server (Phase 1) Note: The following is a basic description of how to install MS SQL Server Version 7.0. MS SQL Server 2000 is similar. Phase 1 involves installing MS SQL Server, setting up the PRISMAaudit database and making the requisite entries in ODBC. Install MS SQL Server from the supplied CD-ROM, referring to the Microsoft SQL Server 7.0 documentation. The following windows show the settings that are important for PRISMAaudit. This is how you install MS SQL Server on the Windows NT / Windows 2000 server: 1. Launch Windows NT and insert the installation CD in the CD-ROM drive. 12 A29247-X68-X

19 Installation The system launches the CD-ROM and opens the following window. 2. Choose Install SQL Server 7.0 Components. The system will display the window shown on the next page. A29247-X68-X

20 Installation 3. In the above window, select Database Server - Standard Edition. The system will display the window shown on the next page. 14 A29247-X68-X

21 Installation 4. Select the installation method Local Install - Install to the Local Machine and click <Next>. The system searches for installed components and will then display the window on the following page. A29247-X68-X

22 Installation 5. Read and observe the information in the above window and click <Next>. The system displays further windows about the license agreement and other items. You do not need to make any further choices until the window shown on the following page appears. 16 A29247-X68-X

23 Installation 6. Select the Typical setup, read the other information and then click <Next>. The system will display the window shown on the next page. A29247-X68-X

24 Installation 7. Leave the settings selected in the window above and enter your password. The field Use a Domain User account should be used only when the PC is in a NT Domain Environment. The local system and local user accounts do not have network access rights. Using a local account restricts SQL Server from interacting with other servers. Some serverto-server activities can be performed only with a domain user account. For example: Remote procedure calls (RPCs) Replication Backing up to network drives Heterogeneous joins that involve remote data sources NT Domain User Account Requirements All domain user accounts must have permission to: Access and change the SQL Server directory (\MSSQL7). Access and change the.mdf,.ndf, and.ldf database files. Log in as a service. 18 A29247-X68-X

25 Installation It is recommended that you use a domain user account that is a member of the Administrators local group. 8. Click <Next>. 9. Confirm the next window with <OK>. The system will display the window shown on the next page. 10. Read and observe the information and click <Next>. The system will display the window shown on the next page. A29247-X68-X

26 Installation You have to restart your PC in order to effect the changes that have been made due to the installation. 11. Check Yes, I want to restart my computer now and click <Finish>. The PC is restarted. 20 A29247-X68-X

27 Installation 3.3 Setting Up the PRISMAaudit Database An empty or operational PRISMAaudit database must exist in order for you to install the Device Manager. This is how you create the PRISMAaudit database: 1. Launch the SQL Enterprise Manager. 2. Select Databases and click the right mouse button. 3. Choose New Database from the shortcut menu. The system will display the dialog box shown on the next page. A29247-X68-X

28 Installation 4. Enter the database name in the Name field (for example domain). In the column Location, you can select where the data files are to be stored. In the tab Transaction Log, you can select where the transaction logs are to be stored. 5. Make the settings as shown in the figure above and confirm with <OK>. The system will store the settings. 22 A29247-X68-X

29 Installation 6. The displayed configuration of the SQL Server is recommended. For details see SQL documentation. A29247-X68-X

30 Installation 3.4 Settings in ODBC The settings in ODBC establish the connection to an SQL server. This is how you make the settings in ODBC: 1. Click the <Start> button and choose Settings Control Panel ODBC-Data Sources. The system opens the ODBC Data Source Administrator dialog box. 2. Click the tab labelled System DSN. The system will display the options shown below: 3. Click <Add>. The system will display the window shown on the next page. 24 A29247-X68-X

31 Installation 4. In this window, choose SQL Server and click <Finish>. The system will display the window shown on the next page. A29247-X68-X

32 Installation 5. Enter a name (DSN name) and choose the server you want to connect to. Note: The entry you make here must be identical with the one in the Device Manager configuration program (see also Chapter "Database", page 143). In the field Server, you must enter either the Server name or its IP-address, local is not allowed. 6. You can enter a brief text in the Description field. 7. Click <Next>. The system will display the window shown on the next page. 8. First click <Client Configuration> to check the settings. The system will display the following window: 26 A29247-X68-X

33 Installation TCP/IP should be selected here. 9. Click <OK>. The system again displays the Create a New Data Source to SQL Server window. 10. Check the With SQL Server authentication using... option. 11. Check the Connect to SQL Server to obtain... option and enter the ID and password for the database. 12. Click <Next>. The system will display the window shown on the following page. A29247-X68-X

34 Installation 13. Check the Change the default database to option and choose the data base from the list. 14. Click <Next>. The system will display the window shown on the next page. 28 A29247-X68-X

35 Installation 15. Check the settings in the above dialog box (none of the options should have a check mark against them) and click <Finish>. The system will display the dialog box shown on the next page. 16. Check the information shown in the dialog box, then click <Test Data Source> or confirm right away by clicking <OK>. The system will store these settings. 3.5 Installing the Device Manager (Phase 2) Phase 2 comprises the installation of the Device Manager including the programs BDE (Borland Database Engine) and Intel DMI 2.0 (Service Provider). The Device Manager ships in the form of an installation package on CD-ROM. There is a special menu-driven installation utility. The utility prompts you to make the requisite settings for the installation. Note: The program Intel DMI 2.0 Service Provider is required for the Device Manager, so you have to install these first. A29247-X68-X

36 Installation The Device Manager consists of the following components: Converter Server (History Taker) Client Database Visio You can choose to install some or all of these components. Converter Installation of the DMI Converter. Server Installation of the History Takers. This step also installs the SQL scripts and MIF files. Client Installation of the programs Device Manager Administrator, Device Manager Client and Device Manager DataFetcher. The bitmaps (icons representing devices) are also installed. Database Installation of the database assistant. Visio 2000 Installation of the Visio files which are used for the connection between Visio 2000 and the Device Manager. The table below shows which components/programs have to be installed on the various computer systems. Component Used on Converter PC Process server Database server Client MS SQL Server 7.0 / % Clients or x MS SQL Server 2000 ODBC 3.0 (3.5) x x x x Intel DMI Client x x x Intel DMI 2.0 x x DM Converter (or third party x converter) DM History Taker x Device Manager DM Administrator DM Client DM Data Fetcher x 30 A29247-X68-X

37 Installation DM Configuration x x x Database x Note: You can also choose to install the Device Manager on the process server and/or database server. You then have the possibility of performing admin tasks on these servers as well recommended in the interest of backup and security. You can install all the components on the same computer system. The above table shows the maximum distribution. For details on how to install MS SQL see Chapter 3.2 "Installing MS SQL Server (Phase 1)", page 12. The settings you have to make for ODBC are given in Chapter 3.4 "Settings in ODBC", page 24. For details on how to install Intel DMI see Chapter "Installing Intel DMI 2.0", page 32. Information about the Converter, the Device Manager History Taker and the various Device Manager components is given in Chapter "Installing the Device Manager", page 34. The database component is dealt with in Chapter 3.7 "Settings in the PRISMAaudit Database Assistant (Phase 4)", page 46. A29247-X68-X

38 Installation Installing Intel DMI 2.0 This is how you install Intel DMI 2.0 from the Device Manager installation CD: 1. Select Intel DMI 2.0 and then Dmtf. 2. Select SDK Intel and then Intel DMI 2.0 Service Provider SDK Version Double-click the program dmi2sdk.exe. The system starts the installation and displays the following window: 4. Read and observe the information in the above window and then click <Next>. The system will display the window shown on the next page. 32 A29247-X68-X

39 Installation 5. Leave the settings as they are and click <Next>. This completes the installation of the Intel DMI 2.0 program. The system has created a program group called Intel Installation. This is displayed when you click the <Start> button and choose Program Files Intel DMI 2.0 SP SDK v Check that the window on your screen contains the line highlighted under Services in the figure below. Click the <Start> button and choose Settings Control Panel and then Services. The system will display the following window: A29247-X68-X

40 Installation If the highlighted line is shown, the Intel DMI 2.0 Service Provider has been installed correctly Installing the Device Manager This is how you install the Device Manager: 1. Start Windows NT / Windows 2000 and insert the Device Manager installation CD into the CD drive. 2. Start the CD drive. 3. Double-click the program setup.exe. The system begins the installation. First you are asked to select a language for the installation of the Device Manager. 34 A29247-X68-X

41 Installation 4. Choose English and click <OK>. The system will display the following window: The system proposes a folder for the installation of the Device Manager. 5. Either confirm the suggestion or select a different folder. Then click <Next>. The system will display the window shown on the next page. A29247-X68-X

42 Installation By scrolling down you will see, in addition to the components currently visible, the following components: Océ License and User Interface (PRISMAaudit Toolbar). When this window opens, all the Device Manager components are selected for installation (as shown above). You can install some or all of the components. Note: See the table on page 30 for details about which components to install on which system. 6. Deselect the components you do not want to install and then click <Next>. 7. Only if you marked the component Server (History Taker) for installation, will you see the following window: 36 A29247-X68-X

43 Installation 8. Either leave the default setting or enter a user account and password and click <Next>. Note: The user account must be registered in Windows NT / Windows 2000 and have a valid domain name. The services will only be installed correctly if there is a valid entry in Windows. The system will display the window shown on the next page. A29247-X68-X

44 Installation 9. You do not have to make any entries in the above window. Click <Next> to continue the installation. The system next runs the Océ License component (assuming you have selected this component for installation). This component is described in Chapter 3.6 "Océ License Manager (Phase 3)", page 40. Next the PRISMAaudit toolbar is installed (assuming you selected it for installation). The system completes the installation and then opens the window shown on the next page. 38 A29247-X68-X

45 Installation You have to restart your PC to put the installation settings into effect. 10. Accept the default setting, Yes, I want to restart my computer now and click <Finish>. This completes the installation procedure. However, before you can begin work with the Device Manager, you have to make certain settings in the PRISMAaudit database assistant (see Chapter 3.7 "Settings in the PRISMAaudit Database Assistant (Phase 4)", page 46) Database Login Before you launch the database assistant (see Chapter 3.7 "Settings in the PRISMAaudit Database Assistant (Phase 4)", page 46), you have to specify which database the PRISMAaudit Systems Manager is to access. You enter this information by way of the configuration program. This is how you specify the database: 1. Launch the Device Manager Configuration program (click the icon in the PRISMAaudit toolbar or on the menu bar, choose Start Programme Océ PRISMAaudit Device Manager DM Configure). The system will display the following window: A29247-X68-X

46 Installation 2. Double-click the Database icon. The system will display the following dialog box: 3. Enter the ODBC Data Source and the user ID and password for the database. 4. Click <OK>. An entry is made in the Registry specifying which database the PRISMAaudit Device Manager will access. 3.6 Océ License Manager (Phase 3) All PRISMAaudit products ship with a restricted license, which prevents unauthorised copies from being made of the software. To gain access to the complete functionality of the Systems Manager you must first assign the software a license number. You need administrator's access rights to enter the license details. 40 A29247-X68-X

47 Installation Restricted License Following the installation you can work with the Device Manager for 30 days without assigning a license number. The number of devices which can be created and monitored with the Device Manager is limited to two non-océ devices. The number of Océ devices to be monitored is unlimited. Without a valid license, the product will be running in Demomodus. The Device Manager may only be installed once in demo mode on the PC. If you assign a license number within the 30-day period, the installed Device Manager automatically becomes a licensed product. You do not need to re-install the software. Note: The license number must be matched to the PC which is running the History Taker service. After the licensing process is completed, the services have to be restarted License A license number is valid for one particular PC and PRISMAaudit product. You are provided with the number by the Océ support organisation. The license agreement for the Device Manager includes: The period of time in which the Device Manager can be used and the number of devices to be monitored. Note: Bear in mind that you cannot exceed the number of agreed devices. The system issues a warning when the number of agreed devices is reached. All the licensing entries are valid for one PC and the associated MAC adapter Installing the License Manager The PRISMAaudit product is licensed using the Océ License Manager. This is launched with the PRISMAaudit installation utility. When you launch Setup.exe you are first shown a window for selecting the language. Next comes the welcome window and the window with the software license agreement. Following this, you enter the path in which you want to install PRISMAaudit. The windows are shown in Chapter "Installing the Device Manager", page 34. This window is then shown: A29247-X68-X

48 Installation 1. Select the License Manager and click <Next>. The system will display the following window: 42 A29247-X68-X

49 Installation The title bar shows the local name of the PC and its network address. This is the same as the MAC address of the network adapter. The network has to be configured appropriately in order for these details to be shown. The left section of the window lists the products installed on the system and their versions; the right section lists the license keys plus information about the selected product. A detailed description of how to install and operate the License Manager is provided in the help file, so this manual merely gives some basic guidelines. You can import the license from diskette or CD or enter it manually. This is how you import the license: 1. Launch the License Manager and choose File Open on the menu bar, or click. A29247-X68-X

50 Installation The system will display the following window: 2. Select the file with the license key and click <Open>. The system shows the following window, initially without data. 3. Click <Import> to import the data and show it in the window. 44 A29247-X68-X

51 Installation 4. Close the window. The system asks if you wish to save the data. 5. Save the data. After the save operation your product is licensed. You can also enter the license details manually. 1. Choose Licence New on the menu bar. 2. Enter the product name, version and license key in the Licence key box. The product name may be up to 20 characters long; the version can be up to seven characters long. A29247-X68-X

52 Installation 3. Click <Accept Changes>. The system saves your entries. If you are still in the installation procedure, continue with phase 4, "Settings in the PRISMAaudit Database Assistant". If you have been working in demo mode, you have to restart the services in order to work with the Device Manager (see Chapter 4.1 "Starting the System", page 55). 3.7 Settings in the PRISMAaudit Database Assistant (Phase 4) Note: Before you open the Database Assistant, you have to first create an ODBC connection. See Chapter "Database Login", page 39. In phase 4 you make the settings in the PRISMAaudit database assistant. Use the database assistant to configure tables for the base system and the Device Manager. The base system contains the tables for user administration (at first empty). Contents are only added if the tables for the Device Manager are created/updated. The database assistant is installed if you elected to install the Database component for the Device Manager (see also page 36). This is how you make the settings: 1. Double-click the database assistant icon. The system will display the following dialog box: 2. Select the Device Manager component and click <OK>. The system will display the window shown on the next page. 46 A29247-X68-X

53 Installation The first step is to establish the connection with the PRISMAaudit database. 1. Click the tab labelled DB Connection and click <Connect to database>. The system will display the dialog box shown on the next page. Note: The following two windows are not shown, if in the registry a database key is registered (HKEY_LOCAL_MACHINE\SOFTWARE\OPS\Oce PRISMAaudit\Database). If those entries are correct, then proceed with step 4. If not, then yuo need to exit the DB Assistent and start the Device Manager Configuration program. Then modify the settings and restart the DB Assistent. For details see Chapters 9.1 "Entering Parameters", page 141 and "Database", page 143. A29247-X68-X

54 Installation 2. On the tab labelled Machine Data Source, select the database configured for PRISMAaudit and click <OK>. The system will display the following dialog box: 3. Enter the database user ID in the Login ID field and enter the password in the Password field. 48 A29247-X68-X

55 Installation 4. Click <OK>. The system will display the following window: This window shows the entries you have made so far. The display is for information purposes. 1. In the database assistant, click the tab labelled Base System. The system will display the window shown on the next page. A29247-X68-X

56 Installation 2. If this is the first PRISMAaudit installation, check the Base System tables CREATE option and then click <Apply>. The system notifies you that existing tables, even those of other PRISMAaudit Managers, will be overwritten and creates the tables for the base system. Note: The installation procedure creates these default users: administrator OPS Administrator profile operator operator Operator profile supervisor supervisor Super profile gast gast Guest profile manager manager Super profile The passwords are case-sensitive. Create a few users in the Device Manager Administrator (see Chapter 5 "User Administration", page 61). 50 A29247-X68-X

57 Installation Finally, you have to create the tables for the Device Manager. 1. In the database assistant, click the tab labelled Device Manager. The system will display the following window: 2. If this is a first time installation, check the Device Manager tables CREATE option and click <Apply>. The system creates the tables. This completes the entries in the database assistant. 3.8 Configuring the Device Manager (Phase 5) Phase 5 entails making entries in the Device Manager configuration program. After completing phases 1 to 4 you can launch the Device Manager components: Device Manager Administrator Device Manager Client Device Manager DataFetcher A29247-X68-X

58 Installation Device Manager Configuration DBAssistant (if selected for installation) The program group called Océ PRISMAaudit Device Manager has also been created. (<Start> button Program Files Océ PRISMAaudit Device Manager). In addition, the PRISMAaudit toolbar was added to your desktop (if selected at the installation): The PRISMAaudit Toolbar contains Icons representing the installed PRISMAaudit components. If you now launch the Device Manager Client, you will see that the evaluations are empty because you have not yet defined any devices. The procedure for defining devices is described in Chapter 7 "Device Types and Devices", page Deinstalling the Device Manager A deinstallation utility is always installed for the Device Manager, irrespective of which components you have chosen to install on the system. For example, you should deinstall the Device Manager before installing a new version of the software. How to Remove the Program This is how you deinstall the Device Manager: 1. Click the <Start> button, choose Settings Control Panel and then Add/Remove Programs. The system will display the following window: 52 A29247-X68-X

59 Installation 2. Select the entry Océ PRISMAaudit Device Manager and click <Add/Remove>. The system removes all the programs that are part of the Device Manager. Note: The services History Taker and DMI Converter can only be deleted after they have been stopped. The deinstallation process always removes all the components of the Device Manager. It is not possible to remove individual components. A29247-X68-X

60 Installation 3.10 Visio Link The following entries are required in the registry for the Visio link, which enables Visio to launch from the Device Manager: VisioEnabled: digit (1 enabled (allows Visio to be opened separately within the Device Manager window ), 0 not enabled) VisioFile Visio file, full path name (see page 152) VisioMarker Additional text to be shown in the refresh window This is how you make settings for the Registry: 1. Start the editor for the Registry (<Start>-button Run). The system will display the following dialog box: 2. Enter regedit and click <OK>. The system opens the window Registry editor. 3. Choose HKEY_LOCAL_Machine Software OPS OcePRISMAaudit DeviceManager. 4. Enter the appropriate values and close the window again. The system confirms the values you have entered. The Visio shapes are identified by way of the device names as entered in the Device Manager. These names have to be entered as properties in the Visio drawing object. Visio and the Device Manager communicate via OLE automation. 54 A29247-X68-X

61 Logging On and Off 4 Starting and Operating the Device Manager This chapter describes what you have to do to make the Device Manager operational. You need special access rights to perform the tasks described in this chapter. 4.1 Starting the System Starting the Database Server This is how you start the database server: 1. Press the power switch on the PC (the green light comes on). The computer boots up and loads the operating system. Loading can take several minutes. When the operating system is loaded, the Windows NT / Windows 2000 startup window displays. A dialog box requires you to log in. 2. Press the Ctrl+Alt+Del key combination. The system displays a dialog box for entering a user name and password. 3. Enter the user name and password. Starting the Process Server The following processes has to be running on the process server for the Device Manager to operate: History Taker for DMI History Taker for SNMP Another prerequisite is a correct configuration of the nodes (see Chapter 8.8 "Nodes", page 131.) This is how you start the process server: 1. Press the power switch on the PC (the green light comes on). The computer boots up and loads the operating system. Loading can take several minutes. A29247-X68-X

62 Logging On and Off When the operating system is loaded, the Windows NT / Windows 2000 startup window displays. A dialog box requires you to log in. 2. Press the Ctrl+Alt+Del key combination. The system displays a dialog box for entering a user name and password. 3. Enter the user name and password. After you have successfully logged in, the processes of the Systems Manager appear as icons on the screen. Stopping/Starting Processes Manually This is how you stop and start processes manually: 1. Choose Start Settings Control Panel Services. The system will open the following dialog box: 2. Check the individual services and stop or start them. Database Connection The first time you launch the Device Manager you may also have to configure the database connection. 56 A29247-X68-X

63 Logging On and Off 4.2 Logging On and Off Starting the Operator PC (Device Manager client) This is how you start the operator PC: 1. Press the power switch on the PC (the green light comes on). The computer boots up and loads the operating system. Loading can take several minutes. When the operating system is loaded, the Windows NT / Windows 2000 startup window displays. A dialog box requires you to log in. 2. Press the Ctrl+Alt+Del key combination. The system displays a dialog box for entering a user name and password. 3. Enter the user name and password. After a successful logon, the PRISMAaudit Toolbar is displayed on the monitor (if it was installed). By clicking on the corresponding symbol you start the Device Manager Client. If the tool bar was not installed, you open the Device Manager the <Start>button. The Device Manager Client / Administrator displays the interface for operators/administrators. This is how you log on the Device Manager: 1. By clicking on the corresponding symbol you start the Device Manager Client. If the tool bar was not installed, you open the Device Manager the <Start>-button. The system will display the following dialog box: 2. Enter your user ID (in the User Name field) and your password. The system will display the main window of the Device Manager (see Chapter "Device Manager Administrator Window", page 76). A29247-X68-X

64 Logging On and Off Note: The system issues a message if you make a mistake typing in your user name or password. Confirm the message and enter the correct values. Logging off from the Device Manager This is how you log off from the Device Manager: 1. On the menu bar, choose File Exit. The system will display the following dialog box: 2. Click the <Yes> button. This closes the Device Manager on your PC. User ID and Password You need a user ID and password to work with the Device Manager. The system administrator assigns user IDs to the different users, and also the respective access authorisations (see Chapter 5 "User Administration", page 61). Refer to Chapter 5.4 "Settings following Installation", page 71 for a list of the default access rights assignments. Note: The installation procedure creates these default users: administrator OPS Administrator profile operator operator Operator profile supervisor supervisor Super profile gast gast Guest profile manager manager Super profile The passwords are case-sensitive. Create a few users in the Device Manager Administrator (see Chapter 5 "User Administration", page 61). 58 A29247-X68-X

65 Logging On and Off 4.3 Monitoring Connections The DMI Converter and the History Taker will display an icon in the status bar when tey are running. When the cursor is placed on top of the icon, its name is displayed. A29247-X68-X

66

67 User Administration 5 User Administration This chapter describes how to manage (administer) users with PRISMAaudit. Before defining new users, profiles or groups, you should read this chapter to familiarise yourself with the basic concept. User administration is a component that is used by all the PRISMAaudit managers. You use this component to define which PRISMAaudit users have which access rights to which PRISMAaudit managers. The access rights or authorisations are implemented by way of profiles, groups and users. Your first step when you begin work with the user administration is to create the profiles. You next define the groups and lastly the users. The Device Manager is installed with the default profile NOPROFILE and the group NOGROUP. This group is assigned the profile NOPROFILE. NOPROFILE does not have any access authorisations when it is installed, so nor does NOGROUP. Consequently, if you create a new user directly after the installation and assign the user to NOGROUP, the user will not have any access rights. If you launch the Device Manager with the new user s login, the program will start but none of the functions will be available. You can make the functions accessible for the new user either by modifying NOPROFILE, or by creating a new profile of your own. You then assign this profile to a group and change the group affiliation of the user. This interrelation is the reason why you have to create the items in a certain order: first the profile, then the group, then the user. Note: The installation procedure creates these default users: administrator OPS Administrator profile operator operator Operator profile supervisor supervisor Super profile gast gast Guest profile manager manager Super profile The passwords are case-sensitive. A29247-X68-X

68 User Administration 5.1 Managing Profiles A profile is a definition of access rights for a PRISMAaudit manager, in this case the Device Manager. In the profile, you define which access rights are valid for the selected manager. There are functions for creating, editing and deleting profiles Creating a Profile This is how you create a profile: 1. On the menu bar, choose Configure Users or click on the toolbar. The system opens the following window: 2. Click the right mouse button in the Profiles list and choose New Profile from the shortcut menu. The system opens the following dialog box: 62 A29247-X68-X

69 User Administration 3. Enter the name of the user profile. 4. Select the component for which these access privileges apply (here the Device Manager). The system displays the possible access privileges. 5. Select the privileges that you want to assign to the user profile. 6. If you wish to define access privileges for a further PRISMAaudit component, select this component and repeat steps 4 to Click <OK>. The system closes the dialog box. The new user profile is now registered in the PRISMAaudit user administration Editing a Profile You can change the assignment of access rights in an existing profile. This is how you edit a profile: 1. On the menu bar, choose Configure Users or click on the toolbar. The system will open the window depicted on page 62. A29247-X68-X

70 User Administration 2. Select the profile you want to edit and press the right mouse button. 3. Choose Edit Profile from the shortcut menu. The system will open the window depicted on page Enter your changes. You can change the access rights in this profile for all the PRISMAaudit managers. You can add rights and/or deactivate them. 5. Click <OK>. The system stores the changed profile in the PRISMAaudit user administration Deleting a Profile Note: You cannot delete a profile without first cancelling its assignments to groups. Check whether the assignments are still in use. If necessary, assign a different profile to the group concerned, and then delete the profile. This is how you delete a profile: 1. On the menu bar, choose Configure Users or click on the menu bar. The system will open the window depicted on page Select the profile you want to edit and press the right mouse button. 3. Choose Delete profile from the shortcut menu. The system opens the following dialog box: 4. Click <OK> to delete the profile. The system removes the profile from the PRISMAaudit user administration. 64 A29247-X68-X

71 User Administration 5.2 Managing Groups A group creates the link between the users and the access authorisations. There must be a profile assigned to a group. This affiliation gives the group the access rights defined in the profile. There are functions for creating, editing and deleting groups Creating a Group This is how you create a group: 1. On the menu bar, choose Configure Users or click on the toolbar. The system opens the following window: 2. Click the right mouse button in the Groups list and choose New Group from the shortcut menu. The system opens the following dialog box: A29247-X68-X

72 User Administration 3. Enter the name of the user group. 4. Select the user profile that you want to assign to this group. 5. In the Other Users list select all the users whom you want to assign to this group. 6. Click <<Insert<<. The selected users are assigned to the user group. They receive the access privileges defined by the user profile. 7. Click <OK>. The system closes the dialog box. The user group is now registered in the PRISMAaudit user administration. Note: Consider that a user can only belong to one user group. When you assign a user to a group using the <<Insert<< function, the system deletes the existing assignment of this user to another group. For example, if a user has up to now belonged to the group AdmGroup and you assign the user to group GuestGroup, the user will then only belong to GuestGroup. Accordingly, the user will also only have the access rights of this group. 66 A29247-X68-X

73 User Administration Editing a Group This is how you edit a group: 1. On the menu bar, choose Configure Users or click. The system will open the window depicted on page Select the group you want to edit and press the right mouse button. 3. Choose Edit Group from the shortcut menu. The system will open the window depicted on the previous page. 4. Enter your changes. You can assign a different profile to the group, and/or assign different users to the group. 5. Click <OK>. The system stores the changed group in the PRISMAaudit user administration Deleting a Group Note: You cannot delete a group if any users still belong to it. Check whether the group is still in use. If necessary, change the assignments, and then delete the group. This is how you delete a group: 1. On the menu bar, choose Configure Users or click on the menu bar. The system will open the window depicted on page Select the group you want to edit and press the right mouse button. 3. Choose Delete Group from the shortcut menu. The system opens the following dialog box: A29247-X68-X

74 User Administration 4. Click <OK> to delete the group. The system removes the group from the PRISMAaudit user administration. 5.3 Managing Users A user is always assigned to a group. This affiliation gives the user the access rights of the group. The group, in turn, is assigned a profile in which each of the access authorisations are defined, e.g. the authorisation to generate error statistics. Note: Bear in mind that a user can only be assigned to one group at a time if you change the affiliation, the access rights of the user will also change Creating a User This is how you configure settings for user administration: 1. On the menu bar, choose Configure Users or click on the toolbar. The system opens the following window: 2. Click the right mouse button in the Users section and choose New User. The system opens the following dialog box: 68 A29247-X68-X

75 User Administration 3. Enter the name of the user. Once you have saved the data with <OK> you will no longer be able to change the name. 4. Assign a password, and re-enter the password in the PWD Confirm field. 5. Select the group to which you want to assign the new user. This group affiliation determines which access rights the user will have. 6. Click <OK>. The system registers the new user in the PRISMAaudit user administration Changing User Data This is how you change the data of a user: 1. On the menu bar, choose Configure Users or click on the toolbar. The system will open the window depicted on the previous page. 2. Select the name of the user whose data you want to change and either double-click the right mouse button, or click once and choose Edit User. The system opens the following dialog box: A29247-X68-X

76 User Administration 3. Check all the user data displayed in the dialog box and make changes if necessary. You can change the password and assign the user to a different group. Bear in mind that by changing the group affiliation you will also assign the user a different set of access rights. 4. Click <OK>. The system registers the changes in the PRISMAaudit user administration Deleting Users This is how you delete a user: 1. On the menu bar, choose Configure Users or click on the toolbar. The system will open the window depicted on page Select the user name. Click the right mouse button and choose Delete User. The system asks you to confirm the delete operation: 3. Click <OK>. The system removes the user from the user list and therefore also from the user group. 70 A29247-X68-X

77 User Administration 5.4 Settings following Installation Following installation, the Device Manager access rights are allocated as shown in the table below. The Administrator s Guide explains how to adapt user administration settings to specific requirements. Access right Administrator Shift Manager Operator Guest Manager Configure device types X Configure devices X Launch statistics X X - - X Launch error statistics X X - - X Launch utilization statistics X X - - X Define time periods for statistics X X - - X Detail view for devices X X X - X Define device groups X X X - X Select history attributes X Configure devices X Delete devices X Set up device types X Delete device types X Set TWIN mode X Create configuration table ( PRT41, X PRT51, PRT61 ) Set/terminate service state X Set mapping of logical to physical X states Edit filters X Set refresh interval X X X - X Assign standard attributes X Set up converter PC nodes X Define users X Define profiles X Define user groups X Assign (user) names X Start Device Explorer X X X X X View device status X X X - X View device group X X X - X View device group which devices are X X X - - in group Delete device groups X Create device group X Edit Shifts X - X - - Launch Timeline Statistic X X A29247-X68-X

78 User Administration Access right Administrator Shift Manager Operator Guest Manager Launch Performance Statistic X X Create Production lines X - X - - Edit Production lines X - X - - Delete Production lines X Display Production lines X X Visio View X - X - X Delete Devices, Device Groups X Delete Attribute History X Displaying Job properties X - X - - Save Settings X Define Hosts X A29247-X68-X

79 Administration 6 Device Manager Administrator The Device Manager Administrator provides functions for defining device types and devices in the Device Manager and for configuring your Device Manager system. The terms explained in Chapter 6.1 are important for understanding Chapters 7 and 8. Chapter 6.2 explains the basic elements of the user interface. 6.1 Basic Considerations DMI / SNMP DMI stands for Desktop Management Interface. The devices, that are monitored by the Device manager, deliver their information through DMI to the Device Manager. If a device does not support DMI, a DMI Converter can be used to convert its information into DMI-format. SNMP Equipment with a SNMP agent can directly send its information to the Device Manager (History Taker) without the need for a converter in between The MIF File What is a MIF file? MIF stands for Management Information Format. A MIF file is an ASCII text file. This file contains the description of the device properties. A MIF file specifies the device type. The specification is subdivided into groups, and each group is subdivided into attributes. Basic configuration of a MIF file: Device type Attribute Groups Attributes A29247-X68-X

80 Administration There must be a MIF file for every device type installed. If you install a new device type in the system, you have to assign a dedicated MIF file explicitly to this new device type (see Chapter 7.1 "Creating a Device Type", page 83) Terms Used Physical State Every device type can be in one of several physical states. You have to register these states in the Device Manager. For Océ printers the following physical states are defined in the system: Standby-Ready Ready Paper Insert Preparation Service Clean Stop Pre/Post Device Stop Printer not ready TWIN Stop Operational Stop Logical State Logical states are defined via physical states and filters. This reduces the amount of information to an essential minimum. The operator can then see at a glance whether a device is working, halted or not connected. It is also possible to collect data for statistics for predefined states or accumulated states. The following logical states are defined in the system: Unknown Operational Stop Pre/Post Proc.Stop Error Ready Running Service You can include new physical and logical states and make new assignments (see Chapter 8.3 "Logical States", page 119, "Editing Physical States", page 115 and "Making Mapping Assignments", page 116). 74 A29247-X68-X

81 Administration Filters Filters make it possible for you to consolidate errors in groups. The following filters are defined by default for Océ printers, for example: F01 Operator intervention F02 Error in pre/postprocessing F03 Device error You can define new filters (see Chapter 8.6 "Filter", page 125). When you evaluate the errors, you can define filters to determine which error statistics are obtained (Refer to Chapter 8.6 "Filter", page 125 for an example). Attribute The attributes are used as a means of defining which data is to be stored and evaluated. The most important attributes are defined as standard attributes. The standard attributes are prerequisite for the creation of the standard statistics. You have to edit these standard attributes, i.e. you have to assign them a DMI attribute (see Chapter 8.7 "Standard Attributes", page 129). A29247-X68-X

82 Administration 6.2 Device Manager Administrator Interface Device Manager Administrator Window When you start the Device Manager Administrator, the system will display the following window: This window is termed the main window. Elements of the main window: The window consists of a title bar, a menu bar, a toolbar, a data section and status bar. The title bar contains the program name PRISMAaudit Device Manager and your logon name. 76 A29247-X68-X

83 Administration The menu bar contains the Device Manager Administrator menus. These are described in Chapter The buttons on the toolbar are an alternative way of accessing certain menu commands. The buttons are described in Chapter "Description of Button Functions", page 79. The data section contains 10 tabs. You bring a tab to the front of the window by clicking its title (see Chapter "Functions on the Tabs", page 79). The status bar displays information about the entries which are currently selected and indicates the proportion of the database that is already occupied by data Device Manager Administrator Menus The menus are accessed from the menu bar. A menu contains commands that enable you to execute particular actions. The Device Manager Administrator has the following menus: File Configure View? File The File menu contains the command Exit, which you use to log off the Device Manager Administrator. Configure The Configure menu contains the following commands: Install new Device type Install new Device Clear Devices/Device types Clear Attribute History Users These menu commands, excepting for the User commands, are described in Chapter 8 "Configuration", page 111. The User menu is described in Chapter 5 "User Administration", page 61. A29247-X68-X

84 Administration View The View menu contains the following commands: Toolbar Status bar Refresh Refresh Options Toolbar The toolbar gives you instant access to frequently used functions (see Chapter 6.2.4, "Description of Button Functions", page 79). If you do not want to work with the buttons, you can turn the toolbar off. Normally, the toolbar is displayed (default setting). The command in the menu then has a check mark preceding it. Status bar The next-to-last line on the screen is the status bar. The status bar indicates if there is a connection to the PRISMAaudit database, for example. You can turn off the status bar if you want. Normally, the status bar is displayed (default setting). The command in the menu then has a check mark preceding it. Refresh If you load data and leave it for a period of time without doing any editing, you should refresh the data before continuing work. This is to make sure you will be working with the latest data. Refresh Options You can update data manually or indicate a time interval. By using a time interval, data is automatically updated by the system.? This menu contains the following commands: About Help About Choose this command to display the version number of your Device Manager installation. Help Use Help to open the Device Manager documentation. 78 A29247-X68-X

85 Administration Functions on the Tabs The Device Manager Administrator window contains 10 tabs: Devices Use this tab to define the device names. Device Types Use this tab to edit the physical states and assignments. In addition, the service time and the symbols for the equipment can be assigned. Twin Mode the representation of printers in Twin mode can be seen here. Service Functions for entering service times. Filter Functions for defining error filters. Standard Attributes the attributes from which the standard statistics are made are defined here. Nodes Define the converter PC. Logical States Use this tab to view and edit logical states. Device Configuration Use this tab to make device configuration settings. Hosts The Host s properties are entered in here. The tabs are described in detail in Chapter 8 "Configuration", page Description of Button Functions Some Device Manager Administrator dialog boxes include the following control buttons. Their function is the same in every dialog box. Control buttons: Insert one line Delete one line Edit line Save A29247-X68-X

86 Administration Delete Refresh data The toolbar in the Device Manager Administrator contains the following icons: Define a new device type Define a new device Delete devices or device types Delete attribute history User administration Refresh data Database symbol The symbol on the right indicates whether or not there is a connection to the PRISMAaudit database. When the symbol is green, a connection has been established to the PRISMAaudit database; when the symbol is red, there is no connection. If this happens, check why this is the case or consult your system administrator if necessary. The system re-establishes the connection automatically as soon as the database is running again. Note: You must connect to the PRISMAaudit database in order to display up-to-date data. Always keep the status bar displayed it shows important information. Fill level for the PRISMAaudit database: A percentage figure is shown next to the database symbol. This tells you how much of the database is already full. 80 A29247-X68-X

87 Administration Online Manual The documentation for the Device Manager Administrator component can be opened online. You open the manual via the menu? Help. This gives you rapid, direct access to the information you need. The online documentation provides the following possibilities: You can display the table of contents (like in a printed manual) and browse through the online text. You can proceed directly to a particular chapter by clicking an entry in the table of contents. You can also go via cross references and the index and go straight to the linked information. The help window has two panels. The left panel shows the table of contents or index (depending on what you choose); the right panel the selected text. Use the following buttons to navigate in the online documentation: Display next chapter. Display previous chapter. Display list of contents. Display index. Navigation buttons in the browser (depending which browser you are using): After navigating to a chapter, you can click this button to return to the previous chapter. After using the above button to move back one chapter, you can click this button to navigate forwards. A29247-X68-X

88

89 Device Types/Devices 7 Device Types and Devices This chapter deals with device types and devices. Read this chapter before creating and configuring devices in the Device Manager. The chapter also explains how to delete device types and devices and to remove data from the database. The Device Manager differentiates between device types and devices. A device type can be a particular set of printers or a particular type of inserter. Every device (e.g. every printer) has to be assigned a device type. Before the Device Manager can monitor a device, you have to create a device type, configure the node (mandatory to be done to be able to create a device), configure the device and correctly finish the process. (if necessary) configure the DMI converter (Device Manager configuration program). You need special access rights to perform these tasks. 7.1 Creating a Device Type You perform the following steps to create a new device type: Assign the MIF file and compile it into the database The first step in creating a new device type is to assign the MIF file. The syntactical correctness of the file is checked, and the file is then compiled into the database. Define default attributes The data of the default attributes is stored in the database for evaluation. The standard attributes are a prerequisite for the creation of the standard statistics. Define error filters You can assemble errors in groups e.g. a group of all the errors that can occur in the post-processing equipment. This gives you the possibility of restricting your evaluations to particular sections of the processing line. A29247-X68-X

90 Device Types/Devices Define device icons for the interface The Device Manager Explorer can display the devices being monitored by the Device Manager. You can choose to display devices in an icon and/or a list view. In the icon view, the devices are represented by large icons. The colour tells you at a glance which state the device is in. In the list view, the outer left column contains a small icon in the colour indicating the state. All the devices of a particular type are represented by the same icon. You choose which icon is to represent which device type. Define/enter the physical states When you create a new device type, you have to define and store the physical states which this type of device may have. Assign the physical to the logical states A distinction is made between physical and logical states. The Device Manager works with the logical states. You have to map the physical states to the logical states for each device type. This process enables the wide range of states to be reduced to a minimum set of information. Assign service You can set every device in the system to the Service state. You avoid thereby redundant statues and errors in the standard statistics. You have to perform these steps in the order as given, so the actions you need to complete are all numbered in the description that follows. You are also guided by the system, i.e. the windows are displayed automatically, and brief texts are shown to explain what entries you need to make. After creating a device, you can modify the settings by going via the tabs (see Chapter 8 "Configuration", page 111. This is how you create a new device type: 1. Launch the Device Manager Administrator by double-clicking the program icon and log on. 2. Choose Configure Install new Device Type on the menu bar. The system will display the following dialog box: 84 A29247-X68-X

91 Device Types/Devices The following chapter describes how to compile the MIF file for the device type into the database. The MIF file describes the device attributes. A29247-X68-X

92 Device Types/Devices Compiling the MIF File This is how you compile the MIF file: 3. Enter the path of the MIF file in the MIF file field, or browse for the file you want to use. Click to open a dialog box where you select a file: 4. Select the MIF file and click <Open>. The system will display the dialog box shown on the next page. 86 A29247-X68-X

93 Device Types/Devices 5. Click <Parse>. The system checks the MIF file. Once the check is complete, the message SUCCESSFUL is shown (see next page) and the <Insert> button is made available for selection. The MIF file can then be integrated into the database. A29247-X68-X

94 Device Types/Devices 6. Click <Insert>. The system inserts the data into the database. The message MIF Insertion SUCCESSFUL then appears in the dialog box (see following page). 88 A29247-X68-X

95 Device Types/Devices 7. Click <Exit> to end the process. The system will display the following message box: 8. Click <Yes>. The system closes the MIF parser dialog and displays the window for entering the default attributes. A29247-X68-X

96 Device Types/Devices Assigning Attributes The system displays the following window: Note: You can create a new device type without assigning any attributes. However, the Device Manager will then not be able to evaluate any data. For example, if you do not assign a DMI attribute to the Error attribute, the Device Manager will not have any list of errors. You will not be able to define error filters or generate error statistics. 90 A29247-X68-X

97 Device Types/Devices This is how you assign attributes: 9. The Component field already contains the name of the device type you are creating. In the left half of the window, the system shows all the DMI groups for the selected device type. 10. Double-click one of the DMI groups. The system will display all the DMI attributes belonging to this DMI group. 11. Assign your attributes now. Click the desired DMI attribute in the left half of the group box, hold down the left mouse button and drag the attribute to the standard attribute to which you want to assign it (Button), or click the button of the selected attribute. The system will display the values of the attributes in the corresponding DMI Group and DMI Attribute fields. Your assignment might look like this: A29247-X68-X

98 Device Types/Devices 12. Once you have assigned all the standard attributes, click the <Save> button. The system will store the values you have entered. 13. Click <Next>, to continue with the creation of the device type. The system then displays the window for entering error filters. Undoing and deleting assignments If you make a mistake assigning an attribute, you can cancel or delete the assignment (see Chapter 8.7 "Standard Attributes", page 129). 92 A29247-X68-X

99 Device Types/Devices Defining Filters After compiling the MIF file into the database and assigning the attributes, you can define error filters for the device type. These filters are optional. If you do not need any error filters for your production environment, click <Next> in the following window. This is the window for defining filters: This is how you define a filter. 14. The Component field already contains the name of the device type you are creating. 15. Enter a filter name. 16. Mark the errors you want the system to filter on the list on the right half of the window. A29247-X68-X

100 Device Types/Devices 17. Click the <Save Filter> button. The system will store the new filter. 18. To create another filter, click the <Create Filter> button and repeat steps 15 to Click <Next> to proceed to the next step. The system then displays the window for you to assign the icons and images and enter the physical states Assigning Icons and Images In the Device Manager Explorer you can have the devices presented as icons. You can choose which icons will be used in the display. The Device Manager needs an icon to present devices in the icon view and another element an image for the list view. The image is displayed in front of the line of text. The image colour indicates the state of the device concerned. The system displays the following window: 94 A29247-X68-X

101 Device Types/Devices This is how you assign icons and images: 20. Click the Icon column in the line with the new device type. A small button is then shown (see figure below). 21. Click this button. The system opens the Load Icon for Component dialog box. A29247-X68-X

102 Device Types/Devices 22. Click <Load> in this dialog box. The system opens a dialog box for you to select the file containing the icon bitmap. 96 A29247-X68-X

103 Device Types/Devices 23. Select the file and click <Open>. The selected icon is shown in the Load Icon for Component dialog box. 24. Click <Save> in this dialog box. 25. In the Device Types window, click to save the data. The system registers your selection. 26. Now assign an image to the device type. The procedure is the same as for the icon. In the foreground of the figure below, you can see the dialog box for loading the image. A29247-X68-X

104 Device Types/Devices Note: The way the abbreviation Blob is written tells you whether or not you have assigned an icon. If the text is in upper case characters, an icon has been assigned. The next step is to enter the physical states for the device type Defining Physical States This is how you define the physical states: 27. Click the Phys. States column in the line with the new device type. A small button is then shown (see figure below). 98 A29247-X68-X

105 Device Types/Devices 28. Click the button. The system opens the Physical States dialog box. This is empty the first time it is opened. 29. Click in the dialog box to define a new physical state. The system displays an empty line. 30. Enter the name of the physical state in the Physical State Name column, and its value in the Value column. 31. When you have made your entries, click to save your data. The system registers the data you have entered. A29247-X68-X

106 Device Types/Devices Mapping Physical States to Logical States A distinction is made between physical and logical states. The Device Manager works with the logical states. Therefore you have to map physical states to logical states, making separate definitions for each device type. This process greatly reduces the range of different states to a much smaller set of salient information. Following the installation, the Device Manager knows these logical states: Unknown Operational Stop Pre/Post Proc. Stop Error Ready Running Service Power off Not Avialable Message Paper Insert Toner empty You can enter other logical states. See Chapter 8.3 "Logical States", page 119. The logical states are shown at the Device Manager interface. This is how you make the assignments: 32. Click the column Logical States in the line you want to edit. The system displays a small button (see below, window in background). 33. Click the button. The system will display the following dialog box: 100 A29247-X68-X

107 Device Types/Devices 34. Click in the dialog box to make a new assignment. 35. Select the name for the physical state and assign a logical state to the physical state. A29247-X68-X

108 Device Types/Devices 36. When you have finished entering the states, click in the dialog box to save your entries. The system will store the data you have entered. 37. When you click the display is updated and the data you have just entered is shown. 38. Click <Close> to continue processing. 102 A29247-X68-X

109 Device Types/Devices Assigning the Service State Enter the value here that you have assigned for the physical state Service. The appropriate value is located in the MIF. For Océ printers, for example, the value is 5. Proceed as follows: 39. In the standard window, enter the appropriate value in the Service State column. 40. Click in the standard window to save the data. The system registers the data you have entered Concluding the Process for Creating a Device Type The system now has all the data it needs to create a device type. 41. Click <Finish>. The system concludes the process and displays a confirmation message: 42. Click <OK>. You have now created the new device type with all the requisite data, i.e. you have compiled the attributes for this device type into the system via the MIF file, assigned the standard attributes, defined error filters (optional), defined the icons that will represent devices of this type at the interface of the Device Manager Client, entered the physical states, assigned the physical states to the logical states. You can now installing the devices. The entries you have to make are described in the next section. A29247-X68-X

110 Device Types/Devices 7.2 Installing a New Device Note: Prerequisites for the installation of a new device, is to define a node (see page 131). This is how you install a new device: 1. Launch the Device Manager Administrator by clicking the icon in the PRISMAaudit toolbar and log on. 2. On the menu bar, choose Configure Install new Device. The system will display the following window: 3. Click <New>. 104 A29247-X68-X

111 Device Types/Devices The system again shows the dialog box depicted above. Excepting for Status, all the fields are empty. The entry Initial is preset in the Status field. You cannot change this value when you are making a new definition. As soon as the History Taker encounters a device with the Initial state, it sends the MIF file to DMI-SP (DMI Service Provider). DMI-SP logically initialises the device and then returns a notification to the History Taker. The History Taker sets the device state to Active. The new device is shown in the Device Manager Explorer with Active state. 4. Enter the device name. 5. Select the device type you want to assign to the device. 6. You can enter an explanatory text in the Description field. This text is shown with the properties (which you display by double-clicking the device, for example). 7. Select the address. For more about creating addresses, see Chapter 8.8 "Nodes", page Enter the performance and unit of measure. 9. Select the unit of time and the type. 10. Click <Save>. The new device is configured in the system. When you have completed the steps up to this point, the new device will be shown in the Device Manager Explorer with the icon you have assigned: The device is still in Unknown state. In order for data transfer to take place, you have to configure the DMI converter this is the last step. 7.3 Other devices In order for the Device Manager to monitor SNMP connected devices, special MIB files are required. This applies to the following devices: PRISMAproduction Print Server PRISMAoffice Print Server Printer with SNMP Agents (Host Resource MIB and/or Standard Printer MIB) When setting up these devices the following has to be taken into account: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. A29247-X68-X

112 Device Types/Devices 2. On the menu bar, choose Configure Install new Device. The System will display the following window: The fields in the area SNMP Properties are activated if you selected a node on which the SNMP History Taker runs, in the Connection section above. 3. Fill in the fields for SNMP Properties: Field Device Index Characteristics Polling Interval (sec) Status des Polling Interval (sec) Description 106 A29247-X68-X

113 Device Types/Devices Field Commuty Description 4. Click <Save>. The new device is configured in the system. 7.4 Configuring the DMI Converter You enter the DMI Converter data in the configuration program. This is described in Chapter 9 "Configuration Program", page 141. Note: You have to enter the converter data on the computer system on which the DMI Converter is installed. 1. Launch the configuration program. 2. Double-click the Converter icon. The system opens the dialog box shown on the next page. A29247-X68-X

114 Device Types/Devices Note: The device name you enter here must be identical with the one you assigned in the Device Manager Explorer. See Chapter 7.2 "Installing a New Device", page 104. The name can be changed at a later time. However, the names must always be identical. 1. Fill out all the fields. The entries are described in Chapter "Converter", page Click <Apply> and then <OK>. The system registers your data. You have now completed all the steps for having a device tracked by the Device Manager. 108 A29247-X68-X

115 Device Types/Devices 7.5 Deleting Devices / Device Types You can delete the devices and device types you no longer need. This is how you delete a device or device type: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. 2. On the menu bar, choose Configure Clear Devices/Device types or click. The system will display the following dialog box: 3. In the Item to clear section, indicate whether you want to delete devices or device types; then select the device or device type you want to delete. 4. Click <Delete>. You are prompted to confirm the delete operation. 5. Click <Yes> to delete the device or device type. The system issues a message to confirm that the data has been deleted. Note: By deleting a device type, you also delete all the devices that have been assigned this type. A29247-X68-X

116 Device Types/Devices 7.6 Deleting the Attribute History The data relating to the devices being monitored is stored in the PRISMAaudit database. If you are certain that you will not be needing the data of a particular device again, you can remove the data from the database. For instance, when a device is removed from the production line, you can delete the associated data from the database. Proceed as follows: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. 2. On the menu bar, choose Configure Clear Attribute History or click on the toolbar. The system will display the following dialog box: 3. Enter the date, up to which the data are to be deleted. 4. Select the devices you want to delete the attributes. 5. Click <Delete>. You are prompted to confirm the delete operation. 6. Click <Yes> to delete the attributes. The system issues a message to confirm that the data has been deleted. 110 A29247-X68-X

117 Configuration 8 Configuration This section describes how you define the device names for the different modes of the devices edit device types configure printers as twin printers enter the service times for a device and terminate the service times activate filters assign standard attributes configure nodes configure devices define hosts create a Visio drawing This section overlaps partially with Chapter 7 "Device Types and Devices", page 83. If you are registering a new device for tracking with the Device Manager, follow the instructions in Chapter 7. If you need help on a specific menu command, you should refer to this chapter. 8.1 Devices The Device Manager Explorer displays devices with their names. You can change these names. A printer can be configured to run in different modes, e.g. I mode or CE mode. The printer must have a unique name in each of the modes. By default, the system will add the mode name (such asior CE) to the device name. You can either keep these names for the devices or you can rename them if they do not fit your particular naming system. This is how you rename a device: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. 2. Click the tab labelled Devices. The system will display the following window: A29247-X68-X

118 Configuration The top half of the window will display all the devices configured on the system. For details on creating a device, see Chapter 7 "Device Types and Devices", page If you mark a device, the bottom half of the window will display all the pertinent data of this device. You can change the displayed names. 4. Enter your changes and click the <Save> button. The system will store the changes. The system will now display the changed names of the devices in the lists of the Device Manager Client. Note: When you are creating a new device, you assign it a name, and you enter precisely this name when you configure the DMI converter (see Chapter 7.4 "Configuring the DMI Converter", page 107). This enables the system to establish its connection. The connection continues to exist under the original name even if you have changed the name here. 112 A29247-X68-X

119 Configuration 8.2 Device Types Every device you want the Device Manager to monitor must be configured in the system (see also Chapter 7 "Device Types and Devices", page 83). Every device must be assigned to a device type. You have to assign icons to the device type, enter the device type s physical and logical states, etc. Chapter 7 describes in detail all the steps you need perform to have a device monitored by the Device Manager. The Device Types tab provides functions for changing the assignment of icons, and for editing the physical states and other settings. Proceed as follows: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. 2. Click the tab labelled Device Types. The system will display the following window: A29247-X68-X

120 Configuration Changing Icons When you create a device type in the Device Manager, you have to assign it icons. You can change these assignments later. This is how you assign a new icon (large or small) to a device type: 1. Click the tab labelled Device Types. 2. Click the column Image or Icon for the device type you want to assign a graphic symbol. The selected column will now have a small button. 3. Click the small button. The system will now display the Load Image or Icon for Component dialog box. 4. Click the <Load> button in the dialog box. The system will display a window in which you can select the file which contains the desired icon/image. 5. Select the file which contains the desired icon/image and click the <Open> button. The icon/image stored in the file is then displayed in the Load Icon for Component. 6. Click the <Save> button. The system will now register the selected icon/image. 7. Click the button to save the data. The system will now confirm the data Changing the Service State If you change the value of the physical state Service, you must enter the changed value here. This is how you change the service state: 1. Click the tab labelled Device Types. 2. In the Device Types window, click the Service State column and enter the desired value. 3. Click the button to save the value. The system confirms the value you entered. 114 A29247-X68-X

121 Configuration Note: Bear in mind that the Service State field must always contain a value. If here is no Service state defined for a device, you should enter a 0 (zero) here Editing Physical States You enter the physical states when you create the device type. The following physical states must be stored for Océ printers: There are two more states in addition to the physical states shown in the window above: Operational Stop and TWIN Stop. You can enter additional states, modify existing states, and delete those which no longer exist. This is how you edit the physical states: 1. Click the tab labelled Device Types. 2. Click the Phys. States column in the line with the device type whose states you want to change. The system will display a small button. 3. Click the button. The system will display the Physical States dialog box shown on the preceding page. 4. Click to enter a new state; click to delete a state; and click to modify a state. A29247-X68-X

122 Configuration The system displays an empty line if you elect to define a new state. 5. Enter the name, then enter the value in the Value column, or change the values that are already in the fields. 6. Once you have entered all the states, click the button to save the information and then click <Close>. The system confirms the values Making Mapping Assignments The physical states have to be mapped to the logical states. You can also assign error filters to the logical states. Example: If a red device icon is shown in the list view in the Device Manager, the device concerned is in error state. This logical state can represent a variety of physical errors. You yourself have to determine which physical errors will cause the device to enter the logical Error state. This is how you make or modify mapping assignments: 1. Click the tab labelled Device Types. 2. Click the Map column in the line with the device type whose mapping you want to change. The system will display a small button. 3. Click the button. The system will display the Map Physical State to Logical State dialog box shown on the following page, but without any entries. The dialog box shown on the next page is an example of mappings made for Océ printers. 116 A29247-X68-X

123 Configuration 4. Click in the Physical State Name column. The system will display a small button. 5. Click the button. The system will display the physical states stored previously. A29247-X68-X

124 Configuration 6. Select a physical state. 7. Accordingly, select the logical state you want the physical state to be mapped to. The system will display the selected states, and in the Colour column, the corresponding colour. 118 A29247-X68-X

125 Configuration 8. You can also map an error filter. You select this the same way you selected the preceding columns. The system provides a range of filters you can select from, which were defined for this type of device (see Chapter 8.6 "Filter", page 125). 9. Click the button to create a new line and map the next state. Click to delete an assignment, and to edit an assignment. 10. Once you have mapped all the states, click the button to save the information. The system confirms the data. 8.3 Logical States The Device Manager provides seven default logical states for devices. The logical states of Océ printers are assigned the following colours: Unknown grey Operational Stop pink Pre/Post Proc. Stop white Error red Ready yellow A29247-X68-X

126 Configuration Running green Service blue Power off brown Not Available aubergine Message blue/green Paper Insert dark blue Toner empty moss-green You can edit the default states and define new ones of your own. This is how you edit/define a logical state and assign a colour to a state: 1. Launch the Device Manager Administrator (click the icon in the toolbar) and log on. 2. Click the tab labelled Logical States. 3. Click to define a new state; to delete a state; or to edit a state. If you are defining a new state, you are shown an empty line. 4. Enter the name of the state and then the value in the Value column. The system will display a small button. 5. Click the button. The system will display a dialog box in which you can select colours. You are now looking at the windows shown below: 120 A29247-X68-X

127 Configuration 6. Select the desired colour and click the <OK> button. 7. Once you have defined all the logical states and assigned the colours, click the button to save the information. The system confirms the values. 8.4 Twin Mode If you want to use printers as twins, you will have to configure them accordingly. The devices list will always display devices configured as twins side by side (Refer to the Device Manager Client manual). This is how you define twin mode for devices: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. A29247-X68-X

128 Configuration Click the tab labelled Twin Mode. The system will display the following window: The top half of the window displays the devices currently configured as twins. The bottom half of the window displays all the devices installed in the system which are currently available as solo devices. 2. In the Device Name area, mark the first device you want to work as a twin and click the button. The system will now display the selected device in the empty field to the right of the. 3. In the Device Name area, mark the second device you want to work as a twin and click the button. 122 A29247-X68-X

129 Configuration The right half of the window will now display the two devices you have selected. If you have not made the correct selection, you can cancel your selections by clicking the <Clear both> button. 4. If you have made the right selection, click the <Make Twin> button. The system will now display the printers configured as twins in the upper half of the window. The Device Name area at the bottom half of the window will no longer display the devices, since they are no longer available as Solo devices. This ensures that the devices you have configured here as a twin system will in fact be presented side by side in the Device Manager Explorer. This is how you remove a twin configuration: 1. Mark the twin you wish to remove in the upper half of the window. 2. Click the <Remove Twin> button. This will remove the twin configuration and the two devices will again be displayed in the bottom half of the window, in the Device name area. They are now available as solo devices again. 8.5 Service You can set every device in the system to Service state. You can then monitor how long a device was in Service state and show this in the utilisation statistics, for example. In addition, you can avoid redundant (nonproductive) statuses and errors from being shown in the standard statistics. The service state can be set in both the Device Manager Client and Device Manager Administrator. This is how you set a device to service state: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. 2. Click the tab labelled Service. The system will display the following window: A29247-X68-X

130 Configuration 3. Select the device you want to be serviced and click the box in the Service column. The box will now have a check mark. 4. Click the <Update> button. The selected device is now in Service state. A coloured bar (default blue) is then shown next to the check mark. The device icon is shown in the configured colour in the icon overview in the Client; "Yes" is entered in the Service column in the list view. You can also see the device state in the utilisation statistics. Once the servicing is concluded for this device, you will have to deactivate the Service state. This is how you deactivate the Service state: 1. Choose Configure Service on the menu bar. The system will display the Service window shown on the preceding page. 124 A29247-X68-X

131 Configuration 2. Remove the check mark in the Service column for this device and click the <Update> button. The Service state is now deactivated. Note: In the Device Manager Client you can set Service under the Configure menu and menu option Service. 8.6 Filter Filters give you the possibility of collecting errors in groups for use in evaluations. For example, you can define a filter to collect all the errors which have to be corrected by the operator, or for which the operator is in some way responsible. Example Name of error Meaning Filter 1 Filter 2 Paper End Operator intervention required X Paper flaps open Paper flaps were opened by operator to load paper Front door open Door was opened by operator X Not Ready Stop key was pressed X Motor temp to high Service all needed X X Filter 1: All errors for which the operator is responsible or which can be corrected by operator intervention Filter 2: Errors triggered by the printer This function is optional. This is how you create a new filter: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. 2. Click the tab labelled Filter. The system will display the following window: A29247-X68-X

132 Configuration The right half of the window displays all the possible errors for the selected device type. 3. Select a device type for which you want to create a filter. 4. Click the <New Filter> button. The system will add an empty line in the Filter Name display area. 5. Enter a name and mark the errors you want the system to filter on the list on the right half of the window. 6. Click the <Save Filter> button. The system will store the new filter. If you are creating a filter and decide to change some of the settings you have made, you can discard entries by clicking the <Reset Filter> button. This has the effect of deactivating all the selected fields. However, you can only do this provided you have not yet saved the changed filter. 126 A29247-X68-X

133 Configuration If you want to discard the entire filter you are creating, click the <Cancel Filter> button. Again, this is only possible provided you have not yet saved the filter. If you no longer need a filter stored in the system, you can delete it. 1. Mark the filter and click the <Delete Filter> button. The system will display a dialog box: 2. Click the <Yes> button. The system will then delete the filter. Example This example shows the error statistics for a device, obtained using different filters. Filter: F01 Operational Stop F02 Pre/Post Proc. Stop F03 Error Error statistics of device A_PS350-1 without a filter All errors that occurred in the selected period are included in the statistics. A29247-X68-X

134 Configuration The two figures on the following page show the error statistics for the same device, but obtained using filters. Error statistics for device A_PS350-1 with the F03 filter If you select filter F03, only one error will be shown in this example. 128 A29247-X68-X

135 Configuration Error statistics for device A_PS350-1 with the F01 filter 8.7 Standard Attributes The following standard attributes are defined in the Device Manager: Error Status Pagecount Manufacturer Errortext Mode Config The attributes defined as standard, for example Mode and Config, must always be available in order to be able to generate the standard statistics completely. You must assign the standard attribute to the corresponding DMI attribute, which means that you must inform the Device Manager where it can find the required value in the database. A29247-X68-X

136 Configuration Example for Océ Printer: The value of the standard attribute named Manufacturer is stored in the DMI group ComponentId under the DMI attribute Manufacturer. The names of the standard attribute and the DMI attribute need not be the same. This is how you assign the standard attributes to the DMI attributes: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. 2. Click the tab labelled Standard Attributes. The system will display the following window: The left panel of the window shows the structur of the attributs (MIF-File). 3. Select the appropriate device type In the Component field. 4. Double-click one of the DMI groups. 130 A29247-X68-X

137 Configuration The system will display all the DMI attributes belonging to this DMI group. 5. Assign your attributes now. Click the desired DMI attribute in the left half of the group box, hold down the left mouse button and drag the attribute to the standard attribute to which you want to assign it (Button), or click the button of the selected attribute. The system will display the values of the attributes in the corresponding DMI Group and DMI Attribute fields. 6. Once you have assigned all the standard attributes, click the <Save> button. The system confirms the selected values. If you want to cancel an assignment you have made, you have to delete it. In the DMI Group or DMI Attribute column, select the field you want to delete, then click <Delete>. The system removes this assignment. If you inadvertently delete assignments you can restore them by clicking <Reset>. The system restores the old state. Bear in mind that the undo operation only works if you have not yet saved the changes. Cancelling and Deleting Assigned Attributes You can cancel assignments and also delete them when they are no longer needed. You can cancel assigned attributes as long as they have not yet been saved. If you have made one or several attribute assignments but decide you do not want to use them in the system, click the <Reset> button. The system will then restore the old state. Bear in mind that this is only possible if you have not yet saved the assignments. If you want to remove a saved assignment, you will have to delete it. 8.8 Nodes The History Taker gets its information from the Nodes. Changes become effective only if the History Taker was stopped prior to making any changes. Here you can enter the name and address of the PC to be used as a converter. Proceed as follows: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. 2. Click the tab labelled Nodes. The system will display the following window: A29247-X68-X

138 Configuration 3. Click to insert a new line. 4. Fill out all the fields. For all fields, except Name and Address, the system provides you values to choose from. In the field Acquisition, choose MIF for DMI-Node devices, or MIB for SNMP devices. In the field HostName, choose the Host which has the corresponding History Taker Service installed. 5. Click to save the data. The system will display the dialog box shown on the following page. 132 A29247-X68-X

139 Configuration 6. Click <Yes> to save the record. The system saves your data. Modifying / Deleting You can modify (with the button) or delete (with the button) the data for a defined node. 8.9 Device Configuration Use this tab to define the device data. You can create new devices in the system or modify the data of existing ones. If you wish to create a new device, you can also go via the menu bar, choosing Configure -> Install new Device (see Chapter 7.2 "Installing a New Device", page 104). This is how you install a new device: 1. Launch the Device Manager Administrator (click the icon in the PRISMAaudit toolbar) and log on. 2. Click the tab labelled Device Configuration. The system will display the following window: A29247-X68-X

140 Configuration 3. Enter your changes and click <Save>. The system will store the changed data Hosts If the Device Manager must monitor a large number of devices, you can improve the performance of the system by the using several History Takers. Each History Taker must be installed on a separate host. This is how you create a new host: 1. Launch the Device Manager Administrator (click on the icon in the PRISMAaudit toolbar) and log on. 134 A29247-X68-X

141 Configuration 2. Clock the tab labelled Hosts. The system will display the following window: 3. Register the Host, and check-off which History Taker (DMI and/or SNMP) is running. 4. Click to save the data. The system will display the following window: A29247-X68-X

142 Configuration 5. Click <Yes> to save the data. The system saves your data. Modifying / Deleting You can modify (with the button ) or delete (with the button ) the data for a defined host Visio Link The Visio link provides additional possibilities for presenting information. You can set up processing lines in the Device Manager Explorer and assign specific Visio drawings to each line. In addition, you can provide a complete overview (Floorplan) of the printing center. This is how you develop a drawing with Visio: A folder called Visio 2000 is installed together with the Device Manager. This folder contains the two files: BaseDraw.vsd CustomMenu.vsu The file BaseDraw.vsd is the template for your Visio drawing; the file CustomMenu.vsu is required for communication between Visio and the Device Manager. The first step in the design of a new Visio drawing is to open the file BaseDraw.vsd either directly in Visio or by double-clicking the file name in the Windows NT Explorer. You will then see the following window (depending upon the settings on your PC): 136 A29247-X68-X

143 Configuration The left panel shows the palette of shapes you can select to represent your devices. The right panel is the workspace for your drawing. The sheet header gives brief instructions on how to create the drawing. Proceed as follows: 1. Open the file BaseDraw.vsd. See the previous page for details on how to open this file. Once you have opened the file, the system will display the window shown above. 2. Create your drawing. You then have to group every device you have drawn, and call a macro for the grouped Visio drawing. 3. Group every device you have drawn. Select the device and choose Shape Grouping -> Group in the menu bar. You have to do this both for devices you have designed using several shapes and for devices designed with only one shape. The grouping is what enables the shapes to be edited by way of the Contextmenu macro (shortcut menu). A29247-X68-X

144 Configuration This macro provides you with a shortcut menu of the functions you can also access in the Device Manager. This macro is only available in the BaseDraw.vsd file. Starting from your Visio drawing, you can then perform actions such as requesting statistical information about a device, setting a device to service state, etc., in exactly the same way as you would in the Device Manager. 4. Run the "Kontextmenu" macro for each device. Select the device and then choose Tools Macros Modul1 CreateContextMenu in the menu bar. After completing all the steps up to this point, you can open the following shortcut menu for a device by clicking it with the right mouse button: The menu provides Device Manager commands and commands for working on the Visio drawing. The Visio view thus provides you with the same environment as in the Device Manager view, and you can execute all the commands in the usual manner. 138 A29247-X68-X

145 Configuration If the editing action failed (perhaps because you have forgotten to group a device), the shortcut menu will be Visio-specific, as shown below: If you see this menu, check that you have completed all the steps as described above. 5. Assign a name to each device you have drawn. Select the device and click the right mouse button. Choose Format Special (Object Data) from the shortcut menu. The system will display the following dialog box: Enter the name of the device. Bear in mind that this must be the same name as in the Device Manager. If the names are not the same, Visio and the PRISMAaudit database will not be able to exchange data. You can now enter this name on your Visio drawing. A29247-X68-X

146 Configuration 6. Complete your Visio drawing. Close the shape window and delete the instructions in the header of your worksheet. 7. Save your Visio drawing. You can now open the new Visio drawing in the Device Manager using the Explorer Visio view command. Note: Various entries have to be made in the registry to enable Visio drawings to be opened using the Device Manager. If this registry information is missing, the system issues a message to tell you so. See Chapter 3.10 "Visio Link", page A29247-X68-X

147 Configuration Program 9 Configuration Program Before users can work with the Device Manager, certain information has to be defined relating to the system structure, current parameter settings on computers and the properties of the Device Manager. Processing with the Device Manager can be controlled by parameters. We differentiate between two types of parameters: Parameters for the database connection and for diagnostic purposes, and Configuration parameters. The local configuration is carried out using the program DM Configure. This has a Graphical User Interface to simplify the entering, changing or deleting of parameters. The data is stored in the registry (see note on page 151). 9.1 Entering Parameters There is a configuration program for entering parameters. This is how you launch the configuration program: 1. Click the <Start> button (in the taskbar). 2. Select Program Files Océ PRISMAaudit Device Manager PRISMAaudit DM Configure or click the Configuration program icon in the PRISMAaudit toolbar. The system opens the following window: A29247-X68-X

148 Configuration Program You have to enter parameters for the following components: Converter Device Manager Client History Taker Device Manager Statistics You also use the configuration program to define database users and to choose whether to keep traces (logs). The entries for each computer are stored in the registry. The following table lists which entries have to be made for each of the computer systems. Computer Component Clients Process Computer Database X X Converter Device Manager Client History Taker Device Manager Statistics X X X DMI Converter Traces X X X 3. To launch a component, double-click its icon in the window. The components are described in detail in the following sections. X 142 A29247-X68-X

149 Configuration Program Database For the database, you have to enter the ODBC name, the user and a password. This is how you make the database entries: 1. In the Device Manager Configuration (Vn) window, double-click the Database icon. The system opens the following dialog box: 2. Fill out these fields: Field ODBC Data Source User Password Description ODBC Name under which the database was configured on the local system (Control Panel ODBC). User ID for the database. Password for the user ID of the database. 3. Click <OK>. The system confirms the values you have entered. A29247-X68-X

150 Configuration Program Converter For the converter, you have set the parameters shown in the dialog box below. The Device Manager - Converter dialog box contains two tabs: Devices Monitor Devices tab 144 A29247-X68-X

151 Configuration Program This is how you set the parameters for devices: 1. In the Device Manager Configuration (Vn) window, double-click the Converter icon. The system opens the dialog box shown above. 2. You can set the following parameters: Field Device Id Device Type Device Name Interface Description The device Id is a sequential number. In this version, numbers 1 through 16 are available. This Version works with the following device types: Océ V24 = Océ Printer with V.24 interface Océ Type II = Océ Printer with Type II interface (not yet implemented) Pitney Bowes = Pitney Bowes inserter Kern = Kern inserter Boewe = Böwe inserter ESP = ESP devices (unwinder, rewinder, cutter) Hunkeler PCS Hunkeler Device Bell+Howell IBM SNMP The name you enter here must be identical with the name defined for the device (see Chapter 7.2 "Installing a new Device", page 104). Reason: the History Taker loads the MIF file for a device into the local DMI-SP (Service Provider) using the name assigned in the Device Manager Explorer. Only if the names match can the converter connect to the DMI-SP and, in turn, with the History Taker. Note: The device name must be a valid file name, otherwise no trace file will be created. Observe the restrictions of your operating system on the use of special characters in file names! See also Chapter "Traces", page 155. This parameter is relevant only for the device types Océ V24 and Océ Type II relevant. Enter the COM port to which the printer will be connected. You can display the settings for the selected port by clicking <COMM> (see description at the end of the table). A29247-X68-X

152 Configuration Program Field File Description This button is not available for the other device types (i.e. it is disabled). This parameter is relevant only for the device types Pitney Bowes, Kern, Böwe and ESP. Enter the interface file for these device types. Important! You cannot change the path once you have specified it. If the file you enter does not yet exist, the following message box is displayed: Remember that you will not be able to change the path later. Respond to the system prompt accordingly. Notes for Kern device types: The name of the event log file for these devices is composed as follows: <Text><X><yyyymmdd><YZ>.<ext> Explanation: <Text> = Usually "Kern <X> = CenterID, machine group <yyyymmdd> = Time in format year, month, day <YZ> = Sequential numbering (per day) <ext> = Extension, usually "log You can enter an original file name, select an existing file name, or create a scheme of your own. However, your own scheme must contain the sections: <Text><CenterID>*.<ext> (observe the wildcard!) Example: "Kern1*.log" If you enter a name, the converter selects the requisite sections of the name itself. 146 A29247-X68-X

153 Configuration Program Field Device Index Line Module ID (IP) Adress CommunityName Description The device index is relevant only for Pitney-Bowes, Kern and ESP device types. It enables the selection of a particular device record from the interface file. Pitney-Bowes and ESP devices: Device index = Record/line number of the device in the file (0-based index) Kern devices: Device index = Inserter ID for selecting a particular event log in the event log file IBM SNMP: Device index is used for Dual Simplex (in the other case set it to "1"). The first printer of a Dual Simplex system has the device index "1" and the second printer has the index "2". For Hunkeler For Hunkeler For IBM SNMP. For IBM SNMP. # Counters For Böwe. # Components For Böwe. Pagetick Counter Status (min) Characteristics (min) HouseKeeping (h) This parameter is relevant only for the device types Océ V24 and Océ Type II. Enter the number of pages after which status polling should be repeated. This parameter is relevant only for the device types Océ V24 and Océ Type II. Enter the interval between operations to poll the printer status. This parameter is relevant only for the device types Océ V24 and Océ Type II and for IBM SNMP. Enter the interval between operations to poll the printer characteristics. This parameter is not evaluated in this version. It is relevant only for the device types Océ V24 and Océ Type II. Enter the interval between global status/characteristics updates. A29247-X68-X

154 Configuration Program Field Poll Cycle (sec) Controlling Active/Inactive Description This parameter is relevant only for the device types Pitney- Bowes, Kern, Böwe, ESP and IBM SNMP. Enter the interval at which the interface file should be polled. For IBM SNMP determine the polling interval of the status. You need this parameter if you want to be able to change the values of devices while they are active. The converter reads the registry entries only when it starts a device (apart from the "Activation" value the converter checks regularly whether the device is active). You can set an active device to inactive while the converter is running. The converter polls the registry entries at 10-second intervals and reacts to any changes. To inform the converter of changes while it is running, set the device to inactive. Make your changes to the device, and then set the device back to active state. This causes the converter to read the registry entries for this device again. Note: Observe the 10-second interval: this ensures the converter has a chance to recognise the inactive state before you set the device back to active. 148 A29247-X68-X

155 Configuration Program Field <COMM> Description This button is available only when you have selected Océ V24 or Océ Type II devices. When you click <COMM>, you are shown the following dialog box: <Datenbase> Port Use this dialog box to make the settings for the selected COM port. Note: The settings are preconfigured for the printer. They may only be changed after agreement with service personnel. For Bell+Howell 3. When you have entered or modified the parameters, click <Apply> in the Device Manager - Converter window. The system confirms the values you have entered. A29247-X68-X

156 Configuration Program Note: The values you have entered are only registered if you confirm them with <Apply> or <OK>. 4. Set the parameters for the monitoring. Click the Monitor tab. The system displays the following dialog box: 5. You can set the following parameters: Field V24-Timeout (sec) Description Use this parameter to set the interval at which the connection with the printer is to be polled. Since polling intervals for the printer can be in terms of minutes or hours, the interval you set here ensures that the connection with the printer is maintained in the interim. 150 A29247-X68-X

157 Configuration Program This is particularly important during idle periods when there are no page ticks (clicks) being logged. Type-II-Timeout (sec) File Timeout (min) Acknowledge Timeout (sek) Directory for Bufferfiles This parameter is not evaluated in this version. This parameter is relevant only for the device types Pitney- Bowes, Kern, Böwe and ESP. Enter the time that is to elapse before the interface file is declared invalid this happens if the Device Management Information System (MIS) does not make any changes to the file within the specified period of time. This parameter is particularly important with files and devices that do not log update counters or time specifications in the file or records. The parameter serves to monitor whether or not the MIS is in fact still serving the interface file. 6. When you have entered or modified the parameters, click <Apply>. The system confirms the values you have entered. 7. Click <OK> to exit the component. The system again displays the Device Manager Configuration (Vn). Note: All converter settings are stored in the registry under the general PRISMAaudit path HKEY_LOCAL_MACHINE/SOFTWARE/OPS/Oce PRISMAaudit, in the section: Device Manager/Converter/Monitor The values defined for the converter are read only when the DMI converter is launched. You can change values while the converter is running, but remember that the changes do not take effect until you restart the converter. A29247-X68-X

158 Configuration Program Device Manager Client You can set the parameters shown below: This is how you set the parameters: 1. In the Device Manager Configuration (Vn) window, double-click the icon for the Device Manager Client. The system opens the dialog box shown above. 2. You can set the following parameters: Field ODBC Repeat Counter ODBC Timeout VISIO File Description If there is a problem with the database connection, the system attempts to establish the connection again. In this field, enter the number of retries that are to be made. Your entry here depends on the timeout value you enter in the ODBC Timeout field. Enter a value in seconds. Enter the interval of time between the database connection being shut down due to a problem, and the first attempt to reconnect to the database (see also ODBC Repeat Counter field). To update Visiofile entry in the registry. 3. Click <OK> to exit the component. The system again displays the Device Manager Configuration (Vn). 152 A29247-X68-X

159 Configuration Program History Taker The History Taker collects information about the devices which are connected to the Device Manager. You can set these parameters for the History Taker: This is how you set the parameters: 1. In the Device Manager Configuration (Vn) window, double-click the icon for the History Taker. The system opens the dialog box shown above. 2. You can set the following parameters: Field DB Reconnect (Min) DB Time Synchronisation (hours) Description The connection to the database is shut down and reestablished at regular intervals in order to free resources that have not been released by the ODBC and to keep the database connection free of errors. Use this parameter to specify the interval of time between two consecutive reconnects. If the times for the database and operating system are different, the History Taker synchronises the times. Use this parameter to specify how often the times are to be A29247-X68-X

160 Configuration Program Field Daily Restart Yes/No Time (hh:mm) Housekeeping (Min) Description synchronised. Use this parameter to specify whether or not the History Taker is to be restarted every day. Consider that this state is recorded in the database, i.e. the connected devices have the state Unknown while the restart is in progress. You can, however, set a time for the restart to be performed (see next field), so you will be able to identify the restart action in the printer statistics. Enter the time of the daily restart of the History Taker. The History Taker receives information regularly from the DMI. When you enter a value here, the History Taker itself polls for information at the specified interval. 3. Click <OK> to exit the component. The system again displays the Device Manager Configuration (Vn) window Statistics You can set the parameters shown below: This is how you set the parameters: 1. In the Device Manager Configuration (Vn) window, double-click the Statistics icon. The system opens the dialog box shown above. 154 A29247-X68-X

161 Configuration Program 2. You can set the following parameters: Field ODBC Repeat Counter ODBC Timeout Description If there is a problem with the database connection, the system attempts to establish the connection again. In this field, enter the number of retries that are to be made. Your entry here depends on the timeout value you enter in the ODBC Timeout field. Enter a value in seconds. Enter the interval of time between the database connection being shut down due to a problem, and the first attempt to reconnect to the database (see also ODBC Repeat Counter field 3. Click <OK> to exit the component. The system again displays the Device Manager Configuration (Vn) window Traces The behaviour of the converter and History Taker components can be monitored by keeping traces. The information supplied by the trace files is helpful in identifying the cause of problems. To make settings for traces, click the Traces icon in the configuration program window. The system opens the following dialog box: A29247-X68-X

162 Configuration Program Note: Trace functionality is also planned for the PRISMAaudit Client, PRISMAaudit Statistics and PRISMAaudit Administrator components. You can select from the following trace levels: Error Trace = 1 Warning Trace = 2 Info Trace = 4 Process Trace = 8 The info trace logs non-critical events. The process trace logs detailed information and constitutes a debug mode. To keep multiple traces, simply add the values. Example: You want to run all the traces for the converter. In the Level field, enter "15" (Error + Warning + Info + Process -> ). You want to run the error, warning and info traces for the History Taker. To do this, enter "7" in the Level field ( ). This is how you configure the trace settings: 1. In the Device Manager Configuration (Vn) window, double-click the Traces icon. The system opens the dialog box shown on the previous page. 156 A29247-X68-X

163 Configuration Program 2. You can run traces for the converter and History Taker components. If the Level field is set to 0 (zero), no trace will be run. 3. Select either the User or Dev column. There are no differences between these two options in this version. In future versions, it is planned to log additional internal information for the developer. 4. Click <OK>. The system confirms the values you have entered and again displays the Device Manager Configuration (Vn) window. You have to state where you want to save the trace files. 1. Click the button next to the Trace Directory field. The system opens the following dialog box: 2. Select the path and click <OK>. The system creates the trace files in the path you have specified. The Device Manager Configuration (Vn) window is then displayed again. A29247-X68-X