Open Print Installation Guide Version

Open Print

Installation Guide

Version 6.3

Paris Boston Bristol www.sefas.com This manual, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Sefas Innovation. Sefas Innovation assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation. Except as per- mitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Sefas Innovation, Inc.

All cited product names and logos are the respective property of their owners.

Introduction 5 Product description ...... 37 ...... Installing Delivery ...... 37 Overview ...... 5 Post-installation ...... 41 MiddleOffice ...... 41 Product description ...... 5 Product description ...... 41 Naming conventions ...... 5 Installing MiddleOffice ...... 41 Installing the DataMapper components ...... 47 Before Installing Open Print 7 FrontOffice ...... 54 ...... Product description ...... 54 Installing FrontOffice ...... 54 Overview ...... 7 Projector...... 59 Database configuration ...... 7 Product description ...... 59 Configuring DB2...... 9 Installing Projector...... 59 Configuring Oracle ...... 10 Installing Projector in load balancing ...... 65 Verifying the C compiler ...... 10 Studio...... 67 Verifying on UNIX ...... 10 Product description ...... 67 Command line verification ...... 10 Installing Studio...... 67 Verifying on Windows ...... 11 Post-installation ...... 71 Setting environment variables ...... 11 Installing on Vista...... 71 Checking the installation ...... 11 Verifying on z/OS ...... 11 Installing on UNIX 73 Backstage, Python, and JRE ...... 12 ...... Installing Backstage ...... 12 Overview ...... 73 Manually installing Backstage ...... 12 Prerequisites ...... 73 Python ...... 14 Installing the Python Interpreter...... 14 Installation ...... 73 JRE...... 15 MiddleOffice ...... 73 Product description ...... 73 Application servers ...... 16 Installing MiddleOffice ...... 74 Tomcat ...... 17 Transferring to the UNIX server ...... 83 WebSphere...... 18 Front Office ...... 84 Configuring WebSphere ...... 19 Product description ...... 84 Deploying the .ear file ...... 20 Installing FrontOffice ...... 84 Changing the class loading mode ...... 20 Transferring to the UNIX server ...... 92 Creating shared libraries for database access. . . . . 21 Projector...... 92 Adding JniVpf API to the Java Library Path ...... 21 Product description ...... 92 Regenerating the WebSphere plug-in configuration 21 Installing Projector...... 92 Editing configuration files...... 21 Transferring to the UNIX server ...... 100 WebLogic ...... 22 Installing Projector in load balancing ...... 100 Configuring WebLogic on Windows ...... 23 Configuring WebLogic on UNIX...... 24 Post-installation tasks ...... 24 Installing on z/OS 103 Testing the WebLogic configuration ...... 24 ...... Deploying MiddleOffice & FrontOffice on WebLogic. 25 Overview ...... 103 Open Print and LDAP...... 25 Prerequisites ...... 103 XML/LDAP mode ...... 26 System requirements ...... 103 Full LDAP mode ...... 26 Operating principles ...... 103 Additional configuration ...... 30 Hardware requirements ...... 104 Memory allocation ...... 104 Setting Java parameters ...... 30 Configuring the browser ...... 31 Installation ...... 104 Transferring files ...... 104 Installing on Windows 33 Connecting to the z/OS system ...... 105 ...... Backstage under z/OS ...... 107 Application launch scripts ...... 108 Overview ...... 33 Native mode JCL example...... 108 Prerequisites ...... 33 Migration to the z/OS system...... 112 Installation ...... 33 Optimization and tips ...... 113 Remake ...... 33 QSAM access versus HFS ...... 113 Product description ...... 33 Compiling and linking to z/OS ...... 114 Installing Remake ...... 34 Using XPLINK to compile C files ...... 114 Post-installation ...... 37 Dataset storage ...... 114 Delivery...... 37 XPLINK Compilation with DLL...... 115

© Sefas Innovation, 2009 3 DLL under Open Edition ...... 115 Troubleshooting 157 DLL under QSAM ...... 115 ...... Files ...... 116 Overview ...... 157 Open Edition ...... 116 Under QSAM ...... 117 Common problems ...... 157 Using Techp ...... 117 TechAFP ...... 118 Index 159 QSAM TechPrint application launch ...... 119 ...... Assembling under OpenEdition ...... 120 Additional...... Tasks...... 121 . . Overview ...... 121 Installing Fonts in MiddleOffice, FrontOffice, and Projector ...... 121 TrueType fonts in Windows ...... 121 Installing in Open Print ...... 122 Installing on the server workstation...... 125 Encodings...... 125 Enabling Unicode ...... 125 Licensing Open Print ...... 126 The license file ...... 126 Static licenses ...... 126 Floating licenses ...... 127 Starting and stopping the license server . . . . . 128 Stopping the server ...... 128 Removing Open Print...... 128 Directory...... Structure ...... 131 . . Overview ...... 131 Remake, Delivery, and Studio ...... 131 Installation directory tree structure ...... 131 Installation directory contents ...... 131 bin directory ...... 131 common directory ...... 132 help directory ...... 132 optemp directory ...... 133 opd directory...... 133 opr and ops directories...... 133 MiddleOffice ...... 133 Installation directory tree structure ...... 133 Installation directory contents ...... 134 bin directory ...... 134 home directory ...... 134 install directory ...... 139 tomcat directory ...... 140 tools directory ...... 140 FrontOffice ...... 141 Installation directory tree structure ...... 141 Installation directory contents ...... 141 bin directory ...... 142 home directory ...... 142 install directory ...... 148 tomcat directory ...... 148 tools directory ...... 148 Projector ...... 149 Installation directory tree structure ...... 149 Installation directory contents ...... 149 bin directory ...... 149 home directory ...... 150 install directory ...... 155 repository directory ...... 155 tomcat directory ...... 155 tools directory ...... 155

4 Open Print 6.3 Installation Guide Introduction Overview Chapter 1: Introduction

Overview

This document describes how to install the applications of the Open Print software suite and how to configure them to work in a client/server environment. For information about the administration tools and production methods for MiddleOffice applications, see the MiddleOffice Administration Guide. For information about how to use the Open Print applications, see the corresponding User Guides.

Product description

Open Print is a suite of software products that provides an end-to-end approach to document creation and output. The Open Print suite’s applications help users manage all aspects of the document production process, from design to production to distribution. Customers use these integrated products for batch and interactive document production, print stream enhancement, output optimization, document viewing, and production management.

Naming conventions

If an Open Print application and its associated products are likely to be transferred between operating systems, the names of files, resources, and directories can contain only the following: • lower-case letters (a-z) • numbers (0-9), dashes (-) •underscores (_) •dots (.) File names cannot contain spaces or upper-case letters. These naming conventions ensure the applications function correctly when exported to any of the operating systems supported by Open Print.

6 Open Print 6.3 Installation Guide Before Installing Open Print Overview Chapter 2: Before Installing Open Print

Overview

This chapter tells users how to install and configure the engines, databases, and other components required to use Open Print.

Database configuration

The Open Print applications run on the following database systems: •MySQL •Oracle •DB2 Depending on your operating system, the databases the applications use might differ. For more information, see the Open Print Prerequisites Guide. During the installation process, configure and select the database to use as follows. 1. From the Open Print Setup dialog box, deselect the MySQL check box. This lets you select and configure an Oracle or DB2 database or an additional MySQL database. If you select MySQL 5.0, no configuration is necessary because this is the default database. 2. Select the database you want to use.

3. Browse the directory where the database is installed to locate the Java Database Connectivity (JDBC) drivers (do not include the bin directory in the path). The example below shows an Oracle installation path.

4. Enter the configuration parameters as follows. • Server: the IP address of the application server • Service: the customer-specific name of the service • Port: the port number used to communicate to the server

5. Enter the user login for the selected database.

6. Enter the login password for the selected database.

8 Open Print 6.3 Installation Guide Before Installing Open Print Database configuration Configuring DB2

7. Complete the installation as documented in the applicable product sections.

Configuring DB2

To configure DB2 for Open Print applications, do the following: 1. Install the JDBC driver for DB2 on the Open Print server. The driver resides in c:\program files\sqllib\java\db2java.zip on the DB2 server. 2. If necessary, make the JDBC driver available to Tomcat by placing the JDBC driver files under \tomcat\webapps\middleoffice\WEB-INF\lib.

3. Edit the \home\httpbean.conf file on the Open Print server. Comment out the login user ID and password for the default database, MySQL, as follows: # DATABASE #jdbc.userlogindbuser=Administrator #jdbc.userlogindbpasswd=SEFAS #jdbc.userloginpasswd=SEFAS Add the login user ID and password for DB2: # IBM DB2 jdbc.userlogindbuser=MOuser jdbc.userlogindbpasswd=MOpasswd jdbc.userloginpasswd=MOpasswd Comment out the following lines that set the JDBC driver for MySQL: jdbc.driver.JdbcOdbc=com.mysql.jdbc.Driver jdbc.DB.httpbean=jdbc:mysql://127.0.0.1:3306/sefas,-,- ,MaxTrans=50,MinTrans=10,UserId=sefas,Password=sefas Add the following lines to set the JDBC driver for DB2: jdbc.driver.JdbcOdbc=COM.ibm.db2.jdbc.net.DB2Driver jdbc.DB.httpbean=jdbc:db2://213.222.84.213:6789/devtest,-,- MaxTrans=30,MinTrans=2 4. In the second line above, configure the port number and the name of the database with the IP address of your DB2 server by typing the following:

jdbc.DB.httpbean=jdbc:db2://213.222.84.213:6789/devtest,-, DBSchema=MOuser,MaxTrans,MaxTrans=30,MinTrans=2,MaxTrans=30,MinTrans=2 Note When using DB2, make sure the TABLESPACE link to the MiddleOffice/FrontOffice user has a page size greater than 8192.

Configuring Oracle

To configure Oracle for Open Print, do the following: 1. If necessary, make the JDBC driver available to Tomcat by placing the JDBC driver files under \tomcat\webapps\middleoffice\WEB-INF\lib.

2. Edit \home\httpbean.conf as follows. Comment out the login user ID and password for the default database, MySQL: # DATABASE #jdbc.userlogindbuser=Administrator #jdbc.userlogindbpasswd=SEFAS #jdbc.userloginpasswd=SEFAS Add the login user ID and password for Oracle: # ORACLE jdbc.userlogindbuser=MOuser jdbc.userlogindbpasswd=MOpasswd jdbc.userloginpasswd=MOpasswd Comment out the following lines that set the JDBC driver for MySQL: jdbc.driver.JdbcOdbc=com.mysql.jdbc.Driver jdbc.DB.httpbean=jdbc:mysql://127.0.0.1:3306/sefas,-,- ,MaxTrans=50,MinTrans=10,UserId=sefas,Password=sefas Add the following lines to set the JDBC driver for Oracle: jdbc.driver.Oracle=oracle.jdbc.driver.OracleDriver jdbc.DB.httpbean=jdbc:oracle:thin:@Name_of_the_Oracle_server:1521:Name _of_the_DB_service_Oracle,-,-,MaxTrans=30,MinTrans=2

Verifying the C compiler

Most Open Print applications require a C compiler. Depending on your operating system, you must verify the C compiler is configured properly. For C compiler versions supported by the Open Print applications, see the Open Print Prerequisites Guide.

Verifying on UNIX

Command line verification To verify the C compiler is installed and running properly, run the following commands: • cc • ar If a command not found message appears, the installation is incorrect. See your C++ compiler documentation for more information. 10 Open Print 6.3 Installation Guide Before Installing Open Print Verifying the C compiler Verifying on Windows

Verifying on Windows

Verifying the C compiler is installed and running properly involves the following: • Setting environment variables • Checking the installation

Setting environment variables Environment variables that must be set include the following: • include: the access path to the include directory of the compiler • lib: the access path to the lib directory of the compiler • path: the access path to the bin directory of the compiler To set these variables, do the following: 1. Right-click My Computer and select Properties. 2. Click the Advanced tab and select Environment Variables. 3. Add or edit the Environment variables as follows: C:\Program Files\Microsoft Visual Studio\VC98\atl\include; C:\Program Files\Microsoft Visual Studio\VC98\mfc\lib; C:\Program Files\Microsoft Visual Studio\VC98\bin; Note These environment variable settings are simple examples. Your settings may differ. These instructions are for the Windows XP Professional operating system. Your procedure may differ slightly if you are using a different Windows operating system. Refer to your operating system’s documentation for more information.

Checking the installation To ensure the installation was successful and the compiler is working properly, do the following: 1. Open a DOS window by selecting Start>Programs>Accessories>Command Prompt. 2. Type the command cl. The following appears: Microsoft (R) 32-bit C/C++ Standard compiler Version 12.00.8168 for 80x86 Copyright (C) Microsoft Corp 1984-1998. All rights reserved. 3. Type the command link. The following appears:

Verifying on z/OS

Sefas recommends v2r6 or higher of the C/C++ compiler for z/OS installation. For earlier versions, verify the proper functionality before installing under z/OS. MiddleOffice cannot be installed under z/OS.

Backstage, Python, and JRE

Open Print uses the Backstage engine and Python scripts to process print files and templates. Backstage normally is automatically installed with MiddleOffice, but in some situations you need to manually install Backstage.

Installing Backstage

Backstage is normally installed as part of the installation wizard. If the Open Print Backstage option is deselected in the Select components dialog box, you must confirm the existing Backstage installation directory. This directory corresponds to the environment variable opInstallDir. Sefas strongly recommends keeping the Backstage option selected.

Manually installing Backstage To manually install Backstage, do the following: 1. Untar backstage.tar by typing the following: tar xvf backstage.tar This .tar file contains the following files: • oprint.lst This file contains a list of files in oprint.tar.gz with their respective version numbers. The file must be transferred in ASCII format. • oprint.tar.Z This file contains all installable data and must be transferred in binary form. • setup.sh This must be in executable form. If necessary, you can modify this file’s access rights to enable a transfer. The transfer must be in ASCII format. 2. Run setup.sh; information similar to the following appears: ########################################### # setup.sh FOR UNIX PLATFORMS ########################################### # PRODUCT: backstage # VERSION: 4.8 # OS: NT # COMPANY: sefas

12 Open Print 6.3 Installation Guide Before Installing Open Print Backstage, Python, and JRE Installing Backstage

########################################### # DATE: 200831071043 # TYPE: PROD # SETUP VERSION: 007 ########################################### ENTER THE INSTALLATION DIRECTORY Type the Open Print installation directory, opInstallDir, and press Enter. 3. If an Open Print product is already installed on your system, the following prompt appears: Keep Existing Common Directory (metrics,drivers.cmf...)? (Y or N) Type Y to keep the directory, N to delete it. If this directory exists and Open Print is already installed, it is saved to a specific directory (for example, C:\oprint\patch) along with the code for the installation program (for example, savebackstage_4.7_200831071043). 4. The installation begins and the following appears: ########################################### SAVING EXISTING INSTALLATION to savebackstage_4.7_200831071043.tar ########################################### ############### INSTALLING PRODUCT ############### ############### INSTALLATION ENDS ############### A previous version was found, To Uninstall current version and rollback to previous (type U) To Re-install new version (Type R) 5. Type U to uninstall the current version: ########################################### UNINSTALLING PRODUCT AND ROLLBACK TO PREVIOUS VERSION ########################################### ######################## INSTALLATION ENDS ######################## 6. Type R to reinstall the new version: ########################## INSTALLING PRODUCT ########################## INSTALLATION ENDS ########################## 7. When setup.sh finds the python package, the following appears: PROPOSED PYTHONHOME DIRECTORY = /home/sefas/oprint/python2.4 To c onfirm, type ENTER. Otherwise, type a new directory path. 8. Press Enter or type a new directory path and press Enter. The following appears: ########################## INSTALLING PYTHON ##########################

Python

Python is a standard scripting language that can completely or partially replace the Open Print assembly language. Python is installed as part of the Backstage installation. However, you need to specify an install directory for Python. To specify the installation directory under Windows, enter the path in the following dialog box that displays while running the installation wizard.

To specify the install directory under UNIX-based systems, specify the directory during the manual Backstage installation as noted in Manually installing Backstage on page 12.

Installing the Python Interpreter Python comes with an interpreter you can use to interactively test functions during program development. To install the interpreter, do the following: 1. Unzip Python.org-2.4.1-247-win32-ix86.zip to your Python installation directory. 2. Add the Python installation directory to the Windows PATH Environment Variable; an example is shown below. path C:\Program Files\Python 24

3. Add the PYTHONHOME variable as the Python installation directory, or set the environment variable from the command line by typing: set PYTHONHOME=C:\Program Files\Python 24 14 Open Print 6.3 Installation Guide Before Installing Open Print Backstage, Python, and JRE JRE

JRE

The Java Runtime Environment is a subset of files included in the Java Development Kit. To specify the install directory under Windows, enter the path in the dialog box that displays in the installation wizard.

Open Print MiddleOffice and FrontOffice support the following JRE versions: •1.5.x •1.6

Application servers

Open Print applications run on the following application servers: •Tomcat •IBM WebSphere •Oracle WebLogic

For supported versions, see the Open Print Prerequisites Guide. When installing an Open Print application, Tomcat is installed by default. To install Open Print using a different application server, do the following: 1. Deselect Tomcat and select the Advanced check box from the following installation wizard screen.

2. Click Next and select the appropriate application server.

See the sections below for information on configuring specific application servers.

16 Open Print 6.3 Installation Guide Before Installing Open Print Application servers Tomcat

Tomcat

Tomcat is the default application server installed with Open Print. It is automatically configured during installation. To modify the port numbers for Tomcat, do the following: 1. Select the Tomcat and Advanced check boxes from the Select Components dialog box in the installation wizard.

2. Follow the installation screens as described in the application’s installation section of this document until the first Advanced Configuration screen appears. Change the port numbers as required and click Next.

3. Change the SMD information as necessary and click Next.

4. Enter the DoubleByte information and click Next to complete the advanced configuration.

WebSphere

