Installation and Configuration Guide 3.5

HP Output Server 3.5Installation and Configuration Guide

Part No. T2358-90022

© 1991-2005 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.December 2005 Edition for HP Output ServerConfidential 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 vendor’s 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), or CD-ROM(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 NoticesCopyright © 1991-2005 Hewlett-Packard Development Company, L.P.Portions Copyrighted ByCopyright © 2000-2005 MySQL AB & MySQL Finland AB & TCX DataKonsult AB.Copyright © 2000 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.

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.Copyright © 1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.Copyright © 1993 - 2005 SAP AG, Walldorf.Trademark NoticesAdobe®, Acrobat®, Acrobat Logo®, and PostScript® are trademarks of Adobe Systems Incorporated.Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.UNIX® is a registered trademark of the Open Group.Hewlett-Packard Limited Warranty StatementHP ProductHPOM SoftwarePeriod of Limited Warranty90 DaysA. Extent of Limited Warranty1. 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 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 or region for which it was never intended to function for legal or regulatory reasons.B. Limitations of Warranty1. 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 Liability1. 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 Law1. 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 to country 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 ................................................................................xiiiRelated documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiTypographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvTraining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviSupport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Before you call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

1 Planning the Installation ................................................1CD-ROM hierarchy and contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

MySQL for HP Output Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2HP Output Server, Version 3.5, Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3HP Output Server, Version 3.5, Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4HP Output Manager for SAP, Version 3.5, Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4HP Output Distributor and HP Output Distributor Manager,

Version 3.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

HP Output Server vii

Contents

System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5System requirements for MySQL for HP Output Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5System requirements for HP Output Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Operating system patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Kernel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Interoperability with HP Output Management applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Supported SAP installations with HP Output Manager for SAP, Version 3.5. . . . . . . . . . . . . . . . . . . . . . 20

Supported HP Output Server configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Installation and configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Pre-installation checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Setting permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Installing on a non-English version of Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Planning an installation on a network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Device requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Connecting devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2 Installing HP Output Server .........................................29Installation options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Assumptions and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Installing on UNIX hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Before you install on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Creating a default set of servers on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Joining an existing domain on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Creating a new domain on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Creating a client-only installation (UNIX host only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Installing on Windows hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Before you install on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Creating a set of default servers on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Joining an existing domain on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Creating a new domain without a default set of servers on a Windows host . . . . . . . . . . . . . . . . . . . . . . 54

Completing the installation of HP Output Manager for SAP 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

viii Installation and Configuration Guide

Contents

Completing the installation of HP Output Distributor 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Destination and permissions templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Troubleshooting failed template installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Uploading templates manually after creating a new domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Configuring HP Output Distributor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

3 Uninstalling HP Output Server ....................................59Uninstalling HP Output Server on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Uninstalling HP Output Server on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4 Upgrading HP Output Server .......................................63Integrated product upgrade and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Upgrade effects on HP Output Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Upgrade effects on HP Output Manager for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Upgrade effects on HP Output Distributor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Assumptions and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

HP Output Server 3.3 and 3.4.1 upgrade prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69HP Output Manager for SAP 6.1 upgrade prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73HP Output Distributor 2.0 upgrade prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Upgrading a multi-host domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Upgrading HP Output Server on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Upgrading an HP Output Server server installation on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Upgrading an HP Output Server client installation (UNIX only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Upgrading on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Restoring backup template customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Troubleshooting a failed upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Recovering from a failed HP Output Server upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Recovering from a failed HP Output Distributor upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

5 Installing and Removing Patches................................97Installing a patch on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

HP Output Server ix

Contents

Removing a patch from a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Installing a patch on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Removing a patch from a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

6 Configuring HP Output Server...................................107Setting environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Configuring HP Output Server servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Selecting a different language on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Configuring user authentication and authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Setting the authentication mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Modifying user and group permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Configuring interdomain delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Configuring the LPR Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Creating a delivery pathway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Creating a queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Creating a logical destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Creating a physical destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Testing the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

7 Backing up and Restoring HP Output Server 3.5 ....121Before you begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Backing up HP Output Server on a UNIX host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Task 1: Backing up program and configuration files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Task 2: Backing up HP Output Server databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Restoring HP Output Server on a UNIX host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Task 1: Recreating the HP Output Server databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Task 2: Restoring the program and configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Backing up HP Output Server on a Windows host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Task 1: Backing up program and configuration files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Task 2: Backing up the HP Output Server databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Restoring HP Output Server on a Windows host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Task 1: Recreating the HP Output Server databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Task 2: Restoring the HP Output Server installation directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

x Installation and Configuration Guide

Contents

Backing up and restoring same directory installations (UNIX only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Backing up same directory installations (UNIX only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Restoring same directory installations (UNIX only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

A Mounting a Product CD-ROM on UNIX Systems......139Mounting a CD-ROM on an AIX system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Mounting a CD-ROM on an HP-UX system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Mounting a CD-ROM on a Solaris system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Mounting a CD-ROM on a Linux system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

B Using setup.pl in Non-interactive Mode ...................143Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Creating a server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Creating a client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Upgrading an HP Output Server 3.3 server installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Upgrading an HP Output Server 3.4.1 server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Upgrading a client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Uninstalling HP Output Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Using help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

C Environment Variables in HP Output Server............147Environment variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

UNIX environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Windows environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Setting environment variables in HP Output Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

D Configuring the HP Output Server LPR Gateway ....155Disabling the existing print spooler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Disabling the print spooler on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Disabling the print spooler on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

HP Output Server xi

Contents

Creating a server for the LPR Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Configuring output devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Entries in the printcap file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Use of an input filter for an output device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Authorizing remote hosts to use the LPR Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Configuring remote hosts to use the LPR Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

E Firewall Support..........................................................165Implementing firewall support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

F HP Output Server in a Multi-NIC Environment .........169Configuring multiple instances of HP Output Server to use the same network interface . . . . . . . . . . . . . . . 170Changing the host name throughout the configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Restoring communication on all network interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Configuring multiple LPR Gateway servers in a multiple NIC environment (UNIX only). . . . . . . . . . . . . . 175

G Configuring the MySQL Connection .........................177HP Output Server and MySQL on the same host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177HP Output Server and MySQL on separate hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

H HP Output Distributor 2.0 Clean-up Utility ...............181

I HP Output Distributor 2.0 Data Migration Utility......183

J configod.pl Script .......................................................187Using help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Installing templates and configuring the CM and PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Removing templates for HP Output Distributor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Upgrading templates for HP Output Distributor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Index ...................................................................................189

xii Installation and Configuration Guide

Preface

HP Output Server

This manual provides the information you need to install HP Output Server, HP Output Manager for SAP, and HP Output Distributor. When you install a server installation of HP Output Server, the software for HP Output Manager for SAP and HP Output Distributor installs automatically. If you upgrade an existing HP Output Server server installation, the software for HP Output Manager for SAP and HP Output Distributor installs automatically or is upgraded if an installation that is supported for an upgrade already exists with your HP Output Server installation.

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 describes 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:
• The Installation and Configuration Guide for HP Output Server describes system requirements and planning and explains how to install and configure HP Output Server.

xiii

xiv

Preface

Related documentation

• The System Administrator’s Guide for HP Output Server explains how to perform administrative tasks with the HP Output Server Command Line Interface (CLI) and, where applicable, provides a reference to its GUI counterpart.

• The System Administrator’s Attribute Reference and System Administrator’s Command Reference for HP Output Server provide detailed information about the HP Output Server CLI commands and attributes.

• The Release Notes for HP Output Server provides important information that was not included in the manuals, including specific requirements for each supported platform and information about specific hardware and software that you may want to use with HP Output Server.

• The Installation and Configuration Guide for MySQL for HP Output Management describes system requirements and planning and explains how to install and configure MySQL for HP Output Management.

• The Release Notes for MySQL for HP Output Management contains important information that is not included in this manual, such as requirements for supported platforms and information about specific hardware and software that you may want to use with MySQL for HP Output Management.

If you purchased a license for HP Output Manager for SAP 3.5, your HP Output Server installation includes a CD-ROM that contains documentation for configuring and using HP Output Manager for SAP 3.5. For information about the directory structure and contents of the HP Output Manager for SAP documentation CD-ROM, see the Release Notes for HP Output Manager for SAP.

If you purchased a license for HP Output Distributor 3.5, your HP Output Server installation includes a CD-ROM that contains the documentation for configuring and using HP Output Distributor 3.5 and software and documentation for installing and using HP Output Distributor Manager 3.5, a Windows-based program that enables you to configure and maintain HP Output Distributor. For information about the directory structure and contents of the HP Output Distributor documentation and client software CD-ROM, see the Release Notes for HP Output Distributor 3.5.

You can access the documentation in PDF format on each product CD-ROM or download it from the following Web site:

http://itrc.hp.com

NOTE: You must register to access this Web site.

For more information about HP Output Management products, visit:

http://hp.com/go/outputmanagement

Installation and Configuration Guide

http://itrc.hp.com

http://hp.com/go/outputmanagement

HP Output Server

Preface

Typographic conventions

This site offers a variety of information about HP Output Management products and solutions. Included on the site are links to technical notes. Technical notes provide specific information about a particular device, configuration, or situation. For example, a technical note might explain how to configure HP Output Server to deliver to a specific HP printer.

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.

Click the Modify button.

italic Used for emphasis, book titles, user input variables, and command syntax variables.

Install the program in the installDir directory.

Refer to the System Administrator’s Command Reference.

UPPERCASE Denotes acronyms, device names, logical operators, environment variables, and registry entries.

DZL_HOMEHKEY_CLASSES_ROOT

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:

Type y to confirm the selection.

Delete the example.txt document when you have completed the exercise.

> Shows a selection from a menu in a user interface.

Select File>Save.

(Instructs you to select the Save command from the File menu.)

xv

xvi

Preface

Training

Command examples in HP documentation are operating system-independent and appear separate from the text. Hanging indentation indicates that a command line wraps:

pdshutdown -c server-x"-message \"Down for maintenance\"-when after-all" jqm_01

In text, absolute and relative path and file names follow UNIX conventions:

Change directories to the installDir/var/log directory.

Training
We offer training courses for most of our products. You can attend HP Output Management training in North America or EMEA. Some courses can also be taught at a customer site. For other training options or to register for classes, visit our Web site at
http://www.hp.com/united-states/outputmanagement/training/

Support
To obtain assistance, offer feedback, or request enhancements, contact Customer Support on the Web or by telephone. To contact Customer Support on the Web, use the following URL:
http://itrc.hp.com

To contact Customer Support by telephone, use the following telephone numbers:

Country/Region or City Telephone

In-country/Region International

Americas United States 800 633 3600


http://www.hp.com/united-states/outputmanagement/training/

http://itrc.hp.com

HP Output Server

Preface

Support

Europe/Middle East/Africa (EMEA)

Belgium 078 250 144 +32 2 620 00 55

Finland 0203 66 200 +358 203 66 200

France 0825 00 41 23 +33 241 74 24 65

Germany 01 805 332 525 +49 2102 90 7244

Italy 02 385 91090 +39 (0) 2 385 91090

Netherlands 020 547 9666 +31 (0) 20 547 9666

Portugal 808 203 203 +351 213 176 350

Saudi Arabia 800 124 1001 +966 1 273 1200

South Africa 08 6000 1010 +27 11 785 1010

Spain 902 012 069 +34 902 012 069

Sweden 08 579 29 119 +46 (8) 579 29 119

Switzerland 0800 55 33 13 +41 (0) 848 800 724

United Kingdom 0870 842 2330 +44 1344 389 421

Asia Pacific Singapore 1800 329 3588 +61 2 9022 9218

Sydney 1800 032 935 +61 2 9022 9218

Country/Region Postal Address

United States Hewlett-Packard Company14231 Tandem BoulevardAustin, TX 78728USA

Europe Hewlett-Packard Company80, rue Camille Desmoulins 92788 Issy les Moulineaux Cedex 9France

Country/Region or City Telephone

In-country/Region International

xvii

xviii

Preface

Support

Asia Pacific Hewlett-Packard Far East Pte. Ltd.460 Alexandria Road, PSA BuildingSingapore 119963

Country/Region Postal Address

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(s) 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,

- From what operating system are you delivering?

- To what operating system are you delivering?

• Can you repeat the problem or is it intermittent?


Chapter 1

Planning the Installation

HP Output Server

This chapter describes the types of configurations that HP Output Server supports and the steps that you can take to prepare for an HP Output Server installation in your environment. For more information about particular system requirements for each configuration option, see the Release Notes for HP Output Server.

A typical HP Output Server installation includes installing and configuring MySQL for HP Output Management and HP Output Server. Because HP Output Server uses a client-server model and runs on UNIX and Windows operating systems, it supports a wide range of configuration options.

HP Output Server 3.5 integrates the installation, upgrade, and patching of HP Output Manager for SAP and HP Output Distributor. 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 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.

When you install a server installation of HP Output Server 3.5, the software for HP Output Manager for SAP and HP Output Distributor installs automatically. If you upgrade an existing HP Output Server server installation, the software for HP Output

1

2

Chapter 1 Planning the Installation

CD-ROM hierarchy and contents

Manager for SAP and HP Output Distributor installs automatically or is upgraded if an installation that is supported for an upgrade already exists. For more information about upgrading HP Output Server, see Chapter 4, “Upgrading HP Output Server” on page 63.

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 describes how to use them.

HP Output Server includes the following product CD-ROMs:
• MySQL for HP Output Management

• HP Output Server, Version 3.5, Software

• HP Output Server, Version 3.5, Documentation

If you purchased a license for HP Output Manager for SAP and/or HP Output Distributor, the following additional CD-ROMs are included:

• HP Output Manager for SAP, Version 3.5, Documentation

• HP Output Distributor (documentation) and HP Output Distributor Manager (software and documentation), Version 3.5

This section describes the directory structure and contents of the HP Output Server, Version 3.5 software and documentation CD-ROMs. It also describes how to find information about the directory structure and contents of the documentation and software CD-ROMs for HP Output Manager for SAP 3.5 and HP Output Distributor 3.5.

MySQL for HP Output Management
HP integrates the MySQL relational database management system from MySQL AB with HP Output Server 3.5 and HP Output Distributor 3.5. The MySQL for HP Output Management CD-ROM contains the files that are necessary for installing and configuring MySQL for HP Output Management. For information about the directory structure and contents of the MySQL for HP Output Management CD-ROM, see the Release Notes for MySQL for HP Output Management.



HP Output Server, Version 3.5, Software

HP Output Server

The HP Output Server software CD-ROM contains the files that are necessary for installing and configuring HP Output Server.

The following table describes the directory structure and contents of the HP Output Server CD-ROM.Table 1-1. HP Output Server software CD-ROM contents

Directory Contents

/ The top-level directory contains the Release Notes for HP Output Server in PDF format.

/operatingSystem This directory contains the files necessary for installing and configuring HP Output Server, HP Output Manager for SAP, and HP Output Distributor. The software for each operating system is delivered on a separate CD-ROM. Each HP Output Server software CD-ROM is labeled with one of the following supported operating systems:

• AIX• HP-UX• Red Hat Linux (client only)• Solaris• Windows

The value of operatingSystem is one of the following:

• aix • hp hpia64The HP-UX CD-ROM includes two operating system directories.

• linux • sol • win32

3



HP Output Server, Version 3.5, Documentation

4

The HP Output Server documentation CD-ROM contains PDF versions of the documentation for HP Output Server:

The following table describes the directory structure and contents of the HP Output Server documentation CD-ROM.Table 1-2. Documentation CD-ROM contents

Directory Contents

/ The top-level directory contains the Release Notes document for HP Output Server in PDF format.

/docs/language/pdf The docs/language/pdf directory contains the HP Output Server product documentation in PDF format.

/docs/language/pdf/install This directory contains the Installation and Configuration Guide for HP Output Server.

/docs/language/pdf/saar This directory contains the System Administrator’s Attribute Reference for HP Output Server.

/docs/language/pdf/sacr This directory contains the System Administrator’s Command Reference for HP Output Server.

/docs/language/pdf/sag This directory contains the System Administrator’s Guide for HP Output Server.

HP Output Manager for SAP, Version 3.5, Documentation
HP Output Server 3.5 includes HP Output Manager for SAP 3.5. When you install a server installation of HP Output Server 3.5, the software for HP Output Manager for SAP 3.5 installs automatically. If you upgrade an existing HP Output Server server installation, the software for HP Output Manager for SAP installs automatically or is upgraded if an installation that is supported for an upgrade already exists. If you purchased a license for HP Output Manager for SAP 3.5, your HP Output Server installation includes a CD-ROM that contains documentation for configuring and using HP Output Manager for SAP 3.5.
For information about the directory structure and contents of the HP Output Manager for SAP documentation CD-ROM, see the Release Notes for HP Output Manager for SAP 3.5.



System requirements

HP Output Distributor and HP Output Distributor Manager, Version 3.5

HP Output Server

HP Output Server 3.5 includes HP Output Distributor 3.5. When you install a server installation of HP Output Server 3.5, the software for HP Output Distributor 3.5 installs automatically. If you upgrade an existing HP Output Server server installation, the software for HP Output Distributor installs automatically or is upgraded if an installation that is supported for an upgrade already exists. If you purchased a license for HP Output Distributor 3.5, your HP Output Server installation includes a CD-ROM that contains the documentation for configuring and using HP Output Distributor 3.5 and the software and documentation for installing and using HP Output Distributor Manager 3.5, a Windows-based program that enables you to configure and maintain HP Output Distributor.

For information about the directory structure and contents of the HP Output Distributor documentation and client software CD-ROM, see the Release Notes for HP Output Distributor 3.5.

System requirements
In order 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 3.5 and its supporting software. Use these sections as a guide for determining the physical configuration of your host machine or machines.
System requirements for MySQL for HP Output Management
MySQL for HP Output Management uses the InnoDB storage engine. HP Output Server 3.5 relies on the InnoDB storage engine for proper functioning. You must install or upgrade to MySQL for HP Output Management, Version 4.1.12 or the most recent version that is supported with HP Output Server 3.5 prior to installing a server installation of HP Output Server 3.5 or upgrading to HP Output Server 3.5 from HP Output Server 3.3 or 3.4.1. For more information about system requirements and
5

6


System requirements

how to install MySQL for HP Output Management, see the Installation and Configuration Guide and the Release Notes for the most recent release of MySQL for HP Output Management.

NOTE: HP supports installations of HP Output Server 3.5 that use MySQL for HP Output Management only.

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, also read “Supported HP Output Server configurations” on page 20.
Hardware
This section summarizes the minimum recommended disk space and memory that HP recommends for each supported platform for an HP Output Server installation. These recommended values include 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-3. Minimum hardware requirements

Operating System and Hardware

Default (Full) Installation Client-Only Installation*

Minimum Disk Space†‡

Minimum Physical Memory**

Minimum Disk Space‡


AIX 5.2 and 5.3 (64-bit kernel) on IBM UNIX servers

400 MB 1 GB 250 MB 128 MB

HP-UX 11.11 (64-bit kernel) on PA-RISC

490 MB 1 GB 270 MB 128 MB


490 MB 1 GB 270 MB 128 MB

HP-UX 11.23 (64-bit kernel) on Itanium (IA64)

485 MB 1 GB 265 MB 128 MB

Solaris 9 and 10 (64-bit kernel) on SPARC

520 MB 1 GB 315 MB 128 MB

Windows 2000 Server and Advanced Server

145 MB 1 GB not applicable not applicable



System requirements

Operating system patches

Windows Server 2003 Standard Edition and Enterprise Edition (32-bit)

145 MB 1 GB not applicable not applicable

Red Hat Enterprise Linux ES 4.0; 32-bit kernel version 2.6 (client only) on i386 and x64.

not applicable not applicable 170 MB 128 MB

* HP Output Distributor does not support a client-only installation.

† 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.

‡ Additional disk space is required when upgrading from HP Output Server Version 3.3 or 3.4.1 to HP Output Server 3.5.

** 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.

Table 1-3. Minimum hardware requirements (continued)

Operating System and Hardware

Default (Full) Installation Client-Only Installation*

Minimum Disk Space†‡


Minimum Disk Space‡


HP Output Server

The following table identifies recommended operating system patches, if any, that have been tested by HP for use with HP Output Server 3.5. 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 3.5. See the Release Notes for the latest service pack for HP Output Server 3.5 for updated information about recommended operating system patches for use with a service pack.

Table 1-4. Supported operating system patch levels

Operating System and Hardware Patch Level

AIX 5.2 (64-bit kernel) on IBM UNIX servers

Release Maintenance 6

AIX 5.3 (64-bit kernel) on IBM UNIX servers

Release Maintenance 2


Required Patch Bundle for HP-UX 11i, June 2003

Quality Pack Patches for HP-UX 11i v1, June 2005

Hardware Enablement Patches for HP-UX 11i v1, December 2004

7


System requirements


Feature Enablement Patches for HP-UX 11i v2, May 2005

Hardware Enablement Patches for HP-UX 11i v2, May 2005

Quality Pack Patches for HP-UX 11i v2, May 2005

HP-UX 11.23 (64-bit kernel) on Itanium (IA64)

Feature Enablement Patches for HP-UX 11i v2, May 2005

Hardware Enablement Patches for HP-UX 11i v2, May 2005

Quality Pack Patches for HP-UX 11i v2, May 2005

Solaris 9 (64-bit kernel) on SPARC June 2005 Recommended Patch Cluster

Solaris 10 (64-bit kernel) on SPARC 118560-01

119015-02

119254-02

119317-01

119689-02

Red Hat Enterprise Linux ES 4.0; 32-bit kernel version 2.6 on i386 and x64

none

Windows 2000 Server and Advanced Server

Service Pack 4*

Windows Server 2003 Standard Edition and Enterprise Edition (32-bit)

Service Pack 1†

* Tested with but not required: KB893803, KB842773, KB891861, KB890830, KB897715, KB883939, KB867801, KB837009, KB828741, KB835732, KB898458, KB896358, KB890046, KB896422, Q329115, KB887811, KB839643, Q329553, 814033, 810649, KB901214, KB903235, and KB899588

† Tested with but not required: KB893803, KB842773, KB890830, KB897715, KB832894, KB893066, KB898458, KB870669, KB890046, KB883939, KB896358, KB896422, KB896428, KB898715, KB898792, KB901214, KB903235, and KB899588.

Table 1-4. Supported operating system patch levels (continued)

Operating System and Hardware Patch Level

8 Installation and Configuration Guide


System requirements

Kernel parameters

HP Output Server

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 and 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 Administrator’s Attribute Reference for HP Output Server.

If messages indicating memory or resource issues continue to appear in the DLM or JQM logs after adjusting 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.

9


System requirements

HP-UX recommended settings

10

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-5. Recommended HP-UX kernel parameters

Kernel Parameter Description Recommended Setting

dbc_max_pct Maximum percentage of memory for dynamic buffer cache 25*

Note that this recommended setting is for HP-UX 11.11. For HP-UX 11.23 on PA-RISC and Itanium, use the operating system default setting.



System requirements

max_thread_proc Maximum number of threads that one process can create.

Because the max_thread_proc kernel parameter is related to the MySQL max_connections system variable, it is important to coordinate the two settings.

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.

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 Administrator’s Attribute Reference and “Tuning and Resource Management” in the System Administrator’s Guide for HP Output Server 3.5.

1024

If the MySQL server is running on a different host than HP Output Server, set max_thread_proc to 256 on the HP-UX system that HP Output Server is running on.

maxdsiz Maximum data segment size for an executing 32-bit process.

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.

100,000,000


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

2048

Table 1-5. Recommended HP-UX kernel parameters (continued)


HP Output Server 11


System requirements

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

2048


maxuprc Maximum number of simultaneous processes for any given user.

1000

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†






System requirements

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:

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.

Equal to or greater than the total number of HP Output Server servers on a single host.

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:

vmunix: kthread: table is full

max_thread_proc x 2


nproc Maximum total number of simultaneous processes allowed. 4000


* If your host contains more than 4 GB of memory, decrease this value to 15.

† The formula for nfile is for HP Output Server 3.5 with HP Output Distributor 3.5 and HP Output Manager for SAP 3.5. It does not include other HP Output Management products or other applications.



HP Output Server 13


System requirements

Setting kernel parameters on HP-UX

14

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.

Checking a kernel parameter valueTo 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.

Setting a kernel parameter valueTo change a kernel parameter setting, perform the following steps:

1. Log in as root.

2. Type the following command:

cp /stand/system /stand/system.prev

Operating system Command

HP-UX 11.11 (64-bit kernel) kmtune -q parameterwhere 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 parameterwhere parameter is the name of the kernel parameter, for example:

kctune -q dbc_max_pct


HP Output Server


System requirements

3. For each parameter you want to change, execute the following command:

4. Repeat step 3 for each kernel parameter that you want to set. You can use the kmtune -q or kctune -q command (depending on your operating system) to verify your changes.

5. If you are using HP-UX 11.23, skip to step 6. On HP-UX 11.11, execute the following commands.

cd /stand/buildcp ../vmunix ../vmunix.prevmk_kernelmv vmunix_test ../vmunix

6. Reboot the system.

7. To verify the settings, use the kmtune -q or kctune -q command (depending on your operating system).

Operating system Command

HP-UX 11.0

HP-UX 11.11

kmtune -s parameter=valuewhere parameter is the name of the kernel parameter and value is the new value (number or formula)

HP-UX 11.23 (64-bit kernel) on Itanium (IA64) or PA-RISC

kctune -s parameter=valuewhere parameter is the name of the kernel parameter and value is the new value (number or formula)

15


System requirements

Solaris 9 recommended settings

16

The following table identifies the recommended kernel parameters for Solaris 9 hosts. For information about how to set kernel parameters on a Solaris operating system, refer to the documentation that accompanies the operating system.Table 1-6. Recommended Solaris 9 kernel parameters

System Name Sysdef Name Minimum Value

semsys:seminfo_semmni SEMMNI 100

semsys:seminfo_semmns SEMMNS 200

semsys:seminfo_semmnu SEMMNU 30

semsys:seminfo_semmsl SEMMSL 30

semsys:seminfo_semopm SEMOPM 10

semsys:seminfo_semume SEMUME 10

semsys:seminfo_semvmx SEMVMX 32767

semsys:seminfo_semaem SEMAEM 16384

shmsys:shminfo_shmmax SHMMAX 1073741824

shmsys:shminfo_shmmin SHMMIN 1

shmsys:shminfo_shmmni SHMMNI 100

shmsys:shminfo_shmseg SHMSEG 20



System requirements

Setting kernel parameters on Solaris

HP Output Server

This section describes one method for setting kernel parameters on a Solaris operating system.

NOTE: For more information about setting kernel parameters on a Solaris operating system, see the documentation that accompanies the operating system.

To set kernel parameters on Solaris, use the following steps:

1. Determine if the shared memory module is loaded by typing the following command:

/usr/sbin/modinfo | grep shmsys

If the above command returns a list of information similar to the following example, the shared memory module is loaded.

30 1227ec3 293d 52 1 shmsys (System V shared memory)

30 1227ec3 293d 52 1 shmsys (32-bit System V shared memory)

If the command does not return a list of information, or if the columns contain a value of 0 (zero), update your host to automatically load the shared memory module by including the following line in the /etc/system file:

forceload: sys/shmsys

2. Determine if the semaphore module is loaded by typing the following command:

/usr/sbin/modinfo | grep semsys

If the above command returns a list of information similar to the following example, the semaphore module is loaded.

32 122aa44 2a1a 53 1 semsys (System V semaphore facility)

32 122aa44 2a1a 53 1 semsys (32-bit System V semaphore facil)

If the command does not return a list of information or if the columns contain a value of 0 (zero), update your host to load the semaphore module automatically by including the following line in the /etc/system file:

forceload: sys/semsys

3. To view the current kernel parameter settings, type the sysdef command.

17

18


System requirements

4. If the values of the kernel parameters are not the same as the values in Table 1-6. Recommended Solaris 9 kernel parameters, edit the /etc/system file and change the values. For example:

set semsys:seminfo_semmsl=30

5. Save any changes you make to the /etc/system file.

6. To automatically load the required modules and apply any changes you make to the kernel parameter settings, reboot the system.

Interoperability with HP Output Management applications
If you are upgrading an existing HP Output Server installation to Version 3.5 and that system has additional HP Output Management products that rely on HP Output Server already installed, you must apply the appropriate service pack to each product before upgrading HP Output Server. 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 after you upgrade HP Output Server.
If the product relies on MySQL for HP Output Management, check the product documentation to ensure that your MySQL installation is at a version that is compatible with the HP Output Management product before installing or upgrading the HP Output Management product.

If you are installing HP Output Server 3.5 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-7. Supported HP Output Management applications

HP Output Management Application Version and Patch Level

Server side HP Output Server Version 3.3 or 3.4.1 with Service Pack 05.2 (3.3.0.13.0.3 or 3.4.1.2.0.7)

HP Output Distributor Version 2.0 with Service Pack 04.3 (2.0.0.12.0.2)

HP Output Manager for SAP Version 6.1 with Service Pack 05.2 (6.1.0.15.0.3)

HP Web Delivery Version 1.5.1 with Service Pack 05.2 (1.5.1.3.0.6)

HP Output Manager for OpenView

Version 2.0.1



System requirements

Interoperability with HP Output Distributor Manager

Client side HP Output Server Version 3.3 or 3.4.1 with Service Pack 05.2 (3.3.0.13.0.3 or 3.4.1.2.0.7)

HP Output Manager for SAP Version 6.1 with Service Pack 05.2 (6.1.0.15.0.3)

HP Output Explorer Version 3.0.0.21.0

HP Output Envoy Version 1.1.0.21.0

Table 1-7. Supported HP Output Management applications (continued)

HP Output Management Application Version and Patch Level

HP Output Server

If you are using HP Output Distributor Manager 2.0 with HP Output Distributor 2.0, you must upgrade HP Output Distributor Manager to Version 3.5 after upgrading to HP Output Server 3.5 with HP Output Distributor. HP Output Distributor Manager 2.0 does not function with HP Output Distributor 3.5. For more information about installing or upgrading to HP Output Distributor Manager 3.5, see the Installation and Configuration Guide and the Release Notes for HP Output Distributor Manager 3.5.

Interdomain interoperability
HP Output Server 3.5 communicates with HP Output Server 3.3 and 3.4.1 domains in the following ways:
• You can submit jobs to HP Output Server 3.5 and track them from either HP Output Server 3.3 or 3.4.1.

• You can submit jobs to HP Output Server 3.3 or 3.4.1 and track them from HP Output Server 3.5.

• Events and AIM operations related to job submission and tracking are sent and performed.

• Jobs submitted from HP Output Server 3.5 to either HP Output Server 3.3 or 3.4.1 cannot access the new features of HP Output Server 3.5.

• Interdomain communications through a firewall to or from HP Output Server 3.3 are not supported. HP Output Server 3.3 does not support firewalls.

19


Supported HP Output Server configurations

Intradomain interoperability

20

HP Output Server 3.5 communicates with client installations of HP Output Server 3.3 and 3.4.1 in the following ways:

• You can submit jobs to HP Output Server 3.5 and track them from either HP Output Server 3.3 or 3.4.1 client installations.

• Events and AIM operations related to job submission and tracking are sent and performed.

• New features in HP Output Server 3.5 are not supported from HP Output Server 3.4.1 or 3.3 clients.

• Intradomain communications through a firewall to or from HP Output Server 3.3 are not supported. HP Output Server 3.3 does not support firewalls.

Supported SAP installations with HP Output Manager for SAP, Version 3.5

HP Output Manager for SAP 3.5 is supported with all SAP-supported versions of SAP R/3 that function with the BC-XOM and/or BC-CON interface. HP Output Server 3.5 with HP Output Manager for SAP 3.5 is tested with SAP R/3 Enterprise (4.7) and SAP ECC 5.0.

For HP Output Manager for SAP 3.5 to function properly with SAP R/3 4.6, the minimum required BASIS Support Package Level is 48. For 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 the latest service pack that may be available for HP Output Server 3.5 for updates to required or recommended SAP patch levels.

NOTE: The installation and upgrade scripts for HP Output Server 3.5 do not check for an existing SAP installation.

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.

HP Output Server



HP supports the following HP Output Server configurations:

• a single HP Output Server domain installed on a single host

• a 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 29.

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 29.

For assistance with creating multiple HP Output Server domains, contact Customer Support or your Professional 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 29.

21


Installation and configuration overview

Installation and configuration overview

22

This section identifies the tasks you must perform to install and configure HP Output Server 3.5 with HP Output Manager for SAP 3.5 and HP Output Distributor 3.5. If you are upgrading to HP Output Server 3.5, see Chapter 4, “Upgrading HP Output Server” on page 63 for information about the upgrade process, including prerequisites.

To install and configure HP Output Server 3.5 with HP Output Manager for SAP 3.5 and HP Output Distributor 3.5, perform the following tasks:

1. Install the most recent version of MySQL for HP Output Management that is compatible with HP Output Server 3.5. See the Installation and Configuration Guide and the Release Notes for MySQL for HP Output Management.

2. Install HP Output Server 3.5. For more information, see Chapter 2, “Installing HP Output Server” on page 29.

3. Configure HP Output Server permissions and a test delivery pathway. See Chapter 6, “Configuring HP Output Server” on page 107.

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 3.5” on page 56.

2. Configure the CPIC user and HP Output Manager for SAP interfaces using the instructions in the System Administrator’s 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 3.5” on page 57.

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 Administrator’s Guide for HP Output Distributor.

3. Create delivery pathways using the information in the System Administrator’s 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.


HP Output Server


Pre-installation checklists

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 Administrator’s Guide for HP Output Distributor.

5. Create report definitions and sets using information in the System Administrator’s Guide for HP Output Distributor.

The following checklist outlines the information that you need to install HP Output Server. For information about prerequisites for upgrading HP Output Server, see Chapter 4, “Upgrading HP Output Server” on page 63.
• 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?

Setting permissions
Before you install HP Output Server, you must have the permissions described in the following sections.
23



UNIX hosts

24

If you are installing HP Output Server on a UNIX system, consider the following requirements:

• Can you log in as root to the hosts on which you plan to install and configure HP Output Server?

• Do you have a login account? The servers in HP Output Server use the dazel login account as the default account.

NOTE: Use the default dazel login account. Using a different login account may create interoperability conflicts with other HP Output Management applications.

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?

• The Windows server user varies by the language setting as indicated by the following table.

Table 1-8. Windows server user by language

Language Directory

English/Spanish nt authority\system

French autorite nt\systems

German nt-autoritäte\system



Planning an installation on a network

Installing on a non-English version of Windows

HP Output Server

To install HP Output Server on a non-English version of Windows, make sure you have installed the appropriate non-English version of the operating system before you begin installing HP Output Server.

For example, to run HP Output Server on a system that supports French, ensure you have installed the French version of Windows before you begin the installation.

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. The following topics are addressed:
• device requirements

• connecting devices

• naming conventions

For more information, see the System Administrator’s Guide for HP Output Server, or consult Professional Services.

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, complete the following tasks:
• Attend HP Output Server training

• Read the System Administrator’s Guide for HP Output Server

• Discuss your configuration plan with a consultant from Professional 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.

25

26



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:
• 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.

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 servers, logical destinations, physical destinations, or queues:

• uppercase or lowercase letters (A through Z or a through z)

• numbers (0 through 9)

• the period (.) character

• the underscore character (_)


HP Output Server



• the dash character (-)

The following restrictions apply to naming objects:

• Do not begin server, queue, or destination names with the dash character (-). If the server or queue name contains an invalid character, such as a space or quotation marks in any position, the server can either behave unpredictably or fail to run.

• 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

• 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 department’s printer

27

28




Chapter 2

Installing HP Output Server

HP Output Server

This chapter describes how to install HP Output Server 3.5 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 107 to configure and test the installation. Check the Customer Support Web site at http://www.itrc.hp.com for patch updates.

NOTE: To upgrade an existing installation of HP Output Server, use the instructions in Chapter 4, “Upgrading HP Output Server” on page 63.

Installation options
On a UNIX host, you can install HP Output Server as a server installation or as a client-only installation. On a Windows host, you can install HP Output Server as a server installation only. This section describes these options.
29

http://www.itrc.hp.com

30

Chapter 2 Installing HP Output Server

Installation options

The following configuration options are available when you install HP Output Server:

• Create a default set of servers. This option creates an HP Output Server domain. 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.

For UNIX instructions, see “Before you install on a UNIX host” on page 32 and “Creating a default set of servers on a UNIX host” on page 33.

For Windows instructions, see “Before you install on a Windows host” on page 46 and “Creating a set of default servers on a Windows host” on page 47.

• Join an existing domain. This option configures a new HP Output Server host and joins it to an existing HP Output Server domain. This option does not create any servers on the new host. Use this option to distribute HP Output Server delivery servers among multiple hosts. Note the following for this option:

- If you choose to configure the MySQL connection after installation, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

- 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 Administrator’s Command Reference for HP Output Server.

For UNIX instructions, see “Before you install on a UNIX host” on page 32 and “Joining an existing domain on a UNIX host” on page 39.

For Windows instructions, see “Before you install on a Windows host” on page 46 and “Joining an existing domain on a Windows host” on page 52.

• 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 MySQL connection after installation, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

- After you complete the installation, you must manually configure servers with the config_server command. For more information about using the config_server command, see the System Administrator’s Command Reference for HP Output Server.


HP Output Server


Assumptions and restrictions

For UNIX instructions, see “Before you install on a UNIX host” on page 32 and “Creating a new domain on a UNIX host” on page 41.

For Windows instructions, see “Before you install on a Windows host” on page 46 and “Creating a set of default servers on a Windows host” on page 47.

• Client-only installation (UNIX only). This 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.

For instructions, see “Creating a client-only installation (UNIX host only)” on page 43.

HP Output Server 3.5 integrates the installation of HP Output Manager for SAP 3.5 and HP Output Distributor 3.5. When you install a server installation of HP Output Server 3.5, the software for HP Output Manager for SAP 3.5 and HP Output Distributor 3.5 installs automatically.
The following assumptions and restrictions apply to implementing HP Output Server 3.5:

• These instructions refer to the location of your HP Output Server installation hierarchy as installDir. Substitute the correct path name for your installation when you see the installDir variable.

• Two different instances of HP Output Server with identical domain names and ports cannot share a common MySQL database 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 3.5” on page 56 and “Completing the installation of HP Output Distributor 3.5” on page 57.

31


Installing on UNIX hosts


32

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 and the Release Notes and that you are familiar with the system requirements and supported configurations. For information about installing HP Output Server on a Windows host, see “Installing on Windows hosts” on page 46.

Before you install on a UNIX host
To successfully create a default set of HP Output Server servers, you must first install MySQL for HP Output Management. The MySQL server must be running in your environment prior to installing a server installation of HP Output Server. HP Output Server 3.5 is supported with MySQL for HP Output Management, Version 4.1.12 or greater. For more information, see the Installation and Configuration Guide and the Release Notes for the most recent release of MySQL for HP Output Management and the Release Notes for the most recent service pack for HP Output Server 3.5.
When you install HP Output Server on a UNIX host, you use the setup.pl script that is located on the product CD-ROM. This script prepares your host machine and installs the software. The setup.pl script prompts you for the following information about your MySQL installation:

• user name of the MySQL administrator

• administrative password (if set for your MySQL installation)

• MySQL connection mode, which is one of the following:

- If MySQL is installed on this host, this is the path to the MySQL file socket.

- If MySQL is installed on another host, this is the port number that MySQL is listening on and the host name of the MySQL host.

After you enter this information, the setup script checks to see if the MySQL server is running. If you are creating a set of default servers and the MySQL server is not running, the setup script prompts you for the MySQL connection information until a connection is established.


HP Output Server



If you install HP Output Server by joining an existing domain, or by creating a new domain, you can configure the MySQL connection during the installation process or after installing HP Output Server. If you configure the MySQL connection during the installation process, the setup script returns an error if the MySQL server is not running, but allows you to continue with the installation.

NOTE: If you choose to configure the MySQL connection after joining an existing domain or creating a new domain, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

To create a server installation of HP Output Server on a UNIX host, choose a server installation option and use the corresponding instructions in one of the following sections:

• “Creating a default set of servers on a UNIX host” (the following section)

• “Joining an existing domain on a UNIX host” on page 39

• “Creating a new domain on a UNIX host” on page 41

To create a client-only installation of HP Output Server, use the instructions in the section titled “Creating a client-only installation (UNIX host only)” on page 43.

NOTE: The installation instructions in this section show how to use setup.pl in interactive mode (with prompts). You can use setup.pl in non-interactive mode (without prompts) to install HP Output Server by running setup.pl at the command line with arguments. For more information, see Appendix B, “Using setup.pl in Non-interactive Mode” on page 143.

Creating a default set of servers on a UNIX host
This configuration option creates an HP Output Server domain. It configures the host machine and creates all primary servers (NM, PM, AIM, CM, and EM) and one of each delivery server (DLM, JQM, and DSM).
Creating a server installation of HP Output Server includes the following tasks:

1. specifying a directory location and an owner of the installed files

2. configuring the host machine

33

34



3. configuring the MySQL connection

4. configuring advanced server options (optional)

5. reviewing the configuration settings

Use the following instructions to complete these tasks.

Task 1: Specifying a directory location and file owner
1. Log in as the root user.
2. Mount the product CD-ROM. For further instructions, see Appendix A, “Mounting a Product CD-ROM on UNIX Systems” on page 139.

3. Change directories to the location of the setup.pl installation script. For example, to change to the aix directory, type the following command:

cd /cdrom/aix

4. Run the installation script by typing the following command:

./perl ./setup.pl

5. The following configuration options appear. If the setup script does not detect an existing HP Output Server installation, the default selection is 1. If the setup script detects an existing HP Output Server installation, the default option is either uninstall (3) or upgrade (4), depending on the existing installation. For more information, see Chapter 3, “Uninstalling HP Output Server” on page 59 and Chapter 4, “Upgrading HP Output Server” on page 63.

1. Install HP Output Server.2. Install HP Output Server client only.3. Uninstall HP Output Server.4. Upgrade existing HP Output Server installation.

Accept the default or type 1.

6. When prompted for the installation path, accept the default or type a new installation directory. The default installation path is /opt/hpom. If the installation directory does not exist, the setup script prompts you to allow it to create one for you. If the installation directory exists and is not empty, except for the presence of installDir/var, the setup script warns of the existing files and prompts for a decision to continue or exit.

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. The file path cannot contain embedded spaces, tabs, or any of the following characters: * ? ‘ “ '


HP Output Server



7. When prompted for the name of the user who will own the installed files, accept the default, or type 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. The default user is dazel.

8. When prompted to create a set of servers or join an existing domain, accept the default (1).

Task 2: Configuring the host machine
1. When prompted for the name of the HP Output Server domain, accept the default or
type the domain name. The domain name is not the same as the network domain name. The default domain name is hostname.d.

Use the following rules when specifying an HP Output Server domain name:

- 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 ( . )

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.

2. When prompted for the port number on which the HP Output Server Name Space Manager (NM) will listen, accept the default or type a port number. The default is 4009.

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 step 7 on page 34. You can select a port number in the range 1024 through 65535 if you specified any user as the owner of the installed files.

35



Task 3: Configuring the MySQL connection

36

1. When prompted for the MySQL administrator user name, accept the default or type the name. The default is dazel.

The MySQL administrator user name can contain only simple ASCII characters and must not exceed 32 characters. Do not use accented characters, single or double quotes, spaces, backslashes, back tics, commas, or special symbols.

2. When prompted for a MySQL administrator password, do one of the following:

- If your MySQL installation has an administrator password, accept the default. The default is y.

When prompted for the password, type the password. The setup script does not provide a default value.

NOTE: The password can contain only simple ASCII characters and must not exceed 32 characters. Do not use accented characters, single or double quotes, spaces, backslashes, back tics, commas, or special symbols.

When prompted to verify the password, retype it.

- If your MySQL installation does not have an administrator password, type n.

3. When prompted to choose the MySQL connection mode that HP Output Server will use to connect to your MySQL server, do one of the following:

- If your MySQL server is installed on this host, accept the default (1).

When prompted for the path to the MySQL file socket, accept the default or type the absolute path. The default is installDir/var/mysql/mysql.sock. If you are connecting to a MySQL server on the local host, you must use the file socket.

- If your MySQL server is installed on another host, type 2.

When prompted for the port number that MySQL is listening on, accept the default or type the port number. The default is 3306.

When prompted for the host name where MySQL is running, type the name of the host. The setup script does not provide a default value.




Task 4: Configuring advanced server options

HP Output Server

The setup script enables you to configure HP Output Server to restrict communication between its servers to specific ports and to specify that HP Output Server servers use a specific network interface. For more information about these options, see Appendix E, “Firewall Support” on page 165 and Appendix F, “HP Output Server in a Multi-NIC Environment” on page 169.

When prompted to configure these advanced server options, do one of the following:

• To skip this step, accept the default (n).

Proceed with the installation using the instructions in “Task 5: Reviewing the configuration settings” on page 38.

• To configure advanced server options, type y.

Proceed with the installation using the instructions in the following section titled “Configuring firewall support.”

Configuring firewall supportWhen prompted to enable firewall support, do one of the following:


Proceed with the installation using the instructions in the following section titled “Specifying a network interface.”

• To enable firewall support, type y.

When prompted for a list of port numbers or ranges of port numbers for firewall support, type the port numbers separated by commas, or ranges of port numbers separated by dashes. Only numeric characters, the comma, and the dash characters are allowed. For example:

4000-4100,4102,4104-4199

You can specify one or more port numbers in the range 1 through 1023 only if you specified root as the owner of the installed files in step 7 on page 35. You can select one or more port numbers in the range 1024 through 65535 if you specified any user as the owner of the installed files.

Because each HP Output Server server requires a minimum of one port, you must enter at least eight port numbers. The setup program does not provide default values and does not check the ports that you specify for availability.

37

38



Specifying a network interfaceWhen prompted to restrict HP Output Server processes to use a specific network interface, do one of the following:


Proceed with the installation using the instructions in the following section titled “Task 5: Reviewing the configuration settings.”

• To restrict HP Output Server processes to use a specific network interface, type y.

When prompted for the host name or IP address of the network interface, type the host name or IP address.

Task 5: Reviewing the configuration settings
1. When prompted to allow the setup script to start the HP Output Server servers when
the installation is finished, do one of the following:

- 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, type n.

2. 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). Do one of the following:

- If the settings are correct, accept the default (y).

- If the settings are not correct, type n.

The setup script returns to the beginning of the program and displays your current selection for each prompt. When prompted, change any setting that is incorrect.

The setup script displays setup progress and notifies you when the installation is complete. If the installation was successful, the following messages appear:

HP Output Server 3.5 server successfully installed and configured.

The log file is located in installDir/var/log/setupos.log

If the installation was unsuccessful, see the log file located at /tmp/setupos.log.


HP Output Server



3. Source your environment variables before proceeding. Depending on your shell, source the environment variables by typing one of the following commands:

Shell Command

C source installDir/etc/setup_env.csh

Bourne or Korn . installDir/etc/setup_env.sh

Joining an existing domain on a UNIX host
Joining an existing domain is an installation option that joins a 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 through an existing HP Output Server domain.
Joining an existing domain includes the same tasks as creating a server installation of HP Output Server (see “Creating a default set of servers on a UNIX host” on page 33) with the following exceptions:

• When specifying information to configure the host machine, you specify an existing HP Output Server domain. The setup script configures the host to join the existing domain, but does not create any HP Output Server servers.

• You can configure the MySQL connection during the installation process or after completing the installation. If you configure the MySQL connection during the installation process, the setup script returns an error if your MySQL server is not running, but allows you to continue with the installation process.


Task 1: Specifying a directory location and file owner (join a domain)
1. Specify a directory location and file owner for your HP Output Server installation
by completing steps 1 through 7 in the section titled “Task 1: Specifying a directory location and file owner” on page 34.

2. When prompted to create a set of servers or join an existing domain, type 2.

3. When prompted to join an HP Output Server domain or create a new domain, accept the default. The default is 1 (join a domain).

39



Task 2: Configuring the host machine (join a domain)

40

1. When prompted for the HP Output Server host name, type 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 on which the NM server in the existing HP Output Server domain is listening. The setup script does not provide a default value.

2. When prompted for the HP Output Server domain name, type the HP Output Server domain name of the primary host. The setup script does not provide a default value.

3. When prompted for the port number that the HP Output Server NM is listening on, accept the default or type the port number. The default is 4009.

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.

Task 3: Configuring the MySQL connection (join a domain)
When prompted to configure the MySQL connection, do one of the following:
• To configure the MySQL connection, accept the default (y) and then configure the MySQL connection using steps 1 through 3 in the “Task 3: Configuring the MySQL connection” on page 36.

• To skip this step, type n.

NOTE: If you skip this step, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

Task 4: Configuring advanced server options (join a domain)
To configure HP Output Server to restrict communication between its servers to specific ports or to specify that HP Output Server servers use a specific network interface, perform the steps in “Task 4: Configuring advanced server options” on page 37.



Task 5: Reviewing the configuration settings (join a domain)

HP Output Server

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). The setup script does not provide a default value. Complete the installation using step in “Task 5: Reviewing the configuration settings” on page 38.

Post-installation reminders (join a domain)
After you complete the installation process, remember to do the following:
• If you did not configure the MySQL connection when installing HP Output Server by joining an existing domain, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

• 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 Administrator’s Command Reference for HP Output Server.

Creating a new domain on a UNIX host
Creating a new domain is an installation option in which the setup script 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 Administrator’s Command Reference for HP Output Server.
Creating a new domain includes the same five tasks as creating a server installation of HP Output Server (see “Creating a default set of servers on a UNIX host” on page 33) with the following exceptions:

• 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.

• You can configure the MySQL connection during the installation process or after completing the installation. If you configure the MySQL connection during the installation process, the setup script returns an error if your MySQL server is not running, but allows you to continue with the installation process.


41



Task 1: Specifying a directory location and a file owner (new domain)

42

1. Specify a directory location and file owner for your HP Output Server installation by completing steps 1 through 7 in the section titled “Task 1: Specifying a directory location and file owner” on page 34.

2. When prompted to create a set of servers, type 2.

3. When prompted to join an HP Output Server domain or create a new domain, type 2.

Task 2: Configuring the host machine (new domain)
Configure the host machine by completing the steps in “Task 2: Configuring the host machine” on page 35.
Task 3: Configuring the MySQL connection (new domain)
When prompted to configure the MySQL connection, do one of the following:
• To configure the MySQL connection, accept the default (y) and then configure the MySQL connection using steps 1 through 3 in “Task 3: Configuring the MySQL connection” on page 36.

• To skip this step, type n.

NOTE: If you skip this step, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

Task 4: Configuring advanced server options (new domain)
To configure HP Output Server to restrict communication between its servers to specific ports or to specify that HP Output Server servers use a specific network interface, use the steps in “Task 4: Configuring advanced server options” on page 37.
Task 5: Reviewing the configuration settings (new domain)
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). The setup script does not provide a default value. Complete the installation using step in “Task 5: Reviewing the configuration settings” on page 38.



Post-installation reminders (new domain)

HP Output Server


• If you did not configure the MySQL connection when installing HP Output Server by creating a new domain, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

• 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 Administrator’s Command Reference for HP Output Server.

Creating 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.
Creating a client-only installation of HP Output Server includes the following tasks:

1. specifying a directory location and an owner of the installed files

2. specifying the existing HP Output Server domain and host


NOTE: You can create a client-only installation of HP Output Server on a UNIX host only.


Task 1: Specifying a directory location and a file owner (client-only)
2. Mount the product CD-ROM. For further instructions, see Appendix A, “Mounting a Product CD-ROM on UNIX Systems” on page 139.


cd /cdrom/aix


./perl ./setup.pl

43

44



5. You are prompted with the following options. If the setup script does not detect an existing HP Output Server installation, the default selection is (1). If the setup script detects an existing HP Output Server installation, the default option is either uninstall (3) or upgrade (4), depending on the existing installation.

1. Install HP Output Server.2. Install HP Output Server client only.3. Uninstall HP Output Server.4. Upgrade existing HP Output Server 3.3.

installation.

To install the HP Output Server client only, type 2.

6. When prompted for the installation path, accept the default or type a new installation directory. The default installation path is /opt/hpom. If the installation directory does not exist, the setup script prompts you to allow the script to create one for you.

The file path to the installation directory must be an absolute path that begins with the / character. The file path cannot contain embedded spaces, tabs, or any of the following characters: * ? ‘ " '

7. When prompted for the name of the user who will own the installed files, accept the default, or type 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. The default user is dazel.

Task 2: Specifying the domain and host (client-only)
1. When prompted for the HP Output Server host name, type the host name of the
primary host machine of the existing HP Output Server domain. The primary host machine is the machine on which the NM server in the existing HP Output Server domain is listening. The setup script does not provide a default value.

2. When prompted for the HP Output Server domain name, type the HP Output Server domain name of the primary host. The setup script does not provide a default value.

3. When prompted for the port number that the HP Output Server NM is listening on, accept the default or type the port number. The default is 4009.

Task 3: Reviewing the configuration settings (client-only)
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). To complete your installation, use the following steps:
1. Do one of the following:


HP Output Server



- If the settings are correct, type y.

- If the settings are not correct, type n.

The setup script returns to the beginning of the program and displays your current selection for each prompt. When prompted, change any setting that is incorrect.

The setup script displays setup progress and notifies you when the installation is complete. If the installation was successful the following message appears:

HP Output Server 3.5 client successfully installed and configured.

The log file is located in installDir/var/log/setupos.log

If the installation was unsuccessful, the log file is located at /tmp/setupos.log.

2. Source your environment variables before proceeding. Depending on your shell, source the environment variables by typing one of the following commands:

Shell Command



45


Installing on Windows hosts


46

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 for installing HP Output Server. For information about installing HP Output Server on a UNIX host, see “Installing on UNIX hosts” on page 32.

Before you install on a Windows host
To successfully install a default set of HP Output Server servers, you must first install MySQL for HP Output Management. The MySQL server must be running in your environment prior to installing HP Output Server. HP Output Server 3.5 is supported with MySQL for HP Output Management, Version 4.1.12 or greater. For more information, see the Installation and Configuration Guide and the Release Notes for the most recent release of MySQL for HP Output Management and the Release Notes for the most recent service pack for HP Output Server 3.5.
When you install HP Output Server on a Windows host, you use the Setup program that is located on the product CD-ROM. This program prepares your host machine and installs the software. The Setup program prompts you for the following information about your MySQL installation:

• user name of the MySQL administrator

• administrative password (if set for your MySQL installation)

• MySQL host name

• port number on which MySQL is listening

After you enter this information, the Setup program checks to see if the MySQL server is running. If you are installing a default set of HP Output Server server and the MySQL server is not running, the Setup program prompts you for the MySQL information


HP Output Server



again. If you are installing HP Output Server by joining an existing domain or by creating a new domain and the MySQL server is not running, the Setup program displays a warning, but allows you to continue with the installation.

NOTE: If you choose to configure the MySQL connection after joining an existing domain or creating a new domain, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

To create a server installation of HP Output Server on a Windows host, choose a server installation option and use the corresponding instructions in one of the following sections:

• “Creating a set of default servers on a Windows host” on page 47

• “Joining an existing domain on a Windows host” on page 52

• “Creating a new domain without a default set of servers on a Windows host” on page 54

Creating a set of default servers on a Windows host
This option creates an HP Output Server domain on a Windows host. 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).
Creating a set of default HP Output Server servers on a Windows host includes the following tasks:

1. specifying a directory location

2. configuring the host machine

3. configuring the MySQL connection

4. configuring advanced server options (optional)


6. verifying that the SSM is running


47



Task 1: Specifying a directory location

48

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 23.

2. Insert the product CD-ROM in the local CD-ROM drive. The Setup program starts.

NOTE: If the Setup program does not start automatically, use Windows Explorer to locate the win32 folder on the CD-ROM. Open the folder and double-click Setup.exe.

3. When the Welcome screen of the HP Output Server Setup Wizard appears, click Next.

4. In the Destination Location dialog box specify the destination folder for installing HP Output Server by doing one of the following:

- Click Next to accept the default. The default destination folder is C:\HP\OM.

- Click Browse to choose a folder and then click Next.

NOTE: The file path to the destination folder cannot contain embedded spaces, tabs, or any of the following characters: * ? ‘ “ '%For example, you cannot install HP Output Server in C:\Program Files.

5. In the Configuration Options dialog box, accept the default, Yes (create a set of default servers), by clicking Next.

Task 2: Configuring the host machine
1. In the Host Configuration Options dialog box, accept the default domain name or
type the domain name for your HP Output Server installation in the Domain box.

The HP Output Server domain name is not the same as the network domain. The default domain name is hostname.d, where hostname is the name of this host machine.

If you specify a domain name other than the default name, the name must conform to the following rules:

- The first character must be a letter (a through z or A through Z).


HP Output Server



- After the first character, domain names can contain any combination of the following:

letters (a through z or A through Z)

dashes ( - )

underscores ( _ )

periods ( . )

numbers (0 through 9)

- 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.

2. In the NM Port box, accept the default port number or type the port number on which the Name Space Manager (NM) will listen. The default is 4009.

3. Click Next.

4. In the Server State Configuration dialog box select either Running (the default) or Stopped when prompted to have the HP Output Server servers running or stopped when setup is complete, and then click Next.

Task 3: Configuring the MySQL connection
1. In the MySQL Administrator User and Password dialog box, type the MySQL
administrator user name in the User Name box. The default dazel is provided for the MySQL administrator user name.

NOTE: The MySQL administrator user name can contain only simple ASCII characters and must not exceed 32 characters. Do not use accented characters, single or double quotes, spaces, backslashes, back tics, commas, or special symbols.

49

50




- If your MySQL for HP Output Management installation has an administrator password, type the password in the Password box. Retype the password in the Confirm Password box, and then click Next.

NOTE: The MySQL password can contain only simple ASCII characters and must not exceed 32 characters. Do not use accented characters, single or double quotes, spaces, backslashes, back ticks, commas, or special symbols.

- If your MySQL for HP Output Management installation does not have an administrator password, leave the Password box blank and click Next.

3. In the MySQL Host Name and Port dialog box, do one of the following:

- To accept the defaults for the name of the MySQL host and the port number on which the MySQL server is listening, click Next. The default host name is localhost and the default port number is 3306.

- Type the name of the host on which MySQL is installed and the port number on which the MySQL server is listening. Click Next.

NOTE: If MySQL is installed on the same machine as HP Output Server, you must use localhost as the name of the host.

Task 4: Configuring advanced server options (optional)
The Setup program enables you to configure HP Output Server to restrict communication between its servers to specific ports and to specify that HP Output Server servers use a specific network interface. For more information about these options, see Appendix E, “Firewall Support” on page 165 and Appendix F, “HP Output Server in a Multi-NIC Environment” on page 169.
1. In the Advanced Server Configuration dialog box, do one of the following:

- If you do not want to configure advanced server options, click Next to accept the default (No). Proceed with the installation using the instructions in the “Task 5: Reviewing the configuration settings” on page 51.

- To configure advanced server options, click Yes, and then click Next.

2. In the Firewall Support dialog box, do one of the following:

- If you do not want to configure firewall support, click Next to accept the default (No), and then skip to step 4.


HP Output Server



- To configure firewall support, click Yes, and then click Next.

3. In the Firewall Ports dialog box, type the port numbers separated by commas, or ranges of port numbers separated by dashes, and then click Next.

Only numeric characters, the comma, and the dash characters are allowed. For example:

4000-4100,4102,4104-4199

Because each HP Output Server server requires a minimum of one port, you must enter at least eight port numbers. The Setup program does not provide default values and does not check the ports that you specify for availability.

4. In the Network Interface Support dialog box, do one of the following:

- If you do not want to restrict HP Output Server processes to use a specific network interface, click Next to accept the default (No). Proceed with the installation using the instructions in “Task 5: Reviewing the configuration settings” on page 51.

- To restrict HP Output Server processes to use a specific network interface, click Yes, and then click Next.

In the Network Interface dialog box, type the host name or IP address of the network interface, and then click Next. This value will also be used for the NM host name.

Task 5: Reviewing the configuration settings
1. In the Review Settings dialog box, review the settings that you have 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 dialog box, review the results of the configuration and click Next.

3. To exit the HP Output Server Setup Wizard, click Finish.

Task 6: Verifying that the SSM is running
1. Open the Services window of the Windows operating system.
2. Locate the Output Server Startup Manager (SSM) 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 SSM, to restart automatically whenever you reboot, change the mode to automatic under Startup Type.

51



Joining an existing domain on a Windows host

52

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 through 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 (see “Creating a set of default servers on a Windows host” on page 47) with the following exceptions:

• When you specify information to configure 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, see the System Administrator’s Command Reference for HP Output Server.

• You can configure the MySQL connection during the installation process or after completing the installation. If you configure the MySQL connection during the installation process, the Setup program displays a warning message if your MySQL server is not running, but allows you to continue with the installation process.


Task 1: Specifying a directory location (join a domain)
1. Specify a directory location for your HP Output Server installation by completing
steps 1 through 4 in “Task 1: Specifying a directory location” on page 48.

2. In the Configuration Options dialog box, click No (configure host options only), and then click Next.

3. In the Domain Options dialog box, click Join a domain, and then click Next.

Task 2: Configuring the host machine (join a domain)
1. In the Host Configuration Options dialog box, type the domain name for your HP
Output Server installation in the Domain box.

2. In the NM Host box, type the name of the Name Space Manager (NM) host in the existing domain.

3. Accept the default port number or type the port number on which the NM in the existing domain is listening. The default is 4009.


HP Output Server



4. Click Next.

Task 3: Configuring the MySQL connection (join a domain)
You can configure the MySQL connection during the installation process or after completing the installation. If you configure the MySQL connection during the installation process and your MySQL server is not running, the Setup program displays a warning, but allows you to continue with the installation process.
In the MySQL Connection Configuration dialog box, do one of the following:

• To configure the MySQL connection during the installation process, select Yes (recommended) and then perform the steps in “Task 3: Configuring the MySQL connection” on page 49.

• To skip these steps, select No and then click Next.

NOTE: If you choose to configure the MySQL connection after joining an existing domain, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

To configure HP Output Server to restrict communication between its servers to specific ports or to specify that HP Output Server servers use a specific network interface, use the steps in “Task 4: Configuring advanced server options (optional)” on page 50.
Task 5: Reviewing the configuration settings (join a domain)
To review the configuration settings and complete the installation process, complete the steps in “Task 5: Reviewing the configuration settings” on page 51.
Post-installation reminders (join a domain)
• If you did not configure the MySQL connection when installing HP Output Server by joining an existing domain, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

53

54



• 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, see the System Administrator’s Command Reference for HP Output Server.

NOTE: You must configure the SSM before configuring any delivery servers on the host that you are joining to the existing HP Output Server domain.

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, see the System Administrator’s Command Reference for HP Output Server.

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.

• You can configure the MySQL connection during the installation process or after completing the installation. If you configure the MySQL connection during the installation process and your MySQL server is not running, the Setup program displays a warning, but allows you to continue with the installation process.


Task 1: Specifying a directory location (new domain)
1. Specify a directory location for your HP Output Server installation by completing
steps 1 through 4 in “Task 1: Specifying a directory location” on page 48.

2. In the Configuration Options dialog box, click No (configure host options only), and then click Next.

3. In the Domain Options dialog box, click Create a new domain, and then click Next.




Task 2: Configuring the host machine (new domain)

HP Output Server

In the Host Configuration Options dialog box, do one of the following:

• To accept the default domain name and NM Port number, click Next. The default host name is hostname.d, where hostname is the name of this host.

• In the Domain box, type the domain name for your HP Output Server installation. In the NM Port box, type the port number on which the NM in the existing domain is listening. Then click Next.

Task 3: Configuring the MySQL connection (new domain)
You can configure the MySQL connection during the installation process or after completing the installation. If you configure the MySQL connection during the installation process, the Setup program displays a warning if your MySQL server is not running, but allows you to continue with the installation process.
In the MySQL Connection Configuration dialog box, do one of the following:

• To configure the MySQL connection during the installation process, select Yes (recommended) and then perform the steps in “Task 3: Configuring the MySQL connection” on page 49.

• To skip these steps, select No and then click Next.

NOTE: If you choose to configure the MySQL connection after joining an existing domain, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

To configure HP Output Server to restrict communication between its servers to specific ports or to specify that HP Output Server servers use a specific network interface, complete the steps in “Task 4: Configuring advanced server options (optional)” on page 50.
Task 5: Reviewing the configuration settings (new domain)
To review the configuration settings and complete the installation process, complete the steps in “Task 5: Reviewing the configuration settings” on page 51.
55


Completing the installation of HP Output Manager for SAP 3.5

Post-installation reminders (new domain)

56


• If you did not configure the MySQL connection when installing HP Output Server by creating a new domain, you must configure the MySQL connection before creating any HP Output Server servers. For more information, see Appendix G, “Configuring the MySQL Connection” on page 177.

• 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 Administrator’s Command Reference for HP Output Server.

Completing the installation of HP Output Manager for SAP 3.5

To complete the installation of HP Output Manager for SAP, you must perform the following additional installation tasks after installing a server installation of HP Output Server:

1. 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 3.5 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 3.5 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” on page 52.

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 3.5 installation configure the CPIC user and the HP Output Manager for SAP interfaces using the instructions in the System Administrator’s Guide for HP Output Manager for SAP.


HP Output Server


Completing the installation of HP Output Distributor 3.5

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.


If you are planning to use HP Output Distributor 3.5, you must complete additional installation or configuration tasks after installing 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 installDir/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 Administrator’s Guide for HP Output Distributor 3.5.

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 the setup program completes. For more information about running configod.pl, see Appendix J, “configod.pl Script” on page 187.
Uploading templates manually after creating a new domain
If you installed 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
57

58



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 J, “configod.pl Script” on page 187.

Configuring HP Output Distributor
To configure HP Output Distributor, use the System Administrator’s Guide for HP Output Distributor to complete the following tasks:
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 Administrator’s Guide for HP Output Distributor.


Chapter 3

Uninstalling HP Output Server

HP Output Server

This chapter guides you through the process of uninstalling HP Output Server on UNIX and Windows hosts. Consider the following as you plan the uninstallation:

• 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 3.5 uninstalls HP Output Manager for SAP 3.5 and HP Output Distributor 3.5.

• If MySQL for HP Output Management is installed in installDir/var/mysql, uninstalling HP Output Server removes all files and directories in installDir except for var and all files and directories in installDir/var except for mysql.

To uninstall MySQL for HP Output Management, see the Installation and Configuration Guide for MySQL for HP Output Management.

59

Chapter 3 Uninstalling HP Output Server

Uninstalling HP Output Server on a UNIX host


60

This section describes how to uninstall HP Output Server from a UNIX host. These instructions apply to both server and client installations of HP Output Server on a UNIX host.

NOTE: Do not use rm -rf to uninstall HP Output Server on a UNIX host. Using this method does not remove the databases from the MySQL server.

To uninstall HP Output Server on a UNIX host, complete the following steps:

1. Ensure that MySQL for HP Output Management and HP Output Server are running.


3. Depending on your shell, source the UNIX environment variables with one of the following commands:

4. 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 OpenView 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 applications 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, refer to the documentation for your HP Output Management applications.

Shell Command




HP Output Server



6. Run the HP Output Server setup.pl script as follows:

cd installDir/etc

perl ./setup.pl

You may also uninstall HP Output Server from the CD-ROM.

NOTE: These instructions show how to use setup.pl in interactive mode (with prompts) to uninstall HP Output Server. You can use setup.pl in non-interactive mode (without prompts) to uninstall HP Output Server by running setup.pl at the command line with arguments. For more information, see Appendix B, “Using setup.pl in Non-interactive Mode” on page 143.

7. At the prompt, accept the default installation directory or type the installation directory of your HP Output Server installation.

8. After the setup script displays a summary of the information you have typed and performs pre-uninstallation checks, you are prompted to start the uninstallation (y) or exit the uninstallation options (n).

NOTE: If you are uninstalling a client installation of HP Output Server, the summary information indicates that the setup script is ready to uninstall a client installation.

To start the uninstallation, type y.

The setup script displays progress. When the uninstallation is complete, the setup script displays a message similar to the following:

HP Output Server 3.5 successfully uninstalled. The log file is located in /tmp/uninstallos.log.

61


Uninstalling HP Output Server on a Windows host

Uninstalling HP Output Server on a Windows host

62

This section describes how to remove HP Output Server from a Windows host.

NOTE: You must remove all locally installed HP Output Management applications 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, complete the following steps:

1. Ensure that both MySQL for HP Output Management and HP Output Server are running.

2. Use the Add/Remove Programs feature of the Windows operating system to remove HP Output Server.

3. You may be prompted to restart your system. 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.


Chapter 4

Upgrading HP Output Server

HP Output Server

This chapter describes how to upgrade UNIX and Windows installations of HP Output Server, Versions 3.3 and 3.4.1 to HP Output Server 3.5.

CAUTION: Before upgrading, back up your installation of HP Output Server. Typically, the only method of recovering from a failed HP Output Server upgrade is restoring from a backup.

For information about backing up your HP Output Server 3.3 installation, see the Installing and Configuring manual for HP Output Server 3.3.

For information about backing up your HP Output Server 3.4.1 installation, see the technical note Backing up and Restoring HP Output Server, Version 3.4.1 at http://www.hp.com/united-states/outputmanagement/hpos341tn1enus.pdf.

For more information about troubleshooting a failed upgrade, see “Troubleshooting a failed upgrade” on page 86.

Integrated product upgrade and installation
When you upgrade a server installation of HP Output Server, existing installations of HP Output Manager for SAP 6.1 with Service Pack 05.2 or greater and HP Output Distributor 2.0 with Service Pack 04.3 or greater are upgraded to Version 3.5. If
63

http://www.hp.com/united-states/ outputmanagement/hpos341tn1enus.pdf

http://www.hp.com/united-states/ outputmanagement/hpos341tn1enus.pdf

64

Chapter 4 Upgrading HP Output Server

Upgrade effects on HP Output Server

installations of HP Output Manager for SAP 6.1 or HP Output Distributor 2.0 do not exist, the software for these products is installed when you upgrade a server installation of HP Output Server.

If you purchased a license for HP Output Manager for SAP 3.5, your HP Output Server installation includes a CD-ROM that contains documentation for configuring and using HP Output Manager for SAP 3.5. If you purchased a license for HP Output Distributor 3.5, your HP Output Server installation includes a CD-ROM that contains the documentation for configuring and using HP Output Distributor 3.5 and the software and documentation for installing and using HP Output Distributor Manager3.5.

CAUTION: HP Output Server 3.5 supports upgrading an existing HP Output Distributor 2.0 installation that is located in installDir only, where installDir is the location of your HP Output Server installation. If you have an existing installation of HP Output Distributor 2.0 that is not installed in installDir, contact your Professional Services representative for assistance. The upgrade process aborts if an existing installation of HP Output Distributor is not located in installDir.

Upgrade effects on HP Output Server
Upgrading HP Output Server 3.3 or HP Output Server 3.4.1 to Version 3.5 affects customizations and templates as follows:
• Customized DPAOIDs are preserved during an HP Output Server upgrade. The DPAOIDs database is also upgraded 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 Administrator’s Guide for HP Output Server 3.5.


HP Output Server


Upgrade effects on HP Output Manager for SAP

• Customizations made to the following are preserved:

- cover sheets

- hosts.equiv

- hosts.lpd

- printcap

• Files in installDir/nls/cfg are deleted and replaced.

• Files in installDir/custom are preserved.

• The unsupported directory, if it exists in installDir, is deleted. Files that were shipped in installDir/unsupported/examples are located in installDir/examples after an upgrade.

Upgrade effects on HP Output Manager for SAP
Upgrading to HP Output Server 3.5 has the following effects on an existing HP Output Manager for SAP 6.1 installation:
• The HP Output Manager for SAP version file located at installDir/etc/versions/dr3 is deleted, where installDir is the installation directory of your HP Output Server installation. The product version for HP Output Manager for SAP is determined by examining the version of HP Output Server 3.5 using the dzl_version command. A separate version specifically identified for HP Output Manager for SAP does not exist after upgrade. For more information about the dzl_version command, see the System Administrator’s Command Reference for HP Output Server 3.5.

• A symbolically linked installation of HP Output Manager for SAP is not supported with HP Output Server 3.5. Symbolic links to installed files are replaced with actual files during an upgrade.

• On a UNIX installation, the file ownership for HP Output Manager for SAP files is changed from bin:bin to the owner of the HP Output Server installed files.

• All user-customizable items are backed up prior to the upgrade process and restored after the upgrade is complete.

65

66


Upgrade effects on HP Output Distributor

• The following files are backed up in the HP Output Server custom directory:

- $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 referred to 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 upgrade completes.

Upgrade effects on HP Output Distributor
Upgrading to HP Output Server 3.5 has the following effects on an existing HP Output Distributor 2.0 installation:
• The HP Output Distributor version file located at installDir/etc/versions/OD is deleted, where installDir is the installation directory of your HP Output Server installation. The product version for HP Output Distributor is determined by examining the version of HP Output Server 3.5 using the dzl_version command. A separate version specifically identified for HP Output Distributor does not exist after upgrade. For more information about the dzl_version command, see the System Administrator’s Command Reference for HP Output Server 3.5.

• A symbolically linked installation of HP Output Distributor is not supported with HP Output Server 3.5. Symbolic links to installed files are replaced with actual files during an upgrade.

• On a UNIX installation, the file ownership for HP Output Distributor files is changed from bin:bin to the owner of the HP Output Server installed files.

• The location of the odconfig_server command is changed to installDir/bin.

• HP Output Distributor 3.5 with HP Output Server 3.5 relies on MySQL for HP Output Management for database management. The upgrade process migrates data from the HP Output Distributor 2.0 database to the MySQL for HP Output Management database. The HP Output Distributor odstart_server command for starting the HP Output Distributor 2.0 database server and the odstop_server commands for closing the HP Output Distributor 2.0 databases and the database server are deprecated after upgrading to HP Output Server 3.5. After upgrading your HP Output Server installation, use the native MySQL commands for starting and stopping the MySQL server. For more information


HP Output Server



about starting and stopping the MySQL server, see the Installation and Configuration Guide and the Release Notes for MySQL for HP Output Management.

NOTE: After an upgrade of an existing HP Output Distributor 2.0 installation, you can continue to use the HP Output Distributor odconfig_server command to create an HP Output Distributor database. New arguments are added to the command to enable you to create databases in MySQL for HP Output Management. For more information about using the odconfig_server command, see the System Administrator’s Guide for HP Output Distributor 3.5.

• All customizations made to HP Output Distributor 2.0 objects are preserved during data migration.

• Jobs that have been submitted, but not delivered at the time of upgrade, will be migrated to the MySQL for HP Output Management database.

The following assumptions and restrictions apply to upgrading HP Output Server to Version 3.5:
• If you are upgrading HP Output Server 3.3 and want to configure HP Output Server to use the multi-NIC and firewall support features, you must add these features manually after performing an upgrade. See Appendix E, “Firewall Support” on page 165 and Appendix F, “HP Output Server in a Multi-NIC Environment” on page 169.

• The instructions for upgrading HP Output Server refer to the location of your HP Output Server installation hierarchy as installDir. Substitute the correct path name for your installation when you see the installDir variable.

• On UNIX hosts, if any portion of the installDir/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 maps to the remote root user ID.

• On UNIX hosts, only the installDir/var directory or the installDir/var/jobdb directory may be mounted or linked to another file system.

• Two different instances of HP Output Server with identical domain names and ports cannot share a common MySQL database server.

67

68



• During an upgrade of a server installation of HP Output Server where HP Output Distributor 2.0 is installed, the setup program upgrades the existing templates for creating HP Output Distributor logical and physical destinations. If the setup program fails to update the templates, run the configod.pl script with the -u argument after the installation completes to upgrade the templates.

• HP Output Distributor relies on HP Output Server for delivery pathways and security. During an upgrade of a server installation of HP Output Server where an installation of HP Output Distributor does not exist, 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 CM and stores them in the installDir/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 the OD_ADMIN permissions template, see the System Administrator’s Guide for HP Output Distributor.

If the setup program fails to install the templates for HP Output Distributor when you upgrade a default server installation of HP Output Server, run the configod.pl script with the -i argument after the setup program completes. For more information about running configod.pl, see Appendix J, “configod.pl Script” on page 187.

If you upgrade a server installation of HP Output Server that does not have primary servers configured (for example, upgrade 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 manually and then run the configod.pl script with the -i argument. For more information about running configod.pl, see Appendix J, “configod.pl Script” on page 187.

To complete the configuration of HP Output Distributor, see the System Administrator’s Guide for HP Output Distributor.

• If an installation of HP Output Manager for SAP 6.1 with Service Pack 05.2 or greater does not exist with HP Output Server, the software for HP Output Manager for SAP 3.5 is installed, but not configured, when you upgrade a server installation


HP Output Server


Before you begin

of HP Output Server. To complete the installation of HP Output Manager for SAP 3.5, see “Completing the installation of HP Output Manager for SAP 3.5” on page 56.

Before you begin
This section describes prerequisite tasks and requirements for upgrading HP Output Server 3.3 and HP Output Server 3.4.1 to HP Output Server 3.5. This section assumes that you have read Chapter 1, “Planning the Installation” on page 1 and installed or upgraded to and configured MySQL for HP Output Management, Version 4.1.12 or the most recent version that is available and compatible with HP Output Server 3.5. For more information about installing and configuring MySQL for HP Output Management, see the Installation and Configuration Guide for MySQL for HP Output Management.
HP Output Server 3.3 and 3.4.1 upgrade prerequisites
HP Output Server 3.5 supports upgrades from HP Output Server 3.3 and HP Output Server 3.4.1. The following table describes the prerequisites for upgrading HP Output Server 3.3 and HP Output Server 3.4.1 to HP Output Server 3.5. Ensure that these prerequisites are met prior to upgrading HP Output Server.
Table 4-1. Prerequisites to upgrading HP Output Server 3.3 or 3.4.1

Prerequisite HP Output Server 3.3 HP Output Server 3.4.1

1. service pack level Your HP Output Server 3.3 installation must be at Version 3.3.0.13.0.3 (Service Pack 05.2) or greater prior to upgrading to HP Output Server 3.5.

Your HP Output Server 3.4.1 installation must be at Version 3.4.1.2.0.7 (Service Pack 05.2) or greater prior to upgrading to HP Output Server 3.5.

2. server configuration Your HP Output Server 3.3 server installation must have HP Output Server servers configured or a configured host. If you installed HP Output Server 3.3 using the none server configuration option on a UNIX host or the No Configuration option on a Windows host, ensure that you have configured servers using the config_server command or configured the host using the config_host command prior to upgrading to HP Output Server 3.5.

Ensure that your HP Output Server 3.4.1 server installation has configured HP Output Server servers or a configured host (the HostConfig.sgml file exists) prior to upgrading to HP Output Server 3.5.

69


Before you begin

3. data migration HP Output Server 3.5 replaces its proprietary database from HP Output Server 3.3 with MySQL for HP Output Management. During an upgrade, the setup program runs a data migration utility (dbupgrade) to migrate data from the HP Output Server 3.3 AIM, CM, DLM, EM, JQM, and PM databases to the MySQL database.

To facilitate successful data migration, HP recommends that you run the dbreorg.pl script on these servers in your HP Output Server 3.3 installation prior to performing an upgrade. The dbreorg.pl script is located in your HP Output Server 3.3 installation at installDir/unsupported/tools. If you have never used the dbreorg.pl script, or if you have not used it successfully, contact Customer Support for assistance before running the script.

Because the dbreorg.pl script was developed for HP Output Server’s database in versions prior to Version 3.4.1, this script does not work on HP Output Server 3.4.1 or greater.

For information about troubleshooting data migration, see “Troubleshooting a failed upgrade” on page 86.

Before you upgrade HP Output Server 3.4.1 to HP Output Server 3.5, you must be using MySQL for HP Output Management, Version 4.1.12 or the most recent version that is available and compatible with HP Output Server 3.5. The MySQL server must be running in your environment. For more information about installing MySQL for HP Output Management or upgrading from a previous version, see the Installation and Configuration Guide and the Release Notes for the latest release of MySQL for HP Output Management.

4. back up Before upgrading HP Output Server, back up your installation. The only method of recovering from a failed upgrade is restoring from a backup. For more information about backing up your HP Output Server 3.3 installation, see the Installing and Configuring manual for HP Output Server 3.3.

Before upgrading HP Output Server, back up your installation. Typically, the only method of recovering from a failed upgrade is restoring from a backup. For more information about backing up your HP Output Server 3.4.1 installation, see the technical note Backing up and Restoring HP Output Server, Version 3.4.1, which is located at http://www.hp.com/united-states/outputmanagement/hpos341tn1enus.pdf

Table 4-1. Prerequisites to upgrading HP Output Server 3.3 or 3.4.1 (continued)



http://www.hp.com/united-states/outputmanagement/hpos341tn1enus.pdf


Before you begin

5. active jobs in queues If you upgrade when 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 upgrade 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 Administrator’s Guide for HP Output Server.

6. processes or scripts using Perl

Ensure that no other processes or scripts are using Perl in the installDir/bin directory when you perform the upgrade.

7. disk space Upgrading HP Output Server 3.3 to Version 3.5 requires more disk space than a full installation. For more information, see “System requirements” on page 5.



HP Output Server 71


Before you begin

8. database replacement HP Output Server 3.5 replaces its proprietary database from HP Output Server 3.3 with MySQL. Before upgrading HP Output Server 3.3 to HP Output Server 3.5, you must install MySQL for HP Output Management, Version 4.1.12 or the most recent version that is available and compatible with HP Output Server 3.5. The MySQL server must be running in your environment. For more information, see the Installation and Configuration Guide and the Release Notes for MySQL for HP Output Management.

When you upgrade HP Output Server 3.3, the setup program prompts you for the following information about your MySQL installation:

• user name of the MySQL administrator• administrative password • MySQL connection mode, which is

one of the following: On UNIX: the path to the MySQL file socket (if MySQL is installed on this host) or the port number that MySQL is listening on and the host name of the MySQL host (if MySQL is installed on another host)On Windows: the port number that MySQL is listening on and the host name of the MySQL host.

After you enter this information, the upgrade program checks to see if the MySQL server is running. If the MySQL server is not running, the upgrade program returns an error (on a UNIX host) or exits (on a Windows host) and does not allow you to proceed.

Before upgrading HP Output Server 3.4.1 to HP Output Server 3.5, you must be using MySQL for HP Output Management, Version 4.1.12 or the most recent version that is available and compatible with HP Output Server 3.5. The MySQL server must be running in your environment.

For more information about installing or upgrading MySQL for HP Output Management from a previous version, see the Installation and Configuration Guide and the Release Notes for the latest release of MySQL for HP Output Management.

9. upgrade order When upgrading a multi-host HP Output Server domain, upgrade the host containing the primary servers prior to upgrading any other hosts. Upgrade all servers in a multi-host domain. Upgrade client installations of HP Output Server after upgrading the servers.





Before you begin

HP Output Manager for SAP 6.1 upgrade prerequisites

HP Output Server

The following table describes prerequisites for upgrading HP Output Manager for SAP 6.1 to HP Output Manager for SAP 3.5. If you have an existing installation of HP Output Manager for SAP 6.1, ensure that the following prerequisites are met prior to upgrading HP Output Server.

Table 4-2. Prerequisites to upgrading HP Output Manager for SAP 6.1

Prerequisite Description

1. service pack level Your HP Output Manager for SAP 6.1 installation must be at Version 6.1.0.15.0.3 (Service Pack 05.2) or greater prior to upgrading to HP Output Server 3.5.

2. back up Prior to upgrading HP Output Server, back up your installation. Backing up HP Output Server automatically backs up HP Output Manager for SAP 6.1. For more information about backing up your HP Output Server 3.3 installation, see the Installing and Configuring manual for HP Output Server 3.3. For more information about backing up your HP Output Server 3.4.1 installation, see the technical note Backing up and Restoring HP Output Server, Version 3.4.1, which is located at http://www.hp.com/united-states/outputmanagement/hpos341tn1enus.pdf

3. active jobs If you upgrade when 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 upgrade process, do not use the pdpause command to pause the queues. Using pdpause instead of pdset will cause queued jobs to fail.

4. upgrade order Both new installations and upgrades to HP Output Server 3.5 introduce enhanced job event reporting features for HP Output Manager for SAP. If you plan to use these new features and you are upgrading an existing installation of HP Output Manager for SAP 6.1, you must upgrade your OMS callback servers first, then upgrade all client installations of HP Output Manager for SAP prior to enabling the enhanced job event reporting features.

For more information about enhanced job event reporting for HP Output Manager for SAP, see the System Administrator’s Guide for HP Output Manager for SAP 3.5.

73



Before you begin

HP Output Distributor 2.0 upgrade prerequisites

5. supported SAP versions HP Output Manager for SAP 3.5 is supported with all SAP-supported versions of SAP R/3 that function with the BC-XOM and/or BC-CON interface. HP Output Server 3.5 with HP Output Manager for SAP 3.5 is tested with SAP R/3 Enterprise (4.7) and SAP ECC 5.0.

For HP Output Manager for SAP 3.5 to function properly with SAP R/3 4.6, the minimum required BASIS Support Package Level is 48. For 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 the latest service pack that may be available for HP Output Server 3.5 for updates to required or recommended SAP patch levels.

The upgrade script for HP Output Server 3.5 does not check for an existing SAP installation.

Table 4-2. Prerequisites to upgrading HP Output Manager for SAP 6.1 (continued)


74

The following table describes prerequisites for upgrading HP Output Distributor 2.0 to HP Output Distributor 3.5. If you have an existing installation of HP Output Distributor 2.0, ensure that the following prerequisites are met prior to upgrading HP Output Server.

Table 4-3. Prerequisites to upgrading HP Output Distributor 2.0


1. service pack level Your HP Output Distributor 2.0 installation must be at Version 2.0.0.12.0.2 (Service Pack 04.3) or greater prior to upgrading to HP Output Server 3.5.

2. database replacement During an upgrade, data from the HP Output Distributor 2.0 database is migrated to the MySQL for HP Output Management installation that you are using for HP Output Server 3.5. During an upgrade, the hpod_dmutil.pl data migration utility migrates HP Output Distributor 2.0 data to MySQL for HP Output Management. If data migration fails, you must correct the problem that caused the failure and run the data migration utility manually. For more information, see “Troubleshooting a failed upgrade” on page 86.

3. location of installation directory

HP Output Server 3.5 supports upgrading an existing HP Output Distributor 2.0 installation that is located in installDir only, where installDir is the location of your HP Output Server installation. If you have an existing installation of HP Output Distributor 2.0 that is not installed in installDir, contact your Professional Services representative for assistance. The upgrade process aborts if an existing installation of HP Output Distributor is not located in installDir.



Before you begin

Upgrading a multi-host domain

4. back up Prior to upgrading HP Output Server, back up your installation. Backing up HP Output Server, where HP Output Distributor is installed in installDir (and installDir is the location of your HP Output Server installation), automatically backs up HP Output Distributor. For more information about backing up your HP Output Server 3.3 installation, see the Installing and Configuring manual for HP Output Server 3.3. For more information about backing up your HP Output Server 3.4.1 installation, see the technical note Backing up and Restoring HP Output Server, Version 3.4.1, which is located at http://www.hp.com/united-states/outputmanagement/hpos341tn1enus.pdf

Table 4-3. Prerequisites to upgrading HP Output Distributor 2.0 (continued)


HP Output Server

If you are upgrading a multi-host HP Output Server domain to Version 3.5, you must upgrade the host running the primary servers prior to upgrading the servers of all other hosts.

NOTE: Upgrade server installations of HP Output Server on a UNIX host before upgrading client installations.

To upgrade a multi-host HP Output Server domain to Version 3.5, perform the following steps:

1. Stop all of the delivery servers on the machine where the NM resides.

2. Stop all of the servers on all of the remaining machines.

3. Upgrade the host running the primary servers using the upgrade steps in the following sections in this chapter as appropriate to your platform. Ensure that the primary servers are running after the upgrade.

4. Upgrade the servers of all other hosts using the upgrade steps in the following sections in this chapter as appropriate to your platform. Ensure that all servers are running on all machines after the upgrade.

CAUTION: Failure to follow these steps may result in a loss of jobs or other errors.

75



Upgrading HP Output Server on a UNIX host


76

This section describes how to upgrade HP Output Server 3.3 and 3.4.1 to HP Output Server 3.5 on a UNIX host. This section assumes that you have read the section “Before you begin” on page 69. To upgrade a client HP Output Server, see “Upgrading an HP Output Server client installation (UNIX only)” on page 80.


Upgrading an HP Output Server server installation on a UNIX host
To upgrade a server installation of HP Output Server, Version 3.3 or 3.4.1 to HP Output Server 3.5 on a UNIX host, perform the following steps:
1. Log in as root on your machine.

2. Create a backup of your current HP Output Server installation for every host. For more information, see the installation and configuration manual for the version of HP Output Server that you are upgrading.


4. Stop all programs that monitor the HP Output Server server you want to upgrade. On multiple-domain hosts, some programs may be monitoring processes that are managed by other HP Output Server instances.

For example, the HP OpenView Operations and dzl_epod programs monitor HP Output Server processes and should be stopped before you start the setup.pl script.

NOTE: Monitor programs are not restarted automatically; you must restart these programs manually.

Shell Command




HP Output Server



5. Stop all HP Output Management applications that depend on the HP Output Server installation. 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, refer to the documentation for your HP Output Management applications.

6. Mount the CD-ROM file system as described in Appendix A, “Mounting a Product CD-ROM on UNIX Systems” on page 139.

NOTE: You must log in as root to mount CD-ROM file systems. Some operating systems, such as Solaris, automount CD-ROM file systems.


cd /cdrom/aix


./perl ./setup.pl

NOTE: These instructions show how to use setup.pl in interactive mode (with prompts) to upgrade to HP Output Server 3.5. You can use setup.pl in non-interactive mode (without prompts) to upgrade to HP Output Server 3.5 by running setup.pl at the command line with arguments. For more information, see Appendix B, “Using setup.pl in Non-interactive Mode” on page 143.

If the setup script detects an existing installation of HP Output Server, it displays the installation path, domain name, NM host name, and the NM port number of the existing HP Output Server installation. The following configuration options appear:

1. Install HP Output Server.2. Install HP Output Server client only.3. Uninstall HP Output Server.4. Upgrade existing HP Output Server version

installation.

9. If the setup script detects an existing HP Output Server 3.3 or 3.4.1 installation, the default selection is 4. Accept the default or type 4.

77

78



10. When prompted for the installation path where HP Output Server is currently installed, accept the default or type the correct path. The default is the path that appears in step 8.

NOTE: Directory names can only include letters (A-Z and a-z), numbers (0-9), underscores (_) and dashes (-). Directory names cannot begin with a - (dash).

11. If you are upgrading HP Output Server 3.4.1, skip to step 15.

12. When prompted for the MySQL administrator user name, accept the default or type the name. The default is dazel.


- If your MySQL installation has an administrator password, accept the default. The default is y.

When prompted for the password, type the password. The setup script does not provide a default value. The password can contain only simple ASCII characters and must not exceed 32 characters. Do not use accented characters, single or double quotes, spaces, backslashes, back tics, commas, or special symbols.




- If your MySQL server is installed on this host, accept the default. The default is 1.

When prompted for the path to the MySQL file socket, accept the default or type the path. The default is installDir/var/mysql/mysql.sock.




15. If HP Output Server servers exist, the setup script prompts you to allow it to start the HP Output Server servers when the upgrade is finished. The default is the current state of the servers. 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, type y.

- If you do not want the setup script to start the HP Output Server servers when the installation is finished, type n.

If you choose n, you must manually start the servers with the start_server command after the upgrade is finished.

16. If your HP Output Server installation does not include an existing installation of HP Output Distributor 2.0, skip to the next step.

The setup script offers you the option to run a cleanup utility (od20_cleanup.pl) to remove the HP Output Distributor 2.0 files that are no longer used after the upgrade completes successfully. The default is yes (y). Accept the default to run the utility or type n if you do not want to run the utility.

NOTE: If data migration for HP Output Distributor 2.0 fails during the upgrade, the cleanup utility will not be invoked. You must correct the problem that caused data migration to fail and run the data migration utility manually. Upon successful completion of data migration you can then run the cleanup utility manually. You can also choose not to run the cleanup utility as part of the upgrade and run it later manually. See “Troubleshooting a failed upgrade” on page 86 and Appendix H, “HP Output Distributor 2.0 Clean-up Utility” on page 181.

17. When you complete all previous upgrade 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). Use the following steps to complete your installation.

Do one of the following:

- If the settings are not correct, accept the default (n).


The setup script displays setup progress and notifies you when the upgrade is complete. If the upgrade was successful, the following message appears:

HP Output Server 3.5 upgrade successfully installed and configured.

The log file is located in installDir/var/log/upgradeos.log

79

80



If the upgrade does not complete successfully, the log file is located in tmp/upgradeos.log.

Upgrading an HP Output Server client installation (UNIX only)
This section describes how to upgrade client installations of HP Output Server, Versions 3.3 and 3.4.1 to HP Output Server 3.5. Because a client installation of HP Output Server is supported on UNIX hosts only, an upgrade of a client installation is available on a UNIX host only.

1. Log in as root on your machine.


3. Stop all programs that monitor the HP Output Server server you want to upgrade. On multiple-domain hosts, some programs may be monitoring processes that are managed by other HP Output Server instances.

For example, the HP OpenView Operations and dzl_epod programs monitor HP Output Server processes and should be stopped before you start the setup.pl script.



Shell Command




HP Output Server



5. Mount the CD-ROM file system as described in Appendix A, “Mounting a Product CD-ROM on UNIX Systems” on page 139.

NOTE: You must log in as root to mount CD-ROM file systems. Some operating systems, such as Solaris, automount CD-ROM file systems.


cd /cdrom/aix


./perl ./setup.pl

NOTE: These instructions show how to use setup.pl in interactive mode (with prompts) to upgrade to HP Output Server 3.5. You can use setup.pl in non-interactive mode (without prompts) to upgrade to HP Output Server 3.5 by running setup.pl at the command line with arguments. For more information, see Appendix B, “Using setup.pl in Non-interactive Mode” on page 143.

If the setup script detects an existing client installation of HP Output Server, it displays the installation path, domain name, NM host name, and the NM port number of the existing HP Output Server installation. The following configuration options appear:

1. Install HP Output Server.2. Install HP Output Server client only.3. Uninstall HP Output Server.4. Upgrade existing HP Output Server version

installation.

8. If the setup script detects an existing HP Output Server 3.3 or 3.4.1 client installation, the default selection is 4. Accept the default or type 4.

81

82


Upgrading on a Windows host

9. When prompted for the installation path where the HP Output Server client installation is currently installed, accept the default or type the correct path. The default is the path that appears in step 7.

NOTE: Directory names can only include letters (A-Z and a-z), numbers (0-9), underscores (_) and dashes (-). Directory names cannot begin with a - (dash).

10. When you complete all previous upgrade 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). Use the following steps to complete your installation.

