HPOS SP12.1 Install and Config Guide Hpos41sp121incenUS

HP Output Server 4.1.0.
3
Service Pack 12.1
Installation and Configuration Guide
1991-2012 Hewlett-Packard Development Company, L.P.

Reproduction, adaptation or translation without prior written permission is prohibited, except as allowed under
the copyright laws.
Refer to the license.txt file shipped with the software for comprehensive third-party copyright information.
April 2012 Edition for HP Output Server
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent
with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and
Technical Data for Commercial Items are licensed to the U.S. Government under vendors standard
commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and
services are set forth in the express warranty statements accompanying such products and services. Nothing
herein should be construed as constituting an additional warranty. HP shall not be liable for technical or
editorial errors or omissions contained within.
Software Warranty. The specific warranty terms applicable to your Hewlett-Packard software can be found
in your software license.
Restricted Rights Legend. All rights are reserved. No part of this document may be photocopied, reproduced,
or translated to another language without the prior written consent of Hewlett-Packard Company. The
information contained in this document is subject to change without notice.
Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)
(1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD
agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause
at FAR 52.227-19 for other agencies.
Use of this manual and flexible disk(s), tape cartridge(s), CD-ROM(s), or DVD(s) supplied for this pack is
restricted to this product only. Additional copies of the programs may be made for security and back-up
purposes only. Resale of the programs in their present form or with alterations, is expressly prohibited.
Software Copyright Notices
Copyright 1991-2012 Hewlett-Packard Development Company, L.P.
Portions Copyrighted By
Copyright 2000-2005 MySQL AB & MySQL Finland AB & TCX DataKonsult AB.
Copyright 1996 Carnegie Mellon University.
Copyright 1987-2003 Larry Wall. Perl is distributed without warranty or the implied warranty of
merchantability or fitness for a particular purpose. See either the GNU General Public License or the Artistic
License for more details. For the copyright notice and full text of the General Public License, contact
Customer Support.
Perl is Copyright (C) 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006,
2007, 2008 by Larry Wall and others. All rights reserved.
Copyright 1990 Massachusetts Institute of Technology. Permission to use, copy, modify, and distribute
M.I.T. software and its documentation for any purpose and without fee is hereby granted, provided that the
above copyright notice and this permission appear in all copies and that both that copyright notice and this
permission notice appear in supporting documentation, and that the name of M.I.T. not be used in supporting
advertising or publicity pertaining to the distribution of the software without specific written prior permission.
M.I.T. makes no representations about the suitability of this software for any purpose. It is provided as is
without express or implied warranty.
Copyright 2001-2002 Robin Berjon.
Copyright 1998-2000 Larry Wall and Clark Cooper.
Copyright 2001 Matt Sergeant.
Copyright 1999-2003 Grant McLean.
Copyright 1999 Megginson Technologies.
Copyright 2000 AxKit.com.
Copyright 1990, 1991, 1992, 1993 Michael Sample and the University of British Columbia.
Copyright 1994, 1995 Robert Joop and GMD FOKUS.
GNU Lesser General Public License Version 2.1, February 1999.
Copyright 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
Copyright 1993 - 2005 SAP AG, Walldorf.
Copyright 1993 - 2009 Easysoft Limited. All rights reserved.
Copyright 1988-1997 Sam Leffler.
Copyright 1991-1997 Silicon Graphics, Inc.
Trademark Notices
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
PostScript is a trademark of Adobe Systems Incorporated.
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
UNIX is a registered trademark of The Open Group.
JBoss is a registered trademark of Red Hat Middleware LLC.
Hewlett-Packard Limited Warranty Statement
HP Product
HPOM Software
Period of Limited Warranty
90 Days
A. Extent of Limited Warranty
1. Hewlett-Packard ("HP") warrants to the customer ("Customer") that the HP software product specified
above ("Product") shall execute its programming instructions for the period specified above. The warranty
period begins on the date of purchase by Customer.
2. HP does not warrant that the operation of the Product shall be uninterrupted or error free.
3. HP's limited warranty covers only those defects which arise as a result of normal use of the Product, and
does not cover any other problems, including those which arise as a result of:
a. Improper use, maintenance, or modification;
b. Software, media, accessories, or supplies not provided or supported by HP;
c. Operation outside a Product's specifications; or,
d. Improper site preparation or maintenance.
4. If HP receives, during the applicable warranty period, notice of a defect in any Product, HP shall at its
option either fix or replace the defective Product.
5. If HP cannot fix or replace the defective Product that is covered by HP's limited warranty, HP shall, within a
reasonable time after being notified of the defect, refund the purchase price for the Product.
6. HP shall have no obligation to issue a refund until Customer returns the defective Product to HP.
7. HP's limited warranty for the Product is valid in any country/region or locality where HP has a support
presence for the Product and has marketed the Product. The level of warranty service may vary according to
local standards. HP shall not alter form, fit or function of the Product to make it operate in a country/region for
which it was never intended to function for legal or regulatory reasons.
B. Limitations of Warranty
1. TO THE EXTENT ALLOWED BY LOCAL LAW, NEITHER HP NOR ITS THIRD PARTY SUPPLIERS
MAKE ANY OTHER WARRANTY OR CONDITION OF ANY KIND, WHETHER EXPRESS OR
IMPLIED, WITH RESPECT TO THE PRODUCT, AND SPECIFICALLY DISCLAIM THE IMPLIED
WARRANTIES OR CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, AND
FITNESS FOR A PARTICULAR PURPOSE.
C. Limitations of Liability
1. To the extent allowed by local law, the remedies provided in this Limited Warranty Statement ("LWS") are
Customer's sole and exclusive remedies.
2. TO THE EXTENT ALLOWED BY LOCAL LAW, EXCEPT FOR THE OBLIGATIONS SET FORTH IN
THIS LWS, IN NO EVENT SHALL HP OR ITS THIRD PARTY SUPPLIERS BE LIABLE FOR DIRECT,
INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER BASED ON
CONTRACT, TORT, OR ANY OTHER LEGAL THEORY AND WHETHER ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
D. Local Law
1. This LWS gives Customer specific legal rights. Customer may also have other rights that vary from state to
state in the United States, from province to province in Canada, and from country/region to country/region
elsewhere in the world.
2. To the extent this LWS is inconsistent with local law, this LWS shall be deemed modified to be consistent
with local law. Under local law, certain disclaimers and limitations of this LWS may not apply to Customer.
For example, the federal government of the United States, some states in the United States, and some
governments outside the United States (including provinces in Canada) may:
a. Grant Customer additional warranty rights;
b. Preclude the disclaimers and limitations in this LWS from limiting the statutory rights of a consumer (e.g.
the United Kingdom);
c. Otherwise restrict the ability of a manufacturer to enforce such disclaimers or limitations;
d. Specify the duration of implied warranties that the manufacturer cannot disclaim; or,
e. Disallow limitations on the duration of implied warranties.
3. For consumer transactions in the United States, any implied warranties imposed by law are limited in
duration to the express warranty period.
4. FOR CONSUMER TRANSACTIONS IN AUSTRALIA AND NEW ZEALAND, THE TERMS IN THIS
LWS, EXCEPT TO THE EXTENT LAWFULLY PERMITTED, DO NOT EXCLUDE, RESTRICT, OR
MODIFY, AND ARE IN ADDITION TO, THE MANDATORY STATUTORY RIGHTS APPLICABLE TO
THE SALE OF A PRODUCT TO SUCH CUSTOMERS.
Printed in the U.S.A.
Contents
Preface ...............................................................................xvii
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Text variables used in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Accessing the Software Support Online Web site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Creating an HP Passport account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Linking your Support Agreement Identifiers to your HP Passport account . . . . . . . . . . . . . . . . . . . . . . xxi
Downloading software updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Downloading software patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Downloading product documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Submitting a support case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Searching support documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Signing up for software update notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Before you call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
Planning the installation ................................................1
Contents of the HP Output Server package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

HP Output Server Version 4.1, Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
HP Output Server Version 4.1 documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
HP Output Server
vii
System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
System requirements for HP Output Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
System requirements for HP Output Server Manager and
HP Job Manager for Output Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Client browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Kernel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Interoperability with HP Output Management applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Supported SAP installations with HP Output Manager for SAP, Version 4.1. . . . . . . . . . . . . . . . . . . . . . 25
Supported HP Output Server configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Installation and configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Pre-installation checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Setting permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Planning an installation on a network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Device requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Obtaining the GPL source code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
30
31
32
Installing HP Output Server .........................................33
Installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Assumptions and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
File structure and behavior changes in
HP Output Server 4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Installing HP Output Server on UNIX hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Before you install HP Output Server on UNIX hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before you install HP Output Server with Oracle on a UNIX host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for using Oracle as a backend database server on a UNIX host . . . . . . . . . . . . . . . . . . . . .
Installing and configuring HP Output Server on a UNIX host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
41
42
45
Performing an HP Output Server standard installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing and configuring only the HP Output Server binaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing and configuring only the HP Output Server instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing a client-only installation (UNIX host only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
65
69
72
viii
Installing HP Output Server on Windows hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Before you install HP Output Server on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Before you install HP Output Server with Oracle on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Prerequisites for using Oracle as a backend database server on a Windows host . . . . . . . . . . . . . . . . . . . 78
HP Output Server server installation options on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Installing and configuring HP Output Server on a Windows host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Completing the installation of HP Output Manager for SAP 4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Completing the installation of HP Output Distributor 4.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Destination and permissions templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Uploading templates manually after creating a new domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configuring HP Output Distributor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Uninstalling HP Output Server ..................................101
Uninstalling HP Output Server from a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Uninstalling an HP Output Server standard installation from a UNIX host . . . . . . . . . . . . . . . . . . . . . . 102
Uninstalling only the HP Output Server binaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Uninstalling only the HP Output Server instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Uninstalling HP Output Server from a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Migration......................................................................109
Migration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

What is and what is not migrated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Assumptions and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
HP Output Server 3.5 and 4.0 migration prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Migrating a multi-host domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Migration effects on HP Output Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Migration effects on HP Output Manager for SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Migration effects on HP Output Distributor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Migration scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
hpos_dump.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
hpos_load.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Migrating HP Output Server on a UNIX host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Migrating an HP Output Server server installation on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
HP Output Server
ix
Migrating HP Output Server on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Restoring backup template customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Troubleshooting a failed migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Recovering from a failed HP Output Server migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Installing and removing patches ...............................131
Join a domain patch installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Installing a patch on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Installing a patch on an HP Output Server standard installation on a UNIX host. . . . . . . . . . . . . . . . . .
Installing a patch on an HP Output Server binaries installation on a UNIX host . . . . . . . . . . . . . . . . . .
Installing a patch on an HP Output Server instance installation on a UNIX host . . . . . . . . . . . . . . . . . .
Removing a patch from a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
132
135
138
139
Removing a patch from an HP Output Server standard installation on a UNIX host . . . . . . . . . . . . . . .

Removing a patch from an HP Output Server binaries installation on a UNIX host . . . . . . . . . . . . . . .
Removing a patch from an HP Output Server instance installation on a UNIX host . . . . . . . . . . . . . . .
Installing a patch on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
139
142
144
145
Removing a patch from a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Configuring HP Output Server...................................149
Setting environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Post-installation prerequisites for HP-UX operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Configuring HP Output Server servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Configuring user authentication and authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Setting the authentication mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Modifying user and group permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Configuring interdomain delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Configuring the LPR Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Creating a delivery pathway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a logical destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a physical destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Testing the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
157
158
158
159
Changing log level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Switching the HP Output Server binaries used by an HP Output Server instance . . . . . . . . . . . . . . . . . . . . . 161
Backing up and restoring HP Output Server............163
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Backing up HP Output Server and MySQL on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Task 1: Backing up program and configuration files (UNIX host) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Task 2: Backing up HP Output Server MySQL database (UNIX host). . . . . . . . . . . . . . . . . . . . . . . . . . 167
Restoring HP Output Server and MySQL on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Task 1: Re-creating the HP Output Server MySQL database (UNIX host). . . . . . . . . . . . . . . . . . . . . . . 169
Task 2: Restoring program and configuration files (UNIX host) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Backing up HP Output Server and MySQL on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Task 1: Backing up program and configuration files (Windows host) . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Task 2: Backing up HP Output Server MySQL database (Windows host) . . . . . . . . . . . . . . . . . . . . . . . 173
Restoring HP Output Server and MySQL on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Task 1: Re-creating the HP Output Server MySQL database (Windows host) . . . . . . . . . . . . . . . . . . . . 175
Task 2: Restoring program and configuration files (Windows host) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Backing up and restoring same-directory installations (UNIX only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Backing up same-directory installations (UNIX only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Restoring same-directory installations (UNIX only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Backing up and restoring HP Output Server and Oracle database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Backing up program and configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Restoring program and configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Backing up and restoring Oracle database server tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Backing up HP Output Distributor Oracle database server tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Using setup.pl in non-interactive mode....................185
Sample syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Creating a server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Creating a client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Using help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
server.ini parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
client.ini parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
HP Output Server
xi
Environment variables in HP Output Server ............193
UNIX environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Windows environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Setting environment variables in HP Output Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Configuring the database connection

on UNIX hosts .............................................................203
HP Output Server and the database on the same host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

HP Output Server and the database on separate hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Firewall support ..........................................................209
Implementing firewall support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
HP Output Server in a multi-NIC environment .........213
Configuring multiple instances of HP Output Server to use the same network interface . . . . . . . . . . . . . . . 214
Changing the host name throughout the configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Configuring multiple LPR Gateway servers in a multiple NIC environment (UNIX only). . . . . . . . . . . . . . 216
Hot backup ..................................................................217
HP Output Distributor configod.pl script..................223
Using help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Installing templates and configuring the CM and PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Removing templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
xii
Prerequisites for installing HP Output Server

with Oracle ..................................................................225
Creating an Oracle user for HP Output Server and granting privileges. . . . . . . . . . . . . . . . . . . . . . . . . . 225
Creating the tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Configuring Oracle parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Downloading Oracle 10g and 11g Instant Client libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Installing Easysoft ODBC-Oracle Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Tuning Oracle parameters .........................................239
Limited access to directories and files.....................243
Installing OpenSSL .....................................................245

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Configuring and administering

HP Web Console Job Manager ..................................247
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Domain groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Managing HP Output Server domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Adding domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Listing domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Editing domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Deleting domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Trusted authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Enforced authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Login session time-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
HP Output Server
xiii
Managing authentication methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Adding authentication methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Listing authentication methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing authentication methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting authentication methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting or modifying the login session time-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
256
259
259
260
260
M Configuring MySQL for HP Output Management.....263

Granting access for HP Output Management products on remote hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Adjusting variables for MySQL for HP Output Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Concurrent connections to MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
connect_timeout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
max_connections and the max_thread_proc kernel parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
thread_cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
innodb_max_purge_lag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
max_allowed_packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
wait_timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tuning MySQL for HP Output Server........................271

Prerequisites for tuning MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tuning the MySQL for HP Output Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tasks performed by the tunemysql_hpos.pl script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tasks performed by the tunemysql_hpos.pl script with de-fragmentation of databases . . . . . . . . . . . . .
Tuning MySQL parameters for 256 MB, 512 MB, 1 GB and 1.5 GB memory usage for buffer pool . .
xiv
266
267
267
268
268
269
269
271
274
278
279
280
Using HP Output Server data for

determining the type of memory usage....................281
MySQL tunable parameters .......................................283
Using patch.pl in non-interactive mode....................289
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Installing a Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Backing out of a Service Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Using help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Installing HP Output Server Manager .......................293
Installing HP Output Server Manager in interactive mode on Windows hosts . . . . . . . . . . . . . . . . . . . . . . . 293

Installing HP Output Server Manager in non-interactive mode on Windows hosts . . . . . . . . . . . . . . . . . . . . 294
Uninstalling HP Output Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Upgrading HP Output Server Manager in interactive mode on Windows hosts . . . . . . . . . . . . . . . . . . . . . . 296
Installing HP Job Manager for

Output Server Software..............................................297
Installing HP Job Manager for Output Server Software in interactive mode on Windows hosts. . . . . . . . . . 297
Installing HP Job Manager for Output Server Software in non-interactive mode on Windows hosts . . . . . . 299
Uninstalling HP Job Manager for Output Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Upgrading HP Job Manager for Output Server Software in interactive mode on Windows hosts. . . . . . . . . 303
HP Output Server
xv
Setting MySQL startup time.......................................305
Tuning the JBoss application server ........................307

Setting startup time for the JBoss application server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing JBoss Web Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling JMX Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure for tuning the JBoss application server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
307
308
308
309
Changing configuration settings in the

my.cnf file ....................................................................313
W Executing the pdconfig command from an

HP Output Server client installation..........................315
Index ...................................................................................319
xvi
Preface
This manual provides the information you need to install HP Output Server, HP Output
Manager for SAP, and HP Output Distributor. When you perform a server installation
of HP Output Server, the software for HP Output Manager for SAP and HP Output
Distributor is installed automatically.
NOTE: You must purchase separate licenses for HP Output Manager
for SAP and HP Output Distributor to use these products and
to receive documentation that describe how to use them.
This manual is intended for HP Output Server system administrators and assumes that
you have a working knowledge of the UNIX operating system, Windows operating
system, or both, depending on your computing environment.
Related documentation
The HP Output Server documentation library includes the following items:
HP Output Server
The Installation and Configuration Guide for HP Output Server, which describes
system requirements and planning, and explains how to install and configure HP
Output Server.
The System Administrators Guide for HP Output Server, which explains how to
perform administrative tasks with the HP Output Server command-line interface
(CLI) and, where applicable, provides a reference to its graphical user interface
(GUI) counterpart.
xvii
Typographic conventions
The System Administrators Command Reference and System Administrators

Attribute Reference for HP Output Server, which provide detailed information
about the HP Output Server CLI commands and attributes, respectively.
The Release Notes for HP Output Server, which provides important information
that was not included in the manuals, including specific requirements for each
supported platform, information about specific hardware and software that you may
want to use with HP Output Server, and product limitations.
You can access and download these documents in PDF format from the following Web
site:
http://www.hp.com/go/hpsoftwaresupport
For more details about downloading the product manuals, refer to Downloading
product documentation on page xxiii.
For more information about HP Output Management products, including HP Output
Server, visit:
http://hp.com/go/outputmanagement
Typographic conventions
HP product documentation follows the typographic conventions described in this table.
Each convention includes an example of usage.
Convention
Meaning
Examples
bold
Used to denote new terms and to

indicate user interface elements
such as menu names, command
names, icon names, dialog box
titles, field names, dialog box
options, and button names.
Each of these objects has

attributes that define, control,
and report its characteristics.
Used for emphasis, book titles, user

input variables, and command
syntax variables.
Install the program in the

installDir directory.
Denotes acronyms, device names,

logical operators, environment
variables, and registry entries.
DZL_HOME
HKEY_CLASSES_ROOT
italic
UPPERCASE
xviii
Click the Modify button.
Refer to the System

Administrators Command
Reference.
Accessing the Software Support Online Web site
Convention
Meaning
Examples
monospace
Represents text, commands,

attributes, and code examples that
constitute user input or computer
output.
Also includes file names, file name
extensions, and directory names.
pdls -c server ids_ccm:
Shows a selection from a menu in a

user interface.
Select File>Save.
>
Type y to confirm the selection.

Delete the example.txt
document when you have
completed the exercise.
(Instructs you to select the Save

command from the File menu.)
Text variables used in this document

The following text variables are used in this document:
Variable
Description
installDir
The installDir variable refers to the installation directory of an HP Output

Server standard installation. An HP Output Server standard installation is
one in which the HP Output Server binaries and instance are installed at
the same location.
For a standard installation, the installDir, installBinDir, and installInstDir
variables refer to the same directory location and may be used
interchangeably.
installBinDir
The installBinDir variable refers to the installation directory of the HP

Output Server binaries of an HP Output Server split installation. A split
installation is one in which the HP Output Server binaries and instance are
installed at different locations.
installInstDir
The installInstDir variable refers to the installation directory of the HP

Output Server instance of an HP Output Server split installation.

HP Software Support Online (SSO) is a fast and efficient way to access interactive
technical support tools needed to manage your business. You can download the latest
software, documentation, and updates for your products from the SSO Web site at:
To access the Software Support Online Web site, you must do the following:
1.
HP Output Server
Create an HP Passport account.
xix
2.
Link your Support Agreements ID (SAID) to your HP Passport account.
After you create an HP Passport account and link your SAID to your account, you can
access and use the SSO Web site and do the following:
Download software updates.
Download software patches.
Download product manuals.
Submit a support case.
Search support documents.
Sign up for notifications of software updates.
The following sections describe the detailed procedures that you must perform to access
the tools on the SSO Web site.
Creating an HP Passport account

An HP Passport account helps you access the tools on the SSO Web site. If you have
ever submitted a support case online, then you are already registered and have an active
HP Passport account (login and password). If you are a new customer or if you have not
submitted a case line in the past, you must create an HP Passport account. To create an
HP Passport account, perform the following steps:
1.
Go to the SSO Web site at

http://www.hp.com/go/hpsoftwaresupport.
2.
Click the Register link at the top of the page.
3.
Enter the required information listed in the form.

NOTE: Remember your user ID and password. You will need these
details to login when you access the SSO Web site.
NOTE: For questions about HP Passport, refer to the frequently
asked questions at
http://h20229.www2.hp.com/news/passport_
faq.html
xx
Linking your Support Agreement Identifiers to your HP Passport

account
After you create an HP Passport account, you must link your support contracts to your
HP Passport account. To link your Support Agreement Identifiers (SAIDs) to your HP
Passport account, perform the following steps:
1.

2.
Click Check Entitlement in the Short-cuts section.
3.
Log in using your HP Passport account credentials.
4.
Click Edit your profile at the top of the page.
5.
Select Edit System Handle / Service Agreement Identifiers (SAID).
6.
Enter your support contract's SAID in the field, and then click Add.
7.
Repeat steps 5 and 6 to link more SAIDs to your HP Passport account.
To review all support contracts linked to your HP Passport account, click List
Contracts on the left navigation pane.
Downloading software updates

You can download the latest version of your software from the SSO Web site. To
download the latest version of your software, perform the following procedure:
1.

2.
Click the Downloads tab.
3.
Click the Software Updates link.
4.
Click the My Updates link.
5.
If the system prompts you to log in, log in using your HP Passport account
credentials.
NOTE: If you have not associated any SAIDs with your HP Passport
account, perform the procedure in Linking your Support
Agreement Identifiers to your HP Passport account
on page xxi before you proceed.
6.
HP Output Server
To locate the available software updates, do one of the following:
xxi
Select Select an SAID, and then select the required SAID from the list.
Select Directly enter an SAID, and then enter an SAID in the text box.
7.
Select the Yes, I accept these terms and conditions box, and then click Submit.
8.
Select the product from the Show a single category / product center list, and then
click Get software updates.
NOTE: You can also expand the product center to view all the
products available for the specified SAID.
9.
Click the Get Software link for the selected product.
10. Select the required product from the 1.Product name list.
11. Select the file to download from 2.Electronic media list.
12. Download the software update by using any one of the following options:
-
Download Directly.
Use HP Download Manager.
Add to your shopping cart.
Downloading software patches

You can download the software patches for your product from the SSO Web site. To
download the software patches, perform the following procedure:
1.

2.
3.
4.
Click the Software Patches link.
5.
Select the product, version, operating system, and sub-product.

You can also enter key words to narrow your search.
xxii
6.
Click Search to view the search results.
7.
After you have identified the required patch, click the Download Patch link.
Downloading product documentation

You can download the latest documentation for your product from the SSO Web site. To
download the product documentation, perform the following procedure:
1.

2.
3.
Click the Software Updates link.
4.
Click the My Updates link.
5.
If the system prompts you to log in, log in using your HP Passport account
credentials.
NOTE: If you have not associated any SAIDs with your HP Passport
account, perform the procedure in Linking your Support
Agreement Identifiers to your HP Passport account
on page xxi before you proceed.
6.
To locate the available product documentation, do one of the following:

-
Select Select an SAID, and then select the required SAID from the list.
Select Directly enter an SAID, and then enter an SAID in the text box.
7.
Select the Yes, I accept these terms and conditions box, and then click Submit.
8.
Select the product from the Show a single category / product center list, and then
click Get software updates.
NOTE: You can also expand the product center to view all the
products available for the specified SAID.
9.
Click the Get Documentation link for the selected product.
10. Select the required product from the 1.Product name list.
11. Select the file to download from 2.Documents list.
12. Download the product documentation by using any one of the following options:
HP Output Server
Download Directly.
Use HP Download Manager.
Add to your shopping cart.
xxiii
Submitting a support case

You can submit a support case directly to technical support from the SSO Web site. To
submit a support case, perform the following procedure:
1.

2.
3.
Click the Submit a new case link.
4.
Complete all the fields on the form.
5.
Click Next.
6.
Review the recommendations provided on the page, and then click Submit to
submit the support case.
Searching support documents

You can search for support documentation to help you resolve technical questions. To
search for support documentation, perform the following procedure:
1.

2.
Type the key words to describe your question in the Search box at the top of the
page, and then click the arrow next to the Search box to see the resulting
documents.
You can also use the advanced search capabilities on the SSO Web site to refine your
search. To use the advanced search capabilities, perform the following procedure:
xxiv
1.

2.
3.
Click the Self Solve tab.
4.
Type the key words to describe your question in the Search box.
5.
To narrow your search results, select the product, version, operating system, and
document types of interest.
6.
Click Search at the bottom of the page to view the results.
Training
Signing up for software update notifications

You can sign up to receive e-mail notifications when new software versions are
available. To sign up to receive e-mail notifications, perform the following procedure:
1.
Go to the Subscribers Choice Web site at:

https://h30046.www3.hp.com/SubChoice/country/us/en/s
ubhub.aspx
2.
3.
If you have never accessed the Subscribers Choice Web Site before, click the sign
in link on the left pane, and then click Register under the New Subscriber section.
4.
Enter your e-mail address and select your country.
5.
Select the Driver and Support alerts box.
6.
Click Continue at the bottom of the page.
7.
Under Column A, click + next to Software.
8.
Locate and select the appropriate product.
9.
Select the product in Column B.
10. Complete the remaining information in the form, and then click Submit.
11. You can select additional products by selecting the products in columns A and B in
the next window.
Training
We offer training courses for most of our products. You can attend HP Output
Management training in North America or EMEA. To find out more information or to
register for classes, visit our Web site at
http://www.hp.com/united-states/outputmanagement/customer_
training.html
Support
To obtain assistance, offer feedback, or request enhancements, contact Customer
Support through any of the following means:
HP Output Server
Web: http://hp.com/go/outputmanagement
xxv
Before you call
Telephone:
Location
Language
Phone
North
America
English
Dial 800-633-3600
Europe,
Middle East,
Africa
French
Use the phone system to directly contact HP Output

Management experts. Press 2, enter your SAID
number, and then enter *395.
German
English
France: 0820 211 211 (local)

or +33 1 41 86 24 05 (international)
Germany: +49 2102 90 7244 (international)
UK: 0870 842 2330 (local)
or +44 870 842 2330 (international)
For customers in other countries/regions, refer to
your support agreement for local telephone numbers.
Asia Pacific
English
Australia: 1800-032-935 (local) or +61 2 9022 9218

(international)
For customers in other countries/regions, refer to
your support agreement for local telephone numbers.
Before you call

If you experience a problem with an HP product, you can help us diagnose and solve
your problem more efficiently by collecting the following information prior to
contacting Customer Support:
Which product are you calling about?

-
What is the version number?
What is the Service Pack level?
What operating system/version does your environment use?
Are you running any clients, such as HP Output Envoy or SAP R/3?
What kind of documents are you sending, for example text, PCL, or PostScript?
From what application are you sending them?
What application did you use to create the document?
If you are calling about delivering to an FTP site,

-
xxvi
From what operating system are you delivering?
Before you call
HP Output Server
To what operating system are you delivering?
Can you repeat the problem or is it intermittent?
xxvii
Before you call
xxviii
Chapter 1
Planning the installation

This chapter describes the types of configurations that HP Output Server 4.1 supports
and the steps that you can take to prepare for an HP Output Server 4.1 installation in
your environment. For more information about particular system requirements for each
configuration option, see the Release Notes for HP Output Server.
HP Output Server 4.1 supports MySQL and Oracle database servers. Because HP
Output Server 4.1 uses a client/server model and runs on UNIX and Windows operating
systems, it supports a wide range of configuration options. HP Output Server allows
sharing of a single database instance with other applications such as HP Output
Manager for HP Software and HP Web Delivery.
HP Output Server 4.1 combines a unified installation and patching process for the
following HP Output Management product components:
HP Output Server
HP Output Manager for SAP
HP Output Distributor
HP Output Management Web Console
HP Output Manager for SAP augments the output capabilities of SAP by providing a
seamless link to HP Output Server destinations and to the extensive management and
delivery features that HP Output Server offers.
HP Output Distributor extends the traditional report distribution functions of bursting
and bundling with the personalized, device-independent delivery offered by HP Output
Server. Users can burst and bundle reports with HP Output Distributor, and then deliver
them through HP Output Server.
HP Output Server
Chapter 1
HP Output Management Web Console includes the Job Manager module. Job
Manager allows you to track and manage jobs within configured HP Output Server
domains. HP Output Management Web Console and Job Manager also include the
Authentication method management functionality. For more information on configuring
HP Output Management Web Console, see Appendix L, Configuring and
administering HP Web Console Job Manager on page 247. For more information about
using the HP Output Management Web Console, see the HP Output Management Web
Console application online help.
HP Output Server 4.1 includes the following features:
Standard and split installation options on a UNIX host - You can install HP
Output Server 4.1 either as a standard installation or as a split installation on a
UNIX host. However, only a standard installation of HP Output Server is supported
on a Windows host. An HP Output Server standard installation option installs the
HP Output Server binaries and instance together at the same location. A split
installation of HP Output Server provides you the flexibility to install the
HP Output Server binaries and instance at different locations. This also provides the
flexibility to have multiple instances use the same binaries and better control to
different administrator groups to maintain the binaries and instances separately.
Create the third party servers and default set of servers - HP Output Server 4.1
installs and configures the third party serverMySQL database server (if you
choose to install HP Output Server with MySQL as the database server) and JBoss
server by default.
The MySQL and JBoss servers are primary servers and can be managed as any
other standard HP Output Server servers using standard set of commands.
HP Output Server domain and the default set of servers are also created. It
configures the host machine and creates all primary servers: NM, PM, AIM, CM,
and EM (and an SSM on a Windows host). It also creates one of each delivery
server: DLM, JQM, and DSM. The delivery servers are named dlm, jqm, and
dsm.
Secure File Transfer Protocol - The Secure File Transfer Protocol provides an
interactive file transfer protocol, similar to FTP destination, which performs all
operations over the network in an encrypted tunnel. The documents transferred
over the network will be tamper-proof and integrity will be maintained. It uses
features such as key- based authentication and compression.
Log File Improvement - Enables the system administrators to change the logging
level for the servers dynamically without having to restart the servers.
Chapter 1
Contents of the HP Output Server package
HP Output Manager for Oracle Applications - HP Output Manager for Oracle

Applications is integrated with HP Output Server on both client and server
installation through an integration mechanism called Oracle interface, which is
capable of querying and retrieving all relative job information for HP Output Server
to use in printing. HP Output Management for Oracle application is a
database-oriented Enterprise Resource Planning (ERP) application that can deliver
output to all supported Output Server destinations.
HP Web Services for Output Server support - HP Output Server 4.1 supports HP
Web Services for Output Server.

HP Output Server product package includes the following:
HP Output Server Version 4.1 software.
HP Output Server Version 4.1 documentation.
If you purchased a license for HP Output Manager for SAP, the package includes the
following:
HP Output Manager for SAP Version 4.1 documentation.
If you purchased a license for HP Output Distributor, the package includes the
following:
HP Output Distributor Version 4.1 documentation and HP Output Distributor

Manager Version 4.1 software and documentation.
If you purchased a license for HP Output Manager for Oracle Applications, the package
includes the following:
HP Output Manager for Oracle Applications, Version 4.1 documentation.
HP Output Server Version 4.1, Software

The HP Output Server software package contains files that are necessary for installing
and configuring HP Output Server. You can download the software from the following
Web site:
For more details about downloading the software, refer to Downloading software
updates on page xxi.
HP Output Server
Chapter 1
The following table describes the directory structure and contents of the HP Output
Server software package.
Directory
Contents
HP Output Server top-level directory, which contains the

Release Notes document for HP Output Server in PDF
format
/hpos/operatingSystem
This directory contains the files necessary for installing and

configuring HP Output Server, HP Output Distributor, HP
Output Manager for SAP, HP Output Manager for Oracle
Applications, and HP Output Management Web Console.
The value of operatingSystem is one of the following:
aix
hp
hpia64
linux
sol
win64
/hposm/operatingSystem

configuring HP Output Server Manager.
The value of operatingSystem is win.
/hpomfsap/operatingSystem

configuring HP Output Manager for SAP user interface (UI).
/hpjmfhpos/operatingSystem

configuring HP Job Manager for Output Server Software.
/easysoft/operatingSystem

configuring Easysoft ODBC-Oracle Driver, Version 3.2.26.
aix
hp
hpia64
linux
sol
Chapter 1
Directory
Contents
/migration/operatingSystem
This directory contains the files necessary for migrating your

existing HP Output Server installation to HP Output Server
4.1.
aix
hp
hpia64
linux
sol
win
HP Output Server Version 4.1 documentation

The HP Output Server documentation package contains PDF versions of the
documentation for HP Output Server. You can access and download these documents in
PDF format from the following Web site:
For more details about downloading the product manuals, refer to Downloading
product documentation on page xxiii.
HP Output Server
Chapter 1
System requirements
System requirements
To perform successfully, HP Output Server requires a computer system with sufficient
power and performance. Your host machine or machines must be able to run the
necessary HP Output Server components, as well as any other software you install on
the system. The following sections explain the requirements for successfully installing
and running HP Output Server 4.1 and its supporting software. Use these sections as a
guide for determining the physical configuration of your host machine or machines.
System requirements for HP Output Server

This section describes the hardware and software requirements for HP Output Server.
After reading this section and before installing HP Output Server, read Supported HP
Output Server configurations on page 26.
Hardware
This section summarizes the minimum disk space and memory that HP recommends for
each supported platform for an HP Output Server installation. These recommended
values include what is required for HP Output Manager for SAP and HP Output
Distributor, but are in addition to disk space and memory required by any other HP
Output Management products that may be installed.
Table 1-1. Minimum hardware requirements
Default (Full) Installation
Client-Only Installation1
Operating System and Hardware
Minimum
Disk Space2
Minimum
Physical
Memory3
Minimum
Disk Space
Minimum
Physical
Memory
HP-UX 11.11 on PA-RISC (64-bit

kernel)
1.5 GB
2 GB
335 MB
256 MB
HP-UX 11.23 on Itanium (IA64)

(64-bit kernel)
1.5 GB
2 GB
350 MB
256 MB

kernel)
1.5 GB
2 GB
350 MB
256 MB

kernel)
1.5 GB
2 GB
350 MB
256 MB
HP-UX 11.31on Itanium (IA64)

(64-bit kernel)
1.5 GB
2 GB
350 MB
256 MB
Chapter 1

System requirements
Table 1-1. Minimum hardware requirements (continued)

Default (Full) Installation
Client-Only Installation1
Minimum
Disk Space2
Minimum
Physical
Memory3
Minimum
Disk Space
Minimum
Physical
Memory
Solaris 10 on SPARC (64-bit kernel)
1.5 GB
2 GB
405 MB
256 MB
IBM AIX 6.1 (64-bit kernel)
1.5 GB
2 GB
345 MB
256 MB
Red Hat Enterprise Linux 5.0, 64-bit

kernel on x64
1.5 GB
2 GB
250 MB
250 MB
Red Hat Enterprise Linux Advanced

Platform 5.0, 64-bit kernel on x64
1.5 GB
2 GB
250 MB
250 MB
SUSE Linux Enterprise Server 10,

64-bit kernel on x64
1.5 GB
2 GB
250 MB
128 MB
Microsoft Windows Server 2003 R2,

Standard Edition on x86 (64-bit
kernel)
1.5 GB
2 GB
Not applicable
Not applicable

Enterprise Edition on x86 (64-bit
kernel)
1.5 GB
2 GB
Not applicable
Not applicable

Standard Edition on x86 (64-bit
kernel)
1.5 GB
2 GB
Not applicable
Not applicable

Enterprise Edition on x86 (64-bit
kernel)
1.5 GB
2 GB
Not applicable
Not applicable
1: HP Output Distributor does not support a client-only installation.

2: Disk space and physical memory requirements depend on the number of servers you configure on a given host and
the overall processing load on the host. For example, if you have large log files, a large number of devices, or a large
number of jobs, the disk space and physical memory requirements could be affected. The disk space mentioned in this
table includes the minimum disk space for MySQL.
3: Unless you have greater than 4 GB of physical memory, consider configuring your paging space/swap file to double
the amount of the system's physical memory. This includes memory required for JBoss and MySQL database server.
HP Output Server
Chapter 1
System requirements
Minimum ulimit parameter values required for IBM AIX 6.1

The minimum ulimit parameter values required to install HP Output Server 4.1 with
MySQL as the database server and JBoss as the Web server on IBM AIX 6.1 (64-bit
kernel) system are as follows:
Table 1-2. Ulimit parameter values for IBM AIX 6.1
Ulimit parameter
Values
time (seconds)
unlimited
file (blocks)
1048576
data (kbytes)
unlimited
stack (kbytes)
10240
memory (kbytes)
1048576
coredump (blocks)
1048576
nofiles (descriptors)
10240
NOTE: The data segment size should be greater than 2GB to run HP
Output Server 4.1.
Chapter 1

System requirements
Operating system patches

The following table identifies recommended operating system patches, if any, that HP
has tested for use with HP Output Server 4.1. More recent operating system patches,
quality releases, or Service Packs may exist. Only those listed in the following table
have been tested by HP for use with HP Output Server 4.1.
Table 1-3. Supported operating system patch levels
Patch Level
HP-UX 11.11 on PA-RISC

(64-bit kernel)
Required Patch Bundle for HP-UX 11i, June 2003

Hardware Enablement Patches for HP-UX 11i v1,
December 2006
Quality Pack Depot for 11i v1, June 2009
HP-UX 11.23 on Itanium (IA64)

(64-bit kernel)
Required Patch Bundle for HP-UX 11i v2 (B.11.23),

September 2004
Feature Enablement Patches for HP-UX 11i v2, September
2010
Hardware Enablement Patches for HP-UX 11i v2, October
2010
Quality Pack Depot for 11i v2, December 2010
HP-UX 11.23 on PA-RISC

(64-bit kernel)
Required Patch Bundle for HP-UX 11i v2 (B.11.23),

September 2004
2010
Hardware Enablement Patches for HP-UX 11i v2, October
2010
Quality Pack Depot for 11i v2, December 2010

kernel)

September 2010
2010
Quality Pack Depot for HP-UX 11i v3, September 2010
HP-UX 11.31on Itanium (IA64) (64-bit

kernel)

September 2010
2010
Quality Pack Depot for HP-UX 11i v3, September 2010
HP Output Server
Chapter 1
System requirements
Table 1-3. Supported operating system patch levels (continued)

Patch Level
Solaris 10 on SPARC
(64-bit kernel)
Solaris 05/09 Patch Bundle
IBM AIX 6.1

(64-bit kernel)
Service Pack Level 02
Red Hat Enterprise Linux 5.0 ES; 64-bit

kernel (HPOS Servers and Client; R/3
Servers and Client Only) on x64
Update 5
Red Hat Enterprise Linux Advanced

Platform 5.0; (HPOS Servers and
Client; R/3 Servers and Client Only) on
x64
Update 5
SUSE Linux Enterprise Server 10;

64-bit kernel on x64
Service Pack 3

Standard Edition x86
(64-bit kernel)
Service Pack 2

Enterprise Edition x86
(64-bit kernel)
Service Pack 2

Standard Edition x86
(64-bit kernel)
NA

Enterprise Edition x86
(64-bit kernel)
NA
Technology Level 06
System requirements for HP Output Server Manager and HP Job

Manager for Output Server Software
Hardware
The minimum memory required for HP Output Server Manager installation is 512 MB
for Windows XP and 1GB for Windows Vista Enterprise Edition and disk space is 6
MB.
10
Chapter 1

System requirements
The minimum memory required for an HP Job Manager for Output Server Software
installation is 64 MB and disk space is 5 MB.
Software
Operating system patches for HP Output Server Manager and HP Job
Manager for Output Server Software
The following table describes the supported operating systems and the recommended
patch for the supported platform.
Table 1-4. Supported operating systems and patches
HP Output Server
Patch Level
Microsoft Windows Server 2003 R2 (32-bit

kernel) Standard Edition and Enterprise
Edition
Service Pack 2

Edition
Service Pack 2
Microsoft Windows XP Professional
Service Pack 3
Microsoft Windows XP Professional (64-bit

kernel)
Service Pack 3
Microsoft Windows Vista Enterprise Edition
Service Pack 2
Microsoft Windows Vista Enterprise Edition

(64-bit kernel)
Service Pack 2

Edition
NA

Edition
NA
Microsoft Windows Terminal Services 5.2
Service Pack 2
Microsoft Windows Citrix Presentation

Server Environment 4.5
NA
Microsoft Windows 7 (32-bit kernel)
NA
Microsoft Windows 7 (64-bit kernel)
NA
11
Chapter 1
System requirements
Client browser requirements

HP Output Server supports the following Web browsers:
Table 1-5. Supported Web browsers
Browser
Minimum Supported Version
Microsoft Internet Explorer
6.0.26
Mozilla Firefox
1.5.0.4
Client Web browsers must have a Java Runtime Environment available in order to run
the authentication applet that is part of the built-in client-side authentication method
(and is optionally a part of any custom authentication methods). The applet is supported
with the following Java Runtime Environments:
Table 1-6. Supported Client-Side Java Runtime Environments
Distribution
Minimum Supported Version(s)
Microsoft JVM
5.0 and later
Sun JRE
1.4,1.5 and 1.6
By default, none of Microsoft operating systems come with JVM. To find out if JVM is
available on your system, do the following:
1.
Open Internet Explorer.
2.
Select Tools > Internet Options
3.
In the Internet Options window, select the Advanced tab.
4.
Scroll down the Settings list to see if Microsoft VM is listed. If it is available,

select the menus listed under it and click OK.
5.
In case Microsoft VM is not available, you must download Sun JRE from the Sun
site.
If you use Firefox, you must download the Sun JRE from the Sun site.
When using Internet Explorer, if the security settings for the zone containing HP Output
Server are set to High (or Java and/or Java applets are disabled), the authentication
applet will not be able to run on the client. If this occurs (and the authentication applet is
needed), adjust the security settings.
12
Chapter 1

System requirements
Kernel parameters
This section summarizes the recommended kernel parameters for an HP Output Server
installation.
If you are running a large HP Output Server configuration and experience problems, it
may be necessary to increase the kernel/environmental limits on processes and/or file
handles beyond those in the recommendations that follow. Symptoms that may be
related to these limits include but are not restricted to the following:
Processes getting stuck or failing to start
Error messages about files that cannot be opened or locked
Broken pipes
Processes exiting
AIX recommended settings

With heavy job loads in HP Output Server, memory or resource issues may occur with
related messages logged to the HP Output Server Delivery Manager (DLM) and/or Job
and Queue Manager (JQM) server logs. If this occurs, HP recommends that you use HP
Output Server attributes to tune DLM and JQM memory usage.
For the DLM, use the -cleanup-checkjob-period-limit attribute to limit the
size of internal time-out queues that the DLM builds.
For the JQM, modify the -job-retention-period-limit to limit the size of
internal JQM time-out queues.
For more information about these attributes, see the System Administrators Attribute
Reference for HP Output Server.
If messages indicating memory or resource issues continue to appear in the DLM or
JQM logs after you adjust these attributes for DLMs and/or JQMs running on the AIX
operating system, or the AIX operating system terminates these server processes,
consider modifying operating system parameters. For example, consider increasing the
data segment size on the AIX operating system using the ulimit command.
HP Output Server
13
Chapter 1
System requirements
Linux recommended settings

The following table identifies the recommended kernel parameters for Linux 64-bit
hosts.
Table 1-7. Recommended Linux kernel parameters
Kernel Parameter
Description
Recommended
Setting
kernel.threads-max
Maximum number of
threads.
Minimum 4000
fs.file-max
Maximum number of file

descriptors for the
system.
8192
Use the following command to set the kernel parameters on Linux:

sysctl -w <parameter name> = <value>
For example:
sysctl -w kernel.threads-max = 4000
For detailed information about checking and setting kernel parameters on a Linux
operating system, see the documentation that accompanies the operating system.
14
Chapter 1

System requirements
HP-UX recommended settings

The following table identifies the recommended kernel parameters for HP-UX hosts.
For information about checking and setting kernel parameters on an HP-UX operating
system, see the documentation that accompanies the operating system.
Table 1-8. Recommended HP-UX kernel parameters
Kernel Parameter
Description
Recommended
Setting
dbc_max_pct
Maximum percentage of memory for dynamic buffer cache.
25*
This setting is for HP-UX
11.11.
For HP-UX 11.23 on
PA-RISC and Itanium,
use the operating system
default setting.
Note:
This parameter does not
exist on HP-UX 11.31 on
PA-RISC and IA64 and
should not be used for
these operating systems.
HP Output Server
15
Chapter 1
System requirements
Table 1-8. Recommended HP-UX kernel parameters (continued)

Kernel Parameter
Description
Recommended
Setting
max_thread_proc
Maximum number of threads that one process can create.
1024
Because the max_thread_proc kernel parameter is

related to the MySQL max_connections system
variable, it is important to coordinate the two settings.
If MySQL server is
running on a different
host than HP Output
Server, set the
max_thread_proc
parameter to 256 on the
HP-UX system that runs
HP Output Server.
The MySQL max_connections tuning variable defines

the number of concurrent connections (threads) MySQL will
allow at any given time. When you install MySQL for HP
Output Management on a UNIX host, the my.cnf file
created by setupmysql.pl sets max_connections to
1000.
If max_thread_proc is set to a value that is lower than
the value of max_connections, it is possible that
attempts to connect to the MySQL server will fail because
the kernel will not allow the server to create a thread to
service the request.
This setting is valid for

HP-UX 11.11, HP-UX
11.23 on PA-RISC and
Itanium, and HP-UX
IA64.
The max_thread_proc kernel parameter setting may

also be affected by the following HP Output Server
attributes:
-queue-task-maximum
-queue-task-ratio
-printer-task-maximum
-printer-task-ratio
For more information about these attributes, see the System
Administrators Attribute Reference and Tuning and
Resource Management in the System Administrators Guide
for HP Output Server 4.1.
maxdsiz_64bit
Maximum data segment size for executing HP Output Server

processes.
If the process data segment grows beyond this limit through
dynamic memory allocation, for example, the kernel will
terminate the process. For more information about the
memory allocation method HP-UX uses, see the malloc
man page on your HP-UX system.
16
4294967296
HP-UX 11.11, HP-UX
Itanium, and HP-UX
IA64.
Chapter 1

System requirements

Kernel Parameter
Description
Recommended
Setting
maxfiles
Soft limit on how many files a single process can have

opened or locked at any given time.
2048
Hard limit on how many files a single process can have

opened or locked at any given time.
2048
maxfiles_lim

HP-UX 11.11, HP-UX
Itanium, and HP-UX
IA64.
Note that this

recommended setting is
for HP-UX 11.11.
For HP-UX 11.23 on
default setting.
For HP-UX 11.31 on
PA-RISC and IA64, use
the operating system
default setting (4096).
maxuprc
Maximum number of simultaneous processes for any given

user.
2000
Note that this
for HP-UX 11.11, and
HP-UX 11.23 on
PA-RISC and Itanium.
For HP-UX 11.31 on
3780.
HP Output Server
17
Chapter 1
System requirements

Kernel Parameter
Description
Recommended
Setting
nfile
Maximum number of files that can be open simultaneously.
[(nproc x 2) + 1000] +
[(numPhysDest x 5) +
(numJQMs x 10) +
(numDLMs x 10) +
(numLPGDest x 2)]
where numPhysDest is
the number of physical
destinations; numJQMs is
the number of JQMs;
numDLMs is the number
of DLMs on the host; and
numLPGDest is the
number of destinations
configured in the LPR
Gateway
Note that this
for HP-UX 11.11.
For HP-UX 11.23 on
default setting.
For HP-UX 11.31 on
2048.
nflocks
Maximum number of file locks available on the system. You

may need to adjust the number of file locks when configuring
a large number of HP Output Server servers (approximately
150 or greater). If the limit is reached while configuring
servers, the servers above the limit will not start and a
message appears instructing you to adjust the
-server-startup
-completion-time attribute. The server log file
identifies the source of the problem and contains the
following error message:
Equal to or greater than

the total number of HP
Output Server servers on
a single host.
For HP-UX 11.31 on
Unable to open file - filename.LCK in

function LockFileOpen, errno=2.
Each server process needs one file lock. Consider other
processes running on the system that may need file locks
when adjusting this kernel parameter.
18
Chapter 1

System requirements

Kernel Parameter
Description
Recommended
Setting
nkthread
Number of threads that all processes can run, system-wide, at

a given time. If nkthread is set too low, the following
message appears in the system syslog file:
max_thread_proc
x 2
vmunix: kthread: table is full
Note that this

for HP-UX 11.11.
For HP-UX 11.23 on
default setting.
For HP-UX 11.31 on
Maximum total number of simultaneous processes allowed.
nproc
4000
Note that this
for HP-UX 11.11. For
HP-UX 11.23 on
default setting.
For HP-UX 11.31 on
* If your host contains more than 4 GB of memory, decrease this value to 15.
The formula for nfile is for HP Output Server 4.1 with HP Output Distributor 4.1 and HP Output Manager for SAP 4.1. It does not
include other HP Output Management products or other applications.
Setting kernel parameters on HP-UX

The following steps describe one method for setting an HP-UX kernel parameter by first
checking the value of the parameter, and then setting the parameter.
NOTE: For more information about setting kernel parameters on an
HP-UX operating system, see the documentation that
accompanies the operating system.
HP Output Server
19
Chapter 1
System requirements
Checking a kernel parameter value

To check the value of a kernel parameter on an HP-UX host, perform the following
steps:
1.
Log in as root.
2.
To check the value of the kernel parameter, use the command syntax identified in
the following table for your platform.
Operating system
Command
HP-UX 11.11 (64-bit kernel)
kmtune -q parameter
where parameter is the name of the kernel
parameter, for example:
kmtune -q dbc_max_pct
HP-UX 11.23 (64-bit kernel) on

Itanium (IA64) or PA-RISC
kctune -q parameter
kctune -q dbc_max_pct

PA-RISC and IA64
kctune -q parameter
kctune -q max_thread_proc
Setting a kernel parameter value

To change a kernel parameter setting, perform the following steps:
1.
Log in as root.
2.
Enter the following command:

cp /stand/system /stand/system.prev
20
Chapter 1

System requirements
3.
For each parameter you want to change, execute the following command:
Operating system
Command
HP-UX 11.11
kmtune -s parameter=value
parameter and value is the new value (number or
formula)

Itanium (IA64) or PA-RISC
kctune -s parameter=value

PA-RISC and IA64
kctune -s parameter=value

formula)

formula)
You can use the kmtune -q or kctune -q command (depending on your

operating system) to verify your changes.
4.
If you are using HP-UX 11.23, skip to step 5. On HP-UX 11.11, execute the
following commands:
cd /stand/build
cp ../vmunix ../vmunix.prev
mk_kernel
mv vmunix_test ../vmunix
5.
Reboot the system.
6.
To verify the settings, execute the kmtune -q or kctune -q command

(depending on your operating system).
Solaris 10 recommended settings

NOTE: If the host operating system is Solaris 10, then by default the
kernel parameters are auto-tunable during the installation
process and no manual settings are required.
Swap space requirements on Solaris

This section describes the swap space requirements on the Solaris operating system, if
you have installed HP Output Server and configured Oracle as the back-end database.
HP Output Server
21
Chapter 1
System requirements
The swap space requirements depend on the following parameters:
Number of servers that you intend to configure
Number of destinations that you intend to create
Number of jobs that would be typically processed in a day
The following table lists the approximate swap space required for each of the HP Output
Server servers.
Table 1-9. HP Output Server servers and required swap space
HP Output Server
Server
Required Swap Space

(in MB)
NM
70.5
PM
70.5
AIM
70.5
EM
71.5
CM
71.5
JQM
71.5
DLM
71.5
DSM
72.5
NOTE: The values specified in the table are approximate values for
an HP Output Server installation with Oracle as the database
server on the Solaris platform.
For example, if your HP Output Server installation has 8 JQMs, 10 DLMs, and 80
DSMs, then you can calculate the minimum required swap space for HP Output Server
servers using the following formula:
70.5 + 70.5 + 70.5 + 71.5 + 71.5 + (8*71.5) + (10*71.5)
+ (80*72.5) = 7442 MB
The swap space required for HP Output Server will increase as more destinations are
configured and jobs submitted. You should plan for additional swap space for this
purpose. HP recommends that you plan for an additional swap space of the same size as
the required swap space.
22
Chapter 1

System requirements
Based on the preceding formula, the required swap space is 7442 MB. If you allocate
another 7442 MB for additional swap space, the total swap space would be 14884 MB.
This is the minimum swap space that HP recommends for an HP Output Server
installation similar to the preceding example.
NOTE: The attributes -cleanup-interval and
-cleanup-checkjob-period-limit, when set to
values larger than the default, can result in high memory
usage especially when job submission rates are high. This
can result in a corresponding increase in the swap space
requirements (more than the minimum recommended swap
space). If you intend to modify the value of the attributes to
values larger than the default, you must plan accordingly.
Use the following instructions to check for and add swap space on the Solaris platform.
To check swap space:
Run the $ swap -s command.

The command displays the used as well as the available swap space on the system.
To create and add a swap file:

1.
To create a swap file, enter the following command:

$ mkfile <size> <swap_file_path>
For example, if you want to create a 1000-MB swap file in the
/opt/data/swapfile directory, enter the following command:
$ mkfile 1000m /opt/data/swapfile
2.
To add the swap file to the system swap space, enter the following command:
$ swap -a /opt/data/swapfile
3.
To use the newly created swap file when the system is rebooted, add an entry for
the swap file in the /etc/vfstab file by running the following command:
/opt/data/swapfile --swap -no -
For more information on swap space management, see the documentation for your
operating system.
HP Output Server
23
Chapter 1
System requirements
Interoperability with HP Output Management applications

The following table lists the required Service Pack for each product. This ensures that
HP Output Management products that rely on HP Output Server will continue to
function.
If you are installing HP Output Server for the first time and plan to install other HP
Output Management products that rely on HP Output Server, install and patch HP
Output Server prior to installing and patching the other HP Output Management
products.
Table 1-10. Supported HP Output Management solutions with the current release
HP Output Management Solution
Version and Patch Level
Server side
Version 4.1 with Service Pack 11.1 (4.1.0.1)
HP Output Server

HP Web Delivery

Version 1.6.1
Client side
HP Output Server

HP Output Explorer
Version 4.1.0.1
Version 3.0.0.34 (on remote hosts)
HP Output Envoy
Version 4.1.0.1
Version 1.1.0.34 (on remote hosts)
HP Output Distributor Manager
Version 4.1 with Service Pack 11.1
HP Output Server Manager
Version 4.1
Version 2.0.0.4
24
HP Smart Office Delivery for

Output Server
Version 4.1
HP Job Manager for Output

Server Manager
Version 4.1

User Interface
Version 4.1
Version 3.0.0.4
Version 3.0.0.4
Version 2.0.
Chapter 1

System requirements
Interdomain interoperability
HP Output Server 4.1 communicates with HP Output Server 4.0 domain in the
following ways:
You can submit jobs to HP Output Server 4.1 and track them from HP Output
Server 4.0.
Server 4.1.
Events and AIM operations related to job submission and tracking are sent and
performed.
Jobs submitted from HP Output Server 4.1 to HP Output Server 4.0 cannot access
the new features of HP Output Server 4.1.
Intradomain interoperability
HP Output Server 4.1 communicates with client installations of HP Output Server 4.0 in
the following ways:
Server 4.0 client installations.
Events and AIM operations related to job submission and tracking are sent and
performed.
HP Output Server 4.0 clients do not support new features in HP Output Server 4.1.
Supported SAP installations with HP Output Manager for SAP,

Version 4.1
HP Output Manager for SAP 4.1 is supported with all SAP-supported versions of SAP
R/3 that function with the BC-XOM and/or BC-CON interface. HP Output Manager for
SAP 4.1 is tested with SAP R/3 Enterprise (4.7), SAP ECC 5.0, and SAP ECC 6.0.
For HP Output Manager for SAP 4.1 to function properly with SAP R/3 Enterprise
(4.7), the minimum required BASIS Support Package Level is 41. If you are running
SAP ECC 5.0, HP recommends that you use BASIS Support Package Level 9. Check
the Release Notes that accompany HP Output Server 4.1, or the latest Service Pack, for
updates to required or recommended SAP patch levels.
NOTE: The installation script for HP Output Server 4.1 does not
check for an existing SAP installation.
HP Output Server
25
Chapter 1
Supported HP Output Server configurations
Supported HP Output Server configurations

The section describes supported HP Output Server configurations. For information
about supported configurations with MySQL for HP Output Management and HP
Output Server, see the Installation and Configuration Guide and the Release Notes for
for the latest release of MySQL for HP Output Management. For information about
configurations supported with Oracle database server for HP Output Management and
HP Output Server, see the Release Notes for HP Output Server.
HP supports the following HP Output Server configurations:
Single HP Output Server domain installed on a single host
Single HP Output Server domain split across multiple hosts
Multiple HP Output Server domains installed on a single host (UNIX only)
Multiple HP Output Server domains split across multiple hosts
Client installation of HP Output Server (UNIX only)
An HP Output Server domain is a standalone configuration of HP Output Server that

includes a set of primary servers and at least one of each type of delivery server. For
information about installing a single HP Output Server domain on a single host, see
Chapter 2, Installing HP Output Server on page 33.
You can also install HP Output Server by joining an existing HP Output Server domain.
This configuration option distributes HP Output Server delivery servers among multiple
hosts. For information about distributing an HP Output Server domain among multiple
hosts, see Chapter 2, Installing HP Output Server on page 33.
For assistance with creating multiple HP Output Server domains, contact Customer
Support or your Implementation and Integration Services representative.
A client installation of HP Output Server joins the local machine to an existing HP
Output Server domain without configuring HP Output Server servers on the machine.
This option allows jobs to be submitted and monitored by a machine other than the
server host. This configuration option is available on supported UNIX systems only.
For information about distributing an HP Output Server domain among multiple hosts,
see Chapter 2, Installing HP Output Server on page 33.
Installation and configuration overview

To install and configure HP Output Server 4.1 with HP Output Manager for SAP 4.1
and HP Output Distributor 4.1, you must perform the following tasks:
26
Chapter 1
Installation and configuration overview
1.
Install HP Output Server 4.1. For more information, see Chapter 2, Installing HP
Output Server on page 33.
2.
Configure HP Output Server permissions and a test delivery pathway. See Chapter
6, Configuring HP Output Server on page 149.
If you plan to use HP Output Manager for SAP, complete its installation and
configuration by performing the following tasks:
1.
Complete the installation using the steps in Completing the installation of HP

Output Manager for SAP 4.1 on page 98.
2.
Configure the CPIC user and HP Output Manager for SAP interfaces using the
instructions in the System Administrators Guide for HP Output Manager for SAP.
If you plan to use HP Output Distributor, complete its installation and configuration by
performing the following tasks:
1.
Complete the installation using the information in Completing the installation of

HP Output Distributor 4.1 on page 99.
2.
Configure permissions in the HP Output Server Privilege Manager by assigning

privileges to users who create or modify objects in an HP Output Distributor
database. For more information, see the System Administrators Guide for HP
Output Distributor.
3.
Create delivery pathways using the information in the System Administrators

Guide for HP Output Distributor. Each HP Output Distributor destination connects
to an HP Output Distributor database.
4.
Configure HP Output Distributor databases using the odconfig_server

command.
You can configure one or more HP Output Distributor databases on one or more HP
Output Distributor production hosts. For example, you can put marketing, sales,
and accounting report processing information in separate databases, and enable
each department to maintain its own database. You can create multiple HP Output
Distributor databases in single HP Output Server domains or in multiple HP Output
Server domains to localize bursting and bundling.
If you want to use HP Output Distributor on a host where HP Output Server was
installed by joining an existing domain, ensure that you create delivery servers, an
HP Output Distributor database, and a delivery pathway on that host.
For more information about the odconfig_server command, see the System
Administrators Guide for HP Output Distributor.
5.
HP Output Server
Create report definitions and sets using information in the System Administrators
Guide for HP Output Distributor.
27
Chapter 1
Pre-installation checklist
Pre-installation checklist
The following checklist outlines the information that you need to install HP Output
Server.
Is your platform supported?
Do you have the recommended patches for your platform?
Does your platform require any specific procedures or considerations?
Are any patches available for HP Output Server?
What are the kernel parameters?
Do you have sufficient swap space?
Do you have sufficient disk space?
Do you have sufficient physical memory?
What are the device dependencies and limitations?
Are permissions set correctly on your system?
Do you have the required ports for HP Output Server installation?

NOTE: HP Output Server installation requires 17 ports for JBoss
server configuration, 1 port where NM listens on, and 1 port
where MySQL database server listens (if you plan to install
HP Output Server with MySQL as the database server).
Ensure that all the ports you plan to specify during the
installation are enabled.
Setting permissions
Before you install HP Output Server, you must have the permissions described in the
following sections.
UNIX hosts
If you are installing HP Output Server on a UNIX system, consider the following
requirements:
28
To install HP Output Server as root, ensure that you log in as root to the hosts
on which you plan to install and configure HP Output Server.
Chapter 1
Planning an installation on a network
If you are a user other than the root user, ensure that you can log in with a valid
user ID with sufficient privileges to the hosts on which you plan to install and
configure HP Output Server.
Ensure that you have a login account. HP Output Server servers use the hposadm
login account as the default account.
Windows hosts
If you are installing HP Output Server on a Windows host, consider the following:
Can you log in as a user with administrator privileges?
Do you have write permission for the file systems you write to during installation
and configuration? The default installation directory is C:\HP\OM.
Is the underlying file system NTFS?

NTFS uses hard links. Because HP Output Server uses hard links to pass files from
client to server, the underlying file system must be NTFS.
CAUTION: Ensure that your Windows system uses NTFS, not FAT.
Does the Windows server user have write permission for the file systems where you
will install HP Output Server?

This section provides general information you need to plan an installation of HP Output
Server throughout a network. HP Output Server is designed to meet a variety of output
management needs in many different environments. Read about the following topics as
an introduction to planning an HP Output Server configuration:
Device requirements
Connecting devices
Naming conventions
For more information, see the System Administrators Guide for HP Output Server or
consult your Implementation and Integration Services representative.
HP Output Server
29
Chapter 1
Device requirements
After successfully installing HP Output Server in a test environment, consider how you
plan to distribute HP Output Server across your network. To design a configuration that
best suits your resources and information delivery needs, perform the following tasks:
Attend HP Output Server training.
Read the System Administrators Guide for HP Output Server.
Discuss your configuration plan with a consultant from Implementation and

Integration Services.
When planning your HP Output Server configuration, assess the available hardware
resources. You can optimize reliability and performance by installing and configuring
servers according to your hardware resources and information delivery requirements.
Carefully select the number of servers you need and their locations and the hardware.
Consider the following factors when planning which servers you want to place on which
hosts:
Size of your network
Number of supported destinations
Performance tuning
Throughput required
Response time required
Speed of printers
Anticipated loading of hosts where HP Output Server software resides
The Delivery Manager (DLM), Job and Queue Manager (JQM), and Destination
Manager (DSM) affect delivery performance. For example, configuring a JQM server
on a powerful host can provide a good buffer between fast inbound delivery requests
and slow printers.
Connecting devices
As you plan how to connect devices to HP Output Server, consider the following:
30
Attach printers through a TCP/IP connection
Use the lpd (line printer daemon) protocol to connect to a host running lpd or a
printer supporting the lpd protocol
Connect modems through network connectivity devices such as terminal servers
Chapter 1
Naming conventions
You can assign names to HP Output Server objects. Names for all objects must be
unique within an HP Output Server domain. When naming logical destinations,
remember that users see the logical destination names in various HP Output
Management applications. Make these names intuitive and descriptive.
Certain characters can also be used when naming HP Output Server objects. The
following are valid characters for use when naming logical destinations, physical
destinations, and queues:
Uppercase or lowercase letters (A through Z or a through z)
Numbers (0 through 9)
The underscore character (_)
The following restrictions apply to object names:
If the server or queue name contains an invalid character, such as a space or a

quotation mark, the server can either behave unpredictably or fail to run.
Server names cannot start with numbers (0 through 9) and should not exceed 26
characters.
NOTE: The server name should not exceed 16 characters for Event
Manager (EM).
Server names having the same text characters but different special characters such
as period (.), underscore (_), and dash (-) are considered to be the same. For
example, dsm_01, dsm-01, and dsm.01 are all considered to be the same, and
cannot co-exist.
Although object names can contain uppercase and lowercase letters, uppercase A is
equivalent to lowercase a. This means that the names DSM, dsm, and Dsm (or any
variation of capitalizing the same set of letters) are equivalent and prohibited in a
single HP Output Server domain.
The following optional naming conventions can assist you with creating meaningful
names for your servers and destinations:
Use the convention host_serverType_serverNumber for server names. For example:

dilbert_dlm_01 for a DLM running on the dilbert host
Preface the names of physical destinations with a p.

For example:
p_ps1 for a PostScript printer
HP Output Server
31
Chapter 1
Preface queue names with a q.

For example:
q_sales_printer
Use more meaningful names that are specific to their function.

For example:
sales_printer and psales_printer for the logical and physical
destinations for the Sales departments printer
Server names beginning with a dash (-), underscore (_), or a period (.) are not supported
for HP Output Server 4.1, and you will receive an error if you create server names with
these characters.
When migrating from HP Output Server 3.5 or 4.0 to HP Output Server 4.1, the HP
Output Server server names should not begin with special characters such as dash (-),
period (.), or with an underscore (_).
NOTE: Ensure that the server names are valid before creating the
server.
Obtaining the GPL source code

If you require the source code for third-party softwares included in HP Output
Server 4.1 as per the General Public License (GPL) agreement, contact HP
Customer Support.
32
Chapter 2
Installing HP Output Server

This chapter describes how to install HP Output Server 4.1 on UNIX and Windows
hosts. Before you begin, read Chapter 1, Planning the installation on page 1 and the
Release Notes for important information about system requirements and configuration
options.
NOTE: HP recommends that you install HP Output Server on a
non-production host before installing it on a production host.
When you are finished installing HP Output Server, use the information in Chapter 6,
Configuring HP Output Server on page 149 to configure and test the installation. For
patch updates, check the Software Support Online (SSO) Web site:
For more details about accessing and using the Software Support Online Web site, refer
to Accessing the Software Support Online Web site on page xix.
HP Output Server
33
Chapter 2
Installation options
You can install HP Output Server 4.1 either as a standard installation or as a split
installation on a UNIX host. However, only a standard installation of HP Output Server
is supported on a Windows host. An HP Output Server standard installation option
installs the HP Output Server binaries and instance together at the same location. A split
installation of HP Output Server provides you the flexibility to install the
HP Output Server binaries, instances, and logs at different locations. This also gives you
the flexibility to have multiple instances use the same binaries. Different administrator
groups can maintain the binaries and instances separately.
On a UNIX host, you can perform a server installation or a client-only installation. On a
Windows host, you can perform a server installation only.
The following configuration options are available when you install HP Output Server:
Create the third party servers and default set of servers. HP Output Server 4.1
installs and configures the third party serversMySQL database server (if you
choose to install HP Output Server with MySQL as the database server) and JBoss
server by default.
This option creates an HP Output Server domain and a default set of servers. It
configures the host machine and creates all primary servers: MySQL (if you install
HP Output Server with MySQL as the database server), NM, PM, AIM, CM, EM
(and an SSM on a Windows host), and JBoss. It also creates one default server for
each delivery server: DLM, JQM, and DSM. The delivery servers are named dlm,
jqm, and dsm.
Join an existing domain. This option configures a new HP Output Server host and
joins it to an existing HP Output Server domain.
If you choose to install HP Output Server installation with integrated MySQL as the
database server, this option will create the MySQL and JBoss servers and all the
MySQL database server prompts are prompted during the HP Output Server
installation.
If you choose to install HP Output Server installation with remote/existing database
server, you have the option of configuring the database server during the
installation or after the HP Output Server installation. Use this option to distribute
HP Output Server delivery servers among multiple hosts. Note the following for
this option:
-
34
If you choose to configure the database connection after installation, you must
configure the database connection before creating any HP Output Server
servers. For more information, see Appendix C, Configuring the database
connection on UNIX hosts on page 203.
Chapter 2

After you complete the installation, use the config_server command to

create delivery servers on the new host. For more information about using the
config_server command, see the System Administrators Command
Create a new domain without a default set of servers. This option configures the
host for a new HP Output Server domain but does not create any HP Output Server
servers. Note the following for this option:
-
If you choose to configure the database connection after installation, you must
configure the database connection before creating any HP Output Server
servers. For more information, see Appendix C, Configuring the database
connection on UNIX hosts on page 203.
After you complete the installation, you must manually configure servers using
the config_server command. For more information about using the
config_server command, see the System Administrators Command
Perform a client-only installation (UNIX host only). This option connects the
local machine to an existing HP Output Server domain without configuring HP
Output Server servers on the machine. This option allows jobs to be submitted and
monitored by a machine other than the host server and allows you to configure
EPOD server.
For instructions, see Performing a client-only installation (UNIX host
only) on page 72.
For more information on commands for configuring the EPOD server, refer to HP
Output Server System Administrators Command Reference.
HP Output Server
35
Chapter 2
Assumptions and restrictions

HP Output Server 4.1 integrates the installation of HP Output Manager for SAP 4.1 and
HP Output Distributor 4.1. When you perform a server installation of HP Output Server
4.1, the software for HP Output Manager for SAP 4.1 and HP Output Distributor 4.1 is
installed automatically.
The following assumptions and restrictions are applicable for implementing HP Output
Server 4.1:
36
These instructions refer to the location of the HP Output Server binaries as

installBinDir and the location of HP Output Server instance as installInstDir.
Substitute the correct path of the binaries installation directory when you see the
installBinDir variable and the correct path of the instance installation directory
when you see the installInstDir variable. For a standard installation of HP Output
Server, that is, where the binaries and instance are installed at the same location,
substitute the correct path of the HP Output Server installation directory when you
see either the installDir, the installBinDir, or the installInstDir variables.
You must have the following versions of Java Runtime Environment installed,
configured, and running on the machine where you want to install HP Output
Server 4.1:
-
Java SE Runtime Environment 6, update 20 or a higher version on Windows,

Linux, and Solaris hosts
JRE 6.0 update 8 or a higher version on HP-UX hosts
Java 6.0 SR 8 or a higher version on AIX hosts
If you intend to use the Oracle database server with HP Output Server, the Oracle
database server must be installed and fully functional before HP Output Server is
installed.
HP Output Server requires Oracle Instant Client libraries to communicate with the
Oracle database server. Install Oracle Instant Client libraries on the same machine
where you plan to install HP Output Server.
These instructions refer to the location of your Easysoft ODBC-Oracle Driver

installation hierarchy as easysoftDir. Substitute the correct path name for your
installation when you see the easysoftDir variable.
To obtain optimum performance from your HP Output Server installation with

Oracle as the database server, certain Oracle parameters must be set. For
information on tuning Oracle parameters, see Appendix I, Tuning Oracle
parameters on page 239.
Chapter 2

HP Output Server
Additional installation and/or configuration tasks must be performed to complete

the installation of HP Output Manager for SAP and HP Output Distributor after you
successfully install HP Output Server. If you plan to use either of these integrated
products, see Completing the installation of HP Output Manager for SAP 4.1
on page 98 and Completing the installation of HP Output Distributor 4.1
on page 99.
HP Output Server 4.1 Server and Oracle database server installations must be on
the same subnet if you choose to install HP Output Server with Oracle as the
database server.
HP Output Server 4.1 limits the read, write, and execute permissions on directories
and files, and restricts access privileges to user IDs that do not belong to the
primary group of the owner. See, Appendix J, Limited access to directories and
files on page 243.
37
Chapter 2
File structure and behavior changes in HP Output Server 4.1
File structure and behavior changes in

HP Output Server 4.1
With the introduction of the split installation feature, the HP Output Server 4.1
installation files are split into binaries and instance. This results in a change in the folder
structure and a change in the installation and configuration behavior from the earlier
versions. This section lists the main structure and behavior changes in HP Output Server
4.1 when compared to the earlier versions.
Environment variables
A new environment variable, HPOM_INSTALL, is introduced in HP Output Server
4.1 that points to the HP Output Server binaries installation directory in a split
installation. The existing DAZEL_HOME environment variable points to the HP
Output Server instance installation directory in a split installation of HP Output
Server. Both the HPOM_INSTALL and the DAZEL_HOME environment variables
point to the HP Output Server installation directory in a standard installation of HP
Output Server.
File locations in an HP Output Server split installation
38
Installation log files. When you install HP Output Server 4.1 as a split installation,
a setup.log file is created inside the installBinDir for the HP Output Server
binaries installation and a separate setup.log file is created inside the
installInstDir/var/log for the HP Output Server instance installation.
Product version files. When you install HP Output Server 4.1 as a split
installation, the product version file for the HP Output Server binaries installation is
created inside installBinDir/etc/versions/os and the product version file for
the HP Output Server instance installation is created inside
installInstDir/etc/versions/os.
Patch log files. When you install or remove patches on an HP Output Server 4.1
split installation, a patch.log file is created inside the installBinDir for the HP
Output Server binaries patch and another patch.log file is created inside the
installInstDir/var/log for the HP Output Server instance patch.
dzl_version command. When you install HP Output Server 4.1 as a split

installation, the dzl_version command displays the versions of HP Output
Server binaries and instance separately.
Perl files. When you install HP Output Server 4.1, all perlfiles are located inside
$HPOM_INSTALL/bin instead of $DAZEL_HOME/etc in earlier versions of
HP Output Server.
Chapter 2
JBoss
In HP Output Server 4.1, you can choose to install and configure JBoss during the
installation or choose to install and configure JBoss later.
MySQL
MySQL versions. In HP Output Server 4.1, UNIX hosts use the version 5.0.24 of
MySQL and Windows hosts use the version 5.0.91 of MySQL.
dzl_version command. In HP Output Server 4.1, the dzl_version command

does not display the version of installed MySQL.
MySQL binaries. On UNIX, when you install MySQL provided with HP Output
Server 4.1 as the database, the MySQL binaries are installed in the
$HPOM_INSTALL/share/mysql/5.0.24 folder instead of the
$DAZEL_HOME/var/mysql folder in earlier versions of HP Output Server.
On Windows, when you install MySQL provided with HP Output Server as the
database, the MySQL binaries are installed in the
$HPOM_INSTALL/share/mysql/5.0.91 folder and MySQL data is
installed in the $DAZEL_HOME/var/mysql folder.
Upgrading an existing MySQL. If you install HP Output Server 4.1 as a standard

or a split installation on a system where MySQL is already installed in the
$DAZEL_HOME/var/mysql folder, the installation will not upgrade the existing
MySQL. This is because of the change in directory structure in HP Output Server
4.1. The existing MySQL may not be usable after the installation.
Location of the my.cnf file. In HP Output Server 4.1, when you install MySQL
provided with HP Output Server as the backend database, the my.cnf
configuration file is located in $DAZEL_HOME/etc instead of
$DAZEL_HOME/var/mysql in earlier versions of HP Output Server.
Migration and patching

If you install HP Output Server 4.1 as a split installation, and you have different
owners for HP Output Server binaries and instance, you must log in as the root
user to carry out operations such as migration or patching.
HP Output Server
39
Chapter 2
SAPconnect, HP OMS callback, and HP Output Management

for Oracle Applications installations
If you want to install HP Output Server as a server installation on systems where
SAPconnect, HP OMS callback, or HP Output Management for Oracle
Applications are installed, you must install HP Output Server as a standard
installation. A split installation of HP Output Server is not permitted on such
systems.
40
Chapter 2
Installing HP Output Server on UNIX hosts

This section describes how to install HP Output Server on a UNIX host. It assumes that
you have read the information in Chapter 1, Planning the installation on page 1,
Assumptions and restrictions on page 36, and the Release Notes, and that you are
familiar with the system requirements and supported configurations.
Before you install HP Output Server on UNIX hosts

Before you install HP Output Server 4.1 on a UNIX host, you must have the following
Java Runtime Environment (JRE) installed, configured, and running on the machine:
Java SE Runtime Environment 6, update 20 or a higher version on Linux and

Solaris hosts
JRE 6.0 update 8 or a higher version on HP-UX hosts
Java 6.0 SR 8 or a higher version on AIX hosts
You can download the Java Runtime Environment (JRE) for your platform from the
following locations:
Linux and Solaris
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/
CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetailStart?ProductRef=jre-6u20-oth-JPR@CDS-CDS_Developer
HP-UX
http://www.hp.com/go/java
AIX
http://www.ibm.com/developerworks/java/jdk/aix/
service.html
Before you install HP Output Server with Oracle on a UNIX host

Before you install HP Output Server with Oracle as the database server, you must have
Oracle Database 10g Release 2 or Oracle Database 11g Release 2 installed on your
system.
If you try to install a later version of Oracle and Oracle client libraries, the setup script
displays the following warning message:
HP Output Server
41
Chapter 2
WARNING: You specified the <xxx> version of the ORACLE

server which is higher than the recommended ORACLE version
11.02.0000 supported by HP Output Server.
Do you want to enter the database options again? (y/n/q)
-
To re-enter the database options, enter y.
To continue with the installation of HP Output

Server, enter n.
If you want to quit the installation, enter q.
You can choose to enter the database options again, continue with the installation, or
quit the installation.
HP Output Server 4.1 uses the ODBC architecture to communicate with various data
sources. To install HP Output Server 4.1 with Oracle as the database server, you must
have the following:
Oracle ODBC driver provided by Easysoft
Oracle Instant Client libraries provided by Oracle

NOTE: For more information, see Prerequisites for using Oracle as
a backend database server on a UNIX host on page 42.
For UNIX, HP Output Server 4.1 uses UNIX ODBC driver manager, shipped with the
HP Output Server product package, and does not require a separate installation; for
Windows, HP Output Server 4.1 uses the native ODBC driver manager.
NOTE: HP Output Server 4.1 does not support ODBC driver
managers other than the UNIX ODBC driver manager and
the native Windows ODBC driver manager.
Prerequisites for using Oracle as a backend database server on a

UNIX host
To use Oracle as a backend server with an HP Output Server installation on a UNIX
host, your Oracle database administrator must perform the following prerequisite tasks:
1.
42
Create a separate user and grant appropriate privileges to the user.
Chapter 2
While installing HP Output Server, the HP Output Server administrator has the
option of creating the tablespace used by an Oracle user for HP Output Server
(automatically create tablespace). If that option is to be selected during HP Output
Server installation, grant the following privileges to the user:
-
create session
create tablespace
create table
create sequence
alter tablespace
alter session
alter user
drop tablespace
unlimited tablespace
Retain the configuration if you have created a tablespace and assigned it as a

default to the Oracle user for HP Output Server. In this scenario, the following
reduced set of privileges is sufficient:
-
create session
create table
create sequence
alter session
For more information on creating an Oracle user for HP Output Server and granting
privileges, see Appendix H, Prerequisites for installing HP Output Server with
Oracle on page 225.
NOTE: Additionally, grant the create trigger privilege to the
Oracle user for HP Output Server to use HP Output
Distributor.
2.
If the user will not create the tablespace automatically during HP Output Server
installation, create the tablespace, set the quota for the tablespace, and make the
tablespace the default for the user.
For more information on creating the tablespace, see Appendix H, Prerequisites
for installing HP Output Server with Oracle on page 225.
HP Output Server
43
Chapter 2
3.
Configure Oracle parameters as described in Appendix H, Prerequisites for

installing HP Output Server with Oracle on page 225.
4.
Ensure that the hostname of the Oracle database server is resolvable from the
machine where HP Output Server is to be installed.
Typically, on a UNIX host, the Oracle database server hostname and IP address are
entered in the /etc/hosts file.
5.
Download the appropriate Oracle Instant Client libraries.

For more information on downloading the Oracle Instant Client libraries, see
Appendix H, Downloading Oracle 10g and 11g Instant Client libraries
on page 229.
6.
Download the Easysoft ODBC-Oracle Driver.

For more information on downloading the Easysoft ODBC-Oracle Driver, see
Appendix H, Installing Easysoft ODBC-Oracle Driver on page 233.
44
Chapter 2
Installing and configuring HP Output Server on a UNIX host
Installing and configuring HP Output Server on a

UNIX host
This section describes the following installation and configuration options available
when you install HP Output Server on a UNIX host:
Performing an HP Output Server standard installation
Installing and configuring only HP Output Server binaries
Installing and configuring only HP Output Server instance
Performing a client-only installation (UNIX host only)
Performing an HP Output Server standard installation

With the HP Output Server standard installation and configuration option, you can
install HP Output Server in the conventional way with binaries and instance installed at
the same location, or as a split installation with binaries and instance installed at
separate locations. By default, the binaries and instance are installed at the same
location.
You can also choose to install HP Output Server with MySQL Server provided with HP
Output Server or with an existing/remote MySQL or Oracle as the database server.
To install HP Output Server as a standard installation, perform the following tasks:
Task 1. Select the installation components.
Task 2. Specify the directory locations.
Task 3. Specify the JRE location.
Task 4. If you are installing HP Output Server as a root user, specify the owner
and permissions for the installed files.
NOTE: If you are installing HP Output Server as any user other than
the root user, your user ID is set as the owner of the
installed files.
Task 5. Configure the host machine in one of the following ways:
HP Output Server
Create a set of default servers.
Join an existing domain.
Create a new domain.
45
Chapter 2
Task 6. Configure advanced server options (optional).

i.
Configure firewall settings.
ii.
Specify a network interface.
Task 7. Configure the JBoss server ports (optional).

Task 8. Specify one of the following database type:
-
MySQL provided with HP Output Server.
Existing/remote MySQL.
Oracle.
Task 9. Configure the specified database connection.

Task 10. Review the settings and complete the installation.
Task 11. Perform post-installation checks.
Follow the instructions in each tasks to complete the installation.
Task 1: Select the installation components

1.
Log in to the system as the root user or with a valid user ID.
2.
If you are logged in to the system with a root user ID, untar the files. If you are
logged in to the system with a valid user ID other than the root user ID, ask your
system administrator to untar the files.
3.
Change the directory to the location of the setup.pl installation script.

For example, to change to the location of setup.pl installation script for the
hp-ux platform, enter the following command:
cd /hp/hpos/hp-ux
4.
Run the installation script by entering the following command:

./perl setup.pl
The following configuration options appear:
1. Install HP Output Management product components.
2. Uninstall HP Output Management product components.
5.
Accept the default [1].

The following HP Output Management packages appear:
1. HP Output Server
2. HP Output Server Client only
46
Chapter 2
6.

The following installation types appear:
1. HP Output Server standard installation.
2. HP Output Server binaries installation only.
3. HP Output Server instance Installation only.
7.
Task 2: Specify the directory locations

While specifying the installation directory paths and the directory names, keep in mind
the following:
The file path to the installation directory must be an absolute path that begins with
the / character.
The file path must not point to the root directory.
The file path must not contain embedded spaces, tabs, or the *, ?, , , and
'characters.
Directory names can include letters (A-Z and a-z), numbers (0-9), underscores (_),
and dashes (-).
Do not begin a directory name with a dash (-).
To specify the directory locations, perform the following tasks:

1.
Specify the installation path for HP Output Server binaries.

The default installation path is /opt/hpom.
NOTE: By default, the binaries and instance will be installed in the
same directory. If you want to have a split installation, you
must provide different paths for the binaries and instance.
NOTE: If the binaries and instance are installed in the same
directory, you cannot split the installation later. However,
you can use any other binaries from other split installations
with that instance.
HP Output Server
47
Chapter 2
NOTE: If the installation directory that you specified does not exist,
the setup script prompts whether to create the specified
directory. If the directory creation fails, the setup script
prompts you for the installation path again. If the installation
directory exists and is not empty, the setup script warns you
about the existing files and prompts whether to continue or
select a new or empty directory.
2.
Specify the installation path for HP Output Server instance.

The default installation path is installBinDir.
NOTE: If you want to have a split installation, you must provide a
different path for the instance.
3.
Specify the location where you want to create the HP Output Server Log files.
The default log file path is installInstDir/var/log.
Task 3: Specify the JRE location

Specify the path where the Java Runtime Environment (JRE) is installed.
NOTE: You must have the appropriate JRE version installed,
configured, and running on the machine where you want to
install HP Output Server 4.1. For more details, refer to
Before you install HP Output Server on UNIX
hosts on page 41.
Task 4: Specify the owner and file permissions for the installed files
1.
48
If you are a root user, the setup prompts you for the name of the user who will
own the installed files. Accept the default, or enter the name of the user. The owner
of the installed files must be a valid user in the system on which HP Output Server
is installed.
Chapter 2
The default user is hposadm.

NOTE: If you specify a NIS user as the owner of the installed files,
other local operating system users such as root cannot
perform HP Output Management operations such as
start_server, stop_server, config_server,
and server_status.
If you are installing HP Output Server as any user other than the root user, the
setup script does not prompt you to specify the owner of the installed files. Your
user ID is set as the owner of the installed files.
2.
Specify whether you want to restrict access to server binaries to other users.
The default option is n.
-
If you select n, the permission for server binaries is set as rwxr-xr-x

(755).
If you select y, the permission for server binaries is set as rwxr-x--(750).
Task 5: Configure the host machine

1.
Specify whether you want to create a set of default servers or join an existing
domain. The following options appear:
1. Yes. Create the primary servers and one default
server for each delivery server.
2. No. Join an existing domain or create the servers
later.
-
Accept the default 1 to create the primary servers.

Proceed to the instructions in Creating a set of default servers on a UNIX
host on page 50.
Enter 2 to join an existing HP Output Server domain or create a new domain

on the system.
Proceed to step 2.
2.
Specify whether you want to join an existing HP Output Server domain or create a
new domain on the system. The following options appear:
1. Join a domain.
2. create a new domain.
-
HP Output Server
Accept the default 1 to join an existing domain.
49
Chapter 2
Proceed to the instructions in Joining an existing domain on a UNIX

host on page 50.
-
Enter 2 to create a new domain on the system.

Proceed to the instructions in Creating a new domain on a UNIX
host on page 52.
Creating a set of default servers on a UNIX host

1.
Enter the name of the HP Output Server domain.

The domain name is not the same as the network domain name. The default domain
name is hostname.d.
Keep in mind the following restrictions when specifying an HP Output Server
domain name:
2.
The first character must be a letter (a through z or A through Z).
After the first character, domain names can contain any combination of letters
(a-z or A-Z), dashes (-), underscores (_), periods (.), or numbers.
The domain name must not contain embedded spaces.
Only standard 7-bit ASCII characters are allowed. Extended 8-bit ASCII
characters, for example , are not allowed in any position.
Enter the port number to which the HP Output Server Name Space Manager (NM)
will listen.
The default is 4009.
Proceed to the instructions in Task 6: Configure advanced server options

(optional) on page 53.
Joining an existing domain on a UNIX host

The Join a domain option adds the new installation of HP Output Server to an existing
HP Output Server domain. This configuration option distributes HP Output Server
delivery servers among multiple hosts within an existing HP Output Server domain.
Joining an existing domain includes the same tasks as creating a server installation of
HP Output Server with the following exceptions:
50
When specifying information to configure the host machine, you specify an

existing HP Output Server domain.
Chapter 2
If you choose to install HP Output Server installation with integrated MySQL

as the database server, this option will create the MySQL and JBoss servers
and all the MySQL database server prompts are prompted during the HP
Output Server installation.
If you choose to install HP Output Server installation with remote/existing

database server, you have the option of configuring the database server during
the installation or after the HP Output Server installation. Use this option to
distribute HP Output Server delivery servers among multiple hosts.
NOTE: If you choose to configure the database connection after
installation, you must configure the database connection
before creating any HP Output Server servers. For more
information, see Appendix C, Configuring the database
connection on UNIX hosts on page 203. After you
complete the installation, use the config_server
command to create delivery servers on the new host. For
more information about using the config_server
command, see the System Administrators Command
NOTE: You can configure the database connection during the
installation process or after completing the installation. If
you configure the database connection during the installation
process, the setup script returns an error if your database
server is not running but allows you to continue with the
installation process.
To join an existing domain, perform the following steps:
HP Output Server
1.
When the setup prompts for the HP Output Server host name, enter the host name
or IP address of the primary host machine of the existing HP Output Server domain
to which you are joining this host. The primary host machine is the machine to
which the NM server in the existing HP Output Server domain is listening.
2.
When the setup prompts for the HP Output Server domain name, enter the HP
Output Server domain name of the primary host. The setup script does not provide
a default value.
3.
When the setup prompts for the port number to which HP Output Server NM is
listening, accept the default or enter the port number. The default is 4009.
51
Chapter 2
HP Output Server can use any valid TCP port that is not being used by another
application. Because ports 1 through 1023 on most systems can be used only by
system or root processes, you can select a port number in the range 1 through 1023
only if you specified root as the owner of the installed files in the previous task.
You can select a port number in the range 1024 through 65535 if you specified any
user as the owner of the installed files.
NOTE: For successful job delivery across inter-domain systems
located in different locations with firewall on the systems,
you must manually enable the used ports or contact your
system administrator to enable the used ports on both the
machines. Execute the nmcp list command to obtain a
list of ports used after installing HP Output Server. For more
information on executing the nmcp list command, see
HP Output Server System Administrators Command
Reference.
4.
When the setup prompts you to configure the database connection, do one of the
following:
-
To configure the database connection, accept the default y.
To skip this step, enter n.

If you skip this step, you must configure the database connection before
creating any HP Output Server servers. For more information, see Appendix C,
Configuring the database connection on UNIX hosts on page 203.

Creating a new domain on a UNIX host

The Create a new domain option configures the host for a new HP Output Server
domain, but does not create any servers. If you choose this option, you must manually
configure HP Output Server servers with the config_server command after
completing the installation. For more information about using the config_server
command, see the System Administrators Command Reference for HP Output Server.
Creating a new domain includes the same tasks as creating a server installation of HP
Output Server with the following exceptions:
52
When providing information to configure the host machine, you specify an HP

Output Server domain name and a port number. The setup script configures the host
with this information, but does not create any HP Output Server servers.
Chapter 2
You can configure the database connection during the installation process or after
completing the installation. If you configure the database connection during the
installation process, the setup script returns an error if your database server is not
running, but allows you to continue with the installation process.
Use the following instructions to create a new domain:

1.
When the setup prompts you for the HP Output Server domain name, enter the HP
Output Server domain name of the primary host.
2.
When the setup prompts you for the port number to which HP Output Server NM is
listening, accept the default or enter the port number. The default is 4009.
3.
When the setup prompts you to configure the database connection, do one of the
following:
-
To configure the database connection, accept the default y.
To skip this step, enter n.

If you skip this step, you must configure the database connection before

Task 6: Configure advanced server options (optional)

The setup script enables you to configure HP Output Server processes to use a specific
set of ports and network interfaces. For more information about these options, see
Appendix D, Firewall support on page 209 and Appendix E, HP Output Server in a
multi-NIC environment on page 213.
When the setup prompts whether to configure the advanced server options, do one of the
following:
If you do not want to configure the advanced server options, accept the default n.
When the setup prompts whether to start the HP Output Server servers after
completing the installation, do one of the following:
HP Output Server
If you want the setup script to start the HP Output Server servers when the
installation is finished, accept the default y.
If you do not want the setup script to start the HP Output Server servers when
the installation is finished, enter n.
To configure advanced server options, enter y.
53
Chapter 2
Proceed with the installation by using the instructions in the following section,
Configuring firewall support.
Configuring firewall support

1.
When the setup prompts whether to enable firewall support, do one of the
following:
-
To skip this step, accept the default n.

Proceed with the installation using the instructions in Specifying a network
interface on page 55.
To enable firewall support, enter y.

Proceed to the instructions in step 2.
2.
When the setup prompts you for a list of port numbers or ranges of port numbers for
firewall support, enter the port numbers separated by commas, or ranges of port
numbers separated by dashes. Only numeric characters, the comma, and the dash
are allowed.
For example:
4000-4100,4102,4104-4199
If you are installing HP Output Server as a root user, you can select one or more
port numbers in the range 1 through 65535. If you are installing HP Output Server
as a user other than the root user, you can select one or more port numbers in the
range 1024 through 65535.
NOTE: Because each HP Output Server server requires a minimum
of one port, you must enter at least eight port numbers. If you
want to create more servers later, you must provide an equal
number of ports. The setup program does not provide default
values and does not check the ports that you specify for
availability.
54
Chapter 2
NOTE: For successful job delivery across inter-domain systems

located in different locations with firewall on the systems,
you must manually enable the used ports or contact your
system administrator to enable the used ports on both the
machines. Execute the nmcp list command to obtain a
list of ports used after installing HP Output Server. For more
information on executing the nmcp list command, see
HP Output Server System Administrators Command
Reference.
Specifying a network interface

1.
When the setup prompts whether to restrict HP Output Server processes to use a
specific network interface, do one of the following:
-
To skip this step, accept the default n.
When the setup prompts whether to start the HP Output Server servers when the
installation is finished, do one of the following:
To restrict HP Output Server processes from using a specific network interface,

enter y.
When the setup prompts you for the host name or IP address of the network
interface, enter the host name or IP address.
When the setup prompts whether to start the HP Output Server servers when the
installation is finished, do one of the following:
-
Task 7: Configure the JBoss server ports

1.
HP Output Server
When the setup prompts whether to configure the JBoss server at the end of the
installation, do one of the following:
55
Chapter 2
If you want to configure the JBoss servers at the end of the installation, accept
the default y.
Proceed to step 2.
If you do not want to configure the JBoss servers at the end of the installation,
enter n.
Skip step 2 and proceed to Task 8: Specify the database type.
NOTE: If you want to configure the JBoss server after you install
HP Output Server, run the cd $HPOM_INSTALL
command, and then run the config_host -u -x
-application-server-port 9000-9016
command, and then run the config_server -t jboss
command.
If you want to configure HP Output Management Web
Console, run the perl jmconfig.pl -i -p 9000
script.
NOTE: While restarting the JBoss server using the stop_server
and start_server commands, make sure that all the
JBoss related processes are stopped before issuing the
start_server jboss or the
start_server -t all command.
2.
Specify 17 port numbers for JBoss server configuration. Accept the default port
numbers or enter 17 port numbers in the range 1024 through 65535.
NOTE: Port numbers must be separated by commas or specified as a
range.
For example:
9000, 9001, 9002-9016
Task 8: Specify the database type

Select the type of database that you want to use from the following:
1. MySQL
2. Oracle
The default selection is 1.
56
Chapter 2
If you select MySQL as the database type, the following message appears:
Do you want to configure and use the MySQL provided
with HP Output Server (y/n)?
-
If you want to configure MySQL that is provided with HP Output Server, enter
y.
Proceed with the installation using the instructions in Configuring MySQL
provided with HP Output Server on page 57.
If you want to configure an existing or remote MySQL database, select n.

Proceed with the installation using the instructions in Configuring an
existing/remote MySQL with HP Output Server on page 59.
If you select Oracle as the database type, proceed with the installation using the
instructions in Configuring the Oracle database connection on page 61.
Task 9: Configure the database connection

Based on the database type that you selected, you must configure either the MySQL or
Oracle database connection.
Configuring MySQL provided with HP Output Server

To configure MySQL provided with HP Output Server, perform the following steps:
NOTE: This is the default installation option. If you choose this
option, HP Output Server is installed at the location
specified in Task 2: Specify the directory locations and
MySQL database server is installed at the location,
installInstDir/var/mysql by default.
1.
Enter a password for the MySQL database server.

NOTE: Do not use a password that starts with the word edit for the
MySQL database server or your HP Output Server
installation might not be successful.
HP Output Server
2.
Re-enter the password to verify it.
3.
Enter the database size in megabytes or gigabytes.
57
Chapter 2
The default size of the ibdata file during MySQL for HP Output Management
installation is 100 MB.
NOTE: If ibdata file is not set to the proper value, you may
encounter disk write performance issues, disk fragmentation
issues, and unexpected growth, which can result in database
crash leading to unrecoverable setup. For more information
on calculating the recommended size of the ibdata file,
see Appendix N, Tuning MySQL for HP Output Server
on page 271.
4.
Enter the extent size.

The extent size should be at least 50% of the size of the ibdata file. If you enter a
size that is less than 50% of the size of the ibdata file, an error message appears.
NOTE: For more information on how to configure MySQL database
server to grant access to HP Output Management programs
on remote hosts and how to adjust variables to optimize
database performance with HP Output Server, see Appendix
M, Configuring MySQL for HP Output Management
on page 263.
NOTE: By default the MySQL database server tuning parameters are
set to certain default values in the my.cnf file. For
instructions on customized tuning of the MySQL database
server, see, Appendix N, Tuning MySQL for HP Output
Server on page 271.
5.
Enter the port number to which MySQL is listening.

The default port number is 3306.
Proceed to Task 10: Review the settings and complete the installation on page 63.
58
Chapter 2
Configuring an existing/remote MySQL with HP Output Server

To configure an existing/remote MySQL with HP Output Server, perform the following
steps:
NOTE: Before configuring the MySQL database connection, ensure
that both the user installing HP Output Server and owner of
the MySQL database server belong to the same group and
have the same privilege.
1.
Enter the user name of the MySQL database if you logged in as a root user.
If you are installing HP Output Server as any other user other than the root user,
you are not prompted to specify the user name of the MySQL database.
NOTE: The MySQL database user name can contain only simple
ASCII characters and must not exceed 30 characters. Do not
use accented characters, single or double quotes, spaces,
backslashes, accent graves, commas, or special symbols.
2.
Enter the password of the MySQL database user.

3.
Re-enter the password to verify it.
4.
Select the MySQL connection mode that HP Output Server will use to connect to
your MySQL database server. The following options appear:
1. File socket. Required for connecting to MySQL on
this host.
2. Port. Required for connecting to MySQL on another
host.
-
If your connection type is File socket, accept the default 1.

When the setup prompts you for the path to the MySQL file socket, accept the
default or enter the absolute path.
The default path is installInstDir/var/mysql/mysql.sock. If you are
connecting to a MySQL server on the local host, you must use the file socket.
HP Output Server
If your connection type is Port, enter 2.
59
Chapter 2
i.
Enter the host name or IP address where the MySQL database server is
running.
The setup script does not provide a default value.
ii.
Enter the port number to which MySQL is listening.

The default value is 3306.
NOTE: Ensure that the specified MySQL port is enabled.
5.
Enter the MySQL database prefix name

The default is hpomdb.
The MySQL database prefix name will be used to create the database name. The
database name used by HP Output Server will be a combination of prefix name,
domain, and port. The MySQL database name will be created in the following
format:
<prefix name>_<domain>_<port>
For example, if the prefix name is hpomdb, the domain hpos.d, and the port
number 4009, the database name would be hpomdb_hpos_d_4009.
NOTE: Only alphanumeric characters and underscores are allowed
in the prefix name. Begin the prefix name with a letter.
NOTE: By default, the MySQL user for HP Output Server has the
permissions to create and modify databases. The
-database-name-prefix host attribute is set to the
value of MySQL database prefix name entered by the user.
6.
Specify whether you want the HP Output Server to automatically create the
database.
-
If you want the HP Output Server to automatically create the database, accept
the default y.
Proceed with the installation using the instructions in Task 10: Review the
settings and complete the installation on page 63.
60
If you do not want HP Output Server to automatically create the database, enter
n.
Chapter 2
If the database exists, you can proceed with the installation by using the
instructions in the section titled Task 10: Review the settings and complete the
installation on page 63.
If the database does not exist, a warning message, asking whether you want to
continue with the installation is displayed. You must provide a valid database
name or allow HP Output Server to create the database automatically.
Configuring the Oracle database connection

To configure the Oracle database connection, perform the following steps:
1.
When the setup prompts for a user name that HP Output Server will use to connect
to the Oracle database server, accept the default hposadm or enter a user name.
2.
Enter the password for the user that HP Output Server will use to connect to Oracle.
When the setup prompts you to verify the password, re-enter it.
3.
Select the type of connection identifier to connect to Oracle database from the
following options:
1) Oracle System Identifier (SID)
2) Net Service Name (TNS Name)
-
If you select the default Oracle System Identifier (SID), perform

the following steps:
i.
Enter the name or IP address of the host where Oracle database is running.
The default is localhost.
ii.
When prompted for the port number to which Oracle is listening, accept the
default 1521 or enter a port number.
iii. Enter the service name for Oracle.

The default value is ORCL.
-
If you select Net Service Name (TNS Name), perform the following
steps:
i.
Enter the Net Service Name (TNS Name)

The default value is ORCL.
ii.
4.
HP Output Server
Enter the path of local/client tnsnames.ora file.
Enter the path of the installed Oracle Instant Client libraries.
61
Chapter 2
The default path is $DAZEL_HOME/var/oracle_client_library.

NOTE: If you downloaded the Oracle Instant Client libraries to
$DAZEL_HOME/var/oracle_client_library
/lib directory, provide the path as
$DAZEL_HOME/var/oracle_client_library.
5.
Enter the path of the Easysoft ODBC-Oracle driver installation.

The default path is $DAZEL_HOME/var/easysoft.
NOTE: For more information on installing Easysoft ODBC-Oracle
Driver, see Appendix H, Prerequisites for installing HP
Output Server with Oracle on page 225.
6.
Enter the Oracle tablespace prefix name.

The Oracle tablespace prefix name will be used to create the tablespace name. The
tablespace name used by HP Output Server will be the combination of prefix name,
domain, and port in the following format:
number 4009, the tablespace name would be hpomdb_hpos_d_4009.
7.
Specify whether you want HP Output Server to automatically create the tablespace.
-
If you want HP Output Server to automatically create the tablespace, accept the
default y.
Proceed with the installation using the instructions in Task 10: Review the
settings and complete the installation on page 63.
62
Chapter 2
If you want HP Output Server to automatically create the tablespace, the

Oracle user for HP Output Server must have the required privileges. For more
information, see Prerequisites for using Oracle as a backend database server
on a UNIX host on page 42.
NOTE: If you choose to automatically create a tablespace, ensure
that you retain the alter user privilege for the HP Output
Server user. This is required for the normal operation of HP
Output Server.
-
If you do not want HP Output Server to automatically create the tablespace,

enter n.
If the tablespace exists, you can proceed with the installation by using the
instructions in Task 10: Review the settings and complete the
installation on page 63.
If the tablespace does not exist, a warning message, asking whether you want to
continue the installation, is displayed.
NOTE: The Oracle database administrator must create a tablespace,
assign a quota for the tablespace, and set the tablespace as
the default tablespace for the HP Output Server user. The
Oracle user for HP Output Server must be granted these
privileges: create session, alter session,
create table, and create sequence.
NOTE: If you choose not to create the tablespace automatically, you
do not need the alter user privilege.
Task 10: Review the settings and complete the installation

1.
When you complete all previous tasks, the setup script displays your server
configuration settings and prompts you to accept the settings (y), change the
settings (n), or quit the program (q).
-
HP Output Server
If the configuration settings are correct and you want to continue with the
installation, accept the default Y.
63
Chapter 2
The setup script displays the installation progress and notifies you when the
installation is complete. If the installation is successful, the following message
appears:
The setup log file is located at
installInstDir/var/log/setup.log
-
If you want to change any configuration settings, enter n.

The setup script returns to the beginning of the program and displays your
current selections for each prompt. Change any setting that is incorrect at the
corresponding prompt.
2.
After the installation of HP Output Server on UNIX is complete, source your

environment variables by entering one of the following commands, depending on
your shell:
Shell
Command
source installInstDir/etc/setup_env.csh
Bourne or Korn
. installInstDir/etc/setup_env.sh
NOTE: You can change the log level of HP Output Management

product deployed components such as HP Web Services for
Output Server, UPD Gateway, and HP Output Management
Web Console by changing the priority value in the
jboss-log4j.xml log file located at
installInstDir/var/jboss/server/default/conf
directory. The priority value can be set to one of the
following: INFO, DEBUG, ERROR, and TRACE.
NOTE: To use Secure File Transfer Protocol (SFTP), you must
install Open SSL. For more information, see Appendix K,
Installing OpenSSL on page 245.
Task 11: Perform post-installation checks

If you selected Join a domain or Create a new domain option during the installation
process in Task 5: Configure the host machine on page 49, remember to perform the
following after the installation process.
64
Chapter 2
Post-installation reminders (Join a domain)

After you complete the installation process, remember to do the following:
Use the config_server command to create delivery servers on the host

machine that you joined to the domain. For more information about using the
config_server command, see the System Administrators Command Reference
for HP Output Server.
NOTE: A wait time of 90 seconds is recommended before recreating
the JBoss server using the config_server command.
If you want to configure HP Output Management Web Console, run the

perl jmconfig.pl -i -p 9000 script.
Post-installation reminders (Create a new domain)

After you complete the installation process, remember to do the following:
If you did not configure the database connection when installing HP Output Server
by creating a new domain, you must configure the database connection before
Use the config_server command to create HP Output Server servers on the

host machine. For more information about using the config_server command,
see the System Administrators Command Reference for HP Output Server.
NOTE: A wait time of 90 seconds is recommended before recreating
the JBoss server using the config_server command.
Installing and configuring only the HP Output Server binaries

With the HP Output Server binaries installation only option, you can install only the
server binaries without installing the instance.
To install only the HP Output Server binaries, perform the following tasks:
HP Output Server
65
Chapter 2
Task 3. If you are installing HP Output Server as a root user, specify the owner
and permissions for the installed files.
installed files.

1.
2.
3.

cd /hp/hpos/hp-ux
4.

./perl setup.pl
If the setup script does not detect an existing HP Output Server server installation,
the default selection is 1.
5.
Accept the default selection 1.

1. HP Output Server
6.
66
Chapter 2

7.
Select option [2].
Task 2: Specify a directory location

1.
Specify the installation path for HP Output Server binaries.

The default installation path is /opt/hpom/binaries.
If the installation directory does not exist, the setup script prompts whether to
create the specified directory. If the installation directory exists and is not empty,
the setup script warns of the existing files and prompts for a decision to continue or
NOTE: The file path to the installation directory must be an absolute
path that begins with the / character. The file path cannot be
the root directory, and it cannot contain embedded spaces,
tabs, or any of the following characters: *, ?, , , and '.
Directory names can include letters (A-Z and a-z), numbers
(0-9), underscores (_), and dashes (-). Do not begin a
directory name with a dash (-).
NOTE: If the script is unable to detect the presence of the directory
that you specify, it tries to create the directory for you. If the
directory creation fails, you are prompted for the installation
path again.
HP Output Server
67
Chapter 2
Task 3: Specify the owner and file permissions for the installed files
1.
If you have logged in as a root user, the setup prompts you for the name of the
user who will own the installed files. Accept the default, or enter the name of the
user. The owner of the installed files must be a valid user in the system on which
HP Output Server is installed.
perform HP Output Management operations like
and server_status.
2.
Specify whether you want to restrict access to server binaries to other users.
-
If you select n, the permissions for server binaries is set as rwxr-xr-x

(755).
If you select y, the permissions for server binaries is set as rwxr-x--(750).

When you complete all previous tasks, the setup script displays your server
configuration settings and prompts you to accept the settings (y), change the settings
(n), or quit the program (q).
-
installation, accept the default (y).
The setup script displays the progress and notifies you when the installation is
complete. If the installation is successful, the following message appears:
The setup log file is located at installBinDir/setup.log

current selection for each prompt. Change any setting that is incorrect at the
corresponding prompt.
68
Chapter 2
Installing and configuring only the HP Output Server instance

With the HP Output Server instance installation only option, you can install only the
HP Output Server instance without installing the HP Output Server 4.1 binaries.
However, you must have any pre-installed HP Output Server 4.1 binaries that the
instance can use. You can point to the binaries from any HP Output Server split
installation that you want the particular instance to use.
To install only the HP Output Server instance, perform the following tasks:
Task 4. If you are installing HP Output Server as a root user, specify the owner of
the installed files.
installed files.
-

i.
ii.

Task 8. Specify one of the following database type:
-
MySQL provided with HP Output Server.
Oracle.

HP Output Server
69
Chapter 2

1.
NOTE: The owner of the HP Output Server instance must belong to
the same user group as the owner of the HP Output Server
binaries that you want to use and must have the read and
execute permissions on the HP Output Server binaries.
2.
3.

cd /hp/hpos/hp-ux
4.

./perl setup.pl
If the setup script does not detect an existing HP Output Server server installation,
the default selection is 1.
5.

1. HP Output Server
6.

7.
70
Enter 3.
Chapter 2

While specifying the installation directory paths and the directory names, keep in mind
the following:
The file path to the installation directory must be an absolute path that begins with
the / character.
The file path must not point to the root directory.
The file path must not contain embedded spaces, tabs, or the *, ?, , , and
'characters.
Directory names can include letters (A-Z and a-z), numbers (0-9), underscores (_),
and dashes (-).
Do not begin a directory name with a dash (-).
To specify the directory locations, perform the following steps:

1.
Specify the installation path for HP Output Server instance.

The default installation path is /opt/hpom/instance.
2.
Specify the installation path where you have installed the binaries that you want to
use.
The default path is /opt/hpom/binaries.
3.
Specify the location where you want to create the HP Output Server Log files.
The default log file path is installInstDir/var/log.

Specify the path where the Java Runtime Environment (JRE) is installed.
NOTE: You must have the appropriate JRE version installed,
configured, and running on the machine where you want to
install HP Output Server 4.1. For more details, refer to
Before you install HP Output Server on UNIX
hosts on page 41.
Task 4: Specify the owner of the installed files

1.
HP Output Server
If you are a root user, you are prompted for the name of the user who will own the
installed files. Accept the default, or enter the name of the user. The owner of the
installed files must be a valid user in the system on which HP Output Server is
installed.
71
Chapter 2
The default user is hposadm.

perform HP Output Management operations like
and server_status.
Refer to Performing an HP Output Server standard installation on page 45 and
complete Task 5 through Task 11 to complete the installation.
Performing a client-only installation (UNIX host only)

On a UNIX system, you can also install HP Output Server as a client-only installation.
This configuration option joins the local machine to an existing HP Output Server
domain without configuring HP Output Server servers on the machine. This option
allows jobs to be submitted and monitored by a machine other than the server host.
NOTE: You can create a client-only installation of HP Output Server
on a UNIX host only.
To install HP Output Server as a client-only installation, perform the following tasks:
Task 3. If you are installing HP Output Server as a root user, specify the owner of
the installed files.
root user, your user ID is set as the owner of the installed
files.
Task 4. Configure the host machine.
72
Chapter 2

1.
2.
3.
Change the directories to the location of the setup.pl installation script.

cd /hp/hpos/hp-ux
4.

./perl setup.pl
5.
Accept the default selection 1.

Setup displays the following available HP Output Management packages:
1. HP Output Server
6.
Select option [2].

1.
HP Output Server
When the setup prompts for the installation path for HP Output Server client,
accept the default path or enter a new installation path.
73
Chapter 2
The default installation path is /opt/hpom.

NOTE: If the installation directory that you specified does not exist,
the setup script prompts whether to create the specified
directory. If the directory creation fails, the setup script
prompts you for the installation path again. If the installation
directory exists and is not empty, the setup script warns you
about the existing files and prompts whether to continue or
NOTE: The file path to the installation directory must be an absolute
path that begins with the / character. The file path cannot be
the root directory, and it cannot contain embedded spaces,
tabs, or any of the following characters: *, ?, , , and '.
NOTE: Note: Directory names can include letters (A-Z and a-z),
numbers (0-9), underscores (_), and dashes (-). Do not begin
a directory name with a dash (-).
Task 3: Specify the owner of the installed files

1.
If you have logged in as a root user, the setup prompts you for the name of the
user who will own the installed files. Accept the default, or enter the name of the
user. The owner of the installed files must be a valid user in the system on which
HP Output Server is installed.
perform HP Output Management operations such as
and server_status.
74
Chapter 2

1.
When the setup prompts you for the HP Output Server host name, enter the name of
the primary host machine of the existing HP Output Server domain.
The primary host machine is the machine to which the NM server in the existing
HP Output Server domain is listening.
2.
When the setup prompts you for the HP Output Server domain name, enter the HP
Output Server domain name of the primary host.
The setup script does not provide a default value.
The domain name is not the same as the network domain name. The default domain
name is hostname.d.
Observe the following restrictions when specifying an HP Output Server domain
name:
3.
The first character must be a letter (a through z or A through Z).
After the first character, domain names can contain any combination of the
following: letters (a through z or A through Z), dashes (-), underscores (_)
periods (.), and numbers.
The domain name cannot contain embedded spaces.
Only standard 7-bit ASCII characters are allowed. Extended 8-bit ASCII
characters, for example , are not allowed in any position.
Enter the port number to which the HP Output Server Name Space Manager (NM)
will listen.

1.
When you complete all previous installation steps, the setup script displays your
configuration settings and prompts you to accept the settings (y), change the
settings (n), or quit the program (q).
-
HP Output Server
installation, accept the default y.
75
Chapter 2
The setup script displays the setup progress and notifies you when the
installation is complete. If the installation is successful, the following message
appears:
HP Output Server 4.1 client successfully installed
and configured.
The setup log file is located at
installInstDir/var/log/setup.log.
-

current selection for each prompt. When prompted, change any setting that is
incorrect.
2.
Source your environment variables by entering one of the following commands,

depending on your shell:
Shell
Command
Bourne or Korn

NOTE: To perform operations like creating a delivery pathway, you
must set suitable permission on the UNIX server using the
pm_edit command. For more information on pm_edit
command, see HP Output Server System Administrators
Command Reference.
76
Chapter 2
Installing HP Output Server on Windows hosts

This section describes how to install HP Output Server on a Windows host. It assumes
that you have read the information in Chapter 1, Planning the installation on page 1
and the Release Notes, and that you are familiar with the system requirements and
supported configurations.
Before you install HP Output Server on a Windows host

Before you install HP Output Server 4.1 on a Windows host, you must have Java SE
Runtime Environment 6, update 20 or a higher version installed, configured, and
running on the machine. You can download Java SE Runtime Environment 6 from the
following location:
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_
Developer-Site/en_US/-/USD/ViewProductDetail-Start?
ProductRef=jre-6u20-oth-JPR@CDS-CDS_Developer
Before you install HP Output Server with Oracle on a Windows

host
Before you install HP Output Server with Oracle as the database server, you must have
Oracle Database 10g Release 2 or Oracle Database 11g Release 2 installed on your
system.
HP Output Server 4.1 uses the ODBC architecture to communicate with various data
sources. To install HP Output Server 4.1 with Oracle as the database server, you must
have:
Oracle ODBC drivers provided by Oracle
Oracle Instant Client libraries provided by Oracle

NOTE: For more information, see Prerequisites for using Oracle as
a backend database server on a Windows host on page 78.
HP Output Server
77
Chapter 2
For UNIX, HP Output Server 4.1 uses UNIX ODBC driver manager, shipped with the
HP Output Server, and does not require a separate installation; for Windows, HP Output
Server 4.1 uses the Native ODBC driver manager.
NOTE: HP Output Server 4.1 does not support ODBC driver
managers other than the UNIX ODBC driver manager and
the native Windows ODBC driver manager.
Prerequisites for using Oracle as a backend database server on a

Windows host
To use Oracle as a backend server with an HP Output Server installation on a Windows
host, you and your Oracle database administrator must perform the following
prerequisite tasks:
1.
Complete steps 1 through 3 in Prerequisites for using Oracle as a backend

database server on a UNIX host on page 42.
2.
Download the appropriate Oracle Instant Client libraries.

For more information on downloading the Oracle Instant Client libraries, see
Appendix H, Prerequisites for installing HP Output Server with Oracle
on page 225.
3.
Download the latest Oracle ODBC driver for Windows from the following Web
site:
http://www.oracle.com/technetwork/topics/winx64soft-089
540.html
NOTE: For Oracle Database 10g, HP recommends that you use the
Oracle Instant Client libraries and Oracle ODBC driver
version 10.2.0.3.0 on Windows 2003 R2 and Oracle Instant
Client libraries and Oracle ODBC driver version 10.2.0.5 on
Windows 2008 R2.
NOTE: You must create a lib folder under any location on your
system and download both the Oracle Instant Client libraries
and the Oracle ODBC driver for Windows to the lib folder.
If the downloaded Oracle ODBC driver for Windows is in a compressed format,
use an appropriate tool to extract the required files.
78
Chapter 2
HP Output Server server installation options on a Windows host

On a Windows host, you can perform only a standard server installation. A split
installation of HP Output Server is not supported on Windows. You can choose to install
MySQL Server provided with HP Output Server or you can install HP Output Server
with an existing/remote MySQL or Oracle as the database server. HP Output Server 4.1
provides the following component-based installation options on Windows hosts:
MySQL provided with HP Output Server

You can choose this option to install HP Output Server with MySQL provided in
the package. HP recommends you to use this option for HP Output Server
installation.
HP Output Server with existing/remote MySQL or Oracle as the database

server
This option allows you to use the existing/remote MySQL 5.0.91 or Oracle
database server for HP Output Server installation. It creates an HP Output Server
domain on a Windows host and configures the host machine to create all primary
servers (SSM, NM, PM, AIM, CM, and EM) and one of each delivery server
(DLM, JQM, and DSM).
Creating a set of default servers on a Windows host

This installation and configuration option creates an HP Output Server domain. It
configures the host machine and creates all primary servers (SSM, NM, PM, AIM,
CM, and EM) and one of each delivery server (DLM, JQM, and DSM).
Joining an existing domain on a Windows host

Joining an existing domain is an installation option that joins an installation of HP
Output Server to an existing HP Output Server domain. This results in a
multiple-host domain configuration by distributing HP Output Server delivery
servers among multiple hosts within an existing HP Output Server domain.
Joining an existing domain is similar to creating a default server installation of HP
Output Server on a Windows host with the following exceptions:
-
HP Output Server
When configuring the host machine, you specify an existing HP Output Server
domain. The setup program configures the host to join the existing domain, but
does not create any HP Output Server servers. After you complete the
installation process, you must use the config_server command to create
an SSM server and delivery servers on the host machine that you joined to the
domain. For more information about using the config_server command,
79
Chapter 2
If you configure the database connection during the installation process, the
setup program displays a warning message if your database server is not
running, but allows you to continue with the installation process.
Creating a new domain without a default set of servers on a Windows host

Creating a new domain on a Windows host is an installation option in which the
setup program configures the host for a new HP Output Server domain, but does
not create any servers. If you choose this option, you must manually configure HP
Output Server servers with the config_server command after completing the
installation. For more information about using the config_server command,
Creating a new domain is similar to creating a set of default servers with the
following exceptions:
-
The setup program configures the host for a new HP Output Server domain,
but does not create any HP Output Server servers. After you complete the
installation process, you must use the config_server command to create
HP Output Server servers.
If you configure the database connection during the installation process and
your database server is not running, the setup program displays a warning, but
allows you to continue with the installation process.
Installing and configuring HP Output Server on a Windows host

To install HP Output Server on a Windows host, perform the following tasks:
Task 1. Specify a directory location.
-

i.
ii.

Task 6. Specify the database type from the following.
-
80
Integrated MySQL.
Chapter 2
Oracle.

Task 8. Review the server configuration settings.
Task 9. Verify that SSM is running
Task 1: Specify a directory location

1.
Log in as a user with administrator privileges and check for the required
permissions. For more information about required permissions, see Setting
permissions on page 28.
2.
Navigate to the win64/hpos folder, and double-click Setup.exe.
3.
In the Welcome to the HP Output Server Setup Wizard window, click Next.
4.
In the Destination Location window, specify the destination folder for installing
HP Output Server by doing one of the following:
-
Click Next to accept the default location. The default destination folder is
C:\HP\OM.
Click Browse, select the required folder, and then click Next.
NOTE: The path name for the destination folder must not contain
embedded spaces, tabs, or any of the following characters:
*, ?, , , ', and %.
For example, you cannot install HP Output Server in
C:\Program Files.
HP Output Server
81
Chapter 2

1.
In the JRE Location window, click Browse, and then select the folder where you
have installed JRE.
NOTE: You must have Java SE Runtime Environment 6, update 20
or a higher version installed, configured, and running on the
machine where you want to install HP Output Server 4.1. For
more details, refer to Before you install HP Output Server
on a Windows host on page 77.
2.
Click Next.

1.
In the Configuration Options window, do one of the following:

-
If you want to create a set of default servers, select

Yes (Create a set of default servers) (the default), and then click Next.
Skip step 2 and proceed to Creating a set of default servers on a Windows
host on page 82.
If you want to join an existing domain or create a new domain, select

No (Configure host options only), and then click Next.
Proceed to step 2.
2.
In the Domain Options window, do one of the following:

-
If you want to join an existing domain, select Join a domain (the default), and
then click Next.
Proceed to Joining an existing domain on a Windows host on page 83.
If you want to create a new domain, select Create a new domain, and then
click Next.
Proceed to Creating a new domain on a Windows host on page 84.
Creating a set of default servers on a Windows host

1.
In the HP Output Server Domain window, enter the following parameters:

-
82
In the Domain field, accept the default domain name or enter a domain name
for your HP Output Server installation.
Chapter 2
The domain name is not the same as the network domain name. The default
domain name is hostname.d, where hostname is the name of the host machine
where you are running the HP Output Server installation.
NOTE: Keep in mind the following restrictions when specifying an
HP Output Server domain name:
The first character must be a letter (a-z or A-Z).
After the first character, domain names can contain any
combination of letters (a-z or A-Z), dashes (-), underscores
(_), periods (.), or numbers.
The domain name must not contain embedded spaces.
Only standard 7-bit ASCII characters are allowed. Extended
8-bit ASCII characters, for example , are not allowed in
any position.
-
In the NM Port field, enter a port number to which the HP Output Server
Name Space Manager (NM) will listen.
2.
Click Next.
3.
In the Server State Configuration window, do one of the following:
4.
If you want the HP Output Server servers to be running when the setup is
complete, select Yes (the default).
If you want to start the HP Output Server servers manually after the setup is
complete, select No.
Click Next.
Proceed with the installation using the instructions in Task 4: Configure advanced
server options (optional) on page 84.
Joining an existing domain on a Windows host

1.
2.
HP Output Server
In the Host Configuration Options window, enter the following parameters:

-
In the Domain field, enter the name of an existing HP Output Server domain.
In the NM Host field, enter the name of the Name Space Manager (NM) host
in the existing domain.
In the NM Port field, enter the port number to which the NM in the existing
domain is listening. The default value is 4009.
Click Next.
83
Chapter 2
3.
In the HP Output Server Domain window, do one of the following:

-
To configure the database connection during the installation process, select

Configure now (recommended), and then click Next.
To configure the database connection later, select Configure later, and then
click Next.
NOTE: If you choose to configure the database connection after
joining an existing domain, the setup does not prompt you
for database options and treats the installation as a
client-only installation. The setup performs only the host
configuration.
Creating a new domain on a Windows host

1.
In the HP Output Server Domain window, enter the following parameters:

-
In the Domain field, enter the domain name of your HP Output Server
installation or accept the default domain name. The default host name is
hostname.d, where hostname is the name of this host.
In the NM Port field, enter the port number to which the NM is listening.
The default value is 4009.
2.
Click Next.
Task 4: Configure advanced server options (optional)

With advanced server configuration options, you can configure HP Output Server
processes to use a specific set of ports and network interfaces. For more information
about these options, see Appendix D, Firewall support on page 209 and Appendix E,
HP Output Server in a multi-NIC environment on page 213.
In the Advanced Server Configuration window, do one of the following:
-
If you want to configure the advanced server options, select Yes, and then click
Next.
Proceed with the installation by using the instructions in Configuring firewall
support.
84
Chapter 2
If you do not want to configure the advanced server options, select No (the
default), and then click Next.
Proceed with the installation using the instructions in Task 5: Configure the
JBoss server ports on page 86.
Configuring firewall support

1.
In the Firewall Support window, do one of the following:

-
To skip this step, select No (the default), and then click Next.
Proceed with the installation using the instructions in Specifying a network
interface.
2.
To enable firewall support, select Yes, and then click Next.
In the Firewall Ports window, enter seven port numbers for firewall support, and
then click Next.
NOTE: Because each HP Output Server server requires a minimum
of one port, you must enter at least seven port numbers. The
setup program does not provide default values and does not
check the ports that you specify for availability. Enter the
port numbers separated by commas, dashes, or as a range.
Only numeric characters, the comma, and the dash are
allowed.
For example:
4000-4100,4102,4104-4199
Specifying a network interface

1.
In the Network Interface Support window, do one of the following:

-
To skip this step, select No (the default), and then click Next.
Proceed with the installation using the instructions in Task 5: Configure the
JBoss server ports on page 86.
2.
HP Output Server
To specify HP Output Server processes to use a specific network interface,

select Yes, and then click Next.
In the Network Interface window, enter the host name or IP address of the
network interface that you want to use.
85
Chapter 2
Task 5: Configure the JBoss server ports

1.
In the JBoss Installation window, do one of the following:

-
If you do not want to configure the default JBoss server, select No, and then
click Next.
Proceed with the installation using the instructions in Task 6: Specify the
database type on page 86.
2.
If you want to configure the default JBoss server, select Yes (the default), and
then click Next.
In the JBoss Server Configuration window, specify 17 port numbers for JBoss
Server configuration. Port numbers must be in the range 1024 through 65535.
NOTE: Port numbers must be separated by commas or specified as a
range.
For example:
9000, 9001, 9002-9016
Task 6: Specify the database type

1.
In the Database Options window, do one of the following:

-
If you want to use MySQL Server as the database, select MySQL (the default),
and then click Next.
Proceed to step 2.
If you want to use Oracle database server as the database, select Oracle, and
then click Next.
Skip step 2 and proceed to Configuring the Oracle connection on page 90.
2.
In the MySQL Configuration Option window, do one of the following:

-
If you want to configure the default MySQL Server provided with HP Output
Server, select Yes (the default), and then click Next.
Proceed to Configure the MySQL Server provided with HP Output
Server on page 87.
If you want to configure an existing/ remote MySQL Server database, select

No, and then click Next.
Proceed to Configure an existing/remote MySQL Server on page 89.
86
Chapter 2
Task 7: Configure the database connection

Based on the database type that you selected in Task 6: Specify the database type, you
must configure either the MySQL or Oracle database connection.
Configure the MySQL Server provided with HP Output Server

NOTE: This is the default installation option. If you choose this
option, MySQL binaries are installed at the location
$DAZEL_HOME/share/mysql/5.0.91 and the MySQL
database is installed at the location
$DAZEL_HOME/var/mysql.
1.
In the MySQL Server Configurations window, enter the following configuration

parameters:
i.
In the Ibdata size field, enter the Ibdata size in megabytes or gigabytes.
ii.
In the Extent size field, enter the extent size in megabytes or gigabytes. Extent
size must be atleast 50% of the ibdata size.
iii. In the Port field, enter the port number to which MySQL Server is listening.
iv. Click Next.
2.
In the Database Logon Credentials window, enter the following configuration

parameters:
i.
In the User field, enter the MySQL user name for HP Output Server.
The default value of MySQL user name is hposadm.
NOTE: The MySQL user name for HP Output Server can contain
only simple ASCII characters and must not exceed 30
characters. Do not use accented characters, single or double
quotes, spaces, backslashes, accent graves, commas, or
special symbols.
HP Output Server
87
Chapter 2
ii.
In the Password field, enter the password for the MySQL server.
NOTE: You must specify a password of minimum three characters.
iii. In the Confirm Password field, enter the password again.

iv. Click Next.
3.
In the DB Prefix window, accept the default or enter the MySQL database prefix
name in the DB Prefix field, and then click Next.
The MySQL database prefix name is used to create the database name. The
database name used by HP Output Server is a combination of prefix name,
domain, and port. The MySQL database name is created in the following
format:
-database-name-prefix host attribute will be set to
the value of the MySQL database prefix name entered by the
user.
4.
88
In the Auto Create window, do one of the following:

-
If you want HP Output Server servers to create the database name

automatically, select Yes (the default).
If you do not want HP Output Server servers to create the database name
automatically, select No.
Chapter 2
Proceed to Task 8: Review the server configuration settings on page 93.
Configure an existing/remote MySQL Server

1.
In the ODBC Driver window, enter the following database server connection
parameters:
i.
In the Host field, enter the name or IP address of the MySQL host to which
MySQL Server is listening.
The default host name is localhost. You can also enter the name of the host
on which MySQL is installed.
NOTE: If MySQL is installed on the same machine as HP Output
Server, you must use localhost as the name of the host.
ii.
In the Port field, enter the port number to which MySQL Server is listening.
NOTE: Ensure that the specified MySQL port is enabled.
iii. Click Next.

2.
In the Database Logon Credentials window, enter the following configuration

parameters, and then click Next:
i.
In the User field, enter the MySQL user name for HP Output Server.
The default name is hposadm.
NOTE: The MySQL user name for HP Output Server can contain
only simple ASCII characters and must not exceed 30
characters. Do not use accented characters, single or double
quotes, spaces, backslashes, accent graves, commas, or
special symbols.
ii.
In the Password field, enter the password for MySQL server.

HP Output Server
89
Chapter 2
iv. Click Next.

3.
In the DB Prefix window, accept the default or enter the MySQL database prefix
The MySQL database prefix name is used to create the database name. The
database name used by HP Output Server is a combination of prefix name,
domain, and port. The MySQL database name is created in the following
format:
-database-name-prefix host attribute will be set to
the value of the MySQL database prefix name entered by the
user.
4.

-
If you want HP Output Server servers to create the database name

automatically, select Yes (the default).
If you do not want HP Output Server servers to create the database name
automatically, select No.
Proceed to Task 8: Review the server configuration settings on page 93.
Configuring the Oracle connection

1.
In the Oracle Configuration window, do one of the following:

-
If you want to configure the Oracle database by using the Oracle System ID,
select Oracle System Identifier (SID) (the default), and then click Next.
Perform the steps 2, 3, and steps 5 through 9. Skip step 4.
90
If you want to configure the Oracle database by using the Transparent Network
Substrate names, select Net Service Name (TNS), and then click Next.
Chapter 2
Perform the steps 3 through 9. Skip step 2.

2.
In the ODBC Driver Settings window, enter the following configuration

parameters:
i.
In the Host field, enter the name or IP address of the Oracle host to which the
Oracle server is listening.
The default host name is localhost. You can also enter the name of the host
on which Oracle is installed.
ii.
In the Port field, enter the port number to which Oracle server is listening.
3.
In the Database Logon credentials window, enter the following configuration

parameters:
i.
In the User field, enter the user name that HP Output Server will use to connect
to the Oracle database server.
The default value is hposadm.
ii.
In the Password field, enter the password for the user name that HP Output
Server will use to connect to Oracle database server.

iv. Click Next.
4.
5.
In the Select TNS Location window, do the following:

i.
Click Browse, and then select the path where you have downloaded the
tnsname.ora file.
ii.
Click Next.
In the DB Prefix window, accept the default or enter the Oracle tablespace prefix
The Oracle tablespace prefix name is used to create the tablespace name. The
tablespace name used by HP Output Server is a combination of prefix name,
domain, and port in the following format:
HP Output Server
91
Chapter 2
For example, if the prefix is hpomdb, the domain hpos.d, and the port
number 4009, the tablespace name would be hpomdb_hpos_d_4009.
NOTE: Special characters, such as dot (.) and exclamation mark (!),
are not supported.
6.

-
If you want HP Output Server to create the tablespace automatically, select Yes
(the default), and then click Next.
NOTE: If you choose to automatically create a tablespace, ensure
that you retain the alter user privilege for the HP Output
Server user. This is required for the normal operation of HP
Output Server.
If you do not want HP Output Server to automatically create a tablespace,

select No, and then click Next.
If the tablespace does not exist, the setup displays a warning message asking
whether you want to continue with the installation. You must provide a valid
tablespace name or allow the installer to create the tablespace automatically.
NOTE: For more details about creating a tablespace, refer to the
section, Before you install HP Output Server with Oracle
on a Windows host on page 77.
7.
In the Oracle Server Service Name window, enter the service name for Oracle in
the Service field, and then click Next.
The default Oracle server service name is ORCL.
8.
In the Oracle Driver path window, do one of the following:

-
92
Click Next to accept the default path.
Chapter 2
The default path is installDir\var\Oracle_driver_path.

CAUTION: The path name for the destination folder must not
contain embedded spaces, tabs, or any of the following
characters: *, ?, , , ', and %.
NOTE: You must create a lib folder under any location on your
system and download both the Oracle Instant Client libraries
and the Oracle ODBC driver for Windows to the lib folder.
NOTE: When you specify the location for Oracle Instant Client
libraries and the Oracle ODBC driver, you must specify the
path excluding lib.
For example:
If you have stored the Oracle Instant Client libraries and the
Oracle ODBC driver in installDir\var\lib, specify the
path as installDir\var.
9.
Click Browse, select the path of the installed Oracle ODBC driver, and then
click Next.
In the Oracle Instant Client Libraries Path window, do one of the following:
-
Click Next to accept the default path.

The default path is installDir\var\Oracle_lib_path.
Click Browse, select the path of installed Oracle Instant Client libraries, and
then click Next.
CAUTION: The path name for the destination folder must not
contain embedded spaces, tabs, or any of the following
characters: *, ?, , , ', and %.
Task 8: Review the server configuration settings
HP Output Server
1.
In the Review Settings window, review the server configuration settings that you
specified for the installation. If any of the settings are incorrect, click Back and
change the incorrect settings. If the settings are correct, click Next.
2.
In the Configuration window, review the results of the configuration, and then
click Next.
93
Chapter 2
An Information dialog box appears.

NOTE: If you selected MySQL provided with HP Output Server as
the database, the Information dialog box displays the
following message:
By default the MySQL database server tuning
parameters are set to certain default values. You can tune
MySQL Server using
$HPOM_INSTALL\share\mysql\5.0.91.0.0.1
\bin\tunemysql_hpos.pl.
NOTE: The Information dialog box also displays the URL for the
Web application for the HP Output Management product.
NOTE: For instructions on customized tuning of the MySQL
database server, see Appendix N, Tuning MySQL for HP
3.
Click OK.
If you get the error message, Setup encountered an error while creating Server
nm. Setup will not attempt to configure HP Output Server further, but will
complete the installation (rc=-1), check for error messages similar to the
following in the NM server log file (nm.log):
-
[error 00064012] DB connection failed.
[error 00064006] HY000: [MySQL][ODBC 5.1Driver] Access denied for

user '<hposDbUser>'@'<DbHost>' (using password:NO)
[error 0021402E] Initialization of the NM database failed.

Where <hposDbUser> is the database user name and <DbHost> is the
HP Output Server database server host name.
If you find similar messages, do the following:

i.
Continue with the installation.
ii.
Apply the HP Output Server Service Pack 11.2 patch.
iii. Configure all the HP Output Server servers manually.
94
Chapter 2
If you get a warning message Setup was unable to modify the enscript
configuration file (rc=1), you have to manually do the following changes in the
enscript.cfg file after the installation is complete:
i.
Open the enscript.cfg file located in the InstallDir\share\enscript

folder with a suitable text editor such as Notepad.
ii.
Replace the $DAZEL_HOME environment variable with the correct value of

InstallDir.
iii. Search for the AFMPath variable and change its value to
AFMPath: InstallDir/share/enscript.
For example:
If the current value for the AFMPath variable is
AFMPath:C:/HP/OM/shares/enscript:/usr/local/lib/ps:/
usr/lib/ps, where C:HP/OM is the installDir, then change the value to
AFMPath: C:/HP/OM/share/enscript.
iv. Save the changes to the enscript.cfg file.
4.
To complete the installation and exit the HP Output Server Setup Wizard, click
Finish.
NOTE: The log files will be created under installDir/var/log
directory. If the installation fails, review or back up the log
files before exiting the setup wizard.
HP Output Server
95
Chapter 2
Task 9: Verify that the SSM is running

1.
Open the Services window of the Windows operating system.
2.
Locate the Output Server Startup Manager and verify that it is running. If it is
not running, start the service. The default mode at system startup is manual. If you
want your HP Output Server servers, including the Server Startup Manager (SSM),
to restart automatically whenever you reboot, change the mode to automatic
under Startup Type.
NOTE: The Output Server Startup Manager starts all HP Output
Server servers along with the SSM server.
NOTE: For more information about installing HP Output Server
Manager in interactive or non-interactive mode, see
Appendix R, Installing HP Output Server Manager
on page 293.
NOTE: For more information about installing HP Job Manager for
Output Server Software in interactive or non interactive
mode, see Appendix S, Installing HP Job Manager for
Output Server Software on page 297.
Task 10: Post-installation reminders

If you selected Join a domain or Create a new domain option during the installation
process in Task 3: Configure the host machine on page 82, remember to perform the
following after the installation process.
96
Chapter 2
After you complete the installation process, use the config_server command to
create HP Output Server servers on the host machine. Create and start the SSM server
before starting other HP Output Server servers. For more information about using the
config_server command, see the System Administrators Command Reference for
HP Output Server.
NOTE: To configure delivery servers when joining a domain from
Windows host to UNIX server domain, you must set suitable
permission on the primary UNIX server using the pm_edit
command. For more information on pm_edit command,
see HP Output Server System Administrators Command
Reference.
NOTE: If you want to configure HP Output Management Web
Console, run the
perl jmconfig.pl -i -p 9000 script.
HP Output Server
97
Chapter 2
Completing the installation of HP Output Manager for SAP 4.1
Completing the installation of HP Output Manager

for SAP 4.1
To complete the installation of HP Output Manager for SAP, you must perform the
following additional installation tasks after performing a server installation of HP
Output Server:
1.
98
Depending on the operating system of your SAP installation, do one of the

following:
-
On UNIX hosts, complete the installation of HP Output Manager for SAP 4.1
by performing a client installation of HP Output Server on each SAP R/3
Enterprise (4.7) or SAP ECC 5.0 spool server host that accesses HP Output
Server.
On Windows hosts, complete the installation of HP Output Manager for SAP

4.1 by installing HP Output Server using the Join a domain installation
option on each SAP R/3 Enterprise (4.7) or SAP ECC 5.0 host that accesses
HP Output Server. See Joining an existing domain on a Windows host.
2.
Record the client number, host name, SAP R/3 Enterprise (4.7) or SAP ECC 5.0
system ID (SID), and instance number of each SAP R/3 Enterprise (4.7) or SAP
ECC 5.0 host on which you install HP Output Server.
3.
To configure your HP Output Manager for SAP 4.1 installation, configure the CPIC
user and the HP Output Manager for SAP interfaces using the instructions in the
System Administrators Guide for HP Output Manager for SAP.
4.
Configure a logical fax destination for delivering SAP jobs using the HP
SAPconnect server. Deliver a test document to the destination using the HP Output
Server pdpr command.
Chapter 2
Completing the installation of HP Output Distributor 4.1
Completing the installation of HP Output Distributor

4.1
If you are planning to use HP Output Distributor 4.1, you must complete additional
installation or configuration tasks after performing a server installation of HP Output
Server. This section provides an overview of these tasks.
Destination and permissions templates

HP Output Distributor relies on HP Output Server for delivery pathways and security.
During the installation of a default set of servers for HP Output Server, the setup
program performs the following configuration tasks:
Verifies that the Configuration Manager (CM) is running
Adds templates for creating HP Output Distributor logical and physical destinations
to the Configuration Manager (CM) database and stores them in the
installBinDir/nls/cfg/C/od_printer_template.cfg file
Defines the OD_ADMIN permissions template in the HP Output Server Privilege

Manager (PM). The OD_ADMIN permissions template enables you to assign
privileges to users who create or modify objects in an HP Output Distributor
database. For more information about using the OD_ADMIN permissions template,
see the System Administrators Guide for HP Output Distributor 4.1.
Troubleshooting failed template installations

If the setup program fails to install the templates for HP Output Distributor during an
installation of a default set of HP Output Server servers, you must run the
configod.pl script with the -i argument after setup is completed. For more
information about running configod.pl, see Appendix G, HP Output Distributor
configod.pl script on page 223.
Uploading templates manually after creating a new domain

If you performed a server installation of HP Output Server without configuring primary
servers (installing by creating a new domain), the templates for configuring destinations
are not added to the CM and the appropriate permissions templates are not added to the
PM in HP Output Server. To install the templates, you must first create the primary
servers manually and then run the configod.pl script with the -i argument. For
more information about running configod.pl, see Appendix G, HP Output
Distributor configod.pl script on page 223.
HP Output Server
99
Chapter 2
Completing the installation of HP Output Distributor 4.1
Configuring HP Output Distributor

To configure HP Output Distributor, use the System Administrators Guide for HP
Output Distributor to perform the following tasks:
100
1.
Configure permissions and delivery pathways.
2.
Configure HP Output Distributor databases with the odconfig_server

command.
3.
Create report definitions and sets using information in the System Administrators
Guide for HP Output Distributor.
Chapter 3
Uninstalling HP Output Server

Consider the following as you plan the uninstallation:
HP Output Server
With HP Output Server uninstalled, other HP Output Management products that

rely on HP Output Server cannot function properly.
When uninstalling HP Output Server on multiple hosts, uninstall the primary host
last.
The uninstallation script does not check for pending jobs before deleting the
installation.
Uninstalling HP Output Server 4.1 uninstalls HP Output Manager for SAP 4.1 and
HP Output Distributor 4.1.
If MySQL for HP Output Management is installed in installInstDir/var/mysql,

uninstalling HP Output Server removes all files and directories in installInstDir
including mysql.
101
Chapter 3
Uninstalling HP Output Server from a UNIX host

NOTE: These instructions describe how to use setup.pl in
interactive mode (with prompts) to uninstall an HP Output
Server standard, binaries, or instance installation. You can
use setup.pl in non-interactive mode (without prompts)
to uninstall an HP Output Server standard, binaries, or
instance installation by running setup.pl at the command
line with arguments. For more information, see Appendix A,
Using setup.pl in non-interactive mode on page 185.
Uninstalling an HP Output Server standard installation from a UNIX

host
This section describes how to uninstall an HP Output Server standard installation from a
UNIX host. These instructions apply to both server and client installations of HP Output
Server on a UNIX host.
NOTE: If you installed HP Output Server as a split installation, that
is, with HP Output Server binaries and HP Output Server
instance installed in separate locations, you must first
uninstall the HP Output Server instance using the procedure
in Uninstalling only the HP Output Server instance
on page 106, and then uninstall the HP Output Server
binaries using the procedure in Uninstalling only the HP
Output Server binaries on page 104.
NOTE: Do not use rm -rf to uninstall HP Output Server from a
UNIX host. Using this method does not remove the
databases from the MySQL server.
To uninstall HP Output Server from a UNIX host, perform the following steps:
102
1.
Ensure that the database and HP Output Server are running.
2.
Log in as the root user, or as the owner of the HP Output Server installation.
Chapter 3
3.
4.
Source the UNIX environment variables with one of the following commands,
Shell
Command
source
installInstDir/etc/setup_env.csh
Bourne or Korn
Stop all programs that monitor the HP Output Server server instance you want to
uninstall.
On multiple-domain hosts, some programs may be monitoring processes that are
managed by other HP Output Server instances. For example, HP Output Manager
for HP Software Operations and dzl_epod monitor HP Output Server processes
and should be stopped before you start the setup script.
NOTE: Monitor programs are not restarted automatically; you must
start these programs manually.
5.
Stop all HP Output Management products that depend on the HP Output Server
installation on the host. Some applications require that you run a product-specific
shutdown command. For more information, see the documentation for your HP
Output Management products.
6.
Change the directory to the location of the setup.pl installation script by

executing the following command:
cd installBinDir/bin
7.
Run the following script:

perl setup.pl
8.
Enter 2 to uninstall HP Output Server.
9.
When the setup prompts for the path for the HP Output Management product
component(s) to be uninstalled, enter the path where you have installed HP Output
Server.
For example:
/opt/hpom
HP Output Server
103
Chapter 3
The setup detects and displays the type of HP Output Management product
component in the specified directory.
For example:
HP Output Server standard installation.
10. At the prompt, if you want to uninstall the displayed components, enter y.
After the uninstallation is complete, the setup script displays the following
message:
The uninstall log file is located in
/tmp/uninstall.log.
Uninstalling only the HP Output Server binaries

This section describes how to uninstall only the HP Output Server binaries from a
UNIX host.
To uninstall HP Output Server binaries from a UNIX host, perform the following tasks:
Task 1. Uninstall all the HP Output Server instance(s) that are using the binaries
you want to uninstall.
Task 2. Uninstall the HP Output Server server binaries.
Task 1: Uninstall the HP Output Server instance(s) that are using the
binaries
To uninstall the HP Output Server instance(s), refer to Uninstalling only the HP Output
Server instance on page 106.
NOTE: You must uninstall all the HP Output Server instances that
are using the HP Output Server binaries you want to
uninstall before you uninstall the HP Output Server binaries.
Otherwise, the HP Output Server instance(s) will not be
usable.
NOTE: If multiple HP Output Server instances are using the same
HP Output Server binaries, you must uninstall each HP
Output Server instance separately before uninstalling the HP
Output Server binaries.
104
Chapter 3
Task 2: Uninstall the HP Output Server binaries

To uninstall HP Output Server binaries, perform the following steps:
1.
Log in as the root user or as the owner of the installed binaries.
2.

3.

perl setup.pl
4.
5.
When the setup prompts for the path of the HP Output Management product
component(s) to be uninstalled, enter the path where you have installed the
binaries.
For example:
/opt/hpom/binaries
For example:
HP Output Server binaries installation.
NOTE: You must manually stop or uninstall all HP Output Server
instances that are using the HP Output Server binaries you
want to uninstall. Otherwise, the HP Output Server instances
will not be usable.
6.
At the prompt, if you want to uninstall the displayed components, enter y.

When the uninstallation is complete, the setup script displays the following
message:
/tmp/uninstall.log.
HP Output Server
105
Chapter 3
Uninstalling only the HP Output Server instance

To uninstall any HP Output Server instance on a UNIX host, perform the following
steps:
NOTE: If multiple HP Output Server instances are using the same
HP Output Server binaries, you have to uninstall each HP
Output Server instance separately before uninstalling the HP
Output Server binaries.
1.
Make sure that the database and HP Output Server instance are running.
2.
Log in as the root user or as the owner of the installed HP Output Server instance.
3.
4.
Shell
Command
source
Bourne or Korn
Stop all programs that monitor the HP Output Server server instance you want to
uninstall.
managed by other HP Output Server instances. For example, HP Output Manager
for HP Software Operations and dzl_epod monitor HP Output Server processes
and should be stopped before you start the setup script.
start these programs manually.
5.
Stop all HP Output Management products that depend on the HP Output Server
installation on the host. Some applications require that you run a product-specific
shutdown command. For more information, see the documentation for your HP
Output Management products.
6.

106
Chapter 3
Uninstalling HP Output Server from a Windows host
7.

perl setup.pl
8.
9.
When the setup prompts for the path of the HP Output Management product
component(s) to be uninstalled, enter the path where you have installed the HP
Output Server instance.
For example:
/opt/hpom/instance
For example:
HP Output Server instance installation.
10. At the prompt, if you want to uninstall the displayed components, enter y.
After the uninstallation is complete, the setup script displays the following
message:
/tmp/uninstall.log.

This section describes how to remove HP Output Server from a Windows host.
NOTE: You must remove all locally installed HP Output
Management programs that are using this installation of HP
Output Server prior to removing HP Output Server. Do not
remove MySQL for HP Output Management.
To remove HP Output Server from a Windows host, perform the following steps:
HP Output Server
1.
Ensure that both the database and HP Output Server are running.
2.
Click the Start button, point to Settings, and then click Control Panel.
107
Chapter 3
3.
In the Control Panel, double-click Add or Remove Programs.
4.
Select HP Output Server Version 4.1 from the list, and then click
Change/Remove.
The system prompts whether to uninstall HP Output Server Version 4.1.
5.
Click Yes.
After successful uninstallation, the system prompts whether to restart your system
immediately or later.
6.
Select the required option, and then click Finish.

If you choose to restart your system when prompted, remove any disks from their
disk drives before continuing.
The HP Output Server uninstallation is complete.
NOTE: You must manually delete the HP Output Server installation
directory after uninstalling HP Output Server 4.1 with
Oracle as the database server on a Windows host.
For example:
If you have installed HP Output Server 4.1 with Oracle as
the database server at C:\HP\OM directory, you must
manually delete this folder after uninstalling HP Output
Server 4.1.
CAUTION: Do not stop the uninstallation after the process has
started. Your system might crash because of the
ikernel.exe file getting corrupted.
108
Chapter 4
Migration
This chapter describes how to migrate data and configuration settings of HP Output
Server Versions 3.5 or 4.0 to HP Output Server 4.1.
The following migration scripts are shipped with HP Output Server 4.1 to perform the
migration:
hpos_dump.pl
hpos_load.pl
NOTE: For more information of migration scripts, see Migration
scripts on page 120.
When you migrate an existing installation of HP Output Server, the installations of HP

Output Management Web Console and HP Output Distributor are migrated to Version
4.1.
NOTE: HP Output Server 4.1 does not support upgrade from your
existing HP Output Server 3.5 or 4.0 installations to HP
Output Server 4.1.
HP Output Server
109
Chapter 4
Migration
Migration options
During migration, the migration scripts migrate data from the following HP Output
Server servers:
Type of Server
Name of Server
Primary
Name Space Manager (NM)

Privilege Manager (PM)
Accounting and Inventory Manager (AIM)
Configuration Manager (CM)
Delivery
Delivery Manager (DLM)

Job and Queue Manager (JQM)
Destination Manager (DSM)
Accessory
OMS Callback (OMSCB)*

SAPconnect (SAPCON)
EPO server
* The OMS Callback server is configured as part of HP Output Manager for SAP.
The SAPconnect server is configured as part of HP Output Manager for SAP.
CAUTION: Before migrating, back up your installation of HP

Output Server. Typically, the only method of recovering
from a failed HP Output Server migration is restoring
from a backup.
For information about backing up your HP Output Server installation, see Chapter 7,
Backing up and restoring HP Output Server on page 163.
For more information about troubleshooting a failed migration, see Troubleshooting a
failed migration on page 128.
Migration options
HP Output Server 4.1 allows the following migration options:
110
Chapter 4
Migration
What is and what is not migrated
Migration to the same directory: You can migrate the HP Output Server
installation to the same directory location as that of an existing HP Output Server
installation.
If you choose this option, you can migrate job data and configuration settings from
your existing HP Output Server 3.5 or 4.0 installation on UNIX hosts.
NOTE: This option is supported only on UNIX. For more
information on performing migration, see Migrating HP
Output Server on a UNIX host on page 121
NOTE: If you are migrating to the same directory with a split
installation of HP Output Server 4.1, the owner of the HP
Output Server binaries, instance, and logs must be the same.
NOTE: If you are migrating to the same directory with HP Output
Server 4.1, and if HP Web Delivery and HP Output Server
are using the same MySQL database under the
installInstDir/var/Mysql directory, you must take a
manual dump of the MySQL database for HP Web Delivery.
Migration to a different directory: You can migrate the existing HP Output

Server configuration settings to a different directory location on the same system or
on a different system.
If you choose this option, your existing HP Output Server installation is retained.
NOTE: This option is supported on Windows and UNIX. For more
information on performing migration, see Migrating HP
Output Server on a UNIX host on page 121 and Migrating
HP Output Server on a Windows host on page 126.

The following table lists what is and what is not migrated during the migration process:
HP Output Server
HP Output Server
server/component
Name Space Manager

(NM)
All information, except server bindings, is migrated.
111
Chapter 4
Migration
HP Output Server
server/component
All information is migrated.
Configuration Manager
(CM)
All information, except Cap tickets, is migrated.
Accounting and Inventory

Manager (AIM)
The inventory management classes data, including persons,

person-destinations, groups, and destinations are migrated.
The accounting information, such as job, destination, and server
accounting data, is not migrated.
Event Manager (EM)
No data from EM is migrated.
EPOD server
If EPOD is configured as an EPO server (HP Output Server 4.0

only), the server subscription and description files are backed
up and migrated.
If EPOD is not configured as a server, the files are not backed
up or migrated.
HP Output Management
Web Console
The entire HP Output Management Web Console database is

migrated.
All data, except HP Output Distributor job data, is migrated.
SAPconnect (SAPCON)
The saprfc.ini configuration file is backed up and restored.
OMS Callback (OMSCB)
The config.txt configuration file is backed up and restored.
Server Attributes
The following server attributes are not migrated:

HP Output Server: -server-log-file, -server-name,
-server-type, -server-start-enabled,
-server-start-order,
-server-working-directory,
-server-login-name,
-dazel-install-directory,
-server-executable-path,
-server-executable-name,
-server-executable-options,
-managing-server,
-transfer-methods-supported,
-transformers-supported, and -object-class.
SAPconnect (SAPCON): -sapcon-infax-working-dir
LPR Gateway
112
All information is not migrated.
Chapter 4
Migration
HP Output Server
server/component
Job data
You can migrate job data from an existing HP Output Server 3.5
or 4.0 installation only and you must perform migration to the
same directory as that of an existing HP Output Server
installation for job data migration. Job data migration is not
supported on Windows hosts.
HP Web Delivery
If you are migrating to the same directory as the existing HP

Output Server installation with HP Output Server 4.1, and if HP
Web Delivery and HP Output Server are using the same
MySQL database, then the MySQL database for HP Web
Delivery will not be migrated.
HP International Printing
for HP Output Server
If there are any new fonts added for HP International Printing

for HP Output Server 3.5 or 4.0, they will be migrated to HP
Output Server 4.1.
The following files are backed up in the
installBinDir/migration_bak/hpipfhpos
directory:
HP Inbound Fax for

Output Server
mffpos.pro
mffpcl.pro
mffpdf.pro
cpmcopy_doc_format.cfg
If HP Inbound Fax for Output Server is configured as a server

(In HP Output Server 4.0 only), the following files are backed
up in the installBinDir/migration_bak/ibf directory:
callctrl.cfg
btcall.cfg
IBFaxGateway.properties
To use Inbound fax capabilities, you must install HP Inbound
Fax for Output Server after installing HP Output Server 4.1.
HP Output Server
113
Chapter 4
Migration

The following assumptions and restrictions apply to migrating HP Output Server to
Version 4.1:
If you are migrating HP Output Server 3.5 or 4.0 and want to configure HP Output
Server to use the multi-NIC and firewall support features, you must add these
features manually after performing migration. See Appendix D, Firewall support
on page 209 and Appendix E, HP Output Server in a multi-NIC environment
on page 213.
The instructions for migrating HP Output Server refer to the location of the HP
Output Server binaries as installBinDir and location of HP Output Server instance
as installInstDir. Substitute the correct path name for your binaries installation
when you see the installBinDir variable and the correct path name for your instance
installation when you see the installInstDir variable. For a standard installation of
HP Output Server, where the binaries and instance are installed at the same
location, substitute the correct path name for your installation when you see either
the installDir, installBinDir, or installInstDir variables.
On UNIX hosts, if any portion of the installInstDir/var directory structure is

mounted from another file system on a remote host, the remote file system must be
exported such that the local root user ID or the owner of the HP Output Server
installation maps to the remote root user ID.
On UNIX hosts, only the installInstDir/var directory or the

installInstDir/var/jobdb directory may be mounted or linked to another file
system.
HP Output Distributor relies on HP Output Server for delivery pathways and

security.
During HP Output Server 4.1 installation, if the setup program fails to install the
templates for HP Output Distributor, run the configod.pl script with the -i
argument from installBinDir/etc before migration. For more information about
running configod.pl, see Appendix G, HP Output Distributor configod.pl
script on page 223.
If you migrate a server installation of HP Output Server that does not have primary
servers configured (for example, migrate an installation that was created by
creating a new domain), and an installation of HP Output Distributor does not exist,
the templates for configuring HP Output Distributor destinations are not added to
the CM and the appropriate permissions templates are not added to the PM in HP
Output Server. To install the templates, you must first create the primary servers
114
Chapter 4
Migration
manually and then run the configod.pl script with the -i argument. For more
information about running configod.pl, see Appendix G, HP Output
Distributor configod.pl script on page 223.
To complete the configuration of HP Output Distributor, see the System
Administrators Guide for HP Output Distributor.
HP Output Server
115
Chapter 4
Migration
Before you begin
Before you begin

This section describes prerequisite tasks and requirements for migrating HP Output
Server 3.5 or 4.0 to HP Output Server 4.1. This section assumes that you have read
Chapter 1, Planning the installation on page 1.
HP Output Server 3.5 and 4.0 migration prerequisites

HP Output Server 4.1 supports migration from HP Output Server 3.5 and 4.0. The
following table describes the prerequisites for migrating HP Output Server 3.5 and 4.0
to HP Output Server 4.1. Ensure that these prerequisites are met prior to migrating HP
Output Server.
Table 4-1. Prerequisites to migrating HP Output Server 3.5 or 4.0
116
Prerequisite
1. Service Pack level

installation must be at
Service Pack 10.2 before
migrating to HP Output
Server 4.1.

installation must be at Service
Pack 10.2 before migrating to
HP Output Server 4.1.
2. Server
configuration
Ensure that your HP Output Server 3.5 or 4.0 server

installation has configured HP Output Server servers or a
configured host (the HostConfig.sgml file exists) prior to
migrating to HP Output Server 4.1.
3. Back up
Before migrating HP Output Server, back up your installation.

Typically, the only method of recovering from a failed
migration is restoring from a backup.
4. Active jobs in
queues
If you migrate while HP Output Server is processing jobs, use

the pdset command to pause all queues that are processing
active jobs. Because servers are stopped and started during the
migration process, do not use the pdpause command to
pause the queues. Using pdpause instead of pdset will
cause queued jobs to fail. For information about using the
pdset command to pause an object in a delivery pathway, see
the System Administrators Guide for HP Output Server.
5. Processes or
scripts using Perl
Ensure that no other processes or scripts are using Perl in the

installBinDir/bin directory when you perform a migration.
6. Disk space
Migrating HP Output Server 3.5, or 4.0 to Version 4.1 requires

more disk space than a full installation. For more information,
see System requirements on page 6.
Chapter 4
Migration
Before you begin
Table 4-1. Prerequisites to migrating HP Output Server 3.5 or 4.0

Prerequisite
7. Migration order
When migrating a multi-host HP Output Server domain,

migrate the host containing the primary servers prior to
migrating any other hosts. Migrate all servers in a multi-host
domain. Migrate client installations of HP Output Server after
migrating the servers.
9. Job data migration
For job data migration, you must perform migration to the

same directory and perform the dump and upload operations
as the owner of the HP Output Server installation.
If you are migrating to a split installation of HP Output Server
4.1, and if the owner of the HP Output Server binaries and
instance are different, you have to perform the dump and
upload operations as the root user.
Job data migration is supported only on UNIX hosts.
10. Resource
requirements
Generally, resource
requirements for HP Output
Server 4.1 and HP Output
Server 3.5 are equivalent.
HP Output Server 4.1 may
allow increased throughput
when benchmarked against
However, additional
resources may be required to
realize the increased
performance in HP Output
Server 4.1.
Not applicable
Migrating a multi-host domain

If you are migrating a multi-host HP Output Server domain to Version 4.1, you must
migrate the host running the primary servers prior to migrating the servers of all other
hosts.
To migrate a multi-host HP Output Server domain to Version 4.1, perform the following
steps:
HP Output Server
1.
Stop all the delivery servers on the machine where the NM resides.
2.
Stop all of the servers on all of the remaining machines.
117
Chapter 4
Migration
Migration effects on HP Output Server
3.
Migrate the host that is running the primary servers using the migration steps in the
following sections of this chapter as appropriate to your platform. Ensure that the
primary servers are running after the migration.
4.
Migrate the servers of all other hosts using the migration steps in the following
sections of this chapter as appropriate to your platform. Ensure that all servers are
running on all machines after the migration.
CAUTION: Failure to follow these steps may result in a loss of jobs
or other errors.
Migration effects on HP Output Server

Migrating HP Output Server 3.5 or 4.0 to HP Output Server 4.1 affects customizations
and templates as follows:
Customized DPAOIDs are preserved during an HP Output Server migration if the

customized DPAOIDs are placed in the installBinDir/custom directory. The
DPAOIDs database is not migrated during this process.
Customizations made to delivery objects (logical destinations, physical

destinations, and queues) are preserved.
Supported transformers and the transformer framework in the DSM have been
changed. For more information, see the Release Notes and the System
Administrators Guide for HP Output Server 4.1.
Customizations made to the following are preserved if the customizations are

placed in the installBinDir/custom directory:
118
cover sheets
hosts.equiv
hosts.lpd
printcap
Files in installBinDir/nls/cfg are deleted and replaced.
Chapter 4
Migration
Migration effects on HP Output Manager for SAP
Files in installBinDir/custom are preserved.

NOTE: Server names beginning with a dash (-), underscore (_), or a
period (.) are not supported for HP Output Server 4.1, and
you will receive an error if you create server names with
these characters. When migrating from HP Output Server 3.5
to HP Output Server 4.1, the HP Output Server server names
should not begin with special characters such as dash (-),
period (.), or with an underscore (_). Ensure that the server
names are valid before creating the server.
Migration effects on HP Output Manager for SAP

Migrating to HP Output Server 4.1 has the following effects on an existing HP Output
Manager for SAP installation:
The SAPconnect (SAPCON) saprfc.ini file and OMS Callback (OMSCB)

config.txt are backed up during the migration process.
Back up the following customizations:

-
$DAZEL_HOME/var/sap: This directory contains configuration files for

previously configured OMS call back and SAPconnect servers.
$DAZEL_HOME/lib/r3*.pl: These files may have user-defined

customizations and will not be preserved. However, the customized files are
preserved in the backup and they can be referenced in order to customize the
new files.
$DAZEL_HOME/lib/dzl_*.pl: These files may have user-defined

customizations. They can be restored from the backup after the migration
completes.
NOTE: Uninstalling HP Output Server will remove all the template
customizations.
Migration effects on HP Output Distributor

Migrating to HP Output Server 4.1 has the following effects on an existing HP Output
Distributor installation:
HP Output Server
HP Output Distributor job data migration is not supported.
119
Chapter 4
Migration
Migration scripts
The location of the odconfig_server command is changed to

installBinDir/bin.
Migration scripts
The following migration scripts are shipped with HP Output Server 4.1:
hpos_dump.pl
This perl script creates a dump of your existing HP Output Server 3.5, or 4.0 installation
into a.tar file.
Syntax
perl hpos_dump.pl [-h]
perl hpos_dump.pl [-f filename]
Arguments
-h
This argument provides help menu options for the hpos_dump.pl script.
-f filename
This argument specifies the archive filename of the .tar file which stores the
dump of the existing HP Output Server installation.
NOTE: If -f argument is not specified, a default .tar file is created
in installInstDir/var/log directory. The .tar file is in
the following format:
hpos_dump_hpom.d_20090302_1524.tar
Where, hpom.d is the domain name, 20090302 is the date
in yyyymmdd format, and 1524 is time in hhmm format.
hpos_load.pl
This perl script loads existing HP Output Server 3.5 or 4.0 installation from the archive
.tar file to HP Output Server 4.1 installation.
120
Chapter 4
Migration
Migrating HP Output Server on a UNIX host
Syntax
perl hpos_load.pl [-h]
perl hpos_load.pl filename
Arguments
-h
This argument provides help menu options for the hpos_load.pl script.
filename
This is a mandatory argument and specifies the dump archive filename which
is a .tar file which stores the dump of the existing HP Output Server
installation. The hpos_load.pl uses the contents of this .tar file to load the
data and configuration settings to HP Output Server 4.1 installation.

This section describes how to migrate HP Output Server 3.5, or 4.0 to HP Output Server
4.1 on a UNIX host. This section assumes that you have read the section Before you
begin on page 116.
Migrating an HP Output Server server installation on a UNIX host

To migrate a server installation of HP Output Server 3.5 or 4.0 to HP Output Server 4.1
on a UNIX host, perform the following steps:
Task 1: Dump configuration

1.
Log in as root or the owner of the HP Output Server installation.

For example, if you have specified the owner of the installed files as hposadm
while installing HP Output Server, login as hposadm.
NOTE: For job data migration, perform the dump operation as the
owner of the HP Output Server installation.
HP Output Server
121
Chapter 4
Migration
2.
Shell
Command
Bourne or Korn
NOTE: If you have an existing HP Output Management Web

Console installation, source the setup_omwc_env.sh
environment variable on UNIX host.
3.
Change directories to the location of the hpos_dump.pl migration script.

For example, to change to the migration directory for your operating system,
enter the following command:
cd /migration/operating system
4.
Run the hpos_dump.pl script by entering the following command:

perl hpos_dump.pl
The migration utility creates a back-up of your configuration settings in a
compressed file format at the location installInstDir/var/log.
NOTE: The log file is located in
installInstDir/var/log/hpos_dump.log.
Task 2: Back-up the migration dump file

CAUTION: You must back up the migration dump file only if you
are performing migration to the same directory location
as that of an existing HP Output Server installation.
Back-up the migration dump file to a convenient location on your system.
122
Chapter 4
Migration
Task 3: Uninstall an existing HP Output Server installation

CAUTION: You must unistall an existing HP Output Server
installation only if you are performing migration to the
same directory location as that of an existing HP Output
Server installation.
CAUTION: If MySQL and JBoss are installed under
$DAZEL_HOME, the uninstall script uninstalls MySQL
and JBoss automatically. MySQL and JBoss will not be
usable later.
Uninstall the existing HP Output Server installation by running the customized
uninstallation script. To uninstall an existing HP Output Server installation by using the
customized uninstallation script, perform the following steps:
1.
Change directories to the location of the uninstall.pl customized

uninstallation script.
2.
Run the uninstallation script by entering the following command:

./perl uninstall.pl
The customized uninstallation script removes an existing HP Output Server
installation.
NOTE: After uninstallation, the installInstDir/var/jobdb and
installBinDir/var/custom directories are retained.
HP Output Server
123
Chapter 4
Migration
Task 4: Install HP Output Server

Install HP Output Server 4.1 on your system. For more information on installing HP
Output Server 4.1 refer to Chapter 2, Installing HP Output Server on UNIX hosts
on page 41.
NOTE: For job data migration, you must enter the same domain
name that you mentioned in your previous HP Output Server
installation and you must perform migration to the same
directory location as that of an existing HP Output Server
installation.
NOTE: To use Unicode jobs, you must install HP International
Printing for HP Output Server after installing HP Output
Server 4.1.
NOTE: To use Inbound Fax capabilities, you must install HP
Inbound Fax for Output Server after installing HP Output
Server 4.1.
NOTE: If you are migrating to the same directory with a split
installation of HP Output Server 4.1, the owner of the
HP Output Server binaries, instance, and logs must be the
same.
NOTE: Generally, resource requirements for HP Output Server 4.1
and HP Output Server 3.5 are equivalent. HP Output Server
4.1 may allow increased throughput when benchmarked
against HP Output Server 3.5. However, additional resources
may be required to realize the increased performance in HP
Output Server 4.1.
Task 5: Load configuration

1.
124
Log in as root or the owner of the HP Output Server installation.
Chapter 4
Migration
For example, if you have specified the owner of the installed files as hposadm
while installing HP Output Server, login as hposadm.
NOTE: If you are migrating to a split installation of
HP Output Server 4.1, and if the owner of the
HP Output Server binaries and instance are different, you
must login as the root user to load the configuration.
NOTE: For job data migration, perform the upload operation as
the owner of the HP Output Server installation.
2.
3.
Shell
Command
Bourne or Korn
Change directories to the location of the hpos_load.pl migration script.

4.
Run the hpos_load.pl script by entering the following command:

perl hpos_load.pl filename
For example, if domain name of the system from where the dump operation was
performed is hpom.d, and the dump archive file name is
hpos_dump_hpom.d_20090302_1524.tar, execute the following
command to load the configurations:
perl hpos_load.pl
installInstDir/var/log/hpos_dump_hpom.d_20090302_1524.
tar
The migration utility loads your existing configuration settings to
HP Output Server
125
Chapter 4
Migration
Migrating HP Output Server on a Windows host
The log file is located in installInstDir/var/log/hpos_load.log.

NOTE: After migrating HP Output Server 4.1 installation, the
HP Output Server domain name, hostname, and port number
must be updated in the SAP system if OMS Callback
(OMSCB) is configured.
NOTE: If there are any new fonts added for
HP International Printing for HP Output Server 3.5 or 4.0,
the hpos_load.pl utility migrates the fonts automatically
to HP Output Server 4.1. If there are any customization
changes in mffpcl.pro file, you must do the changes
again in HP Output Server 4.1.
Migrating HP Output Server on a Windows host

To migrate a server installation of HP Output Server Version 3.5, or 4.0 to HP Output
Server 4.1 on a Windows host, perform the following steps:
1.
Open a Command Prompt window.
2.
3.
Change the directory to \win
4.
Change directories to the location of the hpos_dump.pl migration script.

For example, to change to the migration directory, enter the following
command at the command prompt:
cd /win/migration
NOTE: If you have an existing HP Output Management Web
Console installation, source the setup_omwc_env.bat
environment variable on Windows host.
5.
Run the hpos_dump.pl script by entering the following command:

perl hpos_dump.pl
The migration utility creates a back-up of your configuration settings in a
compressed archive file format at the location installInstDir/var/log.
126
Chapter 4
Migration
Restoring backup template customizations
An example of the archive file is as follows:

installInstDir/var/log/hpos_dump_hpom.d_20090302_1524.tar
NOTE: The log file for the dump operation is located in
installInstDir/var/log/hpos_dump.log.
6.
Back-up the migration dump file to a convenient location on your system.
7.
Use the Add/Remove Programs feature of the Windows operating system to

remove the existing HP Output Server installation.
8.
Install HP Output Server 4.1 on your system. For more information on installing
HP Output Server 4.1 refer to Chapter 2, Installing HP Output Server on Windows
hosts on page 77.
NOTE: Generally, resource requirements for HP Output Server 4.1
and HP Output Server 3.5 are equivalent. HP Output Server
4.1 may allow increased throughput when benchmarked
against HP Output Server 3.5. However, additional resources
may be required to realize the increased performance in HP
Output Server 4.1.
9.
Change directories to the location of the hpos_load.pl migration script.

10. Run the hpos_load.pl script by entering the following command:

perl hpos_load.pl domain-name configuration_filename
The migration utility loads your existing configuration settings to HP Output
Server 4.1.
The log file for the load operation is located in
installInstDir/var/log/hpos_load.log.
Restoring backup template customizations

This section describes how to restore backup template customizations after a migration
on UNIX and Windows hosts.
HP Output Server
127
Chapter 4
Migration
Troubleshooting a failed migration
During migration, some templates are replaced or removed and not retained in the CM.
These templates may be restored from a backup .cfg file and reloaded into the CM
manually. To restore these templates, perform the following steps:
1.
Depending on your shell, source the UNIX environment variables with one of the
following commands to update your environment.
Shell
Command
source
Bourne or Korn
On Windows hosts, the environment variables do not require additional sourcing.

2.
Change to the migration_bak directory using the following command:

cd installBinDir/migration_bak
3.
To change to the custom/templates directory, enter the following:

cd custom/templates
4.
Identify which templates are to be reloaded into the CM and move them into files
within the installBinDir/custom/templates directory.
5.
To change to the installBinDir/custom/templates directory, enter the

following:
cd installBinDir/custom/templates
6.
To load the modified template files into the CM, enter the following:
pdconfig -u -c filename
Run this command for each .cfg file that is to be reloaded into the CM.
For more information on restoring backup template customizations, contact Customer

Support.

Following is the order in which HP Output Server, HP Output Manager for SAP, and
HP Output Distributor are migrated during migration of HP Output Server:
128
1.
HP Output Server
2.
3.
Chapter 4
Migration
If migration of HP Output Server fails, the setup script aborts and the remaining
products are not migrated or installed.
For information about recovering from a failed migration of HP Output Server, see the
following section Recovering from a failed HP Output Server migration.
Recovering from a failed HP Output Server migration

Typically, the only way to recover from a failed HP Output Server migration is to
restore the installation from a backup, fix the problem that caused the failure, and rerun
the setup program. You do not need to restore from a backup before fixing the problem
and rerunning the setup program when a failure occurs due to the following:
The setup program detected an unsupported Service Pack level for HP Output
Server, HP Output Manager for SAP, or HP Output Distributor.
An attempt to stop all servers failed, causing the setup program to abort the
migration.
Insufficient disk space caused the setup program to abort the migration.
In these cases, fix the problem that caused the failure and rerun the migration process.
HP Output Server
129
Chapter 4
Migration
130
Chapter 5
Installing and removing patches

This chapter describes how to install and remove patches (Service Packs and Hotfixes)
on HP Output Server. See the Release Notes that accompany a patch before attempting
to install a Service Pack or Hotfix. Patching HP Output Server 4.1 also patches HP
Output Manager for SAP 4.1 and HP Output Distributor 4.1 installations.
CAUTION: Back up your installation of HP Output Server before
installing or removing a patch. Failure to do so could
result in a catastrophic data loss. For more information,
see Chapter 7, Backing up and restoring HP Output
Server on page 163.
Install a patch in a test environment before you apply it
to a production environment.
Do not interrupt the patch process after it has begun.
To install a patch on a UNIX host, use the instructions in the following section.
To install a patch on a Windows host, use the instructions in Installing a patch on a
Windows host on page 145.
Join a domain patch installation

When HP Output Server is using integrated MySQL, make sure that MySQL is
configured and running before applying a patch.
HP Output Server
131
Chapter 5
Installing a patch on a UNIX host

This section describes how to install a patch for HP Output Server on a UNIX host. See
the Release Notes that accompany a patch before attempting to install it.
Service Pack installations are cumulative. For example, a Service Pack that updates HP
Output Server to 4.1.0.3 includes defect fixes and enhancements in Service Packs
4.1.0.2 and 4.1.0.1.
Hotfix installations are not cumulative. For example, Hotfix 2 does not include defects
fixed in Hotfix 1.
You must apply hotfixes in order. For example, if you apply Hotfix 3 only, but later
determine that you also need to apply Hotfix 2, you must remove Hotfix 3 before
applying Hotfix 2.
NOTE: If your HP Output Server domain is configured to run on
multiple hosts, install a patch within the same maintenance
window first on the host that runs the primary servers, and
then on all other hosts that run all other HP Output Server
servers. Then, either within the same service window
(recommended) or within a subsequent service window,
install the patch on client-only systems.
Installing a patch on an HP Output Server standard installation on

a UNIX host
To install a patch on an HP Output Server standard installation on a UNIX host, perform
132
1.
Log in as root or the user specified during the installation as the owner of the
installed files, to the host where HP Output Server is running.
2.
Shell
Command
Bourne or Korn
Chapter 5

3.
Download the patch from the Software Support Online (SSO) Web site,
http://www.hp.com/go/hpsoftwaresupport and save it in
installBinDir/bin.
For more details about downloading the software patches from the Software
Support Online Web site, refer to Downloading software patches on page xxii.
4.
Stop all programs that monitor the HP Output Server installation you want to patch.
managed by other HP Output Server instances. For example, the HP Output
Manager for HP Software Operations and dzl_epod monitor HP Output Server
processes and should be stopped.
NOTE: Monitor programs are not restarted automatically. You must
restart these programs manually.
5.
Stop all HP applications that depend on the HP Output Server installation on the
host. Some applications require a product-specific shutdown command. In general,
these applications are not restarted automatically; you must restart these
applications manually. For more information, see the documentation for your HP
Output Management applications.
NOTE: Do not stop the database instance used by HP Output
Management.
6.
Change to the installBinDir/bin directory by entering the following command:

7.
Run the patch.pl script:

perl patch.pl
1. Install patch for HP Output Management product
components
2. Backout patch for HP Output Management product
components
8.
Select option 1.
9.
Enter the path where you have installed the product.

The default path is installInstDir.
HP Output Server
133
Chapter 5
The setup detects and displays the installed HP Output Management product
component.
For example:
1. HP Output Server standard installation
4.1.0.0.0.20
10. Enter a valid fix file path or a valid path to the directory where fix files are present.
Setup detects and displays the available HP Output Management product patches.
For example:
1. HP Output Server standard installation 4.1.0.2.0.1
11. Enter the number corresponding to the patch you want to process or enter q to quit
the setup.
The patch utility then extracts the necessary files and validates all patch files.
NOTE: All servers are stopped during the patch installation.
NOTE: If one or multiple EPOD processes are running on the system
and are part of the HP Output Server instance, you are
prompted to quit the operation, stop the processes manually,
and restart the operation.
12. When the system prompts you to restart the servers after the patch installation is
complete, select one of the following:
-
Select n to accept the default.

NOTE: If you choose not to restart the servers when the patch
installation is complete, you must restart the servers
manually before using HP Output Server.
Select y, to stop and subsequently restart all servers.
The log file is located at installInstDir/var/log/patch.log.
134
Chapter 5

The patch installation is complete.

NOTE: Customized files that are located in the
installBinDir/custom directory are not modified by patch
installations. Customized files located in any other directory
may be modified or overwritten during a patch installation.
For guidance, contact HP Output Management
Implementation and Integration Services.
Installing a patch on an HP Output Server binaries installation on a

UNIX host
NOTE: If you have installed HP Output Server as a split installation,
that is, if you have installed the HP Output Server binaries
and instance at separate locations, you must install the patch
for the binaries and instance separately.
NOTE: For a split installation of HP Output Server, you must patch
the binaries and instance to the same patch level.
the binaries first, and then patch the instance(s) that are
referring to the binaries.
NOTE: If the HP Output Server binaries are used by multiple
instances, you must stop all the instances that are using those
binaries before patching the binaries.
To install a patch on an HP Output Server binaries installation on a UNIX host, perform
1.
Log in as root or as the owner of the installed HP Output Server binaries.
2.
http://www.hp.com/go/hpsoftwaresupport and save it in
installBinDir/bin.
HP Output Server
135
Chapter 5
3.
Stop all programs that monitor the HP Output Server installation you want to patch.
managed by other HP Output Server instances. For example, the HP Output
Manager for HP Software Operations and dzl_epod monitor HP Output Server
processes and should be stopped.
NOTE: Monitor programs are not restarted automatically. You must
4.
Stop all HP applications that depend on the HP Output Server installation on the
host. Some applications require a product-specific shutdown command. In general,
these applications are not restarted automatically. You must restart these
Management.
5.

NOTE: The patch for HP Output Server binaries includes only the
modified binaries. You must have the bare version of
HP Output Server or any previous Service Packs installed to
carry out the patching.
6.

perl patch.pl
components
components
7.
Select option 1.
8.

The default path is installBinDir.
136
Chapter 5

components.
For example:
1. HP Output Server binaries installation
4.1.0.0.0.20
9.
Enter a valid fix file path or a valid path to the directory where you have
downloaded the fix files.
The setup detects and displays the available HP Output Management product
patches.
For example:
1. HP Output Server 4.1.0.2.0.1
10. Enter the number corresponding to the patch you want to process or enter q to quit
the setup.
The patch utility then extracts the necessary files and validates all patch files.
NOTE: If any HP Output Server instances that use the HP Output
Server binaries are found running on the system, the system
prompts you to quit the operation and stop the instances
manually before continuing the patch operation.
After the patch installation is successfully completed, the system displays the
following message:
Patch installation has been successfully completed.
You are now running HP Output Server binaries
installation 4.1.0.2.0.1.
The patch log file is located at installBinDir/patch.log.
HP Output Server
137
Chapter 5
Installing a patch on an HP Output Server instance installation on

a UNIX host
that is, if you have installed HP Output Server binaries and
instance at separate locations, you must install the patch for
the binaries and instance separately.
NOTE: You must patch the HP Output Server binaries and instance
to the same patch level.
the binaries first, and then patch the instance(s) that are
referring to the binaries.
instances, you must stop all instances that are using those
binaries before patching the binaries.
To install a patch on an HP Output Server instance installation on a UNIX host, perform
the steps mentioned in Installing a patch on an HP Output Server standard installation
on a UNIX host on page 132. However, note the following exceptions:
In step 1, you must log in as root or as the owner of the installed HP Output
Server instance.
In step 9, the setup detects and displays the installed HP Output Management
product component.
For example:
1. HP Output Server instance installation
4.1.0.0.0.20
In step 10, the setup detects and displays the available HP Output Management
product patches.
For example:
1. HP Output Server 4.1.0.2.0.1
138
Chapter 5

Removing a patch from a UNIX host

This section describes how to back out a patch from an HP Output Server installation
hierarchy on a UNIX host.
Service Pack installations automatically commit previous patch installations. When
removing a Service Pack, you can back out only one installation level. For example, if
you install Service Pack 4.1.0.1 and then install Service Pack 4.1.0.2, you can back out
only to Service Pack 4.1.0.1.
fixed in Hotfix 1.
Backing out a hotfix backs out all previously applied hotfixes. For example, if you
install Hotfix 4.1.0.2.1 and then install Hotfix 4.1.0.2.2, you can back out only to HP
Output Server 4.1.0.2 but all previous hotfixes are removed.
multiple hosts, remove patches within the same maintenance
servers. For client-only systems, remove patches within the
same maintenance window (recommended) or within a
subsequent maintenance window and either before or after
removing it from the hosts that run the HP Output Server
servers.
Removing a patch from an HP Output Server standard installation

on a UNIX host
To remove a patch from an HP Output Server standard installation on a UNIX host,
perform the following steps:
1.
HP Output Server
Log in as root or the user specified during the installation as the owner of the
installed files, to the host where HP Output Server is running.
139
Chapter 5
2.
3.
Shell
Command
Bourne or Korn
Stop all programs that monitor the HP Output Server installation from which you
want to uninstall patches. On multiple-domain hosts, some programs may be
monitoring processes that are managed by other HP Output Server instances.
For example, HP Output Management for HP Software Operations and dzl_epod
monitor HP Output Server processes and should be stopped.
4.
Stop all HP Output Management applications that depend on the HP Output Server
installation on the host. Some applications require a product-specific shutdown
command. In general, these applications are not restarted automatically; you must
restart these applications manually. For more information, see the documentation
for your HP Output Management applications.
Management.
5.

6.

perl patch.pl
components
components
140
7.
Select option 2.
8.
Chapter 5

The default path is installInstDir.

components for backout.
For example:
1. HP Output Server standard installation 4.1.0.2.0.1
9.
Enter the number corresponding to the HP Output Management product

components you want to back out or enter q to quit the setup.
10. When the system prompts you to restart the servers after the patch backout is
complete, select one of the following:
-
Accept the default n.

NOTE: If you choose not to restart the servers when the patch
backout is complete, you must restart the servers manually
before using HP Output Server.
Select y, if you want the patch utility to stop and subsequently restart all
servers.
After the patch backout is successfully completed, the system displays the following
message:
Patch backout has been successfully completed.
You are now running HP Output Server standard
The patch log file is located at installInstDir/patch.log.
HP Output Server
141
Chapter 5
Removing a patch from an HP Output Server binaries installation

on a UNIX host
NOTE: For a split installation of HP Output Server, you must back
out the HP Output Server binaries and instance to the same
patch level.
binaries before backing out the binaries.
To remove a patch from an HP Output Server binaries installation on a UNIX host,
1.
Log in as root or as the owner of the installed HP Output Server binaries.
2.
Stop all programs that monitor the HP Output Server installation from which you
want to uninstall patches. On multiple-domain hosts, some programs may be
monitoring processes that are managed by other HP Output Server instances.
For example, HP Output Management for HP Software Operations and dzl_epod
monitor HP Output Server processes and should be stopped.
3.
Stop all HP Output Management applications that depend on the HP Output Server
installation on the host. Some applications require a product-specific shutdown
command. In general, these applications are not restarted automatically; you must
restart these applications manually. For more information, see the documentation
for your HP Output Management applications.
Management.
4.

5.

perl patch.pl
142
Chapter 5


components
components
6.
Select option 2.
7.

The default path is installBinDir.
components for backout.
For example:
1. HP Output Server binaries installation 4.1.0.2.0.1
8.
Enter the number corresponding to the HP Output Management product

components you want to back out or enter q to quit the setup.
After the patch backout is successfully completed, the system displays the following
message:
You are now running HP Output Server binaries
The patch log file is located at installBinDir/patch.log.
HP Output Server
143
Chapter 5
Removing a patch from an HP Output Server instance installation

on a UNIX host
NOTE: For a split installation of HP Output Server, you must back
out the HP Output Server binaries and instance to the same
patch level.
binaries before backing out the binaries.
To remove a patch from an HP Output Server instance installation on a UNIX host,
perform the steps mentioned in Removing a patch from an HP Output Server standard
installation on a UNIX host on page 139. However, note the following exceptions:
In step 1, you must log in as root or as the owner of the installed HP Output
Server instance.
In step 8, setup detects and displays the installed HP Output Management product
component as in the following example:
For example:
1. HP Output Server instance installation 4.1.0.2.0.1
After the patch backout is successfully completed, the system displays the
following message:
You are now running HP Output Server instance
The patch log file is located at installInstDir/patch.log.
144
Chapter 5

Installing a patch on a Windows host

The following section describes how to install a patch for HP Output Server on a
Windows host.
Service Pack installations are cumulative. For example, if you apply a Service Pack that
updates HP Output Server to 4.1.0.3, it includes defect fixes and enhancements in
Service Packs 4.1.0.2 and 4.1.0.1.
fixed in Hotfix 1.
You must apply hotfixes in order. For example, if you apply Hotfix 3 only, but later
determine that you also need to apply Hotfix 2, you must remove Hotfix 3 before
applying Hotfix 2.
The following requirements and limitations may apply to your environment:
To extract files from the patch file, you must have a PKZIP file extraction utility,
for example, WinZip.
HP Output Server is not supported on a system acting as a Terminal Server.
You must stop all programs that monitor HP Output Server processes. For example,
the HP Output Management for HP Software Operations and dzl_epod monitor
HP Output Server processes and must be stopped before you proceed.
To install a patch on a Windows host, perform the following steps:

1.
Log in as a user with administrator privileges to the host on which HP Output

Server is installed.
2.
Stop all programs that monitor HP Output Server processes.
3.
Stop HP Output Management applications that depend on the HP Output Server

installation you are patching. Some applications require that you run a
product-specific shutdown command. In general, these applications are not
restarted automatically; you must restart these applications manually. For more
information, see the documentation for your HP Output Management applications.
Management.
HP Output Server
145
Chapter 5
4.
http://www.hp.com/go/hpsoftwaresupport, extract the Service Pack
files, and then save into a temporary directory.
5.
Extract the Service Pack files into a temporary directory.

NOTE: Use the original subdirectory structure when extracting the
Service Pack files into a temporary directory.
6.
Run the setup.exe program from the patch files.

The HP Output Server Patch Wizard screen appears.
7.
Click Next.
The Review Settings dialog box provides a summary of HP Output Server
installation settings.
NOTE: The setup program applies the patch to the detected
components on the system.
8.
If the settings are correct, click Next. If the settings contain incorrect information,
click Cancel and quit the setup program. Make the necessary modifications before
running the setup program again.
If HP Output Server servers are running, the setup program prompts you to stop all
HP Output Server servers.
9.
Click Yes.
NOTE: If you click No, the setup program quits.
10. In the HP Output Server Patch Installation Complete dialog box, click Finish.
146
Chapter 5

Removing a patch from a Windows host
The patch installation is complete.

NOTE: The patch.pl script determines the MySQL database
version before executing the patching process. If the current
version of the database is less than the recommended
version, an error message is displayed. The patching process
is executed on getting the confirmation when you select the
yes option, else it is aborted.

This section describes how to back out patches for HP Output Server 4.0 on Windows
hosts.
Service Pack installations automatically commit previous patch installations. When
removing a Service Pack, you can back out only one installation level. For example, if
you install Service Pack 4.1.0.1 and then install Service Pack 4.1.0.2, you can back out
only to Service Pack 4.1.0.1.
fixed in Hotfix 1.
Backing out a hotfix backs out all previously applied hotfixes. For example, if you
install Hotfix 4.1.0.2.1 and then install Hotfix 4.1.0.2.2, you can back out only to HP
Output Server 4.1.0.2 but all previous hotfixes are removed.
multiple hosts, remove patches within the same maintenance
servers.
To remove a patch on a Windows host, perform the following steps:
HP Output Server
1.
Log in as a user with administrator privileges to the host on which HP Output

2.
Stop all programs that monitor HP Output Server processes.
3.
Stop HP Output Management applications that depend on the HP Output Server

installation you are patching.
147
Chapter 5
Some applications require that you run a product-specific shutdown command. In

general, these applications are not restarted automatically; you must restart these
Management.
4.
Open the Windows Add or Remove Programs tool.
5.
Select HP Output Server Version 4.1 Service Pack x (where x is the Service Pack
number) from the list, and then click Change/Remove.
6.
In the Uninstall Options screen, select Backout HP Output Server Service Pack
x, and then click Next.
7.
If the setup program prompts you to stop all HP Output Server servers, click Yes.
NOTE: If you click No, the program quits.
After the patch backout is complete, the HP Output Server Patch Backout
Complete dialog box appears.
8.
148
Click Finish to complete the patch backout.
Chapter 6
Configuring HP Output Server

This chapter describes tasks that you can perform to configure HP Output Server.
Before you configure HP Output Server, be sure that you have completed the following:
Review configuration options in Chapter 1, Planning the installation on page 1.
Configure the database connection for HP Output Server.
Be able to log in as the root user on UNIX or as a user with administrator privileges
on Windows on all hosts on which you plan to run servers.
This chapter describes the following configuration tasks:
HP Output Server
Setting environment variables
Configuring servers
Configuring user authentication and authorization
Configuring interdomain delivery
Configuring the LPR Gateway
Creating a delivery pathway
Testing the configuration
Switching the HP Output Server binaries used by an HP Output Server instance
149
Chapter 6

When you install HP Output Server, the installation program creates files that contain
environment variables specific to your HP Output Server installation. The variables
define file and directory pathways that HP Output Server requires to operate.
Post-installation prerequisites for HP-UX operating systems

If you have installed HP Output Server 4.1 with MySQL as the back-end database on
HP-UX 11.11 PA-RISC, HP-UX 11.23 PA-RISC or HP-UX 11.31 PA-RISC operating
systems, perform the following steps before configuring HP Output Server destinations:
1.
Stop the HP Output Server servers, if you have already configured them as a part of
the HP Output Server installation.
2.
Go to the directory $DAZEL_HOME/etc.
3.
In the odbc.ini file, add the following line:

"option=256"
4.
Restart the HP Output Server servers.

NOTE: These steps are required to ensure that no deadlock issues
occur under high loads on the HP-UX PA-RISC operating
system.
NOTE: The preceding steps are not required for other operating
systems.
For a list of HP Output Server environment variables, their settings, and a description of
methods for setting these variables, see Appendix B, Environment variables in HP
Configuring HP Output Server servers

If you installed HP Output Server by joining an existing domain or by creating a new
domain, you must configure HP Output Server servers manually with the
config_server command. When you configure a server with the
config_server command, the server starts automatically by default. For detailed
information about using the config_server command, see the System
Administrators Command Reference for HP Output Server.
150
Chapter 6 Configuring HP Output Server


HP Output Server allows authorized users to submit jobs, manage destinations, control
servers, and perform other types of tasks. The Privilege Manager (PM) maintains a
database of user and group permissions that determines the types of tasks a user or
group may perform. Although the PM grants, revokes, and manages user and group
permissions, the PM does not perform user authenticationdetermining and verifying
the identity of a particular user. After installing HP Output Server, you can configure the
PM to use a different type of user authentication, and you modify the permissions for
users and groups.
Setting the authentication mode

You use the config_server command to set the authentication mode for HP Output
Server. The authentication mode determines how the PM checks the identity of users
and authorizes their activities, such as submitting jobs or managing destinations. The
PM supports two types of user authentication: Dazel ID mode and UNIX ID mode.
Dazel ID mode is the default type of user authentication, which relies on the
authentication mechanisms within external environments, such as the Windows
operating system or SAP, to ensure a users identity. UNIX ID mode obtains user and
group information from the underlying UNIX operating system on which HP Output
When you first install HP Output Server, you set the authentication mode only if you
need to change the default mode from Dazel ID to UNIX ID.
NOTE: If you change the default ID mode to UNIX ID mode, you
cannot use the pm_edit command.
To set the authentication mode for HP Output Server, enter the following command:
config_server -u -x"-pm-id-mode authenticationMode"
pmName
where authenticationMode is the authentication mode you want to use, and pmName is
the name of the PM server for the installation. The valid values for -pm-id-mode are
unix and dazel.
Modifying user and group permissions

You use the pm_edit command to grant and revoke permissions for users or groups to
be able to do the following:
HP Output Server
151
Chapter 6
Submit jobs
Receive notices
Manage destinations
Control servers
Use commands
HP Output Server includes a list of default groups with a set of default permissions. For
example, the dazel_guest group allows unauthorized users to submit jobs, manage
their own jobs, view the status of servers, and perform other tasks. The default groups
for HP Output Server include:
dazel_guest
dazel_user
dazel_support
dazel_admin
dazel_superuser
dazel_server
dazel_appl
Each group has a different type and a different level of permissions. For example, the
dazel_superuser group can perform all tasks, and the dazel_server group
gives servers permission to communicate and exchange information between
themselves.
After installing HP Output Server, use the pm_edit command to change the default set
of user and group permissions and establish your own authorization policies. Changing
the default set of permissions allows you to better manage and control access to HP
Output Server resources as well as better track system usage. For example, you can add
a user to the default dazel_admin group by entering the following command:
pm_edit -p dazel_admin group add user jjschmidt
This sample command gives the user named jjschmidt the same level of
permissions as other members of the dazel_admin group, so the user can administer
HP Output Server. You can also add your own groups and grant each group a specific
set of permissions. For example, the following command creates a new group called
helpdesk:
pm_edit group create helpdesk
152

After you create a group, create a capabilities list for the group so you can grant
permissions to the group. For example:
pm_edit -p helpdesk add cl
You can then add permissions for the group. For example, you can explicitly grant the
helpdesk group permission to shut down the servers for HP Output Server:
pm_edit -p helpdesk -t IDS_SERVERS
-o ".*" add perm SHUTDOWN
After you are finished granting users and groups the permissions you want to assign to
them, reload the permissions by entering the following command:
pm_edit m i all
The preceding command clears the cache and reloads permissions for HP Output
Server.
The System Administrators Guide for HP Output Server provides more information
about how to use the pm_edit command to grant and revoke permissions for users and
groups.

Configuring interdomain delivery enables users in one HP Output Server domain to
submit jobs to destinations in another HP Output Server domain. An HP Output Server
domain is a stand-alone configuration that includes the following minimum set of
servers:
HP Output Server
SSM (Windows only)
NM
PM
AIM
CM
EM (at least one)
DLM (at least one)
JQM (at least one)
DSM (at least one)
153
Chapter 6
Multiple HP Output Server domains cannot share servers, queues, logical destinations,
or physical destinations directly. However, users in one HP Output Server domain can
deliver jobs to destinations in another HP Output Server domain if interdomain delivery
has been configured. For information about configuring interdomain delivery, see the
System Administrators Guide for HP Output Server.

The LPR Gateway is a replacement for the standard print spooler on UNIX and
Windows systems. As an interface to HP Output Server, the LPR Gateway accepts
requests from clients that use the LPR set of commands. The LPR Gateway lets users
submit and manage jobs that are sent to HP Output Server. For more information about
configuring the LPR Gateway, see the System Administrators Guide for HP Output
Server.

You create a delivery pathway so users can submit jobs to an output device. A delivery
pathway consists of the following objects:
A logical destination in a delivery pathway identifies an output device. When an

end user submits a job, HP Output Server handles the request and creates subjobs
for the logical destination. As a part of delivering information, a logical destination
forwards a subjob to the queue that is associated with one or more output devices.
A queue receives a group of ordered subjobs from a logical destination. A queue

schedules access to an output device and forwards the subjobs to an awaiting
physical destination.
A physical destination represents an actual output device, such as a printer, a fax

machine, or a pager. A physical destination receives a subjob from a queue and
processes the delivery request by handling communication with the associated
output device. A physical destination can also change a subjob by making any
necessary format or layout changes, such as translating text to PostScript or
changing the duplex mode for a device to meet a subjobs particular specifications.
A delivery pathway may also contain multiple logical destinations and multiple physical
destinations.
154

You can create a delivery pathway from the command-line interface (CLI) or with HP
Output Explorer, a Windows-based suite of applications that are designed for the needs
of system administrators, operators, and help desk personnel who use and support HP
Output Server. The remainder of this section shows you how to use the CLI to create a
delivery pathway.
Before you begin

Before you create a delivery pathway, consider the following:
To ensure proper configuration of delivery pathway objects, you must use the
-managing-server attribute when you create a logical destination, physical
destination, or queue.
HP Output Server includes device templates that make it easier and reduce the time
it takes to create a delivery pathway from the command line. Use the
-copy-from attribute to copy a template when creating a delivery pathway
object from a template.
For information about creating advanced delivery pathways, see the System
Administrators Guide for HP Output Server.
Using the -managing-server attribute

The -managing-server attribute is required when you create a logical destination,
a queue, or a physical destination. The -managing-server attribute specifies the
server that manages the object you create.
When you create a logical destination or a queue, specify the related Job and Queue
Manager (JQM). For example:
pdcreate -c d -x"-copy-from postscript_template
-managing-server my_jqm -queue-supported
my_queue" my_printer
When you create a physical destination, specify the Destination Manager (DSM). For
example:
pdcreate -c d -x"-queue-supported my_queue
-copy-from hp_9000dn_ps_tcp_template
-tcp-host 172.16.0.2
-managing-server my_dsm" p_my_printer
If you do not specify the -managing-server attribute when creating a delivery
object, HP Output Server creates the object, but the object cannot deliver a job until you
properly set the attribute.
HP Output Server
155
Chapter 6
Using templates
A template is a text file that contains a pre-configured set of attributes and a default
value for each attribute. The templates help you quickly create delivery objects by
providing you with the most frequently used configurations. The default queue
templates give you examples of different types of scheduling algorithms. The logical
destination templates define different types of devices, such as a printer, a fax, or a
modem. The templates for physical destinations offer a default configuration for
specific types of hardware devices. Although creating a delivery object based on a
template saves you time and effort, you may need to customize the new object for your
environment.
To view a list of template names for a delivery object, use the commands in the
following table.
Table 6-1. Commands for listing templates
156
Delivery Object
Command
logical destination
pdls -c d -a none -x"-template true

-printer-realization 0" ids_ccm:
physical destination

queue
pdls -c q -a none -x"-template true" ids_ccm

To view the current settings for a particular template, use the commands in the
following table.
Table 6-2. Commands for listing a templates settings
Delivery Object
Command
logical destination
pdls -c d -a all ids_ccm:template_name
pdls -c d -a all ids_ccm:template_name
queue
pdls -c q -a all ids_ccm:template_name
For more information about setting attributes for delivery objects and customizing
templates, see the System Administrators Guide for HP Output Server.
Using the -copy-from attribute

You can use the -copy-from attribute to create a new delivery object by copying the
attributes and values from a template. For example, the following command lets you
create a new physical destination for a fax machine:
pdcreate -c d -x"-managing-server my_dsm
-queue-supported fax_queue -tcp-host 172.16.0.4
-tcp-data-port 2001
-fax-phone-number-default 4745170
-copy-from generic_fax_tcp_template" my_fax
This sample command creates a physical destination based on a generic template for a
fax as specified by the -copy-from attribute.
The -copy-from attribute also lets you create multiple copies of an object at one
time. The following example creates three new physical destinations (her_printer,
his_printer, and their_printer) based on an existing printer named
my_printer:
pdcreate -c d -x"-copy-from my_printer"
her_printer his_printer their_printer
Creating a queue
To create a queue for a delivery pathway, perform the following steps:
1.
To list the available templates for a queue, use the following command.
pdls -c q -a none -x"-template true" ids_ccm:
2.
HP Output Server
Select the template you want to use.
157
Chapter 6
3.
The batch_queue_template processes jobs according to priority.

Higher-priority jobs are processed before lower-priority jobs.
The shortest_job_first_queue_template processes jobs

according to their size in bytes. Smaller jobs are processed before larger jobs.
The fifo_queue_template processes jobs in chronological order. The

first job that enters the queue is the first job to be processed.
Create a queue with the selected template. For example:

pdcreate -c q -x"-copy-from batch_queue_template
-managing-server my_jqm" q_ps_printer
This command creates a new queue called q_ps_printer and assigns the queue
the same attributes and values as listed in the default batch_queue_template.
Creating a logical destination

To create a logical destination for a delivery pathway, perform the following steps:
1.
To list the available templates for logical destinations, use the following command:
2.
3.
Create a logical destination with the selected template. For example:

pdcreate -c d -x"-queue-supported q_ps_printer
-copy-from postscript_template
-managing-server my_jqm" l_ps_printer
This command creates a logical destination called l_ps_printer that has the
same settings as the default postscript_template.
Creating a physical destination

To create a physical destination for a delivery pathway, perform the following steps:
1.
Verify that the hardware device is connected and ready to use.
2.
To list the available templates for physical destinations, use the following
command:
3.
158

4.
Create a physical destination with the selected template. For example:

pdcreate -c d -x"-queue-supported q_ps_printer
-copy-from hp_9000dn_ps_tcp_template
-tcp-host 172.16.0.2
-managing-server my_dsm" p_ps_printer
This command creates the physical destination called p_ps_printer with the
hp_9000dn_ps_tcp_templatea template for a PostScript printer that
connects through TCP/IP.

After you have configured HP Output Server, use the steps in this section to test your
configuration.
1.
Deliver a document to an output device with the following command:

pdpr -d logicalDestination file
2.
To check the status of the job, enter the following command:

pdls -c job -a all jobID
The pdls command returns information the specified job.
3.
When you see the following attribute values reported, verify that the job has been
delivered successfully to the physical destination.
-current-job-state
-job-completion-status
:retained
:success
Troubleshoot unsuccessful attempts by checking the following:

1.
To verify that all servers are running, enter the following command:
server_status
2.
If any server is not running, use the start_server command to re-start it.
start_server -t all
3.
To verify that the queue has a logical and physical destination associated with it,
pdls -c q -a all queueName
HP Output Server
159
Chapter 6
4.
If a logical destination is not assigned to the queue

(-logical-printers-assigned attribute) or if a physical destination is not
registered with the queue (-physical-printers-registered attribute),
see Creating a logical destination on page 158 and Creating a physical
destination on page 158 for instructions.
5.
Enable logging for the DSM. In the following command, path/logFile is the
directory path and file name of the log file and server is the name of the DSM (for
example, installInstDir/var/log/!{server-name}!.log).
config_server -u -x"-server-log-level terse
-server-uses-syslog false -server-log-file
path/logFile" server
stop_server -t server
start_server -t server
6.
If the server configuration fails, follow these steps:

i.
Locate the odbcinst.ini file in the installInstDir/etc directory.
ii.
Change the Trace field value to Yes.
iii. Perform the server configuration again and re-test the configuration.
iv. Access the odbc.log file to trace errors.
The log file is located in the path noted in the TraceFile field. It is usually
set to the file installInstDir/var/log/odbc.log.
NOTE: The size of the odbc.log file increases rapidly with the
Trace field value set to Yes. Therefore, disable the Trace
field value after rectifying the problem.
7.
If the test still fails after performing the troubleshooting, contact Customer Support.
Changing log level

You can change the log level of HP Output Management product deployed components
such as HP Web Services for Output Server, UPDGateway, and HP Output Management
Web Console by changing the priority value in the jboss-log4j.xml log file
located at installInstDir/var/jboss/server/default/conf directory.
160

Switching the HP Output Server binaries used by an

HP Output Server instance
A utility is provided in HP Output Server 4.1 to use different HP Output Server binaries
with an HP Output Server instance. After you install HP Output Server, you can use this
utility to switch the HP Output Server binaries used by an instance to a different set of
binaries or have multiple instances referring to the same HP Output Server binaries.
NOTE: This utility is applicable only on UNIX platforms.
To change the HP Output Server binaries used by an HP Output Server instance,
1.
Log in to the system as the owner of the HP Output Server instance.

NOTE: The owner of the HP Output Server instance must belong to
the same user group as the owner of the HP Output Server
binaries that you want to use, and have the read and execute
permissions on HP Output Server binaries.
2.
3.
Shell
Command
source
Bourne or Korn
Change the directory to the location of the hpom_switch_binary.pl script by

entering the following command:
installBinDir/bin
4.
Run the script by entering the following command:

perl hpom_switch_binary.pl -i <required installBinDir>
Where <required installBinDir> is the path of the HP output server binaries that you
want to use with the instance.
5.
HP Output Server
Restart all servers.
161
Chapter 6
162
Chapter 7
Backing up and restoring HP Output

Server
This chapter describes how to back up and restore HP Output Server 4.1, including the
HP Output Server database stored in an installation of MySQL for HP Output
Management or an Oracle database instance. Backing up HP Output Server 4.1 also
backs up HP Output Manager for SAP 4.1 and HP Output Distributor 4.1.
HP Output Server stores program files in installBinDir and configuration files in
installInstDir, the installation paths for your HP Output Server binaries and instance
installations respectively. HP Output Server also stores configuration settings and
records in databases. Backing up and restoring an existing HP Output Server installation
includes the following tasks:
Backing up and restoring the HP Output Server program files in installBinDir and
configuration files in installInstDir.
NOTE: The installBinDir variable refers to the location of the HP
Output Server binaries and the installInstDir variable refers
to the location of HP Output Server instance in case of a split
installation of HP Output Server. For a standard installation,
that is, where the binaries and instance are installed at the
same location, the installBinDir or the installInstDir variable
refers to the location of your HP Output Server installation.
HP Output Server
Backing up and restoring the MySQL or Oracle database server
163
Chapter 7
Backing up and restoring HP Output Server
Before you begin
The following sections describe how to perform these tasks.

NOTE: If HP Output Server and MySQL for HP Output
Management are installed in the same directory on a UNIX
host, see Backing up and restoring same-directory
installations (UNIX only) on page 176.
For assistance with backup issues or configurations not addressed in this chapter,
contact your Implementation and Integration Services representative or Customer
Support.
Before you begin

Before you back up your HP Output Server installation, note the following
requirements:
164
You must create a backup of your current HP Output Server installation on each
host. Backing up HP Output Server automatically backs up HP Output Manager for
SAP 4.1 and HP Output Distributor 4.1.
The target directory you specify for a backup must contain sufficient space for the
backup.
You must stop all programs that monitor or depend on the HP Output Server
installation before creating a backup. In general, these applications are not restarted
automatically. You must restart these applications manually after restoring HP
Output Server from a backup.
To create a reliable backup copy of your HP Output Server installation on a

Windows host, HP recommends that you back up the entire Windows system.
Chapter 7
Backing up HP Output Server and MySQL on a UNIX host
Backing up HP Output Server and MySQL on a

UNIX host
CAUTION: The information in this section assumes that HP Output
Server and MySQL for HP Output Management are
installed in separate installation directories or on
separate hosts. If HP Output Server and MySQL for HP
Output Management are installed in the same directory
on a UNIX host, see Backing up and restoring
same-directory installations (UNIX only) on page 176.
Task 1: Backing up program and configuration files (UNIX host)

To back up your HP Output Server program and configuration files on a UNIX host,
NOTE: The following procedure applies to HP Output Server
standard and split installations. For a split installation, you
must back up HP Output Server binaries and instance
separately.
1.
If you have not already done so, log on as the root user.
2.
Shell
Command
Bourne or Korn
3.
Stop all programs that monitor or depend on the HP Output Server installation that
you want to back up.
4.
Stop the HP Output Server servers by entering the following command:

stop_server -t all
HP Output Server
165
Chapter 7
5.
For backing up the HP Output Server binaries, perform the following steps:
NOTE: For a standard installation of HP Output Server, perform
only step 5. For a split installation of HP Output Server,
perform step 5 and step 6.
i.
Change to the HP Output Server binaries installation directory by entering the

following command:
cd installBinDir
ii.
Back up and compress the existing HP Output Server binaries by using the
tar utility shipped with HP Output Server 4.1. Enter the following command:
For Linux operating system:

installBinDir/bin/tar -cvf - .|gzip > /Binpath/fileNameBin.gz
For other UNIX operating systems:

installBinDir/bin/tar -cvf - .|compress >
/Binpath/fileNameBin.tar.Z
where Binpath is the target directory for the HP Output Server binaries backup
and fileNameBin is a name for the HP Output Server binaries backup file.
NOTE: For an HP Output Server standard installation, the Binpath
variable is the target directory for the HP Output Server
installation and fileNameBin is a name for the HP Output
Server backup file.
6.
For backing up the HP Output Server instance, perform the following steps:
i.
Change to the HP Output Server instance installation directory by entering the

following command:
cd installInstDir
ii.
Back up and compress the existing HP Output Server instance by using the
tar utility shipped with HP Output Server 4.1. Enter the following command:

installBinDir/bin/tar -cvf - .|gzip > /Instpath/fileNameInst.gz

/Instpath/fileNameInst.tar.Z
166
Chapter 7
where Instpath is the target directory for the HP Output Server instance backup
and fileNameInst is a name for the HP Output Server instance backup file.
Task 2: Backing up HP Output Server MySQL database (UNIX host)

This section describes how to back up HP Output Server database and tables in an
installation of MySQL for HP Output Management on a UNIX host. It provides
instructions for performing the following types of backups:
Backing up the database
Backing up specified tables within the database
MySQL for HP Output Management must be running to back up HP Output Server

database and tables.
CAUTION: Before you create a copy of an HP Output Server
database, ensure that all HP Output Server servers are
stopped.
NOTE: In HP Output Server 4.1, when you install MySQL provided
with HP Output Server as the database, the my.cnf
configuration file is located in $DAZEL_HOME/etc folder
and the MySQL binaries are installed in the
$HPOM_INSTALL/share/mysql/5.0.24 folder.
Backing up the database

You can create a backup of an HP Output Server database, including all tables and
records in the database, by entering the following commands:
cd mySQLinstallDir/bin
./mysqldump --defaults-file=mySQLinstallDir/my.cnf
--quote-names --add-drop-table --quick
--extended-insert databaseName
--result-file=/path/fileName --user=username
--password=password
where
-
HP Output Server
mySQLinstallDir is the location of the MySQL for HP Output Management

installation.
167
Chapter 7
Restoring HP Output Server and MySQL on a UNIX host
databaseName is the name of an HP Output Server database, for example,

hpomdb_dazel_d_4009.
path is the location you choose for saving the backup of the database.
fileName is a name for the file where the database and its contents will be
saved.
username is the name of the MySQL database owner.
password is the password of the MySQL database owner.
Backing up specified tables within the database

You can back up individual tables in a database using the preceding commands for
backing up a single database and by specifying the names of the tables to back up. This
backup option can be used when, for example, your jobs table for a JQM is large and
has many retained jobs that are about to expire. Backing up all the tables in that
database, except for the jobs table, reduces the size of the backup.
The following example creates a backup of tables named dlm_00, em_clients and
em_subscriptions in the database named hpomdb_dazel_d_4009. MySQL
for HP Output Management is installed in /usr/local/mysql and the backup file
is located at /mybackup/myDBtables.
cd /usr/local/mysql/bin
./mysqldump --defaults-file=/usr/local/mysql/my.cnf
--extended-insert hpomdb_dazel_d_4009 dlm_00
em_clients em_subscriptions
--result-file=/mybackup/myDBtables --user=username
--password=password
Restoring HP Output Server and MySQL on a UNIX

host
This section describes how to restore HP Output Server from a backup on a UNIX host.
This section assumes that you have created a backup of HP Output Server by
performing the steps in Backing up HP Output Server and MySQL on a UNIX host
on page 165.
Restoring HP Output Server includes the following tasks:
1.
168
Re-creating the MySQL database from the backup
Chapter 7

2.
Restoring the HP Output Server program and configuration files from the backup
Task 1: Re-creating the HP Output Server MySQL database (UNIX

host)
Before you restore the program and configuration files for HP Output Server, you fix or
re-create the database.
CAUTION: Before you re-create HP Output Server databases from a
backup, ensure that all HP Output Server servers are
stopped.
Re-creating the database or specified tables in the database

Enter the following commands to re-create the database or tables:
./mysql --defaults-file=mySQLinstallDir/my.cnf
databaseName < /path/fileName --user=username
--password=password
where
HP Output Server

installation.
databaseName is the name of the HP Output Server database in your backup,

for example, hpomdb_dazel_d_4009.
path is the location you chose for saving a copy of the database or tables.
fileName is the name of the backup file that you created for the database or
tables.
169
Chapter 7
Task 2: Restoring program and configuration files (UNIX host)

To restore an existing installation of HP Output Server on a UNIX host, perform the
following steps:
standard and split installations. For a split installation you
must restore HP Output Server binaries and instance
separately.
1.
If you have not already done so, log in as the root user.
2.
On AIX hosts, run the slibclean command to ensure that library files are not in
use.
3.
For restoring the HP Output Server binaries, perform the following steps:
i.
Change to the HP Output Server binaries installation directory by entering the

following command:
cd installBinDir
NOTE: For an HP Output Server standard installation, substitute the
installBinDir variable with the location of your HP Output
Server installation.
ii.
Copy the tar utility shipped with HP Output Server 4.1 to a known directory
on your system and use the same for uncompressing the backup copy of the HP
Output Server binaries files. Enter the following command:
cp -p installBinDir/bin/tar tar_Binpath/tar
Where tar_Binpath is the target directory for copying the tar utility shipped
with HP Output Server 4.1.
iii. Restore the previous installation with the backup copy of the files by entering
the following command:
-

zcat fileNameBin.gz | tar_Binpath/tar -xvf -
170
Chapter 7


zcat fileNameBin.Z | tar_Binpath/tar -xvf Where fileNameBin is the name of the HP Output Server binaries backup file
and tar_Binpath is the directory of the tar utility shipped with HP Output
Server 4.1 on your system.
NOTE: For an HP Output Server standard installation, fileNameBin
is the name for the HP Output Server backup file.
4.
For restoring the HP Output Server instance, perform the following steps:
i.
Change to the HP Output Server instance installation directory by entering the

following command:
cd installInstDir
ii.
on your system and use the same for uncompressing the backup copy of the HP
Output Server instance files. Enter the following command:
cp -p installBinDir/bin/tar tar_Instpath/tar
Where tar_Instpath is the target directory for copying the tar utility shipped
iii. Restore the previous installation with the backup copy of the files by entering
the following command:
-

zcat fileNameInst.gz | tar_Instpath/tar -xvf -

zcat fileNameInst.Z | tar_Instpath/tar -xvf Where fileNameInst is the name of the HP Output Server instance backup file
and tar_Instpath is the directory of the tar utility shipped with HP Output
Server 4.1 on your system.
5.
HP Output Server
Shell
Command
Bourne or Korn
171
Chapter 7
Backing up HP Output Server and MySQL on a Windows host
6.
Start the HP Output Server servers by entering the following command:

start_server -t all
Backing up HP Output Server and MySQL on a

Windows host
Backing up HP Output Server includes the following tasks:
1.
Backing up the HP Output Server program and configuration files in installDir
2.
Backing up the configured MySQL database
Task 1: Backing up program and configuration files (Windows

host)
This section provides instructions for backing up the program and configuration files
located in the installation directory of an HP Output Server installation on a Windows
host.
NOTE: As a more reliable alternative to backing up only the
installation directory of your HP Output Server installation,
HP recommends that you back up the entire Windows
system. For more information or assistance, contact
Customer Support or your Implementation and Integration
Services representative.
To back up your HP Output Server program and configuration files on a Windows host,
1.
If you have not already done so, log in as an administrator.
2.
Open a command prompt.
3.
Stop all programs that monitor or depend on the HP Output Server installation for
which you are creating a backup.
4.

stop_server -t all
172
Chapter 7
Backing up HP Output Server and MySQL on a Windows host
5.
Change to the installation directory for HP Output Server by entering the following
command:
cd installDir
The default location for this directory is C:\HP\OM.
6.
Use a compression and file packaging utility shipped with HP Output Server 4.1 to
back up the existing installation.
Task 2: Backing up HP Output Server MySQL database (Windows

host)
HP Output Server stores configuration settings and records in a single MySQL database.
This section describes how to back up HP Output Server database and tables in an
installation of MySQL for HP Output Management on a Windows host. It provides
instructions for performing the following types of backups:
Backing up a database
Backing up specified tables within a database
MySQL for HP Output Management must be running to back up HP Output Server

databases and tables.
CAUTION: Before you create a copy of HP Output Server
databases, ensure that all HP Output Server servers are
stopped.
Backing up a database
You can create a backup of an HP Output Server database, including all tables and
records in the database, by entering the following commands:
cd mySQLinstallDir\bin
.\mysqldump --defaults-file=mySQLinstallDir\my.cnf
--extended-insert databaseName
--result-file=\path\fileName --user=username
--password=password
where
-
HP Output Server

installation.
173
Chapter 7
Restoring HP Output Server and MySQL on a Windows host
databaseName is the name of an HP Output Server database, for example,

hpomdb_dazel_d_4009.
path is the location you choose for saving the backup of the database.
fileName is a name for the file that will save a copy of the database and its
contents.
Backing up specified tables within a database

You can back up individual tables in a database using the preceding commands for
backing up the database and by specifying the names of the tables to back up. This
backup option can be used when, for example, your jobs table for a JQM is large and
has many retained jobs that are about to expire. Backing up all the tables in that
database, except for the jobs table, reduces the size of the backup.
The following example creates a backup of tables named dlm_00, em_clients and
em_subscriptions in a database named hpomdb_dazel_d_4009. MySQL for
HP Output Management is installed in C:\mysql and the backup file is located at
C:\mybackup\myDBtables.
cd C:\mysql\bin
.\mysqldump --defaults-file=C:\mysql\my.cnf
--extended-insert hpomdb_dazel_d_4009 dlm_00
em_clients em_subscriptions
--result-file=C:\mybackup\myDBtables
--user=username --password=password
Restoring HP Output Server and MySQL on a

Windows host
This section assumes that you have created a backup of HP Output Server by
performing the steps in Backing up HP Output Server and MySQL on a Windows
host on page 172.
174
Chapter 7
Restoring HP Output Server and MySQL on a Windows host
Restoring HP Output Server includes the following tasks:

1.
Re-creating the MySQL database from the backup
2.
Restoring the HP Output Server program and configuration files from the installDir
backup
The following sections describe how to perform these tasks:
Task 1: Re-creating the HP Output Server MySQL database

(Windows host)
Before you restore the program and configuration files for HP Output Server, you fix or
re-create the database.
CAUTION: Before you re-create HP Output Server databases from a
backup, ensure that all HP Output Server servers are
stopped.
Re-creating the database or specified tables in the database

If you created a backup of a database or specified tables in a database, enter the
following commands to re-create the database or tables:
cd mySQLinstallDir\bin
.\mysql --defaults-file=mySQLinstallDir\my.cnf
databaseName < \path\fileName --user=username
--password=password
where
HP Output Server

installation.
databaseName is the name of the HP Output Server database in your backup,

for example, hpomdb_dazel_d_4009.
path is the location you chose for saving a copy of the database or tables.
fileName is the name of the backup file that you created for the database or
tables.
175
Chapter 7
Backing up and restoring same-directory installations (UNIX only)
Task 2: Restoring program and configuration files (Windows host)

To restore an existing installation of HP Output Server on a Windows host, perform the
following steps:
1.
If you have not already done so, log in as an administrator.
2.
Install HP Output Server from the product package.
3.
Install any patches you previously installed for HP Output Server.
4.
Open a command prompt.
5.

stop_server -t all
6.
Change to the installation directory for HP Output Server by entering the following
command:
cd installDir
7.
Use a file extraction utility shipped with HP Output Server 4.1 to uncompress and
restore the previous installation with the backup copy of the files.
NOTE: The above step is not applicable on Windows.
8.

start_server -t all
Backing up and restoring same-directory

installations (UNIX only)
This section describes how to back up and restore HP Output Server when HP Output
Server and MySQL for HP Output Management are installed in the same directory on a
UNIX host. When you back up HP Output Server that is installed in the same
installation directory as MySQL for HP Output Management, you create a single
backup of the HP Output Server program and configuration files and the MySQL for HP
Output Management program and database files.
Before you begin

Before you back up your HP Output Server installation, note the following
requirements:
176
Chapter 7
You must create a backup of your current HP Output Server installation on each
host.
The target directory you specify for a backup must contain sufficient space for the
backup.
You must stop all programs that monitor or depend on the HP Output Server
installation before creating a backup. In general, these applications are not restarted
automatically, you must restart these applications manually after restoring HP
Output Server from a backup.
Backing up same-directory installations (UNIX only)

To create a backup of HP Output Server on a UNIX host when HP Output Server and
MySQL for HP Output Management are installed in the same directory, perform the
following steps:
standard and split installations. For a split installation, you
must backup HP Output Server binaries and instance
separately.
1.
If you have not already done so, log on as the root user.
2.
3.
HP Output Server
Shell
Command
Bourne or Korn
Stop all programs that monitor or depend on the HP Output Server installation that
you want to back up.
177
Chapter 7
4.

stop_server -t all
NOTE: Stop the MySQL server if you are not using MySQL
provided with HP Output Server by entering the following
commands:
cd mySQLinstallDir
./bin/mysqladmin--defaults-file=mySQLins
tallDir/my.cnf shutdown
where mySQLinstallDir is the location of MySQL for HP
Output Management installation.
5.
For backing up the HP Output Server binaries and MySQL binaries, perform the
following steps:
i.
Change to the installation directory for HP Output Server and MySQL binaries
by entering the following command:
cd installBinDir
where installBinDir is the installation directory of HP Output Server and
MySQL binaries.
ii.
Back up and compress the existing installation by using the tar utility shipped
with HP Output Server 4.1. Enter the following command:

installBinDir/bin/tar -cvf - .|gzip > /Binpath/fileNameBin.gz

/Binpath/fileNameBin.tar.Z
178
Chapter 7
where Binpath is the target directory for the HP Output Server binaries backup
and fileNameBin is a name for the HP Output Server binaries backup file.
NOTE: For an HP Output Server standard installation, the Binpath
variable is the target directory for the HP Output Server
installation and fileNameBin is a name for the HP Output
Server backup file.
6.
For backing up the HP Output Server and MySQL instance, perform the following
steps:
i.
Change to the installation directory for HP Output Server and MySQL instance
cd installInstDir
where installInstDir is the installation directory of HP Output Server and
MySQL instance.
ii.
Back up and compress the existing installation by using the tar utility shipped
with HP Output Server 4.1. Enter the following command:

installBinDir/bin/tar -cvf - .|gzip > /Instpath/fileNameInst.gz

/Instpath/fileNameInst.tar.Z
where Instpath is the target directory for the HP Output Server instance backup
and fileNameInst is a name for the HP Output Server instance backup file.
Restoring same-directory installations (UNIX only)

This section assumes that you have created a backup of HP Output Server and MySQL
for HP Output Management by performing the steps in Backing up same-directory
installations (UNIX only) on page 177.
To restore an existing installation of HP Output Server on a UNIX host, when HP
Output Server and MySQL for HP Output Management are installed in the same
directory, perform the following steps:
1.
HP Output Server
If you have not already done so, log in as the root user.
179
Chapter 7
2.
3.
Shell
Command
Bourne or Korn
Ensure that HP Output Server servers and the MySQL server are stopped before
restoring the installations from the backup. Stop HP Output Server servers before
stopping the MySQL server.
To stop the HP Output Server servers, enter the following command:
stop_server -t all
NOTE: If you are not using MySQL provided with HP Output
Server, stop the MySQL server by entering the following
commands:
cd mySQLinstallDir
./bin/mysqladmin--defaults-file=mySQLins
tallDir/my.cnf shutdown
where mySQLinstallDir is the location of MySQL for HP
Output Management installation.
4.
On AIX hosts, run the slibclean command to ensure that library files are not in
use.
5.
For restoring the HP Output Server and MySQL binaries, perform the following
steps:
i.
Change to the installation directory for HP Output Server and MySQL binaries
cd installBinDir
where installBinDir is the installation directory of HP Output Server and
MySQL binaries.
180
Chapter 7
ii.
on your system and use the same for uncompressing the backup copy of the
files. Enter the following command:
cp -p installBinDir/bin/tar tar_Binpath/tar
Where tar_Binpath is the target directory for copying the tar utility shipped
iii. Restore the previous installation of HP Output Server and MySQL binaries
with the backup copy of the files by entering the following command:
-

zcat fileNameBin.gz | tar_Binpath/tar -xvf -

zcat fileNameBin.Z | tar_Binpath/tar -xvf -
Where fileNameBin is the name of the HP Output Server and MySQL binaries
backup file and tar_Binpath is the directory of the tar utility shipped with HP
Output Server 4.1 on your system.
NOTE: For an HP Output Server standard installation, fileNameBin
is the name for the HP Output Server and MySQL backup
file.
6.
For restoring the HP Output Server and MySQL instance, perform the following
steps:
i.
Change to the installation directory for HP Output Server and MySQL instance
cd installInstDir
where installInstDir is the installation directory of HP Output Server and
MySQL instance.
ii.
on your system and use the same for uncompressing the backup copy of the
files. Enter the following command:
cp -p installBinDir/bin/tar tar_Instpath/tar
Where tar_Instpath is the target directory for copying the tar utility shipped
iii. Restore the previous installation of HP Output Server and MySQL instance
with the backup copy of the files by entering the following command:
HP Output Server
181
Chapter 7
Backing up and restoring HP Output Server and Oracle database server

zcat fileNameInst.gz | tar_Instpath/tar -xvf -

zcat fileNameInst.Z | tar_Instpath/tar -xvf -
Where fileNameInst is the name of the HP Output Server and MySQL instance
backup file and tar_Instpath is the directory of the tar utility shipped with HP
Output Server 4.1 on your system.
7.
8.
Shell
Command
Bourne or Korn

start_server -t all
NOTE: If you are not using MySQL provided with HP Output
Server, start the MySQL server by entering the following
commands:
cd mySQLinstallDir
./bin/mysqld_safe--defaults-file=mySQLin
stallDir/my.cnf &
Backing up and restoring HP Output Server and

Oracle database server
This section describes how to back up and restore HP Output Server and which Oracle
database server tables should be backed up.
Backing up program and configuration files

To back up the HP Output Server program and configuration files, see Task 1: Backing
up program and configuration files (UNIX host) on page 165, or Task 1: Backing up
program and configuration files (Windows host) on page 172
182
Chapter 7
Restoring program and configuration files

To restore the HP Output Server program and configuration files, see Task 2: Restoring
program and configuration files (UNIX host) on page 170, or Task 2: Restoring
program and configuration files (Windows host) on page 176.
Backing up and restoring Oracle database server tables

HP recommends that you back up and restore the following primary server tables of HP
Output Server:
All tables with names in the format IDS_CCM_<numeric_string> in the

Configuration Manager (CM) server
The PM_CTDB_TBL, PM_GDB_GROUP, and PM_GDB_MEMBERS tables in the

Privilege Manager (PM) server
The QSD_SCHEMA table and all tables with table name

QSD_TABLE_<numeric_string> in the Accounting and Inventory Manager (AIM)
server
<em_server_name>_CLIENTS and <em_server_name>_SUBSCRIPTIONS

table for every Event Manager (EM) server
NOTE: Dot (.) and dash ( - ) characters in <em_server_name> must
be replaced by underscore ( _ ).
HP recommends that you back up and restore the following delivery server tables of HP
Output Server:
All tables with names in the format <delivery_server_name>_<numeric_string>

for every delivery server
NOTE: Dot (.) and dash ( - ) characters in <delivery_server_name>
must be replaced by underscore
( _ ).
Backing up HP Output Distributor Oracle database server tables

HP recommends that you back up and restore the following tables for every HP Output
Distributor Oracle database server:
HP Output Server
REPORT_<hpod_database_name>
DOCOBJ_<hpod_database_name>
183
Chapter 7
184
RPTINF_<hpod_database_name>
RPTTOK_<hpod_database_name>
SET_<hpod_database_name>
PGSMAP_<hpod_database_name>
JOBATR_<hpod_database_name>
RPTFMT_<hpod_database_name>
STATTR_<hpod_database_name>
STLOCK_<hpod_database_name>
STSRTK_<hpod_database_name>
STSG_<hpod_database_name>
STSGE_<hpod_database_name>
STSGEV_<hpod_database_name>
STRECP_<hpod_database_name>
Appendix A
Using setup.pl in non-interactive mode

This appendix describes the syntax for using setup.pl in non-interactive mode. You
can use setup.pl in non-interactive mode at the command line to install or uninstall
HP Output Server on a UNIX host. For more information about the arguments for this
script, see the instructions for using setup.pl in interactive mode in the following
chapters:
Chapter 2, Installing HP Output Server on page 33.
Chapter 3, Uninstalling HP Output Server on page 101.
HP Output Server 4.1 provides customized configuration files for using setup.pl in
non-interactive mode. For more information about the parameters for this script, see
server.ini parameterson page 187 and client.ini parameters on page 191.
The general syntax of the configuration files is as follows:
[HP Output Management component name]
<key 1> = <value>
<key 2> = <value>
.
.
<key N> = <value>
The sample configuration files shipped with HP Output Server 4.1 can be used for
installing HP Output Server in a non-interactive mode. The following sample
configuration files are shipped with HP Output Server 4.1:
HP Output Server
server.ini
client.ini
185
Appendix A
Sample syntax
Sample syntax
This section describes the sample syntax for using setup.pl in non-interactive mode
for the following tasks:
Creating a server installation
Creating a client installation
Using help
For a complete list of parameters, see server.ini parameters on page 187, and
client.ini parameters on page 191.
Creating a server installation

To create a server installation of HP Output Server, use the following syntax:
perl setup.pl [-c] server.ini
NOTE: The parameters in the server.ini file are set to default
values. For a customized installation, edit the server.ini
file accordingly before executing the command.
NOTE: The key-value pairs in the server.ini configuration file
can be customized to perform specific HP Output Server 4.1
installations, such as:
- HP Output Server 4.1 with MySQL database server
provided with HP Output Server.
- HP Output Server 4.1 with existing/remote database server.
- HP Output Server 4. 1 Join a domain installation.
Creating a client installation

To create a client installation of HP Output Server, use the following syntax:
perl setup.pl [-c] client.ini
Using help
To view information about using setup.pl, enter the following:
setup.pl -h|-?
186
Appendix A

server.ini parameters
The following table describes the parameters in the server.ini file for running the
setup.pl in non-interactive mode.
Parameters
Description
HPOM_OPERATION
Set this to INSTALL, if you want to install HP Output Management

product components or to UNINSTALL, if you want to remove HP
Output Management product components. The default value is
INSTALL.
HPOM_UNINSTALL_PATH
Set this to the directory path of the installed HP Output Server

installation (HP Output Server binaries, instance, or standard
installation), if you want to uninstall HP Output Server. The default
value is /opt/hpom.
HPOM_CUSTOM_INSTALL_TYPE
Set this to BINARIES if you want to install only HP Output Server

binaries.
Set this to INSTANCE if you want to install only HP Output Server
instance.
Set this to STANDARD if you want to install HP Output Server in the
conventional way with the binaries and instance installed in the same
location.
The default value is STANDARD.
HPOM_USER
If you are installing HP Output Server as a root user, set this to the
owner of the installed files.
The default value is hposadm.
HPOM_INSTALL_PATH
Set this to the directory path of HP Output Server instance installation.

The default value is /opt/hpom.
HPOM_INSTALL_BIN_PATH
Set this to the directory path of HP Output Server binaries installation.

HPOM_LOG_PATH
Set this to the directory path of HP Output Server logs. The default
value is /opt/hpom/var/log.
JRE_HOME
Set this to the directory path where JRE is installed. The default value is
/opt/java.
HPOM_INSTALL_NONEMPTY_DIR
Set this to YES if want to install HP Output Server in a non-empty

directory. The default value is NO.
HPOM_INSTALL_PATH_CREATE
Set this to YES for the setup script to create the specified non-existing
directory path. The default value is NO.
HP Output Server
187
Appendix A
Parameters
Description
HPOS_RESTRICT_SERVER_BINARY
Set this to YES if you want to restrict other users from accessing HP
Output server binaries.
Set this to NO if you want to allow other users to access HP Output
server binaries.
The default value is NO.
HPOS_SERVER_CONFIG
Set this to DEFAULT if you want to create a set of servers, to HOST if

you want to join a domain, or to LATER if you want to create only the
domain. The default value is DEFAULT.
HPOS_DOMAIN_NAME
Set this to the HP Output Server domain name. The default value is
hpos.d.
HPOS_NM_PORT
Set this to the port number that the HP Output Server Name Space
Manager (NM) will listen to. The default value is 4009.
HPOS_ADVANCED_SERVER_OPTION
Set this to YES to configure advance server options. The default value is
NO.
DAZEL_HOSTNAME
Set this to the hostname or IP address of the network interface if you

have set HPOS_ADVANCED_SERVER_OPTION to YES.
DAZEL_PORTS
Enter a list of port numbers or ranges of port numbers for firewall

support if you have set HPOS_ADVANCED_SERVER_OPTION to YES.
Type the port numbers separated by commas, or ranges of port numbers
separated by dashes.
Following are the additional parameters for Join a domain option while installing HP Output Server:
HPOS_DOMAIN_HOST
Enter the hostname of the primary HP Output Server domain. The

default value is localhost.
DB_AUTO_CREATE
Set this to YES, if you want HP Output Server to automatically create

the database. The default value is YES.
HPOS_START_SERVER_OPTION
Set this to YES, if you want HP Output Server to start the HP Output
Server servers after the installation. Else, enter STOPPED. The default
value is STOPPED.
HPOM_DB_CONFIG
Set this to YES, if you want to configure the connection to the database.
Set this to NO, if you do not want to set the database related parameters
such as DB_TYPE, DB_USER, DB_PASSWD, and DB_PORT.
188
Appendix A

Parameters
Description
USE_HPOS_PROVIDED_MYSQL
Set this to YES, if you want to use MYSQL provided with HP Output
Server.
Set this to NO, if you want to use external MySQL or Oracle as the
database server.
The default value is YES.
DB_HOSTNAME
Set this to the database hostname or IP address. Set to localhost if

the database exists on the same machine or hostname of the system
where the database exists. The default value is localhost.
DB_TYPE
Set this to the database type. Valid values are MySQL or ORACLE. The
default value is MySQL.
DB_USER
Set this to HP Output Server username for the database. The default
value is hposadm.
DB_PASSWD
Set this to the password for the database. The default value is
hposadm.
DB_PORT
Set this to the port number to which database server is listening. The
default value is 3306.
Following are the additional fields for JBoss Server configuration

CONFIGURE_JBOSS_SERVER
Set this to YES if you want to configure JBoss Server.

Set this to NO if you do not want to configure JBoss Server.
CONFIG_PORT_USER_INPUT
Specify the 17 port numbers in the range 1024 through 65535 that HP
Output Server requires to configure JBoss server. The default value is
9000-9016.
Following are the additional fields if you choose existing MySQL as the database server while installing HP
Output Server:
DB_SOCKET_CHOSEN
Set this to YES if the file socket connection mode is used to connect to
the database server on the same machine. Set this to No if the MySQL
database server is on a remote machine.
MYSQL_SOCKET_PATH
Set this to the MySQL database server file socket path. The default
value is /opt/hpom/var/mysql/mysql.sock.
DB_PREFIX_NAME
Set this to the database server prefix name. The database prefix name
will be used to create the database/tablespace. The default value is
hpomdb.
HP Output Server
189
Appendix A
Parameters
Description
DB_AUTO_CREATE
Set this to YES if you want HP Output Server to automatically create the
database.
Following are the additional field for bypass validation:

Enter YES if you want to bypass validation.
HPOM_BYPASS_VALIDATION
Following are the additional fields if you choose Oracle as the database server while installing HP Output
Server:
DB_CONNECT_IDENTIFIER
Set this to the required ODBC-Oracle connection identifier type. The

valid values are TNS or SID. The default value is SID.
DB_SERVICE_NAME
Set this to the Oracle database server service name. The default value is
ORCL.
DB_SERVER_TNS_NAME
Set this to the Oracle database server TNS name.
TNS_ORA_FILE_PATH
Set this to the Oracle database server tnsnames.ora file path.
DB_CLIENT_LIB_PATH
Set this to the path of the installed Oracle Instant Client libraries.
DB_DRIVER_PATH
Set this to the path of the Easysoft ODBC-Oracle driver installation.
Following are the additional fields if you choose MySQL provided with HP Output Server as the database server
while installing HP Output Server:
DB_PASSWD
Set this to the password for the MySQL database server. The default
value is hposadm.
MYSQL_IBDATA_SIZE
Set this to the ibdata file size. The default value is 100M.
MYSQL_IBDATA_EXTENDED_SIZE
Set this to the ibdata file autoextend size. The default value is 50M.
NOTE: If you install HP Output Server 4.1 as a standard or a split

installation on a system where MySQL is already installed in
the $DAZEL_HOME/var/mysql folder, the installation
will not upgrade the existing MySQL. This is because of the
change in directory structure in HP Output Server 4.1. The
existing MySQL may not be usable after the installation.
190
Appendix A

client.ini parameters
The following table describes parameters in client.ini file for installing HP Output
Server as a client only installation in non-interactive mode.
Parameters
Description
HPOM_OPERATION
Set this to INSTALL, if you want to install HP Output

Management product components or Enter UNINSTALL, if
you want to remove HP Output Management product
components. The default value is INSTALL.
HPOM_INSTALL_TYPE
Set this to the type of the HP Output Server installation. Set this
to client for client-only installation.
HPOM_UNINSTALL_PATH
Set this to the directory path of the installed HP Output Server

installation, if you want to uninstall HP Output Server. The
default value is /opt/hpom.
HPOM_USER
If you are installing HP Output Server as a root user, specify the

owner of the installed files. If you are installing HP Output
Server as any other user other than root user, the owner of the
installed files is set to the user ID of the user installing HP
Output Server. The default value is hposadm.
HPOM_INSTALL_PATH
Set this to the directory path for HP Output Server installation.

HPOM_INSTALL_NONEMPTY_DIR
Set this to YES if want to install HP Output Server in a non

empty directory
HPOM_INSTALL_PATH_CREATE
Set this to YES for the setup script to create the specified
non-existing directory path. The default value is YES.
HPOS_DOMAIN_HOST
Set this to the database hostname. The default value is

localhost.
HPOS_DOMAIN_NAME
Set this to the HP Output Server domain name. The default

value is hpos.d.
HPOS_NM_PORT
Set this to the port number on which the HP Output Server

Name Space Manager (NM) will listen. The default value is
4009.
HP Output Server
191
Appendix A
192
Appendix B
Environment variables in HP Output

Server
This appendix lists HP Output Server environment variables and their settings, and
describes methods for setting environment variables in HP Output Server.
When you install HP Output Server, the following files are created:
installInstDir/etc/setup_env.sh (Bourne/Korn shell file)
installInstDir/etc/setup_env.csh (C shell file)
installInstDir/etc/setup_env.pl (Perl file)
installInstDir/etc/setup_env.bat (Windows only)
These files contain environment variables specific to your HP Output Server, HP Output
Manager for SAP, and HP Output Distributor installations. Before executing HP Output
Server commands on a UNIX host, you can set the environment variables by sourcing
setup_env.sh or setup_env.csh. The variables define file and directory
pathways that HP Output Server requires to operate.
When you install HP Output Server on a Windows host, the setup program
automatically sets or modifies the environment variables.
HP Output Server
193
Appendix B
Environment variables in HP Output Server
UNIX environment variables

The following tables list environment variables that are set on UNIX platforms.
Table B-1. Environment variables for all UNIX platforms
Variable
Setting
DAZEL_HOME
installInstDir
Refers to the HP Output Server installation directory in case of an
HP Output Server standard installation.
Refers to the HP Output Server instance installation directory in
case of an HP Output Server split installation.
HPOM_HOME
installInstDir
(Refers to the HP Output Management product installation
directory)
HPOM_INSTALL
installBinDir
Refers to the HP Output Server installation directory (same as
DAZEL_HOME) in case of an HP Output Server standard
installation.
Refers to the HP Output Server binaries installation directory in
case of an HP Output Server split installation.
HPOM_LOG
installInstDir/var/log
(Refers to the HP Output Server logs directory)
DAZEL_HOSTNAME
Set to restrict HP Output Server processes to a specific interface.

Use this environment variable only with systems containing
multiple network configurations.
For more information, see Appendix E, HP Output Server in a
multi-NIC environment on page 213, or contact Customer
Support.
DAZEL_PORTS
194
Set to control which port numbers a server process will use. For
more information, see Appendix D, Firewall support
on page 209.
Appendix B

Table B-1. Environment variables for all UNIX platforms (continued)

Variable
Setting
DAZELNS
DAZEL:dazelDomain,nmHost[nmPort]
If the NM is on the local host and DAZEL_HOSTNAME is set,
nmHost must match the value of DAZEL_HOSTNAME.
The syntax for NM server portion of this environment variable
requires both the host name where the NM server is running and
the port number where the NM server is listening. You must
delimit the port number and the HP Output Server domain name
with a left square bracket ([) and a right square bracket (]).
ENSCRIPT_LIBRARY
installBinDir/share/enscript
JRE_HOME
Stores the path of the JRE installation.
MANPATH
Prepend:
installBinDir/man
MIBDIRS
installBinDir/share/snmp/mibs
MIBS
ALL
NLSPATH
Prepend:
installBinDir/nls/cat/%L/%N
:installBinDir/nls/oid/%L/%N
ODBCINI
installInstDir/etc/odbc.ini
ODBCSYSINI
installInstDir/etc
PATH
Prepend:
installBinDir/bin
PERL5LIB
Prepend:
installBinDir/lib/perl5
:installBinDir/lib/perl5/site_perl
ORACLE_HOME
Path of the Oracle Client libraries

This environment variable is valid when HP Output Server is
installed with Oracle as the back-end.
EASYSOFT_ROOT
Path of the Easysoft installation

This environment variable is valid when HP Output Server is
installed with Oracle as the back-end.
HP Output Server
195
Appendix B
Table B-2. Environment variables for Solaris platforms

Variable
Setting
LANG
C
If you plan to run HP Output Server on a non-English version of
UNIX, see Configuring user authentication and authorization
on page 151.
LD_LIBRARY_PATH*
If not already preset in LD_LIBRARY_PATH, also prepend:

installBinDir/lib
:/user/lib/lwp
:/usr/lib
easysoftdir/lib:easysoftdir/oracle:oracle_
client_libs
* If only LD_LIBRARY_PATH is set, the operating system uses that path to search for both 32-bit and 64-bit
libraries. If LD_LIBRARY_PATH64, is set the operating system uses LD_LIBRARY_PATH for 32-bit
libraries and LD_LIBRARY_PATH64 for 64-bit libraries. On Solaris, sourcing the setup_env* files will
append HP Output Server required library paths to LD_LIBRARY_PATH64 only if this environment
variable is currently set.
Table B-3. Environment variables for AIX platforms

Variable
Setting
LANG
en_US
on page 151.
LIBPATH
Prepend:
installBinDir/lib
If not already preset in LIBPATH, also prepend:
/usr/lib
client_libs
Table B-4. Environment variables for HP-UX platforms

Variable
Setting
LANG
C
on page 151.
196
Appendix B

Windows environment variables
Table B-4. Environment variables for HP-UX platforms (continued)

Variable
Setting
SHLIB_PATH
Prepend:
installBinDir/lib
client_libs
Table B-5. Environment variables for Linux platforms

Variable
Setting
LANG
C
Linux, see Configuring user authentication and authorization
on page 151.
LD_LIBRARY_PATH
Prepend:
installBinDir/lib
easysoftdir/lib:easysoftdir/oracle:oracle_c
lient_libs

The setup program automatically sets or prepends to the following environment
variables during configuration of HP Output Server on a Windows host.
NOTE: All HP Output Server environment variables on a Windows
host are (and must be) set as system variables.
Table B-6. Windows environment variables
Variable
Setting
DAZEL_HOME
installInstDir
(Refers to the HP Output Server installation directory)
DAZEL_HOSTNAME
HP Output Server
Set to restrict HP Output Server processes to a specific interface.

Use this environment variable only with systems containing
multiple network configurations. For more information, see
Appendix E, HP Output Server in a multi-NIC environment
on page 213.
197
Appendix B
Table B-6. Windows environment variables (continued)

Variable
Setting
DAZEL_PORTS
Set to control which port numbers a server process will use. For
more information, see Appendix D, Firewall support
on page 209.
DAZELNS
DAZEL:dazelDomain,nmHost[nmPort]
If the NM is on the local host and DAZEL_HOSTNAME is set,
nmHost must match the value of DAZEL_HOSTNAME.
The syntax for NM server portion of this environment variable
requires both the host name where the NM server is running and
the port number where the NM server is listening. You must
delimit the port number and the HP Output Server domain name
with a left square bracket ([) and a right square bracket (]).
ENSCRIPT_LIBRARY
installBinDir/share/enscript
JRE_HOME
Stores the path of the JRE installation.
MIBDIRS
Prepend:
installBinDir/share/snmp/mibs
MIBS
ALL
PATH
Prepend:
installBinDir\bin
PERL5LIB
Prepend:
installBinDir/lib/perl5
;installBinDir/lib/perl5/5.8.1/lib
;installBinDir/lib/perl5/site/5.8.1/lib
198
Appendix B

Setting environment variables in HP Output Server

You can use the following methods for setting environment variables in HP Output
Server.
Specify the environment variable for the entire HP Output Server environment by
setting the -environment-variables attribute with the config_host
command.
Specify the environment variable at the server by setting the

-server-environment-variables attribute with the config_server
command.
Export the environment variable as a system environment variable.

CAUTION: Do not use the config_host or config_server
command to set the DAZEL_HOSTNAME
environment variable. For more information, see
Appendix E, HP Output Server in a multi-NIC
environment on page 213.
You can use the following attribute operators with the config_host -u and
config_server -u constructions to set and unset multi-valued attributes. For
multi-valued attributes only, you can add and subtract values with the -+ and -operators.
The following table describes these operators.
Operator
Definition
-attribute value,...
This replaces the values of attribute with value,... If no attributes

exist, add attribute.
-+attribute value,...*
This adds the value,... to attribute. If no attributes exist, add

attribute.
--attribute value,... *
This removes the value,... from attribute.
* Use this operator with the config_host -u or config_server -u construction only.
HP Output Server
199
Appendix B
If a multi-valued attribute is not set, using the -+attribute value construction has the
same effect as using the -attribute value construction. Consider the following sample
commands, in which the -server-environment-variables attribute is not set
on the installations delivery servers. In this example, both commands set the attribute to
40000-40200.
config_server -u -t delivery
-x"-+server-environment-variables
\"DAZEL_PORTS=40000-40200\""
-x"-server-environment-variables
\"DAZEL_PORTS=40000-40200\""
Subtracting the last value in a multi-valued attribute removes the attribute.
Methods
Your choice of method depends on your objective for setting the environment variable.
NOTE: You must restart the HP Output Server servers for changes to
take effect.
The following examples illustrate the effects of the different methods:
Set the -environment-variables attribute with the config_host

command. The following example sets DAZEL_PORTS on all of a configurations
servers to 40000-40300:
config_host -u -x"-+environment-variables
\"DAZEL_PORTS=40000-40300\""
Using the config_host command sets the environment variable and leaves it
defined until you remove the setting as follows:
config_host -u -x"--environment-variables
\"DAZEL_PORTS=40000-40300\""
200
Set the -server-environment-variables attribute with the

config_server command. The -server-environment-variables
multi-valued attribute lets you specify the environment variables and values to be
set in the environment of a server when it is started.
Appendix B

The following example sets DAZEL_PORTS on all of a configurations delivery

servers to 40000-40200:
-x"-+server-environment-variables
\"DAZEL_PORTS=40000-40200\""
Using the config_server command sets the server environment variable and
leaves it defined until you remove the setting as follows:
-x"--server-environment-variables
\"DAZEL_PORTS=40000-40200\""
Setting DAZEL_PORTS as a server environment variable with config_server
overrides any settings defined with config_host or in your shell. However, if
you use config_server to define DAZEL_PORTS for all delivery servers and
then add a new server later, that new server will not be restricted to the same port or
port range.
Set DAZEL_PORTS as a system environment variable.

The following UNIX example uses the export command in your shell:
export DAZEL_PORTS=40000-40200
When you end your shell session, the setting for DAZEL_PORTS is removed.
Consider using this method to test the effects of setting this environment variable.
On Windows, use the operating systems Control Panel to set environment
variables.
HP Output Server
201
Appendix B
202
Appendix C
Configuring the database connection

on UNIX hosts
If you installed HP Output Server without configuring the connection to the database
server, use the config_host command to set up the connection between HP Output
Server and the database before configuring HP Output Server servers. The examples in
this appendix show how to configure the connection when no servers have been
configured on the HP Output Server host.
NOTE: You can also configure the database connection using the
config_server command and the
-database-server* attributes. For more information
about using the config_server command, see the
System Administrators Attribute Reference for HP Output
Server. For more information about using the
-database-server* attributes, see the System
Administrators Attribute Reference for HP Output Server.
HP Output Server and the database on the same

host
In the following example, HP Output Server communicates with the database as root
and with the password set to dazel. In this example, HP Output Server and the
database are installed on the same host.
HP Output Server
203
Appendix C
Configuring the database connection on UNIX hosts
HP Output Server and the database on the same host
1.
If you have not already done so, log on to your HP Output Server host machine as
the root user or the user with administrative privileges, depending on your
operating system.
2.
3.
Shell
Command
Bourne or Korn
Set the -database-server* attributes on the HP Output Server host as

follows:
UNIX:
For MySQL
config_host -u -x"-database-server-user root
-database-server-password dazel
-database-server-socket mySQLinstallDir/socket
-database-server-hostname localhost
-database-datasource-name MySQL_HPOM_DSN
-database-name-prefix hpomdb
-database-type MySQL
-database-auto-create true" -f -c
where mySQLinstallDir is the installation path for MySQL for HP Output
Management, for example, /user/local/mysql, and socket is the file
socket name for the MySQL server to use for local connections, for example,
mysql.sock.
NOTE: Use -f and -c options as follows:
-f re-creates the environment scripts.
-c creates the odbc.ini/odbcinst.ini file.
204
Appendix C

HP Output Server and the database on separate hosts
For Oracle
-database-server-hostname localhost
-database-server-port 1521
-database-server-service-name ORCL
-database-datasource-name ORACLE_HPOM_DSN
-database-type ORACLE
-database-auto-create true
-database-lib-paths
<EASYSOFT_ROOT>/oracle:<EASYSOFT_ROOT>/lib:<$DAZE
L_HOME>/var/oracle_client_libs
-database-client-lib-path
<$DAZEL_HOME>/var/oracle_client_libs
-database-driver-path <EASYSOFT_ROOT>" -f -c
NOTE: Use -f and -c options as follows:
-f re-creates the environment scripts.
-c creates the odbc.ini/odbcinst.ini file.
NOTE: After executing the config_host command, you must
source the UNIX environment variables.
4.
Configure your servers using the config_server command.

For more information, see the System Administrators Command Reference for HP
Output Server.
HP Output Server and the database on separate

hosts
In the following example, HP Output Server communicates with the database as root
and with the password set to dazel. In this example, the database server is installed on
a separate host named tiger and listening to port 3306.
1.
HP Output Server
If you have not already done so, log on to your HP Output Server host machine as
the root user.
205
Appendix C
2.
3.
Shell
Command
Bourne or Korn
Set the -database-server* attributes on the HP Output Server host as

follows:
UNIX:
For MySQL
-database-server-hostname DATABASE SERVER HOST NAME
-database-datasource-name MySQL_HPOM_DSN
-database-type MySQL
-database-auto-create true" -f -c
For Oracle
-database-server-hostname DATABASE SERVER HOST NAME
-database-server-service-name ORCL
-database-datasource-name ORACLE_HPOM_DSN
-database-type ORACLE
-database-auto-create true
-database-lib-paths
<EASYSOFT_ROOT>/oracle:<EASYSOFT_ROOT>/lib:<$DAZE
L_HOME>/var/oracle_client_libs
-database-client-lib-path
<$DAZEL_HOME>/var/oracle_client_libs
-database-driver-path <EASYSOFT_ROOT>" -f -c
NOTE: After executing the config_host command, you must
source the UNIX environment variables.
206
Appendix C

4.
HP Output Server
Configure your servers using the config_server command. For more

information, see the System Administrators Command Reference for HP Output
Server.
207
Appendix C
208
Appendix D
Firewall support
This appendix describes firewall support in HP Output Server. With this
implementation in place, a client program on one side of a companys firewall, such as
an HP Output Manager for SAP client, can communicate with HP Output Server on the
protected side of the firewall.
A firewall is a system that enforces access control between network addresses. One very
common way of enforcing such access control in a firewall is to limit the endpoint of a
target request. That is, when a client requests a connection to a server's endpoint, the
firewall either allows or refuses the connection based upon the network interface
address and/or port number of the server process (not the calling or client process).
Because HP Output Server is designed to run in a distributed environment,
communication between processes requires a fully-bound endpoint for each process.
Each of these endpoints consists of a network interface address (a dotted Internet
address) and a port number.
In HP Output Server, the Namespace Manager (NM) listens for requests on all of the
network interface addresses on a well-known host and port number. All other server
processes listen for requests on all of the network interface addresses on the host
machine that they are running, and on an operating system-assigned port number. Client
processes let the operating system assign the network interface address and port number
for their endpoints.
HP Output Server uses the DAZEL_PORTS environment variable to support a
companys firewall. The DAZEL_PORTS environment variable controls which port
numbers a server process will use. You can specify a single port number, a range of port
numbers, or a list of ranges and/or individual port numbers when defining
DAZEL_PORTS. The behavior is as follows:
HP Output Server
209
Appendix D
Firewall support
Implementing firewall support
If DAZEL_PORTS is defined, the server process will attempt to find an available

port in the list of specified ports. If none of the specified ports is available, the
server process will report and log an error.
NOTE: Because the NM listens for requests on all of the network
interface addresses on a well-known host and port number, it
ignores the value of DAZEL_PORTS, if set.
If DAZEL_PORTS is not defined, the server process will listen for requests on a
unique port number assigned by the operating system.
A server process in HP Output Server uses a port until the server is stopped. If you are
using DAZEL_PORTS to limit the available ports for HP Output Server processes,
ensure that the number of available ports is large enough to handle all of the servers in
your environment. Allow one port for each server in your HP Output Server installation.
NOTE: It is not necessary to set the DAZEL_PORTS environment
variable on the client side for print clients.

The following procedure details the recommended method of setting the
DAZEL_PORTS environment variable. For information about different methods of
setting environment variables, see Appendix B, Environment variables in HP Output
Server on page 193.
To specify a servers port number or range of numbers, complete these steps:
1.
Stop HP Output Server and its servers by entering the following command:
stop_server -t all
2.
Ensure that all servers have been stopped by entering the following command:
server_status
3.
Specify a servers port number or range of numbers with the config_server

command.
The following command sets DAZEL_PORTS on all of an installations delivery
servers:
-x"-server-environment-variables
\"DAZEL_PORTS=40000-40100\""
210
Appendix D
Firewall support
4.
Start HP Output Server by entering the following:

start_server -t all
5.
Verify that the servers are listening to the correct ports. For example, you can use
the nmcp command as follows:
nmcp list |grep binding
The port number is the last entry on the binding.
6.
HP Output Server
Start other processes.
211
Appendix D
Firewall support
212
Appendix E
HP Output Server in a multi-NIC

environment
This appendix describes configuring multiple instances of HP Output Server on a single
server system with multiple network interface cards (NICs) installed. Specifying the
host name on which a server listens for connection requests effectively restricts
communication to the interface associated with a specific HP Output Server domain.
Limiting communication in this way accomplishes the following:
Because each NIC has a full range of port numbers, you can reuse a port number
from one domain to the next.
You are not required to configure the NM on subsequent HP Output Server

domains on a non-standard NM port.
A scenario in which reusing port numbers is required involves setting up multiple

instances of an LPR Gateway. Each LPR Gateway must use port 515 for
communication. If multiple HP Output Server domains in a multiple NIC environment
are configured to communicate through a unique interface, as specified through the
DAZEL_HOSTNAME environment variable, each HP Output Server domain can run
HP Output Server
213
Appendix E
HP Output Server in a multi-NIC environment
Configuring multiple instances of HP Output Server to use the same network interface
an LPR Gateway even though the domains physically reside on the same server system.
Specifying the host name for each HP Output Server domain permits the reuse of the
same TCP port number (515 in this example) for each LPR Gateway.
NOTE: If you configure two HP Output Server domains in a
multiple NIC environment to run two LPR Gateway servers
(one for each HP Output Server domain), you must set the
-lpg-masterlock attribute on one of the LPR Gateway
servers. Without specifying a different lock file, the second
LPR Gateway server will not start.
The DAZEL_HOSTNAME environment variable controls which network interface
address a server process listens on. The behavior is as follows:
If DAZEL_HOSTNAME is defined, the server process listens for requests on the

specified network interface address.
If DAZEL_HOSTNAME is not defined, the server process listens for requests on

all network interface addresses for the host.
If you set DAZEL_HOSTNAME, follow these requirements:
DAZEL_HOSTNAME must be a valid host where the NM resides and resolve to

an IP address. The value for DAZEL_HOSTNAME can be a host name or IP
address.
For the system where the NM resides, the value for the host in DAZELNS must
match the value of DAZEL_HOSTNAME.
All HP Output Server processes in a single domain on a single host must use the
same value or no value for DAZEL_HOSTNAME. The value of
DAZEL_HOSTNAME must be identical for all processes. For example, sandbox
and sandbox.bigcompany.com are interpreted as two distinct addresses.
Configuring multiple instances of HP Output Server

to use the same network interface
This section describes the manual steps you will take to configure HP Output Server on
a single server system with multiple NICs installed.
For new installations of HP Output Server, the recommended method of configuring
multiple instances of HP Output Server in a multiple NIC environment is to select the
advanced server options when you perform a clean installation of HP Output Server.
214
Appendix E HP Output Server in a multi-NIC environment

Changing the host name throughout the configuration
One advanced server option lets you restrict HP Output Server processes to use a
specific network interface. For more information, see Chapter 2, Installing HP Output
Server on page 33.
Changing the host name throughout the

configuration
If the NM resides on the local HP Output Server instance and you changed the
-dazel-nm-host attribute, ensure that this change is reflected throughout the
configuration, including:
Client-only installations of HP Output Server
An HP Output Server installation that is distributed across a domain
To change the host, complete these steps:

1.
Log in as root or a user with administrator privileges.
2.
3.
Shell
Command
source ./setup_env.csh
Bourne or Korn
. ./setup_env.sh
Enter the following command:

config_host -u -f -x"-dazel-nm-host
newHostName[nmPort]"
For other clients, such as HP Output Envoy, HP Output Explorer, and HP Output
Distributor, change the host. Also, check that these clients are using the correct port
number. For information about making changes to these products, see the
documentation for those products.
Depending on your configuration, you may need to change the host on additional
systems. For example, if your installation supports interdomain delivery, you must
change the host name on all of the configured systems.
HP Output Server
215
Appendix E
HP Output Server in a multi-NIC environment
Configuring multiple LPR Gateway servers in a multiple NIC environment (UNIX only)
Configuring multiple LPR Gateway servers in a

multiple NIC environment (UNIX only)
This section provides general steps for configuring more than one LPR Gateway on a
single physical host. Support for this feature is available on UNIX hosts only.
The following procedure configures two LPR Gateway servers (one for each HP Output
Server domain) and assumes that you have already configured two HP Output Server
domains and the required primary servers.
1.
From the first HP Output Server domain, create an LPR Gateway server:
config_server -t lpg lpg1
This operation creates a lock file at the default location. On UNIX, the default
location of the lock file is /var/spool.
2.
If you are configuring more than one LPR Gateway server, set
-lpg-masterlock on the second and subsequent LPR Gateway servers to a
uniqueLockFile. From the second HP Output Server domain, create the second LPR
Gateway server and set the -lpg-masterlock attribute to a different lock file.
config_server -t lpg -x"-lpg-masterlock uniqueLockFile"
lpg2
216
Appendix F
Hot backup
The hot backup feature in HP Output Server 4.1 enables backup and restore of HP
Output Server and HP Output Distributor MySQL databases.
The hpos_db_backup.pl script is available in the $DAZEL_HOME/bin directory
for an HP Output Server standard installation and in the $HPOM_INSTALL/bin
directory for an HP Output Server split installation. When running the script to back up
and restore HP Output Server and HP Output Distributor MySQL databases, consider
the following recommendations:
A 1:1 relationship should exist between HP Output Server instances and MySQL
server. The backup/restore feature for remote MySQL server is not currently
supported.
NOTE: The hot backup and restore of HP Output Server and HP
Output Distributor databases are not supported if the
back-end database server is Oracle.
Backup and restore operations must be done on the same database and HP Output
Server version.
The backup occurs as follows:
HP Output Server
The PM, NM, and CM databases are fully backed up.
In the AIM database, all data, except for accounting information, is backed up.
All EM, DLM, and JQM databases are backed up without data.
No job data is included in the backup.
217
Appendix F
Hot backup
HP Output Distributor databases that are in HP Output Server MySQL instances are
backed up.
You must stop all the servers after configuring them to restore the database. Re-create
the servers with the same name before restoring the database. The backup process reads
MySQL connection information from HostConfig.sgml.
Consider the following limitations:
When you create a backup for an HP Output Server installation and delete the
existing installation, you cannot restore the deleted HP Output Server installation
with the backup. You have to re-create the HP Output Server installation before you
can back up the contents of the server.
The script does not back up the accounting data in the AIM database.
Using the hpos_db_backup.pl script

Execute the hpos_db_backup.pl script as follows:
hpos_db_backup.pl [-h|?] -d|-u [-D <MySQL install
directory>] [-i <MySQL binary install directory>] -c
<target backup/restore file>
where:
-h|? refers to help
-d refers to backup
-u refers to restore
-D refers to <MySQL install directory> (the default is
$DAZEL_HOME/var/mysql)
-i refers to <MySQL binary install directory> (the default is
$HPOM_INSTALL/share/mysql/5.0.24). The -i option is applicable only
for an HP Output Server split installation.
-c refers to the target backup/restore file
Additionally, you can use the following options with the hpos_db_backup.pl
script when a MySQL instance is corrupted:
-r refers to cleaning of the MySQL database
-b refers to the MySQL user table backup that should be used with -d
Backup example
UNIX:
For an HP Output Server standard installation:
./hpos_db_backup.pl d D /opt/hpom/var/mysql c
/home/backup/hpos_backup.dump
218
Appendix F
Hot backup
For an HP Output Server split installation:

./hpos_db_backup.pl d D /opt/hpom/var/mysql i
/opt/hpom_bin/share/mysql/5.0.24 c
Windows:
perl hpos_db_backup.pl d D "C:\HP\OM\var\mysql" c
"C:\backup\backup.dump"
Restore example
UNIX:
For an HP Output Server standard installation:
./hpos_db_backup.pl u D /opt/hpom/var/mysql c
For an HP Output Server split installation:
./hpos_db_backup.pl u D /opt/hpom/var/mysql i
/opt/hpom_bin/share/mysql/5.0.24 c
Windows:
perl hpos_db_backup.pl u D "C:\HP\OM\var\mysql" -c
"C:\backup\backup.dump"
Usage of the hpos_db_backup.pl script when a MySQL instance is

corrupted
When a MySQL instance is corrupted, you can use the hpos_db_backup.pl script
to restore the MySQL database. The script is capable of handling the following types of
corruption:
Table space corruption (ibdata)
Form file corruption (frm files)
MySQL base table corruption
To restore the MySQL database, use the following syntax:

hpos_db_backup.pl [-h|?] -d|-u [-b] [-r] [-D <MySQL
install directory>] [-i <MySQL binary install
directory>] -c <target backup/restore file>
For a description of these options, see the previous topic.
HP Output Server
219
Appendix F
Hot backup
Backup example
To back up the HP Output Server application data, run the command provided in the
backup example in the previous topic, Using the hpos_db_backup.pl script.
To back up the MySQL user table data, run the command with the following options:
For UNIX:
./hpos_db_backup.pl -d -b -D /opt/hpom/var/mysql -c
/home/backup/user_backup.sql
For Windows:
perl hpos_db_backup.pl -d -b -D "C:\HP\OM\var\mysql" -c
"C:\backup\user_backup.sql"
Restore example
To restore both application data and MySQL user table data, run the command twice
with the respective backup files. To restore the HP Output Server application data, run
the command indicated in the restore example in the previous topic Using the
hpos_db_backup.pl script. To restore MySQL user table data run the following
command:
For UNIX:
./hpos_db_backup.pl -u -D /opt/hpom/var/mysql -c
/home/backup/user_backup.sql
For Windows:
perl hpos_db_backup.pl -u -D "C:\HP\OM\var\mysql" -c
While restoring MySQL user data when a MySQL instance is corrupted, first restore HP
Output Server application data and then restore the MySQL user data. If you try to
restore only MySQL user data without restoring HP Output Server application data, the
servers will fail to start.
NOTE: When a MySQL instance is corrupted, the restore process
using the -r option can restore HP Output Server and HP
Output Distributor databases, and it removes other
databases, if any exist.
To restore the corrupted MySQL instance, run the following commands:
For UNIX:
220
Appendix F
Hot backup
./hpos_db_backup.pl -u -r -D /opt/hpom/var/mysql
-c/home/backup/hpos_backup.sql
./hpos_db_backup.pl -u -D /opt/hpom/var/mysql
-c/home/backup/user_backup.sql
For Windows:
perl hpos_db_backup.pl -u -r -D "C:\HP\OM\var\mysql" -c
"C:\backup\hpos_backup.sql"
perl hpos_db_backup.pl -u -D "C:\HP\OM\var\mysql" -c
NOTE: Manually restore databases such as one for HP Web Delivery
and remove the backup directory from the MySQL install
directory, if it is not required.
If the process of restoring the corrupted MySQL instance fails, then the MySQL
instance is restored to the state before you started the restore operation. The MySQL and
HP Output Server servers are not started automatically; you must start them manually.
NOTE: If you take a backup of the HP Output Server database after
installing HP Output Server without submitting any jobs,
some warning messages are displayed.
HP Output Server
221
Appendix F
222
Hot backup
Appendix G
HP Output Distributor configod.pl

script
During the installation of a default set of servers for HP Output Server where an
installation of HP Output Distributor does not exist, the setup program performs the
following configuration tasks as part of installing HP Output Distributor:
Verifies that the Configuration Manager (CM) is running
Adds templates for creating HP Output Distributor logical and physical destinations
to the CM database and stores them in the
installBinDir/nls/cfg/C/od_printer_template.cfg file
Defines the OD_ADMIN permissions template in the HP Output Server Privilege

Manager (PM) database
If these configuration tasks fail during the installation of HP Output Distributor, you can
run the configod.pl script with the -i argument after the installation is completed
to perform these tasks.
NOTE: If you created a new HP Output Server domain without
configuring primary servers, the templates for configuring
destinations are not added to the CM database and the
appropriate permissions templates are not added to the PM
database in HP Output Server. To install the templates, you
must first create the primary servers manually and then run
the configod.pl script with the -i argument.
HP Output Server
223
Appendix G
HP Output Distributor configod.pl script
Using help
The configod.pl script is located in installBinDir/etc and can be run at the HP

Output Server CLI. The following sections describe the syntax for using the script.
NOTE: You can use only one argument with the configod.pl
script.
Using help
To get information about using configod.pl, enter the following:
perl ./configod.pl -h|-?
Installing templates and configuring the CM and PM

To upload HP Output Server templates for creating logical and physical destinations for
HP Output Distributor to the CM and set the appropriate permissions in the PM, use the
configod.pl script with the following syntax:
perl ./configod.pl -i
The od_connect.ini file is created in the $DAZEL_HOME/etc directory.
This file contains information such as user name, password, and the type of database
you choose to use. If you choose to use MySQL, the default user name is root and the
default password is dazel.
Removing templates
To remove HP Output Server templates for creating logical and physical destinations for
HP Output Distributor, use the configod.pl script with the following syntax:
perl ./configod.pl -r
NOTE: The od_connect.ini file that was created during the
installation process also gets removed.
224
Appendix H
Prerequisites for installing HP Output

Server with Oracle
This appendix describes the prerequisite tasks which is performed by the Oracle
database administrator for installing HP Output Server 4.1 with Oracle as the database
server.
Creating an Oracle user for HP Output Server and granting

privileges
Create a user and grant privileges using either the Oracle Enterprise Manager or the
command-line interface (CLI).
Oracle Enterprise Manager method

1.
Open Oracle Enterprise Manager in the Web browser, using the URL displayed on
the console.
NOTE: The Oracle database console should be running before you
access the URL.
The URL is in this format:
http://Oracle_Server_HostName:1158/em
Where Oracle_Server_HostName is the host name where Oracle database server is
installed.
HP Output Server
225
Appendix H
Prerequisites for installing HP Output Server with Oracle
2.
Log in to the Oracle Enterprise Manager using the user ID with privileges required
to create users and grant privileges to them.
3.
On the Database Instance page, click the Administration tab.
4.
In the User and privileges section of the Database Administration page, click the
Users link.
5.
On the Users page, click Create.
6.
Enter the data in the mandatory Name and Password fields.

If the user opts not to create the tablespace automatically during HP Output Server
installation, specify the tablespace name in the Default Tablespace field.
7.
Click OK.
The user is created.
8.
Go to the Users page and click the user you created.
9.
Click Edit.
10. On the Edit User page, click the System privileges tab.
11. Click Edit list.
12. In the Available System Privileges list on the Modify System Privileges page,
move the required privileges to the Selected System Privileges list.
NOTE: For more information about prerequisites for using Oracle as
a back-end database server, see Chapter 2, Installing HP
13. Click OK.
14. Click Apply.
CLI method
1.
Create a user by entering the following command at the command prompt:

sqlplus
SQL> create user user name identified by password;
2.
226
If you want the HP Output Server administrator to choose the automatically

create tablespace option during HP Output Server installation, enter the
following command to grant the privileges to the Oracle user:
Appendix H
SQL> grant create session, alter session, create

table, create tablespace, create sequence, drop
tablespace, alter tablespace, unlimited tablespace,
alter user to user name;
If you do not want the HP Output Server administrator to choose the
automatically create tablespace option during HP Output Server
installation, enter the following commands to grant privileges to the Oracle user
and make the created tablespace the default tablespace for the user:
-
Grant the required limited privileges to the Oracle user by entering the
following command:
SQL> grant create session, alter session, create
table, create sequence to user name;
Create the tablespace by entering the following command:

SQL> create tablespace tablespace name;
Set the tablespace quota by entering the following command:

SQL> alter user user name quota unlimited on tablespace
name;
Make the tablespace the default tablespace for the user by entering the
following command.
SQL> alter user user name default tablespace tablespace
name;
SQL> exit
Creating the tablespace

Create the tablespace and set the quota for the tablespace using either the Oracle
Enterprise Manager or the CLI.
HP Output Server
1.
Access the Oracle Enterprise Manager by completing steps 1 and 2 in Creating an

Oracle user for HP Output Server and granting privileges on page 225.
2.
3.
In the Storage section of the Database Administration page, click the Tablespace
link.
4.
On the Tablespace page, click Create.
227
Appendix H
5.
On the Create Tablespace page, enter the tablespace name in the Name field, and
select the default options displayed for Extent Management, Type, and Status.
6.
Click Add to add the datafile.
7.
Type the datafile name in the File Name field.
8.
Set the quota using the fields in the Storage section.
9.
Click Continue.
10. On the Create Tablespace page, ensure that the created datafile is selected and
click OK.
You can view the created tablespace on the Tablespace page.
CLI method
Enter the following commands at the command prompt to create the tablespace and set
the quota for the tablespace:
sqlplus
SQL> create tablespace tablespace name;
SQL> alter user user name quota unlimited on tablespace name;
SQL> exit
Configuring Oracle parameters

Configure the Oracle parameters using either the Oracle Enterprise Manager or the CLI.
NOTE: For information on tuning Oracle parameters, see
Appendix I, Tuning Oracle parameters on page 239.
228
1.
Access the Oracle Enterprise Manager by completing steps 1 and 2 in Creating an

Oracle user for HP Output Server and granting privileges on page 225.
2.
3.
In the Database configuration section of the Database Administration page,

click the All Initialization Parameters link.
4.
On the Initialization Parameters page, click the SPFile tab.
5.
Select Process and Sessions from the Category list.
Appendix H
6.
Click Go.
7.
Set the value for processes.
8.
Click Apply.
9.
On the Initialization Parameters page, select Shared Server from the Category
list.
10. Click Go.

11. Set the values for shared_servers, max_shared_servers, dispatchers, and
max_dispatchers.
12. Click Apply.
CLI method
Enter the following commands to configure the Oracle parameters at the command
prompt:
sqlplus
SQL> ALTER SYSTEM SET processes = 10241 SCOPE=SPFILE;
SQL> ALTER SYSTEM SET shared_servers = 60 SCOPE=SPFILE;
SQL> ALTER SYSTEM SET dispatchers = '(PROTOCOL=TCP)
SERVICE=ORCL)(DISP=2)' SCOPE=SPFILE;
SQL> ALTER SYSTEM SET max_dispatchers = 4 SCOPE=SPFILE;
SQL> ALTER SYSTEM SET max_shared_servers = 200
SCOPE=SPFILE;
SQL> exit
Downloading Oracle 10g and 11g Instant Client libraries

If you are using Oracle Database 10g server with HP Output Server 4.1, you must
download the Oracle 10g Instant Client libraries. If you are using Oracle Database 11g
server with HP Output Server 4.1, you must download the Oracle 11g Instant Client
libraries.
HP Output Server
You must use the 64-bit versions of the library for all UNIX platforms.
229
Appendix H
Solaris 64-bit includes an additional ODBC Instant Client Package, which should
also be downloaded and extracted to the same directory as the Instant Client
Package.
NOTE: Before you use Oracle 11.2.0.2.0 client libraries on Windows
64-bit platform, you must download and install VC++ 2005
redistributable (2005 vcredist_x64) from the following
location:
http://www.microsoft.com/download/en/det
ails.aspx?id=18471
The following table describes the driver version and the files that you need to download
for your platform.
Table C-1. Operating system and Oracle 10g Instant Client library files and version
Platform
Driver
version
Description
File to download
HP-UX on
PA-RISC
10.2.0.2
Instant Client Package - Basic

(all files required to run OCI,
OCCI, and JDBC-OCI
applications)
instantclient-basic-hpux-parisc64-10.2.0.2-20060303.zip
HP-UX on Itanium
10.2.0.2

OCCI, and JDBC-OCI
applications)
instantclient-basic-hpux-ia
64-64-10.2.0.2-20060428.zip
Solaris (SPARC)
10.2.0.3

OCCI, and JDBC-OCI
applications)
instantclient-basic-solaris
64-10.2.0.3-20070101.zip
Instant Client Package ODBC (additional libraries for

enabling ODBC applications)
instantclient-odbc-solaris64
-10.2.0.3-20070101.zip
IBM AIX
10.2.0.2

OCCI, and JDBC-OCI
applications)
instantclient-basic-aix6410.2.0.2-20060303.zip
Linux (AMD)
10.1.0.5

OCCI, and JDBC-OCI
applications)
instantclient-sdk-linuxAMD
64-10.1.0.5.0-20060519.zip
230
Appendix H
Platform
Driver
version
Description
File to download
Linux x86(64-bit
kernel)
10.2.0.3

OCCI, and JDBC-OCI
applications)
instantclient-basic-linux-x8
6-64-10.2.0.3-20070103.zip
Microsoft Windows
2003 R2 (64-bit)
10.2.0.3
Instant Client Package - Basic:

OCCI, and JDBC-OCI
applications)
instantclient-basic-win-x8664-10.2.0.3.0.zip

Microsoft Windows
2008 R2 (64-bit)
10.2.0.5
Instant Client Package - Basic:

OCCI, and JDBC-OCI
applications)
instantclient-odbc-win-x86-6
4-10.2.0.3.0.zip
instantclient-basic-win64-10
.2.0.5.zip
instantclient-odbc-win64-10.
2.0.5.zip
Platform
Driver
version
Description
File to download
Linux x86 (64-bit

kernel)
11.2.0.3

OCCI, and JDBC-OCI
applications)
instantclient-basic-linux.x6
4-11.2.0.3.0.zip
Solaris (SPARC)
11.2.0.3

OCCI, and JDBC-OCI
applications)
instantclient-basic-solaris.
sparc64-11.2.0.3.0.zip
IBM AIX
11.2.0.3

OCCI, and JDBC-OCI
applications)
instantclient-basic-aix.ppc6
4-11.2.0.3.0.zip
HP Output Server
231
Appendix H
Platform
Driver
version
Description
File to download
HP-UX on
PA-RISC
11.1.0.7

OCCI, and JDBC-OCI
applications)
basic-11.1.0.7.0-hpux-parisc
64.zip
HP-UX on Itanium
(11.23)
10.2.0.2

OCCI, and JDBC-OCI
applications)
instantclient-basic-hpux-ia6
4-64-10.2.0.2-20060428.zip
HP-UX on Itanium
(11.31)
11.2.0.3

OCCI, and JDBC-OCI
applications)
instantclient-basic-hpux.ia6
4-11.2.0.3.0.zip
Microsoft Windows
2003 R2 and 2008
R2 (64-bit)
11.2.0.2

OCCI, and JDBC-OCI
applications)
instantclient-basic-windows.
x64-11.2.0.2.0.zip

instantclient-odbc-windows.x
64-11.2.0.2.0.zip
To download the Oracle Instant Client libraries, follow these steps:

1.
Access the following Web site:

http://www.oracle.com/technetwork/database/features/
instant-client/index-097480.html
2.
232
Select and download the Oracle Instant Client Package for your platform.
Appendix H
3.
Extract the contents of the.zip file.

NOTE: On UNIX, HP recommends that you extract the Oracle
Client libraries to the directory
installInstDir/var/oracle_client_library/lib.
NOTE: On UNIX, the ownership of the Oracle Instant Client
libraries installation directory must be set to the owner of the
HP Output Server installation and the permissions for this
directory must be set to 555, which provides read and
execute permissions to the owner, group, and others.
NOTE: On Windows, you must create a lib folder under any
location on your system and download both the Oracle
Instant Client libraries and the Oracle ODBC driver for
Windows to the lib folder.
To change the security context of the downloaded Oracle Instant Client libraries on
SELinux-enabled installations follow these steps:
1.
Run the following command to change the security context:

chcon R v t textrel_shlib_t
installInstDir/var/oracle_client_library
2.
Run the ls Z command to verify the security context for the Oracle Instant
Client libraries files.
Installing Easysoft ODBC-Oracle Driver

If you are using Oracle database server with HP Output Server on UNIX platforms, you
must install the Easysoft ODBC-Oracle Driver, Version 3.2.26. Perform the following
steps to install the Easysoft ODBC-Oracle Driver:
1.
Register as an Easysoft user.
2.
Download the Easysoft drivers from the following location:

ftp://ftp.easysoft.com/pub/oracle
HP Output Server
233
Appendix H
The following table lists the appropriate Easysoft ODBC-Oracle drivers for
different platforms:
Table C-3. Easysoft ODBC-Oracle Drivers
Platform
Driver version
Linux
odbc-oracle-3.2.26-linux-x86-64.tar
HP-UX on PA-RISC
odbc-oracle-3.2.26-hpux-parisc2.tar
HP-UX-ia64
odbc-oracle-3.2.26-hpux11-ia64.tar
Solaris (SPARC)
odbc-oracle-3.2.26-sunos-sparcv9.tar
IBM AIX
odbc-oracle-3.2.26-aix50+-ppc64.tar
3.
Untar the .tar file to a directory with adequate space.
4.
Log in as the root user.
5.
Run the Easysoft ODBC-Oracle Driver install script as follows:

i.
Start the script by entering the following command:

./install
The license agreement appears.
ii.
Respond to the prompts as described in the following table:
Prompt
Action and description
Do you accept the license?

(q=quit, yes, no):
Enter yes.
Enter a base install

directory (q=quit) [
/usr/local]:
By default, this is /user/local. However,

HP recommends that you install the Easysoft
ODBC-Oracle driver in the installInstDir/var/
directory.
Do you already have the

unixODBC DM installed?
Enter n.
(y/n i=do not know) [n]):

Would you like to request a
Easysoft ODBC-Oracle Driver
license now (y/n) [y]:
234
Select the default option if you are installing

the UNIX ODBC driver manager on the
system for the first time.
Enter n.
Appendix H
Prompt
Is this because you intend to

use an Oracle 10g Instant
Client (y/n) [y]:
Enter y.
Enter the name or IP address

of the Oracle server (i.e.
server):
Enter the name or IP address of the Oracle

database server.
Enter the port the Oracle

server is listening on
(default 1521):
Enter the port number to which the Oracle

database server is listening.
Enter the Oracle Service Name

(i.e. test):
Enter the service name of Oracle database

server.
Enter an Oracle user name

(i.e. system):
Enter the Oracle database server user name.
Enter the Oracle password for

<user name> (i.e. manager):
Enter the password of the Oracle database

server user.
Install unixODBC/Easysoft
ODBC-Oracle Driver data
source (y/n) [y]:
Enter n.
6.
Run the Easysoft ODBC-Oracle Driver license script as follows:

i.
Enter the following command at the command prompt to navigate to the

location of the Easysoft licence script:
cd easysoftDir/license
ii.
Start the license script by entering the following command:

./licshell
NOTE: While running the script, you are prompted for an
authorization code from Easysoft. Contact your
Implementation and Integration Services representative to
get the authorization code.
HP Output Server
235
Appendix H
iii. Respond to the prompts as described in the following table:

Prompt
If this program cannot

determine the IP address of
license.easysoft.com it will
try 213.249.238.4
Enter 2.
[0] Exit
[1] View existing licenses
[2] Oracle ODBC Driver V3.2
Please choose the product you
would like a license for by
entering its item number or
enter one of the other
options.
Option:
Name (Your full name) []:
Enter your name.
Company (Your company name)

[]:
Enter your company name.
Email (A contact email

address) []:
Enter your email address.
Phone (Your telephone number)

[]
Enter your telephone number.
Fax (Your fax number) []:
Enter your fax number.
Ref (An authorisation code

from Easysoft - leave blank
for trials):
Enter the authorization code.
How would you like to obtain

the license?
Enter 2.
[1] Automatically by
contacting the Easysoft
License Daemon
[2] Write information to file
so you can fax, telephone it
[3] Cancel this operation
236
Appendix H
Prompt
License Request written to

./license_request.txt
Enter 0.
[0] Exit
[1] View existing licenses
[2] Oracle ODBC Driver V3.2
The license request file is created.

NOTE: In a multi-NIC configuration on the Linux operating system,
you must obtain an Easysoft license for each NIC card.
To retrieve the site information number of each NIC card,
which is required to obtain licenses, use the following
command:
./licshell muladd
iv. Contact your Implementation and Integration Services representative with the
license_request.txt file to obtain the license key.
v.
Add the obtained license key at easysoftDir/license/licenses.
You are now ready to use the Easysoft ODBC-Oracle Driver.

NOTE: You may choose to install HP Output Server in a failover
scenario where both machines share a common file system
that has both HP Output Server and Easysoft installations. In
this scenario, the licenses file can be shared with a license
key for each machine listed in the licenses file.
HP Output Server
237
Appendix H
238
Appendix I
Tuning Oracle parameters

To tune Oracle parameters to obtain optimum performance from your HP Output Server
installation with Oracle as the database server, follow these steps.
NOTE: The recommended settings for Oracle parameters provided
in this section are for HP Output Server. If other applications
are using the Oracle database server instance, those
applications might work optimally with other recommended
values.
1.
HP Output Server
Determine the number of HP Output Server processes that will connect to an Oracle
database server instance. The following HP Output Server servers connect to the
Oracle database server:
-
Namespace Manager (NM)
Accounting and Inventory Manager (AIM)
Event Manager (EM)
Configuration Manager (CM)
Delivery Manager (DM)
Job and Queue Manager (JQM)
Destination Manager (DSM)
239
Appendix I
To obtain the number of HP Output Server processes for your HP Output Server
configuration, count the HP Output Server servers connecting to the Oracle
database server instance.
For example, consider an HP Output Server configuration with five primary servers
(NM, PM, CM, AIM, and EM), an LPR Gateway server, 16 JQMs, and 160 DSMs.
The number of HP Output Server servers connecting to the Oracle database server
is: 5 (NM, PM, CM, AIM, and EM) + 10 (DLM) + 16 (JQM) + 160 (DSM) = 191
NOTE: You need not count the LPR Gateway, SAPconnect, and
OMS Callback processes because they do not connect to the
Oracle database server.
2.
Determine the number of connections to the database.

Every HP Output Server server connecting to the Oracle database server currently
maintains 10 database connections in the connection pool:
Total number of connections to the database is 191 * 10 = 1910
NOTE: This total number of connections to the database is constant
and does not change during the HP Output Server operation.
Some connections will be timed by the Oracle database
server if HP Output Server is idle for a long time. To tune the
idle connection time, see the Oracle documentation.
3.
Set the Oracle database server to run in shared server configuration mode as
follows:
i.
dispatchers: Set the value of the dispatchers parameter by using the

following equation:
Total number of connections to the database / 1000 = <dispatchers value>
For example, if the total number of connections to the database is 1910 and the
resultant value is 1.91, set the dispatchers parameter to 2 (1.91 can be
rounded off to 2).
ii.
max_dispatchers: Set the value of the max_dispatchers parameter by

using the following equation:
<dispatchers value> * 2 = <max_dispatchers value>
iii. max_shared_servers: Set the value of the max_shared_servers

parameter by using the following equation:
240
Appendix I
Oracle recommends one shared process for every 10 connections. Every HP

Output Server server connecting to the Oracle database server currently
maintains 10 database connections in the connection pool. The number of
database connections is approximately equal to the number of HP Output
Server processes that will connect to an Oracle database server instance.
Total number of HP Output Server processes connecting to Oracle database
server + <buffer> = <max_shared_servers value>
To determine the value of max_shared_server, add a small buffer of 5 or
10 to the number of HP Output Server processes that will connect to an Oracle
database server instance.
NOTE: HP recommends that you use a buffer value of 5. If the
rounding operation of total number of HP Output Server
processes connecting to the Oracle database server results in
a number greater than 5, you do not need to add an additional
buffer.
NOTE: If the total number of HP Output Server processes
connecting to the Oracle database server results in an integer
not divisible by 10, round it to the next highest integer.
For example, if the total number of HP Output Server
processes connecting to Oracle database server is 192, set
the max_shared_server parameter to 200. You do not
need to add an additional buffer in this case.
iv. shared_servers: Set the value of the shared_servers parameter by using
the following equation:
<max_shared_servers value> / 3 = <shared_servers value>
For example, if max_shared_servers is 195 and the resultant value is 65,
set the shared_servers parameter to 60 or 70.
v.
queuesize: Set the value of the queuesize parameter in the

listener.ora file by using the following equations:
Equation 1: Total number of HP Output Server processes connecting to Oracle
database server - Number of DSMs = <Result of Equation 1>
Equation 2: Number of DSMs / 10 + <Result of Equation 1> = <queuesize>
vi. processes: Set the value for processes related to kernel parameters of the
operating system.
HP Output Server
241
Appendix I
For HP-UX PA-RISC, HP recommends that the value of this parameter be no

more than semmsl. Typically, a value of 1000 is recommended for this
parameter. See the Oracle documentation for your operating system for more
information on setting this parameter.
vii. sessions and transactions: Set values for the sessions and
transactions parameters.
These values are obtained from the processes parameter. HP recommends
default derivations.
242
Appendix J
Limited access to directories and files

HP Output Server 4.1 limits the read, write, and execute permissions on directories and
files, and restricts access privileges to user IDs that do not belong to the primary group
of the owner.
For example:
The installInstDir/var/jobdb and installInstDir/var/cm directories have the
drwxr-x--- permissions, which means that the owner has read, write, and execute
permissions; the group has read and execute permissions; and others do not have any
permissions.
The scripts that set up the environment, setup_env.sh and setup_env.pl, have
-rw-rw-r-- permissions, which means that the owner has read and write
permissions, the group has read and write permissions, and others have read permission.
All the server log files, such as nm.log, pm.log, em.log, aim.log, cm.log,
dlm.log, jqm.log, and dsm.log, in the installInstDir/var/log/ directory
have the -rw-r----- permissions, which means that the owner has read and write
permissions, the group has read permissions, and others do not have any permissions.
HP Output Server
243
Appendix J
244
Limited access to directories and files
Appendix K
Installing OpenSSL
This section describes how to install Open SSL on different platforms.
Linux
OpenSSL comes installed with most Linux distributions.
HP-UX
OpenSSL does not come installed by default but HP provides OpenSSL binaries that
can be installed on HP-UX 11i versions. Refer to
http://h20392.www2.hp.com/portal/swdepot/displayProd
uctInfo.do?productNumber=OPENSSL11I.
IBM AIX
OpenSSL does not come installed by default but IBM provides OpenSSL binaries that
can be installed on AIX.
To install Open SSL on IBM AIX follow these steps:
1.
Install Open SSL available in RPM packages on the AIX toolbox of the Linux
applications CD-ROM.
or
Download the RPM packages from the AIX toolbox using the Linux Applications
Web site:
HP Output Server
245
Appendix K
Installing OpenSSL
http://www-1.ibm.com/servers/aix/products/aixos/linux/
download.html.
OpenSSL package contains cryptographic content, you must register on the Web
site to download the packages. To register and download the packages, follow these
steps:
i.
Click the AIX Toolbox Cryptographic Content link on the right

pane of the AIX Toolbox from the Linux Applications Web site.
ii.
Click on the option, I have not registered before. Fill in the

required fields in the form.
iii. Read and accept the license agreement. The browser automatically redirects
you to the download page.
iv. Select openssl-0.9.6m-1.aix4.3.ppc.rpm under OpenSSL SSL Cryptographic Libraries from the displayed list of
cryptographic content packages.
v.
2.
Click on Download Now to install

openssl-0.9.6m-1.aix4.3.ppc.rpm.
On downloading the OpenSSL package, you can install OpenSSL and OpenSSH.
Install the OpenSSL RPM package using the following geninstall command:
# geninstall -d/dev/cd0 R:openssl-0.9.6m.
On successful installation of the application, a success message is displayed.
Windows
OpenSSL binaries are not shipped or distributed for Windows. OpenSSL binaries can be
downloaded using the link:
http://www.openssl.org/
246
Appendix L
Configuring and administering HP

Web Console Job Manager
This appendix describes how to configure and administer HP Web Console Job
Manager.
HP Web Console Job Manager is installed automatically when you installed HP Output
Server. With HP Web Console Job Manager, administrators can view job details and
track, resubmit, modify, pause, resume, and cancel all jobs submitted through HP
Output Server.
NOTE: You must restart the JBoss server if you encounter a database
connection error after you install HP Output Management
Web Console. When the JBoss server is restarted, the
configuration file containing the access details of the HP
Output Management database will be uploaded successfully.
To take full advantage of all the administrative capabilities available in HP Web
Console Job Manager, you may need to modify its configuration beyond the default
configuration provided during the installation of HP Output Server.
HP Output Server
247
Appendix L
Configuring and administering HP Web Console Job Manager
Before you begin
The following two scripts are on the server where HP Web Console Job Manager is
installed: DomainManager (used to manage the definition of HP Output Server
domains in HP Web Console Job Manager) and AuthenticationManager (used to
manage the definition of authentication methods).
NOTE: Upon installation, HP Web Console Job Manager is
configured to use the domain on which it was installed. The
default installation may provide all of the functionality
needed for your environment. When additional domains are
required, these scripts can be used.
NOTE: If you have an existing HP Web Console Job Manager
installation, when you install HP Output Server, you cannot
retain the database of the earlier version of HP Web Console
Job Manager.
NOTE: If the DomainManager.sh script is unavailable after
reconfiguring the MySQL servers, you must execute the
following commands before accessing the HP Web Console
Job Manager application:
perl jmconfig.pl -t
perl jmconfig.pl -i -p <jboss_port>
This appendix focuses primarily on the command-line interface (CLI). Additional
administrative tasks are performed through the Web browser. Some are mentioned in
this appendix, but they are primarily documented in the online Help.
Before you begin

Before you begin, you should have installed HP Output Server by following the
instructions in Chapter 2, and you should verify that you can access HP Web Console
Job Manager with a supported Web browser.
248
Appendix L

Domain groups
Domain groups
Domain groups allow you to perform actions across multiple HP Output Server domains
at one time from within HP Web Console Job Manager. A given domain group has a
unique name and can contain any number of HP Output Server domains defined in HP
Web Console Job Manager.
Domain groups are managed through the Web interface and can be managed only by
administrators. For more information, see Configuring Domain Groups in the online
Help.
Managing HP Output Server domains

The DomainManager script provides functionality like adding, listing, editing, and
deleting domains. This section describes how to use the DomainManager script to
manage HP Output Server domains in HP Web Console Job Manager.
NOTE: Only HP Output Server users belonging to the
dazel_superuser group can perform domain
management. Therefore, ensure that you log in as an
administrator of HP Output Server before you run the
domain management utility. For more information about
which users are administrators, see Authorization
on page 251.
The DomainManager script is available as a shell script on UNIX
(DomainManager.sh) and as a batch file on Windows (DomainManager.bat).
Use the correct command for your operating system. The syntax descriptions and
examples in this section use UNIX conventions.
Adding domains
You can add new domains to HP Web Console Job Manager by executing the following
command:
DomainManager.sh -o add -D domainName -H hostName
-P portNumber
where
domainName is the HP Output Server domain name.
hostName is the name of the host system where HP Output Server is running.
HP Output Server
249
Appendix L
Managing HP Output Server domains
portNumber is the port number to which HP Output Server is listening.

For example:
DomainManager.sh -o add -D horse.d
-H horse.txn.cpqcorp.net -P 4009
Listing domains
You can list all of the domains that are configured in HP Web Console Job Manager by
DomainManager.sh -o list
NOTE: Add at least one domain before performing the list operation;
otherwise, the list operation will fail.
Editing domains
You can edit the domains that have already been configured in HP Web Console Job
Manager by executing the following command:
DomainManager.sh -o edit -D domainName [-d
newDomainname] -H hostName [-h newHostName]
-P portNumber [-p newPortNumber]
where
newDomainname is the replacement name for the domain.
hostName is the host name of the system where HP Output Server is running.
newHostName is the replacement host name for the domain.
newPortNumber is the replacement port number for the domain.
Deleting domains
You can delete existing domains that have been configured in HP Web Console Job
Manager by executing the following command:
DomainManager.sh -o delete -D domainName -H hostName -P
portNumber
250
Appendix L

Authorization
where
hostName is the host name of the system where HP Output Server is running.
NOTE: Deleting a domain through the CLI does not completely
remove that domain from a domain group; you must also
delete it from the domain group(s) using the Web interface.
Authorization
Typical HP Web Console Job Manager operations (such as canceling jobs) are
authorized using the existing permissions and object types in the Privilege Manager of
the applicable HP Output Server domain.
However, some features in HP Web Console Job Manager are available only to
privileged users. Accessing these features requires authorization. HP Web Console Job
Manager uses the HP Output Server Privilege Manager to perform user authorization.
Functionality of HP Web Console Job Manager that can be accessed by users identified
as administrators includes the following:
Authentication method managementOnly administrators can define and

configure authentication methods available to end users. End users can select which
authentication method to use when accessing the application, if more than one
method is defined.
Domain configurationOnly administrators can associate HP Output Server with

HP Output Server domains, and define and manage domain groups. End users can
select which domain or domain group to use when managing jobs.
Custom search managementOnly administrators can create, manage, and share

custom searches with all users. End users can create custom searches and manage
only self-created custom searches. End users cannot share the custom searches.
However, they can use self-created and administrator-created custom searches.
HP Output Server automatically recognizes members of the dazel_superuser

Privilege Manager group as administrators.
HP Output Server
251
Appendix L
Authentication
In addition, any user or group having access rights for object HP Web Console Job
Manager of type OMWC with MANAGE permission is defined as an HP Output
Management Web Console administrator. For more information on adding permissions,
see the Privilege Manager chapter in the System Administrators Guide for HP Output
Server.
To determine if a user has administrative privileges, HP Web Console Job Manager
consults the Privilege Manager of the primary domain. If for some reason HP Output
Server cannot contact that domain, it searches the list of domains until one can be
contacted and checks for privileges with the Privilege Manager of that domain.
NOTE: Authorization will not be successful if HP Output Server
domains are not configured in HP Web Console Job
Manager.
Authentication
The process of confirming the identity of an authorized user is known as authentication.
HP Web Console Job Manager provides a built-in authentication method as well as the
ability to add custom authentication methods.
Trusted authentication
HP Web Console Job Manager's built-in authentication method is a form of client-side
authentication. In client-side authentication, the server assumes that the user has been
authenticated by the operating system on the client machine where the user is logged in.
HP Web Console Job Manager refers to this as trusted authentication.
With trusted authentication, a Java applet is executed on the users system. This applet
is signed with security credentials and obtains the following information from the
operating system and sends it back to the server:
252
User name with which the user has logged into the client operating system
On Windows, the domain on which the user is logged in
Appendix L

Authentication
Host name or IP address, or both, of the client system

NOTE: Depending on the security level and trusted certifying
authorities (CA) in the user's browser, the user may be
prompted for permission to execute the applet. If the security
level is set too high or the user is denied permission, then the
applet will not run. If the authentication method requires the
applet (as does trusted authentication), the user will not be
able to access HP Web Console Job Manager.
The trusted authentication method uses the user name (or domain\user name on
Windows) obtained by the applet for authorization and checks with the HP Output
Server Privilege Manager.
Enforced authentication
Custom authentication methods are referred to as enforced authentication. With
enforced authentication, a back-end script implemented on the server is executed
whenever the custom authentication method is used by a client.
Enforced authentication methods can use the applet provided by the built-in client-side
authentication, but cannot request additional information beyond what is already
provided. In this case, a custom script uses the information provided by the applet to
determine a user name for the HP Output Server Privilege Manager other than the user
name (or domain\username) that the built-in client-side authentication methods provide.
For example, if you were to send a user name with a prefix of the SAP server to the
Privilege Manager, the script would remove the Windows domain name (if present) and
prepend an SAP server name instead, before sending the user name to the Privilege
Manager.
Running the applet on the client is optional for advanced enforced authentication
methods. Such custom authentication methods can gather the information using other
means (in addition to or instead of using the applet), usually through a special HTML
form. For example, users could be prompted for a password, SAP user ID, or some other
data used to identify themselves. The additional information can be used to perform
server-side authentication to confirm that identity.
Advanced enforced authentication methods also allow the user to provide an HTML
error page in the event that the authentication method fails. Custom authentication
scripts that do not include an input HTML form are referred to as basic enforced
authentication methods.
HP Output Server
253
Appendix L
Authentication
Enforced authentication scripts have access to variables defined by the applet used for
trusted authentication as well as to variables defined by the input form. The scripts use
this information to authenticate a user and return the name of the HP Output Server user.
Authentication scripts return an error message when authentication fails. Return values
are used as follows:
Return code: 0 indicates successful authentication; anything else indicates failure.
Standard Out: User name to send to the HP Output Server Privilege Manager
Standard Error: Single-line failure message for the login error page
Samples of a script and pages are provided in the following locations:
Script: installBinDir/examples/JobManagerAuth.pl
Input page: installBinDir/examples/JobManagerAuth.jsp
Error page: installBinDir/examples/JobManagerAuthError.jsp
NOTE: Ensure that the input HTML file has a form with action as
binaryaction.do and method as post.
Login session time-out

HP Web Console Job Manager maintains a login session for each user for a specific
time interval. If the specified amount of time passes without activity from the client, the
user is automatically logged out on the next activity. The user then must re-authenticate
to access the HP Web Console Job Manager. This time-out is a configurable setting and
is set to 30 minutes by default.
254
Appendix L

Managing authentication methods
To modify the time-out setting, edit the line indicated in the following example in the
installDir/share/jboss/server/default/deploy/jbossweb.deployer/conf/web.xml file:
<session-config>
<session-timeout>
30 !-- 30 minutes -</session-timeout>
</session-config>.
<(edit this line)
WARNING: Increasing the session time-out may cause performance

(in terms of memory usage or speed or both) to degrade
because user query results may have to be cached on the
server for a longer period of time. This setting is global
and changing it may adversely affect any of the three
components of HP Smart Office Delivery for Output
Server.

This section describes how to use the AuthenticationManager script to add, list,
edit, and delete authentication methods for HP Output Server.
NOTE: You must be an HP Web Console Job Manager administrator
to manage authentication methods. Therefore, ensure that
you log in as an HP Web Console Job Manager administrator
before you run the authentication management utility. For
more information about which users are administrators, see
Authorization on page 251.
NOTE: The AuthenticationManager script is available as a
shell script on UNIX (AuthenticationManager.sh)
and as a batch file on Windows
(AuthenticationManager.bat). Use the correct
command for your operating system. The syntax
descriptions and examples in this section use UNIX
conventions.
HP Output Server
255
Appendix L
The syntax for the AuthenticationManager script is as follows:

AuthenticationManager.sh -o operation
operation_specific_arguments
where:
operation = list|list_all|add|edit|del|del_all.
operation_specific_arguments are described in the following sections.
NOTE: Changes made to the authentication methods through the
CLI are immediately propagated to the Web interface.
Adding authentication methods

For an example of how to add an authentication method on both UNIX and Windows,
see the text of the sample script located at
installBinDir/examples/JobManagerAuth.pl.
The syntax for adding authentication methods is as follows:
AuthenticationManager.sh -o add -n method_name
-d Default|Non-Default
-t trusted|basic-enforced|advanced-enforced
[-i input_html_path -e error_html_path]
[-b binary_path [-a comma_separated_arguments]]
[-p disable|enable]
where:
method_name is the user-visible label given to the authentication method.

NOTE: The size of the authentication name is limited to 30
characters. Special characters other than underscore ( _ )and
hyphen (-) are not allowed. Spaces are also not allowed.
Alphanumeric characters are valid. The first character in the
authentication name should be an alpha character.
256
Appendix L

Default or Non-Default signifies if the authentication method should be the

default method used when users log in to HP Output Management Web Console for
the first time.
NOTE: If none of the third-party authentication mechanisms is set as
default, the built-in client-side authentication method will be
used as the default authentication method.
trusted, basic-enforced, or advanced-enforced signifies the type of

authentication.
input_html_path is the HTML file to be used to gather additional information for

advanced enforced methods.
error_html_path is the HTML file to be displayed if authentication fails (for

advanced enforced methods only).
binary_path is the name of the executable to be used to check authentication (for

enforced methods only).
NOTE: If the executable is a script (such as a Perl script), the
binary_path should be the script engine (for example,
/opt/hpom/bin/perl) and the first argument should be
the script itself.
comma_separated_arguments is a comma-separated list of arguments to be passed

to the executable (for enforced methods only).
NOTE: Specify the value of the third-party binary name as the first
argument in the -a switch. You can specify any number of
arguments in any form for an input HTML file.
HP Output Server
disable or enable signifies if the applet should be enabled or disabled. By

default the applet is enabled.
257
Appendix L
To add a new basic enforced authentication mechanism with the name SAPAustin, a
third-party binary name of /opt/hpom/custom/sapAuth.pl, a configuration file
name of /opt/hpom/custom/sapmysql.conf, and applet values of
$username, $hostname, and $domain, execute the following command:
AuthenticationManager.sh -o add -n "SAPAustin"
-d Non-Default -t Basic-Enforced
-b /opt/hpom/bin/perl
-a "/opt/hpom/custom/sapAuth.pl,/opt/hpom/custom/
sapmysql.conf,\"\$username\",\"\$hostname\",\"\
$domain\""
NOTE: The applet provides values for $username,
$hostname,$domain, and $user-agent.
To add a new advanced enforced authentication mechanism with the name
SAPBangalore, a third-party binary name of
/opt/hpom/custom/sapAuth.pl, a configuration file name of
/opt/hpom/custom/sapmysql.conf, applet values of $username,
$hostname, and $domain, input HTML values of $input_usr and
$input_pwd, and the specified HTML input form and error page, where you want
this authentication method to be the default, execute the following command:
AuthenticationManager.sh -o add -n "SAPBangalore"
-d Default -t advanced-enforced
-i /opt/hpom/custom/sapAuth.htm
-e /opt/hpom/custom/sapAuthError.htm
-b /opt/hpom/bin/perl
-a "/opt/hpom/custom/sapAuth.pl,/opt/hpom/custom/
sapmysql.conf,\"\$username\",\"\$hostname\",\"\
$domain\",\"\$input_usr\",\"\$input_pwd\""
The Web page /opt/hpom/custom/SapAuth.htm will be displayed when a user
attempts to authenticate. If the user authentication fails,
/opt/hpom/custom/sapAuthError.htm will be displayed.
NOTE: On UNIX, because $ is a special character for the shell, HP
recommends using \ to escape $ while invoking
AuthenticationManager.sh. $ represents the value of the
attribute with which it is displayed.
258
Appendix L

Listing authentication methods

To list all configured authentication methods, execute the following command:
AuthenticationManager.sh -o list_all
NOTE: The list_all operation does not list the built-in
client-side authentication method.
To list the authentication method with a specific ID, execute the following command:
AuthenticationManager.sh -o list -id id
where:
id is the ID number of the authentication method you want to list.
Editing authentication methods

The syntax for editing authentication methods is as follows:
AuthenticationManager.sh -o edit [-n method_name]
[-d Default|Non-Default]
[-t trusted|basic-enforced|advanced-enforced]
[-i input_html_path -e error_html_path]
[-b binary_path] [-a comma_separated_arguments]
[-p disable|enable]
-id id
where:
id is the ID number of the authentication method you want to edit.
All other values are the changes to the existing authentication method that you want
to make.
For example, to enable or disable the authentication applet for an enforced
authentication mechanism with an ID of 14, execute the following commands:
AuthenticationManager.sh -o edit -id 14 -p disable
AuthenticationManager.sh -o edit -id 14 -p enable
By default, the applet is enabled for enforced authentication mechanisms.
HP Output Server
259
Appendix L
You can also use the script to designate an authentication mechanism as the default. For
example, to designate the mechanism with an ID of 10 as the default, execute this
command:
AuthenticationManager.sh -o edit -id 10 -d Default
NOTE: Setting the current authentication mechanism as non-default
automatically sets the client-side authentication mechanism
as default.
Deleting authentication methods

To delete all configured authentication methods, execute the following command:
AuthenticationManager.sh -o del_all
To delete the authentication method with a specific ID, execute the following command:
AuthenticationManager.sh -o del -id id
where:
id is the ID number of the authentication method you want to delete.
NOTE: The built-in client-side authentication method cannot be
deleted.
The default authentication method cannot be disabled or deleted; to disable or

delete it, first set another method as the default.
If an authentication method is activated and the input HTML form, error HTML, or
binary is not available at the expected location, an error message is displayed.
Setting or modifying the login session time-out

In HP Output Management Web Console, the login session is a configurable setting and
can be set for each user for a specific time interval.
Example:
260
Appendix L

To modify or set the time-out setting for 15 minutes, edit the following line
installDir/share/jboss/server/default/deploy/jbossweb.deployer/conf/web.xml file:
<session-config>
<session-timeout>
15 !-- 15 minutes -</session-timeout>
</session-config>
HP Output Server
<(edit this line)
261
Appendix L
262
Appendix M
Configuring MySQL for HP Output

Management
This chapter describes how to configure MySQL for HP Output Management to grant
access to HP Output Management programs on remote hosts and how to adjust variables
to optimize database performance with HP Output Server.
Granting access for HP Output Management

products on remote hosts
If HP Output Management products or remote systems will be connecting to the
MySQL server, you must add access privileges to the MySQL server for those remote
hosts.
NOTE: The following procedure uses the forward slash (/) on
UNIX. On Windows, use the backslash (\).
To add access privileges:
1.
In a UNIX shell or in a Windows Command Prompt window, type the following

commands:
./mysql -defaults-file=mySQLinstallDir/my.cnf
--password=password
where mySQLinstallDir is the installation path for your MySQL installation.
HP Output Server
263
Appendix M
Configuring MySQL for HP Output Management
Granting access for HP Output Management products on remote hosts
If you are using MySQL provided with HP Output Server 4.1 as the backend
database, use the following commands:
For UNIX
cd $HPOM_INSTALL/share/mysql/5.0.24/bin
./mysql -defaults-file=$DAZEL_HOME/etc/my.cnf
--password=password
For Windows
mysql -defaults-file=$DAZEL_HOME/etc/my.cnf
--password=password
2.
For each additional host privilege you want to add, type the following commands.
If the remote system is identified by multiple host names, you may need to issue
additional GRANT commands for each short and long host name.
GRANT ALL PRIVILEGES ON *.* TO user@shortHostName
IDENTIFIED BY password;
GRANT ALL PRIVILEGES ON *.* TO user@longHostName
IDENTIFIED BY password;
where:
-
user is the user for which you are adding privileges. This user does not need to
be a UNIX (or Windows) login user.
shortHostName is the default host name of the remote host, for example,
lion.
longHostName is the default host name with the TCP/IP domain name of the
remote host, for example, lion.bigcompany.com.
password is the password the user will use when connecting to MySQL.
NOTE: Host names used in a GRANT command must resolve to an
IP address. You cannot use an IP address in a GRANT
command.
NOTE: The single quotes around user and
ShortHostName/LongHostName must be included when
typing the command.
264
Appendix M
Granting access for HP Output Management products on remote hosts
After you enter each GRANT command, you will see a message similar to the
following:
Query OK, O rows affected.
3.
When you have finished adding the host privileges, update the MySQL cache as
follows:
FLUSH PRIVILEGES;
4.
To verify that you have added the appropriate privileges, type the following:
SELECT User,Host FROM mysql.user;
MySQL returns user and host privilege information similar to the following
example:
+---------+---------------------------+
| User
| Host
|
+---------+---------------------------+
| root
| tiger
|
| root
| tiger.bigcompany.com
|
| root
| localhost
|
| mysql
| tiger
|
| mysql
| tiger.bigcompany.com
|
| mysql
| localhost
|
| mysql
| lion
|
| mysql
| lion.bigcompany.com
|
+---------+---------------------------+
8 rows in set (0.00 sec)
5.
If your entries are correct, return to the command prompt by typing the following:
exit
HP Output Server
265
Appendix M
Adjusting variables for MySQL for HP Output Management
Example
The following example shows how to grant MySQL access to other HP Output
Management applications on the remote host lion. The password for the MySQL root
user is secret. In this example, the other HP Output Management applications will
connect to the MySQL server with the user otheruser and the password somepass.
./mysql --defaults-file=mySQLinstallDir/my.cnf mysql
GRANT ALL PRIVILEGES ON *.* TO otheruser@lion
IDENTIFIED BY somepass;
GRANT ALL PRIVILEGES ON *.* TO
otheruser@lion.bigcompany.com IDENTIFIED
BYsomepass;
FLUSH PRIVILEGES;
SELECT User,Host FROM mysql.user;
exit
If you are using MySQL provided with HP Output Server 4.1 as the backend database,
use the following commands:
For UNIX
./mysql --defaults-file=$DAZEL_HOME/etc/my.cnf
--password=password
For Windows
mysql --defaults-file=$DAZEL_HOME/etc/my.cnf
--password=password
Adjusting variables for MySQL for HP Output

Management
This section describes how to configure the MySQL database to optimize performance
with HP Output Server.
Concurrent connections to MySQL

If HP Output Server allows many concurrent connections to the MySQL server, the HP
Output Server performance can increase significantly.
266
Appendix M

The -database-client-max-connections single-valued attribute specifies

the maximum number of concurrent MySQL connections allowed per HP Output Server
server. For more information about setting this attribute, see the System Administrators
Guide for HP Output Server.
connect_timeout
The MySQL connect_timeout system variable defines the length of time that the
MySQL server will keep a connection open for a client until the MySQL server receives
a query. If the query is not received within connect_timeout seconds, the MySQL
server closes the connection. The client can make up to three attempts to re-initiate the
request before logging a failure message from MySQL. The MySQL default for
connect_timeout is 5 seconds.
If MySQL is running on a remote system, or if a client is unable to provide a query to
MySQL within the time set for connect_timeout, the following message appears
in the HP Output Server server log files:
[error 00064007] mySQL connection failed (Lost
connection to MySQL server during query).
The my.cnf file created by setupmysql.pl or configmysql.pl during an
installation of HP Output Server does not include an entry for connect_timeout. If
this message occurs frequently in the HP Output Server logs, you can improve
reliability by adding a connect_timeout value to the my.cnf file. Depending on
your environment, consider using 20 as the value for this variable.
To change the default setting for connect_timeout, add an entry for this variable in
the Tuning Parameters section (under Server/Services) of the my.cnf file. For
example:
#connection timeout for clients
connect_timeout=20
max_connections and the max_thread_proc kernel parameter

The MySQL max_connections tuning variable defines the number of concurrent
client connections or threads the MySQL server can accept. When you install MySQL
for HP Output Management, the my.cnf file created by setupmysql.pl or
configmysql.pl sets max_connections to 1000.
On HP-UX systems, the max_thread_proc kernel parameter defines the maximum
number of threads the kernel allows for each process. If max_connections is
greater than max_thread_proc, requests from HP Output Server to the MySQL
HP Output Server
267
Appendix M
server might fail because the kernel will not allow MySQL to create threads greater than
the number specified by max_thread_proc. The HP Output Server clients log
displays the following message when this occurs:
[error 00064007] mySQL connection failed (Too many
connections)
HP recommends that you set max_thread_proc to 1024 on HP-UX systems.
thread_cache
The MySQL thread_cache system variable maintains a pool of threads for
servicing requests. When you install MySQL for HP Output Management, the my.cnf
file created by setupmysql.pl or configmysql.pl sets thread_cache to
100.
Setting thread_cache reduces the load on the operating system and can improve
overall performance. If thread_cache is not set or is set to 0, MySQL creates a
thread every time a connection is made. When the connection is closed, MySQL deletes
the thread. Because HP Output Server clients open and close connections to MySQL
with every request, threads are created and deleted with each request if
thread_cache is not set.
innodb_max_purge_lag
The MySQL innodb_max_purge_lag system variable controls how to delay
INSERT, UPDATE, and DELETE operations when the purge operations are lagging.
When you install MySQL for HP Output Management, the my.cnf file created by
setupmysql.pl or configmysql.pl sets innodb_max_purge_lag to 50.
The default value of innodb_max_purge_lag parameter is zero, meaning that
there are no delays. When purge_lag exceeds innodb_max_purge_lag, each
INSERT, UPDATE and DELETE operation is delayed by
((purge_lag/innodb_max_purge_lag)*10)-5 milliseconds. The
delay is computed in the beginning of a purge batch, every ten seconds. In HP Output
Server, this option can be used to address a slowing in job throughput caused when the
rate of job submission continuously exceeds the rate at which the MySQL purge thread
can remove retained jobs that have expired. HP recommends that customers set this
option to 50. For more information about this option, see:
http://dev.mysql.com/doc/refman/4.1/en/innodb-multi-versio
ning.html
268
Appendix M

max_allowed_packet
The MySQL internal variable max_allowed_packet controls the maximum size of
its communication buffer.
To set the max_allowed_packet variable for MySQL to a value of 16MB, use the
following in the my.cnf options file.
[mysqld]
max_allowed_packet=16777216
You can specify the value in bytes or a numeric value, and the value can be given with a
suffix of K, M, or G (either uppercase or lowercase) to indicate a multiplier of 1024,
10242 or 10243. In the my.cnf option file, variable settings are given without the
leading dashes. To specify in numeric value, for example in MegaBytes (MB), add a
suffix M.
[mysqld]
max_allowed_packet=16M
In HP Output Server, this option can be used to address problems that arise when the
server needs to handle big queries like doing a pdls using set of non-indexed attributes
or while working with big BLOB columns. HP recommends that customers set this
option to 16MB. For more information about this option, see:
http://dev.mysql.com/doc/refman/4.1/en/packet-too-large.ht
ml
wait_timeout
The MySQL wait_timeout system variable defines the length of time that the
MySQL server will wait for activity from a non-interactive client before closing the
connection. The wait_timeout system variable applies only to TCP/IP and UNIX
socket file connections.
By default, the server closes the connection after 28,800 seconds (eight hours) if there is
no activity from the client. To change the default wait time, you can set the
wait_timeout variable when you start MySQL. The value should be specified in
seconds.
To change the default setting for wait_timeout, add an entry for this variable in the
Tuning Parameters section (under Server/Services) of the my.cnf file. For
example:
[mysqld]
wait_timeout = 36000
HP Output Server
269
Appendix M
270
Appendix N
Tuning MySQL for HP Output Server

The MySQL database used with HP Output Server can be tuned to improve the
performance, stability, and reliability and to prevent memory or CPU-related issues.
NOTE: On tuning the MySQL database, if you change the value of
the -database-client-max-connections attribute
to 25 for the delivery servers (DLM, JQM and DSM), the
CM server, and the AIM server, performance improves
significantly.
The tuning of MySQL databases can be performed with or without de-fragmentation,
depending on whether or not the database is de-fragmented. Refer to, Determining if
the MySQL database is fragmented on page 273.
Prerequisites for tuning MySQL

The following are the prerequisites for tuning the MySQL database.
1.
The required ulimit parameters are set to the highest possible values as below:
data seg size (kbytes) - unlimited
max memory size (kbytes) - unlimited
open files - unlimited
HP Output Server
271
Appendix N
stack size (kbytes) - unlimited

cpu time (seconds) - unlimited
virtual memory (kbytes) - unlimited
NOTE: Set the ulimit parameters to the highest possible value based
on the load characteristics.
A few operating system will not accept unlimited as valid value, set the tunable
parameters to the highest possible value.
NOTE: See the Chapter 2, Installing HP Output Server on page 33
for the formula on data file sizing.
2.
The system memory should be sufficient before starting the tuning process, or else
the MySQL server does not restart.
3.
Tuning is highly dependent on usage pattern and landscape. The

innodb_buffer_pool_size is a major component of MySQL that gives
higher performance benefits. If MySQL grows to a higher value, increase the value
of this variable.
4.
The tunable values are based on innodb_buffer_pool_size. The actual

memory usage by MySQL will be equal to the sum of
innodb_buffer_pool_size +
innodb_additional_mem_pool_size + read_buffer +
read_rnd_buffer + innodb_log_buffer + query_cache_size +
key_buffer.
Calculating the recommend size of the ibdata file

To arrive at the recommended size of the ibdata file, calculate the approximate space
in bytes with the help of the following formula:
=(1600*s+21*q+55*p+58*l+83*j+20*c+12*u+30)*100*1.30
where:
s = number of servers (DLM + JQM + DSM) configured on HP Output Server
q = number of queues configured in JQM servers
p = number of physical destinations configured in DSM servers
l = number of logical destinations configured in JQM servers
j = number of jobs stored in the database at any given point of time
c = number of Event manager clients (SAPCON, OMSCB, EPOD, Active Event
272
Appendix N
Monitor)
u = number of users defined in the PM database or the number of users configured
in HP Output Server
1.30 = buffer of 30 percent to the calculated size
NOTE: The buffer of 30% can vary between 5% (1.05) to 30%
(1.30) based on the predicted growth of the implementation.
NOTE: If ibdata file is not set to the proper value, you may
encounter disk write performance issues, disk fragmentation
issues, and unexpected growth, which can result in database
crash leading to unrecoverable setup.
NOTE: For every SAP system logged in HP Output Server, only
sidadm user will communicate with HP Output Server.
Even if more than one user is logged in to SAP, every SAP
system counts as only one user of HP Output Server.
NOTE: The jobs stored in the database will be approximately 15% to
20% of the load on HP Output Server per day. Retained jobs
and the retention period of the jobs contribute to the number
of jobs stored in a database.
To calculate jobs in a database:
load per day = XXX jobs / day
peak load per min = (load per day /
2)/480
To calculate total jobs in a database:
(peak load per min * retention period for
successful jobs) + (2% of peak load per
min * retention period for unsuccessful
jobs)
Determining if the MySQL database is fragmented

To determine if the MySQL database is fragmented, compare the current size of the
database with the initial size the database.
HP Output Server
273
Appendix N
The initial size of the database file indicated by xxx in the

innodb_data_file_path=ibdata: xxxM: autoextend
in the my.cnf file. This parameter is compared with the current size of the ibdata
file in the $MYSQL_HOME/data directory, where MYSQL_HOME is the MySQL
installation directory.
If the actual size of the ibdata file is larger than the value set in the my.cnf file, it
indicates that the database is fragmented. In this situation, follow the steps in the section
Tuning the MySQL for HP Output Server on page 274.
If the actual size of the ibdata file is less than or equal to the value set in the my.cnf
file, it indicates that the database is not fragmented. In this situation, follow the steps in
the section Tuning the MySQL for HP Output Server on page 274, skip step 10 and
continue with step 11.
Tuning the MySQL for HP Output Server

1.
Type the following command to change directories to the location of the

tunemysql_hpos.pl installation script.
where mySQLinstallDir is the installation path for your MySQL installation.
2.
To run the tunemysql_hpos.pl script, type the following command:

On Windows:
.\perl.exe .\tunemysql_hpos.pl
On UNIX:
./perl ./tunemysql_hpos.pl
3.
274
Before continuing with the tuning, you must manually stop all HP Output
Management programs (HP Output Server, HP Output Distributor, and HP Web
Delivery) that use HP Output Server. The script prompts whether to continue with
the tuning. The default is y.
Appendix N
4.
When the default MySQL installation directory is prompted, accept the default if
the path is correct: if not, specify the correct directory. The script checks for a
MySQL installation. The script aborts with an error message if MySQL is not
installed in that directory.
NOTE: In UNIX, the default MySQL installation directory is
indicated, if MySQL is installed in the
DAZEL_HOME/var/mysql directory and the
DAZEL_HOME environment variable is set.
In Windows, the default installation directory path must be
C:\Program Files\MySQL\MySQL Server 5.0
and C:\Program Files (x86)\MySQL\MySQL
Server 5.0 for Windows x64.
5.
The tunemysql_hpos.pl script prompts for the type of tuning:

1) Tuning MySQL without de-fragmenting the database
2) Tuning MySQL after de-fragmenting the database
The default option is 1.
6.
The tunemysql_hpos.pl script prompts for the type of memory usage:

1) Tune MySQL for 256 MB memory usage.
2) Tune MySQL for 512 MB memory usage.
3) Tune MySQL for 1 GB memory usage.
4) Tune MySQL for 1.5 GB memory usage.
The default option is 1.
NOTE: Most MySQL installations for HP Output Server have to be
tuned for 256MB memory usage for MySQL buffer pool. If
the MySQL memory usage grows beyond 400MB, then
different set of higher buffer pool size is used to tune
MySQL. Refer to, Tuning MySQL parameters for 256 MB,
512 MB, 1 GB and 1.5 GB memory usage for buffer pool
on page 280.
NOTE: Refer to Appendix O, Using HP Output Server data for
determining the type of memory usage on page 281.
HP Output Server
275
Appendix N
7.
If Tune MySQL without de-fragmenting of the database is selected, skip step 10

and continue with Step 11.
8.
If Tune MySQL after de-fragmenting of the database is selected, then the following
prompts are displayed:
CAUTION: The MySQL database is backed up and restored. All
applications using MySQL database must be stopped
before proceeding with tuning.
1) Specify a temporary directory path or accept the default path, if indicated, for
data migration.
The script indicates /tmp as the default directory if it has enough disk space
available. If /tmp does not has enough disk space, no default option is provided
and you must specify an alternate directory path.
NOTE: The default temporary directory path for UNIX is /tmp and
for Windows it is C:\WINDOWS\Temp.
NOTE: The directory path selected must not be in the current
MySQL installation directory.
2) Enter the size of the ibdata file. By default the existing size of the ibdata file is
displayed.
The minimum value of ibdata file must be 100 MB and the maximum value
should be set lower than the available disk space in the MySQL installation
directory.
3) Enter the extent size. By default the value of
innodb_autoextend_increment parameter is half of that of the ibdata
file.
276
Appendix N
9.
Enter the value of innodb_sync_spin_loops parameter. The default value is

40.
NOTE: The value of the innodb_sync_spin_loops
parameter is calculated using the formulae:
innodb_sync_spin_loops= 10 X number of
CPUs, where X is the multiplication operation.
The minimum value for innodb_sync_spin_loops is
20, even for a single CPU system.
10. Enter the value of innodb_thread_concurrency. The default value is 12.

NOTE: The value of the innodb_thread_concurrency
parameter is calculated using the formulae:
innodb_thread_concurrency = 2 X(number of
CPUs+ number of disks), where X is the multiplication
operation and + is the addition operation. If you have a
single CPU and a single hard disk system, change the
my.cnf manually after running the script and set the
innodb_thread_concurrency to 4 (this is the
MySQL default value for this variable).
NOTE: Execute the following calculations to identify the number of
disks, if RAIDs are used.
For raid 0: number of disks = total disks in raid array
For raid 0+1: number of disks = total disks in raid array / 2
For raid 5: number of disks = total disks in raid array / 3
If SAN or NAS is used then the available I/O per second is in
the range of 5 to 10 times that of a single disk (2500 IOPS to
3500 IOPS) In this situation, number of disk is assumed to
be around 5.
11. The tuning script displays your tuning settings and prompts you to accept the
settings (y), change the settings (n), or quit the program (q). Review the tuning
settings and do one of the following:
-
If the settings are correct, type y.
If any setting is not correct, type n.
The tuning script returns to the beginning of the program and displays your current
selection for each prompt. When prompted, change any setting that is incorrect.
HP Output Server
277
Appendix N
The tuning script finishes tuning and configuring the MySQL server. If the tuning was
successful, the tuning script displays the following messages:
MySQL server successfully configured and tuned using the
new settings.
The tuning and configuration log for the tunemysql_hpos.pl script is located in
the mySQLinstallDir/tunemysql.log (where mySQLinstallDir is the
installation directory for MySQL).
NOTE: If tunemysql_hpos.pl is not completed successfully,
the tunemysql.log will not be created. Instead, the
tunemysql-pid.log (where pid is the process ID) file
is created in /tmp. The tuning script can be run again to
tune MySQL. When tuning with de-fragmentation of the
database, a back up created by the tuning script in the
temporary directory has to be manually removed.
The original my.cnf is saved as my.cnf.old in the
$MYSQL_HOME directory.
The tuning script can be run again to tune MySQL. When tuning with de-fragmentation
of the database, a back up created by the tuning script in the temporary directory has to
be manually removed.
Tasks performed by the tunemysql_hpos.pl script

The tunemysql_hpos.pl script performs the following tasks for tuning without
de-fragmentation:
1.
Stops the MySQL server.
2.
Makes a backup of the my.cnf file and name the file as my.cnf.old in the
3.
Updates the existing my.cnf file with values of the tuning parameters calculated
based on the memory usage.
4.
Starts the MySQL server.

NOTE: If the system does not have enough memory, MySQL server
does not restart. Run the tunemysql_hpos.pl script to
allocate less memory.
278
Appendix N
Advantages of tuning without de-fragmentation of databases

The advantages of tuning a MySQL database without de-fragmentation are as follows:
Eliminates the risk involved in re-creating a database due to fragmented disk

failures.
Helps tune memory pools and increases query performance.
There are no known disadvantages in tuning a MySQL database without

de-fragmentation of databases.
Tasks performed by the tunemysql_hpos.pl script with

de-fragmentation of databases
The tunemysql_hpos.pl script performs the following tasks for tuning with
de-fragmentation:
1.
Makes a backup of the database in the temporary directory.
2.
3.
Makes a backup of the data directory in the temporary directory.
4.
Starts the MySQL server
5.
Deletes all the databases except the internal database.
6.
7.
Removes the ibdata and iblog files.
8.
Makes a copy of the my.cnf file and name the file as my.cnf.old in the
9.
Updates the existing my.cnf file with values of the tuning parameters calculated
based on the memory usage and the type of tuning.
10. Starts the MySQL server.

11. Reloads the database from the backup file created in the Step1.
Advantages and disadvantages of tuning with de-fragmentation of

databases
The advantages and disadvantages of tuning MySQL database with de-fragmentation of
databases are as follows:
Advantages
HP Output Server
Increases reads per second.
279
Appendix N
Decreases the response time.
Configures indexes.
Increases the query performance.
Cleans temporary data in the datafiles and undo segments.
Disadvantages
Re-creates the database.
Corrupts the database if the re-creation of the database fails.
Tuning MySQL parameters for 256 MB, 512 MB, 1 GB and 1.5 GB
memory usage for buffer pool
Parameter
256MB
512MB
1GB
1.5GB
table_cache
250
350
550
650
innodb_buffer_pool_size
256M
512M
1024M
1536M
innodb_additional_mem_pool_size
20M
50M
100M
100M
read_buffer_size
2M
5M
5M
5M
read_rnd_buffer_size
8M
10M
10M
10M
innodb_log_buffer_size
30M
60M
100M
100M
query_cache_size
800K
1600K
1600K
1600K
key_buffer
30M
60M
100M
150M
innodb_flush_method (only UNIX)
O_DIRECT
O_DIRECT
O_DIRECT
O_DIRECT
innodb_log_file_size
30M
60M
100M
100M
NOTE: The information on tuning individual parameters is

explained in detail in Appendix P, MySQL tunable
parameters on page 283.
280
Appendix O
Using HP Output Server data for

determining the type of memory usage
The table below exhibits a rough estimate of parameters on which set of tuning is
performed.
HP Output Server
Metrics
256MB
512MB
1GB
1.5GB
Number of
servers
30 to 50
50 to 100
100 to150
150 to 200
Number of
destinations
1000
5000
10000
15000 and
above
Job load per

day
25000 to
30000
30000 to
50000
50000 to
100000
100000 and
above
Aim enabled
Not
applicable
Yes
Yes
Yes
Percentage
destinations
are multi
logical single
queue multi
physical
configuration
up to 5%
up to 10%
up to 25%
greater than
25%
Job retention
period
less than 15
minutes
less than 30
minutes
less than 30
minutes
less than 30
minutes
281
Appendix O
282
Using HP Output Server data for determining the type of memory usage
Metrics
256MB
512MB
1GB
1.5GB
Possibility of
using HP Web
Delivery
along with HP
Output Server
Not applicable
Yes
Yes
Yes
Possibility of
extensive use
of job tracker
Not applicable
Yes
Yes
Yes
Possibility of
concurrent
pdls
Not applicable
Yes
Yes
Yes
System
memory
requirement
up to 2 GB
up to 4GB
up to 6GB
greater than
6GB
System CPU
requirement
2CPU
4CPU6
6 to 8CPU
more than 8
CPU
Possibility of
RAID 0
3 disks
6 disks
8 to 10 disks
or SAN
10 to 15 disks
or SAN
Appendix P
MySQL tunable parameters

The following section describes the MySQL tunable parameters.
Parameters that affect memory
This is the size of the memory volume used by InnoDB to store the index and related
data in memory. It should be large enough to execute all operations on InnoDB tables.
This parameter affects MySQL performance to a greater extent. You can tune the value
to the next multiple of 64 if the MySQL database is growing.
innodb_log_buffer_size
This is the size of the buffer that InnoDB uses to write to log files on the disk. Values
typically range from 1 MB to half the combined size of log files. A large log buffer
allows large transactions to run without the need to write the log to disk until the
transaction is complete. Therefore, a value of 15 to 30 percent of buffer pool size is
required. If the innodb_buffer_pool_size is more than 1 GB, the value is fixed
between 150 to 300 MB.
innodb_additional_mem_pool_size
This parameter is used to hold the internal structure and the hash table. It is
approximately 5 to 30 percent of the innodb_buffer_pool_size based on the
number of HP Output Server servers configured. If show innodb status indicates
higher values for hash merges and the hash index, then the parameter must be tuned. If
there is a growth in the memory, increase the value in steps of 10 MB.
HP Output Server
read_buffer_size
283
Appendix P
This parameter helps to load huge amounts of data from the disk while executing
operations such as pdq and pdls. This parameter helps in table scans. Each sequential
scan performed allocates a read buffer that increases the memory size by 5 to 10 MB
utilized per connection thread. The value is maintained usually in the range of 5 to 10
MB. If the innodb_buffer_pool size is greater than 1 GB, the value is set to 10
MB.
read_rnd_buffer_size
This parameter allocates a random-read buffer to avoid disk seeks when reading rows in
an arbitrary sequence. This parameter helps in pdls queries. During query, data is
selected randomly and not through sequential queries. Increase the value by 2 to 5M
size. The amount of memory allocated is utilized per connection thread. If the
innodb_buffer_pool size is greater than 1 GB, maintain this value around 5M.
table_cache
This parameter is related to caching of tables for faster access as HP Output Server uses
different databases to store tables. The frequently accessed table structures should be
stored in memory. It should be determined if the operating system can handle the
number of open file descriptors indicated by the table_cache setting. If
table_cache is set to a higher value, the system might run out of file descriptors,
refuse connections, fail to perform queries, and become unreliable. Ideally, the ulimit
value for the MySQL user should not exceed 8096.
Parameters that affect CPU
innodb_sync_spin_loops
This parameter balances the CPU time wasted while running spin locks with
unnecessary context switches. If the spin lock setting is high, the CPU time wasted will
increase. Alternatively, if the spin lock setting is low, it results in unnecessary context
switches. This parameter also represents the number of times a thread waits for an
InnoDB mutual exclusion to be freed before the thread is suspended.
innodb_thread_concurrency
This parameter increases the InnoDB kernel execution threads, which use the CPU
efficiently. Currently, InnoDB maintains the number of operating system threads
concurrently inside InnoDB to be less than or equal to the limit given by this variable.
Once the number of threads reaches this limit, additional threads are placed into a wait
state within a FIFO queue for execution. Threads waiting for locks are not counted in
the number of concurrently executing threads.
In the version of MySQL currently used, a value of 20 or higher is interpreted as infinite
concurrency. The default value for this variable is 8.
284
Appendix P
NOTE: Execute the following equations to calculate the values for

these parameters,
innodb_sync_spin_loops= 10 x
Number_of_CPUs
innodb_thread_concurrency=2 x
(Number_of_CPUs +
Number_of_disks_in_use_for_MySQL)
where x indicates the multiplication operation.
NOTE: Execute the following calculations to identify the number of
disks, if RAIDs are used.
For raid 0: number of disks = total disks in raid array
For raid 0+1: number of disks = total disks in raid array / 2
For raid 5: number of disks = total disks in raid array / 3
If SAN or NAS is used, then the available I/O per second is in the range of 5 to 10 times
of a single disk (2500 IOPS to 3500 IOPS). As a result, the number of disks is assumed
to be around 5.
Parameters that affect disk
innodb_data_file_path ibdata
This parameter specifies the value in the ibdata file. This is a single table space where
all the server's databases and indexes are present. The size is also dependent on the
retention and expirations periods of HP Output Server. The value is maintained to be
sufficiently high to accommodate all the data of HP Output Server. A recommendation
on the values is given at the end of document for reference.
innodb_autoextend_increment
This parameter specifies the amount of disk space to be increased in the current table
space (ibdata file). By default, the amount of disk space is increased in increments of
8 MB. This value is maintained in the range of 25 to 50 percent of the ibdata file size.
innodb_log_file_size
This parameter specifies the online log file size. These log files are binary and used by
MySQL for transaction journaling. The value is maintained to be around 10 to 30
percent of the ibdata file size.
HP Output Server
285
Appendix P
Miscellaneous parameters improving performance
innodb_flush_logs_at_trx_commit
This is a mechanism to direct MySQL when to push the data to disk. By default, it is set
to 1. If you wish to take the risk of loosing 2 minutes of data in case of system crash or
sudden power failure, you could set it to 0. If 30 seconds data lose is acceptable, set the
value of this parameter to 2.
innodb_flush_method
This parameter defines how to flush or push the data to disk. By default, the data will be
pushed to file system cache. In order to make the insert statements faster, this behavior
is forcefully changed to write to disk directly by setting O_DIRECT as the value for this
parameter.
innodb_file_io_threads
This parameter will increase the I/O threads of MySQL. If MySQL is not responding
then increase the value of this in steps of 2. Default value for this variable is 4.
Calculating tunable parameters

The following procedure is used to calculate the values of the tunable parameters for
customized memory values. It is used to allocate memory to MySQL other than the set
values.
NOTE: The decision on the values for the setup is based on the
ibdata file size.
Memory pool parameters
286
innodb_buffer_pool_size = 1.25 times the size of ibdata file size
innodb_additional_mem_pool_size = 5% of
if the innodb_buffer_pool_size is less than 512 MB else set to 20MB
read_buffer_size = 2 MB if innodb_buffer_pool_size is less than

512MB else set to 5MB
read_rnd_buffer_size = 8MB if Innodb_buffer_pool_size is less

than 512 MB else set to10 MB
key_buffer=15% of innodb_buffer_pool_size
table_cache=5 x number_of_HPOS_servers
Appendix P
Online Redo log parameters

innodb_log_buffer_size = 10% of Innodb_buffer_pool_size or
equal to innodb_log_file_size which ever is higher
Disk space parameters
innodb_data_file_path = ibdata1:<value obtained at by

formula>M:autoextend
innodb_autoextend_increment = 25% to 50% of

innodb_data_file_size
innodb_log_file_size = 10% of innodb_data_file_size
CPU related parameters
innodb_sync_spin_loops= 10 x Number_of_CPU
innodb_thread_concurrency = 2 x (number_of_CPU +
number_of_disks_in_use_for_MySQL)
Optional tuning parameters

innodb_flush_method = O_DIRECT. This changes the mechanism MySQL
uses to write to the disk. This improves insert query performance.
innodb_flush_logs_at_trx_commit=2 OR 0, determines how log buffer
is written to the disk. If the value is 2, it indicates that data is flushed on very
commit, but there was no disk flush. The default value is 1 and 0 means that there
was no data and disk flush
innodb_file_io_threads=6, this value determines how many I/O threads
will be spawned for disk I/O operations.
HP Output Server
287
Appendix P
288
Appendix Q
Using patch.pl in non-interactive mode

You can use patch.pl in non-interactive mode at the command line to install or
back-out a Service Pack installation on a UNIX host. This appendix describes the syntax
for using patch.pl in non-interactive mode.
Syntax
This section describes the syntax for using patch.pl in non-interactive mode for the
following tasks:
Installing a Service Pack
Backing out of a Service Pack
Using help
For a complete list of arguments, see Arguments on page 291.

NOTE: A sample patch.ini file is available in the
installBinDir/examples directory.
HP Output Server
289
Appendix Q
Syntax
Installing a Service Pack

To install a Service Pack with HP Output Server in non-interactive mode, use the
following syntax:
perl patch.pl
-c <Absolute path of patch.ini file>

that is, if you have installed HP Output Server binaries and
instance at different locations, you must patch the HP Output
Server binaries and instance separately and to the same patch
level.
NOTE: If you are patching only HP Output Server binaries, you
must log in as the owner of the installed binaries or as the
root user. Similarly, if you are patching only the HP Output
Server instance, you must log in as the owner of the installed
instance or as the root user.
NOTE: If there are any applicable patches, the patch utility will
automatically update MySQL provided with HP Output
Server while patching HP Output Server binaries or HP
Output Server standard installation.
The following table describes the parameters in the patch.ini file for running the
patch.pl in non-interactive mode.
Parameters
Description
HPOM_OPERATION
Set this to INSTALL if you want to install HP Output Management

product components.
Set this to UNINSTALL if you want to remove HP Output Management
product components.
The default value is INSTALL.
HPOM_INSTALL_PATH
Set this to the path where HP Output Server binaries, instance, or

standard installation is installed depending on the type of your
installation.
Set this to STARTED, if you want HP Output Server to start the HP

Output Server servers after the installation.. else enter STOPPED. The
default value is STARTED.
290
Appendix Q

Arguments
Parameters
Description
HPOM_FIX_FILE
Set this to the location of fix file.
Backing out of a Service Pack

To back out of a Service Pack with HP Output Server in non-interactive mode, use the
following syntax:
perl patch.pl
-c <Absolute path of patch.ini file>
The following table describes the parameters in the patch.ini file for running the
patch.pl in non-interactive mode.
Parameters
Description
HPOM_OPERATION
Set this to BACKOUT if you want to back out HP Output Management

product components.
HPOM_INSTALL_PATH
Set this to the path where HP Output Server binaries, instance, or

standard installation is installed depending on the type of your
installation.
Set this to STARTED, if you want HP Output Server to start the HP

Output Server servers after the installation. else enter STOPPED. The
default value is STARTED.
HPOM_FIX_FILE
Set this to the location of fix file.
Using help
To view information about using patch.pl, enter the following:
patch.pl -h |-?
Arguments
The following table describes the arguments for running patch.pl in non-interactive
mode.
HP Output Server
Argument
Description
-c
This option accepts patch.ini as an argument.
291
Appendix Q
Arguments
292
Appendix R
Installing HP Output Server Manager

This appendix provides instructions for installing HP Output Server Manager.
For installing HP Output Server Manager, log in as administrator or a user with
administrator privileges.
Installing HP Output Server Manager in interactive

mode on Windows hosts
To install HP Output Server Manager in interactive mode on a Windows host, follow
these steps:
1.
2.
Go to the directory where you have extracted the .zip file for HP Output Server.
3.
Open the hposm/win folder in the directory, and then double-click setup.exe.
The Welcome dialog box appears.
4.
Click Next.
5.
The License Agreement dialog box appears. Accept the terms in the license
agreement.
6.
Click Next.
The Destination Folder dialog box appears.
7.
HP Output Server
Do one of the following:
293
Appendix R
Installing HP Output Server Manager in non-interactive mode on Windows hosts
Click Next to accept the default location. The default location is

C:\Program Files\Hewlett-Packard\HP Output Manager
8.
Click Change to change the location and click OK to continue.
Click Next.
The Ready to Install the Program screen appears. Select the Create desktop
shortcut checkbox to create a desktop shortcut.
9.
Click Install.
The installation continues and launches the Installing progress screen. The
Installation Wizard Completed dialog box appears. If the installation is
successful, the following message appears:
The installation Wizard has successfully installed HP
Output Server Manager.
10. Click Finish to exit.
Installing HP Output Server Manager in

non-interactive mode on Windows hosts
To install HP Output Server Manager in non-interactive mode on a Windows host, follow these steps:
1.
2.
3.
Open the hposm/win folder in the directory, and then double-click the
setup.bat file.
On Windows Vista, install HP Output Server Manager by running the command
prompt in administrator mode (elevated mode) and execute the setup.bat file.
4.
To customize the installation, right-click setup.bat file and select Edit.
5.
Use the following commands with setup.exe in the setup.bat file:

-
To change the directory in which you want to install HP Output Server

Manager
INSTALLDIR=C:\Destination
294
To enable logging for a silent installation
Appendix R Installing HP Output Server Manager

Uninstalling HP Output Server Manager
/l* C:\InstallLog.txt
For example, after editing the commands as given above, the final command will
be: setup.exe /s /v"/qn INSTALLDIR=C:\Destination"
Uninstalling HP Output Server Manager

For uninstalling HP Output Server Manager, log in as administrator or a user with
administrator privileges and use one of the following methods:
From the Control Panel:

1.
Select Add/Remove Programs.
2.
Select HP Output Server Manager from the list of installed programs.
3.
Click Remove.
4.
When prompted to remove HP Output Server Manager, click Yes. If prompted to

restart your computer, click Yes to restart the computer and complete the removal.
On Microsoft Windows Vista:

1.
Select Programs and Features.
2.
Select HP Output Server Manager from the list of installed programs.
3.
Right-click and select Uninstall.
4.
When prompted to uninstall HP Output Server Manager click Yes. If prompted to

restart your computer, click Yes to restart the computer and complete the removal.
Execute setup.exe:
On Vista, uninstall HP Output Server Manager by running the setup.exe in
administrator mode (elevated mode).
The following options in the HP Output Server Manager Setup Wizard page are
displayed:
-
Repair
Remove
Select Remove to uninstall HP Output Server Manager.
From the Start Menu:

1.
HP Output Server
Go to All Programs>HP Output Manager>HP Output Server Manager.
295
Appendix R
Upgrading HP Output Server Manager in interactive mode on Windows hosts
2.
Select Uninstall HP Output Server Manager. When prompted for confirmation,

click Yes.
Upgrading HP Output Server Manager in interactive

mode on Windows hosts
To upgrade HP Output Server Manager in interactive mode on a Windows host, follow
these steps:
1.
For a normal user, right-click the setup.exe file and select the Run as
Administrator option.
2.
For an administrator or user with administrator privileges, launch setup.exe.

The setup prompts for upgrading the current installation.
3.
Click Yes.
To continue the upgrade process, follow steps 3 through 9 in Installing HP Output
Server Manager in interactive mode on Windows hosts on page 293.
296
Appendix S
Installing HP Job Manager for Output

Server Software
This appendix provides instructions for installing HP Job Manager for Output Server
Software.
Installing HP Job Manager for Output Server

Software in interactive mode on Windows hosts
To install HP Job Manager for Output Server Software in interactive mode on a
Windows host, follow these steps:
HP Output Server
1.
2.
3.
Open the hpjmfhpos/win folder in the directory, and then double-click

setup.exe.
297
Appendix S
Installing HP Job Manager for Output Server Software
Installing HP Job Manager for Output Server Software in interactive mode on Windows hosts

NOTE: To change the user preferences, application settings, and
window settings of the HP Job Manager for Output Server
Software user interface, you must edit the config.xml
file located in the /win folder before installation.
Upon successful installation, this configuration file, which is
in .xml format, is stored at the default location
C:\Program Files\Hewlett-Packard\HP
Output Manager\HP Job Manager for Output
Server Software\config.For more details, refer to
Table O-4 on page 301.
4.
Click Next.
The License Agreement dialog box appears. Accept the terms in the license
agreement.
5.
Click Next.
The Destination Folder dialog box appears.
6.
Do one of the following:

-
Click Next to accept the default location. The default location is

C:\Program Files\Hewlett-Packard\HP Output Manager
7.
Click Change to change the location and click OK to continue.
Click Next.
The Ready to Install the Program screen appears. Select the Create desktop
shortcut checkbox to create a desktop shortcut.
8.
Click Install.
The installation continues and launches the Installing progress screen. The
Installation Wizard Completed dialog box appears. If the installation is
successful, the following message appears:
The installation Wizard has successfully installed HP
Job Manager for Output Server Software.
9.
298
Click Finish to exit.
Appendix S
Installing HP Job Manager for Output Server Software in non-interactive mode on Windows hosts
Installing HP Job Manager for Output Server

Software in non-interactive mode on Windows
hosts
To install HP Job Manager for Output Server Software in non-interactive mode on a
1.
2.
Close all running applications if any.

NOTE: To change the user preferences, application settings, and
window settings of the HP Job Manager for Output Server
Software user interface, you must edit the config.xml
file located in the /win folder before installation.
Upon successful installation, this configuration file, which is
in .xml format, is stored at the default location
C:\Program Files\Hewlett-Packard\HP
Output Manager\HP Job Manager for Output
Server Software\config.For more details, refer to
Table O-4 on page 301.
3.
4.
Open the hpjmfhpos/win folder in the directory, and then run the setup.bat
file.
On Windows Vista, run the command prompt in administrator mode (elevated
mode) and execute the setup.bat file.
5.
To customize the installation, right-click setup.bat file and select Edit.
6.
Use the following commands with setup.exe in the setup.bat file:

-
To change the directory in which you want to install Job Manager

INSTALLDIR=C:\Destination
To enable logging for a silent installation

/l* C:\InstallLog.txt
HP Output Server
299
Appendix S
For example, after editing the commands as given above, the final command will
be: setup.exe /s /v"/qn INSTALLDIR=C:\Destination"
The config.xml file consists of the following options:
300
HP Web Services for Output Server address
All the preferences options specified in the user interface
The details of HP Job Manager for Output Server Software window as displayed
last
Appendix S
The following table describes the XML tags in the configuration file.
Table O-4. Configuration file details
HP Output Server
XML tag
Description
detail-viewvisible
Specifies if job details are displayed. The value can be either

true or false.
hpos-wsdl-url
Specifies the Web Service Definition Language (WSDL) path

used by HP Job Manager for Output Server Software to
communicate with HP Web Services for Output Server.
job-query-options
Specifies display job options such as all_jobs,

pending_jobs, and failed_jobs.
logging-option
Specifies about the logging option. The values can be

log_all , log_disable, log_info, log_warning,
log_error, and log_critical.
main-windowheight
Specifies height (in pixels) of the HP Job Manager for Output

Server Software window.
main-window-width
Indicates width (in pixels) of the HP Job Manager for Output

Server Software window.
monitored-printer
-name
Indicates if HP Job Manager for Output Server Software gets the

print notification from the printer specified in the printer spooler.
run-on-start-up
Indicates if HP Job Manager for Output Server Software is

launched automatically during system startup. The value can be
either true or false.
show-app-onlaunch
Indicates if HP Job Manager for Output Server Software is

launched with the main user interface. The value can be either
true or false.
smart-pollingenabled
Specifies if smart polling is used for jobs submitted through HP

Universal Print Driver client or resubmitted through HP Job
Manager for Output Server Software. The value can be either
true or false.
smart-pollinginitial-interval
Specifies the wait time for the next poll. This time can be
doubled up to 60 seconds and further incremented by 1 minute.
smart-polling-max
-time
Indicates the time (in seconds) after which HP Job Manager for
Output Server Software stops smart polling.
smart-pollingrandom-interval
Specifies the random polling time (in minutes) for jobs.
301
Appendix S
Uninstalling HP Job Manager for Output Server Software
Table O-4. Configuration file details

XML tag
Description
tray-icon-changeoption
Specifies the tray icon color change options. When a job fails,
this option is displayed.
tray-notification
-option
Specifies the notification options.
enable-attributefriendly-names
Indicates if the HP Output Server attribute names cane be

customized to have a friendly name. The value can be either
true or false.
NOTE: If you want to resubmit a job to the same file destination,

you must set the -file-overwrite attribute value to
true. The default value of -file-overwrite attribute
is false.
For more information about the -file-overwrite
attribute, see the System Administrators Attribute Reference
for HP Output Server 4.1.
Uninstalling HP Job Manager for Output Server

Software
To uninstall HP Job Manager for Output Server Software from your system, use one of
the following methods:
From the Control Panel:
302
1.
Select Add/Remove Programs.
2.
Select HP Job Manager for Output Server Software from the list of installed
programs.
3.
Click Remove.
4.
When prompted to remove HP Job Manager for Output Server Software, click Yes.
If prompted to restart your computer, click Yes to restart the computer and complete
the removal.
Appendix S
Upgrading HP Job Manager for Output Server Software in interactive mode on Windows hosts
On Microsoft Windows Vista:

1.
Select Programs and Features.
2.
Select HP Job Manager for Output Server Software from the list of installed
programs.
3.
Right-click and select Uninstall.
4.
When prompted to uninstall HP Job Manager for Output Server Software click Yes.
If prompted to restart your computer, click Yes to restart the computer and complete
the removal.
Execute setup.exe:
On Vista, uninstall HP Job Manager for Output Server Software by running the
setup.exe in administrator mode (elevated mode).
The following options in the HP Job Manager for Output Server Software Setup
Wizard page are displayed:
-
Repair
Remove
Select Remove to uninstall HP Job Manager for Output Server Software.
From the Start Menu:

1.
Go to All Programs>HP Output Manager>HP Job Manager for Output Server

Software.
2.
Use the following options:

-
For a normal user, right-click Uninstall HP Job Manager for Output Server
Software and select Run as administrator and provide administrator details.
When prompted for confirmation, click Yes.
For an Administrator or user with Administrator privileges, select Uninstall

HP Job Manager for Output Server Software. When prompted for
confirmation, click Yes.
Upgrading HP Job Manager for Output Server

Software in interactive mode on Windows hosts
To upgrade HP Job Manager for Output Server Software in interactive mode on a
HP Output Server
303
Appendix S
Upgrading HP Job Manager for Output Server Software in interactive mode on Windows hosts
1.
For a normal user, right-click the setup.exe file and select the Run as
Administrator option.
2.
For an administrator or user with administrator privileges, launch setup.exe.

The setup prompts for upgrading the current installation.
3.
Click Yes.
-
304
To continue the upgrade process, follow steps 4 through 9 in Installing HP Job

Manager for Output Server Software in interactive mode on Windows hosts
on page 297.
Appendix T
Setting MySQL startup time

This section describes the procedure to set the MySQL startup time.
The MySQL server startup time settings are improper if the following conditions occur:
MySQL server status is displayed as stopped when the server status command of
HP Output Server is used.
MySQL server status is displayed as running when the operating system commands
such as ps, top, topas, and prstat are used.
Setting the startup time depends on the following:

1.
The startup time required for MySQL server depends on hardware resources and
configuration. If hardware resources are low, the server takes a longer time to start
up.
2.
Set the startup time appropriately using the

-server-startup-completion-time attribute to ensure that the MySQL
server starts up properly. If the startup time is insufficient, other servers will fail to
start.
For example:
Execute the following command before starting any server:
start_server -t mysql
-x"-server-startup-completion-time 100"
To set the value permanently, use the following command:
config_server -u -x"--server-startup-completion-time
100" -t mysql
HP Output Server
305
Appendix T
306
Setting MySQL startup time
Appendix U
Tuning the JBoss application server

This appendix provides instructions for setting the startup time and tuning the JBoss
application server. JBoss functions effectively in general scenario. In case of large
volumes of traffic, tuning JBoss is required for optimal performance.
Setting startup time for the JBoss application server

The JBoss server startup time settings are improper if the following conditions occur:
The JBoss server status is displayed as stopped when the server status command of
HP Output Server is used.
The JBoss server status is displayed as running when the operating system
commands such as ps, top, topas, and prstat are used.
Setting the startup time, depends on the following:

1.
The startup time required for the JBoss server depends on hardware resources and
configuration. If hardware resources are low, the server takes a longer time to start
up.
2.
Set the startup time appropriately using the

-server-startup-completion-time attribute to ensure that the JBoss
server starts up properly. If the startup time is insufficient, other servers will fail to
start.
For example:
Execute the following command before starting any server:
start_server -t jboss
-x"-server-startup-completion-time 180"
HP Output Server
307
Appendix U
To set the value permanently, use the following command:

config_server -u -x"--server-startup-completion-time
180" -t jboss
Accessing JBoss Web Console

1.
To access JBoss Web Console, use the link

http://hostname:portnumber/web-console/.
where,
The default portnumber is 9000. You can also use the first port in the port range
for the JBoss server.
2.
Enable JBoss Web Console for HP Output Server by uncommenting the following
command line in the
$DAZEL_HOME/share/jboss/server/default/conf/props/
web-console-users.properties file:
#admin=admin
The default user name and password is set to admin. You can set a different
username and password using the following syntax:
username=password
NOTE: You need not restart the JBoss server for the changes to take
effect.
Enabling JMX Console

You must enable JMX Console to modify the parameters for JBoss tuning. To enable
JMX Console for HP Output Server, uncomment the following command line in the
$DAZEL_HOME/share/jboss/server/default/conf/props/
jmx-console-users.properties file:
#admin=admin
The default user name and password is set to admin. You can set a different username
and password using the following syntax:
308
Appendix U
username=password
NOTE: You need not restart the JBoss server for the changes to take
effect.
Procedure for tuning the JBoss application server

Tuning the JBoss application server involves tuning the environment on which JBoss is
running, which includes the following:
JVM Tuning
JBoss Tuning
JVM Tuning
Java Virtual Machine (JVM) enables better performance in production servers with
proper configuration of JVM parameters, particularly those related to memory usage
and garbage collection.
JVM allocates Java objects in an area of memory called the Java heap. A Java
application will place the objects on the heap. When the application completes its task
with the object, it removes the object, along with all its references, and the object
becomes unreachable. When an object becomes unreachable, it is deemed as available
to the garbage collector and the garbage collector frees up memory by removing any
unreachable objects. The garbage collector typically runs when memory resources are
low.
The following are the JVM heap sizing arguments that can be specified:
-Xms<size> Sets the minimum heap size
-Xmx<size> Sets the maximum heap size
To specify the JVM heap sizing arguments, follow these steps:
Windows:
Open the run.bat file in the $DAZEL_HOME/share/jboss/bin folder. In
this file, search set JAVA_OPTS and update the values of the required JVM
heap sizing arguments.
HP Output Server
309
Appendix U
UNIX:
Open the run.conf file in the $DAZEL_HOME/share/jboss/bin folder. In
this file, search set JAVA_OPTS and update the values of the required JVM
heap sizing arguments.
NOTE: For both Windows and UNIX, you must restart the JBoss
server after setting the JVM heap sizing arguments.
NOTE: It is recommended that you set the minimum and maximum
size of the Java heap to the same value. This reduces the time
it takes by JVM to determine the adjustment to be made for
the minimum and maximum size after garbage collection.
JBoss Tuning
JBoss tuning includes the following:
Checking the JBoss thread pool.
Checking the embedded Web container.
Checking the JBoss thread pool

The JBoss thread pool is defined in
$DAZEL_HOME/share/jboss/server/default/conf/jboss-service
.xml
<mbean code="org.jboss.util.threadpool.BasicThreadPool"
name="jboss.system:service=ThreadPool">
<attribute name="Name">JBoss System
Threads</attribute>
<attribute name="ThreadGroupName">System
Threads</attribute>
<attribute name="KeepAliveTime">60000</attribute>
<attribute name="MaximumPoolSize">10</attribute>
<attribute name="MaximumQueueSize">1000</attribute>
<attribute name="BlockingMode">run</attribute>
</mbean>
For most applications, the default values are sufficient. In scenarios where the
application processes several requests to JBoss, monitoring the thread pool size is
essential.
310
Appendix U
To monitor the thread pool size, follow these steps:

i.
Open the JBoss Web Console.
ii.
On the left pane, expand System, and then expand JMX Mbeans.
NOTE: You must enable JMX Console to modify the parameters.
For more details on enabling JMX Console, see Enabling
JMX Console on page 308.
iii. Expand jboss.system under JMX Mbeans, and then click

jboss.system:service=ThreadPool.
iv. Start a monitor on the QueueSize parameter under
jboss.system:service=ThreadPool.
v.
If the value of the QueueSize attribute reaches the value of the

MaximumPoolSize attribute, set a higher value for the
MaximumPoolSize attribute.
Checking the embedded Web container

JBoss supports connectors for http, https, and ajp. The configuration file is
server.xml and it is deployed in the root of JBoss Web container.
(For JBoss 4.2.0 it is:
"JBOSS_HOME\server\default\deploy\jboss-web.deployer")
<Connector port="9000" address="${jboss.bind.address}"
maxThreads="250" maxHttpHeaderSize="8192"
emptySessionPath="true" protocol="HTTP/1.1"
enableLookups="false" redirectPort="8443"
acceptCount="100"
connectionTimeout="20000"
disableUploadTimeout="true" />
The underlying HTTP connector of JBoss must be fine tuned for production settings.
Consider the following important parameters:
1.
maxThreads-This indicates the maximum number of threads to be allocated for

handling client HTTP requests. The number of threads corresponds to the
concurrent users accessing the application. Depending on the configuration of the
system, there is a physical limit beyond which you will need to do clustering.
To determine if it is necessary to raise the maxThreads number, follow these
steps:
i.
HP Output Server
Open the JBoss Web Console.
311
Appendix U
ii.
On the left pane, expand System, and then expand JMX Mbeans.
NOTE: You must enable JMX Console to modify the parameters.
For more details on enabling JMX Console, see Enabling
JMX Console on page 308.
iii. Expand jboss.web under JMX Mbeans, and then click

jboss.web:type=ThreadPool,name=http-0.0.0.0-9000.
iv. If the value of the currentThreadsBusy attribute is about 70 to 80
percent of the value of the maxThreads attribute, consider raising the value
of the maxThreads attribute.
312
2.
acceptCount - This is the number of request threads that are placed in the
request queue when all available threads are used. When the acceptCount
parameter exceeds the set limit, the client systems receive a request timeout
response.
3.
compression - When set to force, this attribute enables compression of the

content by JBoss and the compressed data is sent to the browser. The browser
extracts the content and displays the page on screen. Enabling compression can
substantially reduce the bandwidth requirements of applications.
Appendix V
Changing configuration settings in the

my.cnf file
This appendix provides instructions for configuring the my.cnf file for improving the
performance when the commands aim select and aim insert are used during
processing and expiration of jobs.
A new parameter innodb_flush_log_at_trx_commit must be added with a
value 2 in the my.cnf configuration file to enhance the performance.
The following entry must be added to in the my.cnf configuration file:
innodb_flush_log_at_trx_commit = 2
This parameter can be assigned with three different values. The following are the
descriptions with the three values:
Scenario 1:
When the value of the innodb_flush_log_at_trx_commit parameter is set to
0, the log information is stored in the MySQL log buffer and flush to disk operation is
performed on the log file once every second.
If MySQL crashes, there will be a loss of information from the MySQL log buffer for a
maximum of one second.
Scenario 2:
1 (default value), the log information is stored in the MySQL log buffer and flush to
disk operation is performed on the log file at each transaction commit.
Scenario 3:
HP Output Server
313
Appendix V
Changing configuration settings in the my.cnf file

2, the log information is stored in operating system log buffer instead of MySQL log
buffer at each transaction commit and flush to disk operation is performed on the log
file once every second.
There will be a data loss for a maximum of one second during an operating system
crash.
NOTE: HP recommends that you set the value of the
innodb_flush_log_at_trx_commit parameter to 2 to
enhance the performance during the job processing and expiration.
314
Appendix W
Executing the pdconfig command

from an HP Output Server client
installation
This appendix provides information about the usage of the setup_odbc_env.pl
script. The setup_odbc_env.pl script configures the ODBC environment on an
HP Output Server client installation, which lets you execute the pdconfig command
from an HP Output Server client installation. On UNIX, the setup_odbc_env.pl
script is available only in the HP Output Server client installation. The script is located
in the $HPOM_INSTALL/bin directory.
Before you execute the pdconfig command from an HP Output Server client
installation, you must apply HP Output Server Service Pack 12.1, and then run the
setup_odbc_env.pl script with appropriate parameters.
For more information about using the pdconfig command from an HP Output Server
client installation, refer to the System Administrators Command Reference for
HP Output Server.
The usage of the setup_odbc_env.pl script is as follows:
Syntax
setup_odbc_env.pl [-h|?] -a -d database type [-o ODBC
driver path] [-c Oracle client lib path] -r -e
HP Output Server
315
Appendix W
Executing the pdconfig command from an HP Output Server client installation
Arguments
-h|?
The -h|? argument displays the help for the setup_odbc_env.pl script.
-a
The -a argument sets up the ODBC environment. If you use -a, then you
must specify the database type.
-d database type
The -d database type argument specifies the database type. Specify either
MySQL or ORACLE as the database type. The database type must be the same
as the database type of the HP Output Server server installation. If -d is
ORACLE, then you must specify the ODBC driver path and the Oracle client
library path.
-o ODBC driver path
The optional -o ODBC driver path argument specifies the ODBC driver path
if the database type is ORACLE. For UNIX, specify the Easysoft ODBC driver
path. For Windows, specify the Oracle ODBC driver path.
-c Oracle client lib path
The optional -c Oracle client lib path argument specifies the path of the
Oracle client libraries if the database type is ORACLE.
-r
The -r argument removes the ODBC environment.
-e
The -e argument checks the existence of ODBC settings.
For more information about ODBC drivers and Oracle client libraries for UNIX, see
Chapter 2, Before you install HP Output Server with Oracle on a UNIX host
on page 41.
316
Appendix W
For more information about ODBC drivers and Oracle instant client libraries for
Windows, see Chapter 2, Before you install HP Output Server with Oracle on a
Windows host on page 77.
NOTE: When you specify the location for Oracle instant client
libraries and the Oracle ODBC driver on Windows, you must
specify the full path.
For example:
If you have stored the Oracle instant client libraries and the
Oracle ODBC driver in installDir\lib, specify the
path as installDir\lib.
Examples
To create an ODBC environment with MySQL as the database, enter the following
command:
perl setup_odbc_env.pl -a -d MySQL
To create an ODBC environment with Oracle as the database, enter the following
command:
perl setup_odbc_env.pl -a -d ORACLE -o
/usr/local/easysoft -c /home/user1/oracle_client_libs
To check the existence of ODBC settings, enter the following command:

perl setup_odbc_env.pl -e
To remove ODBC settings, enter the following command:

perl setup_odbc_env.pl -r
HP Output Server
317
Appendix W
318
Index
A
acceptCount 312
Accessing JBoss Web Console 308
Adjusting variables 266
AIM
configuring 110, 112
AIX
recommended settings 13
authentication 151, 252
authentication mode 151
AuthenticationManager script 255
authorization 151, 251
B
backup
MySQL 217
Oracle 182
same-directory installations 177
UNIX 163, 165
Windows 172
C
Checking the Embedded web container 311
HP Output Server
Checking the JBoss thread pool 310

client.ini 191
CM
compression 312
Concurrent connections 266
concurrent connections 267
configod.pl script 223
Configuration Manager
See CM
configuring
database connection on UNIX host 203
HP Output Server 149
HP Output Server domains 249
HP Web Console Job Manager 247
servers in HP Output Server 150
Configuring HP Output Distributor 100
263
connect_timeout 267
cover sheets
customizations 118
customer support xxv
customizations
file 118
319
D
Dazel ID mode 151
dazel_admin group 152
dazel_appl group 152
dazel_guest group 152
DAZEL_HOME environment variable 194, 197
DAZEL_HOSTNAME environment variable 194,
197, 213
DAZEL_PORTS environment variable 194, 198,
209
dazel_server group 152
dazel_superuser group 152
dazel_support group 152
dazel_user group 152
DAZELNS environment variable 195, 198
Delivery Manager
See DLM
delivery objects
customizations 118
delivery pathway
creating 154
Destination Manager 155
See DSM
disk space
HP Output Server 6
DLM
configuring 110
domain groups 249
DomainManager script 249
DPAOIDs
customizations 118
DSM
configuring 110
E
Easysoft ODBC-Oracle Driver 233
EASYSOFT_ROOTenvironment variable 195
320
enforced authentication 253

ENSCRIPT_LIBRARY environment variable 195,
198
environment variables
on UNIX 194
on Windows 197
setting in HP Output Server 150, 199
F
files
customizations 118
firewall support 209
G
Granting access 263
group authorization 151
groups 152
H
hardware requirements
HP Output Server 6
hotfixes
installing
on UNIX 132
on Windows 145
removing
on UNIX 139
on Windows 147
HP Job Manager for Output Server Software 297
operating system supported 11
XML tags 301
configod.pl script 223
installing 98
supported installations 25
HP Output Server
DVD contents 3
installing 33
interoperability 24
system requirements 6
templates 155
uninstalling 101, 245
upgrading 109
HP Output Server domains 252
HP Output Server Manager 293
HP Output Server Privilege Manager 251
HP Web Console Job Manager
configuring 249
domain groups 249
managing domains 250
HPOM_HOME environment variable 194
HP-UX recommended settings 15
I
innodb_max_purge_lag 268
installation
hotfixes
on UNIX 132
on Windows 145
HP Output Server
on UNIX 41
planning on a network 29
pre-installation checklist 28
on UNIX 293
on Windows 293
Installation package
hierarchy and contents 3
interdomain delivery 154
J
JBoss Tuning 310
Job and Queue Manager
See JQM
Job And Queue Manager (JQM) 155
HP Output Server
JQM
configuring 110
JVM Tuning 309
K
kernel parameters
recommended on HP-UX 15
setting on HP-UX 19
L
LANG environment variable 196, 197
LD_LIBRARY_PATH environment variable 196,
197
LIBPATH environment variable 196
Linux recommended settings 14
lock file 216
logical destination
creating 158
definition 154
templates 156, 158
login session time-out 254
-lpg-masterlock attribute 216
LPR Gateway
configuring in a multi-NIC environment 214,
216
M
-managing-server attribute 155
MANPATH environment variable 195
max_allowed_packet 269
max_connections 267
max_thread_proc 267
maxThreads 311
memory
HP Output Server 6
MIBDIRS environment variable 195, 198
MIBS environment variable 195, 198
Microsoft Windows
See Windows
321
multi-NIC environment
configuring HP Output Server 214
configuring the LPR Gateway 216
MySQL for HP Output Management
hot backup and restore 217
system requirements 6
MySQL tunable parameters 225, 283
N
Name Space Manager
See NM
network interface cards 213
NLSPATH environment variable 195
NM
O
ODBCINI environment variable 195
ODBCSYSINI environment variable 195
OMS Callback 110
Open SSL 245
operating systems
kernel parameters 13
required patches 9
supported platforms
HP Output Server 9
Oracle database
backing up 183
prerequisites 42
restoring 183
Oracle Instant Client libraries
downloading 229
Oracle parameters
tuning 239
ORACLE_HOME environment variable 195
P
patches 131
PATH environment variable 195, 198
PERL5LIB environment variable 195, 198
322
permissions
modifying 151
setting 151
creating 158
definition 154
templates 156, 158
Prerequisites for tuning MySQL 271
prerequisites for upgrading 116
Privilege Manager
See PM
Q
queue
creating 157
definition 154
templates 156, 157
R
restoring files
backup template customizations 127
UNIX 127
Windows 127
S
SAPconnect 110
server.ini 187, 290, 291
Setting MySQL startup-time 305
setup.pl
using non-interactively 185
setup.pl, using non-interactively 289
setup_env.bat 193
setup_env.csh 193
setup_env.pl 193
setup_env.sh 193
SHLIB_PATH environment variable 197
Solaris
installation requirements 7
patch levels 10
swap space requirements 21
startup-time for JBoss 307

support xxv, xxvi
System requirements for HP Output Server Manager
10
T
Task performed by the tunemysql_hpos.pl script 278
Tasks performed by the tunemysql_hpos.pl script
with de-fragmentation of databases 279
templates
definition 156
logical destination 156, 158
physical destination 156, 158
queue 156, 157
thread_cache 268
training xxv
trusted authentication 252
Tuning JBoss Application Server 307
Tuning MySQL parameters for 256MB, 512MB,
1GB and 1.5GB memory usage for buffer
pool 280
Tuning the MySQL for HP Output Server 274
HP Output Server
typographic conventions xviii
U
uninstalling
hotfixes
on UNIX 139
on Windows 147
HP Job Manager for Output Server Software 302
HP Output Server
on UNIX 102, 104
on Windows 107
UNIX
installation 293
UNIX ID mode 151
user authentication 151
W
wait_timeout 269
Windows
installation 293
323
324

HPOS SP12.1 Install and Config Guide Hpos41sp121incenUS

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HPOS SP12.1 Install and Config Guide Hpos41sp121incenUS

Uploaded by

Copyright:

Available Formats

HP Output Server 4.1.0.

1991-2012 Hewlett-Packard Development Company, L.P.

Planning the installation ................................................1

Contents of the HP Output Server package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing HP Output Server .........................................33

Performing an HP Output Server standard installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation and Configuration Guide

Installing HP Output Server on Windows hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Uninstalling HP Output Server ..................................101

Uninstalling HP Output Server from a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Migration options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Migrating HP Output Server on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Installing and removing patches ...............................131

Join a domain patch installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Removing a patch from an HP Output Server standard installation on a UNIX host . . . . . . . . . . . . . . .

Removing a patch from a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Configuring HP Output Server...................................149

Setting environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Changing log level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Installation and Configuration Guide

Backing up and restoring HP Output Server............163

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Using setup.pl in non-interactive mode....................185

Sample syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Environment variables in HP Output Server ............193

UNIX environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Configuring the database connection

HP Output Server and the database on the same host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Firewall support ..........................................................209

Implementing firewall support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

HP Output Server in a multi-NIC environment .........213

Hot backup ..................................................................217

HP Output Distributor configod.pl script..................223

Using help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Installation and Configuration Guide

Prerequisites for installing HP Output Server

Tuning Oracle parameters .........................................239

Limited access to directories and files.....................243

Installing OpenSSL .....................................................245

Configuring and administering

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Managing authentication methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

M Configuring MySQL for HP Output Management.....263

Tuning MySQL for HP Output Server........................271

Installation and Configuration Guide

Using HP Output Server data for

MySQL tunable parameters .......................................283

Using patch.pl in non-interactive mode....................289

Installing HP Output Server Manager .......................293

Installing HP Output Server Manager in interactive mode on Windows hosts . . . . . . . . . . . . . . . . . . . . . . . 293

Installing HP Job Manager for

Setting MySQL startup time.......................................305

Tuning the JBoss application server ........................307

Changing configuration settings in the

W Executing the pdconfig command from an

Installation and Configuration Guide

The System Administrators Command Reference and System Administrators

Used to denote new terms and to

Each of these objects has

Used for emphasis, book titles, user

Install the program in the

Denotes acronyms, device names,

Click the Modify button.

Refer to the System