Installing Open Print applications for use with WebSphere includes the following steps: • Installing the application in Advanced Configuration • Configuring WebSphere •Deploying the .ear file Before installing on WebSphere, note the following: • Sefas recommends creating a dedicated application server within WebSphere for deploying each Open Print application (for example, one server for MiddleOffice and another for Projector). • If WebSphere is installed in standalone configuration, deploy the WebSphere administration console on the Open Print server. • Open Print requires a front-end HTTP server to serve the static components (HTML pages and images). Configure the HTTP server to use the WebSphere module plug-in for routing HTTP requests to the application server.

18 Open Print 6.3 Installation Guide Before Installing Open Print Application servers WebSphere

To install Open Print with WebSphere, do the following: 1. Follow the installation wizard steps described in the Installation chapter until you reach the Select Components dialog box. In this box, deselect Tomcat and Advanced. Selecting Advanced lets you set port numbers in the installation wizard. This is not necessary since port numbers are configured in WebSphere. Click Next.

2. Select EAR (WebSphere 6) from the Http Server Configuration dialog box. Click Next.

3. Click Next and continue the steps described in the Installation chapter to complete the installation. 4. Access the MiddleOffice directory on your machine and make sure the .ear (for example, middleoffice.ear) file exists.

Configuring WebSphere Use the WebSphere Administration console to configure the following to use WebSphere with Open Print applications. For detailed instructions on configuring in WebSphere, see the documentation that came with your version of WebSphere. To configure WebSphere for Open Print, do the following: 1. Create an HTTP virtual host and give it a unique name (for example, openprint_host). 2. Add a host alias using the pre-defined front end TCP port with a wildcard character as the host name. For example, *9200. 3. If one does not already exist, create a dedicated server (for example, openprint).

4. In the web container configuration, change the default virtual host in the Container Settings section to openprint_host (or whatever name you gave to the host in Step 1). 5. Add the TCP ports you want to use by changing the HTTP port settings in the web container configuration.

Note Configure WebSphere with one TCP port for the HTTP transport. You can add another TCP port if the administration console is deployed on the Open Print application server

6. In the Java and Processing Management section, set the Initial and Maximum heap sizes to 512.

7. In the WebSphere Variables section, create the following variables:

Variable Description

$OPENPRINT_BASE Location of the deployed web application. Example: $\installedApps\\middleoffice.ear\middleoffice.war

$OPENPRINT_HOME Location where application files reside. Example: \home\qualif\was_mo_62

$MIDDLEOFFICE_TLIB Location of the application libraries. Example: $\tomcat\webapps\middleo ffice\WEB-INF\lib

$PYTHON_HOME Location of Python. Example: \usr\local\python2.4\py2.4

Deploying the .ear file Use the WebSphere administration console to deploy .ear. For specific instructions on deploying the file, refer to the documentation you received with your application server. 1. Browse to the location of the .ear file (for example, ..\middleoffice\home\middleoffice.ear). 2. Select Generate Default Bindings. 3. Select Process embedded configurations. 4. Map the module to the appropriate servers. 5. Select the application and click Reference shared libraries. 6. Add the database libraries. 7. Select openprint_host. 8. Save the configuration.

Changing the class loading mode Open Print uses standard Java XML parsers. Because these XML parsers are also embedded in the WebSphere application server as shared components, you must configure the Open Print application to use its own classes instead of the shared ones. To do this, do the following: 1. In the Enterprise applications section, select the Open Print application (for example, middleoffice). 2. Select the Reload classes when application files are created check box. 3. Set the Polling interval for updated files to 3.

20 Open Print 6.3 Installation Guide Before Installing Open Print Application servers WebSphere

4. Select the Classes loaded with application classloader first radio button. 5. Click OK.

Creating shared libraries for database access You must provide the Open Print application access to the JDBC driver libraries. Open Print applications use their own data pool/JDBC connection. Therefore, it is not necessary to specify a data source in WebSphere. 1. In the Shared Libraries section, select the Scope check box. 2. Name the library DB_LIBS. For example, a DB2 database connection driver requires three driver files that can be defined as the following: • ${MIDDLEOFFICE_TLIB}\db2java.jar • ${MIDDLEOFFICE_TLIB}\db2jcc_license_cu.jar • ${MIDDLEOFFICE_TLIB}\db2jccu.jar 3. In the Enterprise Applications section, select the Open Print application (for example, middleoffice) and select Shared Library References. 4. Select the Open Print application and click the Reference shared libraries file. 5. Add the DB-LIBS library you created in Step 2 to the shared library.

Adding JniVpf API to the Java Library Path Open Print applications use the JNI component JniVpf. This resides in $\bin\backstage\\bin. You must add this path to the java.library.path environment variable. To do this, do the following: 1. In the Custom Properties section, create a property directive named java.library.path. 2. Enter the path where JniVpf resides to point to this directory.

Regenerating the WebSphere plug-in configuration For the HTTP server to properly map HTTP requests to the WebSphere server through WebSphere’s plug-ins, you need to update the plug-in configuration. From the Web Servers section, select the Web service and select Generate Plug-in.

Editing configuration files To complete the WebSphere configuration, you need to edit the following configuration files: • httpd.conf • the mime types file in \IHS\conf

httpd.conf

This file is located in \home\ServerStuff\websphere in the application’s installation directory and contains the directives that must be added to the main server configuration. Edit the configuration file of the front-end WebSphere http server (located in \IHS\conf\httpd.conf) so it appears as shown: Listen 9200 Listen 9201 # projector Alias /projector/home "/home/openprint/middleoffice/home" Alias /projector/dynhtml "/home/openprint/middleoffice/home/dynhtml" Alias /projector/html "/home/openprint/middleoffice/home/html/projector"

Alias /repository "/home/openprint/middleoffice/repository" # middleoffice Alias /openprint/middleoffice "/home/openprint/middleoffice/home" Alias /openprint/middleoffice/images "/home/openprint/middleoffice/home/ opWD/default/common/macro" # middleoffice Alias /openprint/middleoffice "/home/openprint/middleoffice/home" Alias /openprint/middleoffice/images "/home/openprint/middleoffice/home/ opWD/default/common/macro" After this modification, restart the IHS http server, regenerate the WebServer plug-in, and edit httpd.conf by adding the following lines: LoadModule was_ap20_module /usr/IBM/WebSphere/plug-ins/bin/ mod_was_ap20_http.so WebSphereplug-inConfig /usr/IBM/WAS61/WebSphere/AppServer/profiles/ sefas_was61/config/cells/saturneNode03Cell/nodes/WAS61_NODE/servers/ sefas_webserver/plug-in-cfg.xml

Note Your settings may differ slightly depending on your organization’s needs.

mime type

To add a new MIME type, edit and add one more line on the mime.types WebSphere application file found in the \IHS\conf\ WebSphere directory: application/x-javascriptjs application/x-java-jnlp-filejnlp application/x-koanskp skd skt skm This lets the server recognize the Open Print file extensions.

Note After completing the WebSphere configuration, you must restart the HTTP and application servers.

WebLogic

Installing Open Print applications for use with WebLogic includes the following: • Installing Open Print in Advanced Configuration • Configuring WebLogic • Performing post-installation tasks To install Open Print with WebLogic, do the following: 1. Follow the installation wizard steps described in the Installation chapter until you reach the Select Components dialog box. In this box, deselect To mc a t and Advanced. Selecting Advanced lets you set port numbers in the installation wizard. This is not necessary since port numbers are configured in WebLogic. Click Next.

22 Open Print 6.3 Installation Guide Before Installing Open Print Application servers WebLogic

2. Select WAR (Tomcat, WebLogic) from the Http Server Configuration screen.

3. Select the directory where WebLogic is to be installed. 4. Click Next and continue the steps described in the Installation chapter to complete the installation.

Configuring WebLogic on Windows Configure WebLogic for use with Open Print applications as follows. For detailed instructions, see your WebLogic documentation. 1. Launch WebLogic’s configuration wizard. 2. Select Create a new WebLogic configuration. 3. Select Basic WebLogic Server Domain. 4. Select Express Configuration. 5. Enter a user name and password for the domain. 6. Select Development mode and the appropriate JDK version. 7. Change the domain name to the Open Print application you are installing (for example, middleoffice). 8. Click Create.

Configuring WebLogic on UNIX Install Open Print with WebLogic on UNIX as follows: 1. Execute config.sh located in ...\bea\weblogic\81\common\bin. 2. Press 1 and Enter to create a new WebLogic configuration. 3. Press 2 and Enter to configure Basic WebLogic Server Domain 8.1.4.0. 4. Press 1 and Enter to run the wizard in Express mode. 5. Press 1 to modify or type a new administrator user name. Press Enter. 6. Press 2 to modify or type a new administrator password. Press Enter. 7. Press 3 to confirm the new administrator password was entered correctly. Press Enter. 8. Press 4 to enter a description of the new user. Press Enter. 9. Press 1 and Enter to use the Development Mode configuration. 10. Select the appropriate JDK to use and press Enter. 11. Press Enter to confirm the target location. 12. Press 1 to change the domain name to the Open Print application you are installing (for example, middleoffice). Press Enter to confirm the change. 13. Press Enter to exit the program when the following message appears: ****Domain Created Successfully****

Post-installation tasks After installing and configuring WebLogic, do the following: 1. Copy \home\ServerStuff\weblogic to \. 2. Rename \\config.xml to configorig.xml. 3. Rename \\config_sample.xml to config.xml. 4. Edit the WebLogic start scripts as follows. •For Windows, in startWebLogic.cmd add the following before the last line of text (%JAVA_HOME%\bin\java...): echo SEFAS IN set SEFAS_HOME= call "%SEFAS_HOME%\home\ServerStuff\Sethttp.bat" set JAVA_OPTIONS=%OPTIONS% echo SEFAS OUT •For UNIX, in startWebLogic.sh, add the following before the last line of text (%JAVA_HOME%\bin\java...): echo "SEFAS IN" SEFAS_HOME= . "$SEFAS_HOME/home/ServerStuff/SetHttp.sh" JAVA_OPTIONS="$OPTIONS" echo "SEFAS OUT"

Testing the WebLogic configuration To test the WebLogic configuration, do the following: 1. Start the .bat file for the database you have selected (for example, MysqlServer.bat) in c:\\install\home\serverstuff\ .

24 Open Print 6.3 Installation Guide Before Installing Open Print Open Print and LDAP WebLogic

2. Run WebLogic_sample.cmd (Windows) or startWebLogic_sample.sh (UNIX). 3. Check the traces in the command window. When WebLogic is configured correctly, the window appears as shown below.

You can now connect on http://localhost:8-/servlet/middleoffice. To change the port, activate the Advanced option in the installation wizard.

Deploying MiddleOffice & FrontOffice on WebLogic To deploy Open Print MiddleOffice and FrontOffice on WebLogic, do the following: 1. In the WebLogic administration console tree structure, click the Servers directory folder. 2. Select the Deploy a new web application module link. 3. Select the middleoffice.war file generated by the Open Print installation wizard on the host server. 4. Select the target WebLogic application server by clicking the appropriate check box in the Deploy a Web Application Module dialog box. 5. Select how you want source files to become accessible by clicking one of the radio buttons in the Source Accessibility section of the dialog box (Sefas recommends Copy this Web Application module onto every target for me). 6. In the same dialog box’s Identity section, type a name for your application module. For more information on the administration console, see your WebLogic documentation.

Open Print and LDAP

Open Print applications can use an LDAP server to replace the user name/password database authentication. Open Print supports the following LDAP servers: • eNDS (Novell) •OpenLDAP (University of Michigan) • Oracle Internet Directory (Oracle) • Sun Java System Directory Server (Sun) • Active Directory (Microsoft) •Lotus LDAP (IBM) Open Print uses two types of LDAP Authentication: •XML/LDAP mode • Full LDAP mode

XML/LDAP mode

The XML/LDAP method authenticates the user ID in the directory, and the permissions and applications are referenced in the password.xml file and loaded from the database. In this mode, define the users and groups in the directory repository and the other resources in password.xml.

Creating specific groups

When you add new pages to LDAP’s Directory Information Tree (DIT), map these entries corresponding to specific groups. You can add new groups using one of the following methods: • Create the new Directory Information Tree (DIT) sub-entry on the Open Print server (for example: ou=sefas,o=company,dc=dom) (Recommended). This lets you easily identify which groups are used. When you delete LDAP Open Print information, delete the complete sub-entry; only information in that tree is deleted. • Add groups to the same location as the existing groups.

Full LDAP mode

In full LDAP mode, the LDAP server manages security, including users, groups, permissions, and applications. Security-related information must be contained in a specific sub-tree of the DIT. Therefore, you must first define a new sub-tree for the server’s data (for example: ou=sefas,o=company,dc=dom). In this sub-tree, define the groups, applications, and permissions used by the Open Print server. If necessary, you can define users at the Open Print level, but they must already exist on the directory server. The user ID provides the link between Open Print and LDAP.

Configuration procedures for Open Print in LDAP mode

The Open Print architecture interacts with an LDAP server using the following files: • httpbean.conf This file configures the service directory’s login mode. • directory.conf This file contains the parameters for accessing the LDAP server. • schema.xml This file maps information between LDAP and Open Print. • export.xml This file contains information relating to the definition of users in the LDAP directory. It is used to update the database used by Open Print.

26 Open Print 6.3 Installation Guide Before Installing Open Print Open Print and LDAP Full LDAP mode

Definition of login mode

Configure httpbean.conf as follows to define the login mode:

Key Description

loginclass Default values:

httpbean.LoginUserXml in XML/LDAP mode httpbean.LoginUserDIrectory in full LDAP mode Example: loginclass=httpbean.LoginUserXml

loginmodel Defines authentication with LDAP and manages user rights: Valid values: ldap xldap Example: loginmodel=ldap

properties.userloginfname Defines the location of the LDAP server directory configuration file. Example: properties.userloginfname=.\directory.conf

security.userpolicyfile Defines database resources. The value points to \home\password.xml. Example: security.userpolicyfile=.\password.xml

Access to the LDAP server

Configure access to the server directory in the directory.conf file on the Open Print server, as follows:

Key Description

host Name or IP address of the service directory. Default value: 127.0.0.1 Example: host=127.0.0.1

port Port number for accessing the service. Default value: 389 Example: port=389

rootdn Defines a user (full dn) if the service directory does not accept login in anonymous mode. Default value: anonymous Example: rootdn=cn=roberto,ou=admin,dc=sefas,dc=fr

rootpw Defines the password of the root user. Example: rootpw=yitu

crypt_mode Password encrypting mode.

crypt_key Encryption key, if the encryption mode has been defined.

schema Name of XML configuration file (with or without extension). Required parameter. The value below points to the \home\schema.xml file. Example: schema=.\schema

root_directory Defines the tree structures in which users and groups are located. The tree structures are separated by the; character. By default, all LDAP tree structures are browsed. Example: root_directory=userTree;grpsTree

referral Defines whether the search can be made on other LDAP servers (dependent on the LDAP server itself – distributed mode). Valid values: true/false Default value: true Example: referral=true

Configuration of the tree schema

The schema.xml directory defines Open Print information in LDAP. The schema.xml configuration file matches the LDAP attributes with those of the Open Print applications. If the LDAP server is used for authentication, only information about groups and users must be matched. In full LDAP mode, it also contains the configuration of permissions and the application

28 Open Print 6.3 Installation Guide Before Installing Open Print Open Print and LDAP Full LDAP mode

for Projector. This information is organized as follows:

Key Parameters Description

User user_id User ID dbpwd Password for accessing the database dbuser User ID for accessing the database

Group name Group name users List of users applications* List of applications for the group permissions* List of permissions for the group

Application* Name Application name URL URL for accessing the application

Permissions* Name Name of permission Permissions List of permissions

Permission* Name Name of permission Scope Permissions scope Actions Available actions

*Only in full LDAP mode. In MiddleOffice, the identifier is defined by the user_id attribute in the user profile and the name of the group is defined by the name attribute in the group profile. In LDAP, the identifier corresponds to the cn attribute of the LDAP object person. In LDAP, the name of the group is defined by the cn attribute of the LDAP object groupofuniquenames. To match these fields, use a schema.xml file such as the one shown below: This sample schema above illustrates the following mapping.

Parameters in LDAP Parameters in Open Print

person user

uid user_id

givenName password

givenName dbpassword

Parameters in LDAP Parameters in Open Print

givenName dbuser

groupofuniquenames group

uniquemember users

Associate a user with one or more groups by references (as in the table above) by using the attribute field parameter, where each user can be physically associated with a single group, by using the contener parameter.

Additional configuration

Additional configuration of Open Print applications includes the following: • Setting Java parameters • Configuring the browser

Setting Java parameters

Files required for client installation reside on the server; install them on the client as follows: 1. Access the Open Print Login page or Home page.

2. Click the this file link as shown below.

3. Download and save ClientStuffInstall.exe to a location on your client machine. 30 Open Print 6.3 Installation Guide Before Installing Open Print Additional configuration Configuring the browser

4. Access the directory where you downloaded ClientStuffInstall.exe and double-click the file. This installs the .java policy file. 5. Open the Windows Control Panel and double-click Java Plug-in. In the Advanced tab, enter the following minimum and maximum java memory settings, then click Apply. -Xms64m -Xmx256m

Configuring the browser

When using Open Print applications, it is helpful to refresh your screen often to update variables and resources. To configure your browser to automatically refresh pages, do the following: 1. From Internet Explorer select Tools>Internet Options. 2. In the General tab’s Browsing history section, click Settings.

3. Select the Automatically radio button. Click OK, then click OK again.

32 Open Print 6.3 Installation Guide Installing on Windows Overview Remake Chapter 3: Installing on Windows

Overview

This chapter gives detailed instructions on installing the Open Print applications on Windows.

Prerequisites