Do one of the following:

- If the settings are not correct, accept the default (n).


The setup script displays setup progress and notifies you when the upgrade is complete. If the upgrade was successful, the following message appears:

HP Output Server 3.5 upgrade successfully installed and configured.

The log file is located in installDir/var/log/upgradeos.log

If the upgrade does not complete successfully, the log file is located in tmp/upgradeos.log.

This section describes how to upgrade HP Output Server, Versions 3.3 and 3.4.1 to HP Output Server 3.5 on a Windows host.
The installation directory for an HP Output Server 3.5 upgrade is the same directory in which your current installation of HP Output Server is installed. The Setup program for an upgrade on a Windows host automatically locates the directory in which HP Output Server is installed and installs files into that directory.

To upgrade HP Output Server on a Windows host, perform the following steps:

1. Log in as a user with the required permissions. For more information, see Chapter 1, “Planning the Installation” on page 1.


HP Output Server



2. Stop all programs that monitor the HP Output Server instance that you want to upgrade. On hosts with multiple domains, some programs may be monitoring processes that are managed by other HP Output Server instances. For example, the HP Open View for Operations and dzl_epod programs monitor HP Output Server processes and should be stopped before you run the setup program.



4. Ensure that all HP Output Server servers are stopped.

5. Insert the HP Output Server 3.5 CD-ROM into the CD-ROM drive.

