columbus om installation configuration

Columbus OMInstallation and Configuration

5.000

Publication numberUQCO-5000-01 (September 2012)

Information in this publication is subject to change. Changes will be published in new editions or technical newsletters.

Documentation setThis is the only manual for this product.

Copyright noticeColumbus OM (the Programs and associated materials) is a proprietary product of Macro 4 Limited a division of UNICOM Global. The Programs have been provided pursuant to License Agreement containing restrictions on their use. The programs and associated materials contain valuable trade secrets and proprietary information of Macro 4 Limited and are protected by United States Federal and non-United States copyright laws. The Programs and associated materials may not be reproduced, copied, changed, stored, disclosed to third parties, and distributed in any form or media (including but not limited to copies on magnetic media) without the express prior written permission of Macro 4 Limited, The Orangery, Turners Hill Road, Worth, Crawley, West Sussex, RH10 4SS, U.K.

Columbus OM Copyright 1995-2012 All Rights Reserved. Macro 4 Limited a division of UNICOM Global.

No part of this Program may be reproduced in any form or by electronic means, including the use of information storage and retrieval systems, without the express prior written consent and authorization of Macro 4 Limited.

No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, without prior written permission from Macro 4 Limited.

DisclaimerWe cannot guarantee freedom from, or assume any responsibility or liability for technical inaccuracies or typographical errors. The information herein is furnished for informational use only and should not be construed as a commitment by Macro 4 Limited a division of UNICOM Global.

Trademark acknowledgementsThe following is a trademark of Macro 4 Limited or of UNICOM Global: Columbus OM.

SAP and R/3 are trademarks or registered trademarks of SAP AG in Germany and in several other countries.

Product and company names mentioned herein may be the trademarks or registered trademarks of their respective owners.

3Upgrading Columbus OM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Uninstalling Columbus OM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 3 Columbus OM utilities . . . . . . . . . . . . . . . . . . . . . . . . . 55Columbus OM Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

IOP Universal Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Columbus Windows Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

IOP Messenger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Contents

Columbus OM Installation and Configuration UQCO-5000-01

About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

New features in Columbus OM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Overview of a Columbus OM output management environment . . . . . . . . . . . . 16