Before installing Open Print in a Windows environment, make sure the server computer corresponds to the system prerequisites. This includes the following: 1. Make sure all prerequisite software is installed: • Database (Oracle, DB2, or MySQL); do the following before installing Open Print: • Create an empty database using the default parameters. • Create a database user ID and password. • Java Runtime Environment (JRE) • Application server (Tomcat, WebSphere, or WebLogic) 2. Make sure you have enough memory and disk space. • Memory: 512 MB for most Open Print applications • Disk space: 10 GB for most Open Print applications (some require only 4 MB) 3. Save existing repositories before installing a new version of Open Print. The repository archiving process is presented in the MiddleOffice Administration Guide. 4. Stop services and servers before launching the Open Print installation. 5. Deactivate local firewall and anti-spyware/virus programs before launching the installation.

For more information, see the Open Print Prerequisites Guide.

Note The database and application server are not required for Remake and Delivery installation.

Installation

Remake

Product description Open Print Remake is a print stream enhancement tool used to re-engineer and re-purpose legacy print streams from different systems and convert them to the Open Print architecture. Remake can convert documents from AFP-DS, PDF, Xerox Metacode, Xerox LCDS, HP-PCL, and PostScript formats into Sefas’ Virtual Page Format (VPF). It lets users colorize documents, add marketing messages, convert pages from simplex to duplex, add barcodes, add or modify inserter marks, and add or remove sections for their online versions. It then integrates the converted data into the production chain. The converted documents benefit from advanced processes such as sorting, © Sefas Innovation, 2009 33 Installation Remake

grouping, and indexing.

Installing Remake For more information on C compiler verification and Backstage, Python, and JRE installation, see Verifying the C compiler on page 10 and Backstage, Python, and JRE on page 12. Remake installation does not require a database and application server. To instal l Remake, do the fol low ing: •Double-click OpenPrintRemake6.3.exe on the installation CD. The dialog box shows the InstallShield Wizard extracting the installation files.

6. Specify the installation language: French or English. Click OK.

7. The InstallShield Wizard opens. Click Next.

34 Open Print 6.3 Installation Guide Installing on Windows Installation Remake

8. Specify the installation directory. The default directory for Remake is c:\oprint\opr. To change this, click Browse... and select the directory for the installation files. Click Next.

9. Specify the shared files directory. The default directory is c:\oprint. To change this, click Browse... and select the directory for the shared files. Click Next.

10. Specify the program group name for the Windows Start>Programs menu. By default, this name is SEFAS INNOVATION. To change it, click on one of the folder names in the list, or enter a new folder name in the text box. Click Next.

11. Check the parameters selected for the installation. If the information is incorrect, click Back to make changes. When correct, click Next.

The installation wizard shows the progress of the setup.

12. At the end of the installation, the wizard asks whether you want to open the Release Notes file. To open the file, click the check box. If you do not want to open the file, leave it as is. Click Next. 36 Open Print 6.3 Installation Guide Installing on Windows Installation Delivery

Post-installation If installing Open Print for the first time, Sefas recommends you log out and log back in before starting Remake.

Delivery

Product description Open Print Delivery is a post-production optimization tool used to create and manage electronic publishing processes. It lets users concatenate, merge, sort, and split jobs. It also enables house- holding and output right-sizing. When used with postal preparation software, Delivery validates and standardizes addresses and electronically commingles customers’ mail to maximize postal discounts. Delivery can manipulate data streams from Remake, MiddleOffice, and FrontOffice.

Installing Delivery For more information on C compiler configuration and Backstage, Python, and JRE installation, see Verifying the C compiler on page 10 and Backstage, Python, and JRE on page 12. Delivery installation does not require a database and application server. To install Delivery, do the following: 1. Double-click OpenPrintDelivery6.3.exe on the installation CD. The dialog box shows the InstallShield Wizard extracting the installation files.

2. Specify the installation language: French or English. Click OK.

3. The InstallShield Wizard opens. Click Next.

4. Specify the installation directory. The default directory for Delivery is c:\oprint\opd. To change this, click Browse... and select the directory for the installation files. Click Next.

38 Open Print 6.3 Installation Guide Installing on Windows Installation Delivery

5. Specify the shared files directory. The default directory is c:\oprint. To change this, click Browse... and select the directory for the shared files. Click Next.

6. Specify the program group name for the Windows Start>Programs menu. By default, this name is SEFAS INNOVATION. To change it, click on one of the folder names in the list, or enter a new folder name in the text box. Click Next.

7. Check the parameters selected for the installation. If the information is incorrect, click Back to make changes. When correct, click Next.

The installation wizard shows the progress of the setup.

8. At the end of the installation, the wizard asks whether you want to open the Release Notes file. To open the file, click the check box. If you do not want to open the file, leave it as is. Click Next.

40 Open Print 6.3 Installation Guide Installing on Windows Installation MiddleOffice

Post-installation If installing Open Print for the first time, Sefas recommends you log out and log back in before starting Delivery.

MiddleOffice

Product description Open Print MiddleOffice is a collaborative application used to design templates for a variety of customer communications, from simple letters to complex financial statements. During the design process, MiddleOffice lets everyone involved in the document production process work together by sharing objects and reusing components. MiddleOffice helps users manage their digital assets, define document presentation standards, meet compliance requirements, and reduce development time and maintenance costs.

Installing MiddleOffice For more information on C compiler verification and Backstage, Python, and JRE installation, see Verifying the C compiler on page 10 and Backstage, Python, and JRE on page 12. To install MiddleOffice on Windows, do the following: 1. Double-click OpenPrintMiddleOffice6_3.exe on the installation CD. The dialog box shows the InstallShield Wizard extracting the installation files.

2. Specify the installation language: French or English. Click OK.

3. The InstallShield Wizard opens. Click Next.

4. Specify the installation directory. The default directory for MiddleOffice is c:\middleoffice. To change this, click Browse... and select the directory for the installation files. Click Next.

5. Specify the program group name for the Windows Start>Programs menu. By default, this name is SEFAS INNOVATION. To change it, click on one of the folder names in the list, or enter a new folder name in the text box. Click Next.

42 Open Print 6.3 Installation Guide Installing on Windows Installation MiddleOffice

6. Select the components to install by clicking the check boxes next to the component name as shown. Click Next.

components must be imported from its administration interface. For more information, see the MiddleOffice Administration Guide. • Java Runtime 1.6 (Windows only) This component is required. • Select the check box to install the JRE. The Java Runtime Component installation wizard runs before the InstallShield Wizard continues with the MiddleOffice installation. • Deselect if JRE is already installed. •MySQL This is the default database. • Select the check box to install MySQL. • Deselect if MySQL is installed or if you want to use another database (a dialog box prompting you to select another appears after you click Next). •Advanced This option is used to access the configuration parameters of the Open Print MiddleOffice repository. • Select the check box to specify the port numbers of the HTTP and servlet servers. • Deselect to use the default connection ports. • English online help & French online help These options installs the online help and documentation in the language of your choice. 7. A Java installation wizard appears if Java has not been installed on your computer and you selected the Java Runtime 1.6 check box in the previous step. Click Next, then Finish. 8. Confirm the installation directory of the C compiler. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

9. Confirm the Python installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

44 Open Print 6.3 Installation Guide Installing on Windows Installation MiddleOffice

10. Locate the file HelpUS.tar.gz on the installation CD, then click Open. This installs the online help documentation.

11. Check the parameters selected for the installation. If the information is incorrect, click Back to make changes. When correct, click Next.

The installation wizard shows the progress of the setup.

12. At the end of the installation, select Display the start page and/or Install MiddleOffice as service, then click Finish.

The start page contains the release note and information about Open Print (technical support, documentation, contacts, and other information) in HTML. This page lets you start MiddleOffice (the server and the product) from hyperlinks without using the Start menu. If you select "Install MiddleOffice as service," this application will start automatically when you start your computer.

46 Open Print 6.3 Installation Guide Installing on Windows Installation MiddleOffice

Installing the DataMapper components The DataMapper tool is a plug-in for the jEdit text editor (it can also work on NetBeans) that is installed when the Tools component is included in the MiddleOffice, FrontOffice, and Projector installations. It generates a complete dataloader application based on the Python XML parser.

Prerequisites

Before installing the DataMapper components, make sure you have installed the following: •Engines • Java Runtime (version 1.5 or higher for jEdit operation) • Open Print Backstage engines (version 6.1.2.6 or higher) • Python interpreter (version 2.4) • PyXML libraries for Python (version 0.8.4 for Python 2.4) • Software Development Kit •jEdit 4.2 final setup • XML plug-in for jEdit (XML-0.14.zip) • XSLT plug-in for jEdit (XSLT-0.6.0.zip) • JPyDebug plug-in for jEdit (version 0.16) Note the JPyDebug component also requires the following jEdit plug-ins: • Sidekick • ErrorList Note The Python installation directory should be added to the PATH Windows environment variable.

Installation

To install DataMapper, do the following: 1. Copy all of the jEdit plug-ins into the jars subdirectory of your jEdit installation directory, including datastuffer.jar. (This is Sefas’ DataMapper plug-in for jEdit. For the XML and XSLT plug-ins, only the jar files in the archives supplied are required for normal use.) 2. Make sure the opInstallDir path of the MiddleOffice 6.2 engines is referenced in the PATH environmental variable and that no other Open Print engines are referenced. This lets Python access the DataMapper modules in the Open Print engines. 3. Open jEdit and click plugins>DataMapper>DataMapper to activate the DataMapper plug-in.

4. Click the ErrorList and JPyDebug plug-ins to activate them.

5. Click Utilities>Toubleshooting>Activity Log to activate the Activity Log.

48 Open Print 6.3 Installation Guide Installing on Windows Installation MiddleOffice

Configuration

After activating the DataMapper plug-in, two new floating windows appear along the main interface (look at the main Windows taskbar if they are hidden).

To make your jEdit window look like the examples in this document, dock the main DataMapper window at the bottom of the jEdit frame, then dock the structure browser window at the right. To do this, click the small arrow in the upper-left corner of the plug-in windows and activate the docking options. After docking, the jEdit window looks like the example below, with the Activity Log and Error List windows at the bottom of the frame and the JPyDebug window on the right.

The DataMapper plug-in options are accessed through the plug-in>plug-in Options menu in jEdit. The Options window is shown below.

The DataMapper generation directory is the working directory. The dataloader application is generated here. The dataloader is the module that reads the input stream and creates the data pool available to MiddleOffice users. The Python modules directory is the Open Print engines directory. Because DataMapper Python modules are provided inside the Open Print engines, the modules directory is equivalent to the \bin directory.

Dataloader generation

Only a sample XML file is needed to generate a dataloader application with the DataMapper. Sefas recommends naming the XML file as the desired dataloader application name (for example, dataloader.xml). The DataMapper window has two tabs: •The Node Editor tab is the main options tab, used for configuration and node definition. •The Data Navigator tab displays the variables when the generated application is tested (as it was done in with the "Check" script in Open Print Studio version 5).

Open the XML file in jEdit. The structure browser on the right displays the XML tree of your file. The XML file can be edited in jEdit to add or modify nodes and tags. Then refresh the structure browser to match it. When a particular node is selected in the structure browser, the DataMapper window displays specific options in the Node Editor tab (see Defining nodes). If the XML filename tag is selected (the top item in the structure browser at the right of the frame; the example in this document is client.xml), the options are as shown.

The Auto detect check box lets the DataMapper identify automatically iterative XML tag groups (same tag repeated several times) and mark them as iterative nodes. The Output Encoding text box lets the XML file be parsed in a specific encoding if no information is provided in the data file itself. The XML encoding is automatically detected and defaults to UTF- 8. The bound xml template stores the node information associated with the file, so you can quit jEdit, saving your XML data mapping. The file is automatically saved. Three buttons are provided for code generation & testing: Save, View source, and Run. 50 Open Print 6.3 Installation Guide Installing on Windows Installation MiddleOffice

Save generates the dataloader source code. If the code generation is successful, the following line appears: INFO: code production succeeded for client.xml props If you encounter an error while generating, an error report appears. Check the activity log window for further details on the error. View source displays the Python code generated for the dataloader application. Run triggers the dataloader application and activates the Data Navigator tab.

Defining nodes Before generating the dataloader code, define node types in the XML file by clicking the xml tag in the structure browser. The following options are displayed below.

The four nodes to define are shown below.

The Standard node represents a regular tag to be parsed by the DataMapper application. It is added in the data dictionary. The Ignored node is discarded during parsing and not added to the data dictionary. The Data Type Record node specifies an iterative message in the dataloader application. The Recipient node defines a document container in the dataloader application for batch operation. One document is generated in MiddleOffice for each Recipient node occurrence (this is equivalent to the definition of the Content tag in Open Print’s SchemaToDataloader tool).

Note For a simple dataloader generation, only the Recipient tag needs to be defined. The iterative nodes are automatically detected.

Adding functions to nodes The DataMapper allows use of additional functions during parsing (for example, data format or other data manipulation as it was done in Open Print Studio). This is done by defining functions in a Python module, then selecting the function to trigger with a given node.

Node mapping example Below is an example of mapping using the client.xml file bundled with MiddleOffice.

You can define a standard node before a recipient node in order to make global information available for the entire stream. With this operating mode, the batch operation matches the behavior of current dataloaders defined with the SchemaToDatamanager tool (with the tags Header and Content).

Generating and testing Once the required node types are defined, click Save to generate the dataloader source code. Click Run to launch the Data Navigator.

52 Open Print 6.3 Installation Guide Installing on Windows Installation MiddleOffice

The iterative and recipient nodes are displayed with buttons to browse the iterations. Now that the code is generated and tested, the dataloader application can be imported into MiddleOffice.

Dataloader import and use

When the dataloader is executed for testing inside the DataMapper tool, a full Open Print application structure (for example, with opFam and opAppli folders bearing the dataloader name) is generated in the DataMapper generation directory (for more information, see Configuration on page 49). The dataloader application is then imported and used as a regular TechPrint dataloader in MiddleOffice. After the dataloader application is imported, the dataloader window appears in MiddleOffice.

Note Variables coming from a dataloader created with the DataMapper are different from variables used in legacy dataloaders. The variable name contains all of the XML path with some additional characters. The data explorer can be configured in the main MiddleOffice design interface (in the Tools>Options window) to display either simplified or complete variable naming. The variable organization is like that in legacy dataloaders (for example, list of single/iterative containers and their respective variables).

FrontOffice

Product description Open Print FrontOffice is an interactive document production tool used to create personalized documents from templates created in MiddleOffice. FrontOffice can generate various types of business communication, from simple correspondence to complex personalized documents, by integrating with customers’ web portals and delivering the documents through centralized mail processing, email, local print, and other channels. Any document created for batch processing can be reused by FrontOffice for real-time production.

Installing FrontOffice For more information on C compiler verification and Backstage, Python, and JRE installation, see Verifying the C compiler on page 10 and Backstage, Python, and JRE on page 12. To install FrontOffice on Windows, do the following: 1. Double-click FrontOffice6_2.exe on the installation CD. The dialog box shows the InstallShield Wizard extracting the installation files.

2. Specify the installation language: French or English. Click OK.

3. The InstallShield Wizard opens. Click Next.

54 Open Print 6.3 Installation Guide Installing on Windows Installation FrontOffice

4. Specify the installation directory. The default directory for FrontOffice is c:\frontoffice. To change this, click Browse... and select the directory for the installation files. Click Next.

5. Specify the program group name for the Windows Start>Programs menu. By default, this is SEFAS INNOVATION. To change it, click on one of the folder names in the list, or enter a new folder name in the text box. Click Next.

6. Select the components to install by clicking the check boxes next to the component name as shown below. Click Next.

•FrontOffice This component is required. •Tomcat This is the default application server. • Select the check box to install Tomcat. • Deselect if an application server is already installed. You can select the server to use afterward (for more information, see Application servers on page 16). You must deselect this component to parameter a load-balancing installation (for more information, see Installing Projector in load balancing on page 65) For installation with WebLogic, WebSphere, Apache, and external Tomcat, see WebSphere on page 18 or WebLogic on page 22. •Open Print Backstage This is the Open Print engine. • Select the check box to install Backstage. • Deselect if an Open Print product is already installed with Backstage and if it is compatible with the FrontOffice version. You must then locate the corresponding directory (for more information, see Backstage, Python, and JRE on page 12). •Sample This option installs a sample application based on interactive production (letting the user personalize the content of the document). Sefas strongly recommends installing this component. • Java Runtime 1.6 (Windows only) This component is required. • Select the check box to install the JRE. The Java Runtime component is installed before FrontOffice. • Deselect if JRE is already installed. •Advanced This option is used to access the configuration parameters of the Open Print FrontOffice repository. • Select the check box to specify the port numbers of the HTTP and servlet servers. If you select the Advanced option, you can use the installation wizard to modify the port numbers or specify double byte. • Deselect to use the default connection ports. •MySQL • Select the check box to install MySQL. • Deselect if MySQL is installed or if you want to use another database (a dialog box prompting you to select another appears after you click Next).

56 Open Print 6.3 Installation Guide Installing on Windows Installation FrontOffice

7. Confirm the Python installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

8. Confirm the JRE installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

9. Check the parameters selected for the installation. If the information is incorrect, click Back to make changes. When correct, click Next.

The installation wizard shows the progress of the setup.

10. At the end of the installation, select Display the start page and/or Install FrontOffice as service, then click Finish.

The start page contains the release note and information about Open Print (technical support, documentation, contacts) in HTML. This page lets you start FrontOffice (the server and the product) from hyperlinks without using the Start menu.

58 Open Print 6.3 Installation Guide Installing on Windows Installation Projector

If you select "Install FrontOffice as service," this application will start automatically when you start your computer.

Projector

Product description Open Print Projector is a Java-based document search and retrieval application that can display any document processed by the Open Print suite. Its search engine can use any metadata in the user’s documents or extracted from its data stream with Remake. Customers use Projector for proofing, pre-print QA, and reprinting individual documents.

Installing Projector For more information on C compiler verification and Backstage, Python, and JRE installation, see Verifying the C compiler on page 10 and Backstage, Python, and JRE on page 12. To install Projector on Windows, do the following: 1. Double click OpenPrintProjector6_2.exe from the installation CD. The dialog box shows the InstallShield Wizard extracting the Projector installation files.

2. Specify the installation language: French or English. Click OK.

3. The InstallShield Wizard opens. Click Next.