The Welcome screen appears.

NOTE: Run the setup.exe program on the CD-ROM if it does not start automatically. The setup.exe program is located in the win32 folder.

6. Click Next.The Setup program detects an existing installation and prompts you to upgrade it.

7. To continue with the upgrade, click Yes.

8. If HP Output Server servers exist, the Server State Configuration dialog box appears. Select either Running or Stopped when prompted to have the HP Output Server servers running or stopped when the upgrade is complete. The default is the current state of the servers. Click Next.

NOTE: If you select Stopped, you must manually start the servers with the start_server command after the upgrade is finished.

If HP Output Server servers are stopped, Setup will start the servers after the upgrade completes.

83

84



9. If you are upgrading HP Output Server 3.4.1, skip to step 11. If you are upgrading HP Output Server 3.3, the MySQL Administrator User and Password dialog box appears. Type the MySQL administrator user name. The default user name that appears is dazel. If your MySQL administrator user has a password, type the password in the Password box. Retype the password in the Confirm password box. Click Next.

10. In the MySQL Host Name and Port dialog box, do one of the following:

- To accept the defaults for name of the MySQL host and the port number on which the MySQL server is listening, click Next. The default host name is localhost and the default port number is 3306.

- Type the name of the host on which MySQL is installed and the port number on which the MySQL server is listening. Click Next.