Configuration functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 2 Installing Columbus OM . . . . . . . . . . . . . . . . . . . . . . . 23Preparing to install Columbus OM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Installing Columbus OM (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installing a Columbus Intelligent Office Printing (IOP) deployment . . . . . . . . . . 37

Installing Columbus OM (UNIX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring Columbus OM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Starting Columbus OM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Using Columbus OM in a VMWare environment . . . . . . . . . . . . . . . . . . . . . . . . 50COLUMBUS OM INSTALLATION AND CONFIGURATION

IOP desktop components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Columbus OM PC Printer Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Columbus OM Novell Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

CONTENTS4Chapter 4 Managing servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95Server types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Adding servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Configuring servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Starting servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Stopping servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Monitoring servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Chapter 5 Configuring a Columbus OM printing environment . . .107Setting parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Configuration for local printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Configuration for distributed printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Chapter 6 Setting up printers . . . . . . . . . . . . . . . . . . . . . . . . . . .129Adding printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Changing the properties of printers from the command line . . . . . . . . . . . . . . . 145

Managing print servers from the command line . . . . . . . . . . . . . . . . . . . . . . . . . 146

Managing printer servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Defining printer types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Defining paper types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Creating printer classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Creating printer groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Chapter 7 Configuring the printer features . . . . . . . . . . . . . . . . .163Configuring the printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Controlling the documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Supported document formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Applying overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Printing banner pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Formatting documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Assured delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Handling documents that fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Processing documents in batches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Chapter 8 Using the xprinter driver . . . . . . . . . . . . . . . . . . . . . .185Devices supported by xprinter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Configuring a printer to use the xprinter driver . . . . . . . . . . . . . . . . . . . . . . . . . 188

xprinter delivery modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Banner pages for xprinter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Monitoring entries submitted to xprinter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Example configurations for xprinter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198COLUMBUS OM INSTALLATION AND CONFIGURATION

CONTENTS 5Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202

Chapter 9 Adding entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Adding entries by using Columbus OM Explorer . . . . . . . . . . . . . . . . . . . . . . . .212

Adding entries from the command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216

Intercepting the lp and lpstat commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224

Converting lpr/lpd requests to Columbus OM print entries . . . . . . . . . . . . . . . .227

Transferring documents from other hosts into Columbus OM. . . . . . . . . . . . . .232

Processing files in scanned folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238

Chapter 10 Managing entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Displaying entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242

Changing entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255

Resubmitting documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257

Restarting documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259

Deleting entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264

Chapter 11 Managing queues . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Displaying the queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266

Increasing the capacity of the queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Reducing the capacity of queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268

Maintaining queue integrity and efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270

Indexing queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272

Controlling the entry numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Controlling what documents are put in the queues . . . . . . . . . . . . . . . . . . . . . . . 274

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275

Chapter 12 Controlling Columbus OM with the dispatch server . . 279Configuring a dispatch server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280

Creating rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281

Rule format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282

Selecting documents using a condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284

Specifying the actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291

Monitoring the status of dispatch entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308

Example rules using the dispatch server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309

Reference section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320

Chapter 13 Archiving documents. . . . . . . . . . . . . . . . . . . . . . . . . 335Maintaining an archive queue of completed entries . . . . . . . . . . . . . . . . . . . . . .336

Transferring documents to Columbus DW . . . . . . . . . . . . . . . . . . . . . . . . . . . . .341

Transferring documents to other archiving applications . . . . . . . . . . . . . . . . . . .348COLUMBUS OM INSTALLATION AND CONFIGURATION

CONTENTS6Chapter 14 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .351Access to the Columbus OM instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Access to Columbus OM features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Access to administration functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

Access to documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Access to printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Additional security features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Reference section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Chapter 15 Working with multiple instances . . . . . . . . . . . . . . . .387Configuring the network communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388

Enabling instances to work together . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

Copying and deleting files in multiple instances . . . . . . . . . . . . . . . . . . . . . . . . . 390

Communicating with remote instances on different ports . . . . . . . . . . . . . . . . . 398

Accepting users from remote hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

Chapter 16 Monitoring the system . . . . . . . . . . . . . . . . . . . . . . . .405Getting status information from printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

Operating system actions during processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Writing journal information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

Recording information about events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

Monitoring the system: Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

Chapter 17 Processing email messages . . . . . . . . . . . . . . . . . . . .445Configuring Columbus OM to send email messages . . . . . . . . . . . . . . . . . . . . . 446

Processing incoming email messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

Processing email messages: Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458

Chapter 18 Configuring a fax environment . . . . . . . . . . . . . . . . . .463Configuring Columbus OM to send faxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Sending fax documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

Receiving faxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

Configuring a fax environment: Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

Chapter 19 Intelligent Office Printing (IOP) . . . . . . . . . . . . . . . . .495Introduction to Intelligent Office Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

Configuring the IOP deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

Accessing the IOP administration features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

Working with zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502

Working with printers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

Working with printers for OnCall printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

Working with quota-based scanning: Scan2Print . . . . . . . . . . . . . . . . . . . . . . . . 514COLUMBUS OM INSTALLATION AND CONFIGURATION

CONTENTS 7Managing users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .515

Working with enforcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .517

Working with diversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .519

Managing Columbus OM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .521

Printing documents in an IOP deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . .524

Pull printing with SecureJet printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .528

Printer code mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .529

Intelligent Office Printing (IOP): Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . .534

Chapter 20 Integrating Columbus OM with SAP R/3 . . . . . . . . . . 539Columbus OM in a SAP R/3 environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . .540

Configuring SAP R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .543

Configuring Columbus OM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .550

Integration with SAP R/3: Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .553

Chapter 21 Integrating other applications . . . . . . . . . . . . . . . . . 571Integration with Columbus Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .572

Integration with ColumbusZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .577

Integration with formatter applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .580

User Program Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .583

Integrating with other applications: Reference . . . . . . . . . . . . . . . . . . . . . . . . . .598

Chapter 22 Parameters, variables and attributes . . . . . . . . . . . . 601Common parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .602

Substitution variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .603

User variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .612

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613COLUMBUS OM INSTALLATION AND CONFIGURATION

CONTENTS8COLUMBUS OM INSTALLATION AND CONFIGURATION

9About this manual

Installation and Configuration UQCO-5000-01

This manual explains how to install, configure and maintain a Columbus OM system.

Installation and Configuration UQCO-5000-01COLUMBUS OM INSTALLATION AND CONFIGURATION

About this manual Conventions10Conventions

The following typographic conventions are used:

boldface Indicates a command or keyword that you should type, exactly as shown.

italics Indicates a variable for which you should substitute an appropriate value.

monotype Indicates literal input and output.

Ctrl+D Indicates two or more keys pressed simultaneously.

[ ] Brackets surround an optional value.

| Vertical bars separate alternative values from which you must make a selection.

... An ellipsis indicates that the preceding element may be repeated.

Files, folders and environment variables

References to files, folders and environment variables use the Windows conventions, for example: the %UNIQDIR%\config folder. On UNIX, this is equivalent to: the $UNIQDIR/config directory.

uniq and uq

Terms that include uniq and uq, such as the $UNIQDIR environment variable and the uqserver program, derive from the previous name of Columbus OM: UniqPrint. These terms are still valid for Columbus OM.COLUMBUS OM INSTALLATION AND CONFIGURATION

About this manual New features in Columbus OM 11New features in Columbus OM

Columbus OM 5.000

Support for quota-based scanning and printing. For more information, see Working with quota-based scanning: Scan2Print on page 514.

Improved IOP web interface.

Support for IPv6 addresses.

Columbus OM 4.930

Columbus OM supports PCL 6.

xmessage supports newline characters in message texts. See Sending messages using IOP Messenger on page 72.

The filein server can process files either in the order in which they were put in the scanned folder, or in alphabetic order. See the Directory_Read_Order parameter on page 235.

Print indexing can be turned off by setting the PCL_Converter system parameter to NONE. See page 239.

req command: Entries for deletion can be selected by their status. See page 260.

Event monitoring: New events record when queues are automatically purged, extended and archived (see page 433); and when printers are started, stopped and initiated (see page 434). New parameters for evserver control when events are written to a logfile: see Flush_Filter and Flush_Logfile on page 438.

uqsfcache: Remote_User parameter specifies a userid on a remote computer that Columbus OM is to send feedback to. See page 443.

IOP: OnCall_Rls_Medium parameter specifies a medium to be applied to entries when they are released. See page 534.

xnacc_get_acct command: Get records from a device and then delete them (-gap parameter); and specify a timeout period (-t parameter). See page 574.

xnacc_purge command: Specify a timeout period (-t parameter). See page 576.

xmlserver parameters: Action_Frequency, Action_On_SQLError, Cache_SQL, and Timeout. See page 598.

Columbus OM 4.920

Support for partial PCL5 printing.

Improved feedback mechanism when integrating with Columbus DW. For more information, see Tracking the progress of documents that have been archived on page 343.

Ability to send information from Xerox devices that support network accounting to Columbus Accounting.COLUMBUS OM INSTALLATION AND CONFIGURATION

About this manual New features in Columbus OM12Columbus OM 4.915

Combined installation program for Columbus OM for IOP, the Columbus IOP web interface, and Columbus Accounting. For more information, see Installing a Columbus Intelligent Office Printing (IOP) deployment on page 37.

Columbus OM 4.910

Intelligent Office Printing features select most suitable devices for printing documents, based on document properties and user authorisation, with options to divert to other devices or enforce special requirements. For more information, see Intelligent Office Printing (IOP) on page 495.

Combined installation program installs all the IOP desktop components (Columbus Windows Gateway, IOP Messenger and IOP Universal Driver) at once, without user interaction. For more information, see IOP desktop components on page 78.

Columbus OM 4.900

The file-locking system to prevent two users accessing a file at the same time has been supplemented by a faster and more reliable method that provides more effective support for multi-processor computers.

On Windows, mutexes are used. On UNIX, semaphores are used. The method used is specified by the ULM_Method parameter in the default.tab file.

xprinter supports the Internet Printing Protocol (IPP). For more information, see Configuring IPP printers on page 200.

A single Columbus OM password file can now be shared by multiple instances. You can maintain the password file on one instance, and then on other instances, use the csupwd -Redirect command to use that password file. For more information, see page 358.

uqserver timeouts for packages and clients can now be configured separately. For more information, see the UQ_Timeout parameter in the default.tab file (spage 400).

The dispatch server can now handle acknowledgements (ACK/NAKs) from other servers. For more information, see the dispatch servers Process_Acks parameter (page 321).

A printers connection parameters can be more finely specified: the values for the Connect_Delay, Disconnect_Delay and Connect_Interval parameters can be specified in milliseconds (instead of seconds) by adding M after the value.

The uqsfcache server can make a copy of its cache file before processing it, ensuring that statuses are not lost if the server stops abnormally. For more information, see the servers Backup_Cache parameter (page 442).

You can control whether the dispatch server counts the pages and lines in a bundle of documents. For more information, see the servers Count_Bundle_Pages parameter (page 320).

Errors that occur in the status feedback reporting system can be recorded in a logfile. For more information, see the Log_SFB_Errors system default parameter (page 437).COLUMBUS OM INSTALLATION AND CONFIGURATION

About this manual New features in Columbus OM 13 IOP Universal Driver: There is more control over which options in a printers Properties dialog box are available, and the text in the dialog box can be edited. Oncall printers can be configured at installation time or by using the Properties dialog box. For more information, see Configuring the IOP Universal Driver on page 59.COLUMBUS OM INSTALLATION AND CONFIGURATION

About this manual New features in Columbus OM14COLUMBUS OM INSTALLATION AND CONFIGURATION

15

integrating Columbus OM with other applications.Chapter 1 Introduction

This chapter provides an overview of the configuration features that enable you to set up Columbus OM so that it can be used for printing documents and sending faxes. These features include:

setting up the network communications that enable users to access Columbus OM, and instances of Columbus OM to access other instances

administering the document queues that enable users to process, track and archive documents

configuring a printing environment, including how to set up printers so that they can be used and controlled by the Columbus OM print facility, and also how to manage documents using the Columbus OM dispatch facility

configuring a fax environment for sending and receiving faxes by using the Columbus OM fax facility

controlling access to documents and Columbus OM by using the security features

setting up Columbus OM for end-users

monitoring the use of Columbus OM with audit trails, log files and archives

CHAPTER 1COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 1 Introduction Overview of a Columbus OM output management environment16Overview of a Columbus OM output management environment

This section briefly describes how a Columbus OM output management environment works, and shows the components that you have to configure.

Users select the documents that they want to print or fax by using Columbus OM Explorer on their PC. Columbus OM Explorer transfers the documents to a Columbus OM print or fax instance on a host computer. (An instance is an installed copy of any Columbus OM product.) Documents can also added to an instance by using the command line, or directly from another application (for example, ColumbusZ or a SAP system).

Then the instance transfers the documents to a printer or fax modem as appropriate. The printer or fax modem sends status information back to the instance, and the instance sends the status information back to Columbus OM Explorer, so that users can track the progress of their documents.

There may be several Columbus OM instances on the same host: either different Columbus OM products or copies of the same product, configured differently. Each instance usually controls several printers or fax modems.

In a Columbus OM print system, there may be several hosts with print instances. Users may be able to access each instance directly or they may access one instance which in turn accesses another instance.

document

status

Columbus OM Explorer

document

status

Columbus OM instance

printer or fax modem

printers

fax modems


Columbus OM print instance A

Columbus OM fax instance C

Columbus OM print instance B

printersCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 1 Introduction Overview of a Columbus OM output management environment 17For greater control over the use of a Columbus OM print system, you can use the Columbus OM dispatch features. You can specify rules to select documents according to their attributes (for example, the owner or the destination) or their contents, and then process them differently. For example, documents sent to a printer that has been taken offline for maintenance can be automatically redirected to another printer.

The dispatch functionality can be provided either by the dispatch server that is contained within the Columbus OM print instance or by a separately installed Columbus OM dispatch instance.

For more information, see Controlling Columbus OM with the dispatch server on page 279.


Columbus OM instance B


Columbus OM instance A



Columbus OMDispatch

Columbus OMPrintCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 1 Introduction Configuration functions18Configuration functions

This section briefly describes the areas that have to be configured to create a Columbus OM system.

Network communications

The network communications enable the components of a Columbus OM system to communicate with each other. They enable Columbus OM Explorer on a PC to communicate with a Columbus OM instance on a host computer, and a Columbus OM instance to communicate with other Columbus OM instances.

For the network communications to work, you have to choose a port number that Columbus OM uses, and you must use the same port number on every computer within the Columbus OM system.

Queue maintenance

All the documents that you send to a Columbus OM instance are stored in a queue:

The pending queue contains documents that are waiting to be processed. When you add an entry, it first goes in the pending queue.

The completed queue contains documents that have been processed (either successfully or unsuccessfully). Columbus OM automatically moves the documents from the pending queue to the completed queue when it has processed them.

The archive queue contains documents that have been moved from the completed queue and that you want to store for future reference.

Every instance has its own pending queue and a completed queue. The archive is optional: after documents have been in the completed queue, you can either store them in the archive or discard them. If you want to use the archive queue, you have to create it yourself.

The initial size of the pending and completed queue are set when you install the Columbus OM instance. To make sure that there is enough space to hold all the documents that users want to add, you can either increase the size of the queues or delete old entries. Both of these can be done either manually, or automatically when needed.


Columbus OMpending queue

Columbus OMcompleted queue

Columbus OM archive queueCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 1 Introduction Configuration functions 19At regular intervals, you must also check the integrity of the queue, and fix it if necessary. This can also be done either manually or automatically.

Configuring a print environment

This section describes the different print environments that you can set up. Most installations use a combination of these environments.

Local printing

Local printing enables users to print documents on printers that are controlled by the instance to which they are connected. The printer can be directly attached to the host; on the network; attached to a PC that is running the Columbus OM PC Printer Channel; or connected by a modem.

To set up local printing, you have to provide information about how the printers are connected.

Local printing is controlled by one of Columbus OMs servers called printmaster. The printmaster server is configured for you when you install Columbus OM. However, you might need to change its configuration to meet the requirements of your site.

Distributed printing

Distributed printing enables users to print document on printers that are controlled by Columbus OM instances other than the one to which they are connected. These printers are known as remote printers.

Columbus OM print instance

Columbus OMExplorer

printers attached to PC

Columbus OM PC Printer Channel

accessed by modem

printers on network

printers attached to host

printerHOST B Columbus OM


HOST A Columbus OMCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 1 Introduction Configuration functions20In this example, the printer is controlled by the Columbus OM print instance that is on Host B. The printer is in Host Bs local printing environment. On Host A, the same printer is set up as a remote printer. This enables users who can connect only to Host A to use the printer.

To set up a distributed print environment, you need to create a list of the remote printers that you want users to have access to. Distributed printing is controlled by the netmaster server. Like printmaster, netmaster is configured for you when you install Columbus OM.

Converting lp requests into Columbus OM requests

Columbus OM can intercept print requests that users make using the standard UNIX lp command, and add those requests to its own queue.

Transferring documents from other hosts to Columbus OM

Users who do not have direct access to a Columbus OM instance can still add entries to its queue, if they can transfer files to the host that the instance is on.

Setting up printers

For each printer that you want to use with Columbus OM, you have to set up a printer server to control it. Setting up a printer server includes specifying the connection to the printer (for example, whether it is connected to the host, by the network or by a modem) and its type (for example, PCL or PostScript).

Document processing

Additional features enable documents to be processed before they are printed. For example, banner pages can be added to ensure consistent output, and documents can be converted into different formats (for example, from PCL to PostScript), enabling you to make better use of the printers available.

Configuring a fax environment

Within Columbus OM, a fax environment works in a similar way to a print environment. It receives documents from users PCs and puts them into its pending queue which is monitored by fax servers. You have to set up one fax server for each fax modem that you want to use with Columbus OM. When a fax server finds an entry in the queue that it can process, it sends the document to the fax modem that it controls.

Additional features such as coversheets and overlays help to maintain the corporate image, and for security or archiving, confirmation copies of all documents sent can be automatically printed.COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 1 Introduction Configuration functions 21System security

Essential to every Columbus OM system is maintaining security: ensuring that users can modify, view and delete only the documents that are appropriate to their responsibilities, and also ensuring that only authorized users have access to the Columbus OM configuration functions.

Access to documents in the queue is controlled by user groups and printer groups. To modify, view or delete the documents that belong to someone else, you have to be in the same user group. To use a specific printer, you must have access to the printer group that it is in. As part of the configuration of Columbus OM, you have to create user groups and printer groups and add users to them.

Access to the configuration functions is also controlled by user groups, three of which are already set up for you. Each group has access to a different set of functions, representing different levels of responsibilities, from only the day-to-day configuration functions, to all the functions. You have to decide which users need access to which configuration functions and then add them to the appropriate group. For more flexibility, you can create more groups and choose which configuration functions members of those groups can access.

Setting up for end users

When the output management environment has been set up, Columbus OM is available for users to print documents and send faxes. These tasks can be performed with any of the interfaces that Columbus OM provides:

For PC users, Columbus OM Explorer provides a familiar Windows interface for easy access to document management commands to add entries to the queue and to track and monitor their progress. Users can find everything that they need to know about Columbus OM Explorer.

Advanced users and administrators might prefer the command line interface to Columbus OM, available for both Windows and UNIX.

Just before users are given access to these interfaces, the administrator might want to customize how they work. For example, there are several default values that can be set in advance to make it faster and easier for users to add entries.

Monitoring the system

Columbus OM includes extensive features for monitoring its use. Both users and administrators can check the status of printers and fax servers and the progress of documents through the system. (Security features can be set up to ensure that users can only see documents that are relevant to themselves.) Administrators also have access to the extensive and customizable audit trails and log files for checking the progress of documents, and the use of printers, servers and queue maintenance functions.

Integration with other systems

Columbus OM can be integrated with other systems, including Columbus DW (Macro 4s document warehousing application), ColumbusZ (Macro 4s output management system for mainframes), and SAP R/3.COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 1 Introduction Configuration functions22COLUMBUS OM INSTALLATION AND CONFIGURATION

23

uninstalling Columbus OM Uninstalling Columbus OM on page 52Chapter 2 Installing Columbus OM

This section describes how to install Columbus OM.

For information about See

what to do before installing Columbus OM

Preparing to install Columbus OM on page 24

installing Columbus OM Installing Columbus OM (Windows) on page 35 or Installing Columbus OM (UNIX) on page 41

installing a Columbus OM IOP deployment

Installing a Columbus Intelligent Office Printing (IOP) deployment on page 37

what to do after installing Columbus OM

Configuring Columbus OM on page 42

starting Columbus OM Starting Columbus OM on page 48

using Columbus OM in a VMWare environment

Using Columbus OM in a VMWare environment on page 50

upgrading Columbus OM Upgrading Columbus OM on page 51

CHAPTER 2COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM24Preparing to install Columbus OM

This section describes what to do before installing Columbus OM. Use this section with the Checklist on page 33.

Licensing

Columbus OM is licensed by Macro 4 to run on a specified computer for a specified period of time. A license is provided either in a license file or as a set of license keys.

If you have a license file, see Using a license file below.

If you have a set of license keys, see Using a set of license keys on page 25.

Using a license file

If your license is in the form of a license file, it is validated by the Columbus License Manager program. The License Manager is installed when you install Columbus OM itself. The License Manager must be running whenever Columbus OM is running.

Installing the license file

Copy the license file to anywhere on the computer on which you want to install Columbus OM; when you install Columbus OM, it will ask you for the location of the license file, and then move it to where it needs to be.)

If you copy the file by using FTP, make sure that the file is transferred in binary mode.

Updating the license file

If you receive a new license file, do the following:

1 Stop the License Manager service.

See Starting and stopping License Manager below.

2 Copy the new license file into the folder in which the License Manager is installed.

Step Description See

1 Make sure that your license information for Columbus OM is accessible

page 24

2 Check the port numbers that Columbus OM uses page 26

3 Create an operating system user (and on UNIX, a user group) to own and control the Columbus OM programs

page 27

4 Choose the folder in which you want to install Columbus OM page 28

5 (UNIX only.) If you are installing two or more instances on the same computer, and you want the instances to share some of the Columbus OM programs, choose a common directory

page 29

6 (UNIX only.) Make sure that the X-Server with Virtual Frames Buffer is installed

page 29COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM 253 Start the License Manager service.

Starting and stopping License Manager

Windows

Use the Services icon in the Window Control Panel. The License Manager service is called M4 License Manager.

UNIX

1 Change to the directory in which License Manager is installed.

2 Do one of the following:

For example, to start License Manager on Solaris, type:

./cr_lrm.sol start

To start License Manager on AIX, type:

./cr_lrm.aix start

Columbus OM on a shared disk

If you install a Columbus OM instance on a shared disk, each host computer that accesses the disk must have a license file. Each host computer must: be the same type; be from the same manufacturer; and run the same version of the operating system. This ensures that the locking mechanism (used for maintaining update integrity) works correctly, and that queues are managed in the same manner: different systems organize data in different ways and this can cause queue corruption.

Using a set of license keys

If you license is in the form of a set of license keys, you enter the keys when you run the installation program.

Updating the license keys

If you need to update your license keys, use the keyset command.

Before running the keyset command, make sure that the %UNIQDIR% environment variable contains the path of the Columbus OM instance whose license you are updating.

To display your license information

Type:

keyset -q

To update your license keys

1 Log on as the user id which you specified during installation as the Columbus OM owner, and then change to the installation folder.

To Type

start License Manager ./cr_lrm.opsys start

stop License Manager ./cr_lrm.opsys stopCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM262 Type:

keyset

3 Make sure that the name is the same name that you supplied to Macro 4 when you requested the license.

4 Type the license keys in order. After each license key, press Enter.

After the last license key, press Enter twice.

5 Type a name to identify the license, for example, the name of your company. The license name will be displayed when you run a Columbus OM command.

6 Type the license number that has been supplied by Macro 4.

Columbus OM updates the license information.

Network connectivity

Columbus OM components that are installed on different computers communicate by using the TCP/IP protocol and some network services. You must make sure that all the computers use the port numbers for the services.

Columbus OM services

The basic Columbus OM network services are:

You can use different port numbers from those suggested above; but you must use the same port number for any given service on all computers (hosts and PCs) in the Columbus OM network.

If required, you can create two or more independent Columbus OM networks by running each network on different port numbers.

System name: MyHost

Enter key 1:

License name :

License number:

Service Port number Used for

uniqcs 2006 (suggested) General communication (between Columbus OM instances; and between a instance and Columbus OM Explorer)

printer 515 (standard) Columbus OM print LPD/LPR communication

2001 (suggested) Columbus OM PC Printer Channel communicationCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM 27Setting the port numbers

(Windows.) The installation program sets the port numbers for you. Check that the port number is not already being used by looking in the computers services file.

(UNIX.) You must add the uniqcs service and port number to the services file, after you have installed Columbus OM.

The location of the services file is as follows:

Creating a Columbus OM user

Before installing Columbus OM, you must create a operating system user (and, on UNIX, a user group) under whom the Columbus OM services will be started. You are recommended to create a user who is used for only this task. The recommended user name is uniq.

See:

Creating a user (Windows 2000 and later) below

Creating a user and user group (UNIX) on page 28.

Creating a user (Windows 2000 and later)

To create a user account

1 Select Start Settings Control Panel.

2 Double-click the Users and Passwords icon.

3 Select the Advanced tab, and then click the Advanced button.

4 In the Local Users and Groups window, click Users in the left-hand pane.

5 On the Action menu, click New User to display the New User dialog box.

6 Type a user name and password.

The recommended username is: uniq.

The password is case-sensitive.

7 Clear User Must Change Password at Next Logon and select Password Never Expires.

8 Click Create, then click Close.

To configure the user rights policies


System File location

UNIX /etc/services

Microsoft Windows 95/98

\windows\services

Microsoft Windows NT, 2000, XP and later

%SystemRoot%\system32\drivers\etc\services

Novell NetWare \etc\services COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM282 Double-click Administrative Tools, and then double-click the Local Security Policy icon.

3 In the Local Security Settings windows, click + (plus sign) next to Local Policy in the left-hand pane, then click its sub-entry User Rights Assignments.

4 Double-click Act as part of the operating system.

5 Click Add to display the Select Users or Groups dialog box.

6 Click the username of the new account (uniq) in the Names list.

7 Click Add to display the PC\username combination in the Add Names list.

8 Click OK to close the Select Users or Groups dialog box, and then click OK again to close the Local Security Policy Setting window.

9 Double-click Log on as a service.

10 Repeat steps 6 through 10.

If you are using Windows 2003:

Make sure that the uniq user is not a restricted user.

Enable the uniq user to access the folders in which Columbus OM is installed by adding uniq as a user of the folder hierarchy with Full control.

Creating a user and user group (UNIX)

You must create a UNIX user and user group:

The user will own the Columbus OM directories and files.

The user group will have the appropriate access rights to the directories and files.

You are recommended to create a user called uniq, and a user group called uniqgrp, and use them only for Columbus OM.

If you install two or more Columbus OM instances, use the same user and user group for all the instances.

Note Some Columbus OM programs, for example lpdserver and statserver, must be owned by root (and have the s bit set) in order to operate properly. The installation process handles this automatically.

Selecting an installation folder

The installation program asks you which folder you want to install Columbus OM. If the folder does not exist, the installation program creates it for you.

To install multiple instances on the same computer, install them in subfolders of a main Columbus OM folder, for example:

Installation folder for Fax instance 1

Installation folder for Fax instance 2

Installation folder for Print instance 1

Installation folder for Print instance 2

Main Columbus OM folderCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM 29Folder names

(Windows only.) The path for the installation folders must not include any space characters. Other than this restriction, standard Windows naming conventions apply.

(UNIX only.) The recommended location for the main Columbus OM folder is /usr/uniq.

The name of the folder does not relate to the name of the instance; you specify that name later in the installation process.

Selecting a commands directory (UNIX only)

If you install two or more Columbus OM instances on the same computer, you can install some of their programs in a common directory so that they are shared. The programs that can be shared are the commands that are usually installed in the Columbus OM programs/commands directory.

For example, to keep all the Columbus OM programs together, but separate from other UNIX commands, you could create a directory called /usr/UniQ/bin. To keep the programs somewhere that is commonly included in users $PATH environment variable, you could put them in the /usr/local/bin directory.

If you use this feature, you must:

create the folder before installing Columbus OM

make sure that the folder can be accessed by all the instances, typically by setting its owner to uniq and its access group to uniqgrp.

upgrade all instances which share files at the same time to make sure that they are compatible.

Installing X-Server with Virtual Frames Buffer (UNIX only)

Columbus OM handles some image and document formats by using X-Server with Virtual Frames Buffer. You must check that this is installed on your computer. For more information, see:

X-Server and virtual frames buffer (AIX) below

X-Server and virtual frame buffer (HP-UX, Linux and Solaris) on page 30

X-Server and virtual frames buffer (AIX)

To check if X-Server is already installed

At the command prompt, type:

lslpp -l | grep vfb

If the reply includes these lines, it indicates that X-Server is installed.

OpenGL.OpenGL_X.dev.vfb 4.3.3.75 COMMITTED OpenGL Virtual Frame Buffer X11.vfb 4.3.3.50 COMMITTED Virtual Frame Buffer Software

If the reply is blank, it indicates that X-Server is not installed; you must install the X11.vfb module by following the instructions below.COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM30To install the X11.vfb module

The X11.vfb module is available from the AIX V4.3.3 installation CD-ROMs and from the AIX Version 4 Update CD-ROM.

1 Put the CD-ROM in the AIX computers CD-ROM drive.

2 Login as root.

3 At the command prompt, type:

smit

The smit utility starts.

4 Navigate to Software Installation and Maintenance Install and Update Software Install and Update from LATEST Available Software INPUT device/directory for software.

5 Press F4, and then select the CD-ROM drive (for example, /dev/cd0).

6 In Install and Update from LATEST Available Software, set SOFTWARE to install to X11.vfb.

To do this, either type X11.vfb, or press F4 to display a list of options and then select X11.vfb.

7 Set PREVIEW only? (install operation will NOT occur) to yes.

8 Press ENTER.

The preview installation starts.

9 If the preview completes successfully, set PREVIEW only? (install operation will NOT occur) to no, and then press ENTER to complete the installation.

See also Starting the virtual frame buffers on page 30.

X-Server and virtual frame buffer (HP-UX, Linux and Solaris)

1 Check whether Xvfb is installed (for example, in /usr/bin/X11/Xvfb).

2 If it is not installed, install it by following the operating systems instructions.

See also Starting the virtual frame buffers on page 30.

Starting the virtual frame buffers

To start the virtual frame buffers

1 Login as root.

2 At the command prompt, type:

AIX:

X -vfb :n > logfile &

HP-UX:

nohup Xvfb :n -screen 0 1x1x24 -cc 4

Linux:

Xvfb :n -screen 0 1600x1200x24 &

Solaris:

/usr/X11R6/bin/Xvfb :n -screen 0 1x1x24 -cc 4 2>>logfile &COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM 31Replace:

n with the screen number, usually 1.

logfile with the name of a file to be used by the buffer for recording information.

Configuring Microsoft Internet Information Services (IIS)

If you are using the Columbus IOP web interface with Microsoft Internet Information Services (IIS) 7, you must configure IIS manually, as described below. You must do this before installing Columbus OM.

If you are using IIS 6, the Columbus OM installation program configures it for you.

Adding the roles services

1 In IIS Server Manager, navigate to Roles Web Server (IIS).

2 In the Role services section, click Add Role Services.

The Select Roles Services dialog box appears.

3 Select these items:

ISAPI Extensions

ISAPI Filters

Basic Authentication

Windows Authentication

IIS Management Scripts and Tools

IIS 6 Management Compatibility, and all items under it.

4 Click Next.

5 Click Install.

6 When the items have been installed, click Close, and then close IIS Server Manager.

Changing the port number for the default website

1 In IIS Manager, navigate to Sites Default Web Site.

2 Right-click Default Web Site, and then click Edit bindings.

The Site Bindings dialog box appears.

3 Click Edit.

4 Change the port number to something other than 80 (for example, 81), and then click OK. (80 is used by the Columbus IOP web interface, so the default website must use a different number.)

Enabling 32-bit applications

If you are installing the Columbus IOP web interface on a 64-bit operating system, you must also enable IIS to run 32-bit applications.

1 In IIS Manager, navigate to Application pools.COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM322 Right-click DefaultAppPool, and then click Advanced settings.

The Advanced Settings dialog box appears.

3 Set Enable 32-bit Applications to True.COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM 33Checklist

License format

Using a license file

Operating system

Columbus IOP deployments

License information (set of keys or file) available

Location of license file

Choose one of: Install Columbus License

Manager Use an existing Columbus

License Manager

To use an existing License Manager, you need this information: MAC address of the computer

that the License Manager is on (12 numbers or letters; exclude any punctuation symbols)

Port number

Installation folder

Port number for Columbus OM uniqcs service (for example, 2006)

Columbus OM username (for example, uniq). On Windows, include the PC name or domain name

(UNIX only) Columbus OM user group created (for example, uniqgrp)

Installation folder

(UNIX only) Commands directory name

(UNIX only) X-Server with VFB is installed

To use Columbus OM WebChannel: Web server installed

Web browser is installed

Web server is installedCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Preparing to install Columbus OM34PHP is installed, or the PHP installation program is available

If you are using Microsoft Internet Information Services 7: IIS has been configured (see page 31)

For Columbus Accounting: The database application is installedCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Installing Columbus OM (Windows) 35Installing Columbus OM (Windows)

1 Log on with Administrator access rights.

2 Complete the steps that are described in Preparing to install Columbus OM on page 24.

3 Check that you have the information that the installation program needs. For more information, see Checklist on page 33.

4 Using Windows Explorer, navigate to the folder that contains the Columbus OM installation program, and then double-click the setup.exe file.

5 Follow the onscreen instructions.

Installing Columbus OM without user interaction (Windows)

If you are installing multiple copies of Columbus OM with the same or similar values, you can make the process faster by putting the values that you would usually put in the dialog boxes in the installation program in a responses file. You can then run the installation program and tell it to read all the values from the responses file instead of displaying the dialog boxes.

To create a responses file

The easiest way to create a responses file is to install Columbus OM by using the installation program as usual, and record the values that you enter.

1 Set up the environment as described in Preparing to install Columbus OM on page 24.

2 Start the installation program by typing:

setup.exe -r

3 Complete the dialog boxes, and run the installation program to completion.

The installation program records the values that you put in the dialog boxes in a responses file called setup.iss. The file is in the Windows folder.

To use the responses file

1 On the computer on which you want to install another copy of Columbus OM, set up the environment as described in Preparing to install Columbus OM on page 24.

2 If required, edit the responses file to make the values appropriate for this copy of Columbus OM.

3 Start the installation program by typing:

setup -s -f1folder\setup.iss

Replace folder with the path of the folder that the responses file is in, for example: setup -s f1c:\windows\setup.iss.

The installation program installs Columbus OM, using the values that are in the responses file; no dialog boxes appear.

4 When the installation program has finished, check the setup.log file that is in the same folder as the responses file.COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Installing Columbus OM (Windows)36 If the ReturnCode value is zero, it indicates that the installation was successful. To complete the installation, see Configuring Columbus OM on page 42.

If the ReturnCode value is not zero, identify the error by using this list:

Return code Description

0 Success

-1 General error

-2 Invalid mode

-3 Required data not found in the responses file

-4 Not enough memory available

-5 File does not exist

-6 Cannot write to the responses file

-7 Unable to write to the log file

-8 Invalid path to the responses file

-9 Not a valid list type (string or number)

-10 Data type is invalid

-11 Unknown error during setup

-12 Dialog boxes are out of order

-51 Cannot create the specified folder

-52 Cannot access the specified file or folder

-53 Invalid option selectedCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Installing a Columbus Intelligent Office Printing (IOP) deployment 37Installing a Columbus Intelligent Office Printing (IOP) deployment

1 Complete the steps that are described in Preparing to install Columbus OM on page 24 and Support applications for Columbus IOP deployments on page 37.

2 Install the support applications that a Columbus IOP deployment uses. For more information, see Support applications for Columbus IOP deployments on page 37.

3 Check that you have the information that the installation program needs. For more information, see Checklist on page 33.

4 Using Windows Explorer, navigate to the folder that contains the Columbus IOP installation program, and then double-click the setup.exe file.

Support applications for Columbus IOP deployments

If you are installing a Columbus IOP deployment, you must install the following support applications. These applications are used by the Columbus IOP web interface and Columbus Accounting.

For more information about the versions of these applications that are supported, see the Columbus OM Release Notes.

You do not need to create a user for Columbus Accounting or the IOP services, because the Columbus IOP installation program can create one for you.

Application Installation instructions

a web browser Follow the manufacturers instructions.

PHP Download the PHP installation program from www.php.net, and then do one of the following:

Run the PHP installation program. Use the default options.

If you want the Columbus IOP installation program to install PHP, copy the installation program to the same folder as the Columbus IOP installation program, and then rename it to php.msi.

web server: Apache or Microsoft Internet Information Services

Install the web server by using its installation program. Use the default options.

The Columbus installation program will configure the web server to support the IOP web interface.

Only for Columbus Accounting:

a database application (for example, MySQL)

Follow the manufacturers instructions. You must also install an administration program for the database, and then create a database, as described in the Columbus Accounting manual.COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Installing a Columbus Intelligent Office Printing (IOP) deployment38Using the installation program

In the installation program, select these options:

Step Option

IOP Installer Select Standalone installation.

Columbus Accounting

Destination Folder Select the folder in which you want to install Columbus Accounting.

Instance Name This is usually set to Accounting.

License Details Type your license keys in the Keys box, one by one.

After each key, click Add. After the last key, click Add, and then click Next.

Create User Type a name and password for a user to control the Columbus Accounting service.

Accounting Service Use the default values (that is, 0.0.0.0 and 8084).

Create Accounting Database

Type the User and Password to enable access to the database application.

MAGIK and SMTP Set Magik Host to localhost.

Set the host and domain of your SMTP server as appropriate.

Create Shortcuts Select the options that you want.

Columbus OM

Setup Type Select Zone Server.

Choose Destination Location

Select the folder in which you want to install Columbus OM.

Create Instance Type a name to identify the instance, for example IOP, and the port for the uniqcs service (see Columbus OM services on page 26).

Service Logon Type the name and password of the user that you want to control the Columbus OM service.

When the installation program asks if you want to configure the Accounting server, click Yes.

IOP Install (Details of the Accounting server)

Use the default values (that is, localhost and 8084).

When the installation program asks if you want to configure the Zone server, click Yes.

IOP Install (Details of Zone server)

Use the default values (that is, localhost, 8082, and the name of the instance as specified above).COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Installing a Columbus Intelligent Office Printing (IOP) deployment 39Completing the installation

1 Install Columbus OM IOP Messenger. For more information about how to do this, see IOP Messenger on page 70.

2 Open the Windows Control Panel, and then navigate to Administrative Tools Local Security Policy Local Policies User Rights Assignment.

3 Make sure that the following policies include the uniq user:

Act as part of the operating system

Log on as a batch job

Log on locally.

4 Make sure that the uniq user has full Administrator authority over the folder in which Columbus Accounting is installed:

In Windows Explorer, right-click the folder, and then click Properties.

Click the Security tab, and then click the uniq user. Make sure that all the Permissions are set to Allow.

5 Open this file in a text editor (for example, Notepad):

c:\ColumbusAccounting\Security\implementors

6 Make sure that the file contains an entry for the Columbus IOP instance and Columbus Accounting, like this:

# Same# Name Path type? Product ------------ ----------------------- ----- ------- IOP C:\ColumbusOM Yes Print Accounting C:\ColumbusAccounting Yes Batch

If the file does not contain either of these entries, add them.

7 Open this file in a text editor:

c:\ColumbusAccounting\system.tab

MAGIK and PHP

Choose Destination Folder

Select the folder in which you want to install MAGIK.

PHP Location Select the folder in which you installed PHP.

Web server Select the web server that you want to use: either IIS or Apache.

Desktop Shortcut Selection

Select all the options.

Step OptionCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Installing a Columbus Intelligent Office Printing (IOP) deployment408 Make sure that the file contains an entry for Columbus Accounting, like this:

# Same# Name Path type? Product ------------ ----------------------- ----- ------- Accounting C:\ColumbusAccounting\ Yes Batch

9 Stop the Columbus OM service, and then start it again.

Configuring the IOP interface

1 In Windows Explorer, navigate to the magik\application\config folder, and then open the magik.ini file in a text editor.

2 Set the parameters that are described below.

Parameters in the magik.ini file

[application]

;authAdapter = Magik_Auth_Adapter_DummyauthAdapter = Macro4_Auth_Adapter_Om;authAdapter = Magik_Auth_Adapter_Ldap

Specify how users names and passwords are to be validated. (Delete the semicolon that is in front of the method that you want to use; insert a semicolon at the front of the methods that you do not want to use.)

[xmlserver]

xmlserverHost = textxmlserverPort = number

The name or IP address of the computer that xmlserver is on, and the port number on which it listens. If xmlserver and the IOP interface are on the same computer, you can set xmlserverHost to localhost.

xmlserverInstance = text

The name of the Columbus OM instance that controls the xmlserver.

xmlserverPlatform = Windows

If xmlserver is running on Microsoft Windows, delete the semicolon (if any) from the start of this line.

To Use

check the user id in Columbus OM Macro4_Auth_Adapter_Om

You must also configure the xmlserver section.

check the user id in another program (for example, Microsoft Active Directory or OpenLDAP)

Magik_Auth_Adapter_Ldap

You must also configure the xmlserver section (see [xmlserver] below.

not validate the user id (use this option only for testing)

Magik_Auth_Adapter_DummyCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Installing Columbus OM (UNIX) 41Installing Columbus OM (UNIX)

1 Log on as root.

2 Create a temporary directory to hold the Columbus OM distribution file, and then copy the distribution file from the distribution medium to the temporary directory.

The name of the distribution file indicates the operating system that it is for, for example, ColumbusOM490.aix.tar.zip is for AIX (IBM RS6000).

3 Restore the installation files by using the tar command.

This creates a directory with a name like UniQ4900x.aix (that is, the name indicates the version number and the operating system).

4 Change to the new directory.

5 Run the installation script by typing:

sh ./install

6 Follow the onscreen instructions.

To answer the questions about how you want to configure Columbus OM, you can either:

accept the default answer, shown in brackets [...], by pressing Return, or

type your answer, and then press Return.

7 When the installation program has finished, review the contents of the warnings file. To do this, change to the installation directory, and then type:

more warnings

If you see a warning about SAP R/3 not being available on this platform, a small number of integration capabilities, for example the use of the csulin_sap validation program by uqserver, cannot be used.

8 Delete the installation files from the temporary directory.

Welcome to the Columbus OM 4.x installation/upgrade process.

Before proceeding, you will need the following:

1. To be logged on as root.

2. A userid and a groupid to use as the Columbus OM "owner".

3. To know where to install/upgrade the Columbus OM product (80+Mb required).

4. Installations only. Columbus OM 4.2 and above supports two licensing technologies. You will need EITHER: A set of license keys authorising use of this product OR A valid license file authorising use of this product.

5. To shut down any active Columbus OM 4.x servers (upgrades only).

6. To shut down any locally running Columbus OM License Manager (upgrade only).

Ok to proceed? [N]COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Configuring Columbus OM42Configuring Columbus OM

This section describes how to configure Columbus OM and the operating system after you have installed Columbus OM.

These steps enable the Columbus OM program to work. After you have completed these steps, additional steps will be necessary to configure it for your environment, for example, to control printers and enable users to print documents.

Updating the services file (UNIX only)

Add an entry to the services file for Columbus OM uniqcs service. For more information, see Network connectivity on page 26.

Enabling instances to work together

If you have two or more Columbus OM instances installed on the same computer and you want the instances to work together, add the other instances to each instances systems.tab file.

If you have only one Columbus OM instance, you have to update this file only if you want to change the instance name. For example, if you might add other instances later, you could change PRINT to PRINT1.

Occasionally, some sites require that instances are not aware of each other; however, in most cases, it is easier to administer and use Columbus OM if all the instances on a host are aware of each other.

systems.tab file location

The systems.tab file for an instance is in the folder in which the instance was installed (that is, %UNIQDIR%).

Step Description See

1 (UNIX only.) Add the Columbus OM uniqcs service to the services file

below

2 If you have two or more Columbus OM instances installed on the same computer that you want to use together, you must:

3 make each instance aware of the others below

4 make sure that only one instance runs the Columbus OM communications server, uqserver

page 44

5 (Windows only.) Make sure that authorized users can access Columbus OM

page 45

6 (UNIX only) Set the Columbus OM environment variables page 45COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Configuring Columbus OM 43systems.tab file format

The first line describes the instance that the file belongs to.

The other lines describe the other instances on the host that you want to use with it.

Fields

Name

A name to identify the instance.

Each instance on the host must have a unique name. The name can include letters and numbers. It cannot include spaces. The maximum length is 10 characters.

Path

The full path of the folder in which the instance is installed, for example: "C:\Columbus OM\print1" or /usr/uniq/print1. If the path include spaces, enclose it in quotation marks.

Same type?

If the instance is the same type (that is, Print, Fax or Dispatch) as the instance that to which the file belongs, specify Yes.

If they are different types, specify NO.

Product

One of: DISPATCH, FAX, PRINT.

Examples

If you install two Columbus OM instances, the systems.tab file for the first print instance might look like this:

The systems.tab file for the second print instance might look like this:

If you then install a Columbus OM fax instance, the systems.tab files might become:

# Same# Name Path type? Product# ---------- -------------------------------------------------- ----- -------

Print1 C:\Columbus OM\print1 Yes PRINTPrint2 C:\Columbus OM\print2 Yes PRINT

# Same# Name Path type? Product# ---------- -------------------------------------------------- ----- --------

P1 "C:\Columbus OM\print1" Yes PRINTP2 "C:\Columbus OM\print2" Yes PRINT


P2 "C:\Columbus OM\print2" Yes PRINTP1 "C:\Columbus OM\print1" Yes PRINTCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Configuring Columbus OM44For the first print instance:

For the second print instance:

For the fax instance:

Enabling the uqserver program

If there are two or more Columbus OM instances on the host, you must make sure that only one of them runs the uqserver program. (uqserver enables instances on different hosts to communicate with each other, and for Columbus OM Explorer to communicate with the instance.)

If the instances use different versions of Columbus OM, choose the most recent version as the instance to run uqserver. In the other instances, you must disable uqserver.

To disable uqserver

1 In the instance that you do not want to run uqserver, edit the servers\servers.tab file. This file lists all the servers that the instance runs.

2 Look for an entry for uqserver.

3 Inserting a hash symbol (#) at the start of the line for uqserver.

Notes

If there is only one Columbus OM instance on the host, you do not have to edit this file.


P1 "C:\Columbus OM\print1" Yes PRINTP2 "C:\Columbus OM\print2" Yes PRINTF1 "C:\Columbus OM\fax1" No FAX


P2 "C:\Columbus OM\print2" Yes PRINTP1 "C:\Columbus OM\print1" Yes PRINTF1 "C:\Columbus OM\fax1" No FAX


F1 "C:\Columbus OM\fax1" Yes FAXP1 "C:\Columbus OM\print1" No PRINTP2 "C:\Columbus OM\print2" No PRINT

# Name Id Program AI? AT? AS? Master?# ---- -- ------- --- --- --- -------. . .uqserver 2 uqserver Yes Yes Yes Yes. . .

# Name Id Program AI? AT? AS? Master?# ---- -- ------- --- --- --- -------. . .

# uqserver 2 uqserver Yes Yes Yes Yes. . .COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Configuring Columbus OM 45 There might be site-specific circumstances in which multiple instances on the same host should use separate copies of uqserver, and you should then interpret these instructions accordingly. In most cases, however, you will find it easier to administer and use your Columbus OM installation if only one of the instances on a host runs uqserver.

Granting access to local and remote users (Windows only)

You must ensure that Columbus OM is accessible by authorized users. You have separate control over access by:

local users: those running Columbus OM Explorer on the PC where you have installed Columbus OM

remote users: those running Columbus OM Explorer on another PC elsewhere in the network.

To grant appropriate rights to users


2 Double-click the Administrative Tools icon, and then double-click the Local Security Policy icon.

3 In the Local Security Settings windows, click the + next to Local Policy in the left-hand pane, then click its sub-entry User Rights Assignments.

4 For a local user, double-click Log on locally. For a remote user, double-click Access this computer from network.

5 Click Add to display the Select Users or Groups dialog box.

6 Click the username of the new account (uniq) in the Names list.

7 Click Add to display the PC\username combination in the Add Names list.

8 Click OK to close the Select Users or Groups dialog box, and then click OK to close the Local Security Policy Setting window.

The post-installation configuration steps for Windows are now complete, and you can start the new instance. See Starting Columbus OM on page 48.

Setting Columbus OM environment variables (UNIX only)

Columbus OM uses these environment variables:

Variable Description

$UNIQDIR The directory in which the instance has been installed.

$PATH The standard UNIX variable defining a command search path, extended to include a reference to the directory in which the instances binaries have been installed (for example $UNIQDIR/programs/commands).

$UNIQ_GROUP Only if Group Security is in use: The printer group to which the user belongs. If undefined, Columbus OM searches $UNIQDIR/security/groupsec.tab to determine the users group membership and thus the available actions.COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Configuring Columbus OM46With the exception of $TERM and $UNIQTERM, the variables are specific to each Columbus OM instance, and must be properly defined for all users requiring access to that instance. For example, if you have installed two Columbus OM instances, users wanting to use the first instance might set $UNIQDIR to /usr/UniQ/print1 (and the other variables accordingly), while users of the second instance might set it to /usr/UniQ/print2.

To initialize the variables, see:

Setting variables (Bourne and Korn shells) below

Setting variables (C shell) on page 46.

Setting variables (Bourne and Korn shells)

To set the variables statically, add these lines to each users .profile file:

Alternatively, run a Columbus OM script to set the first three values dynamically by adding these lines to each .profile file:

. installation_directory/setupUNIQ_GROUP=printer_group export UNIQ_GROUP # if neededWOPQ_GROUP=printer_group export WOPQ_GROUP # if neededUNIQTERM=terminal_type export UNIQTERM # if needed

Setting variables (C shell)

To set the variables statically, add these lines to each users .login file:

setenv UNIQDIR installation_directorysetenv UF_HOME $UNIQDIR/uniformset PATH ( $PATH bin_directory )setenv UNIQ_GROUP group # if neededsetenv WOPQ_GROUP group # if neededsetenv UNIQTERM terminal_type # if needed

Alternatively, run a script to set the first three values dynamically by adding these lines to each .login file:

$WOPQ_GROUP Only if Group Security is in use: The printer group to which the user belongs for the purpose of the Printer Operations display. If undefined, Columbus OM searches $UNIQDIR/security/groupsec.tab to determine the users group membership and thus the displayable printers.

$UNIQTERM Used in preference to $TERM to identify the users terminal type. If undefined, the $TERM value is used.

Variable Description

UNIQDIR=installation_directory export UNIQDIRUF_HOME=$UNIQDIR/uniform export UF_HOMEPATH=$PATH:bin_directory export PATHUNIQ_GROUP=printer_group export UNIQ_GROUP # if neededWOPQ_GROUP=printer_group export WOPQ_GROUP # if neededUNIQTERM=terminal_type export UNIQTERM # if neededCOLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Configuring Columbus OM 47source installation_directory/csetupsetenv UNIQ_GROUP group # if neededsetenv WOPQ_GROUP group # if neededsetenv UNIQTERM terminal_type # if needed

Environment variables for multiple instances

If you have two or more Columbus OM instances on the same host, you can make all of the instances available to users. There are two ways of doing this.

Method 1: Environment switching

Create a series of shell scripts, one for each instance, which set $UNIQDIR, $UF_HOME and $PATH to refer to that instance. A user can run the appropriate script prior to typing the uq command in order to invoke the appropriate menu interface.

Method 2: Queue switching

1 Make sure that are all the instances are at the same release level.

2 Set $UNIQDIR and $UF_HOME to refer to one instance, which will be the default instance.

3 Extend $PATH to refer to all of the bin directories.

$PATH must refer to only one of the bin directories for each type. For example, if you have two Columbus OM fax instances and three Columbus OM print instances, $PATH must include only one of the Columbus OM fax command directories and one of the Columbus OM print command directories. If you have installed all the Columbus OM binaries in a single directory, $PATH need refer only to that directory.

To Do this

access the default instance Type uq

access the other instances Type uq -qn instance, where instance is the name of the instance. See Enabling instances to work together on page 42).COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Starting Columbus OM48Starting Columbus OM

Starting Columbus OM (Windows)

Columbus OM is installed as Windows service which starts automatically whenever the computer starts. You can also start the service manually.

To start the Columbus OM service manually


2 Double-click the Administrative Tools icon.

3 Double-click the Services icon to display the Services window.

4 Right-click the appropriate name in the right-hand pane to display the shortcut menu.

5 Click Start or Stop.

Starting Columbus OM (UNIX)

To use a Columbus OM instance, its servers (sometimes known as daemons) must be running. To start an instances servers manually, use the command line interface or Columbus OM Explorer. You can also start the servers automatically when the host reboots.

To start Columbus OM manually

1 Log on as uniq.

2 If you are using the Columbus License Manager, start it. (See Starting and stopping License Manager on page 25.)

3 Change to the Columbus OM installation directory, and then initialize the environment variables by typing:

cd installation_directory . ./setup

4 Type:

syq -ai

To start Columbus OM servers automatically

1 Log on as root.

2 Add these lines to a startup script which is appropriate for your UNIX system.

UNIQDIR=installation_directory export UNIQDIR $UNIQDIR/programs/commands/syq -ai

If you installed the Columbus OM commands in a different directory (see Selecting a commands directory (UNIX only) on page 29), change the last line accordingly.

3 Repeat the lines for each instance on the host.COLUMBUS OM INSTALLATION AND CONFIGURATION

CHAPTER 2 Installing Columbus OM Starting Columbus OM 49Alternative procedures for starting and stopping Columbus OM

Columbus OM is started and stopped by starting and stopping the Columbus OM service.

When you start the Columbus OM service, it runs a Columbus syq -ai command to start the servers.

When you stop the Columbus OM service, it runs an syq -atnw command to stop the servers. The syq -atnw command waits for the servers to stop cleanly. When all the servers have stopped cleanly, the Columbus OM service itself stops.

You can specify alternative commands for the Columbus OM service to use when it stops and starts. For example, you can stop Columbus OM more quickly by using the uqshutdown command instead of syq -atnw. The uqshutdown command tries to stop each server; if a server does not stop within a short period, the command kills it.

To s