4. Specify the installation directory. The default directory for Projector is c:\projector. To change this, click Browse... and select the directory for the installation files. Click Next.

60 Open Print 6.3 Installation Guide Installing on Windows Installation Projector

6. Select the following components to install by clicking the check boxes next to the component name, as shown below. Click Next.

•Projector This component is required. •Tomcat This is the default application server. • Select the check box to install Tomcat. • Deselect if an application server is already installed. You can select the server to use later (for more information, see Application servers on page 16). You must deselect this component to parameter a load-balancing installation (see Installing Projector in load balancing on page 65). •Open Print Backstage This is the Open Print engine. • Select the check box to install Backstage. • Deselect if an Open Print product is already installed with Backstage and if it is compatible with the Projector version. You must then locate the corresponding directory. For more information, see Backstage, Python, and JRE on page 12. • Java Runtime 1.6 (Windows only) This component is required. • Select the check box to install the JRE. The Java Runtime Component is installed before Projector. • Deselect if JRE is already installed. •Advanced This option is used to access the configuration parameters of the Open Print Projector repository. • Select the check box to specify the port numbers of the HTTP and servlet servers. • Deselect to use the default connection ports. •MySQL This is the default database. • Select the check box to install MySQL. • Deselect if MySQL is installed or if you want to use another database (a dialog box prompting you to select another appears after you click Next). 7. Confirm the Python installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

8. Confirm the JRE installation directory. To do this, browse through the directories until you find the correct path or enter the path in the text box (do not include the bin directory). Click OK.

62 Open Print 6.3 Installation Guide Installing on Windows Installation Projector

9. Check the parameters selected for the installation. If the information is incorrect, click Back to make changes. When correct, click Next.

The installation wizard shows the progress of the setup.

10. At the end of the installation, select Display the start page and/or Install Projector as service, then click Finish.

The start page contains the release note and information about Open Print (technical support, documentation, contacts) in HTML. This page lets you start Projector (the server and the product) from hyperlinks without using the Start menu. If you select "Install Projector as service," this application will start automatically when you start your computer.

64 Open Print 6.3 Installation Guide Installing on Windows Installation Projector

Installing Projector in load balancing Projector uses load balancing to spread the dispatch processing across several servers. When installing in load balancing, use one Apache 2 server and two Tomcat servers with the Tomcat servers installed on different machines.

Note You need to manually install the second Tomcat server. See the section below.

To install Projector in load balancing, do the following: 1. From the Select Components screen, deselect the Tomcat check box, and click Next.

2. Select the Load balancing (APACHE 2+ 2 Tomcat) radio button and click Next.

3. Browse to the directory where Apache 2 is installed and click OK.

4. Set the server names and port numbers of the second Tomcat server you will share in the section below and click Next.

5. Click Next to complete the installation. After completing the installation, you can run Apache and Tomcat on the same server:

66 Open Print 6.3 Installation Guide Installing on Windows Installation Studio

• home\ServerStuff\StartHttp.bat runs Projector with one Tomcat server. • home\ServerStuff\StartHttpLB.bat starts the second Tomcat server. This setup distributes the requests to the appropriate Tomcat server. When installing Projector under UNIX, follow the procedures above but use Network File System (NFS). For example: • On server 1, export the Projector installation directory. • On server 2, mount the server 2 directory on the same root path (mount server 2:\home\projector\home).

Sharing the second Tomcat server

The goal is to have the resources under one Tomcat to avoid duplication on all servers. To accomplish this, share the directory where the first Tomcat server is installed; for example: •On Server 1: • Create and share the d:\sharing directory. • Connect d:\sharing as e:. • Install Projector under e:\projector. •On Server 2: •Mount the \\server1\sharing shared directory on e:. Note that the drive letters above are only examples; yours may differ. Also ensure that the Java runtime environment variable (JAVA_HOME) in home\serverStuff\StartHttpLB.bat on server 2 is the same as on server 1. If not, change the variable and restart the server.

Studio

Product description Integrated with MiddleOffice, Open Print Studio is a document layout and editing tool that merges variable data from databases and fixed text into Virtual Page Format (VPF). Studio produces documents in three phases: assembly, composition, and rendering. It then translates documents to the output protocol selected in the rendering phase. Documents produced with Studio can be printed in different formats or sent to other peripherals such as faxes or electronic document management systems.

Installing Studio For more information on C compiler verification and installing Backstage, Python, and JRE, see Verifying the C compiler on page 10 and Backstage, Python, and JRE on page 12. To install Studio on Windows, do the following: 1. Double-click OpenPrintStudio6_2.exe on the installation CD. The dialog box shows the InstallShield Wizard extracting the Studio installation files.

2. Specify the installation language: French or English. Click Next.

3. The InstallShield Wizard opens. Click Next.

4. Specify the installation directory. The default directory for Studio is c:\oprint\ops. To change this, click Browse... and select the directory for the installation files. Click Next.

68 Open Print 6.3 Installation Guide Installing on Windows Installation Studio

5. Specify the shared files directory. The default directory is c:\oprint. To change this, click Browse... and select the directory for the shared files. Click Next.

6. Specify the program folder name. By default, this name is SEFAS INNOVATION. To change it, click on one of the folder names in the list, or enter a new folder name in the text box. Click Next.

7. Check the parameters selected for the installation. If the information is incorrect, click Back to make changes. When correct, click Next.

The installation wizard shows the progress of the setup.

8. At the end of the installation, the wizard lets you open the Release Notes file. To do this, select the check box. If you do not want to open the file, leave it as is. Click Next.

70 Open Print 6.3 Installation Guide Installing on Windows Installing on Vista Studio

Post-installation If installing Open Print for the first time, Sefas recommends you log out and log back in before starting Studio.

Installing on Vista

Before installing any of the applications on Vista, right-click on the application’s setup (for example, OpenPrintMiddleOffice6_2.exe) file. 1. Select Properties. 2. Select the Compatibility tab. 3. Select the Run this program in compatibility mode check box, then click OK.

To install the Open Print applications on Vista, follow the same instructions as for Windows XP.

72 Open Print 6.3 Installation Guide Installing on UNIX Overview MiddleOffice Chapter 4: Installing on UNIX

Overview

This chapter gives detailed instructions on installing the Open Print applications on UNIX-based systems.

Prerequisites

Before installing Open Print in a UNIX-based environment, make sure the server computer corresponds to the system prerequisites. This includes the following: 1. Make sure all prerequisite software is installed: • Database (Oracle, DB2, or MySQL); you must do the following before installing Open Print: • Create an empty database using the default parameters. • Create a database user ID and password. • Java Runtime Environment (JRE) • Application server (Tomcat, WebSphere, or WebLogic) 2. Make sure you have enough memory and disk space. • Memory: 512 MB for most Open Print applications • Disc space: 10 GB for most Open Print applications (some require only 4 MB) 3. Save existing repositories before installing any new version of Open Print. For more information, see the MiddleOffice Administration Guide. 4. Stop services and servers before launching the Open Print product setup. 5. Deactivate local firewall and anti spyware/virus programs before launching the installation program.

For more information, see the Open Print Prerequisites Guide.

Installation

MiddleOffice

Installing MiddleOffice For more information on C compiler verification and Backstage, Python, and JRE installation, see Verifying the C compiler on page 10 and Backstage, Python, and JRE on page 12. If Open Print is already installed, make sure the HTTP server and database server are off before installing the new version. Open Print is installed on a UNIX system from a Windows workstation. This procedure includes an intermediate stage that includes a temporary installation on the client workstation. The files are then copied on the UNIX system using remote commands by the user. To install MiddleOffice on a UNIX-based system, do the following: 1. Log in to your user account on the UNIX server. In this document, the user is called sefas and is attached to the \home\sefas tree structure. 2. Open the .rhosts file in a text editor by typing the following. In this document the text editor is Nano, but any UNIX-compatible text editor can be used. nano .rhosts 3. When the text editor opens, type the following: name_client_station[tab]+ • name_client_station is the name of the client workstation from which the installation is executed. • [tab] means a tabulation separates name_client_station from + (that is, press the tab key after typing the name of the client station, then type +). 4. Check the rsh command. To do this, open a DOS window and type the following: rsh server_name -l sefas ls • server_name is the name of the UNIX server computer. • sefas is the name of the UNIX user. If the rsh command does not work, do the following: •Type ping_name_client_station on the server workstation. If DOS responds ping request could not find host, check the \etc\hosts or the DNS configuration to locate the client workstation IP address. If it cannot be found, open the host file and enter the IP address. •Type ping_server_name on the client computer. If DOS responds ping request could not find host, check the WINNT\system32\drivers\etc\hosts or the DNS configuration to locate the client workstation IP address. If it cannot be found, open the file and add it. If the rsh command still does not work, connect to the server and run theinstall.sh script to update access rights for critical files. For example, to change the rights to Tomcat, type the following: chmod -R +x tomcat/bin 5. Begin installation on the client workstation (Windows). To do this, double-click OpenPrintMiddleOffice6_2.exe on the installation CD. The dialog box shows the InstallShield Wizard extracting the MiddleOffice installation files.

74 Open Print 6.3 Installation Guide Installing on UNIX Installation MiddleOffice

6. Specify the installation language: French or English. Click OK.

7. The InstallShield Wizard opens. Click Next.

8. Specify the installation directory. The default directory for MiddleOffice under Windows is c:\middleoffice. To change this for installation under UNIX, click Browse... and select the directory in which you want to install MiddleOffice. Click Next.

To access the UNIX installation, add the prefix x:\unix to the installation directory path. The character x: represents a Windows system drive. For example, if you want to install MiddleOffice in the \home\sefas\middleoffice directory of the UNIX server, select the following access path: c:\unix\home\sefas\middleoffice

9. Click OK, then click Next.

76 Open Print 6.3 Installation Guide Installing on UNIX Installation MiddleOffice

10. Select the server operating system by clicking the corresponding radio button: Windows, AIX, Linux, Sun, or HP-UX. Click Next.

11. Specify the program group name for the Windows Start>Programs menu. By default, this name is SEFAS INNOVATION. To change it, click on one of the folder names in the list, or enter a new folder name in the text box. Click Next.

12. Select the components to install by clicking the check boxes next to the component name as shown. When finished, click Next.

•MiddleOffice This component is required. •Tomcat This is the default application server. • Select the check box to install Tomcat. • Deselect if an application server is already installed. You can select the server to use afterward (for more information, see Application servers on page 16). You must deselect this component to parameter a load-balancing installation (see Installing Projector in load balancing on page 100). •Open Print Backstage This is the Open Print engine. • Select the check box to install Backstage. • Deselect if an Open Print product is already installed with Backstage and if it is compatible with the MiddleOffice version. You must then locate the corresponding directory. For more information, see Backstage, Python, and JRE on page 12. •Tools This option installs some tools for configuring fonts, batching MiddleOffice export and import, and other actions. It also installs examples of a dataloader and standard plug- ins (for example, Customs/tools in Open Print 6.0). To be used with MiddleOffice, these components must be imported from its administration interface. For more information, see the MiddleOffice Administration Guide. • Java Runtime 1.6 (Windows only) This component is required. • Select the check box to install the JRE. The Java Runtime Component is installed before MiddleOffice. • Deselect if JRE is already installed. •MySQL This is the default database. • Select the check box to install MySQL. • Deselect if you want to use another database (a dialog box prompting you to select another appears after you click Next). •Advanced This option is used to access the configuration parameters of the Open Print MiddleOffice repository. • Select the check box to specify the port numbers of the HTTP and servlet servers. • Deselect to use the default connection ports. • English online help & French online help These options install the online help and documentation in the language of your choice.

78 Open Print 6.3 Installation Guide Installing on UNIX Installation MiddleOffice

13. The Backstage engines for UNIX are stored externally in a .tar file. Specify the location of the .tar file by clicking through the folders and selecting the location in which you want it to go, then click Open.

14. Confirm the installation directory of the C compiler. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

15. Confirm the Python installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

16. Confirm the JRE installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

17. Locate and select the online help documentation to be installed by browsing through the files in the dialog box, then click Open.

18. Enter the server and user names in the text boxes, then click Next.

80 Open Print 6.3 Installation Guide Installing on UNIX Installation MiddleOffice

19. Enter the password you want to use in the text box, then click Next.

20. Check the parameters selected for the installation. If the information is incorrect, click Back to make changes. When correct, click Next.

The installation wizard shows the progress of the setup.

21. When the setup is finished, a DOS window lets you know it is ready to copy the installation files. Press any key to continue.

The DOS window shows the copy status.

22. At the end of the installation, select Display the start page if you want to start MiddleOffice using hyperlinks instead of the Start menu. The start page also contains the release note and other relevant information (technical support, documentation, and contacts).

82 Open Print 6.3 Installation Guide Installing on UNIX Installation MiddleOffice

Transferring to the UNIX server After the Windows installation, the client station begins transferring the UNIX engines and configuration files to the UNIX server specified in the installation wizard. If the transfer is interrupted, you can restart it with installunix.bat, located in C:\unix\home\sefas\install.

Note If the installation can be executed only with remote commands (rsh/ftp), do the following: 1. If the ftp failed (or cannot be used), you must transfer c:\unix\home\sefas\product.tar.z and post_install.sh to \home\sefas\oprint. Then connect to the server and run post_install.sh. 2. If the rsh failed (or cannot be used), you must connect to the server and run the install.sh script to update the access rights for critical files.

Front Office

Installing FrontOffice For more information on C compiler configuration and Backstage, Python, and JRE installation, see Verifying the C compiler on page 10 and Backstage, Python, and JRE on page 12. Before installing, be sure the server workstation meets the system hardware requirements. For more information, see the Open Print Prerequisites Guide. If Open Print is already installed, make sure the HTTP server and database server are off before installing the new version. Open Print is installed on a UNIX system from a Windows workstation. This procedure includes an intermediate stage that includes a temporary installation on the client workstation. The files are then copied on the UNIX system using remote commands by the user. To install FrontOffice on a UNIX-based system, do the following: 1. Log in to your user account on the UNIX server. In this document, the user is called sefas and is attached to the \home\sefas tree structure. 2. Open the .rhosts file in a text editor by typing the following. In this document the text editor is Nano, but any UNIX-compatible text editor can be used. nano .rhosts 3. When the text editor opens, type the following: name_client_station[tab]+ • name_client_station is the name of the client workstation from which the installation is executed. • [tab] means a tabulation separates name_client_station from + (press the tab key after typing the name of the client station, then type +). 4. Check the rsh command. To do this, open a DOS window and type the following: rsh server_name -l sefas ls • server_name is the name of the UNIX server computer. • sefas is the name of the UNIX user. If the rsh command does not work, do the following: •Type ping_name_client_station on the server workstation. If DOS responds "ping request could not find host," check the \etc\hosts or the DNS configuration to locate the client workstation IP address. If it cannot be found, open the host file and type the IP address. •Type ping_server_name on the client computer. If DOS responds "ping request could not find host," check the WINNT\system32\drivers\etc\hosts or the DNS configuration to locate the client workstation IP address. If it cannot be found, open the file and add it. If the rsh command still does not work, connect to the server and run theinstall.sh script to update access rights for critical files. For example, to change the rights to Tomcat, type the following: chmod -R +x tomcat/bin

84 Open Print 6.3 Installation Guide Installing on UNIX Installation Front Office

5. Begin installation on the client workstation (Windows). To do this, double-click OpenPrintFrontOffice6_2.exe on the installation CD. The dialog box shows the InstallShield Wizard extracting the installation files.

6. Specify the installation language: French or English. Click OK.

7. The InstallShield Wizard opens. Click Next.

8. Specify the installation directory. The default directory for FrontOffice under Windows is c:\frontoffice. To change this for UNIX installation, click Browse... and select the directory for the installation files. Click Next.

. To access the UNIX installation, add the prefix x:\unix to the installation directory path. The character x: represents a Windows system drive. For example, if you want to install FrontOffice in the \home\sefas\frontoffice directory of the UNIX server, select the following access path: c:\unix\home\sefas\frontoffice Click Next.

9. Select the server operating system by clicking the corresponding radio button: Windows, AIX, Linux, Sun, or HP-UX. Click Next.

86 Open Print 6.3 Installation Guide Installing on UNIX Installation Front Office

11. Select the components to install by clicking the check boxes next to the component name as shown below. When finished, click Next.