NOTE: If MySQL is installed on the same machine as HP Output Server, you must use localhost as the name of the host.

11. If your HP Output Server installation does not include HP Output Distributor 2.0, skip to the next step.

In the HP Output Distributor Upgrade dialog box, the Setup program offers you the option to run a cleanup utility to remove the HP Output Distributor 2.0 database files that are no longer used after the upgrade completes successfully. The default is Yes. Click Next to accept the default or select No and then click Next if you do not want to run the utility.

NOTE: If data migration for HP Output Distributor 2.0 fails during the upgrade, the cleanup utility will not be invoked. You must correct the problem that caused data migration to fail and run the data migration utility manually. Upon successful completion of data migration you can then run the cleanup utility manually. You can also choose not to run the cleanup utility as part of the upgrade and run it manually later. See “Troubleshooting a failed upgrade” on page 86 and Appendix H, “HP Output Distributor 2.0 Clean-up Utility” on page 181.

12. In the Review Settings dialog box, review the settings that you have 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.


HP Output Server


Restoring backup template customizations

13. If you did not stop all HP Output Server servers, Setup prompts you to allow it to stop the servers. Click Yes.

14. In the HP Output Server Installation Complete dialog box, click Finish.

15. Restart your system if recommended by the Setup program.

The upgrade log is located in installDir/var/log/upgradeos.log.

