Copyright (c) Fujitsu Siemens Computers
All rights reserved
Version date: January 2008
1
1.1
1.2
1.3
2
3
3.1
3.1.1
3.1.2
3.2
3.3
3.3.1
3.3.2
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.5
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
3.5.7
General
Ordering
Delivery
Documentation
Software extensions, new functions
Technical information
Resource requirements
Required disk storage
Virtual Memory consumption
Hardware requirements/support
Software configuration
Operating systems
Several Xprint Versions in one Domain
Product installation/configuration
General
Initial installation
Migration aspects when upgrading from former Xprint versions
SNMP
Domain Monitoring GUI Relay
Domain Monitoring GUI Server
Product use
Xprint License
Renaming the hostname in an Xprint domain
Bsd filter port options
Test of the printer device address
Device selection
Logging
xp_alert
3.5.8
3.5.9
3.5.10
3.5.11
3.5.12
3.5.13
3.5.14
3.5.15
3.5.16
3.5.17
3.5.18
3.5.19
3.5.20
3.5.21
3.6
3.7
3.8
3.8.1
3.8.2
3.8.3
3.8.4
3.8.5
3.8.6
3.8.7
3.8.8
3.8.9
3.8.10
3.8.11
3.8.12
3.8.13
3.8.14
3.8.15
3.8.16
3.9
4
Clean up of directories at the start up
Gateway options
Standard entries
Notification event
Requesting the job states with the APIs
Page context
Inter-domain notification
Goodies
Job id limit
Mercator Viewing
Options order
Cooperation with Wprint 4.0
Which PCL is recommended according to a printer
Interoperability with LDAP
Obsolete functions
Incompatibilities
Restrictions
Maintenance scope
Installation
The database
Xprint fax and mail support
Jobs sent to a remote domain
Interrupted job on a PJL printer
Wprint 4.0
SNMP
Mercator
Firewall
Dprint
Page selection for ASCII files on POSTSCRIPT
On Microsoft Windows
Domain Monitoring GUI (DMG) Server
Domain Monitoring GUI (DMG) Server Installation
Using the options -fc and -rw with PCL POSTSCRIPT
Procedure in the event of errors
Errata for documents and manuals
1 General
This file contains important information - not included in the manuals - on the use of Xprint and the
Domain Monitor GUI.
The navigation in this document is done by hyperlinks. The links in the table of contents will guide you to
the corresponding item. If you want to go back to the table of contents, click on the
The use of names or product designations, etc. in this information does not constitute a general
authorization to use such names or designations. In many cases they are legally or contractually
protected names or designations even if they are not marked as such.
Windows is registered trademark of the Microsoft Corporation. Windows Server is trademark of the
Microsoft Corporation.
section header.
1.1 Ordering
For the use of Xprint you will need software licenses. The data media has always to be ordered
separately.
This product is subject to the general terms and conditions of the software product use and service
agreement.
The delivery unit is a licensed product and may only be used on the computer for which it has been
purchased.
The basic local license contains 32 printers, special additional printer licenses have to be purchased.
If you want to work on a network basis you need at least two Server licences or one Server licence and
one Net-Client licence. The Server license includes the gateway and the administration. The graphical
interface Mercator is integrated into the basic local or network license. For further informations please
refer to
User's and Administrator's Guide (chapter 8.5) oder section 3.5.1 in this release notice.
With XPRINT V8 you have now the web-based graphical user interface DMG GUI.
In the Basic-/Net license of XPRINT two concurrent user windows are already included.
Further user windows you can purchase additionally.
Number of possible
printers
1.2 Delivery
Xprint for Windows (tm) is delivered as a component of the CD-ROM data volume called Xprint-NT-CD (U11436C176).
The following components are included in this Xprint distribution. (N.A stands for "not available"):
Xprint- NT
Basic Software X
Graphical Interface X
XPG/3 Emulation X
Message catalogues N.A
Compatibility Libraries N.A
Inter domain Interoperability X
Development Tool kit X
Manual Pages N.A
Xprint R/3 Kit X
SNMP Agent X
Domain Monitoring GUI Anchor X
Domain Monitoring GUI Relay X
Domain Monitoring GUI Server X
EKS/Patch XPW80B102X
●Xprint-NT means Xprint for Microsoft Windows Server
The activation of each component depends upon the purchased license. Please see section 3.1 for the specific
components of the Xprint distribution.
You will find the files for the DomainMonitoringGUI Open UNIX in the directory <cdrom>/DMG-8.0B10-03-OPENWin.
Current EKS:
In the directory XPW80B102 you will find the EKS XPW80B102 for Xprint (Windows). These correction packages
are meant for Xprint 8.0B10. This correction solves some problems in the licence mechanism. Please install it
befor you start Xprint.
1.3 Documentation
To install and operate Xprint you need the documentation.
2 Software extensions, new functions
Beside the below specific hints, the reader should also consult the sections prerequisite and installation included in the Xprint
8.0B Add-on manual.
New features Explanation
Diagnose file collection within
the DOMAIN MONITORING GUI
Support of active directory
information (through LDAP)
The purpose of the Diagnose File Collection is to allow the product operators to
centraly collect all the product log & debug files produced by the various product
processes within the product domain. This collection is performed from a web
interface that is part of the existing Domain Monitoring GUI Server. The collected
files are "viewable" and "downloadable" from the DFC. Moreover, the user may
decide to create an archive file (tar or zip) in order to send it to the support
departement.
The purpose of this feature is to demonstrate the ability of the product to interact
with an LDAP server. An LDAP server is a server process that works with the LDAP
protocol.
document
OpenLDAP server and Active directory will be referred further as LDAP Server in this
.
The example of interaction that has been designed in the version 8 of the product
consists in taking a default printer for any job submitted with no explicit
destination. The default printer is to be found in the user profile defined in the
LDAP configuration. If the job originator provided an explicit destination, the LDAP
interoperability will have no impact.
If there is no default printer defined in the LDAP configuration, the usual product
processing will take place at the job submission.
DMG view/filter management
tool
Accounting file enhancement The accounting has been enriched with new fields to give the administrator
Interface Windows - Linux /
UNIX using SMB protocol
Support of Accelio JetForm (Accelio) is a tool that enables the formatting of documents to be printed.
Dedicated File Server inside an
Xprint domain
Event notification FILE method
with timestamp
Custom header- trailer pages Customers need to print header, trailer pages containing specific information
DMG Application for open Web
server environment
The purpose of this feature is to facilitate system administrators to distribute
existing DMG filters and DMG views to other DMG operators.
possibilities to produce more accurate accounting reports.
The purpose of this feature is to demonstrate how to share a product device to
windows clients via Samba. The device resource is only defined on the samba
server and the printer driver must be shared too.
The windows clients must be able to use those printers without any extra
installation/configuration tasks.
As a pre-requisite, samba should already be up and running within the user
environment.
It takes as input a plain ASCII document and produces as output a PostScript , PCL
or PDF documents.
The support of Accelio inside this product is performed by means of a specific slow
filter creation.
The goal of this feature is to offer the possiblity to define in the product domain
one or several dedicated server where the input job data file will be stored and
where the slow filter program will be installed and executed.
When a user requires notifications (job, device) via the FILE method, the
timestamp is never put in the event message. The goal of this feature is to provide
this time information in the event file.
according to a specific layout (big characters, special logo, etc.). This feature offers
this possibility.
The DMG Web application can be integrated within an existing Apache/PHP5/SSL
Web server environment. Note that the DMG application formerly delivered as an
integrated “black box” package remains available for unattended installation in an
intranet environment.
The scope of this feature is restricted to the samba/Product interaction.
Xprint 8.0B10:
Device creationAutomatic creation of Servers and Supervisors (see 3.7)
SNMPNo automatic activation ot the SNMP component (see 3.7)
Xprint 8.0B10 introduces no new major functional changes. The only major
other changes
changes between Xprint 8.0B00 and Xprint 8.0B10 are the bug fix
corrections.
3 Technical information
3.1 Resource requirements
The required disk storage capacity depends directly on how the software is packaged and installed. Currently,
Xprint is packaged in three different ways according to the platform. These values have been measured before the DB
initialisation.
3.1.1 Required disk storage
The required disk storage capacity directly depends on how the software is installed. Xprint is distributed as a setup package
containing the entire product. During the wizard execution, three kinds of installations are proposed:
- Typical: represents the installation of the Basic Software, the Inter domain and the XPG/3 emulation components.
- Compact: gathers the installation of the Basic Software and the Inter domain components.
- Custom: this installation type allows a free choice between the available components.
The following table illustrates the amount of space required, once installed on the disk (prior to database initialization):
KB
Basic Software 10312
Inter domain 692
XPG/3 Emulation 88
Development Tool Kit 348
Xprint R/3 Client 648
Xprint R/3 Server 200
SNMP agent 304
Domain Monitoring GUI Anchor 200
12792
Important:
In addition to these given sizes, the total free disk space needed is 35 MB for the complete installation of all components. The
reason is the space needed by the MKS runtime and the installation files.
Moreover, space must be added to these initial figures for the storage of print data, temporary files and configuration files
(database), which may vary widely according to the configuration and the usage model. 20 MB for these files is a minimum.
3.1.2 Virtual Memory consumption
The following table shows the approximate consumption of the Xprint processes in Kb. (in task manager)
Entity
Standby 12120
Server 7076
Supervisor 2856
Printing 6556
Gateway 9112
R/3 Kit Server 12712
SNMP Agent 6472
Memory usage size
(KBytes)
The Standby size is required as soon as Xprint is active. The server and supervisor sizes must be multiplied by the actual
number of active servers and supervisors defined on the system.
The printing size is required by each job, during the time it is actually being printed.
Be careful to configure a sufficient virtual swap memory on the Windows system.
The product could become unstable if there is a low virtual memory message.
3.2 Hardware requirements / support
Please refer to the chapter 7.1 of the reference manual for information about supported printers.
3.3 Software configuration
3.3.1 Operating system
Before installing Xprint, be sure that all previous EKS (Xprint correction packages) are removed from the system.
This product is dedicated to Microsoft Windows 2003 Server (tm) and to Microsoft Windows 2000 Server (tm) with
service pack >= 2. It is not allowed to run the server part of the product on a machine with more than 2 processors maximum.
You may not install this product on Microsoft Windows XP or Microsoft Windows 2000 Professional versions due to the built-in
limitations of these platforms. Some severe instabilities can occur in this product if you have installed it on Windows XP or
Windows 2000 Professional systems. This product is only supported and maintained on Microsoft Windows Servers.
Xprint is based on the runtimes of MKS Platform Components 4.3 from Mortice Kern Systems. These runtimes and the
corresponding service are automatically installed and configured during the Xprint setup.
The MKS Platform Components product is not a part of the Xprint product.
On Windows 2003 and Windows 2000 server, the SNMP agent requires the Microsoft SNMP service.
3.3.2 Several Xprint Versions in one Domain
Xprint 8.0 can only run in a domain with Xprint 5.2 or later.
An EKS has to be installed on each host running a former Xprint version (<6.0A) and where a PJL device
(HP printer supporting the PJL language) is configured (in other words the supervisor of this device runs
on the host). The
EKS names are listed in a table, which you will find in chapter 3.7.
3.4 Product installation/configuration
3.4.1 General
An introduction to installation and instructions is provided in chapter 9 of the Xprint 8.0 User's and
Administrator's Guide.
To simplify matters use also the Appendix information and worksheets in
3.4.2 Installation
3.4.2.1 Installation
The Xprint installation automatically updates the Windows services file (real name is %SystemRoot%
\system32\drivers\etc\services) in order to create the Xprint_db entry. The port number is requested
during the setup wizard execution.
Xprint must be installed on a local hard drive. The network shared drives are not supported.
chapter 10.
Be careful that temporary files will be stored in the selected installation path.
Indeed, the files to be printed are temporary stored in some installation subdirectories.
It is also recommended for performance improvement to install Wprint on the same drive as Xprint.
If you did choose to install the SNMP agent, please make sure that the SNMP service is installed on the
host.
3.4.2.2 Domain with older Xprint versions
If you install Xprint V8.0 in a domain containing hosts running older Xprint versions, be sure that only
hosts running the latest version are defined as POT_MASTER. To avoid problems, define the hosts
running older versions as SLAVE. When installing the first Xprint V8.0 host (H1) in a lower version
domain, H1 will have to take the mastery of the domain. So, after having imported the DB (through
DBinstall), you will have to start Xprint using the control panel - services and setting the startup
parameters to '-fv' (fv means 'force version') in order to allow it to take the mastery from an older
version.
3.4.2.3 Integration with Wprint
The Wprint 4.x product is the Windows integrated client for Xprint. This product provides a very easy way
to print from the Windows applications to your favourite Xprint printers and also a powerful management
of your print jobs submitted to Xprint. This is the major reason why Wprint 4.x is delivered on the same
media as Xprint for Windows.
Just remind that for better performance, it is adviced to install Wprint and Xprint on the same drive.
Concerning the integration for the Wprint configuration, the reader is referred to the Graphical interface
for administration (Mercator) guide and the description of this specific Windows functionality. If the
Wprint is installed on a Xprint Windows system, it is recommended to use the local gateway as entry
point in Xprint.
3.4.2.4 Database backup
During an update installation a backup of the current DB is stored in the (default) C:\WINDOWS\Program
files\Xprint\DB\DB.backup directory.
On all platforms, the backup of the current DB will be restored automatically at the end of the installation
process.
In case of problems during DB recovery, the DB can be restored manually after the installation. Just copy
the (default:) C:\WINDOWS\Program files\Xprint\DB\DB.backup to C:\WINDOWS\Program files\Xprint
\DB. In all cases, do not forget the objects defined by the Xprint administrator (filters, PCLs, recovery
rules, ...) requiring a file at the definition or at the usage: if these files are located in the Xprint tree,
they will be lost during the update installation.
It is also possible to do this with the command xpdbls. This script shows your Xprint configuration. You
must redirect the output to a file.
At the end of the first installation, two GIP2 gateways are created (a LOCAL and a PARTNER one) to allow the
access from a Wprint 4.x client.
Activation
Please refer to the FAQ.
Maximum number of partner gateways in Xprint
Please refer to the
FAQ. (unlimited from Xprint)
3.4.2.6 How to configure an Xprint domain
Please refer to the FAQ.
3.4.2.7 How must the Xprint Pot-Masters be rebooted
Please refer to the FAQ.
3.4.2.8 Local Xprint administrator
This kind of user is called a "subroot" user by Xprint.
You can declare subroot users on a host when you create this host, or by modifying an existent host,
with the " -sr" option.
For instance, if you want that the user "usname" becomes subroot on host "OSL" you can type
"xpmod -hos OSL -sr usname".
3.4.2.9 Maximum number of devices per supervisor / servers objects
The old settings are described in chapter 5.4.3 in the XPRINT User's and Administrator's Guide.
For Xprint 8.0B10 are new default settings introduced.
These defaults settings can be changed by means of 2 environment variables:
1.XP_SPV_BY_DFTSRV
.
Description:maximum number of supervisors by default server
Initialisation time:before xpadd -dev
Possible values:from 1 to 20
Behaviour if unspecified:20 is used
Behaviour if a value larger than
20 is specified
2. XP_DEV_BY_DFTSPV
.
Description:maximum number of device by default superviso
Initialisation time:before xpadd -dev
Possible values:from 1 to 50
Behaviour if unspecified:50 is used
Behaviour if a value larger than
50 is specified
20 is used
50 is used
However, it is not recommended to associate more than 30 printers to a single supervisor, and more than 15
supervisors to a single server. The quantity of objects is also related to their usage model.
For example, you will not associate so many production devices to a supervisor than desktop printers.
3.4.2.10 Installation of additional components of Xprint
Xprint components
Basic Software X
Graphical Interface X
XPG3 Emulation
Standard
Installation
Loading...
+ 19 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.