•FrontOffice This component is required. •Tomcat This is the default application server. • Select the check box to install Tomcat. • Deselect if an application server is already installed. You can select the server to use afterward (for more information, see Application servers on page 16. •Open Print Backstage This is the Open Print engine. • Select the check box to install Backstage. • Deselect if an Open Print product is already installed with Backstage and if it is compatible with the FrontOffice version. You must then locate the corresponding directory. For more information, see Backstage, Python, and JRE on page 12. •Sample This option installs a sample of an indexed document base to launch document searches. Sefas strongly recommends installing this component. • Java Runtime 1.6 (Windows only) This component is required. •Advanced This option is used to access the configuration parameters of the Open Print FrontOffice repository. • Select the check box to specify the port numbers of the HTTP and servlet servers. If you select the Advanced option, you can use the installation wizard to modify the port numbers or specify double byte. On the first screen, you can modify the defaults shown. • Deselect to use the default connections. •MySQL • Select the check box to install MySQL. • Deselect if you want to use another database (a dialog box prompting you to select another appears after you click Next). 12. Specify the location of the .tar file by clicking through the folders and selecting the location in which you want it to go, then click Open. This is where the Backstage engines for UNIX are stored.

13. Confirm the Python installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

88 Open Print 6.3 Installation Guide Installing on UNIX Installation Front Office

14. Confirm the JRE installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

15. Enter the server and user names in the text boxes, then click Next.

16. Enter the password you want to use in the text box, then click Next.

17. Check the parameters selected for the installation. If the information is incorrect, click Back to make changes. When correct, click Next.

The installation wizard shows the progress of the setup.

18. When the setup is finished, a DOS window lets you know it is ready to start copying files. Press any key to continue.

90 Open Print 6.3 Installation Guide Installing on UNIX Installation Front Office

The DOS window shows the copy status.

19. At the end of the installation, select Display the start page if you want to start FrontOffice using hyperlinks instead of the Start menu. The start page also contains the release note and other relevant information (technical support, documentation, and contacts).

Projector

Installing Projector For more information on C compiler verification and Backstage, Python, and JRE installation, see Verifying the C compiler on page 10 and Backstage, Python, and JRE on page 12. 1. Log in to your user account on the UNIX server. In this document, the user is called sefas and is attached to the \home\sefas tree structure. 2. Open the .rhosts file in a text editor by typing the following. In this document the text editor is Nano, but any UNIX-compatible text editor can be used. nano .rhosts

92 Open Print 6.3 Installation Guide Installing on UNIX Installation Projector

3. When the text editor opens, type the following: name_client_station[tab]+ • name_client_station is the name of the client workstation from which the installation is executed. • [tab] means a tabulation separates name_client_station from + (that is, press the tab key after typing the name of the client station, then type +). 4. Check the rsh command. To do this, open a DOS window and type the following: rsh server_name -l sefas ls • server_name is the name of the UNIX server computer. • sefas is the name of the UNIX user. If the rsh command does not work, do the following: •Type ping_name_client_station on the server workstation. If DOS responds ping request could not find host, check the \etc\hosts or the DNS configuration to locate the client workstation IP address. If it cannot be found, open the host file and type the IP address. •Type ping_server_name on the client computer. If DOS responds "ping request could not find host," check the WINNT\system32\drivers\etc\hosts or the DNS configuration to locate the client workstation IP address. If it cannot be found, open the file and add it. If the rsh command still does not work, connect to the server and run theinstall.sh script to update access rights for critical files. For example, to change the rights to Tomcat, type the following: chmod -R +x tomcat/bin 5. Begin installation on the client workstation (Windows). To do this, double-click OpenPrintProjector6_2.exe on the installation CD. The dialog box shows the InstallShield Wizard extracting the installation files.

6. Specify the installation language: French or English. Click OK.

7. The InstallShield Wizard opens. Click Next.

8. Specify the installation directory. The default directory for Projector under Windows is c:\projector. To change this for UNIX installation, click Browse... and type the directory path for the installation files. To access the UNIX-based installation, add the prefix x:\unix to the installation directory path. The character x: represents the Windows system drive in which you want to install Projector. For example, if you want to install Projector in the \home\sefas\projector directory of the UNIX server, select the following access path: c:\unix\home\sefas\projector

9. Click OK, then click Next.

94 Open Print 6.3 Installation Guide Installing on UNIX Installation Projector

10. Select your operating system, then click Next.

11. Specify the program group name for the Windows Start>Programs menu. By default, this name is SEFAS INNOVATION. To change it, click one of the folder names in the list, or type a new folder name in the text box. Click Next.

12. Select the components to install by clicking the check boxes next to the component name. When finished, click Next.

•Projector This component is required. •Tomcat This is the default application server. • Select the check box to install Tomcat. • Deselect if an application server is already installed. You can select the server to use afterward (for more information on other servers, see Application servers on page 16). •Open Print Backstage This is the Open Print engine. • Select the check box to install Backstage. • Deselect if an Open Print product is already installed with Backstage and if it is compatible with the Projector version. You must then locate the corresponding directory. For more information, see Backstage, Python, and JRE on page 12. • Java Runtime 1.6 (Windows only) This component is not required for installation under UNIX. •Advanced This option is used to access the configuration parameters of the Open Print Projector repository. • Select the check box to specify the port numbers of the HTTP and servlet servers. If you select the Advanced option, you can use the installation wizard to modify the port numbers or specify double byte. On the first screen, you can modify the defaults shown. • Deselect to use the default connections. •MySQL • Select the check box to install MySQL. • Deselect if you want to use another database (a dialog box prompting you to select another appears after you click Next). 13. Specify the location of the .tar file by browsing through the folders and selecting the location in which you want it to go, then click Open. This is where the Backstage engines for UNIX are stored.

96 Open Print 6.3 Installation Guide Installing on UNIX Installation Projector

14. Confirm the Python installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

15. Confirm the JRE installation directory. To do this, browse through the directories until you find the correct path, or enter the path in the text box (do not include the bin directory). Click OK.

16. Enter the server and user names in the text boxes, then click Next.

17. Enter the password you want to use in the text box, then click Next.

18. Check the parameters selected for the installation. If the information is incorrect, click Back to make changes. When correct, click Next.

The installation wizard shows the progress of the setup.

98 Open Print 6.3 Installation Guide Installing on UNIX Installation Projector

19. When the setup is finished, a DOS window lets you know it is ready to start copying files. Press any key to continue.

The DOS window shows the copy status.

20. At the end of the installation, select Display the start page if you want to start Projector online. The start page contains the release notes and other information (technical support, documentation, and contacts) and lets the user start FrontOffice (the server and the product) from hyperlinks without using the Start menu.

Note You need to manually install the second Tomcat server. See the section below.

To install Projector in load balancing, do the following: 1. From the Select Components screen, deselect the Tomcat check box and click Next.

100 Open Print 6.3 Installation Guide Installing on UNIX Installation Projector

2. Select the Load balancing (APACHE 2+ 2 Tomcat) radio button and click Next.

3. Browse to the directory where Apache 2 is installed and click OK.

4. Set the server names and port numbers of the second Tomcat server you will share in the section below and click Next.

5. Click Next to complete the installation. After completing the installation, you can run Apache and Tomcat on the same server: • home\ServerStuff\StartHttp.bat runs Projector with one Tomcat server. • home\ServerStuff\StartHttpLB.bat starts the second Tomcat server. This setup distributes the requests to the appropriate Tomcat server. When installing Projector under UNIX, follow the procedures above but use Network File System (NFS). For example: • On server 1, export the Projector installation directory. • On server 2, mount the server 2 directory on the same root path (mount server 2:\home\projector\home).

Sharing the second Tomcat server

The goal is to have the resources under one Tomcat to avoid duplication on all servers. To accomplish this, share the directory where the first Tomcat server is installed; for example: •On Server 1: • Create and share the d:\sharing directory. • Connect d:\sharing as e:. • Install Projector under e:\projector •On Server 2: •Mount the \\server1\sharing shared directory on e:. Note that the drive letters above are only examples; yours may differ. Also ensure the Java runtime environment variable (JAVA_HOME) in home\serverStuff\StartHttpLB.bat on server 2 is the same as on server 1. If not, change the variable and restart the server.

102 Open Print 6.3 Installation Guide Installing on z/OS Overview System requirements Chapter 5: Installing on z/OS

Overview

This chapter gives detailed instructions on installing the Open Print applications on z/OS systems.

Prerequisites

System requirements

The following are required to develop and execute an Open Print z/OS environment: •z/OS kernel Two types of engines are generated: • z/OS load modules These load modules are generated in a z/OS loadlib by a z/OS linker in the Open Edition environment. The only prerequisite in a classical z/OS batch environment from a Job Control Language is the level of the z/OS C/Cobol/PLI language runtime library. • z/OS program objects Program objects are executables on a Hierarchical File System (HFS). They are generated by a z/OS binder call, which is a link editor that generates load module formats specifically for execution under the Open Edition shell. •C compiler The administrator must configure the compiler before launching Open Print. For more information, see Verifying the C compiler on page 10. • DFSMS/z/OS Sefas strongly recommends DFSMS/z/OS level 1.5.0 because it provides optimization in HFS input/output handling. • LE/370 Open Print has been validated with the Language Environment (LE) OS/390 2.6 Language Environment (5647-A01) Release v2r6m0.

Operating principles Open Print applications under z/OS are generated from makefile files in the POSIX environment using POSIX scripts. You can run the resulting C applications either under the Shell POSIX environment or with a z/OS loadlib in a classical batch environment using a z/OS JCL.

Hardware requirements

Workstation prerequisites

The workstation from which you install Open Print must include the following: •CD-ROM drive • Configured access to z/OS mainframe using a standard FTP tool and ability to complete get and put transfers • Ability to open a tn3270 session on the z/OS mainframe

z/OS user prerequisites

The user account created to install and execute Open Print must be able to: • Execute any command on the z/OS mainframe • Execute the C compiler on z/OS • Let the binder generate an executable file on HFS or a load module on z/OS Note You can administer these rights using tools such as RACF and TOPSECRET. Before using other administration tools, consult Sefas.

Memory allocation To ensure the memory allocation for each process run on z/OS is precise, do the following: 1. Set the SIZE parameter in the TSO/E login screen; Sefas recommends 512 MB. This is necessary because a compilation process directly completed from z/OS can use a large amount of memory. 2. Make sure the JCL’s REGION parameter is adapted according to the corresponding application’s memory consumption.

Installation

Transferring files

Under Open Edition, installation is run through the setup.sh script. The z/OS Load Modules needed for the Open Print engine’s BATCH execution are located in the bin directory as *.xmit files. Depending on the product being installed, available files include: • techcodr.xmit • techsort.xmit • techafp.xmit To install the engines in queued sequential access method (QSAM), proceed to an ftp transfer and extract the engine from the *.xmit file. To transfer the files, do the following: 1. Using the client ftp utility, transfer the partitioned z/OS type files (in *.xmit format) from the bin directory to FB 80 format QSAM files on the host computer. An example is shown below. ftp address_IP_MVS set binary

104 Open Print 6.3 Installation Guide Installing on z/OS Installation Connecting to the z/OS system

lcd /u/user/oprint/bin quote site recfm=fb lrecl=80 blksize=800 primary=100 secondary=200 put techcodr.xmit put techsort.xmit put techafp.xmit etc... The quote site command lets the system allocate a file capable of receiving the .xmit file. 2. Install PDS libraries from a TSO panel using the RECEIVE command as follows. RECEIVE INDA (TECHCODR.XMIT) RECEIVE INDA (TECHSORT.XMIT) RECEIVE INDA (TECHAFP.XMIT) If a dataset does not exist, the system requests a dataset name. If so, type the following: dsname (V4@5018 .LOAD) The RECEIVE command automatically substitutes the first element of the file name by the TSO ID of the user performing the receive.

Connecting to the z/OS system

To connect to the z/OS system, do the following: 1. Open a 3270 emulator from an NT workstation and type the z/OS system IP address. Once the connection has been established, the following screen appears.

2. Type L TSO, then press Enter. The following screen appears.

3. Type your user name and password. 4. Press Enter. The following screen appears.

5. From the TSO console, type ISPF to enter the ISPF session.

6. The screen displays the dataset list.

106 Open Print 6.3 Installation Guide Installing on z/OS Installation Backstage under z/OS

7. To return to the ISPF main menu, press F3.

Note Your ISPF panel may be customized differently from those shown above. For more information on accessing OMVS Unix System Services sessions on your machine, contact your z/OS administrator.

Backstage under z/OS

To install Backstage under z/OS, do the following: 1. Connect to z/OS using a 3270 terminal. When the connection is established, type L TSO. 2. Type your user name and password and press Enter. 3. Type ISPF. The following screen appears.

4. Position the cursor on the Option line and type m.10 to connect to z/OS (the Open Edition mode is a z/OS emulation mode).

The application run script is located in the program directory of the letter application. You can configure the Techp options in the compil.sh script in the following ways: • Without option (Open Edition compilation mode only). •With -N option (Open Edition Native compilation mode). •With -X option (Native compilation mode only). •With -D option to place the side decks and the corresponding environment variable.

For more information on the available options with z/OS, see the Open Print Techfont Reference Manual.

Application launch scripts

Compil.sh

Exe.sh

#!/bin/sh export opInstallDir=/u/sftscts/oprint echo "opInstallDir Variable= $opInstallDir" export opWD=/u/sftscts echo "opWD Variable= $opWD" export opFam=famrep echo "opFam Variable= $opFam" export opAppli=letter echo "opAppli Variable= $opAppli" export LIBPATH=/home//oprint/bin/Objets $opWD/$opFam/$opAppli/program/letter -i $opAppli.dat -o $opAppli.bal $opInstallDir/bin/techcodr -dn dvpf -tm $opAppli.tab -ib $opAppli.bal -ov $opAppli.vpf $opInstallDir/bin/techcodr -dn hp -iv $opAppli.vpf -od $opAppli.hp $opInstallDir/bin/techcodr -dn afp -iv $opAppli.vpf -od $opAppli.afp To leave the Open Edition mode and return to the native mode, type Exit and press Enter.

Native mode JCL example • ASCORPRNN: Native mode assembly, composition, and rendering JCL • ASCOPRUU: HFS mode assembly, composition, and rendering JCL • ASCOPRNN JCL: Example of a JCL enabling to launch the assembly, composition, and rendering stages in native mode (dataset). In this example, Sefas binaries are under LOADX; customer binaries are under PROGS.LOAD. Both data sets are PO-E. The customer binaries are xplink binaries, as are the DLL. All steplib steps must be modified because a JCL can contain many of them. Example: //SFTSBSJ1 JOB (999,POK),'JLB',REGION=4M,CLASS=C, // NOTIFY=SFTSBSJ //* //**------** //* START ASSEMBLY - TEMPORARY SGML CREATION * //**------** //ASM EXEC PGM=RCA4CCF, 108 Open Print 6.3 Installation Guide Installing on z/OS Installation Backstage under z/OS

// PARM='/-A DD:PARAM' //STEPLIB DD DSN=SFTSBSJ.PROGS.LOAD,DISP=SHR // DD DSN=SFDVBDR.LOADX,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //DATA DD DSN=SFTSBSJ.RCA4CCF.DATA, // DISP=SHR //SGML DD DSN=&&SGML, // DISP=(NEW,PASS), // UNIT=3390,DCB=(RECFM=VB,LRECL=1024,BLKSIZE=25604), // SPACE=(CYL,(10,5),RLSE) //* //**------** //* NATIVE MODE ASSEMBLY PARAMETERS * //**------** //PARAM DD * -E opInstallDir=/u/sftsbsj/oprint -E opWD=/u/sftsbsj/oprint -E opFam=ccf -E opAppli=rca4ccf -i DD:DATA -o DD:SGML /* //* //**------** //* START COMPOSITION - DELETE AND RECREATE VPF * //**------** //COMPODEL EXEC PGM=IEFBR14 //VPF DD DSN=SFTSBSJ.RCA4CCF.VPF, // DISP=(MOD,DELETE),SPACE=(TRK,1),UNIT=SYSDA //COMPO EXEC PGM=TECHCODR, // PARM='/ -A DD:PARAM' //STEPLIB DD DSN=SFTSBSJ.PROGS.LOAD,DISP=SHR // DD DSN=SFDVBDR.LOADX,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //VPF DD DSN=SFTSBSJ.RCA4CCF.VPF, // DISP=(NEW,CATLG,DELETE),VOL=SER=SFTS00, // UNIT=3390,DCB=(RECFM=VB,LRECL=1024,BLKSIZE=25604), // SPACE=(CYL,(10,5),RLSE) //SGML DD DSN=&&SGML, // DISP=(OLD,DELETE) //* //**------** //* NATIVE MODE COMPOSITION PARAMETERS * //**------** //PARAM DD * -E opInstallDir=/u/sftsbsj/oprint -E opWD=/u/sftsbsj/oprint -E opFam=ccf -E opAppli=rca4ccf -ib DD:SGML -M TPC -R 240 -ov DD:VPF /* //* //**------** //* START AFP RENDERING - DELETE AND RECREATE AFP STREAM * //**------** //PROTODEL EXEC PGM=IEFBR14 © Sefas Innovation, 2009 109 Installation Backstage under z/OS

//FLOTAFP DD DSN=SFTSBSJ.RCA4CCF.AFP, // DISP=(MOD,DELETE),SPACE=(TRK,1),UNIT=SYSDA //PROTO EXEC PGM=TECHCODR, // PARM='/ -A DD:PARAM' //STEPLIB DD DSN=SFTSBSJ.PROGS.LOAD,DISP=SHR // DD DSN=SFDVBDR.LOADX,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //VPF DD DSN=SFTSBSJ.RCA4CCF.VPF, // DISP=SHR //FLOTAFP DD DSN=SFTSBSJ.RCA4CCF.AFP, // DISP=(NEW,CATLG,DELETE),VOL=SER=SFTS00, // UNIT=3390,DCB=(RECFM=VBM,LRECL=1024,BLKSIZE=25604), // SPACE=(CYL,(10,5),RLSE) //AFPRES DD DSN=&&AFPRES, // UNIT=3390,DCB=(RECFM=VB,LRECL=1024,BLKSIZE=25604), // SPACE=(CYL,(10,5)) //AFPIND DD DSN=&&AFPIND, // UNIT=3390,DCB=(RECFM=VB,LRECL=1024,BLKSIZE=25604), // SPACE=(CYL,(2,5)) //AFPDOC DD DSN=&&AFPDOC, // UNIT=3390,DCB=(RECFM=VB,LRECL=1024,BLKSIZE=25604), // SPACE=(CYL,(10,5)) //* //**------** //* NATIVE MODE AFP PROTOCOL PARAMETERS * //**------** //PARAM DD * -E opInstallDir=/u/sftsbsj/oprint -E opWD=/u/sftsbsj/oprint -E opFam=ccf -E opAppli=rca4ccf -R 240 -iv DD:VPF • JCL ASCOPRUU: an HFS assembly, composition, and rendering JCL example: //SFTSWTJ1 JOB (999,POK),'JLV',REGION=4M,CLASS=A,MSGCLASS=H, // NOTIFY=&SYSUID //* //**------** //* FILE DECLARATION BEFORE RUNNING ENGINES * //**------** //COPY1 EXEC PGM=IEFBR14 //L1 DD PATH='/u/sftswtj/oprint/validation/letter/printer/letter.bal', // PATHOPTS=(ORDWR,OCREAT,OTRUNC), // PATHDISP=(KEEP,DELETE), // PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIROTH) //L2 DD PATH='/u/sftswtj/oprint/validation/letter/printer/letter.vpf', // PATHOPTS=(ORDWR,OCREAT,OTRUNC), // PATHDISP=(KEEP,DELETE), // PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIROTH) //L3 DD PATH='/u/sftswtj/oprint/validation/letter/printer/letter.afp', // PATHOPTS=(ORDWR,OCREAT,OTRUNC), // PATHDISP=(KEEP,DELETE), // PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIROTH) //L4 DD PATH='/u/sftswtj/oprint/validation/letter/printer/letter.res', // PATHOPTS=(ORDWR,OCREAT,OTRUNC), // PATHDISP=(DELETE,DELETE),

110 Open Print 6.3 Installation Guide Installing on z/OS Installation Backstage under z/OS

// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIROTH) //L5 DD PATH='/u/sftswtj/oprint/validation/letter/printer/letter.ind', // PATHOPTS=(ORDWR,OCREAT,OTRUNC), // PATHDISP=(DELETE,DELETE), // PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIROTH) //L6 DD PATH='/u/sftswtj/oprint/validation/letter/printer/letter.doc', // PATHOPTS=(ORDWR,OCREAT,OTRUNC), // PATHDISP=(DELETE,DELETE), // PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIROTH) //* //**------** //* START ASSEMBLY * //**------** //ASM EXEC PGM=LETTER, // PARM='/ -A DD:PARAM' //STEPLIB DD [email protected],DISP=SHR // DD DSN=SFDVBDR.LOADX,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //DATA DD PATH='/u/sftswtj/oprint/validation/letter/spool/letter.dat' //SGML DD PATH='/u/sftswtj/oprint/validation/letter/printer/letter.bal' //* //**------** //* OPENEDITION MODE ASSEMBLY PARAMETERS * //**------** //PARAM DD * -E opInstallDir=/u/sftswtj/oprint -E opWD=/u/sftswtj/oprint -E opFam=validation -E opAppli=letter -i DD:DATA -o DD:SGML //* //**------** //* START COMPOSITION * //**------** //STEP EXEC PGM=TECHCODR, // PARM='/ -A DD:PARAM' //STEPLIB DD DSN=SFTSWTJ.PROG.LOAD,DISP=SHR // DD DSN=SFDVBDR.LOADX,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //VPF DD PATH='/u/sftswtj/oprint/validation/letter/printer/letter.vpf' //SGML DD PATH='/u/sftswtj/oprint/validation/letter/printer/letter.bal' //* //**------** //* OPENEDITION MODE COMPOSITION PARAMETERS * //**------** //PARAM DD * -E opInstallDir=/u/sftswtj/oprint -E opWD=/u/sftswtj/oprint -E opFam=validation -E opAppli=letter -ib DD:SGML -M TPC -ov DD:VPF //* //**------** //* START AFP RENDERING * //**------** © Sefas Innovation, 2009 111 Installation Migration to the z/OS system

//STEP EXEC PGM=TECHCODR, //PARM='/ -A DD:PARAM' //STEPLIB DD DSN=SFTSWTJ.PROG.LOAD,DISP=SHR // DD DSN=SFDVBDR.LOADX,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //* //**------** //* OPENEDITION MODE AFP RENDERING PARAMETERS * //**------666------** //PARAM DD * -E opInstallDir=/u/sftswtj/oprint -E opWD=/u/sftswtj/oprint -E opFam=validation -E opAppli=letter -iv /u/sftswtj/oprint/validation/letter/printer/letter.vpf -od /u/sftswtj/oprint/validation/letter/printer/letter.afp -M V -dn afp -E AFP_RES_FNAME=/u/sftswtj/oprint/validation/letter/printer/letter.res -E AFP_DOC_FNAME=/u/sftswtj/oprint/validation/letter/printer/letter.doc -E AFP_IND_FNAME=/u/sftswtj/oprint/validation/letter/printer/letter.ind /*

Migration to the z/OS system

To adapt Open Print to a z/OS environment, place it on an HFS Open Edition partition; the structure is identical to a UNIX structure. Then do the following: 1. Transfer the *.tar files (linked to the common directory and the application) to the z/OS system via ftp. The ASCII files must be converted to EBCDIC; binary files must be transferred to z/OS. The following scripts are required for application migration: • Export.bat (script enabling the .tar file generation) set opInstallDir=c:\oprint set ExportDir=%TEMP%\mvs rem Please drag and drop common directory or family directory onto export.bat rem Do not use directories and files that have more than 8.3 char. FOR /F %%i IN ('echo %1') DO set Export=%%~ni

REM IMAGE CREATE WITH ASCII/EBCDIC CONVERSION EM cnvzp.exe -i in dir -o out dir -f resources list %opInstallDir%\bin\mvs\cnvzp.exe -i %1 -o %ExportDir%\%Export% -f %opInstallDir%\bin\mvs\export.res

REM TAR FILE CREATE %opInstallDir%\bin\mvs\tar.exe -C %ExportDir% -cvf %ExportDir%\ %Export%.tar%Export% rmdir /S /Q %exportDir%\%Export% @echo @echo EXPORT is ready : %exportDir%\%Export%.tar pause. • Export.res (configuration file) [CNVZIP] EXTENSION=c,h,lnk,src,sh,mac,tab,txt,spg,dat,cmd,cnd,sri,prc,sh, txt,cfg,

112 Open Print 6.3 Installation Guide Installing on z/OS Installation Optimization and tips

NAME=letter,drivers.cnf,hp.fnt,afp.fnt,xrx.fnt,pdf.fnt, [INCLUDE] EXTENSION=pcx,jpeg,tif,tiff,cha,sfp,FNT, NAME= DIRECTORY=common,chasse,config,fonthp,fontafp,letter,calc,common, program,Condition,procedure,script,call,record,printer,spool, macro,text,num,sort,tablei The following files are required for application migration: • tar.exe (compression utility in .tar format) • zip.exe (compression utility in .zip format) • cnvzp.exe (ACSII/EBCDIC conversion utility) 2. Copy the scripts and executable files in the z/OS directory of your NT workstation (for example, C:\oprint\bin\mvs). 3. Configure the export.bat and export.res files according to your tree structure. 4. Execute the export.bat commands by doing one of the following: • Type the following: Export.bat / • Create a shortcut of the export.bat command. Drag and drop the directory to be converted on the shortcut. You must convert the directory containing the application or the directory of the group containing the application, as well as the Open Print common directory. The configuration file names are case sensitive and must be in DOS format.

Optimization and tips

QSAM access versus HFS When installing engines and related applications that use resource files, consider the most efficient access method to provide the best production performance with regard to the sequential input/output operations to Open Print applications. Two options are available: • QSAM (access method used by classical z/OS batches) • HFS (access method used by the Open Edition volume setup; provides a file access interface to the POSIX under z/OS norm) The following table provides comparative performance figures between the QSAM and HFS methods, based on Sefas’s test programs.

System/ 1000 10 MB 100 MB 1 GB 10 GB 100 GB Volume bytes

Linux P90 48 R. 0 ms R. 1 ms R.17 ms R.340 ms R. 6955 ms R.67558 ms MO Memory W. 0 ms W. 1 ms W. 14 ms W. 194 ms W. 5729 ms W. 69614 ms S. 1 ms S. 0 ms S. 0 ms S. 0 ms S. 0 ms S. 0 ms

P390 z/OS R. 2 ms R. 15 ms R. 84 ms R. 1284 ms R. 10240 ms R. 107247 ms OE W. 2 ms W. 20 ms W. 70 ms W. 1242 ms W. 16234 ms W. 159262 ms HFS File S. 1 ms S. 0 ms S. 1 ms S. 1 ms S. 0 ms S. 0 ms

P390 z/OS R. 1 ms R. 5 ms R. 134 ms R. 1223 ms R. 13232 ms R. 146851 ms OE W. 1 ms W. 13 ms W. 163 ms W. 1886 ms W. 20162 ms W. 189105 ms QSAM FB80 S. 0 ms S. 55 ms S. 67 ms S. 67 ms S. 72 ms S. 114 ms 6080 OPEN DD

System/ 1000 10 MB 100 MB 1 GB 10 GB 100 GB Volume bytes

P390 z/OS R. 0 ms R. 6 ms R. 118 ms R. 1323 ms R. 13389 ms R. 153451 ms OE W. 1 ms W. 17 ms W. 179 ms W. 1802 ms W. 18907 ms W. 198024 ms QSAM FB80 S. 0 ms S. 51 ms S. 73 ms S. 67 ms S. 81 ms S. 125 ms 32000 OPEN DD

P390 z/OS R. 0 ms R. 5 ms R. 181 ms R. 1498 ms R. 13547 ms R. 148048 ms BATCH QSAM W. 1 ms W. 13 ms W. 166 ms W. 1943 ms W. 18025 ms W. 195816 ms FB80 32000 S. 0 ms S. 63 ms S. 81 ms S. 136 ms S. 96 ms S. 198 ms

P390 z/OS R. 1 ms R. 5ms R. 122 ms R. 1696 ms R. 14436 ms R. 153896 ms BATCH QSAM W. 0 ms W. 12ms W. 63 ms W. 1856 ms W. 19389 ms W. 200790 ms FB80 6080 S. 0 ms S. 65ms S. 0 ms S. 70 ms S. 98 ms S. 168 ms

Compiling and linking to z/OS

Using XPLINK to compile C files

To support enhanced z/OS functionalities such as DLL, USS, and z/OS native load modules, the generated C files must be compiled and linked in XPLINK mode. For more information about XPLINK, see IBM’s C/C++ and LINKER and Language Environment (LE) documentation.

Dataset storage Previous versions of PARTITIONED DATASET cannot be used to store resulting XPLINK load modules. Use the HFS or PDSE predefined dataset instead. The following figure shows the information panel for a PDSE dataset. LIBRARY indicates you are using the correct DATASET type for storing XPLINK load modules.

The following figure shows what you must not use.

114 Open Print 6.3 Installation Guide Installing on z/OS Compiling and linking to z/OS XPLINK Compilation with DLL

XPLINK Compilation with DLL

DLL under Open Edition Instead of linking engines such as techcodr with static libraries (.a files), use side deck files. Side decks are text files containing the name and prototypes of the functions exported by the DLL files. They are similar to .def files in Windows or .exp files in AIX. After compilation, the engine uses the DLL file associated with the side decks. The side decks have the .x extension.) A sample Python side-deck file extraction is shown below.