Restoring backup template customizations
This section describes how to restore backup template customizations after an upgrade on UNIX and Windows hosts.
During an upgrade, 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.

On Windows hosts, the environment variables do not require additional sourcing.

2. Change to the upgrd33bak or upgrd341bak directory (depending on the version of HP Output Server that you upgraded) using the following command:

cd installDir/directoryName

where directoryName is either upgrd33bak or upgrd341bak.

3. When restoring backup template customizations on UNIX hosts, extract the contents of the directoryName directory with the following command:

zcat directoryName.tar.Z | tar -xvf -

On Windows hosts, no commands are necessary to extract the contents of the directoryName directory.

4. To change to the custom/templates directory, type the following:

cd custom/templates

5. Identify which templates are to be reloaded into the CM and move them into files within the installDir/custom/templates directory.

Shell Command



85

86


Troubleshooting a failed upgrade

6. To change to the installDir/custom/templates directory, type the following:

cd installDir/custom/templates

7. To load the modified template files into the CM, type 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 upgraded during an upgrade of HP Output Server:
1. HP Output Server

2. HP Output Manager for SAP

3. HP Output Distributor

If an upgrade of HP Output Server fails, the setup script aborts and the remaining products are not upgraded or installed.

For information about recovering from a failed upgrade of HP Output Server, see “Recovering from a failed HP Output Server upgrade” on page 87.

For information about recovering from a failed upgrade of HP Output Distributor, see “Recovering from a failed HP Output Distributor upgrade” on page 95.




Recovering from a failed HP Output Server upgrade

HP Output Server

Typically, the only way to recover from a failed HP Output Server upgrade 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 upgrade.

• Insufficient disk space caused the setup program to abort the upgrade.

In these cases, fix the problem that caused the failure and rerun the setup program.

If you are upgrading HP Output Server 3.3 and the upgrade fails due to a failure in migrating data to MySQL for HP Output Management, you must also drop any HP Output Server databases created in MySQL for HP Output Management before rerunning the setup program. The following section describes how to recover from a failed upgrade when data migration for HP Output Server 3.3 fails.

Recovering from failed data migration from HP Output Server 3.3
During data migration in an upgrade of HP Output Server 3.3, the setup script receives error information from dbupgrade and logs a general status message (success, warning, or failure) in the installDir/var/log/upgradeos.log for each server that is upgraded. If the upgrade fails, the log is located at /tmp/upgradeos.log.
CAUTION: The only method of recovering from a failed upgrade for HP Output Server when data migration from HP Output Server 3.3 fails is restoring a backup.

87

88



In addition to upgradeos.log, individual server logs are located in the directories listed in the following table.

Table 4-4. Location of server dbupgrade.log files

Server* Path

PM installDir/var/pm/ctdb/dbupgrade.log

installDir/var/pm/ptdb/dbupgrade.log

installDir/var/pm/gdb/dbupgrade.log

installDir/var/pm/pdb/dbupgrade.log

EM installDir/var/em/serverName/INCdb/dbupgrade.log

AIM installDir/var/qsd/IDS_QS_DB/dbupgrade.log

CM installDir/var/ccm/ids_ccm/ids_ccm.pdb/dbupgrade.log

DLM installDir/var/jobdb/dm/serverName/serverName.pdb/dbupgrade.log

JQM installDir/var/jobdb/drb/serverName/serverName.pdb/dbupgrade.log

* Some HP Output Server servers are not listed in this table, indicating that the server either does not use MySQL or is recreated at server startup.

The dbupgrade.log can contain messages of the following types. Use the information in these logs to determine what type of data did not migrate. Each log presents a summary at the end of the log. If you ran dbreorg on the databases prior to performing an upgrade, a warning or an error message indicates that the data in the record, table, or database for that server is not recoverable.

Warning. A warning indicates that dbupgrade was unable to process a record in a database. The upgrade continues. A warning message indicates that one or more records are missing in the upgraded database. Use the information in the database tables to determine what type of information is missing. See “Database tables” on page 91. To address the warning condition and re-run the upgrade, use the suggested workaround for an error condition.

Error. An error indicates that dbupgrade was unable to read or create a table or database. An error causes the upgrade to fail. An error message stops the upgrade process. Do the following:

1. Restore your HP Output Server 3.3 installation from a previous backup (other than the backed-up version that failed), or attempt to fix the problem in the most recent backup.


HP Output Server



2. Run the dbreorg.pl script.

3. If any MySQL tables were created, drop the tables. See “Dropping a database in MySQL” in the following section.

4. Run the upgrade.

Fatal Error. A fatal error results from more general errors that cause data migration to fail, such as errors in memory allocation. Typically, a fatal error means that an error occurred due to an operating system error. In this case, do the following:

1. Reboot the system.

2. Restore your HP Output Server 3.3 installation from backup.

3. Run the dbreorg.pl script on the HP Output Server 3.3 databases.

4. If any MySQL tables were created, drop the tables. See “Dropping a database in MySQL” in the following section.

5. Run the upgrade.

Dropping a database in MySQL
To drop a database in MySQL, perform the following steps:
1. Locate the name of the database that you want to drop. For the names and locations of HP Output Server database tables, see “Database tables” on page 91.

2. To delete a database, use the mysqladmin utility by typing the following commands:

cd mySQLinstallDir/bin./mysqladmin --defaults-file=mySQLinstallDir/my.cnf drop

databaseName

where

databaseName is the name of the database to drop.

All databases and tables are created in the MySQL mySQLinstallDir/data directory. Although table names are the same as in HP Output Server 3.3, database names are changed to be able to support multiple HP Output Server domains sharing one MySQL server. Each server’s database name is prepended with the DAZELNS values of unqualified host name, domain name, and port number. For

89

90



example, if the PM database has a DAZELNS value of DAZEL:athena.d,edwina.hp.com[4009], the PM database name in the HP Output Server 3.5 installation is the following:

athena!d_4009_pm

NOTE: The domain name includes a ! (exclamation) because the . (dot) is a database/table delimiter in MySQL.

Examples of failed upgrades
The following two scenarios illustrate examples of an aborted upgrade of HP Output Server 3.3. In these examples, the upgrade failed during dbupgrade.
Scenario 1In the following scenario, the existing HP Output Server installation caused duplicate names of the MySQL database tables (apollo!d_4009_qsd). An excerpt from the log follows:

Setting file ownership to dazel:other...Configuring the var directory structure...

Upgrading accounting-and-inventory-manager 'aim'...ERROR: dbupgrade failure on server database

/home/dazel/os/33upto34B/dbupgrade/IDS_QS_DB with return value 1

***Installation Aborted***The logfile is located in /tmp/upgradeos.logDatabase already exists


HP Output Server



Scenario 2In this scenario, the DLM contained corrupt data. The log excerpt follows:

Setting file ownership to dazel:other...Configuring the var directory structure...

Upgrading accounting-and-inventory-manager 'aim'...Upgrading event-manager 'em'...Upgrading privilege-manager 'pm'...Upgrading configuration-manager 'cm'...Upgrading delivery-manager 'dlm_01'...ERROR: dbupgrade failure on server database

/home/dazel/os/34up/dbupgrade/dlm_01.pdb with return value 1

***Installation Aborted***The logfile is located in /tmp/upgradeos.log

Database tables
This section describes the tables that are in each HP Output Server database by type of server. All databases and tables for HP Output Server 3.5 are created in the MySQL mySQLinstallDir/data directory.
Although table names are the same as in HP Output Server 3.3, database names are changed to be able to support multiple HP Output Server domains sharing one MySQL server. Each server’s database name is prepended with the DAZELNS values of unqualified host name, domain name, and port number. For example, if the PM database has a DAZELNS value of DAZEL:athena.d,edwina.hp.com[4009], the PM database name in the HP Output Server 3.5 installation is the following:

athena!d_4009_pm

NOTE: The domain name includes a ! (exclamation) because the . (dot) is a database/table delimiter in MySQL.

91

92



The following table lists database tables for the HP Output Server primary servers.Table 4-5. Primary server database tables

Server Table Name Description

AIM schema DB schema

table_001 classes

table_002 attributes

table_003 types

table_004 domains

table_005 defaults

table_006 privileges

table_007 hierarchies

table_008 keys

table_009 destinations

table_010 destination-type-controls

table_011 destination-name-controls

table_012 persons

table_013 person-destinations

table_014 job-accounting

table_015 destination-accounting

table_016 server-accounting

table_017 operation-accounting

table_018 groups

table_019 group-members


HP Output Server



The following table lists the DLM database tables.

CM 002 destinations

003 servers

051 queues

101 transformers

102 forms

103 paging systems

105 device types

107 capabilities

EM clients clients

subscriptions subscriptions

PM ctdb_tbl clients

pdb_tbl privileges

ptdb_tbl permissions templates

gdb_group groups

gdb_members group members

Table 4-6. DLM database tables

Table Name Description Pre-upgrade Post-upgrade

jobs jobs yes no

001 subjobs no yes

003 DLM server yes yes

016 dlm jobs no yes

Table 4-5. Primary server database tables (continued)

Server Table Name Description

93

94



The following table lists the JQM database tables.

The following table lists the DSM database tables.

Table 4-7. JQM database tables

Table Name Description

001 jobs

002 destinations

003 JQM server

051 queues

107 capabilities

Table 4-8. DSM database tables

Table Name Description

002 destinations

003 DSM server

101 transformers

107 capabilities




Recovering from a failed HP Output Distributor upgrade

HP Output Server

