SDL XPP Installation and Upgrade Guide for Unix/Linux
for use with SDL XPP 9.0 updated September 2014 Notice © SDL Group. 2007 - 2014. All rights reserved. Printed in U.S.A. SDL Group has prepared this document for use by its personnel, licensees, and customers. The information contained herein is the property of SDL Group and shall not, in whole or in part, be reproduced, translated, or converted to any electronic or machine-readable form without prior written approval from SDL Group. Printed copies are also covered by this notice and subject to any applicable confidentiality agreements. The information contained in this document does not constitute a warranty of performance. Further, SDL Group reserves the right to revise this document and to make changes from time to time in the content thereof. SDL Group assumes no liability for losses incurred as a result of out-of-date or incorrect information contained in this document.
Trademark Notice See the Trademark Notice PDF file on your SDL Group product documentation CD-ROM for trademark information.
U.S. Government Restricted Rights Legend Use, duplication or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or other similar regulations of other governmental agencies, which designate software and documentation as proprietary. Contractor or manufacturer is SDL Group, 201 Edgewater Drive, Wakefield, MA 01880-6216.
ii SDL XPP Installation and Upgrade Guide for UNIX/Linux Contents
Chapter 1 Preparing to Install XPP Prerequisites ...... 1‐1 Java ...... 1‐1 Contenta ...... 1‐1 IBM AIX Prerequisites ...... 1‐2 Disable Allow Primary Windows on Top ...... 1‐2 Selecting the CDE Window Manager ...... 1‐2 Required AIX 7.1 Packages ...... 1‐3 Sun Solaris Prerequisites ...... 1‐3 Disable Allow Primary Windows on Top ...... 1‐3 Required Red Hat Enterprise Linux Packages ...... 1‐3 Required 32‐bit .rpm Packages ...... 1‐3 Other 32‐bit Packages ...... 1‐4 Installing 32‐bit Packages ...... 1‐4 Pre‐Installation Information for XPP ...... 1‐5 Directory Structure ...... 1‐5 Temporary Files Directory ...... 1‐5 Distribution Directory ...... 1‐5 Quick Access to XPP Directories ...... 1‐6
Chapter 2 Licensing About Licensing ...... 2‐1 Multiprocessor Reporting Tool ...... 2‐2 Obtaining and Installing a License ...... 2‐3
Chapter 3 Installing XPP Introduction ...... 3‐1 Java (optional) ...... 3‐1 Installing XPP ...... 3‐2 Post‐Installation Tasks ...... 3‐4
SDL XPP Installation and Upgrade Guide for UNIX/Linux Contents iii Chapter 4 Upgrading XPP Introduction ...... 4‐1 Java (optional) ...... 4‐1 Upgrading from XPP 7.3 or earlier ...... 4‐2 Upgrading the XCS Spec ...... 4‐2 Upgrading XPP Servers ...... 4‐3 Post‐Upgrade Tasks ...... 4‐5
Chapter 5 Post-Installation Configuration Locating the Latest Configuration Files and Specs ...... 5‐1 Distribution Directories ...... 5‐1 Distribution and Destination Directories ...... 5‐3 LD_LIBRARY_PATH Variable ...... 5‐8 Configuring System Processes ...... 5‐8 Configuring a Console Log ...... 5‐9 Completing an Upgrade of XPP Server ...... 5‐9 Converting Data ...... 5‐10 PathFinder Font Size ...... 5‐10 Installing the Shakespeare CSS Demo ...... 5‐11 Configuring Print Directly to PDF ...... 5‐11 Installing 32‐bit Packages for AIX ...... 5‐11
Chapter 6 Configuring XPP Server with Unix Clients Configuring the ADVP Server with Unix Clients ...... 6‐1 The ADVP Configuration Model ...... 6‐1 Configuring the Server ...... 6‐2 Configuring Unix Clients ...... 6‐3 Configuring for an rlogin ...... 6‐4 Validating the Installation ...... 6‐5 Client Configuration Troubleshooting Tips ...... 6‐6
Chapter 7 Configuring XPP Server with Windows Clients Configuring Windows Clients of Unix/Linux XPP Server ...... 7‐1 Compiling and Loading vuem Fonts ...... 7‐1 Configure X Windows Software ...... 7‐2
iv Contents SDL XPP Installation and Upgrade Guide for UNIX/Linux Setting Up a Connection Directly to XPP ...... 7‐3 Set Up Keyboard Mapping ...... 7‐3 Configure the X Server for an International Keyboard ...... 7‐4 Updating X Servers for Cut, Copy, and Paste ...... 7‐4 Exceed ...... 7‐4 Other X Servers ...... 7‐5
Appendix A Establishing Secure Access (Optional) Assumptions and Recommendations ...... A‐1 System Default Configuration ...... A‐1 XPP Secure Installation ...... A‐2 XPP and File System Permissions ...... A‐2 XPP Application Permissions: Special Groups ...... A‐3
Appendix B Licensing Across a Firewall Changing the Port Number ...... B‐2
Appendix C Troubleshooting .RPM Package Requirements Troubleshooting XPP OS Dependencies ...... C‐1 Determining the installed packages ...... C‐1 Examine a package list ...... C‐1 Build a package list ...... C‐2 Determining missing shared libraries ...... C‐2 Locating .rpm packages containing missing shared library files . . . C‐2 Example ...... C‐3
SDL XPP Installation and Upgrade Guide for UNIX/Linux Contents v vi Contents SDL XPP Installation and Upgrade Guide for UNIX/Linux Chapter 1 Preparing to Install XPP
Prerequisites
This section describes prerequisites that you must perform on your system before installing XPP. XPP is a 32‐bit application and requires specific 32‐bit operating system packages to run. These are usually already present on 32‐bit operating system installations and few, if any, additional packages must be installed. However, on 64‐bit operating system installations, it is likely that some or all of the XPP‐required 32‐bit packages are not present. XPP can be installed and run on 64‐bit versions of Unix/Linux, but you will need to download and install the requisite 32‐bit packages as detailed below for each operating system. Refer to Required Red Hat Enterprise Linux Packages on page 1‐3 and Installing 32‐bit Packages for AIX on page 5‐11.
Java If you use Scalable Vector Graphics (SVG) images or publish using the Perl ePub module, you must install Oracle Java 1.6 or later, which you can download from java.oracle.com.
Contenta XPP 9.0 can be installed with Contenta 5.1 or 5.2.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Preparing to Install XPP 1-1 Prerequisites
IBM AIX Prerequisites The following table documents the AIX operating system version and software products you need to install. You need at least 355 MB of free disk space to install these products.
Table 1-1: IBM AIX Prerequisites
Software Product How to Load Comments
Basic Operating During initial CD When you boot a new system System installation. from the CD, the initial startup program asks various setup questions before loading the Basic Operating System.
Personal Productivity Use the Install Assistant The Install Assistant runs the first Package (includes the menu‐driven program. time you boot your system after CDE). installing the Basic Operating System. Select the heading “Install Software Applications.” SDL XPP requires Common Desktop Environment (CDE) version 1.0 or higher. Select “Personal Productivity” to install CDE to the default directory (/ usr/dt). bos.net Use smit to install the Select the main heading entire subset. “Software Installation.”
bos.compat.termcap Use smit to install the Select the main heading individual component. “Software Installation.”
Disable Allow Primary Windows on Top If the Allow Primary Windows on Top setting is enabled, XPP PathFinder appears on top of the XPP XButton menu and the Softkey menu windows during an XPP editing session. See the IBM manual AIX Getting Started for information about CDE. 1. In the CDE, select Style Manager‐Window. 2. Disable Allow Primary Windows on Top.
Selecting the CDE Window Manager When you install AIX on a new system, the default window manager is CDE. 1. To run the CDE environment after an upgrade, type this AIX command as a one time event: xinit /usr/dt/bin/dtsession 2. To change the default login environment to CDE, type: /usr/dt/bin/dtconfig –e 3. To disable the CDE environment, type: /usr/dt/bin/dtconfig –d
1-2 Preparing to Install XPP SDL XPP Installation and Upgrade Guide for UNIX/Linux Prerequisites
Required AIX 7.1 Packages This version of XPP contains open source versions of the required 32‐bit packages that can be used with AIX 7.1 or later. Once you have finished installing XPP, you can install these packages from the XPP installation. For details, refer to Installing 32‐bit Packages for AIX on page 5‐11.
Sun Solaris Prerequisites You must install, at a minimum, the “End User” configuration cluster that contains the software you need to run the Solaris software in a networked environment. It includes the Common Desktop Environment (CDE) version 1.0 or higher, a MOTIF®‐based GUI that provides a desktop graphical user interface.
Disable Allow Primary Windows on Top If the Allow Primary Windows on Top setting in the CDE is enabled, XPP XyView appears on top of the XPP XButtons menu and the Softkey menu windows during an editing session. 1. In the CDE configuration, select Style Manager‐Window. 2. Disable Allow Primary Windows on Top.
Required Red Hat Enterprise Linux Packages To run XPP on any Red Hat Enterprise Linux 5.10 or 6.5 system (32‐ or 64‐bit), you must have several specific 32‐bit Linux software packages installed. Refer to Troubleshooting XPP OS Dependencies on page C‐1 for more information on packages. From the command line, enter one of the following to learn the package contents and dependencies. • RHEL 5 yum info basepackagename.1386 • RHEL 6 yum info basepackagename.i686
Required 32-bit .rpm Packages Your initial operating system installation likely did not install some or all of these packages:
RHEL 6.5: RHEL 5.10: openmotif-2.3.3 openmotif-2.3.1 bzip2-libs-1.0.5 libXpm-3.5.5 compat-expat1-1.95.8 libgomp-4.4.7 gtk2-2.20.1
SDL XPP Installation and Upgrade Guide for UNIX/Linux Preparing to Install XPP 1-3 Prerequisites
gtk2-engines-2.18.4 libcanberra-gtk2-0.22 libcroco-0.6.2 libgomp-4.4.7 libgsf-1.14.15 librsvg2-2.26.0 libsoup-2.28.2 libXpm-3.5.10 libXxf86vm-1.1.2 PackageKit-gtk-module-0.5.8
Other 32-bit Packages The above packages have dependencies on other packages, and when installed their dependencies must be installed with the primary packages. Failure to load the dependencies will cause XPP to not work properly.
Installing 32-bit Packages Install any 32‐bit packages identified as missing above using the Linux ʺyumʺ utility. From the command line, enter one of the following to learn the package contents and dependencies. • RHEL 5 yum install basepackagename.1386 • RHEL 6 yum install basepackagename.i686 Important! On 64‐bit Linux systems, if you get errors during install indicating multi‐lib compatibility problems, uninstall the 64‐bit package, then reinstall both the 64‐bit and 32‐bit packages. (SDL encountered this problem with the libgomp and librsvg2 packages on 64‐bit RHEL 6.5.)
1-4 Preparing to Install XPP SDL XPP Installation and Upgrade Guide for UNIX/Linux Pre-Installation Information for XPP
Pre-Installation Information for XPP
This section describes the recommended directory paths for the XPP software, but you can install to any directory on any partition that is large enough to accommodate the software.
Directory Structure The following table shows the default structure of the main XPP software directories, where path represents the location you selected to install XPP. For example, the default path (the path where XPP is installed) is /usr/app/xyvision. These software directory names are case‐sensitive. Use only lower‐case letters for xz and sd_liz. Note:You can define additional data handles in any location on your system.
Table 1-2: Directory Structure
Directory Description Software Directory Location
XPP executable programs xz path/xz
Style libraries sd_liz path/sd_liz
Temporary files tmp path/tmp
CLS, GRP, JOB hierarchy jobs path/jobs/handle/alljobz
Temporary Files Directory The XPP installation program prompts you for a directory path (path prefix) that it can use to store temporary files. The installation program creates a directory /tmp under this path prefix and sets the $XYV_TMPS environment variable to point to it. When XPP successfully processes a file, it removes the associated temporary files from the directory. However, if processing fails, the associated temporary files remain in the directory. Note:XPP stores temporary graphics files in the /tmp directory. These graphic files can be very large (over 100 MB for color‐separation images), so you must specify an area on your disk with sufficient space to hold potentially large temporary files.
Distribution Directory XPP delivers some files to the distribution directories (
SDL XPP Installation and Upgrade Guide for UNIX/Linux Preparing to Install XPP 1-5 Pre-Installation Information for XPP
Quick Access to XPP Directories During the installation process, the following XPP environment variables are set.
Table 1-3: XPP Environment Variables
Prompt During Environment Variable Description Installation
$XYV_EXECS The xz directory Path for software
$XYV_STYLES The sd_liz directory Path for style files
$XYV_TMPS The tmp directory Path for temp files
After setting the environment using the following procedure, you can use these environment variables to navigate to directories when working at a command prompt. To make the XPP environment variables available to your login shell, at a command prompt type one of the following commands: • For csh: source /etc/xyvision/xyv.cshrc • For sh or ksh: ./etc/xyvision/xyv.profile For example, cd $XYV_EXECS will change your current directory to the ʺpath/xzʺ directory. Similarly, cd $XYV_STYLES will change your current directory to the path where sd_liz was installed.
1-6 Preparing to Install XPP SDL XPP Installation and Upgrade Guide for UNIX/Linux Chapter 2 Licensing
About Licensing
You must install a new license file on your server or stand‐alone system if you are doing one of the following: • Installing XPP or upgrading XPP • Installing a new XPP software option (CITI, for example) Note: You cannot open or compose a division until you install the license file. Only one active license file is permitted in the License directory. The License Manager will recognize any license file, whether it is active or not. Therefore, if you are replacing an existing license file with a new one, you should back up the old .lic file and rename it (for example, with a .bak file extension). Then install the new license file as is and run rlmreread against it. If you are installing or upgrading to XPP 9.0, you must install the license manager to use Reprise Version 10.1. Note:Releases prior to XPP 8.3 used FlexLM as the license manager. Releases of XPP 8.3 and later use the Reprise license manager. If FlexLM is required by applications other than XPP, it can coexist in the same environment as the new Reprise licensing program. However, if FlexLM is not required, it should be removed from the server. Installing the Reprise License Manager for XPP does not automatically remove the old FlexLM Manager.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Licensing 2-1 About Licensing
Note:When attempting to run XPP, you may encounter the error message “Bad server hostname in license file or port@host” and the XPP application will fail. This may be due to either an incorrect hostname in the license file, or if an sdlxysoft_LICENSE environment variable exists, an incorrectly entered hostname in this environment variable.
If you change the port number in the license file on the XPP server from its default of 5053, then you must manually make this same change in the sdlxysoft_LICENSE environment variable on each XPP client.
See Changing the Port Number on page B‐2. Note:XPP 9.0 can be installed with Contenta 5.1 or Contenta 5.2 (or greater).
Multiprocessor Reporting Tool XPP includes a multiprocessor reporting tool that records the number of CPUs available on the licensed server. This tool is an independent diagnostic tool that monitors the calls to the operating system on the machine on which you are running the tool. The reporting tool helps you monitor compliance of your use of CPUs with the system agreement you have with SDL. The reporting tool does not send a report to SDL. However, SDL may periodically request a report from you. The reporting tool runs automatically and you can also run it manually. The reporting tool runs automatically as part of the installation process for XPP. The installation program generates a message indicating that the tool has run and displays the report in the install wizard. You can also run both manually at any time by using the following procedure. Do one of the following: • In XPP PathFinder, click Tools > More Tools > cpureport.pl • At a command prompt, type $XYV_EXECS/procs/site/cpureport.pl The report is a printable ASCII log file written to $XYV_EXECS/sys/config/ cpu.log.
2-2 Licensing SDL XPP Installation and Upgrade Guide for UNIX/Linux Obtaining and Installing a License
Obtaining and Installing a License
To obtain a license file, connect to the Customer Support Web Portal (http://www.sdl.com/support/one-sdl-support.html), and then click LOG A TICKET. You will need an account to log a ticket. If you do not have an account, contact the designated representative at your site, as identified in your service agreement.
Do the following: 1. Provide your site code. Your site code is listed in the implementation package under contact information for your company. The site code also appears as your Customer Number on SDL/ XyEnterprise invoices and in existing license files. 2. Provide the host name of the designated server. To display the host name, at a command prompt, type hostname 3. Provide the host ID of the designated server. • On Solaris and AIX: type hostid • On Linux: type /sbin/ifconfig eth0 Leave out the colons (:) from the HWaddr value when sending the host ID to SDL. Once your request has been received, SDL emails the license file to you within 24 hours. When you receive the license file, save the file attachment as‐is (do not rename it) to the license directory: /opt/XyEnterprise/SDL_License
The license file name is customer_number.lic. The license manager requires license files to use the .lic file extension. Only one active license file is permitted in this folder. If you are replacing an existing license file with a new one, back up the old .lic file and rename it (possibly with a .bak file extension). Then copy the new license file into this folder. After installing or upgrading XPP: 1. Stop the license daemon if it is running: /etc/init.d/SDL_License stop (/etc/rc.d/init.d/SDL_license stop on AIX). 2. Copy the license file into the RLM installation directory (typically, /opt/XyEnterprise/SDL_License) 3. Restart the license daemon: /etc/init.d/SDL_License start (/etc/rc.d/init.d/SDL_license start on AIX)
SDL XPP Installation and Upgrade Guide for UNIX/Linux Licensing 2-3 Obtaining and Installing a License
2-4 Licensing SDL XPP Installation and Upgrade Guide for UNIX/Linux Chapter 3 Installing XPP
Introduction
Before you proceed with these instructions, review these documents: • SDL XPP Platform Requirements • SDL XPP Release Notes—This document contains late‐breaking product information that might impact the XPP installation instructions in this manual. These instructions apply to installing XPP on your Unix server for the first time. To upgrade an existing installation of XPP, see Upgrading XPP on page 4‐1. In this version of XPP, these third‐party and SDL software versions will be installed. • Perl 5.16 • XPP‐required Extra Perl Modules • Reprise License Manager 10.1
Java (optional) If you use Scalable Vector Graphics (SVG) images or publish using the Perl ePub module, you must install Oracle Java 1.6 or later, which you can download from java.oracle.com.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Installing XPP 3-1 Installing XPP
Installing XPP
The installation program displays prompts on the screen. Default values appear in square brackets. Press the Enter key to accept the default value. 1. Perform the applicable prerequisite tasks located in Preparing to Install XPP on page 1‐1. 2. Back up the system. 3. Ensure all users are logged off the system. 4. Log in as root (not as an Admin). REHL 6 does not allow rlogin as root. If you are not on the console, log in as a user and su –root 5. Set your umask to 0. 6. Create a workspace directory, then change to the workspace directory. For example: mkdir /xyenterprise/xpp/workspace cd /xyenterprise/xpp/workspace 7. Mount the CD (if it is not already mounted). If the CD reader is not on the system on which you are loading XPP, NFS‐mount the /cdrom directory. For Linux, you might have to mount the CD‐ROM device as executable: a. Type mount. b. Check whether the CD‐ROM device was mounted noexec. c. Do one of the following (where /dev/hda is the CD‐ROM device): • If the CD‐ROM device was automatically mounted noexec, type umount /dev/hda mount –t iso9660 –oro/dev/hda /media • If the CD‐ROM device was not automatically mounted, type mount –t iso9660 –oro/dev/hda /media 8. Start the XPP installation program by entering one of the following commands: • Linux, AIX: /media/bin/install.cd • Solaris: /media/cdrom0/bin/install.cd 9. Enter y to continue the installation. 10. Enter y if you have already backed up your system. Note: If you enter n, the installation program exits. 11. Enter the directory path where the CD‐ROM is mounted or accept the default value. 12. Enter the local workspace directory path or accept the default value.
3-2 Installing XPP SDL XPP Installation and Upgrade Guide for UNIX/Linux Installing XPP
13. Enter the product numbers to load, separated by commas or a hyphen (do not enter spaces) to indicate a range. You must install the XPP Software, License Manager, and Perl/Tk. If you want XPP messages in a language other than English, you must also specify the product number for that language. For example, a new XPP installation requires that you specify 1,5,6 for installation options 1, 5, and 6. To include Italian‐language error messages, you could specify 1,4‐6. Note:All purchasable options are installed with XPP, but you must have the appropriate license tokens installed to run them. If you already have Reprise License Manager 10.1 installed for another purpose, XPP will not reinstall it. Note:Perl is installed to /etc/xyvision/common/perl. 14. Press Enter to confirm your selections. You will see a message regarding the XCS spec. Because this is a new installation, this information does not pertain. 15. Press Enter to continue the installation. You will see messages regarding XYPATH, 16. Press Enter to continue. 17. Enter the path name for the location to use for the software directory, named xz. For example: /xyenterprise/xpp 18. Enter the name of the XPP server node (the ADVP node). 19. Enter the path name to the location where you want XPP to create the temporary directory /tmp. For example: /xyenterprise/xpp The prompt indicates your path specification; press Enter to accept that path. Note:XPP stores temporary graphics files in the operating system’s /tmp directory. These graphic files can be very large (over 100 MB for color‐separation images), so you must specify an area on your disk with sufficient space to hold potentially large temporary files. 20. Enter the path name for the location to use for the styles directory, named sd_liz. For example: /xyenterprise/xpp 21. Enter the path name for the first document root handle. This is the name that appears in the XPP PathFinder.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Installing XPP 3-3 Installing XPP
22. Enter yes to confirm the directory names. The installation program installs XPP. When the installation process is complete, the installation program displays the message: Installation process for this node finished without error. Once XPP is installed, the installation program installs selected third‐party products. During these installations, the program displays messages about the status of the installation. Note:If a third‐party product installation fails with a warning message, there is a problem with the system setup. Continue with the XPP installation. When the installation finishes, manually remove the previous version of that third‐party product, and then run the XPP installation again, and select only that product from the list of Product Options. When the third‐party installation is complete, the XPP installation program displays the message: Installation process finished without error. Please check logfile ktilg.date The installation program creates a log file named ktilg.date in the workspace directory (where date is the installation date in mm.dd.yy format). 23. For Red Hat Linux and IBM AIX installations, ensure that the correct versions of the XPP‐required 32‐bit operating system packages are installed. For details, refer to Required Red Hat Enterprise Linux Packages on page 1‐3, and Installing 32‐bit Packages for AIX on page 5‐11. 24. If you have a new license to install, see Obtaining and Installing a License on page 2‐3. 25. Reboot the system.
Post-Installation Tasks 1. If it exists, install the current XPP Service Pack. 2. If you are running XPP on AIX, refer to Installing 32‐bit Packages for AIX on page 5‐11 3. Configure the post‐installation configuration settings (see Post‐Installation Configuration on page 5‐1). 4. Configure the server for Unix clients (see Configuring XPP Server with Unix Clients on page 6‐1). 5. Configure the server for Windows clients (see Configuring XPP Server with Windows Clients on page 7‐1).
3-4 Installing XPP SDL XPP Installation and Upgrade Guide for UNIX/Linux Chapter 4 Upgrading XPP
Introduction
Before you proceed with these instructions, review these documents: • SDL XPP Platform Requirements • SDL XPP Release Notes—This document contains late‐breaking product information that might impact the XPP installation instructions in this manual. These instructions apply to upgrading XPP only on computers that have an existing XPP installation in place. If XPP is not already installed on your server or client computer, see Installing XPP on page 3‐1. In this version of XPP, these third‐party and SDL software versions will be installed. • Perl 5.16 • XPP Required Extra Perl Modules • Reprise License Manager 10.1 If you are upgrading XPP on a 64‐bit system, be sure to install the XPP‐ required 32‐bit packages (see Prerequisites on page 1‐1).
Java (optional) If you use Scalable Vector Graphics (SVG) images or publish using the Perl ePub module, you must install Oracle Java 1.6 or later, which you can download from java.oracle.com.
Introduction 4-1 Upgrading XPP
Upgrading from XPP 7.3 or earlier
Before you upgrade from XPP 7.3 or earlier, you must understand the XCS spec with regard to Unicode values, what effect it has on the conversion of data to 9.x, and what steps you must take to ensure that your data is properly converted. If you do not fully understand the procedures, do not proceed with the upgrade.
Do not open any XPP data, or run any conversion programs (such as cnv_tree) until you have updated the XCS spec with Unicode values.
During upgrade and planning, you may contact SDL to evaluate your current XCS spec. There is no fee for this consultation. For assistance, log a support ticket using the Customer Support Web Portal (http://www.sdl.com/support/one‐sdl‐support.html).
Upgrading the XCS Spec XPP 9.x is Unicode‐based and uses the XCS/Unicode mappings in the _xcs_default.sde spec to convert XPP Style documents and XCS numbers to Unicode. XPP delivers a new version to $XYV_STYLES/xylibrary/Lsyslib, but does not copy it into place on an upgrade because you may have customized this spec. Depending on your XPP environment and current XCS, you may need to modify your XCS or leave your existing XCS as‐is. Once data is converted, it cannot be undone nor re‐converted. Therefore, it is best to understand the impact before you convert. 1. Upgrade XPP on your XPP sever. Complete the installation program on the CD, but do not proceed to configuring your server, client, or stand‐alone system. 2. At a command prompt, type $XYV_EXECS/procs/sc/upgradexcs.pl This program compares the 9.x XCS spec against any previously known versions of XCS on your system to determine if you have made any character changes to the spec. 3. Do one of the following: • If there are no changes, you are asked to copy the new 9.x XCS spec into $XYV_STYLES/Lsyslib. • If you have made changes, the program displays a dialog box containing the differences, saves the results to a file as $XYV_TMPS/xcsdiff.txt, and provides an option to overwrite the current file with a warning that you must manually add the differences to the new XCS spec.
4-2 SDL XPP Installation and Upgrade Guide for UNIX/Linux Upgrading XPP
4. Do one of the following: • If you have only made a few changes to your XCS spec, select the option to overwrite your spec. The program makes a backup of your original XCS spec before overwriting it with the 9.x XCS spec, then asks to run genxcs. Note: Should you run the program more than once, upgradexcs.pl saves the file as $XYV_STYLES/Lsyslib/_xcs_pre90-X.sde (where the program increments X each time you run it.) • If you have made many changes, at a command prompt, type $XYV_EXECS/procs/sc/update_xcs.pl –gui The program opens a dialog box that steps you through the process of merging our proposed Unicode/XCS values into your XCS default spec. Note:This process is more complex than running upgradexcs.pl. You may prefer to receive assistance from SDL Professional Services. Upgrading XPP Servers
The installation program displays prompts on the screen. Default values appear in square brackets. Press Enter to accept the default value. 1. Perform the applicable prerequisite tasks described in Preparing to Install XPP on page 1‐1. 2. Back up the system. 3. Ensure all users are logged off the system. 4. Log in as root. 5. Set your umask to 0. 6. Create a workspace directory (unless one already exists) and then change to the workspace directory. For example: mkdir /xyenterprise/xpp/workspace cd /xyenterprise/xpp/workspace
Upgrading XPP Servers 4-3 Upgrading XPP
7. Mount the CD (if it is not already mounted). If the CD reader is not on the system on which you are loading XPP, NFS‐mount the /cdrom directory. For Linux, you might have to mount the CD‐ROM device as executable: a. Type mount. b. Check whether the CD‐ROM device was mounted noexec. c. Do one of the following (where /dev/hda is the CD‐ROM device): • If the CD‐ROM device was automatically mounted noexec, type umount /dev/hda mount –t iso9660 –oro/dev/hda /media • If the CD‐ROM device was not automatically mounted, type mount –t iso9660 –oro/dev/hda /media 8. Start the XPP installation program by entering one of the following commands: • Linux, AIX: /media/bin/install.cd • Solaris: /media/cdrom0/bin/install.cd 9. Enter y to continue the installation. 10. Enter y if you have already backed up your system. Note:If you enter n, the installation program exits. 11. Enter the directory path where the CD‐ROM is mounted or press Enter to accept the default value. 12. Enter the local workspace directory path or press Enter to accept the default value. 13. Enter u to upgrade all currently installed products and third‐party products that are new since your last XPP installation. If your installation is prior to XPP 8.3, you must install the Reprise License Manager, Version 10.1. You must update all third‐party software. If you already have Reprise License Manager 10.1 installed for another purpose, XPP will not reinstall it. If you are upgrading Perl, first make a note of any user‐defined extra modules you have installed into the site library and be prepared to reinstall these modules after installing XPP. Note: Entering u relies on files in the workspace directory that exists from a previous XPP installation. If you do not have these files, enter the specific product numbers you want XPP to install. 14. Press Enter to confirm your selections. 15. Enter y to continue.
4-4 SDL XPP Installation and Upgrade Guide for UNIX/Linux Upgrading XPP
16. Press Enter to continue the upgrade. The installation program installs XPP. When the installation process is complete, the installation program displays the message: Installation process for this node finished without error. The installation program then installs third‐party products. During these installations, the program displays messages about the status of the installation. Note:If a third‐party product installation fails with a warning message, there is a problem with the system setup. Continue with the XPP installation. When the installation finishes, manually remove the previous version of that third‐party product, and then run the XPP installation again, and select only that product from the list of Product Options. When the third‐party installation is complete, the XPP installation program displays the message: Installation process finished without error. Please check logfile ktilg.date. The installation program creates a log file named ktilg.date in the workspace directory (where date is the installation date in mm.dd.yy format). For Red Hat Linux and IBM AIX installations, ensure that the correct versions of the X/Motif, GTK2, and other required packages are installed (Refer to Required Red Hat Enterprise Linux Packages on page 1‐3 and Installing 32‐bit Packages for AIX on page 5‐11), respectively. 17. If you have a new license to install, see .. 18. If you are upgrading from XPP 7.3 or earlier, upgrade your XCS spec. See Upgrading the XCS Spec on page 4‐2. Do not proceed with configuring the server, client, or stand‐alone system before you have completed this step. Note: Send your XCS Spec to SDL for evaluation before upgrading from XPP 7.3 or earlier to 9.x. 19. Reboot the system.
Post-Upgrade Tasks 1. Specify post‐installation configuration settings (see Post‐Installation Configuration on page 5‐1). 2. Configure the XPP server with Unix clients (see Configuring XPP Server with Unix Clients on page 6‐1). 3. Configure the XPP server with Windows clients (see Configuring XPP Server with Windows Clients on page 7‐1).
Upgrading XPP Servers 4-5 Upgrading XPP
4-6 SDL XPP Installation and Upgrade Guide for UNIX/Linux Chapter 5 Post-Installation Configuration
Locating the Latest Configuration Files and Specs
Each release of XPP software includes changes to default configuration files, setup specs, and style specs. When you install XPP for the first time, the installation program copies the default files and specs directly into their destination directories and libraries so the XPP software can access them. However, if you add a patch to this newly installed version of XPP, you need to review the specs to determine what has changed and whether you need to copy over any files or specs. On an existing system, since users often modify the default configuration files and specs to reflect the needs of their site, the installation program does not overwrite these files and specs when you upgrade a system from a previous version of XPP. Instead, the installation program places the default files and specs in distribution directories, as shown in the following table. You must replace or modify the existing configuration files and specs in the destination directories if you want to take advantage of changes introduced by the most recent XPP release. Note:You do not need to copy over files for every release. Check the SDL XPP Release Notes to determine what files have been modified for this release.
Distribution Directories For upgrade installations, the XPP installation leaves the files in the distribution directories. After the upgrade installation is complete, you must modify or replace existing configuration files and specs to take advantage of changes introduced by the XPP release. With new installations, XPP moves the files to their destination directories.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Post-Installation Configuration 5-1 Locating the Latest Configuration Files and Specs
The following table defines the type of files and the distribution directory to which the Installation Program delivers them. In the where: field, pathprefix is the user‐defined path where you chose to install the XPP software directories (for example, /xyenterprise/xpp/xyvision)
Table 5-1: Distribution Directories
Type of Files Distribution Directory where:
Default $XYV_EXECS/distr/ $XYV_EXECS is the environment configuration files directory variable representing the user‐ defined path (
Default setup specs $XYV_STYLES/xylibrary/ $XYV_STYLES is the environment and style specs Llibrary variable representing the user‐ defined path (
5-2 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for UNIX/Linux Locating the Latest Configuration Files and Specs
Distribution and Destination Directories The following table lists the names of the default files, their function, the distribution directories to which they are delivered when you upgrade your XPP system, and the destination directories whose files you need to modify or replace if you want XPP to use the latest enhancements.
Table 5-2: Distribution and Destination Directories
Delivered To/Destination Files Function Directory
XYwyg Customizes attributes of the Delivered to: XyView window, including $XYV_EXECS/distr/app-defaults foreground and background colors, Line Editor window Destination on Solaris: font and position, Status /usr/openwin/lib/X11/app- window font and position, defaults X‐menu sidebar font and or your home directory. Files in your position. home directory take precedence over system files. Destination on AIX: /usr/lpp/x11/lib/X11/app- defaults or your home directory. Files in your home directory take precedence over system files. Destination on Linux: /usr/share/X11/app-defaults or your home directory. Files in your home directory take precedence over system files.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Post-Installation Configuration 5-3 Locating the Latest Configuration Files and Specs
Table 5-2: Distribution and Destination Directories
Delivered To/Destination Files Function Directory
Sdedit Style editor resources. Delivered to: $XYV_EXECS/distr/app-defaults Destination on Solaris: /usr/openwin/lib/X11/app- defaults or your home directory. Files in your home directory take precedence over system files. Destination on AIX: /usr/lpp/x11/lib/X11/app- defaults or your home directory. Files in your home directory take precedence over system files. Destination on Linux: /usr/share/X11/app-defaults or your home directory. Files in your home directory take precedence over system files.
ps_ctrl Sets screening and other Delivered to: PostScript output parameters $XYV_EXECS/distr/sys/od of TIFF contone, EPS, JPEG, PDF, SVG, CGM, PNG, BMP, Destination: and GIF images. $XYV_EXECS/sys/od
trays.ps File that you send to a Delivered to: particular printer using a $XYV_EXECS/distr/sys/od standard lpr or other print command in order to get a list Destination: of available tray names for $XYV_EXECS/sys/od setting up the tray control file.
Setup specs (for Defines the environment for Delivered to: example, sap XPP applications, including $XYV_EXECS/distr/sys-config config, bgq autoprocessing, print and config, im process queues, graphics, and Destination: config) backup utilities. $XYV_EXECS/sys/config DOF specs Device options files set Delivered to: options for queues defined in $XYV_EXECS/spool/distr-xz the background queues spec. Used to create printer profiles. Destination: $XYV_EXECS/sys/spool/bgq-xz
5-4 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for UNIX/Linux Locating the Latest Configuration Files and Specs
Table 5-2: Distribution and Destination Directories
Delivered To/Destination Files Function Directory
default rollfed Tray control files for default, Delivered to: sheetfed rollfed, and sheetfed devices. $XYV_EXECS/distr/sys/od/ps page Destination: $XYV_EXECS/sys/od/ps_page setup Contains OPI setup Delivered to: information, including the $XYV_EXECS/distr/sys/od/opi path name for graphics images. Destination: $XYV_EXECS/sys/od/opi X‐menu Allows users to access XPP Delivered to: keyboard functions without $XYV_EXECS/distr/sys-config using the keyboard. Also known as the “XButtons Destination: menu.” $XYV_EXECS/sys/config or the user’s home directory. Files in the user’s home directory take precedence over system files.
1col(.m30,.x30) Graphics that are used in XPP Delivered to: 2col(.m30,.x30) environments jobs. $XYV_EXECS/distr/graphics 3col(.m30,.x30) Destination: land(.m30,.x30) User‐definable graphics libraries land3(.m30,.x30) port(.m30,.x30)
part.tif Sample graphics files in TIFF, Delivered to: desk.ps PostScript, and EPS format. $XYV_EXECS/distr/graphics terminal.eps Destination: User‐definable graphics libraries
Style specs Default versions of specs used Delivered to: Translation by XPP that control document $XYV_STYLES/xylibrary/Llibrary tables styles, fonts, color, conversion, and composition and Destination: Keyboard maps pagination parameters. $XYV_STYLES/Llibrary Kerning pairs Font width specs for standard 35 PostScript fonts
SDL XPP Installation and Upgrade Guide for UNIX/Linux Post-Installation Configuration 5-5 Locating the Latest Configuration Files and Specs
Table 5-2: Distribution and Destination Directories
Delivered To/Destination Files Function Directory
table_1 PostScript font download Delivered to: table. $XYV_EXECS/distr/sys/od/ ps_dlf/tables Destination: $XYV_EXECS/sys/od/ps_dlf/ tables extended PostScript font encoding table Delivered to: $XYV_EXECS/distr/sys/od/ ps_dlf/encodings Destination: $XYV_EXECS/sys/od/ps_dlf/ encodings
5-6 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for UNIX/Linux Locating the Latest Configuration Files and Specs
Table 5-2: Distribution and Destination Directories
Delivered To/Destination Files Function Directory
vuem23 Vuem fonts are used to Delivered to: vuem16 support the Sdedit line editor. $XYV_EXECS/xfonts vuem10 Destination: vuem10x20- Vendor‐specified font directories iso8859- 1.pcf vuem16.pcf vuem6x13- iso8859- 1.pcf vuem9x15- iso8859- 1.pcf vuem10x20.pc f vuem18x18ja- iso8859- 1.pcf vuem6x13.pcf vuem9x15.pcf vuem12x13ja- iso8859- 1.pcf vuem18x18ja. pcf vuem9x15B- iso8859- 1.pcf vuem9x18- iso8859- 1.pcf vuem10.pcf vuem12x13ja. pcf vuem23.pcf vuem9x15B.pc f vuem9x18.pcf
SDL XPP Installation and Upgrade Guide for UNIX/Linux Post-Installation Configuration 5-7 LD_LIBRARY_PATH Variable
Table 5-2: Distribution and Destination Directories
Delivered To/Destination Files Function Directory
_sep_ps.sde Color separation specs for Delivered to: tints, patterns and gradient $XYV_STYLES/xylibrary/Lsyslib fills Destination: $XYV_STYLES/Lsyslib
_sep_level1. Lets you obtain color Delivered to: sde separation using the –sep $XYV_STYLES/xylibrary/Lsyslib level1 option for the output driver. Destination: $XYV_STYLES/Lsyslib
LD_LIBRARY_PATH Variable
XPP uses the $LD_LIBRARY_PATH ($LIBPATH on AIX) environment variable to control access to XPP program libraries. Other software products might also require modifications to this variable. Any XPP changes to this path variable specification should be added to the existing path specification (that is, do not remove or replace any existing path directory specifications with the XPP specification). Check that the .cshrc file for each user, which sets the LD_LIBRARY_PATH ($LIBPATH on AIX) variable, uses the following syntax: setenv LD_LIBRARY_PATH pathinfo:$LD_LIBRARY_PATH (setenv LD_LIBRARY_PATH pathinfo:$LIBPATH on AIX) where pathinfo is the directory path list required for XPP program libraries (for example, $XYV_EXECS/lib). Configuring System Processes
Once you have successfully installed XPP on the server, set up the following XPP and system processes needed at your site: • Background processing • Auto‐processing: create an auto‐processing directory • Graphics: create a graphics directory • Document paths: the first document path is created by the installation • Printer configuration: references the pre‐configured UNIX print queue You configure XPP processes using the XPP Administration Tool (XyAdmin). For additional information on accessing XyAdmin or configuring the system processes, see the XML Professional Publisher: Managing XPP publication.
5-8 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring a Console Log
Configuring a Console Log
You can use the system log facility to send XPP processing messages and system error messages to log files on your system. 1. Log in as root. 2. Verify that the syslog or syslogd daemon is in one of the following locations: • AIX: /etc/rc.tcpip • Solaris: /etc/rc2.d/S74syslog • Linux 5.10: /etc/init.d/syslog • Linux 6.5: /etc/init.d/rsyslog 3. Add *.err /usr/adm/xylog to the appropriate file below:
AIX: /etc/syslog.conf Solaris, Linux 5.10: /etc/syslog.conf Linux 6.5: /etc/rsyslog.conf This command names the xylog file and defines message levels. 4. Create a $XYV_EXECS/global.cshrc file (and/or global.profile when a user uses an sh/ksh shell) or edit your personal .cshrc file by entering the following command after alias commands and before comment lines: setenv XYV_SYSLOG_PRIORITY 3 This command sets an XPP environment variable and sends process messages to the syslog daemon. 5. Reboot the server. Completing an Upgrade of XPP Server
If you are upgrading from XPP 7.3 or earlier, you may want to convert your documents and style libraries for the conversion to Unicode values after you install the XPP software.
Do not open any XPP data, or run any conversion programs (such as cnv_tree) until you have updated the XCS Spec with Unicode values (see Upgrading the XCS Spec on page 5‐2).
You may convert all of your documents and styles to run on this version of XPP at this time, or you can allow XPP to convert each division and style file individually as you open it for the first time in this version of XPP. Even after XPP 7.3 there are a few other database conversions that apply, so even if you are upgrading from version XPP 8.x you may want to run cnv_tree to convert all the data up front.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Post-Installation Configuration 5-9 PathFinder Font Size
Converting Data XPP converts each division and style file when you access it through composition or the XyView. You can convert jobs or style files directly using the cnv_tree utility. Because data conversion can take a long time, SDL recommends that you convert your jobs when they are not being used, for example, at night or on a weekend. See the XML Professional Publisher: Command Line Utilities publication for more information on the cnv_tree utility. If all of your jobs are located under the same document root handle, you can run cnv_tree from the document root handle to convert all data. If your jobs are located under different paths, you have to change directories to the root handle of the job you want to convert (or to any part of the job hierarchy under the handle to convert from that point down only) before running cnv_tree. Similarly, if all your spec libraries are located under the same top‐level folder, you can run cnv_tree from that folder to convert all specs. If your spec libraries are located under different paths, you must change folder to each location of the library whose specs you want to convert before running cnv_tree. To convert data and specs: 1. Change to the location of the job or library whose specs you want to convert. If you are • at the document root handle or top‐level spec library, cnv_tree converts all the data below. • in a specific job or library, cnv_tree converts all the divisions of that particular job, or all the specs in that library. • in a division, cnv_tree converts only that division. 2. Enter the following command at the command line prompt, cnv_tree This utility converts your divisions and local specs to run on XPP. Note: For more information on cnv_tree, run `xyhelp cnv_tree` in a terminal window. PathFinder Font Size
You can change the font size of the PathFinder window by creating a $HOME/.gtkrc-2.0 file entry as follows:
gtk-font-name = ”Sans Regular 14”
To make this change system‐wide, add the line above to /etc/gtk-2.0/gtkrc.
5-10 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for UNIX/Linux Installing the Shakespeare CSS Demo
Installing the Shakespeare CSS Demo
In addition to the existing Shakespeare demo, which is based on the Item Format spec, you can also install the same demo based on CSS. From the command line, enter $XYV_EXECS/procs/sc/samples.pl When it completes, an XPP ʺjobʺ will be installed to: CLS_xyvision/GRP_comp/JOB_shakesp_css on the first document handle that contains CLS_xyvision/GRP_comp. Configuring Print Directly to PDF
Before you can use the Print directly to PDF option from XPP, you must convert the encoding files for PostScript Type 1 fonts, and also ensure that they have Adobe Font Metrics (.afm) font descriptions. Note This is a separately licensed feature. From the terminal window, enter $XYV_EXECS/procs/sc/pdfsetup.pl Installing 32-bit Packages for AIX
IBM AIX 7.1 is a 64‐bit OS; therefore, you need to install 32‐bit packages to run XPP. 1. From a terminal window, enter source /etc/xyvision/xyv.cshrc 2. From the $XYV_EXECS/distr/AIX directory, enter INSTALL 3. Reboot your system.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Post-Installation Configuration 5-11 Installing 32-bit Packages for AIX
5-12 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for UNIX/Linux Chapter 6 Configuring XPP Server with Unix Clients
Configuring the ADVP Server with Unix Clients
The Advanced Production (ADVP) model lets you install XPP software on one server and use the Network File Service (NFS) facility to let multiple clients access the data from the server. You establish the ADVP model the first time you install publishing software on your systems.
The ADVP Configuration Model XPP is deployed in a networked environment through use of the ADVP Configuration model. The configuration lets multiple clients in a networked environment access third‐party software and XPP program files and data on a central server. To implement the ADVP model, you install XPP and included third‐party software on the server and export the appropriate file systems. You then NFS mount those file systems on your client machines. While no software is installed on your clients, they can run the XPP application and access all relevant directories and files. The ADVP server • runs operating system software. • runs XPP publishing software. • runs third‐party software products. • contains all software license files. • performs all background processing tasks.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring XPP Server with Unix Clients 6-1 Configuring the ADVP Server with Unix Clients
The ADVP client • can be an operating system server or a workstation. • mounts all directories containing XPP software, as well as third‐party software from the ADVP server. This includes /xyenterprise/xpp /opt/Xyenterprise/SDL_License (optional)
Then on each client ln -s /xyenterprise/xpp/xz/etcxyvision /etc/xyvision • does not require a license file; it uses the server’s license via the variable definition: sdlxysoft_LICENSE=5053@advpserver If the Unix client is configured to mount the license directory (/opt/Xyenterprise/SDL_License), then the sdlxysoft_LICENSE environment variable is not needed. • does not perform background processing task.
Configuring the Server To establish a configuration using the ADVP model, you export the appropriate file systems on the server and NFS‐mount those file systems on the clients. 1. Install, configure, and verify XPP and third‐party software. Install XPP so that the clientʹs NFS‐mounted XPP paths match the server’s XPP paths. This includes job trees and graphics libraries, etc. 2. Edit the appropriate file to specify directories for the XPP software and data (executable programs, pathing information, jobs, graphics, and fonts) and enable use by Unix clients: • AIX, Linux: /etc/exports file • Solaris: /etc/dfs/dfstab file For example, on a Solaris server, these directories would hold the XPP software and PostScript fonts: • /xyenterprise/xpp ‐ XPP application and XPP executable programs • /xyenterprise/xpp/xz/etcxyvision ‐ Software access and pathing information • /xyenterprise/xpp/xz/psres/fonts ‐ Display PostScript fonts The following example directories would hold XPP data: • /xyenterprise/xpp/jobs • /xyenterprise/xpp/graphics • /xyenterprise/xpp/sd_liz
6-2 Configuring XPP Server with Unix Clients SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring the ADVP Server with Unix Clients
For example, the edited Solaris /etc/dfs/dfstab file would be similar to the following: share -F -nfs -o anon=0 /xyenterprise/xpp share -F -nfs -o anon=0 /opt/XyEnterprise/SDL_License You only need to export the top‐level path. When the client mounts it, it will contain all the subdirectories. The client will then have to manually establish the /etc/xyvision link: ln -s /xyenterprise/xpp/xz/etcxyvision /etc/xyvision When a component of XPP data is stored on another disk or another disk partition, you must exercise caution. For example, assume that the graphics path is /xyenterprise/xpp/graphics and you mount a second drive to that same mount point, the /etc/dfs/dfstab would need to export /xyenterprise/xpp/graphics separate from the /xyenterprise/xpp export, and the Solaris clients would have to mount /xyenterprise/xpp and then /xyenterprise/xpp/graphics in their /etc/vfstab files. Check your operating system documentation for additional information.
Configuring Unix Clients The ADVP model lets you install XPP software on one server and use the NFS facility to let multiple Unix clients access the XPP software and data from that server. Perform this procedure on each Unix client. 1. Install XPP on the server (see Installing XPP on page 3‐1). 2. Configure XPP on the Unix server as documented in Post‐Installation Configuration on page 5‐1. 3. Give the client access to his/her homedir. 4. Copy the files from the Unix server directory: • Solaris: /usr/openwin/lib/X11/app-defaults • Linux: /usr/share/X11/app-defaults • AIX: /usr/lpp/X11/lib/X11/app-defaults 5. Edit the appropriate file to nfs‐mount the XPP Server directories that contain the XPP software and data: • Solaris: /etc/vfstab • Linux: /etc/fstab • AIX: /etc/filesystems Example: pubserve:/xyenterprise/xpp /xyenterprise/xpp nfs bg,soft 0 0 6. Create the mount‐point directory using same path as the XPP server. For example, mkdir /xyenterprise/xpp
SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring XPP Server with Unix Clients 6-3 Configuring the ADVP Server with Unix Clients
7. Mount all file systems: mount -a 8. Create a soft link to the
Configuring for an rlogin Perform this procedure on each Unix workstation that will use rlogin to access XPP on a Unix server. For additional information about accessing and using XPP, see the XML Professional Publisher: User Guide publication. 1. Log in to the workstation. You may find it necessary to run an xhost + command to allow for remote server connections. 2. At a command prompt, type xset -q The system responds with system information including a list of current active font path folders/directories. 3. Copy the vuem fonts (.bdf for Windows)or(.pcf for Unix)from $XYV_EXECS/xfonts to one of the listed directories on the workstation. 4. Enter the font names in the font.dir file located in the font directory. 5. At a command prompt, type rlogin XPP_server_name -l login_name 6. Do one of the following to set the display to the IP address or name of your workstation: • setenv DISPLAY IPaddress:0 • setenv DISPLAY name:0
6-4 Configuring XPP Server with Unix Clients SDL XPP Installation and Upgrade Guide for UNIX/Linux Validating the Installation
7. Do one of the following to initialize the environment for the publishing software: • csh shell: source /etc/xyvision/xyv.cshrc • sh/ksh shell: ./etc/xyvision/xyv.profile 8. To access the publishing software, type xzplorer The workstation displays XPP PathFinder. Validating the Installation
After installing and setting up XPP, check that you can run the publishing software. 1. At a command prompt, type one of the following: • csh, type source /etc/xyvision/xyv.cshrc • sh/ksh, type ./etc/xyvision/xyv.profile This sets the environment for the user. 2. Type xzplorer. XPP displays the XPP PathFinder window. Note: To access XPP PathFinder from a remote Unix login, see Configuring for an rlogin on page 6‐4. 3. Edit and store a division. 4. Print a division. 5. Edit and store a style spec. 6. Print a style spec. 7. Type xyadmin. XPP displays the Administrative Tools window. 8. Open and save a spec.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring XPP Server with Unix Clients 6-5 Client Configuration Troubleshooting Tips
Client Configuration Troubleshooting Tips
This table lists some common problems and solutions with configuring clients.
Table 6-1: Client Configuration Troubleshooting Tips
Problem Potential Solution
If you upgraded XPP and find XPP does not overwrite this variable so you must correct that the font displays poorly, the it with one of these two actions: system may have XAPPLRESDIR •Remove this variable and restart your Unix set as an environment variable. connection, allowing XPP to read the newly installed When this variable is set, XPP XYwyg file. reads the XYwyg file from the •Copy the new XYwyg file to the XAPPLRESDIR wrong location. location. Make certain that the Anti‐aliasing and Bitmap options in the file are set to true.
Your X session window starts to Check the network permissions. The server needs to be open, flashes on the screen, then added to the rhosts file, or otherwise identified in the closes. network. Do not use alias names in the command lines, but use the actual IP address instead. Check with your system administrator.
You get an error message that the Check that you compiled and loaded the fonts in the X default font could not be opened. software font database (see Compiling and Loading vuem Fonts on page 7‐1).
You attempt to open a division This problem is generally related to display memory. If and XPP displays the following you have a number of windows open, close a few of them message: and try to open the division again. If your work requires “Cannot display page save that you have a number of windows open concurrently, changes and exit” or using the an alternative is to set lower values for the page height mouse to expand the XyView and page width resources in the XYwyg file. You may window causes XPP to freeze. need to experiment with a combination of the two approaches described above or consider adding display memory to your system.
If you open XPP PathFinder, Port 2994, used by the bgquer, is already in use. You can select a DIV, and try to print, the change the port number in Unix by modifying the /etc/ print interface flashes and hangs services file. XPP PathFinder. If the line is not already there, add the following: xxx/tcp bgquer # XPP Background processing port where xxx is another port number (not 2994).
If you are using the Gnome This problem occurs because the Motif Primary Desktop on a Linux console or Application Modal feature is not implemented in the laptop, with a division open and Linux Gnome window manager. If you switch to Motif a dialog window such as the Line Window Manager this problem will not occur. Editor active, the mouse will not click in the Softkey Menu.
After installing XPP, you are Check permissions. You may need to turn off readonly in unable to open a division. Properties.
6-6 Configuring XPP Server with Unix Clients SDL XPP Installation and Upgrade Guide for UNIX/Linux Chapter 7 Configuring XPP Server with Windows Clients
Configuring Windows Clients of Unix/Linux XPP Server
Running XPP software on a Unix server from a Windows client requires X emulation software. There are many X emulation software packages; you should rely on technical support for installing, configuring, and running your X emulation software from your vendor. SDL has verified that OpenText Exceed 14.0 (or later) works with XPP. This chapter uses the Exceed product in its descriptions and examples. The exact steps may vary if you are running a newer version of Exceed. If you are running MKS XServer or XVision as your XWindows Server, see the SDL XPP Installation and Upgrade Guide for Windows publication for configuration information.
Compiling and Loading vuem Fonts The vuem fonts display the reverse video characters used for the macro and tag syntax and provide the characters you see in XPP windows and specs. For XPP windows and specs to display correctly, load and configure the following fonts on the client. 1. Copy the vuem fonts from $XYV_EXECS/xfonts using binary format from the server to a temporary directory on the client, for example, C:\temp. 2. Click Start > Programs > Open Text Exceed 14 x64 > Exceed Tools > Xconfig 3. Do one of the following: • In classic mode, click Font in the right pane. • In category view, click Font Management icon/text in the right pane. 4. Click Edit in the Font Database section of the Font tab. 5. Select the font directory to which you want to add the new font. SDL recommends ...exceed\font\misc\.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring XPP Server with Windows Clients 7-1 Configuring Windows Clients of Unix/Linux XPP Server
6. Click Add XFonts at the bottom of the Font Database dialog box. 7. Click Browse. 8. Navigate to the directory to which you copied the vuem fonts. 9. Select the fonts you want to add from the list box. 10. Click Advanced in the Add XFonts dialog box. 11. Check the appropriate font compiler options: • Minimize Memory Fragmentation ‐ Use this option with extremely large fonts. • Inhibit Ink Metrics for Terminal Fonts ‐ Use this option with extremely large fonts. • Do NOT Try to Create Terminal Fonts ‐ Not recommended. • Zero Attribute Fields ‐ May speed up certain protocol requests. 12. Click OK in the Font Compiler Options dialog box. 13. Click Add in the Add XFonts dialog box. 14. Click OK in the Font Compiling window. 15. Click OK. 16. Click Close in the Add Fonts dialog box. 17. Click OK in the Font Database dialog box. 18. Click Validate and Apply Changes in the left pane under Common Actions. 19. Continue with Configure X Windows Software on page 7‐2.
Configure X Windows Software SDL does not require any particular X Windows software package. This section provides instructions for setting up OpenText Exceed 14.0 software. 1. Click Start > Programs > Open Text Exceed 14 x64 > Exceed Tools > Xconfig 2. Click Screen Definition. 3. Click Multiple in the Window Mode section. Multiple mode restricts your access to the application specified in the Exceed connection only. (However, you can set up direct connections to other applications and place shortcuts to these connections on the desktop.) 4. Click Validate and Apply Changes in the left pane under Common Actions. 5. Click Communication in the Exceed Xconfig window. 6. Confirm that Passive is the value in the Mode field. 7. Click Validate and Apply Changes in the left pane under Common Actions.
7-2 Configuring XPP Server with Windows Clients SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring Windows Clients of Unix/Linux XPP Server
Setting Up a Connection Directly to XPP 1. Click Start > Programs > Open Text Exceed 14 x64 > Exceed Tools > Xconfig 2. Enter the following information in the Connection section: • Host: Enter the name of the XPP server. • User ID: Enter the name of the user logging in to Unix to run XPP. • Password: Enter that user’s password. 3. In the Command text box, enter the command sequence to start XPP. Separate the commands with semicolons. Note:Be sure you have added source /etc/xyvision/xyv.cshrc to the .cshrc file (for C shell users) or ./etc/xyvision/xyv.profile (for Bourne/Korn shell users) in the user’s home directory. In this example, /xyenterprise/xpp/xz/bin/xzplorer is the default location for starting XPP PathFinder. On your system, you would replace this path with the path you used to install XPP: (setenv DISPLAY @D; /xyenterprise/xpp/xz/bin/xzplorer) >& /dev/ null 4. Click File > Save As to name the startup session. 5. If desired, create a desktop shortcut to XPP on the Unix server. 6. Close the Xstart Client Startup Application dialog box.
Set Up Keyboard Mapping XPP softkeys are affected by the X emulation package you use. You can use the number pad and function keys in XPP with Exceed software. However, since each X emulation software product may be slightly different, and different revisions of the software may exhibit different behavior, you need to check whether other products also have this same capability. The following procedure describes how to set up mapping in Exceed. 1. Click Start > Programs > Open Text Exceed 14 x64 > Exceed Tools > Xconfig 2. Click Keyboard (classic view) or Mouse, Keyboard, and Other Input Devices (category view). 3. In the Primary menu, click the U.S. keyboard, us.kbf. 4. Check Allow Clients to Modify Keyboard Mapping. 5. Select Right to Windows, Left to X in the Alt Key field. 6. Click Edit below the Primary field. 7. Click Edit > Settings. 8. Uncheck Local NumLock.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring XPP Server with Windows Clients 7-3 Configuring Windows Clients of Unix/Linux XPP Server
9. Check NumLock in the Unlatch section. 10. Click OK. 11. Click File > Save As in the us.kbf.XKeys window. 12. Verify the information in the Save in, Filename, and File Type fields, then click Save. 13. Close the us.kbf.XKeys window. 14. Click Validate and Apply Changes in the left pane under Common Actions. 15. Close the Xconfig window. Note:The NumLock light on your keyboard may be lit even though you disabled local NumLock. With local NumLock disabled, XPP softkeys behave as expected.
Configure the X Server for an International Keyboard If you are using an X Server such as Exceed to work with XPP applications, and you have a foreign (non‐US) keyboard set as the default on the Windows client, you must also configure the active keyboard in the X server. This procedure describes how to configure the international keyboard in Exceed. 1. Click Start > Programs > Open Text Exceed 14 x64 > Exceed Tools > Xconfig 2. Click Keyboard (classic view) or Mouse, Keyboard, and Other Input Devices (category view). 3. In the Primary menu, select the appropriate language. 4. Repeat step 3 for the Alternate menu to set a different language for the Alternate keyboard. 5. Click Validate and Apply Changes in the left pane under Common Actions.
Updating X Servers for Cut, Copy, and Paste The following changes must be made to the X servers on each Windows client to support cut, copy, and paste operations using the Windows clipboard within XPP and between XPP and other software applications.
Exceed 1. In Configuration > Copy, Paste, and X selection, set the following: • X Selection Associated with Edit Operations: CLIPBOARD • Check Auto Copy X selection. • Uncheck Copy on Focus Loss. • Check Auto Paste to X Selection. • Grab Clipboard Retry Time (ms): 200 • Auto Paste Delay Time (ms): 200
7-4 Configuring XPP Server with Windows Clients SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring Windows Clients of Unix/Linux XPP Server
2. In Security, Access Control and System Administration, on the System Administration Tab, uncheck X Server Copy/Paste. 3. Click Validate and Apply Changes. 4. Restart the X server.
Other X Servers SDL XPP officially supports Exceed and the MKS X/Server for the Windows implementation of XPP. For other X servers, the configuration must be set to use the clipboard rather than the standard X primary selection. Also, any settings associated with automatically copying the X/selection to the clipboard or UTF‐8 encoding should be enabled. For specific instructions, refer to the X server documentation.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Configuring XPP Server with Windows Clients 7-5 Configuring Windows Clients of Unix/Linux XPP Server
7-6 Configuring XPP Server with Windows Clients SDL XPP Installation and Upgrade Guide for UNIX/Linux Appendix A Establishing Secure Access (Optional)
This appendix assumes system administrator knowledge. It describes how to set up the necessary groups and permissions for establishing secure access to XPP. Establishing secure access to XPP is optional. Assumptions and Recommendations
The information in this appendix assumes the following about your environment setup: • You are installing XPP in an existing computing environment with established users and groups used for other applications. • Your site wants only authorized individuals to use and access XPP software and data. • Your site does not want multiple user logins for different applications‐ any user who logs in should be able to run all the applications the user is authorized to run. • The physical security precautions, in terms of equipment, are in place.
System Default Configuration Before installing XPP, ensure that XPP applications and data servers are physically secure and protected against unauthorized root access. Restrict root login as desired. Modify system default controls for logins, accounts, etc., to reflect the desired level of security for your site. Restrict remote access as desired by modifying network files related to transports and port numbers.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Establishing Secure Access (Optional) A-1 XPP Secure Installation
XPP Secure Installation
You can accomplish a secure installation by establishing the following: • Appropriate Unix file system owner/group/others permissions. • Appropriate XPP application permissions. You can implement either or both of these as desired to achieve your security goals and regulations.
XPP and File System Permissions To implement a file system‐secure installation, install XPP as follows: 1. Log in as root. 2. Create a group for XPP users. 3. Do one of the following: • Add all XPP users and the root user to the XPP user group in the /etc/ group file. • Change the primary group ID in /etc/passwd for each XPP user. If you have a user account that SDL Technical Support uses for remote diagnostics, include this user account in the group, also. 4. At a command prompt, execute the new group to change root’s active group ID by typing newgrp name of group 5. Set umask to 007. 6. Modify the .cshrc file for all XPP C shell users and the .profile file for all Bourne/Korn shell users: a. Set the umask for each user to the appropriate mask, usually 002. The 002 mask makes the XPP files and directories read‐only accessible to everyone; owner and users in the group have full access. b. Set all necessary XPP environment variables for each user by adding the following line to the appropriate file: • For a csh shell user, add: source /etc/xyvision/xyv.cshrc • For an sh/ksh shell user, add: . /etc/xyvision/xyv.profile 7. Install or upgrade XPP. If possible, install XPP applications into a separate, non‐OS file system and keep XPP data (jobs, style libraries, and graphics) in a separate, non‐OS file system.
A-2 Establishing Secure Access (Optional) SDL XPP Installation and Upgrade Guide for UNIX/Linux XPP Application Permissions: Special Groups
XPP Application Permissions: Special Groups
XPP application permissions are set up through the application groups (xyadmin, xystyle, xyjstyle, and xyperuse). Although you create these groups and add users to them on the Unix server, their permissions are defined in the XPP application itself. The xyadmin, xystyle, xyjstyle, and xyperuse groups control access via XPP applications only (xzplorer, sdedit, and xyview). Determine the users who should belong in each of the groups, then create the groups and add the appropriate users. The creation of a group results in a denial of the permissions as defined by the group, for any user who is not included as a member. For example, if you create the xyadmin group but do not add any users to it, no one can execute the XPP administrative tools. However, if you do not create a group, all users will have access. For example, if you do not create the xyadmin group, all XPP users can execute the administrative tools. • xyadmin Group members can execute the XPP administrative tools and modify XPP style files at either the system library or the local job level. If you establish this Unix group, it is advisable to add your Unix system administrator to this group. • xystyle Group members can modify XPP style files at either the system library or local job level. • xyjstyle Group members can modify style files at the local job level only. • xyperuse Group members have read‐only permissions for designated divisions. This group is applicable only if your site has purchased the Peruse option.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Establishing Secure Access (Optional) A-3 XPP Application Permissions: Special Groups
A-4 Establishing Secure Access (Optional) SDL XPP Installation and Upgrade Guide for UNIX/Linux Appendix B Licensing Across a Firewall
This appendix explains how to change the port number in the license file on the XPP server.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Licensing Across a Firewall B-1 Changing the Port Number
Changing the Port Number
If you want to serve licenses across a firewall, both license servers—the Reprise License Manager (RLM) and the sdlxysoft server (ISV)—need known port numbers for your firewall to pass requests on these ports. The RLM server is always set at two known port numbers (5053 and 5054), the first of which you specify in the license file on the SERVER or HOST line. The RLM server also starts up the SDL sdlxysoft server with a dynamic port number, which is not known before startup time. To assign a fixed port number to the sdlxysoft server 1. Change to the RLM license directory. /opt/XyEnterprise/SDL_License 2. Edit the license file xxxxx.lic as follows:. Change the ISV line as follows: ISV sdlxysoft port=#### Important! Do not change any other lines or the license may become invalidated. 3. Change the firewall settings to turn on 5053/5054/XXXX (where XXXX is the port # you chose). 4. Open the new port. Instruct your firewall to allow connections to both the port number on the SERVER or HOST line (for the RLM server) and to the port number on any ISV line (for the SDL server). 5. Restart the license manager. From the command line, enter ./rlm.sh restart.
B-2 Licensing Across a Firewall SDL XPP Installation and Upgrade Guide for UNIX/Linux Appendix C Troubleshooting .RPM Package Requirements
Troubleshooting XPP OS Dependencies
This appendix explains how to troubleshoot .rpm package requirements.
Determining the installed packages As an example, the OpenMotif package contains the Motif runtime libraries and mwm window manager software that you need to run XPP, as well as a MOTIF®‐based GUI that provides a desktop graphical user interface. To determine if the package is already installed, open a console window and run this command: rpm -qa | grep openmotif If the output from this command does not find instances of the OpenMotif package, the required package was not installed. On 64‐bit RHEL5, you should see two instances of a package with the same name, indicating 64‐ and 32‐bit versions, respectively.
Examine a package list In Applications on your desktop, when you click the Add/Remove Software ‐> Package Manager > List tab, the 32‐bit packages have ʺ.i386ʺ extensions and the 64‐bit packages have ʺ.x86_64ʺ extensions (on RHEL5, the rpm utility, when run from command line, does not include these extensions.) On 64‐bit RHEL6, the 32‐bit packages have ʺ.i686ʺ extensions and the 64‐bit packages have ʺ.x86_64ʺ extensions. Note: Repeat the XPP‐required query for each of the above packages, substituting the base package name (ʺbzip2‐libsʺ, for example) in place of the ʺopenmotifʺ string.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Troubleshooting .RPM Package Requirements C-1 Troubleshooting XPP OS Dependencies
Build a package list Alternatively, you can build a list of all installed 32‐bit packages and compare your listing to the required packages. RHEL6: rpm -qa | sort | grep i686 > 32-bit_rpms_linux6.txt RHEL5: rpm -qa | sort > all_rpms_linux5.txt rpm -qa | sort -u > 64-bit_rpms_linux5.txt diff all_rpms_linux5.txt 64-bit_rpms_linux5.txt > 32 bit_rpms_linux5.txt Note:The rpm query output on RHEL5 does not include the .i386 or .x86_64 filename extensions. If you have 32‐bit and 64‐bit versions of a package installed, it returns two identical names, hence the need to generate two files and then diff them—the duplicates are the 32‐bit packages.
Determining missing shared libraries You can run `ldd` and grep for ʺnot foundʺ on the following XPP executables to determine any missing shared library files: cd $XYV_EXECS ldd ./sys/gr/convert/sdi/sdi_cgm_ps | grep "not found" ldd ./sys/gr/convert/tgc/pdffly | grep "not found" ldd ./sys/gr/convert/ImageMagick/bin/convert | grep "not found" ldd ./bin/xyadmin | grep "not found" ldd ./bin/xzplorer | grep "not found" ldd ./bin/xyview | grep "not found" ldd ./bin/conshell | grep "not found" ldd ./bin/xyarchive | grep "not found"
Locating .rpm packages containing missing shared library files
The rpm utility can only list the contents of installed packages on your system. It requires artful Internet searching to locate rpm packages that are not installed, but may contain the missing shared library files.
C-2 Troubleshooting .RPM Package Requirements SDL XPP Installation and Upgrade Guide for UNIX/Linux Troubleshooting XPP OS Dependencies
Example Suppose the rpm utility returned "/usr/lib/libXm.so.4 - not found". 1. List similar files that exist on your system. For example, you may discover /usr/lib/libXm.so.3. 2. Generate a file listing all installed packages and their file contents. Run rpm -qail > /tmp/my_packages.txt 3. Edit my_packages.txt and then search for the libXm.so.3 shared library file and note the package that contains it: openmotif22. This gives you a starting point—you can then peruse your repository for similarly‐named packages. 4. Search for your file, and then scroll to find the package for your version of Linux. 5. Connect to your RHEL repository, and then install the necessary .rpm. Note: A helpful resource for finding packages is http://www.rpmfind.net.
SDL XPP Installation and Upgrade Guide for UNIX/Linux Troubleshooting .RPM Package Requirements C-3 Troubleshooting XPP OS Dependencies
C-4 Troubleshooting .RPM Package Requirements SDL XPP Installation and Upgrade Guide for UNIX/Linux
SDL Group 201 Edgewater Drive Wakefield, MA 01880‐6216 www.sdl.com/support