IMPORT DATA,'libpython2.4.dll','_Py_abstract_hack' IMPORT CODE,'libpython2.4.dll','_Py_addarc' IMPORT CODE,'libpython2.4.dll','_Py_addbit' IMPORT CODE,'libpython2.4.dll','_Py_adddfa' IMPORT CODE,'libpython2.4.dll','_Py_addfirstsets' IMPORT CODE,'libpython2.4.dll','_Py_addlabel' IMPORT CODE,'libpython2.4.dll','_Py_addstate' IMPORT CODE,'libpython2.4.dll','_Py_c_diff' IMPORT CODE,'libpython2.4.dll','_Py_c_neg' IMPORT CODE,'libpython2.4.dll','_Py_c_pow' IMPORT CODE,'libpython2.4.dll','_Py_c_prod' IMPORT CODE,'libpython2.4.dll','_Py_c_quot' IMPORT CODE,'libpython2.4.dll','_Py_c_sum' IMPORT

Note To execute an engine linked with side decks (.x), the environment variable LIBPATH must first be set to the path of the directory containing the corresponding DLL files. Paths can be separated with a “:”. The DLL files must be set to +x (execution right). If not done, Open Edition will return the message The module mymodule.dll was not found, even if LIBPATH is correctly set.

DLL under QSAM Under QSAM, the side-deck files are stored in data sets using the structure FB 3200 80. The TechPrint applications link is done pointing to them. The Storage format of side-decks is shown below.

The side-deck extraction for Python is shown below.

When launching an engine from a JCL, LOADLIB must specify the dataset containing the DLL. Storing DLL and engines in the same dataset simplifies the process. The TechCoDr engine with its three DLL files is shown below.

Files

Both DLL and side deck files are included with z/OS installation. The DLL files are loaded by the Open Print engines and TechPrint applications. The side decks compile TechPrint applications. All binaries are available in the CVS repository.

Open Edition All side deck files are archived in binary format in the CVS repository; no ASCII to EBCDIC operations are necessary. The following files are archived in \extern\lib\OS390: • libfreetype-2.2.1.dll and libfreetype-2.2.1.x.

116 Open Print 6.3 Installation Guide Installing on z/OS Compiling and linking to z/OS Using Techp

• libicuuc36.0.dll and libicuuc36.0.x. • libicui18n36.0.dll and libicui18n36.0.x. • libexpat-2.0.1.dll and libexpat-2.0.1.x. • libpython2.4.dll and libpython2.4.x.

Under QSAM Two XMIT files are available: one for the executables and the other for the side decks. The loadx.xmit file contains a PO-E library; this library contains the following: •FT221 •IXMI36IN •IXMI36UC •EXPAT201 •PYTHON24 The exp.xmit file uses text files as the side decks instead of DLL: •FT221 •IXMI36IN •IXMI36UC •EXPAT201 •PYTHON24 Upload the XMIT files in binary to QSAM in a dataset with structure FB 3200 80. Then enter the following commands: • receive inda(xmit(loadx)) • receive inda(xmit(exp)) In this example, the two xmit files had first been uploaded inside the library dataset named XMIT.

Important You must use structure FB 3200 80 to upload the XMIT files. Otherwise, the RECEIVE command used to extract XMIT on Z fails. The name of the DLL cannot be changed without regenerating the corresponding side decks. The destination dataset for the QSAM side deck must be EXP. Using another name or putting in a deeper hierarchy results in failure.

Using Techp

The Techp command supports a new option for use with side decks: -D. This option sets the name of the dataset containing the QSAM side decks for Open Print (PYTHON24 and others). Alternatively, you can use the SIDE_DECK_DATASET environment variable.

Important IBM only allows the .EXP extension for the side decks containing a dataset. The QSAM path in the screen shots below is SFDVBDR.EXP. All names are members of the dataset SFDVBDR.EXP. Using any other name makes the linker fail.

Example: $techp -f $opFam -a $opAppli -N 'SFDVBDR.LOADX(PRESK)' -D SFDVBDR.EXP

Note The ' character can be used for –N but not for -D: SFDVBDR.EXP. Using ' around SFDVBDR.EXP also does not work.

The side decks inside the .EXP file are shown below.

After executing the Techp command, two new files are created: The PRESK side deck and the PRESK XPLINK binary file. Only the binary file is important; it is shown below.

A PRESK side deck is shown below; this file is not useful for using XPLINK.

For more information about the these options, see Backstage under z/OS on page 107. The Techprint application can be used without the side deck, but the side deck must be stored somewhere for the purpose of compilation. When running the application, only the dataset LOADX is used to pick up the DLL.

TechAFP

TechAFP is stored in a different dataset than the one on which the DLL depends. Consequently, the JCL uses a steplib with two parameters:

//SFDVBDR1 JOB (999,POK),'RSBTD',REGION=0M,CLASS=A,MSGCLASS=H, // NOTIFY=SFDVBDR //********************************************************************* //STAGE0 EXEC PGM=TECHAFP, // PARM='-A DD:PARAM' //STEPLIB DD DSN=SFDVBDR.ENGINE,DISP=SHR // DD DSN=SFDVBDR.LOADX,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //PARAM DD * -E opInstallDir=/mnt/nfs/uV2R10/sfdvbdr

118 Open Print 6.3 Installation Guide Installing on z/OS Compiling and linking to z/OS QSAM TechPrint application launch

-E opWD="" -i /mnt/nfs/uV2R10/sfdvbdr/styliste.afp -o VPF Examples: The TechAFP load module is in sfdvbdr.engine:

All DLL are in sfdvbdr.loadx:

QSAM TechPrint application launch

The assembling application lies in the same dataset that contains the DLL files. Therefore, a simple LOADLIB is enough. The Python DLL contains functions, data, and initialization code. When the DLL is initialized, some external files are needed. PYTHONHOME tells the Python DLL functions where these files are located. Using external files allows altering the behavior of the engine (Python part) without recompiling anything. Set the PYTHONHOME parameter so the Python runtime environment can find all required Python material:

//SFDVBDR1 JOB (999,POK),'RSBTD',REGION=0M,CLASS=A,MSGCLASS=H, // NOTIFY=SFDVBDR //********************************************************************* //STAGE0 EXEC PGM=PRESK, // PARM='/-A DD:PARAM' //STEPLIB DD DSN=SFDVBDR.LOADX,DISP=SHR //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* //PARAM DD * -E opWD=/mnt/nfs/uV2R10/sfdvbdr -E opFam=. -E opAppli=letter -E opInstallDir=/mnt/nfs/uV2R10/sfdvbdr/Oprint -E PYTHONHOME=/mnt/nfs/uV2R10/sfdvbdr/Python24

Assembling under OpenEdition

To assemble Open Print under OpenEdition, set the LIBPATH parameter for the DLL and the PYTHONHOME parameter for the Python runtime. All DLL must have their execution rights set to +x. Example:

export LIBPATH=~/Oprint export opWD=/mnt/nfs/uV2R10/sfdvbdr export opAppli=letter export opInstallDir=/mnt/nfs/uV2R10/sfdvbdr/Oprint export PYTHONHOME=/mnt/nfs/uV2R10/sfdvbdr/Python24

./program/letter

120 Open Print 6.3 Installation Guide Additional Tasks Overview TrueType fonts in Windows Chapter 6: Additional Tasks

Overview

This chapter tells users to how to perform other tasks necessary for Open Print use.

Installing Fonts in MiddleOffice, FrontOffice, and Projector

TrueType fonts in Windows

The Open Print applications are delivered with the following font families: •Times New Roman •Courier •Arial • Wingdings To use any other fonts in MiddleOffice, FrontOffice, or Projector, you must install them in the applications. Before installing fonts in Open Print, make sure all of the TrueType fonts you want to use are installed in Windows. To do this, do the following: 1. Open the Windows Explorer directory Windows\Fonts. If the font you want to use in MiddleOffice is not installed in Windows, click File>Install New Font.

2. Select the drive you want to search, then browse the directories in the dialog box until you find the font you want to install (in this document, we use Frutiger as the example). Select the "Copy fonts to fonts folder" check box, then click OK.