If an upgrade fails due to a failure in data migration from HP Output Distributor 2.0 to MySQL for HP Output Management, you do not have to restore your HP Output Server and HP Output Distributor installations from a backup or drop any HP Output Distributor databases created in MySQL for HP Output Management. Check the upgrade log located in installDir/var/log/hpod_dmutil.log, fix the problem, that caused the data migration to fail, and then run the hpod_dmutil.pl data migration utility. For information about running hpod_dmutil.pl manually, see Appendix I, “HP Output Distributor 2.0 Data Migration Utility” on page 183.

NOTE: If data migration for HP Output Distributor 2.0 fails during the upgrade, the cleanup utility will not be invoked. You must correct the problem that caused data migration to fail and run the data migration utility manually. Upon successful completion of data migration you can then run the cleanup utility manually. For more information, see Appendix H, “HP Output Distributor 2.0 Clean-up Utility” on page 181.

The following table describes errors that can occur as part of data migration of an existing HP Output Distributor 2.0 installation during an upgrade to HP Output Distributor 3.5 and what action you can take to correct the problem before running hpod_dmutil.pl manually:Table 4-9. Troubleshooting data migration

Error Message Action Required

ERROR: Unable to start Output Distributor 2.0 database server.

Determine why the server is not starting, fix the problem, and start the server manually using the odstart_server command.

ERROR: Insufficient disk space. ***Data Migration Aborted*** Please check the log file at installDir/var/log/hpod_dmutil.log for more information.

Delete unwanted files or a select a different partition.

ERROR: Unable to contact your MySQL server using the connection options you specified. Check the options and verify that the specified MySQL server is accepting connections.

Check the MySQL connection options, and specify the correct options.

95

96



Starting data migration...Creating a database instance: odsub... ***FAIL: Fatal Error*** Unable to create the database instance.

The database already exists in the MySQL database. Drop the database manually. For more information about dropping a database in MySQL for HP Output Management, see “Dropping a database in MySQL” on page 89.

Updating od.ini for database instance at: /os33/var/od/odsub/od.ini

Check the file permission and change to the correct permission to update the file.

ERROR: Encountered problems while calculating required space for data migration.

Ensure that the HP Output Distributor 2.0 database is running. Start the server if it is not running.

Table 4-9. Troubleshooting data migration (continued)

Error Message Action Required


Chapter 5

Installing and Removing Patches

HP Output Server

This chapter describes how to install and remove patches (service packs and hotfixes) on HP Output Server. Refer to the release notes that accompany a patch before attempting to install a service pack or hofix. Patching HP Output Server 3.5 also patches HP Output Manager for SAP 3.5 and HP Output Distributor 3.5 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 3.5” on page 121.

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 103.

97

Chapter 5 Installing and Removing Patches

Installing a patch on a UNIX host


98

This section describes how to install a patch for HP Output Server on a UNIX host. Refer to the release notes that accompany a patch before attempting to install it.

Service pack installations are cumulative. For example, if you apply a service pack that updates HP Output Server to 3.5.0.3.0, it includes defects and enhancements in service packs 3.5.0.2.0 and 3.5.0.1.0.

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. For more information, see “Removing a patch from a UNIX host” on page 100.

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.

To install a patch on a UNIX host, perform the following steps:

1. Log in as root to the host where HP Output Server is running. On all UNIX platforms other than AIX, you can also log in as the user specified during an installation or upgrade as the owner of the installed files.

NOTE: Note that if you are logged in as a non-root user, you may be required to copy some files manually and ensure that the files have the correct ownership.

2. Depending on your shell, enter a command from the following table to source the HP Output Server environment variables:

Shell Command




HP Output Server



3. Download the patch from the Customer Support Web site at http://itrc.hp.com and save it in installDir/etc.

4. Stop all programs that monitor the HP Output Server installation you want to patch. On multiple-domain hosts, some programs may be monitoring processes that are managed by other HP Output Server instances.

For example, the HP Output Manager for Open View and dzl_epod programs monitor HP Output Server processes and should be stopped.


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, refer to the documentation for your HP Output Management applications.

NOTE: Do not stop MySQL for HP Output Management.

6. Change to the installDir/etc directory, for example:

cd $DAZEL_HOME/etc

7. Run the patch.pl script:

perl patch.pl

8. The patch utility prompts you to specify the full path name of the installation file and offers as a default the most recent patch file in the installDir/etc directory. If the default path is not correct, type the full path of the patch file. The patch utility then extracts the necessary files and validates all patch files.

NOTE: If you have installed a previous patch, the patch utility displays the following options:

(1) Install a patch for HP Output Server(2) Back out HP Output Server to 3.5.x.x.x.x

Select option 1.

99

http://itrc.hp.com

100


Removing a patch from a UNIX host

9. All servers are stopped during the patch installation. When prompted to restart the servers after the patch installation is complete, accept the default y (yes), or type n (no).

NOTE: If you choose not to have the servers restarted when the patch installation is complete, you must restart the servers manually before using HP Output Server.

10. When prompted, verify that the patch installation version is correct. The patch.pl script will identify the patch level. To continue with the installation, type y.

All servers will be stopped and subsequently restarted (if specified) by the patch utility.

The log file is located at installDir/var/log/patchos.log.

The patch installation is complete.

NOTE: Customized files that are located in the installDir/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 Consulting and Integration.

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 3.5.0.1.0 and then install Service Pack 3.5.0.2.0, you can back out only to Service Pack 3.5.0.1.0.



HP Output Server



Backing out a hotfix backs out all previously applied hotfixes. For example, if you install Hotfix 3.5.0.1.1 and then install Hotfix 3.5.0.1.2, you can back out only to HP Output Server 3.5.0.1.0.

NOTE: If your HP Output Server domain is configured to run on multiple hosts, remove patches 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. 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.

To remove patches on UNIX hosts, perform the following steps:

1. Log in as root to the host where HP Output Server is running.

2. Depending on your shell, enter a command from the following table to source the HP Output Server environment variables:

3. 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, the HP Output Manager for Open View and dzl_epod programs monitor HP Output Server processes and should be stopped.


Shell Command



101

102



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, refer to the documentation for your HP Output Management applications.


5. Change to the installDir/etc directory, for example:

cd $DAZEL_HOME/etc

6. Run the patch.pl script:

perl patch.pl

The following options appear:

1) Install a patch for HP Output Server2) Backout HP Output Server to 3.5.x.x.x.x

7. Select option 2.

8. All servers are stopped during the patch back out. When prompted to restart the servers after the patch backout is complete, accept the default or type n (no). The default is y (yes).

NOTE: If you choose not to have the servers restarted when the patch backout is complete, you must restart the servers manually before using HP Output Server.

9. Verify that the patch installation version is correct. The patch.pl script identifies the patch level. To continue with the patch backout, type y.

All servers will be stopped and subsequently restarted (if specified) by the patch utility.

The patch backout is complete.



Installing a patch on a Windows host

Installing a patch on a Windows host

HP Output Server

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 3.5.0.3.0, it includes defects and enhancements in service packs 3.5.0.2.0 and 3.5.0.1.0.


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 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 Manager for Open View and dzl_epod programs monitor HP Output Server processes and must be stopped before you proceed.


To install a patch on a Windows hosts, 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. For example, the HP Output Manager for Open View and dzl_epod programs monitor HP Output Server processes and must be stopped before you proceed.


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

103

104


Removing a patch from a Windows host

restarted automatically; you must restart these applications manually. For more information, refer to the documentation for your HP Output Management applications.


4. Download the patch from the Customer Support Web site at http://itrc.hp.com and save it in installDir/etc.

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 version 3.5 Patch Setup screen appears.

7. Click Next.

8. The Review Settings dialog box provides a summary of HP Output Server installation settings. 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.

9. If HP Output Server servers are running, the Setup program prompts you to stop all HP Output Server servers. Click Yes.

NOTE: If you click No, the Setup program quits.

The Setup program automatically restarts the HP Output Server servers when the installation is complete.

10. In the HP Output Server v3.5 Patch Setup dialog box, click Finish.

The patch installation is complete.

The following section describes how to back out patches for HP Output Server 3.5 on Windows hosts.

http://itrc.hp.com

HP Output Server



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 3.5.0.1.0 and then install Service Pack 3.5.0.2.0, you can back out only to Service Pack 3.5.0.1.0.


To remove 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, refer to the documentation for your HP Output Management applications.


4. Use the Add/Remove Programs feature of your Windows operating system to select and remove the patch (HP Output Server Version 3.5 patch x).

5. Select Back out HP Output Server patch x, and then click Next.

6. If HP Output Server servers are running, the Setup program prompts you to stop all HP Output Server servers. Click Yes.

NOTE: If you click No, the program quits.

7. After all HP Output Server servers have been stopped, the HP Output Server Patch Backout Complete dialog box appears. Click Finish to complete the patch backout.

105

106




Chapter 6

Configuring HP Output Server

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

• Install MySQL for HP Output Management and HP Output Server on all hosts on which you plan to run servers.

• 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:

• setting environment variables

• configuring servers

• selecting a language for HP Output Server

• configuring user authentication and authorization

• configuring interdomain delivery

• configuring the LPR Gateway

• configuring a delivery pathway

• testing the configuration

107

Chapter 6 Configuring HP Output Server

Setting environment variables

Setting environment variables

108

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.

For a list of HP Output Server environment variables, their settings, and a description of methods for setting these variables, see Appendix C, “Environment Variables in HP Output Server” on page 147.

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 Administrator’s Command Reference for HP Output Server.
Selecting a different language on a UNIX host
HP Output Server uses the English language and the en_US locale as the default language setting for the product on UNIX hosts. You can configure HP Output Server to use the French, German, or Spanish language as well as a range of different locales, such as en_GB, fr_CA, or de_DE. When you change the default language, HP Output Server displays error and warning messages in the language you select. (You must continue, however, to enter commands, attributes, and arguments for the HP Output Server in a manner that complies with the proper syntax.) When you change the locale, you select a different page size—US Letter versus A4—and other options such as date and time format.
You can determine the locales your UNIX operating system supports by typing the following command:

locale -a

The command returns a list of locales.

To configure HP Output Server to use a different locale and to display messages in a different language on a UNIX host, set the LANG environment variable to the locale you want to use. You do this by changing the value of the LANG environment variable in a startup file for the host, such as .cshrc or .profile, or by changing the value


HP Output Server


Configuring user authentication and authorization

of the environment variable in the startup file for HP Output Server—the installDir/etc/setup_env.csh or installDir/etc/setup_env.sh file. For example:

LANG=de_DE

changes the locale setting to use the German language and the de_DE locale.

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 authentication—determining 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 R/3, to ensure a user’s identity. UNIX ID mode obtains user and group information from the underlying UNIX operating system on which HP Output Server is installed.
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, type the following command:

config_server -u -x"-pm-id-mode authenticationMode" pmName

109

110



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:
• 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 an unauthorized user 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 typing the following command:

pm_edit -p dazel_admin group add user jjschmidt


HP Output Server



The example 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 2002

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 typing the following command:

pm_edit m i all

The preceding command clears the cache and reloads permissions for HP Output Server.

The System Administrator’s 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.

111


Configuring interdomain delivery

Configuring interdomain delivery

112

Configuring interdomain delivery enables users in one HP Output Server domain 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:

• SSM (Windows only)

• NM

• PM

• AIM

• CM

• EM (at least one)

• DLM (at least one)

• JQM (at least one)

• DSM (at least one)

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 Administrator’s Guide for HP Output Server.

Configuring the LPR Gateway
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 Appendix D, “Configuring the HP Output Server LPR Gateway” on page 155.


Creating a delivery pathway


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 subjob’s particular specifications.

A delivery pathway may also contain multiple logical destinations and multiple physical destinations.

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.

113



Before you begin

114

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 select printers, HP Output Server provides support for the following advanced printer features:

- folding

- hole punching

- job storage

- private printing

- stapling

Accessing these features requires creating an advanced delivery pathway with advanced templates for physical destinations. For a list of the select printers, see the Release Notes for HP Output Server. For information about creating advanced delivery pathways, see the System Administrator’s 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


HP Output Server



When you create a physical destination, specify the Destination Manager (DSM). For example:

pdcreate -c d -x"-queue-supported my_queue-copy-from hp4si_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.

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

Delivery Object Command

logical destination pdls -c d -a none -x"-template true -printer-realization 0" ids_ccm:

physical destination pdls -c d -a none -x"-template true -printer-realization 1" ids_ccm:

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

115

116



To view the current settings for a particular template, use the commands in the following table.

For more information about setting attributes for delivery objects and customizing templates, see the System Administrator’s Guide for HP Output Server.

Table 6-2. Command for listing a template’s settings

Delivery Object Command

logical destination pdls -c d -a all ids_ccm:template_name

physical destination pdls -c d -a all ids_ccm:template_name

queue pdls -c q -a all ids_ccm:template_name

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

The example 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

HP Output Server

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. Select the template you want to use.

- 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.

3. 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:

pdls -c d -a none -x"-template true -printer-realization 0" ids_ccm:


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.

117


Testing the configuration

Creating a physical destination

118

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:

pdls -c d -a none -x"-template true -printer-realization 1" ids_ccm:


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

pdcreate -c d -x"-queue-supported q_ps_printer-copy-from hp4si_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 hp4si_ps_tcp_template—a 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, type 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 :retained-job-completion-status :success

Troubleshoot unsuccessful attempts by checking the following:

1. To verify that all servers are running, type the following command:

server_status


HP Output Server



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, perform the following command:

pdls -c q -a all queueName

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 117 and “Creating a physical destination” on page 118 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, installDir/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 serverstart_server -t server

6. Re-test the configuration as described in the steps above. If the test still fails after performing the troubleshooting, contact Customer Support.

119

120




Chapter 7

Backing up and Restoring HP Output Server 3.5

HP Output Server

This chapter describes how to back up and restore HP Output Server 3.5, including all HP Output Server databases stored in an installation of MySQL for HP Output Management. Backing up HP Output Server 3.5 also backs up HP Output Manager for SAP 3.5 and HP Output Distributor 3.5.

HP Output Server stores program and configuration files in installDir, the installation path for your HP Output Server installation. HP Output Server also stores configuration settings and records in several MySQL databases. Backing up and restoring an existing HP Output Server installation, where HP Output Server and MySQL for HP Output Management are installed in separate directories or on separate hosts, includes the following tasks:

1. backing up the HP Output Server program and configuration files in installDir

2. backing up the configured databases

3. restoring the databases from the backup

4. restoring the HP Output Server program and configuration files from the installDir backup

121

122

Chapter 7 Backing up and Restoring HP Output Server 3.5

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 135.

For assistance with backup issues or configurations not addressed in this appendix, contact your Professional Services representative or Customer Support.

Before you begin
Before you back up your HP Output Server installation, note the following requirements:
• 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 3.5 and HP Output Distributor 3.5.

• 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.



Backing up HP Output Server on a UNIX host


HP Output Server

This section describes how to back up HP Output Server on a UNIX host. For information about backing up HP Output Server on a Windows host, see “Backing up HP Output Server on a Windows host” on page 129.

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 135.

Backing up HP Output Server includes the following tasks:




Task 1: Backing up program and configuration files
To back up your HP Output Server program and configuration files on a UNIX host, perform the following steps:
1. If you have not already done so, log on as the root user.

2. Set the HP Output Server environment variables by typing one of the following commands:

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 typing the following command:

stop_server -t all

Shell Command



123

124



5. Change to the installation directory for HP Output Server by typing the following command:

cd installDir

6. Back up and compress the existing installation by typing the following command:

tar -cvf - .|compress -c >/path/fileName.Z

where path is the target directory for the backup and fileName is a name for the backup file.

Task 2: Backing up HP Output Server databases
HP Output Server stores configuration settings and records in several MySQL databases. This section describes how to back up HP Output Server databases and tables in an installation of MySQL for HP Output Management on a UNIX host. This section provides instructions for performing the following types of backups:
• backing up all databases

• backing up a single database

• backing up specified tables within a single database

• backing up more than one specified 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 all databases

HP Output Server

To back up all the databases, including the database tables and records for each database, type the following commands:

cd mySQLinstallDir/bin./mysqldump --defaults-file=mySQLinstallDir/my.cnf

--quote-names --add-drop-table --quick --extended-insert --all-databases --result-file=/path/fileName

where

- mySQLinstallDir is the location of the MySQL for HP Output Management installation.

- path is the location you choose for saving the backup of the databases.

- fileName is a name for the file that will save a copy of the databases and their contents.

Backing up a single database
You can also create a backup of a single HP Output Server database, including all tables and records in the database, by typing 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

where


- databaseName is the name of an HP Output Server database, for example, sluggo!d_4009_pm.

- 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.

125



Backing up specified tables within a single database

126

You can also 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 002, 003, and 051 in a database named sluggo!d_4009_jqm. 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

--quote-names --add-drop-table --quick --extended-insert sluggo!d_4009_jqm 002 003 051 --result-file=/mybackup/myDBtables

NOTE: For a list of table names for HP Output Server databases, see “Database tables” on page 91.

Backing up more than one database
You can back up more than one specified database by using the --databases option instead of --all-databases in the preceding commands and by specifying the names of the databases to back up.
All databases and tables are created in the MySQL mySQLinstallDir/data directory, where mySQLinstallDir is the installation path for MySQL for HP Output Management. Each server’s database name is prepended with the DAZELNS values of the domain name and port number. For example, if the PM database has a DAZELNS value of DAZEL:athena.d,edwina.hp.com[4009], the PM database name is athena!d_4009_pm.

NOTE: The database name replaces the period in the domain name with an ! (exclamation) because the period is a database/table delimiter in MySQL.


HP Output Server


Restoring HP Output Server on a UNIX host

The following example creates a backup of the databases named sluggo!d_4009_pm, sluggo!d_4009_em, and sluggo!d_4009_ids_ccm. MySQL for HP Output Management is installed in /usr/local/mysql and the backup file is located at /mybackup/myDBs

cd /usr/local/mysql/bin./mysqldump --defaults-file=/user/local/mysql/my.cnf

--quote-names --add-drop-table --quick --extended-insert --databases sluggo!d_4009_pm sluggo!d_4009_em sluggo!d_4009_ids_ccm --result-file=/mybackup/myDBs

This section describes how to restore HP Output Server from a backup on a UNIX host. For information about restoring HP Output Server from a backup on a Windows host, see “Restoring HP Output Server on a Windows host” on page 133.
This section assumes that you have created a backup of HP Output Server by performing the steps in “Backing up HP Output Server on a UNIX host” on page 123.

Restoring HP Output Server includes the following tasks:

1. recreating the databases from the backup



Task 1: Recreating the HP Output Server databases
Before you restore the program and configuration files for HP Output Server, you fix or recreate the databases. Depending on the type of database backup that you created, use the following options to recreate the databases from the backup.
CAUTION: Before you recreate HP Output Server databases from a backup, ensure that all HP Output Server servers are stopped.

127



Recreating all databases or specified databases

128

If you created a backup of all databases or more than one database, type the following commands to recreate the databases:

cd mySQLinstallDir/bin./mysql --defaults-file=mySQLinstallDir/my.cnf <

/path/fileName

where


- path is the location you chose for saving a copy of the databases.

- fileName is the name of the backup file that you created for the databases.

Recreating a single database or specified tables in a single database
If you created a backup of a single database or specified tables in a single database, type the following commands to recreate the database or tables:
cd mySQLinstallDir/bin./mysql --defaults-file=mySQLinstallDir/my.cnf

databaseName < /path/fileName

where


- databaseName is the name of the HP Output Server database in your backup, for example, sluggo!d_4009_pm.

- 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.

Task 2: Restoring the program and configuration files
To restore an existing installation of HP Output Server on a UNIX host, perform the following steps:
1. If you have not already done so, log in as the root user.


HP Output Server


Backing up HP Output Server on a Windows host


3. On AIX hosts, run the slibclean command to ensure that library files are not in use.


cd installDir

5. Restore the previous installation with the backup copy of the files by typing the following command:

zcat fileName.Z | tar -xvf -

where fileName is the name of the backup file.

6. Start the HP Output Server servers by typing the following command:

start_server -t all

Shell Command



This section describes how to back up HP Output Server on a Windows host. For information about backing up HP Output Server on a UNIX host, see “Backing up HP Output Server on a UNIX host” on page 1.
Backing up HP Output Server includes the following tasks:




129



Task 1: Backing up program and configuration files

130

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 Consulting and Integration representative.

To back up your HP Output Server program and configuration files on a Windows host, perform the following steps:

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.


stop_server -t all


cd installDir

The default location for this directory is C:\HP\OM.

6. Use a compression and file packaging utility, such as the zip command, PKZIP or WinZip, to back up the existing installation.




Task 2: Backing up the HP Output Server databases

HP Output Server

HP Output Server stores configuration settings and records in several MySQL databases. This section describes how to back up HP Output Server databases and tables in an installation of MySQL for HP Output Management on a Windows host. This section provides instructions for performing the following types of backups:

• backing up all databases

• backing up a single database

• backing up specified tables within a single database

• backing up more than one specified 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 all databases
To back up all the databases, including the database tables and records for each database, perform the following steps:
1. Open a Command Prompt window.

2. Type the following commands:

cd mySQLinstallDir\bin.\mysqldump --defaults-file=mySQLinstallDir\my.cnf

--quote-names --add-drop-table --quick --extended-insert --all-databases --result-file=\path\fileName

where


- path is the location where you want to save a backup of the databases.

- fileName is a name for the file that will save a copy of the databases and their contents.

131



Backing up a single database

132

You can also create a backup of a single HP Output Server database, including all tables and records in the database, by typing 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

where


- databaseName is the name of an HP Output Server database, for example, sluggo!d_4009_pm.

- 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 single database
You can also 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 002, 003, and 051 in a database named sluggo!d_4009_jqm. 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

--quote-names --add-drop-table --quick --extended-insert sluggo!d_4009_jqm 002 003 051 --result-file=C:\mybackup\myDBtables

NOTE: For a list of table names for HP Output Server databases, see “Database tables” on page 91.



Restoring HP Output Server on a Windows host

Backing up more than one database

HP Output Server

You can back up more than one specified database by using the --databases option instead of --all-databases in the preceding commands and by specifying the names of the databases to back up.

All databases and tables are created in the MySQL mySQLinstallDir\data directory, where mySQLinstallDir is the installation path for MySQL for HP Output Management. Each server’s database name is prepended with the DAZELNS values of the domain name and port number. For example, if the PM database has a DAZELNS value of DAZEL:athena.d,edwina.hp.com[4009], the PM database name is athena!d_4009_pm.

NOTE: The database name replaces the period in the domain name with an ! (exclamation) because the period is a database/table delimiter in MySQL.

The following example creates a backup of the databases named sluggo!d_4009_pm, sluggo!d_4009_em, and sluggo!d_4009_ids_ccm. MySQL for HP Output Management is installed in C:\mysql and the backup file is located at C:\mybackup\myDBs

cd C:\mysql\bin.\mysqldump --defaults-file=C:\mysql\my.cnf

--quote-names --add-drop-table --quick --extended-insert --databases sluggo!d_4009_pm sluggo!d_4009_em sluggo!d_4009_ids_ccm --result-file=C:\mybackup\myDBs

This section describes how to restore HP Output Server from a backup on a Windows host. For information about restoring HP Output Server from a backup on a UNIX host, see “Restoring HP Output Server on a UNIX host” on page 1.
This section assumes that you have created a backup of HP Output Server by performing the steps in “Backing up HP Output Server on a Windows host” on page 129.

133

134



Restoring HP Output Server includes the following tasks:

1. recreating the databases from the backup



Task 1: Recreating the HP Output Server databases
Before you restore the program and configuration files for HP Output Server, you fix or recreate the databases. Depending on the type of database backup that you created, use the following options to recreate the databases from the backup.
CAUTION: Before you recreate HP Output Server databases from a backup, ensure that all HP Output Server servers are stopped.

Recreating all databases or specified databases
If you created a backup of all databases or more than one database, type the following commands to recreate the databases:
cd mySQLinstallDir\bin.\mysql --defaults-file=mySQLinstallDir\my.cnf <

\path\fileName

where


- path is the location you chose for saving a copy of the databases.

- fileName is the name of the backup file that you created for the databases.

Recreating a single database or specified tables in a single database
If you created a backup of a single database or specified tables in a single database, type the following commands to recreate the database or tables:
cd mySQLinstallDir\bin.\mysql --defaults-file=mySQLinstallDir\my.cnf

databaseName < \path\fileName

where


HP Output Server


Backing up and restoring same directory installations (UNIX only)


- databaseName is the name of the HP Output Server database in your backup, for example, sluggo!d_4009_pm.

- 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.

Task 2: Restoring the HP Output Server installation directory
To restore an existing installation of HP Output Server on a Windows host, perform the following steps:

2. Install HP Output Server from the product CD-ROM.

3. Install any patches you previously installed for HP Output Server.

4. Open a Command Prompt.


stop_server -t all


cd installDir

7. Use a file extraction utility, such as the unzip command, PKZIP or WinZip, to restore the previous installation with the backup copy of the files. For example:

unzip fileName



start_server -t all


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

135

136



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:
• 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:
1. If you have not already done so, log on as the root user.


3. Stop all programs that monitor or depend on the HP Output Server installation that you want to back up.


stop_server -t all

Shell Command




HP Output Server



5. Stop the MySQL server by typing the following commands:

cd mySQLinstallDir./bin/mysqladmin --defaults-file=mySQLinstallDir/my.cnf

shutdown

where mySQLinstallDir is the location of the MySQL for HP Output Management installation.

6. Change to the installation directory for HP Output Server and MySQL for HP Output Management by typing the following command:

cd sharedInstallDir

where sharedInstallDir is the installation directory of HP Output Server and MySQL for HP Output Management.

7. Back up and compress the existing installations of HP Output Server and MySQL for HP Output Management by typing the following command:

tar -cvf - .|compress -c >/path/fileName.Z

where path is the target directory for the backup and fileName is a name for the 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 136.
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:



3. 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.

Shell Command



137

138



To stop the HP Output Server servers, type the following command:

stop_server -t all

To stop the MySQL server by typing the following commands:

cd mySQLinstallDir./bin/mysqladmin --defaults-file=mySQLinstallDir/my.cnf

shutdown

where mySQLinstallDir is the location of the MySQL for HP Output Management installation

4. On AIX hosts, run the slibclean command to ensure that library files are not in use.

5. Change to the installation directory for HP Output Server and MySQL for HP Output Management by typing the following command:

cd sharedInstallDir

where sharedInstallDir is the installation directory of HP Output Server and MySQL for HP Output Management.

6. Restore the previous installations of HP Output Server and MySQL for HP Output Management with the backup copy of the files by typing the following command:

zcat fileName.Z | tar -xvf -


7. Start the MySQL server by typing the following commands:

cd mySQLinstallDir./bin/mysqld_safe --defaults-file=mySQLinstallDir/my.cnf

&


start_server -t all


Appendix A

Mounting a Product CD-ROM on UNIX Systems

HP Output Server

This appendix describes how to mount the HP Output Server product CD-ROM on the following supported UNIX operating systems:

• AIX

• HP-UX

• Solaris

• Linux

For more information about the mount command and mounting a CD-ROM, refer to the man pages for your operating system.

Mounting a CD-ROM on an AIX system
To mount the CD-ROM on an AIX system, perform these steps:

2. Find the name of the CD-ROM device by typing the following command:

lsdev -Cccdrom

3. Mount the CD-ROM by typing the following command:

mount -V cdrfs -o ro /dev/name /cdrom

where /dev/name is the device name of the CD-ROM drive.

139

Appendix A Mounting a Product CD-ROM on UNIX Systems

Mounting a CD-ROM on an HP-UX system

Mounting a CD-ROM on an HP-UX system

140

To mount the CD-ROM on an HP-UX system, perform these steps:


2. Find the name of the CD-ROM device by typing the following command:

ioscan -fn -C disk

3. Mount the CD-ROM by typing the following command:

mount -o ro,rr /dev/dsk/name /cdrom

where /dev/dsk/name is the device name of the CD-ROM drive.

Mounting a CD-ROM on a Solaris system
To mount the CD-ROM on a Solaris system, perform these steps:

2. Verify that the Volume Manager is running by typing the following command:

/usr/bin/ps -ef | /bin/grep vold

If the system displays information similar to the following example, the Volume Manager is running.

root 2091 80 Jul23 ? 0:01 /usr/sbin/vold


- If the Volume Manager is running, insert the disc to automount the CD-ROM. You can then view the contents of the disc with the following command:

ls /cdrom

- If the Volume Manager is not running, type the following commands to manually mount the CD-ROM:

mkdir /cdrom/etc/mount -F hsfs -r /dev/name /cdrom

where /dev/name is the device name of the CD-ROM drive, such as /dev/d or /dev/f.



Mounting a CD-ROM on a Linux system


HP Output Server

To mount the CD-ROM on a Linux system, perform these steps:


2. Mount the CD-ROM by typing the following command.

mount /dev/cdrom /mnt/cdrom

where /mnt/cdrom represents where you want to mount the CD-ROM. You can then view the contents of the disc with the following command:

ls /mnt/cdrom

141

142




Appendix B

Using setup.pl in Non-interactive Mode

HP Output Server

You can use setup.pl in non-interactive mode at the command line to install, upgrade, or uninstall HP Output Server on a UNIX host. This appendix describes the syntax for using setup.pl in non-interactive mode. 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 29

• Chapter 3, “Uninstalling HP Output Server” on page 59

• Chapter 4, “Upgrading HP Output Server” on page 63

Syntax
This section describes the syntax for using setup.pl in non-interactive mode for the following tasks:
• Creating a server installation• Creating a client installation• Upgrading an HP Output Server 3.3 server installation• Upgrading an HP Output Server 3.4.1 server installation• Upgrading a client installation• Uninstalling HP Output Server• Using help

143

144

Appendix B Using setup.pl in Non-interactive Mode

Syntax

For a complete list of arguments, see “Arguments” on page 145.