3. After installing the font, double-click the font name to make sure it displays correctly.

Installing in Open Print

Open Print uses two types of fonts to display document templates and produce documents. • For display, the design interface and production interface in edit mode use TrueType Font (TTF) and PostScript Type 1 fonts. • For production, the rendering stage uses Open Print production fonts, which include protocol-specific font files, metric tables, and a font table. All fonts used by Open Print are in the fontlist.xml file located in the home subdirectory of your Open Print installation directory (for example, \home).

122 Open Print 6.3 Installation Guide Additional Tasks Installing Fonts in MiddleOffice, FrontOffice, and Projector Installing in Open Print

To install in Open Print, do the following: 1. Open fontlist.xml with a text editor and add Frutiger to the list as follows:

Frutiger Frutiger45,Frutiger45 Light 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 2. Open the directory containing the .fnt files. This typically is C:\\bin\backstage\windows\common-orig\chasse.

3. Using the text editor, enter the font information in each output protocol file (for example, hp.fnt, afp.fnt, pdf_ttf2.fnt, pos.fnt). In the example below, the font in the hp.fnt file (used for composition and PCL rendering) is Frutiger 45 Light. [it05np] family=Frutiger Substitute=Frutiger 45 Light,Frutiger45 style=normal size=5 load=no file=it05np.sfp Repeat for each size and style (Bold, Italic, Bold Italic) you want to use (Sefas’ .fnt files include font sizes 5-28). Repeat the process for the pdf_ttf2.fnt file (used for PDF rendering) and all other output files you plan to use.

Note The family= field cannot contain any spaces. The substitute= field contains aliases for this font.

4. Copy the metric file FrutigerN.cha (linked to the TrueType font) to the following location in your installation directory: \bin\backstage\\common\chasse

5. Using Techfont, convert the TTF files to bitmaps. For more information, see the Techfont Reference Manual. 6. To make sure the font has been installed correctly, start MiddleOffice, create a paragraph, and make sure the font is in the font list.

124 Open Print 6.3 Installation Guide Additional Tasks Installing Fonts in MiddleOffice, FrontOffice, and Projector Installing on the server workstation

Installing on the server workstation

To install production fonts on the server workstation, do the following: 1. Copy the font files to the server workstation. The variable can take the values aix, linux, or windows, depending on the server type. • Copy the metrics table of the character font file in \bin\backstage\\common\chasse. • Copy the bitmap files of the character font file in \bin\backstage\\common\. 2. Add the font description in the font table (*.fnt file) using the keyword substitute to specify the name of the font as displayed in the installedFontList utility. 3. Launch the font list-generation utility fnt2FontList.bat located in \tools\fontTools. •In the Input fnt file field, select the *.fnt file. •In the Output xml file field, select the fontlist.xml file from \home. 4. Click Create. Be sure the generated fontlist.xml file references the installed font. 5. Close the installedFontList utility.

Encodings

Open Print supports the following encodings: • Big5-HKSCS • ISO-8859-1 • ISO-8859-15 • ISO-8859-2 • ISO-8859-4 • ISO-8859-5 • ISO-8859-7 • ISO-8859-9 •MacSymbol • Windows-1250 (cp1250) •Windows-1251 •Windows-1252 •Windows-1253 •Windows-1254 •Windows-1257

For more information, see the Open Print Operating Manual.

Enabling Unicode To enable Unicode fonts, modify the following files: • \home\httpbean.conf Set the MIDDLEOFFICE_DOUBLEBYTE attribute to true. • \home\config\env_.prop Set the opDoubleByte attribute to 1.

Licensing Open Print

Each Open Print installation comes with a temporary license lasting three months, after which you must obtain a long-term license that determines which applications you can use and the length of your user agreement. To obtain a long-term license, contact one of the following: • For U.S. customers: Your support team. • For U.K. customers: Your sales team.

The license file

A license file is installed with your application. This file determines your user permissions based on the following criteria: • Functions •Expiration date •Number of licenses The license file is located in \common\config.

Note Change the location of the license file by setting the opLicenseDir environment variable on the engine command line. Example: -E opLicenseDir=$opInstallDir/home

The structure of the file depends on the type of license: • Static: Licenses that are restricted to specific IP addresses. These licenses let users run Open Print on machines without network access. • Floating: Licenses that are not restricted to specific IP addresses. This allows more flexibility for customers who might, for example, have numerous staff who can use Open Print, but require only five to use it at any given time.

Static licenses The license file for static licenses is oprint.lic. The structure of this file is as follows: <1.0> Elements include the following: • This element remains static for every entry in the oprint.lic file. • This element represents the function of the license, or type of permission it grants. Functions include the following: • Input file type • Output file type • Open Print application • Open Print engine • Page count • Static element representing the product; the value must be OPRINT. • <1.0> Static element; the value must be 1.0.

126 Open Print 6.3 Installation Guide Additional Tasks Licensing Open Print The license file

• The license expiration date. Possible values: •The date in DD-MMM-YYYY format. The license expires at 11:59 p.m. on this date. • permanent: This license has no expiration date. • Number of concurrent licenses, that is, the number of machines allowed to connect to the server or, when =PAGECOUNT, the maximum number of pages the customer can print per month. Possible values: • 1-999 for static licenses. • uncounted for floating licenses. • Server machine ID. This element can take the following forms: • : The Medium Access Code, or unique hardware address of the computer's network card. • : The name of the server. • : The IP address of the server. • : The ID of the computer's primary hard drive. For Windows platforms only. • : The eight-digit system planar ID. For AIX platforms only. • Static placeholder element that indicates to the engine that it must read the code that appears after the element. This code, generated by the support team, represents the information previously described and determines which features are to be enabled and for how long.

Floating licenses For floating licenses, customers receive two license files with the installation: server.lic and client.lic.

server.lic

The structure of the floating license server.lic file is similar to that of the static license oprint.lic file, but with two additional lines before the lines: • : The name of the server. • : The vendor name; it is always OPRINT. In the following sample, the customer can have a maximum of six machines connecting to its server and can generate a maximum of 10,000 pages per month using all input file types supported by Open Print.

SERVER license_server_name HOSTNAME=license_server_name 22000 VENDOR OPRINT FEATURE BACKSTAGE OPRINT 1.0 permanent 6 HOSTID=ANY SIGN= FEATURE ALLINPUTS OPRINT 1.0 permanent 6 HOSTID=ANY SIGN= FEATURE PAGECOUNT OPRINT 1.0 permanent 10000 HOSTID=ANY SIGN=

Install server.lic in \common\config on the server.

client.lic

Before using Open Print, you must install a client.lic file on the client side in \common\config. This file is included on the installation disc and tells the engine to use a license server. Example:

SERVER license_server_name ANY 22000 VENDOR OPRINT USE_SERVER In the example, 22000 represents the port.

Other files

In addition, floating licenses require the following executable files: • lmgrd(.exe): Starts the license server. • lmdown(.exe): Stops the license server. • OPRINT(.exe): Extension of lmgrd; lmgrd launches OPRINT. • opcounter(.exe): Used for page counting. These files should be located in the same directory; this can be any directory except the one containing server.lic.

Starting and stopping the license server

Floating licenses require you to run the license server. To start the license server, type the following in the engine command line:

./lmgrd -c license_file ./opcounter start -p 29400 -E opInstallDir=$opInstallDir This text can also be added to the system startup files, such as the /etc/init.tab initialization table.

Stopping the server To stop the license server, type the following in the engine command line:

./lmdown -c license_file -q ./opcounter stop This text can also be added to the system startup files, such as the /etc/init.tab initialization table.

Removing Open Print

If you need to remove Open Print from your client for any reason (for example, to upgrade to the newest version of Open Print from an older version) there are three options available in the InstallShield Wizard. •The Normal uninstall option removes only those components that were installed by the installation wizard (components checked during installation). •The Full delete option removes the entire Open Print installation directory. •The Reinstall option reinstalls the product.

128 Open Print 6.3 Installation Guide Additional Tasks Removing Open Print Starting and stopping the license server

130 Open Print 6.3 Installation Guide Directory Structure Overview Installation directory tree structure Chapter 7: Directory Structure

Overview

This chapter describes the structure of the Open Print installation directories.

Remake, Delivery, and Studio

Installation directory tree structure

The directory structure for Remake, Delivery, and Studio is shown below.

Installation directory contents

bin directory

The bin directory contains the following subdirectories: • bin\jars Contains executable Java Archive file required to run the Open Print VPF viewer, Techview (TechViewIII.jar), and the Java XML parser file (crimson.jar).

• bin\modatamanager Contains executable Python script files (xmldatamanager.py, datamanager.py, copybookdatamanager.py, __init__.py, XDatFactory.py). • bin\mvs Contains script and executable files required to transform the application to an z/OS environment. • bin\Objets and bin\Objets_VS2005 (or bin\Objets_VS2006) Contains library files. • bin\Objets contains files for use with earlier compilers (up to Visual C++ v6.0). • bin\Objets_VS2005 and bin\Objets_VS2006 contain files for use with Visual C++ 6.0 and later compilers.

common directory

The common directory contains the following subdirectories: • common\chasse Contains font, font installation, and font output configuration files. • common\config Contains the files that define the way Remake, Delivery, and Studio generate output files. • common\fontttf Contains TrueType fonts; this is where the Open Print engines search for fonts to be used with Open Print applications.

help directory

The help directory contains the following subdirectories: • Help\help_summary\images • Help\help_summary\pdf • Help\help_summary\script • Help\help_summary\wwhdata • Help\help_summary\wwhelp

132 Open Print 6.3 Installation Guide Directory Structure MiddleOffice Installation directory tree structure

optemp directory The optemp directory contains temporary files.

opd directory The opd directory contains product version information, application start, and logo image files for Open Print Delivery.

opr and ops directories

These directories contain resource files for the applications.

MiddleOffice

Installation directory tree structure

The MiddleOffice directory structure is shown below.

Installation directory contents

The files in the installed directories let you define options and parameter settings. Their organization is described below. The installation directory root contains the following files: • readme.txt Contains information about the product version (new features, naming conventions, and recommendations). • install.ini Contains configuration settings for the installation files.

bin directory

The bin directory contains the following subdirectories: • bin\backstage Contains Open Print engines and resources for Windows. • bin\rcs Contains version management tools for Windows, Linux, AIX, HP-UX, and Sun.

home directory

The home directory contains the following MiddleOffice configuration and application files: • crontab.xml Contains Automatic VPF resource importation configuration file (not enabled by default). • databaseaction.conf The database actions configuration file. • descwizard.xml Describes style sheets and transformation XSL files available for creating wizards. • fontlist.xml, fontlist_1byte.xml, fontlist_unicode.xml Contain the lists of fonts available on the server and installed on client workstations.

134 Open Print 6.3 Installation Guide Directory Structure MiddleOffice Installation directory contents

• httpbean.conf The MiddleOffice management and client/server configuration file. • httpbeancrypt The encryption key for httpbean.conf. • jaas.conf The Java Authentication and Authorization Service configuration file. • LDAP_dit.xml Directory information tree configuration file for the targeted directory/LDAP server. • LDAP_schema.xml Configuration file for the LDAP schema of the useful data type used by the applications. • MediumFormat.xml Contains properties that determine template page sizes. • middleoffice.xml Security and resource configuration file for MiddleOffice. • password.xml Password configuration file. • security.xml Security configuration and management file. • SimpleUserPolicy.xml User authorization configuration file. • Specialcharacterslist.xml Lists special characters available on the server and installed on client workstations.

home\config

The config subdirectory contains files that define how MiddleOffice output files are generated. • engine_win.prop & engine_unix.prop The engine command files for the Windows and UNIX environments. These files contain Open Print Backstage engine settings for MiddleOffice. • env_win.prop The command file for environment variables used by MiddleOffice.

MiddleOffice Within home\config, the MiddleOffice subdirectory contains MiddleOffice configuration files. • middleoffice.conf The main configuration file for the MiddleOffice server. • imagesDesktop.xml Contains a list of the images available for design desktop background. • middleoffice_action_definitions_unix.xml Defines the actions taken during the installation wizard under UNIX. • middleoffice_action_definitions_win.xml Defines the actions taken during the installation wizard under Windows. • middleoffice_engines_unix.prop Defines properties of the engines files under UNIX. • middleoffice_engines_win.prop Defines properties of the engines files under Windows.

home\database

The database subdirectory contains database configuration directory files. • home\database\installation Contains database installation files: • empty_base.moa Restores the database and repository as they were at installation. • MiddleOfficeExtends.xml Specifies database tables required by MiddleOffice. • MiddleOfficeUsersExtends.xml Specifies database tables required by MiddleOffice. • UniversalDocumentArchitectMetaModel.xml Specifies the database schema. • UniversalDocumentArchitectMetaModelOld.xml Specifies the previous database schema; useful during database updates. • UniversalDocumentArchitectMetaModelTemp.xml Temporary file used by the installation program. • macro folder • template folder Contains default page contexts for template design. • home\database\JDBC Contains JDBC installation files. • home\database\mysql Contains MySQL installation files.

home\dynhtml

The dynhtml subdirectory defines the HTML page configuration. • home\dynhtml\httpbean The httpbean subdirectory contains HTML pages relating to the connection to the server.

136 Open Print 6.3 Installation Guide Directory Structure MiddleOffice Installation directory contents

• initerror.html The identification error HTML page. • httpbeandatalogger.html The start and connection HTML page. • loginMiddleOffice.html The login HTML page. • home\dynhtml\MiddleOffice The MiddleOffice subdirectory contains configuration files and directories handling the MiddleOffice display. • css Contains style sheets for start page and administration interface HTML pages. • CVS Contains repository files. • images Contains images used by the administration interface. • js Contains Javascript files used by the administration interface. • wizard Contains HTML files and pages used in standard production wizards.

home\ftp

The ftp subdirectory contains remote application transfer files. • ftp.xml • ftp_get.xml • ftp_listing.xml • ftp_mvs.xml • rsh.xml • rsh_mvs.xml • jobcard.jcl • jobcard2.jcl • sfpax.sh

home\help

The help subdirectory contains the online help files.

home\html

The html subdirectory contains information about security management. • home\html\MiddleOffice\applet • Security management files • Images and skins used in the template design interface for customizing (tools) • Java classes used by design applet •Plug-ins • Client startup scripts and configuration files • CVS repository files • Localizations (bundle files for French and English language user interfaces)

home\lex

The lex subdirectory contains configuration files for available languages.

home\LoggedUsers

The LoggedUsers subdirectory contains information about user sessions (usernames, groups, date and time of the last connection, etc.) and user profiles created.

home\logs

The logs subdirectory contains trace files (logs). • import.log The import trace file. • repository.log The repository trace file. • databaseupdate.log The database log created when a repository is created in MiddleOffice. • systemoutlog.log The standard output log.

138 Open Print 6.3 Installation Guide Directory Structure MiddleOffice Installation directory contents

home\opWD

The opWD subdirectory is the group entry point for MiddleOffice applications. • common Contains elements and tools (customs) available to any application. • common\call Contains compiled imported tools (*.obj for Windows). • common\macro Contains composition styles used by the document engine. • common\program Contains source program for the imported tools (*.h, *.src, *.c) • default The default directory for imported applications. • default\client An example of an imported dataloader (the subdirectory name depends on the dataloader imported). • default\common Contains elements that are available to any imported application. • default\common\text Contains text elements defined in the MiddleOffice design interface (*.txt). • default\common\macro Contains composition styles created by the document engine (*.mac & *.tab).

home\repository

The repository subdirectory contains the resource version management repository.

home\ServerStuff

The ServerStuff subdirectory contains startup and stop scripts and server configuration files for Tomcat, IIS, WebSphere, and WebLogic. It includes the following scripts: • SetHttp.sh • SetHttp.bat • StartHttp.sh • StartHttp.bat • StopHttp.sh • StopHttp.bat

home\temp

The temp subdirectory contains temporary files.

install directory The Install directory contains scripts and tools that create and compress the package

product.tar.Z to be deployed during installation under UNIX.

tomcat directory

The tomcat directory contains the following elements: • Installation directory of the Tomcat application server • Scripts to start the server • Configuration files of the server

tools directory

The tools directory is the directory of Open Print application tools. It contains the following subdirectories: • tools\checkRepository Contains files that check the integrity of the repository (for example, they warn when MiddleOffice will be disconnected). • tools\dataloader Contains examples of Studio dataloader application files. • tools\DataMapper Contains MiddleOffice DataMapper application files. • tools\DynamicDialog Contains files that test the appearance of plug-in dialog boxes. • tools\fontTools Contains an executable .jar file for viewing all installed fonts. • tools\library Contains library files used in MiddleOffice. • tools\moConsole Contains scripts that execute administrative actions in batch mode.

140 Open Print 6.3 Installation Guide Directory Structure FrontOffice Installation directory tree structure

FrontOffice

Installation directory tree structure

The FrontOffice directory structure is shown below.

Installation directory contents

The files in the installed directories let you define options and parameter settings. Their organization is described in the subsequent pages. The installation directory root contains the following files: • readme.txt Contains product version information (new features, naming conventions, recommendations). • install.ini Contains the installation file configuration settings.

bin directory

home directory

The home directory contains the following FrontOffice configuration and application files: • databaseaction.conf The database actions configuration file. • descwizard.xml Describes style sheets and transformation XSLs available for creating wizards. • directory.conf The directory configuration file. • fontlist.xml, fontlist_1byte.xml, fontlist_unicode.xml Contain lists of fonts available on the server and installed on client workstations. • httpbean.conf The MiddleOffice management and client/server configuration file. • httpbeancrypt.conf The encryption key for httpbean.conf. • jaas.conf The Java Authentication and Authorization Service configuration file. • LDAP_dit.xml The directory information tree configuration file for the targeted directory/LDAP server.

142 Open Print 6.3 Installation Guide Directory Structure FrontOffice Installation directory contents

• LDAP_schema.xml The configuration file for the LDAP schema of the useful data type used by the applications. • MediumFormat.xml Contains properties that determine template page sizes. • password.xml The password configuration file. • security.xml The security configuration and management file. • SimpleUserPolicy.xml The user authorization configuration file. • Specialcharacterslist.xml Contains lists of special characters available on the server and installed on client workstations.