Creating a server installation
To create a server installation of HP Output Server, use the following syntax:
setup.pl [[[-n] -s] [-d installDir] [-o owner] [-H host] [-D domain] [-P port] [-N interface] [-R portRange] [-e] [-M [-C] [-U dbuser] [-W dbpasswd] [-S dbsocket | -V dbhost [-T dbport]]]

NOTE: In non-interactive mode only, the value that you specify for the -o argument automatically sets and overrides any value that you specify for the -U argument.

Creating a client installation
To create a client installation of HP Output Server, use the following syntax:
setup.pl [[[-n] -c] [-d installDir] [-o owner] [-H host] [-D domain] [-P port]]

Upgrading an HP Output Server 3.3 server installation
To upgrade a server installation of HP Output Server 3.3, use the following syntax:
setup.pl [[[-n] -u] [-t tempDir]] [-d installDir] [-e][-M [-U dbuser] [-W dbpasswd] [-S dbsocket | -V dbhost [-T dbport]] [-x]]

Upgrading an HP Output Server 3.4.1 server installation
To upgrade a server installation of HP Output Server 3.4.1, use the following syntax:
setup.pl [[-u [-n]] [-d installDir] [-e] [-x]]

Upgrading a client installation
To upgrade a client installation of HP Output Server, use the following syntax:
setup.pl [[[-n] -u] [-d installDir]]



Arguments

Uninstalling HP Output Server

HP Output Server

To uninstall HP Output Server, use the following syntax:

setup.pl [[[-n] -r] [-d installDir]]

Using help
To view information about using setup.pl, type the following:
setup.pl -h|-?

Arguments
The following table describes the arguments for running setup.pl in non-interactive mode.
Argument Description

-n No prompts.

-c Install client package.

-s Install server package.

-u Upgrade existing installation.

-r Remove (uninstall) existing installation.

-d installDir Base installation directory (default: /opt/hpom).

-t tempDir Temporary directory for database migration (default: installDir/dbupgrade).

-o owner Owner of the installed files and pre-configured server processes (default: dazel). In non-interactive mode only, the value you specify for this argument when creating a server installation of HP Output Server automatically sets and overrides any value that you specify for the -U dbuser argument.

-H host Name of the host running the NM server (default: this host).

-D domain HP Output Server domain name (default: host.d).

-P port Port number of the NM server (default: 4009).

-N interface Server processes should listen only on the network interface specified (default: all interfaces).

145

146


Arguments

-R portRange TCP ports available for server processes (default: 1-65535).

-M Configure the connection to MySQL.

-C Create default primary servers and one of each delivery server (ignored if -s is not specified).

-e Stop the servers after install or upgrade.

-U dbuser Database administrator user name (default: dazel).

-W dbpasswd Database administrator password (no default).

-S dbsocket File socket on the local host where the database is listening; assumed if -V is not specified (default: installDir/var/mysql/mysql.sock).

-V dbhost Name of remote host where database is running. The value cannot refer to a local interface (no default).

-T dbport TCP port on the remote host where the database is listening (default: 3306).

-x Invoke the Dazel Output Distributor od20_cleanup.pl cleanup utility after the HP Output Distributor data migration is successful. The utility removes old Dazel Output Distributor files which will no longer be used.

Argument Description


Appendix C

Environment Variables in HP Output Server

HP Output Server

This appendix lists HP Output Server environment variables, their settings, and describes methods for setting environment variables in HP Output Server.

Environment variables
When you install HP Output Server, the following files are created:
• installDir/etc/setup_env.sh (a Bourne/Korn shell file)

• installDir/etc/setup_env.csh (a C shell file)

• installDir/etc/setup_env.pl (a Perl file)

• installDir/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.

147

Appendix C Environment Variables in HP Output Server


UNIX environment variables

148

The following tables list environment variables that are set on UNIX platforms.Table C-1. Environment variables for all UNIX platforms

Variable Setting

DAZEL_HOME installDir

(the HP Output Server installation 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 F, “HP Output Server in a Multi-NIC Environment” on page 169, or contact Customer Support.

DAZEL_PORTS Set to control which port numbers a server process will use. For more information, see Appendix E, “Firewall Support” on page 165.

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 (]).

NLSPATH Prepend:

installDir/nls/cat/%L/%N :installDir/nls/oid/%L/%N

PATH Prepend:

installDir/bin

MIBS ALL

MIBDIRS installDir/share/snmp/mibs

ENSCRIPT_LIBRARY installDir/share/enscript

PERL5LIB Prepend:

installDir/lib/perl5:installDir/lib/perl5/site_perl


HP Output Server



MANPATH Prepend:

installDir/man

Table C-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, refer to “Selecting a different language on a UNIX host” on page 108.

LD_LIBRARY_PATH* If not already preset in LD_LIBRARY_PATH, also prepend:

installDir/lib:/user/lib/lwp:/usr/lib

* 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 C-3. Environment variables for AIX platforms

Variable Setting

LANG en_US


LIBPATH Prepend:

installDir/libIf not already preset in LIBPATH, also prepend:

/usr/lib

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

Variable Setting

149

150



Table C-4. Environment variables for HP-UX platforms

Variable Setting

LANG C


SHLIB_PATH Prepend:

installDir/lib

Table C-5. Environment variables for Linux platforms

Variable Setting

LANG C

If you plan to run HP Output Server on a non-English version of Linux, refer to “Selecting a different language on a UNIX host” on page 108.

LD_LIBRARY_PATH Prepend:

installDir/lib

Windows environment variables
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 C-6. Windows environment variables

Variable Setting

DAZEL_HOME installDir

(the HP Output Server installation 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 F, “HP Output Server in a Multi-NIC Environment” on page 169.


HP Output Server



DAZEL_PORTS Set to control which port numbers a server process will use. For more information, see Appendix E, “Firewall Support” on page 165.

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 (]).

PATH Prepend:

installDir\bin

MIBS ALL

MIBDIRS Prepend:

installDir/share/snmp/mibs

ENSCRIPT_LIBRARY installDir/share/enscript

PERL5LIB Prepend:

installDir/lib/perl5;installDir/lib/perl5/5.8.1/lib;installDir/lib/perl5/site/5.8.1/lib

Table C-6. Windows environment variables (continued)

Variable Setting

151


Setting environment variables in HP Output Server


152

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 F, “HP Output Server in a Multi-NIC Environment” on page 169.

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,...*

* Use this operator with the config_host -u or config_server -u construction only.

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

--attribute value,... * This removes the value,... from attribute.


HP Output Server



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 installation’s 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\""

config_server -u -t delivery -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 configuration’s 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\""

• 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.

153

154



The following example sets DAZEL_PORTS on all of a configuration’s delivery servers to 40000-40200:

config_server -u -t delivery -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:

config_server -u -t delivery -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 system’s Control Panel to set environment variables.


Appendix D

Configuring the HP Output Server LPR Gateway

HP Output Server

This appendix describes how to configure the HP Output Server LPR Gateway. 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.

To configure the LPR Gateway, complete the following tasks:

1. Disable the existing print spooler.

2. Create a server for the LPR Gateway.

3. Configure output devices.

4. Authorize remote hosts to use the LPR Gateway.

5. Configure remote hosts to use the LPR Gateway.

Use the following instructions to complete each task. For more information about using the LPR Gateway, see the System Administrator’s Guide for HP Output Server.

155

Appendix D Configuring the HP Output Server LPR Gateway

Disabling the existing print spooler


156

Disabling the existing print spooler on the host prevents any conflicts with the LPR Gateway. As a replacement for the line printer daemon on UNIX and the print spooler service on Windows, the LPR Gateway listens for requests on the same port as other print spoolers. This can cause a conflict between two background processes (daemons) or services if the existing print spooler is not disabled.

CAUTION: If you attempt to configure an LPR Gateway server before disabling the native print spooler, the LPR Gateway process does not run properly.

To recover from this situation, do the following:

1. Disable the native print spooler using the instructions in the following sections.

2. Delete the entry for the LPR Gateway in the NM:

nmcp delete ids,hosts,lpg

3. Use the config_server command to configure the LPR Gateway.

Disabling the print spooler on UNIX
The LPR Gateway replaces the standard print spooler on UNIX, which is called the line printer daemon or lpd process. Before you create and configure the LPR Gateway, disable the existing line printer daemon on the host. This allows the LPR Gateway to exclusively listen for requests on port 515—the standard, assigned port for the line printer daemon. If the line printer daemon on the host is assigned a different port number, change the /etc/services file accordingly or configure the LPR Gateway to use a different port number.
The following sections describe how to disable the line printer daemon on different UNIX platforms. You must be the root user to perform these actions.

AIX
To disable a running line printer daemon on an AIX host, type the following command:
stopsrc -s lpd

To disable the line printer daemon so that it does not automatically start when the machine reboots, comment out the following line from the /etc/rc.tcpip file:

start /usr/sbin/lpd "$ src_running"

To comment out a line, add the number character (#) at the beginning of the line.




HP-UX

HP Output Server

To disable a running line printer daemon on an HP-UX host, complete the following steps:

1. Find the process ID (PID) for the inetd program by typing the following command:

/bin/ps -elf | grep inetd

2. Send the inetd program a hangup signal to have the program re-read its configuration file by typing the following command:

kill -SIGHUP 123

where 123 represents the PID for the inetd program.

3. Find the PID for the rlpdaemon program by typing the following command:

/bin/ps -elf | grep rlpdaemon

4. Send the rlpdaemon program a terminate signal to stop the daemon from running by typing the following command:

kill -SIGTERM 456

where 456 represents the PID for the inetd program.

5. Stop the print spooler by typing the following command:

/usr/sbin/lpshut

To disable the line printer daemon so that it does not automatically start when the machine reboots, comment out the following line from the /etc/inetd.conf file:

printer stream tcp nowait root /usr/lib/rlpdaemon rlpdaemon -i


Solaris
To disable a running line printer daemon on a Solaris host, complete the following steps:
1. Determine if the network listener service is configured to receive line printer daemon print requests by typing the following command:

/usr/sbin/nlsadmin -v tcp

157

158



If the host displays text similar to the following, the network listener service has been configured to accept line printer daemon requests:

lp NOADDR ENABLED NORPC root NOMODULES /var/spool/lp/fifos/listenS5#

lpd \x00020203000000000000000000000000ENABLED

NORPC root NOMODULES /var/spool/lp/fifos/listenBSD

# 0 \x00020ACE000000000000000000000000ENABLEDNORPC root NOMODULES /usr/lib/saf/nlps_server

2. Temporarily stop the network listener service for all TCP requests by typing the following command:

/usr/sbin/nlsadmin -k tcp

3. Stop the print spooler by typing the following command:

/usr/sbin/lpshut

To disable the line printer daemon so that it does not automatically start when the machine reboots, complete the following steps:

1. Look for a directory called /etc/saf/tcp. If the directory exists, rename the directory. For example: /etc/saf/notcp.

2. Change directories to the /etc/rc2.d directory by typing the following command:

cd /etc/rc2.d

3. Look in the /etc/rc2.d directory for a file beginning with an S and ending with an lp, for example S80lp. In this file, comment out the following line:

[ -f /usr/lib/lpsched ] && /usr/lib/lpsched


Disabling the print spooler on Windows
The LPR Gateway is a replacement for the print spooler service on Windows, a service that is compatible with the UNIX line printer daemon. Before you create and configure the LPR Gateway on a Windows host, disable the existing print spooler to allow the LPR Gateway to exclusively listen for requests on port 515. If the print

HP Output Server


Creating a server for the LPR Gateway

spooler on the host is assigned a port number other than 515, change the %WINDIR%\system32\drivers\etc\services file accordingly or configure the LPR Gateway to use a different port number.

To disable the print spooler service on a Windows host, complete the following steps:


2. Open the Services window.

3. Double-click Print Spooler.

4. In the Print Spooler Properties (Local Computer) dialog box, click Stop. This stops the service from running.

5. In the Startup type list, select Disabled.

6. To save the changes and disable the default Windows print spooler, click OK.

Creating a server for the LPR Gateway
When you install HP Output Server, you may choose to create primary and delivery servers as a part of the installation process. The installation process, however, does not automatically create the LPR Gateway. You use the config_server command to create a server for the LPR Gateway. This configures a background server process to handle incoming line printer daemon requests for HP Output Server.
To create a server for the LPR Gateway, complete the following steps:

1. If you have not already done so, log in as the root user or an administrator user.


3. Create a server for the LPR Gateway.

config_server -t lpg lpgName

where lpg is the type of server and lpgName is the name of the server. This command creates a server of the type lpg. If you do not name the server, the default name is lpg.

Shell Command



159


Configuring output devices


160

HP Output Server requires a printcap file so that you can configure the output devices you want to use with the LPR Gateway. This file makes it possible to configure line printer spooling. The file contains an entry for each output device you want to make available to the LPR Gateway.

HP Output Server installs the file by default in the installDir\etc directory on Windows hosts. On a UNIX host, you must create the printcap file manually and place it in installDir\etc.

NOTE: The HP Output Server LPR Gateway requires a printcap file to implement LP destinations and is independent of any operating system-specific requirements for implementing LP destinations.

The printcap file uses the same syntax as found in the standard printcap printer capability database.

Entries in the printcap file
An entry in the printcap file details the name of the device, its spooling directory, and any desired capabilities. The following example configures two output devices for the HP Output Server LPR Gateway.
lp1:LaserPrinter:\:lp=lprn1:sd=/var/spool/lp1lp2:Fax:\:lp=lfax1:sd=/var/spool/lp2

In the preceding example, the lp1 device forwards incoming job requests to the lprn1 logical destination at the HP Output Server. The entry configures the device to use the /var/spool/lp1 directory to store jobs during processing. The entry for the lp2 device forwards incoming requests to the lfax1 logical destination. The second entry configures the /var/spool/lp2 directory as the spool directory for the device.

When you create or modify the printcap file, make sure that the entries in the file do not end with a blank space or a tab. The LPR Gateway is not able to correctly recognize such entries.


HP Output Server



The LPR Gateway supports the capabilities shown in the following table. The LPR Gateway ignores the standard printcap capabilities that do not appear in the table.

Table D-1. printcap capabilities

Capability Type Example Value Description

dz string -fax-to-person Bob Specifies additional job attributes on a per-printer basis.

hl Boolean false Prints a job sheet after the document.

if string /usr/bin/expand Gives the absolute path name to a command, program, or script that processes the document and returns the results to HP Output Server for further processing.

lo string lock Specifies the lock file that is created in the spool directory.

lp string lfax1 Provides the name of the logical destination to which jobs are sent.

mc number 10 Determines the maximum number of copies per job. A value of zero indicates an unlimited number of copies.

mx number 10000 Sets the maximum size of a document (in 512 byte blocks) per job. A value of zero indicates an unlimited size.

of string full Identifies the type of job sheet to use: full, brief, blank, or none. In conjunction with the hl capability, this capability determines whether the job sheet prints before or after the document.

rg string prog Limits access to the LPR Gateway to the members of the specified UNIX or Windows group. This capability is used in conjunction with the rs capability.

rm string rocky Provides the name of a remote host that forwards jobs to the LPR Gateway. Jobs are sent to the destination that is specified by the rp capability.

rp string lfax1 If the lp capability is not set and the rm capability is set to the local host name, this value provides the name of the logical destination to which jobs are sent.

rs Boolean false Limits access to the LPR Gateway to UNIX or Windows users who have an account on the local machine.

sc Boolean true When set to true, multiple copies are prohibited.

161



sd string installDir/var/lpg1 Sets the name and location of the spool directory.

sh Boolean false When set to true, turns off the printing of a job sheet.

Table D-1. printcap capabilities (continued)

Capability Type Example Value Description

162

For more information about using the HP Output Server LPR Gateway, see the System Administrator’s Guide for HP Output Server.

Use of an input filter for an output device
An input filter is a special type of capability you can specify for an output device. An input filter is a mechanism that reads and writes data from standard input to standard output each time a job is sent to a particular destination. An input filter is similar to an HP Output Server user filter; however, an input filter does not handle arguments that are part of the command, program, or script that runs whenever a job is submitted.
You use an input filter by including the if capability in the printcap entry for an output device. You use an absolute path name to indicate the name and location of the command, program, or script as well as an absolute path name for the name and location of the spool directory. The following example uses an absolute path for the example command and for the spool directory, which is defined as the /var/spool/lpd directory:

lp3:PrinterwithFilter:\:lp=lprn3:sh=true:of=none:if=/usr/local/bin/example:sd=/var/spool/lpd

Whenever a job is sent to the lp3 destination, the example command reads the contents of the file and then performs some type of requested operation, such as include a default copyright notice in the file or reformat the dates that appear in the file. After processing the file, the filter writes the transformed contents back to standard output and forwards the file to HP Output Server for further processing.

For more information about the transformation process, including transformers, user filters, and user exits, refer to the System Administrator’s Guide for HP Output Server.


HP Output Server


Authorizing remote hosts to use the LPR Gateway

When you use an input filter with the LPR Gateway, the LPR Gateway returns one of three codes:

• Error code 0 indicates success.

• Error code 69 indicates success, but the print job is terminated. This code does not indicate an error condition. Instead, the filter has determined that the job should not be printed for some reason or because of a policy mechanism.

• Any other returned code indicates an error condition.

Any failure in the filtering process also terminates the print job.

Authorizing remote hosts to use the LPR Gateway
You can configure the host that runs the LPR Gateway to accept jobs that are sent from remote hosts. This makes it possible for users to submit jobs to output devices in an HP Output Server domain. To authorize remote hosts, you grant permission to the hosts that can use the LPR Gateway. You add the host name and IP address for each remote host to the hosts.lpd file on the machine that runs the LPR Gateway. Adding a host name and an address to this file allows the remote host to connect to the LPR Gateway and submit jobs.
On UNIX hosts, the hosts.lpd file is located in the /etc directory. On Windows hosts, the file is in the etc directory within the HP Output Server installation directory (installDir\etc). The hosts.lpd file lists remote systems that have permission to print on the local system.

To grant a remote host permission to use the LPR Gateway, add a line to the hosts.lpd file. For example:

myhost

The above example adds an entry to the hosts.lpd file that grants a host machine called myhost permission to submit jobs through the LPR Gateway. On AIX hosts, you may need to add a plus sign (+) in front of the entry. For example:

+myhost

The plus sign grants all users on the host permission to submit jobs to the LPR Gateway.

163


Configuring remote hosts to use the LPR Gateway

Configuring remote hosts to use the LPR Gateway

164

Before a remote host can submit jobs to the LPR Gateway, you must configure the remote host to forward job requests to the LPR Gateway. You update the printcap file on the remote host and change the entries in the file to redirect requests to the host machine on which the LPR Gateway runs. For example, the following entries define two output devices that send requests to the LPR Gateway:

my_lp1:LaserPrinter:\:rm=lpgdhost:rp=lp1:sd=/var/spool/lp1

my_lp2:Fax:\:rm=lpgdhost:rp=lfax1:sd=/var/spool/lp2

The my_lp1 device forwards the jobs it receives to the lp1 output device on the host machine that runs the LPR Gateway (lpgdhost). The my_lp2 device forwards the jobs it receives to the lp2 output device.


Appendix E

Firewall Support

HP Output Server

This appendix describes firewall support in HP Output Server. With this implementation in place, a client program on one side of a company’s 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 company’s 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:

165

166

Appendix E 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 C, “Environment Variables in HP Output Server” on page 147.
To specify a server’s port number or range of numbers, complete these steps:

1. Stop HP Output Server and its servers by typing the following command:

stop_server -t all

2. Ensure that all servers have been stopped by typing the following command:

server_status

3. Specify a server’s port number or range of numbers with the config_server command.

The following command sets DAZEL_PORTS on all of an installation’s delivery servers:

config_server -u -t delivery -x"-server-environment-variables \"DAZEL_PORTS=40000-40100\""


HP Output Server



4. Start HP Output Server by typing the following:

start_server -t all

5. Verify that the servers are listening on 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. Start other processes.

167

168




Appendix F

HP Output Server in a Multi-NIC Environment

HP Output Server

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 HP Output Server 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 an LPR Gateway even though the domains physically reside on the

169

170

Appendix F HP Output Server in a Multi-NIC Environment

Configuring multiple instances of HP Output Server to use the same network interface

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.


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.


HP Output Server



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 29.

If you are upgrading HP Output Server and want to restrict communication to a specific interface, you must follow these manual steps. These steps assume that you have upgraded to HP Output Server 3.5.

NOTE: Ensure that you use the same value for newHostName in all steps of the following procedure. You can use a host name only.

1. Log in as the root user or a user with administrator privileges.

2. Depending on the shell, source your environment file by changing to the installDir/etc directory and typing one of the following commands:

3. Stop all programs that monitor the HP Output Server instance you want to change. If the HP Output Server domain is on multiple hosts, ensure that you stop monitoring processes on all systems.

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 OpenView and dzl_epod monitor HP Output Server processes and should be stopped before you start this procedure.

NOTE: Monitor programs are not restarted automatically; you must start these programs manually.

4. Stop all HP Output Management applications 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, refer to the documentation for your HP Output Management applications.

If the HP Output Server domain is on multiple hosts, ensure that you stop the HP Output Management applications on all systems.

Shell Command

C source ./setup_env.csh

Bourne or Korn . ./setup_env.sh

171

172



5. Stop all HP Output Server processes:

stop_server -t all

6. To specify the host name of the interface you want to use for communication, use the config_host command. Using the config_host -u -f construction recreates the setup_env* files, overwriting any customizations to your setup scripts. Depending on your configuration, you will use one of the following constructions:

- If the NM resides on the local HP Output Server instance, type the following command. If you do not specify an nmPort number, the default of 4009 is used. To specify an NM port number that is different from 4009, you must include a value.

config_host -u -f -x"-host-name newHostName -dazel-nm-host newHostName[nmPort]"

- If the NM resides on a different HP Output Server instance, type the following command:

config_host -u -f -x"-host-name newHostName"

7. Change to the HP Output Server installDir/etc directory:

cd installDir/etc

8. Set the DAZEL_HOSTNAME environment variable in all of your setup_env* files. These files have the following extensions: .sh, .csh, .pl, .bat (Windows only).

You must include this setting in all of these files even if you do not use them in your day-to-day operations.

Open a text editor and include the DAZEL_HOSTNAME environment variable setting at the end of each file as follows, remembering that the value of DAZEL_HOSTNAME must match your setting for -host-name in step 6:

- For the setup_env.sh file, add the following two lines:

DAZEL_HOSTNAME=newHostName export DAZEL_HOSTNAME

- For the setup_env.csh, add the following line, ensuring that you do not include an equal sign:

setenv DAZEL_HOSTNAME newHostName

- For the setup_env.pl file, add the following line, remembering to include the semicolon:

$ENV{DAZEL_HOSTNAME} = "newHostName";


HP Output Server



- For the setup_env.bat file on Windows, add the following line:

set DAZEL_HOSTNAME=newHostName

NOTE: You must complete step 6 for your setup_env* files even if you do not use these files.

Using the config_host -u -f construction in step 6 recreates the setup_env* files, overwriting any customizations to your setup scripts, including the DAZEL_HOSTNAME setting. If you use the config_host -u -f construction after changing DAZEL_HOSTNAME (and want to continue to use the DAZEL_HOSTNAME setting), you must repeat this step.

9. On Windows only, set DAZEL_HOSTNAME as a system environment variable by doing the following:

- Open the System control panel.

- Click on the Advanced tab and select Environment Variables.

- In the Variable Name box, type DAZEL_HOSTNAME.

- In the Variable Value box, type the name of the new host name (newHostName).

- To exit and apply your changes, click OK in each of the opened dialog boxes.

10. To set DAZEL_HOSTNAME on other machines, repeat steps 1 through 9.

11. Because you changed the environment, you must source the environment file again. From the installDir/etc directory, type one of the following commands:

12. Restart all processes.

Shell Command



173


Changing the host name throughout the configuration

Changing the host name throughout the configuration

174

If the NM resides on the local HP Output Server instance and you changed the -dazel-nm-host attribute in step 6 in the previous procedure, 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. Depending on the shell, source your environment file by changing to the installDir/etc directory and typing one of the following commands:

3. Type 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, refer to the documentation for your HP Output Management applications.

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.

Shell Command





Restoring communication on all network interfaces

Restoring communication on all network interfaces

HP Output Server

To restore communication on all network interfaces on a machine, follow the steps in “Configuring multiple instances of HP Output Server to use the same network interface” on page 170 with the following exceptions:

• Substitute the machine hostName for newHostName. To see the machine host name, type hostname.

• Skip step 8. This step sets DAZEL_HOSTNAME in the setup_env* files. Because the config_host command in the previous step recreates these files, no further editing is required. Additionally, if your system includes an interface with the same name as the host, setting DAZEL_HOSTNAME in the setup_env* files will restrict communication to that interface.

• For step 9 on Windows, delete the DAZEL_HOSTNAME system environment variable.

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 /etc/locks/lpd.

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

175

176


Configuring multiple LPR Gateway servers in a multiple NIC environment (UNIX only)


Appendix G

Configuring the MySQL Connection

HP Output Server

If you installed HP Output Server without configuring the connection to the MySQL server, use the config_host command to set up the connection between HP Output Server and MySQL 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 MySQL connection using the config_server command and the -database-server* attributes. For more information about using the config_server command, see the System Administrator’s Attribute Reference for HP Output Server. For more information about using the -database-server* attributes, see the System Administrator’s Attribute Reference for HP Output Server.

HP Output Server and MySQL on the same host
In the following example, HP Output Server communicates with MySQL as root and with the password set to dazel. In this example, HP Output Server and MySQL for HP Output Management are installed 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.

177

178

Appendix G Configuring the MySQL Connection

HP Output Server and MySQL on separate hosts

2. If HP Output Server is installed on a UNIX host, enter a command from the following table to source the HP Output Server environment variables:

3. Set the -database-server* attributes on the HP Output Server host as follows:

On UNIX:

config_host -u -x"-database-server-user root -database-server-password dazel -database-server-socket mySQLinstallDir/socket"

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

On Windows:

config_host -u -x"-database-server-user root -database-server-password dazel -database-server-hostname localhost -database-server-port port"

where port is the port number on which the MySQL server is listening, for example, 3306

4. Configure your servers using the config_server command. For more information, see the System Administrator’s Command Reference for HP Output Server.

Shell Command



In the following example, HP Output Server communicates with MySQL as root and with the password set to dazel. In this example, the MySQL server is installed on a separate host named tiger and listening on port 3306.
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.


HP Output Server



2. If HP Output Server is installed on a UNIX host, enter a command from the following table to source the HP Output Server environment variables:

3. Set the -database-server* attributes on the HP Output Server host as follows:

config_host -u -x"-database-server-user root -database-server-password dazel -database-server-hostname tiger -database-server-port 3306"

4. Configure your servers using the config_server command. For more information, see the System Administrator’s Command Reference for HP Output Server.

Shell Command



179

180




Appendix H

HP Output Distributor 2.0 Clean-up Utility

HP Output Server

This appendix describes how to use the HP Output Distributor 2.0 clean-up utility (od20_cleanup.pl). The clean-up utility removes the HP Output Distributor 2.0 database files and binaries located in installDir after data is migrated successfully from the HP Output Distributor 2.0 database to MySQL for HP Output Management. If you upgraded to HP Output Server 3.5 with an existing installation of HP Output Distributor 2.0, you can choose to have the upgrade script invoke the clean-up utility as part of the HP Output Distributor upgrade, or you can run the script manually after a successful upgrade.

NOTE: If data migration for HP Output Distributor 2.0 fails during an upgrade, the upgrade script will not invoke the clean-up utility, even if you specified it as an option during upgrade. After successfully performing data migration, you must run the clean-up utility manually if you want to remove files that are no longer used by HP Output Distributor.

To run the od20_cleanup.pl utility manually, perform the following steps:

1. Log in as root (on UNIX) or a user with administrator privileges (on Windows) on your machine.

2. Change directories to the location of the od20_cleanup.pl utility by typing the following command:

cd installDir/etc

181

182

Appendix H HP Output Distributor 2.0 Clean-up Utility


4. Run the clean-up utility by typing the following command:

perl od20_cleanup.pl

5. When prompted to delete the unused HP Output Distributor 2.0 files, accept the default (y).

Shell Command




Appendix I

HP Output Distributor 2.0 Data Migration Utility

HP Output Server

This appendix describes how to use the HP Output Distributor 2.0 data migration utility (hpod_dmutil.pl). If data migration for an existing installation of HP Output Distributor 2.0 fails during an upgrade of HP Output Server, you must correct the problem specified in the log file for data migration and run the data migration utility manually.

To run the hpod_dmutil.pl utility from the command line, perform the following steps:

1. Log in as root (on UNIX) or a user with administrator privileges (on Windows) on your machine.

2. Change directories to the location of the hpod_dmutil.pl utility by typing the following command:

cd installDir/etc


Shell Command



183

184

Appendix I HP Output Distributor 2.0 Data Migration Utility

4. To run the hpod_dmutil.pl utility, type the following command:

perl hpod_dmutil.pl

5. When prompted for the temporary path for data migration, accept the default or type the path. The default is installDir/dbupgade/oddm.

6. When prompted for the MySQL administrator user name, accept the default or type the name. The default is root.

NOTE: The MySQL administrator user name can contain only simple ASCII characters and must not exceed 32 characters. Do not use accented characters, single or double quotes, spaces, backslashes, back tics, commas, or special symbols.


- If your MySQL installation has an administrator password, accept the default. The default is (y).

When prompted for the password, type the password. The setup script does not provide a default value.

NOTE: The password can contain only simple ASCII characters and must not exceed 32 characters. Do not use accented characters, single or double quotes, spaces, backslashes, back tics, commas, or special symbols.




- If your MySQL server is installed on this host, accept the default (1).

When prompted for the path to the MySQL file socket, accept the default or type the absolute path. The default is /usr/local/mysql/mysql.sock. If you are connecting to a MySQL server on the local host, you must use the file socket.




HP Output Server



9. Review the data migration options. If any are incorrect, type n and correct the options. If the options are correct, type y.

All log messages for hpod_dmutil.pl are located in installDir/var/log/hpod_dmutil.log.

185

186



Appendix J

configod.pl Script

HP Output Server

During the installation of a default set of servers for HP Output Server, and during an upgrade of 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 installDir/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 completes 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.

187

188

Appendix J configod.pl Script

Using help

During an upgrade of a server installation of HP Output Server where HP Output Distributor 2.0 is installed, the setup program upgrades the existing templates for creating HP Output Distributor logical and physical destinations. If the setup program fails to update the templates, you can run the configod.pl script with the -u argument after the installation completes to upgrade the templates.

The configod.pl script is located in installDir/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, type 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

Removing templates for HP Output Distributor
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

Upgrading templates for HP Output Distributor
To upgrade 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 -u


Index

Aauthentication 109authentication mode 109authorization 109, 110

CCD-ROM, mounting 139config_host command 172configod.pl script 187configuration, documentation for setup xiiiconfiguring

HP Output Server 107MySQL connection

on UNIX 32on Windows 46

servers in HP Output Server 108-copy-from attribute 116cover sheets, customizations 65customer support xvicustomizations, file 64

DDazel ID mode 109

HP Output Server

dazel_admin group 110dazel_appl group 110dazel_guest group 110DAZEL_HOME environment variable 148, 150DAZEL_HOSTNAME environment variable 148,

150, 169DAZEL_PORTS environment variable 148, 151,

165dazel_server group 110dazel_superuser group 110dazel_support group 110dazel_user group 110-dazel-nm-host attribute 172DAZELNS environment variable 148, 151delivery objects, customizations 64delivery pathway, creating 113Destination Manager 115disk space, HP Output Server 6DPAOIDs, customizations 64dz capability 161

EENSCRIPT_LIBRARY environment variable 148,

151

189

Index

environment variableson UNIX 148on Windows 150setting in HP Output Server 108, 152

error codes, LPR Gateway 163

Ffiles

customizations 64upgrading on UNIX 76

firewall support 165

Ggroup authorization. See authorizationgroups

dazel_admin 110dazel_appl 110dazel_guest 110dazel_server 110dazel_superuser 110dazel_support 110dazel_user 110

Hhardware requirements, HP Output Server 6hl capability 161host name, specifying for communication 172-host-name attribute 172hosts.lpd file 163hotfixes

installingon UNIX 98on Windows 103

removingon UNIX 100on Windows 104

HP Output Distributor clean-up utility 181HP Output Distributor data migration utility 183HP Output Server documentation, CD-ROM contents

4

190

HP Output Server, CD-ROM contents 3hpod_dmutil.pl 183

Iif capability 161, 162input filter 162installation, documentation for setup xiiiinstalling

hotfixeson UNIX 98on Windows 103

HP Output Serveron non-English Windows host 25on UNIX 32on Windows 46options 29planning on a network 25

interdomain delivery 112interface

restoring communication 175restricting communication 170

JJob And Queue Manager (JQM) 114

Kkernel parameters

recommended on HP-UX 10recommended on Solaris 16setting on HP-UX 14setting on Solaris 17

LLANG environment variable 149, 150language, selecting on a UNIX host 108LD_LIBRARY_PATH environment variable 149,

150LIBPATH environment variable 149


Index

line printer daemondisabling on AIX hosts 156disabling on HP-UX hosts 157disabling on Solaris hosts 157disabling on Windows hosts 159

lo capability 161lock file 175logical destination

creating 117definition 113templates 115, 117

lp capability 161lpd process 156-lpg-masterlock attribute 175LPR Gateway

authorizing remote hosts 163configuring in a multi-NIC environment 169,

175configuring remote hosts 164creating a server 159defined 112defining output devices 160definition 155error codes 163overview of configuration 155port assignment 156

M-managing-server attribute 114MANPATH environment variable 149mc capability 161memory, HP Output Server 6MIBDIRS environment variable 148, 151MIBS environment variable 148, 151mounting, CD-ROM

on AIX 139on HP-UX 140on Linux 141on Solaris 140

multi-host domain, upgrade 75

HP Output Server

multi-NIC environmentconfiguring HP Output Server 170configuring the LPR Gateway 175

mx capability 161MySQL for HP Output Management, CD-ROM

contents 2

Nnetwork interface cards 169NLSPATH environment variable 148

Ood20_cleanup.pl 181of capability 161operating systems

kernel parameters 9required patches 7supported platforms, HP Output Server 7

output device, configuration for the LPR Gateway 160

PPATH environment variable 148, 151PERL5LIB environment variable 148, 151permissions 110physical destination

creating 118definition 113templates 115, 118

prerequisites for upgrading 69print spooler

on UNIX 156on Windows 158

printcap fileexample entries 160, 164remote host 164restrictions 160supported capabilities 160

printer port 156

191

Index

Qqueue

creating a 117definition 113templates 115, 117

Rrestoring files, backup template customizations 85rg capability 161rlp daemon program 157rm capability 161rp capability 161rs capability 161

Ssc capability 161sd capability 162setup.pl, using non-interactively 143setup_env* files 172setup_env.bat 147setup_env.csh 147setup_env.pl 147setup_env.sh 147sh capability 162SHLIB_PATH environment variable 150

192

support xvi

Ttemplates

definition 115logical destination 115, 117physical destination 115, 118queue 115, 117

training xvitypographic conventions xv

Uuninstalling

hotfixeson UNIX 100on Windows 104

HP Output Serveron UNIX 60on Windows 62

UNIX ID mode 109upgrade

multi-host domain 75UNIX 76

user authentication. See authenticationuser filter 162


Installation and Configuration Guide 3.5

Documents

Transcript of Installation and Configuration Guide 3.5