home\config

The config subdirectory contains files that define how FrontOffice output files are generated. • engine_win.prop and engine_unix.prop The engine command files for the Windows and UNIX environments. These files contain Open Print Backstage engine settings for FrontOffice. • env_win.prop and env_unix.prop The properties files for environment variables used by FrontOffice. Within home\config, the Projector subdirectory contains files related to the FrontOffice configuration (the Projector folder name is from an older version of FrontOffice, which used to be called Projector). • action.xml Contains instructions that link actions to be carried out by the application’s administration portal to the html pages on which they are based. • projector.conf The configuration file for the FrontOffice server. • projector _action_definitions_unix.xml Archive file for \home\config\action_definitions.xml in a UNIX environment. • projector _action_definitions_win.xml Archive file for \home\config\action_definitions.xml in a Windows environment. • projector_engines_unix.prop Contains command lines to launch Open Print engines on UNIX. • projector_engines_win.prop Contains command lines to launch Open Print engines on Windows.

home\database

The database subdirectory contains database configuration directory files. • home\database\installation The installation subdirectory contains the database installation files. • empty_base.moa Used to restore the database and repository as they were at installation. • MiddleOfficeExtends.xml and MiddleOfficeUsersExtends.xml Specify database tables required by MiddleOffice. • UniversalDocumentArchitectMetaModel.xml Contains the database schema. • UniversalDocumentArchitectMetaModelOld.xml Contains the previous database schema (useful during database updates). • UniversalDocumentArchitectMetaModelTemp.xml The temporary file used by the installation program. • macro folder • template folder Contains default page contexts for template conception and design. • home\database\JDBC Contains JDBC installation files. • home\database\mysql Contains MySQL installation files.

home\dynhtml

The dynhtml subdirectory defines the HTML page configuration. • home\dynhtml\httpbean Contains HTML pages relating to the server connection:

144 Open Print 6.3 Installation Guide Directory Structure FrontOffice Installation directory contents

• initerror.html The identification error HTML page. • httpbeandatalogger.html The start page and connection HTML page. • loginMiddleOffice.html The login HTML page. • home\dynhtml\MiddleOffice Contains the MiddleOffice display configuration files and directories: • css Contains style sheets for the start page and administration interface HTML pages. • CVS Contains repository files. • images Contains images used by the administration interface. • js Contains Javascript files used by the administration interface. • wizard Contains HTML files and pages used in standard production wizards. • home\dynhtml\Projector Contains configuration files and directories handling the FrontOffice display. • home\dynhtml\Projector_Lite Contains configuration files and elements for specific integration: • css Contains style sheets for start page and administration interface HTML pages. • CVS Contains repository files. • images Contains images used by the administration interface. • javascript Contains Javascript files used by the administration interface. • xml Contains XML files defining user interface configuration and appearance for a previous version of Projector. Not applicable to Projector 6.2. • xsl Contains XSL style sheets for FrontOffice documents. • home\dynhtml\VPF Contains HTML documents for Virtual Page Format output used by a previous version of FrontOffice. Not applicable to the current version.

home\ftp

The ftp subdirectory contains the following remote application transfer files: • ftp.xml • ftp_get.xml • ftp_listing.xml • ftp_mvs.xml • rsh.xml • rsh_mvs.xml

home\help

The help subdirectory contains the online help files.

home\html

The html subdirectory contains security management information. • home\html\MiddleOffice\applet • Security management files • Images and skins used in the template design interface for customizing (tools) • Java classes used by design applet •plug-ins • Client startup scripts and client configuration files • CVS repository files • Localizations (bundle files for French and English language user interfaces)

home\lex

The lex subdirectory contains configuration files for available languages.

home\loggedusers

The LoggedUsers subdirectory contains information about user sessions (users, groups, date and time of the last connection, etc.) and user profiles created.

home\logs

The logs subdirectory contains trace files (logs). • import.log The import trace file. • repository.log The repository trace file.

146 Open Print 6.3 Installation Guide Directory Structure FrontOffice Installation directory contents

home\opWD

The opWD subdirectory is the group entry point for FrontOffice applications. It contains the following: • common Contains elements and tools available to any application. • common\macro Contains composition styles used by the document engine. • common\template Contains template information for the pages styles used in FrontOffice. • default The default directory for imported applications. It contains the following: • default\common Contains elements that are available to any imported application. • default\common\macro Contains composition styles used by the document engine (*.mac and *.tab).

home\opWDTest

The opWDTest subdirectory contains files used when FrontOffice runs in test mode.

home\opWDProd

The opWDProd subdirectory contains files used when FrontOffice runs in production mode.

home\repository

The repository subdirectory contains the repository for resource version management.

home\ServerStuff

The ServerStuff subdirectory contains startup and stop scripts and server configuration files for Tomcat, IIS, WebSphere, and WebLogic. It contains the following scripts: • SetHttp.sh • SetHttp.bat • StartHttp.sh • StartHttp.bat • StopHttp.sh

• StopHttp.bat

home\temp

The temp subdirectory contains temporary files.

install directory

The install directory contains the scripts and tools that create and compress the product.tar.Z package to be deployed during installation under UNIX.

tomcat directory

The tomcat directory contains the following files: • Tomcat server installation directory. • Scripts that start the server. • Tomcat server configuration files.

tools directory

The tools directory is the directory of Open Print application tools. It contains the following subdirectories: • tools\checkRepository Contains files that warn when MiddleOffice will be disconnected. • tools\integration Contains scripts and APIs (.jar files) used in integration. • tools\moConsole Contains scripts that execute administration actions in batch mode.

148 Open Print 6.3 Installation Guide Directory Structure Projector Installation directory tree structure

Projector

Installation directory tree structure

The Open Print Projector directory structure is shown below.

Installation directory contents

The files in the installed directories let you define options and parameter settings. The directory organization is described below.

bin directory

The bin directory contains the following subdirectories: • bin\backstage Contains the Open Print engines and resources for Windows, UNIX, and Linux.

• bin\rcs Contains version management tools.

home directory

The home directory contains the following Projector configuration files: • httpbean.conf The main product configuration file for Projector. • httpcrypt The encryption key. • password.xml Contains a list of applications, groups, and granted rights. • schema.xml The LDAP database access configuration file. • directory.conf The LDAP database location configuration.

home\config

The config subdirectory contains search information configuration. It includes the following: • home\config\projector This subdirectory includes the following files: • projector.conf The main product configuration file for the Projector server. • home\config\projector\backstage The Open Print engine directory. • home\config\projector\menu Contains logic tree configuration files: • tree.xml & .xsl files: Logical tree configuration files • action.xml & .xsl files: Action list associated with each node of the logic tree.

150 Open Print 6.3 Installation Guide Directory Structure Projector Installation directory contents

home\database

The database subdirectory contains database configuration directory files. • home\database\installation Contains database installation files: • empty_base.moa The database archive, used to restore the database and repository as they were at installation. • MiddleOfficeExtends.xml Contains specifies database tables required by MiddleOffice. • MiddleOfficeUsersExtends.xml Contains specific database tables required by MiddleOffice. • UniversalDocumentArchitectMetaModel.xml Contains database schema. • UniversalDocumentArchitectMetaModelOld.xml Contains previous database schema; useful during database updates. • UniversalDocumentArchitectMetaModelTemp.xml Temporary file used by the installation program. • macro folder • template folder This folder contains default page contexts for template design. • home\database\JDBC Contains JDBC installation files. • home\database\MySQL Contains MySQL installation files.

home\dynhtml

The dynhtml subdirectory lets you configure HTML pages. It includes the following:

• home\dynhtml\httpbean Contains HTML pages relating to the connection to the server: • initerror.html The identification error HTML page. • httpbeandatalogger.html The start and connection HTML page. • loginMiddleOffice.html and LoginProjector.html Login HTML pages. • home\dynhtml\MiddleOffice The MiddleOffice subdirectory contains configuration files and directories handling the MiddleOffice display. • css Contains style sheets for start page and administration interface HTML pages • CVS Contains repository files. • images Contains images used by the administration interface. • js Contains Javascript files used by the administration interface. • wizard Contains HTML files and pages used in standard production wizards. • home\dynhtml\Projector Runs and displays dynamic HTML files. • home\dynhtml\Projector_Lite The Projector_Lite subdirectory contains configuration files and directories handling the Projector display. • css Contains style sheets for start page and administration interface HTML pages. • CVS Contains repository file. • images Contains images used by the administration interface. • integration_portal Contains files that define the sample FrontOffice portal’s appearance when installed. • javascript Contains Javascript files used by the administration interface. • xml Contains XML files defining the Projector UI’s configuration and appearance. • xsl Contains XSL style sheets for Projector documents. • home\dynhtml\VPF Contains HTML documents for Virtual Page Format output.

home\ftp

The ftp subdirectory contains remote application transfer files. • ftp.xml • ftp_get.xml • ftp_listing.xml • ftp_mvs.xml

152 Open Print 6.3 Installation Guide Directory Structure Projector Installation directory contents

• rsh.xml • rsh_mvs.xml

home\help

The help subdirectory contains the online help files.

home\html

home\loggedUsers

The LoggedUsers subdirectory contains information about user sessions (for example, users, groups, and date and time of the last connection) and user profiles created.

home\logs

The logs subdirectory contains trace files (logs): • systemout.log The Projector trace file.

home\opWD

The opWD subdirectory is the group entry point for Projector applications. It includes the following:

• common Contains elements and tools (customs) available to any application: • common\macro Contains composition styles used by the document engine. • common\template Contains template information for the page styles used in Projector. • default This is the default directory for imported applications. It includes the following: • default\common Contains elements that are available to any imported application. • default\common\macro Contains composition styles used by the document engine (*.mac & *.tab).

home\opWDSample

The opWDSample subdirectory contains sample files for testing.

home\opWDTest

The opWDTest subdirectory contains files used when Projector runs in test mode.

home\repository

The repository subdirectory contains the repository for resource version management (rcs*, v).

home\searchbase

The searchbase subdirectory contains files that set search parameters.

home\ServerStuff

The ServerStuff subdirectory contains startup and stop scripts and server configuration files for Tomcat, IIS, WebSphere, and WebLogic). It contains the following scripts: • SetHttp.sh • SetHttp.bat • StartHttp.sh • StartHttp.bat • StopHttp.sh • StopHttp.bat

home\temp

The temp subdirectory contains temporary files.

154 Open Print 6.3 Installation Guide Directory Structure Projector Installation directory contents

install directory

The Install directory contains the files that indicate the location of installation components.

repository directory The repository directory contains the repository for resource version management (rcs*,v).

tomcat directory

The tomcat directory contains the following elements: • Tomcat server installation directory • Scripts that start the server • Tomcat server configuration files

tools directory

The tools directory is the directory of Open Print applicative tools. It contains the following subdirectories: • tools\checkRepository Contains files that warn when Projector will be disconnected. • tools\indexer Contains indexer launcher scripts. • tools\integration Contains scripts and APIs (.jar files) used in integration. • tools\moConsole Contains scripts that execute administration actions in batch mode.

156 Open Print 6.3 Installation Guide Troubleshooting Overview Chapter 8: Troubleshooting

Overview

This chapter describes common problems and their solutions.

Common problems

The table below describes the most common problems and their solutions.

Problem Solution

The HTTP server does not start. Check paths in SetHttp.bat (Windows) or SetHttp.sh (UNIX).

User cannot connect from the Check the server name and port number. client computer.

The MiddleOffice design interface Be sure the Java Runtime Environment (JRE) is installed does not start. (from the Configuration Panel) and check the .java.policy file.

The PDF document does not Be sure no specific browser toolbar is installed on the display. station; if the PDF still does not display, reinstall Acrobat Reader.

The UNIX installation can be Transfer c:\unix\home\sefas\product.tar.z and executed only with remote post_install.sh to \home\sefas\frontoffice. Then commands (rsh/ftp) and the connect to the server and run post_install.sh. ftp failed (or cannot be used).

When installing the Python Install the ActivePython-2.4.1-247-win32-ix86.msi interpreter on Windows, it does setup. not load; the system complains that MSVCR71.dll is missing.

Problem Solution

Upon login, the error message Check the database access parameters in httpbean.conf: "HTTP BEAN processing error • In the section CURRENT DATABASE, set the reporting" appears. DBSchema parameter with the database user in lower case (if the user is declared in upper case) or in upper case (if the user is declared in lower case). • Refer to the user name specified in httpbean.conf for the jdbc.userlogindbuser. If jdbc.userlogindbuser=user, use jdbc.DB.httpbean=jdbc:db2://server:6789/ service,- ,DBSchema=USER,MaxTrans=100,MinTrans=10.

When DB2 is updated with the When a FixPak update is done on db2 database, do the new version of MiddleOffice the following: following login error message 1.Launch the following commands in the DB2 command appears: editor window: Login Error: HTTP BEAN terminate processing error connect to QUALIF reporting : bind Parser Syntax/Semantic \SQLLIB\bnd\db2schema.bnd FAILURE :Callee failure blocking all grant public sqlerror continue : terminate java.lang.IllegalStateEx 2.Change the HttpBean.conf system MO file: ception: MIDDLEOFFICE •Replace COM.ibm.db2.jdbc.net.DB2Driver with initial DatabasePool com.ibm.db2.jcc.DB2Driver allocation failure => MO •Replace 6789 with 50000, as shown in the following DATABASE NOT READY/ example: AVAILABLE: logThatGuy # IBM DB2 Update FixPak 10+ (JDBC IBM) StackTrace = jdbc.driver.JdbcOdbc=com.ibm.db2.jcc.DB2Driv java.lang.IllegalStateEx er jdbc.DB.httpbean=jdbc:db2://server:50000/ ception: MIDDLEOFFICE service, initial DatabasePool ,DBSchema=scheme_name,MaxTrans=100,MinTrans= allocation failure => MO 10,UserId=dbuser,Password=dbpassword DATABASE NOT READY/ AVAILABLE at and Database exception... sql0443n "SYSIBM.SQL.Columns"has returned an error SQLSTATE

158 Open Print 6.3 Installation Guide Index

Design applet 157 Studio 67 Symbols directory.conf 28 Installing on z/OS 104 ...... transferring files 104 .ear file 20 E...... B Encodings 125 J ...... ErrorList plug-in 48 ...... Backstage 56, 135, 143 Java installing 12 parameter configuration 30 under z/OS 107 Java Runtime Environment 44, F 56, 62, 78 Backstage, Python, and JRE 12 ...... installation directory 15, 57, bin directory 131, 134, 142, 149 Floating licenses 127 62, 80, 89, 97 Fonts Browser configuration 31 jEdit installation 121, 122 plug-ins 47 on the server workstation JPyDebug plug-in 48 C 125 ...... on Windows 121 C compiler 103 PostScript Type 1 122 verifying 10 K TrueType 121, 122 ...... verifying on MVS 11 FrontOffice Kernel verifying on UNIX 10 installing on UNIX 84 z/OS 103 verifying on Windows 11 installing on Windows 54 Class loading 20 product description 54, 84 client.lic 127 L common directory 132 ...... Configuration H LDAP browser 31 ...... full LDAP mode 26 database 7 help directory 132 installation under 25 DB2 9 home directory 134, 142, 150 server 28 Oracle 10 httpbean.conf 27 XML/LDAP mode 26 directory.conf 28 License servers 128 httpbean.conf 27 Licensing Open Print 126 Java parameters 30 I floating licenses 127 schema.xml 28 ...... static licenses 126 install directory 139, 148, 155 WebLogic Load balancing 65, 100 on UNIX 24 Installation directory on Windows 23 contents WebSphere 19 FrontOffice 141 M MiddleOffice 134 ...... Projector 149 MiddleOffice D Remake 131 installing on UNIX 73 ...... tree structure installing on Windows 41 Database configuration 7 FrontOffice 141 product description 41, 73 Dataloader MiddleOffice 133 MySQL 44, 62, 78 generation 50 Projector 149 import and use 53 Remake, Delivery, and Stu- DataMapper dio 131 N component installation 47 Installing on UNIX 73 ...... Naming conventions 5 plug-in 47, 49 FrontOffice 84 DB2 9 MiddleOffice 73 configuration 9 Projector 92 O Delivery Installing on Vista 71 ...... installing on Windows 37 Installing on Windows 33 opd directory 133 product description 37 Delivery 37 opr and ops directories 133 FrontOffice 54 oprint.lic 126 MiddleOffice 41 optemp directory 133 Projector 59 Oracle 10 Remake 34 configuration 10

© Sefas Innovation, 2009 159 P...... V...... Plug-ins Vista DataMapper 47 installing on 71 ErrorList 48 jEdit 47 JPyDebug 48 W PostScript Type 1 fonts 122 ...... Prerequisites WebLogic on UNIX 73 configuration on UNIX 24 on Windows 33 configuration on Windows 23 on z/OS 103 installing on 22 Product descriptions post-installation 24 Delivery 37 WebSphere FrontOffice 54, 84 configuration 19 MiddleOffice 41, 73 installing on 18 Projector 59, 92 Windows Remake 33 installing on 33 Studio 67 Projector installing in load balancing 65, X 100 ...... installing on UNIX 92 XML/LDAP mode 26 installing on Windows 59 product description 59, 92 Z Python ...... installation directory 14, 44, z/OS 57, 62, 79, 88, 97 Backstage under 107 installing on 104 launch scripts 108 R migration to 112 ...... optimization 113 Remake prerequisites 103 installing on Windows 34 transferring files 104 product description 33 z/OS kernel 103 Removing Open Print 128 repository directory 155

S...... schema.xml 28 server.lic 127 Static licenses 126 Studio installing on Windows 67 product description 67

T...... Tomcat 17, 43, 56, 62, 78, 139, 140, 147, 148, 154, 155 in load balancing 65, 101 tomcat directory 140, 155 tools directory 140, 148, 155 TrueType fonts 122

U...... UNIX installing on 73 Projector 92

160 Open Print 6.3 Installation Guide