SDL XPP Installation and Upgrade Guide for Windows
for use with SDL XPP 9.0 updated September 2014 Notice © SDL Group 2010-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 Windows Contents
Chapter 1 Preparing to Install XPP Pre‐Installation Information for XPP ...... 1‐1 Directory Structure ...... 1‐1 Temporary Files Directory ...... 1‐1 Distribution Directory ...... 1‐2 Quick Access to XPP Directories ...... 1‐2
Chapter 2 Licensing About Licensing ...... 2‐3 Multiprocessor Reporting Tool ...... 2‐4 Obtaining a License ...... 2‐5
Chapter 3 Third-Party Software and XPP Third‐Party Software Modules Required When Upgrading XPP ...... 3‐1 Java ...... 3‐1 MKS X/Server ...... 3‐2 MKS X/Server and SDL Contenta ...... 3‐2 MKS X/Server and XVision X/Server ...... 3‐2 Installing in a Networked Environment ...... 3‐2 Using an NTFS File System or Active Directory ...... 3‐2
Chapter 4 Installing XPP Java (optional) ...... 4‐1 Installing XPP Server ...... 4‐2 Post‐Installation Tasks ...... 4‐4 Installing the XPP Client ...... 4‐5
SDL XPP Installation and Upgrade Guide for Windows Contents iii Chapter 5 Upgrading XPP Overview ...... 5‐1 Upgrading from XPP 7.3 or earlier ...... 5‐2 Upgrading the XCS Spec ...... 5‐2 Upgrading XPP Servers ...... 5‐3 Post‐Upgrade Tasks ...... 5‐5 Upgrading XPP Clients ...... 5‐6
Chapter 6 Post-Installation Configuration Activating Your X Server For XPP ...... 6‐1 Configuring MKS X/Server ...... 6‐1 Configuring MKS X/Server for XPP ...... 6‐1 Configuring MKS X/Server for an International Keyboard ...... 6‐3 Compiling and Loading vuem Fonts in Exceed ...... 6‐3 Updating X Servers for Cut, Copy, and Paste ...... 6‐3 MKS X/Server ...... 6‐4 Exceed ...... 6‐4 Other X Servers ...... 6‐4 UNC Format ...... 6‐5 Document Paths ...... 6‐5 Environment Variables ...... 6‐5 Graphics Paths ...... 6‐6 Distribution and Destination Directories ...... 6‐7 Configuring System Processes ...... 6‐11 Completing an Upgrade of XPP Server ...... 6‐12 Converting Data ...... 6‐12 Installing the Shakespeare CSS Demo ...... 6‐13 Configuring Print Directly to PDF ...... 6‐13
Appendix A Establishing Secure Access (Optional) Assumptions and Recommendations ...... A‐1 System Default Configuration ...... A‐1 XPP and Security ...... A‐2 Pre‐Installation Configuration ...... A‐2 Post‐Installation Configuration ...... A‐2 Special Domain Groups and XPP Permissions ...... A‐3
iv Contents SDL XPP Installation and Upgrade Guide for Windows Application Permissions Groups and Multiple Domains ...... A‐3 XPP Security Lock‐Down Mode ...... A‐4 Source of Access ...... A‐5 Share Permissions ...... A‐6
Appendix B Troubleshooting Troubleshooting ...... B‐1 MKS X/Server Creates Excessive Network Traffic ...... B‐3 Bringing Forms to the Foreground ...... B‐3 Third‐party Upgrades ...... B‐4 First Attempt ...... B‐4
Appendix C Licensing Across a Firewall Changing the Port Number ...... C‐1
SDL XPP Installation and Upgrade Guide for Windows Contents v vi Contents SDL XPP Installation and Upgrade Guide for Windows Chapter 1 Preparing to Install 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
c:\Program Files\XyEnterprise\XML Professional Publisher Note:You can define additional data handles in any location on your system.
Table 1-1: Directory Structure
Software Directory Description 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\alljoz
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.
SDL XPP Installation and Upgrade Guide for Windows Preparing to Install XPP 1-1 Pre-Installation Information for XPP
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 (
Quick Access to XPP Directories During the installation process, the following XPP environment variables are set.
Table 1-2: 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. 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-2 Preparing to Install XPP SDL XPP Installation and Upgrade Guide for Windows 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 or upgrading XPP • Installing a new XPP software option (CITI, for example) You can complete the installation without the license file, but it is recommended that you obtain and save the license file on the designated server or servers before installing XPP. You cannot open or compose a division until you install the license file. Only one active license file is permitted in the License Manager folder. 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 (possibly with a .bak file extension). Then install the new license file as is and run rlmreread.exe against it. Note:XPP 9.0 can be installed with Contenta 5.1 or Contenta 5.2. 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 you are installing or upgrading to XPP 9.0, you must install the license manager to use Reprise Version 10.1. If FlexLM is required by applications other than XPP, it can coexist on the same computer 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. Note:When installing the Reprise License Manager, you may encounter the error message “Installer User Interface Mode Not Supported” and the Reprise installation will fail. This may be due to your admin login user name containing special characters (for example, “!”).
SDL XPP Installation and Upgrade Guide for Windows Licensing 2-3 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 C‐1).
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 the tool 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-4 Licensing SDL XPP Installation and Upgrade Guide for Windows Obtaining a License
Obtaining 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. You will be asked to provide information about your site and XPP server: • 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 or XyEnterprise invoices and in existing license files. • Host name of the designated server To determine the host name of the designated server: a. Right‐click the My Computer icon on your desktop, then click Properties. b. Click the Computer Name tab. The host name is displayed as the ‘Full computer name.’ • Host ID (MAC Address) of the designated server To determine the Host ID of the designated server: a. Open a command prompt. b. Type ipconfig /all. The host ID is the value listed for Physical Address under Ethernet adapter Local Area Connection in the following format: 00‐00‐00‐00‐00‐00. If you have multiple Ethernet connections, use the physical address for the first Ethernet connection in the list. c. Alternately, you can install XPP first, then obtain the host ID from the Reprise License Manager folder by issuing the following command at a command prompt: LicenseManagerInstallDir\rlmhostid.exe ‐q where LicenseManagerInstallDir is the folder where you installed the Reprise License Manager. For example: “C:\Program Files\XyEnterprise\SDL_License\rlmhostid.exe” ‐q
SDL XPP Installation and Upgrade Guide for Windows Licensing 2-5 Obtaining a License
Once your request has been received, SDL should email the license file to you within 24 hours. 1. When you receive the license file, do one of the following: • If you have not yet installed XPP, save the file attachment as‐is (do not rename it) to any folder on the server. • If you have already installed XPP, save the file attachment as‐is (do not rename it) to the license manager folder, for example, C:\Program Files\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. 2. At that point, you can do one of the following: • If you have not yet installed XPP, proceed with installation. When prompted for a license file during installation, navigate to the folder where you saved the file attachment and select it. • If you have already installed XPP, navigate to the license manager folder, and then double‐click rlmreread.exe.
2-6 Licensing SDL XPP Installation and Upgrade Guide for Windows Chapter 3 Third-Party Software and XPP
Third-Party Software Modules Required When Upgrading XPP
This section describes what third‐party software versions must be installed when you are upgrading from older versions of XPP. In this version of XPP, these third‐party and SDL software versions will be installed. • MKS Toolkit 9.5 • MKS X/Server 8.6 • ActivePerl 5.16 • XPP‐required Extra Perl Modules • Reprise License Manager 10.1 The installation steps for specifying these third‐party software installation options are described in Installing XPP on page 4‐1 and Upgrading XPP on page 5‐1. Note: The XPP CD contains subfolders for third‐party products that support XPP, some of which also contain installers. You should not run installers from these subfolders. Instead, run the setup.exe from the root (top) level of the XPP CD, which contains a wizard for installing third‐party products. In doing so, a software hotfix for MKS X/Server 8.6 is installed automatically that lets you copy text containing special characters from a non‐XPP application and successfully paste that text into an XPP division.
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.
SDL XPP Installation and Upgrade Guide for Windows Third-Party Software and XPP 3-1 MKS X/Server
MKS X/Server
MKS X/Server and SDL Contenta If you have Contenta 5.1 or Contenta 5.2 (or greater) and XPP installed on the same computer, MKS X/Server (delivered with XPP) and Xming (delivered with Contenta) can coexist, but depending on which is started first, the DISPLAY must be set accordingly. If MKS X/Server was started first, Xming must be started manually, specifying a different DISPLAY number. In this case, ensure that the X0.host file is copied to X
MKS X/Server and XVision X/Server If you have an old XVision X/Server on your system, you must remove it before installing MKS X/Server; otherwise, you will not be able to successfully install the MKS X/Server. Installing in a Networked Environment
Installing XPP in a networked environment may require that you configure secure access for the application. For details, see Establishing Secure Access (Optional) on page A‐1 before you begin the installation to complete the preliminary configuration steps. Using an NTFS File System or Active Directory
If you are using either an NTFS file system or Microsoft Windows Active Directory, you must configure all file systems on drives hosting XPP software and data before installing XPP.
3-2 Third-Party Software and XPP SDL XPP Installation and Upgrade Guide for Windows Chapter 4 Installing XPP
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 assume that you are familiar with the interactions between XPP and other third‐party products, as described in Third‐Party Software and XPP on page 3‐1. These instructions apply to installing XPP only on server and client computers that do not have an existing XPP installation in place. If XPP is already installed on your server or client computer, see Upgrading XPP on page 5‐1 instead.
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 Windows Installing XPP 4-1 Installing XPP Server
Installing XPP Server
To install XPP server: 1. Obtain a license file and place it in the folder as specified in Obtaining a License on page 2‐5. 2. Log in as a local administrator. 3. On the installation CD‐ROM, double‐click setup.exe. 4. In the Welcome panel, click Next. 5. In the License Agreement panel, read the software License Agreement, then click Yes. 6. In the Introduction panel, click Next. 7. In the Setup Type panel, click Server, then click Next. 8. In the Choose Third‐Party Software panel, select all third‐party products and click Next. Note: During installation, XPP examines the version of the Reprise License Manager; if it detects Version 10.1, it will not be reinstalled. 9. In the Choose Language panel, click the language in which you want XPP messages to display, then click Next. 10. In the dialog box about upgrading the XCS spec, click Yes. Because this is a new installation, this information does not pertain. 11. In the Choose Install Folder panel, specify where to create the xz folder, and then click Next. Note: This install path is the {XPP_home} variable xz contains subdirectories of XPP executable programs and configuration files. It is strongly recommended that you install xz and sd_liz to the same folder. These folder names are case‐sensitive. Use only lowercase letters for xz, sd_liz, and std_jobz. If you type a path name, you must include the disk volume. If the folder you specify does not exist, the installation program creates it. 12. In the Choose Style Files Folder panel, specify where to create the sd_liz folder, then click Next. sd_liz contains the style files and libraries. It is strongly recommended that you install xz and sd_liz to the same folder. These folder names are case‐sensitive. Use only lower‐case letters for xz, sd_liz, and std_jobz. 13. In the Start Copying Files panel, review your settings, then click Next to begin installing.
4-2 Installing XPP SDL XPP Installation and Upgrade Guide for Windows Installing XPP Server
14. To install ActivePerl, do the following: a. Click OK in the Windows Installer dialog to begin the ActivePerl installa‐ tion. b. In the ActivePerl Setup panel, click Next. c. In the End‐User License Agreement panel, click I accept the terms in the License Agreement, then click Next. d. In the Custom Setup panel, click Next to install all Perl options. It is recommended that you install to
SDL XPP Installation and Upgrade Guide for Windows Installing XPP 4-3 Installing XPP Server
Post-Installation Tasks
1. This step applies only if you are installing Windows XPP clients serviced by this Windows XPP server. In step 11 on page 4‐2, XPP was installed to a path, which you refered to as {XPP_home}. In this step, you are going to share the last directory component of {XPP_home} and the name assigned to that share you will call {XPP_share}. a. Define {XPP_home} {XPP_home} = "c:\Program Files (x86)\XyEnterprise\XML Professional Publisher" b. Define {XPP_share} Share the ʺXML Professional Publisherʺ directory, giving it a unique share name, such as ʺxpp.ʺ Now {XPP_share} refers to that share name. All XPP users must have both read and write access to the {XPP_share} folder c. Modify %XYV_EXECS% and %XYV_STYLES% environment variables to be \\server\{XPP_share}\xz and \\server\{XPP_share}\sd_liz, respectively. Later, each XPP client would be configured to use identical settings for their %XYV_EXECS% and %XYV_STYLES% variables. d. By default, the server install adds {XPP_home}\xz\bin to the %PATH% vari‐ able. You should change this to \\server\{XPP_share\xz\bin on the server, and later on the XPP clients as well. 2. If it exists, install the current XPP Service Pack. 3. If you are setting up secure access to XPP, see Establishing Secure Access (Optional) on page A‐1 for post‐installation steps. Even if you are not setting up secure access to XPP, see XPP Security Lock‐Down Mode on page A‐4, which can cause XPP to deny access to XyAdmin, and also deny edit access to style specs and jobs. 4. Optionally, copy the documentation from the XPP Documentation CD‐ROM to {XPP_home}\documentation\manuals. This makes the PDFs available through XPP PathFinder. 5. Complete the post‐installation configuration (see Post‐Installation Configuration on page 6‐1).
4-4 Installing XPP SDL XPP Installation and Upgrade Guide for Windows Installing the XPP Client
Installing the XPP Client
To install XPP client: 1. Log in to the client as a local administrator. 2. On the installation CD‐ROM, click setup.exe, then right‐click and choose “Run as administrator.” 3. In the Welcome panel, click Next. 4. In the License Agreement panel, read the software License Agreement, then click Yes. 5. In the Introduction panel, click Next. 6. In the Setup Type panel, click Client Setup, then click Next. 7. In the Choose Third‐Party Software panel, select all third‐party products (except the license manager) and then click Next. 8. In the Enter Text panel, enter the XPP server name or IP address to which this client will connect, then click Next. 9. In the Choose Install Folder panel, specify the UNC path (for example, \\servername\{XPP_share}) to the server location that contains the xz folder, then click Next. 10. In the Choose Style Files Folder panel, specify the UNC path (for example, \\servername\{XPP_share}) to the server location that contains the sd_liz folder, then click Next. 11. In the Start Copying Files panel, review your settings, then click Next to begin installing. 12. To install ActivePerl, do the following: a. In the ActivePerl Setup panel, click Next. b. In the End‐User License Agreement panel, click I accept the terms in the License Agreement, then click Next. c. In the Custom Setup panel, click Next to install all Perl options. It is recommended that you install to
SDL XPP Installation and Upgrade Guide for Windows Installing XPP 4-5 Installing the XPP Client
14. To install MKS Toolkit and MKS X/Server, do the following for both products: a. In the Choose Destination Location panel, select the folder in which to install the product, then click Next. b. When the program has finished installing, click OK. If it appears that the installation is hung, look for a minimized dialog and then click OK in that dialog. 15. Click Yes, I want to restart my computer now, then click Finish. 16. Complete the post‐installation configuration (see Post‐Installation Configuration on page 6‐1).
4-6 Installing XPP SDL XPP Installation and Upgrade Guide for Windows Chapter 5 Upgrading XPP
Overview
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 tools will be installed. • Perl 5.16 • XPP Required Extra Perl Modules • Reprise License Manager 10.1
SDL XPP Installation and Upgrade Guide for Windows Upgrading XPP 5-1 Upgrading from XPP 7.3 or earlier
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. 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 server. 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.
5-2 Upgrading XPP SDL XPP Installation and Upgrade Guide for Windows Upgrading XPP Servers
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 just running upgradexcs.pl. You may prefer to receive assistance from SDL Professional Services.
Upgrading XPP Servers
Perform this procedure on XPP servers. To upgrade XPP clients, see Upgrading XPP Clients on page 5‐6. 1. If your installation is prior to XPP 8.3, you must obtain and install a new license file (see Obtaining a License on page 2‐5). 2. If you are upgrading from a version of XPP prior to 9.0, you must un‐install ActivePerl before upgrading. Before you uninstall ActivePerl, 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. If you are upgrading from XPP 8.2 or later, you do not have to uninstall any other third‐party software. 3. Uninstall XVision X Server (if it was previously installed) 4. Log in as a local administrator. 5. On the installation CD‐ROM, double‐click setup.exe. 6. In the Welcome panel, click Next. 7. In the License Agreement panel, read the software License Agreement, then click Yes. 8. In the Introduction panel, click Next. 9. In the Setup Type panel, click Server, then click Next.
SDL XPP Installation and Upgrade Guide for Windows Upgrading XPP 5-3 Upgrading XPP Servers
10. In the Choose Third‐Party Software panel, include all options and then click Next. Note: If Reprise License Manager, Version 10.1, has been installed already for other SDL products, XPP will not reinstall it. 11. In the Choose Language panel, click the language in which you want XPP messages to display, then click Next. 12. Read the message about the XCS Spec, then click Yes. Note: Send your XCS spec to SDL for evaluation before upgrading from XPP 7.3 or earlier to 9.x (see Upgrading the XCS Spec on page 5‐2). Do not proceed with configuring the server system before you have completed this step. 13. In the Choose Install Folder panel, click Next to confirm the xz folder. 14. In the Choose Style Files Folder panel, click Next to confirm the sd_liz folder. 15. In the Start Copying Files panel, review your settings, then click Next to begin installing. 16. To install ActivePerl, do the following: a. In the ActivePerl Setup panel, click Next. b. In the End‐User License Agreement panel, click I accept the terms in the License Agreement, then click Next. c. In the Custom Setup panel, click Next to install all Perl options. It is recommended that you install to drive_letter:\Perl (for example, C:\Perl). d. In the Choose Setup Options panel, check Add Perl to the PATH environ‐ ment variable and Create Perl file extension association, then click Next. e. In the Ready to Install window, click Install. f. After the upgrade has completed, click Finish. The ActivePerl release notes appear (unless you uncheck this option). 17. The XPP upgrade will continue with a cmd.exe window automatically opening to display the upgrade progress of the XPP‐required Perl modules. After the modules are installed, press any key in the DOS window to complete this step and continue.
5-4 Upgrading XPP SDL XPP Installation and Upgrade Guide for Windows Upgrading XPP Servers
18. To install the MKS Toolkit and MKS X/Server, do the following for both products: a. Ensure that there is no active MKS X/Server profile running. b. If the installation program detects an existing MKS Toolkit, click Yes. Otherwise, skip to the next step. c. In the Choose Destination Location panel, select the folder in which to install the product, then click Next. d. When the program has finished installing, click OK. e. If you have a previous version of MKS X/Server, an information pop‐up message appears. Click Yes to upgrade. f. In the next window, verify the destination folder for MKS X/Server, and then click Next. If it appears that the installation is not progressing, look for a minimized dialog, and then click OK in that dialog. If the upgrade of any third‐party application fails, note it and continue with this upgrade procedure to its completion. Then, for any failed third‐ party upgrade, refer to Appendix B, Third‐party Upgrades on page B‐4 to resolve the issue. 19. In the Do you have a license file to install? dialog, click Yes. 20. Enter the license file path name and click Next. 21. In the Multiprocessor Check window, click Next. 22. If prompted, click Yes, I want to restart my computer now. 23. Click Finish.
Post-Upgrade Tasks 1. If it exists, install the current XPP Service Pack. 2. If upgrading from 7.3 or earlier, you may need to upgrade your XCS spec (see Upgrading the XCS Spec on page 5‐2). 3. Optionally, copy the documentation from the XPP Documentation CD‐ROM to {XPP_home}\documentation\manuals This makes the PDFs available through XPP PathFinder. 4. Complete the post‐installation configuration (see Post‐Installation Configuration on page 6‐1).
SDL XPP Installation and Upgrade Guide for Windows Upgrading XPP 5-5 Upgrading XPP Clients
Upgrading XPP Clients
Perform this procedure on XPP clients. To upgrade XPP servers, see Upgrading XPP Servers on page 5‐3. 1. If you are upgrading from a version of XPP prior to 9.0, you must uninstall ActivePerl. Before uninstalling ActivePerl, 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: MKS X/Server does not have to be uninstalled to upgrade. If you are upgrading from XPP 8.2 or later, you do not have to uninstall any other third‐party software. 2. Uninstall XVision X Server (if it was previously installed) 3. Log in as a local administrator. 4. On the installation CD‐ROM, double‐click setup.exe. 5. In the Welcome panel, click Next. 6. In the License Agreement panel, read the software License Agreement, then click Yes. 7. In the Introduction panel, click Next. 8. In the Setup Type panel, click Client, then click Next. 9. In the Choose Third‐Party Software panel, select all third‐party products (except the license manager) and then click Next. 10. In the Enter Text panel, enter the XPP server name or IP address to which this client will connect, then click Next. 11. In the Choose Install Folder panel, specify the UNC path (for example, \\servername\{XPP_share}) to the server location that contains the xz folder, then click Next. 12. In the Choose Style Files Folder panel, accept the defaults, or specify the UNC path (for example, \\servername\{XPP_share}) to the server location that contains the sd_liz folder, then click Next. 13. In the Start Copying Files panel, review your settings, then click Next to begin installing. 14. To install ActivePerl, do the following: Note: If you are upgrading from a version of XPP prior to 9.0, you must uninstall ActivePerl before upgrading. a. Click OK in the Windows Installer dialog to begin the ActivePerl installa‐ tion. b. In the ActivePerl Setup panel, click Next. c. In the End‐User License Agreement panel, click I accept the terms in the License Agreement, then click Next.
5-6 Upgrading XPP SDL XPP Installation and Upgrade Guide for Windows Upgrading XPP Clients
d. In the Choose Destination Location panel, specify the folder in which to install the ActivePerl software, then click Next. e. In the Custom Setup panel, click Next to install all Perl options. f. In the Choose Setup Options panel, check Add Perl to the PATH environ‐ ment variable and Create Perl file extension association, then click Next. g. In the Ready to Install panel, click Install to install ActivePerl. After the upgrade has completed, you can view the ActivePerl release notes. h. Click Finish. 15. The XPP upgrade will continue with a cmd.exe window automatically opening to display the upgrade progress of the XPP‐required Perl modules. After the modules are installed, press any key in the DOS window to complete this step and continue. 16. To install MKS Toolkit and MKS X/Server, do the following for both products: a. Ensure that there is no active MKS X/Server profile running. b. If the installation program detects an existing MKS Toolkit, click Yes. Otherwise, skip to the next step. c. In the Choose Destination Location panel, select the folder in which to install the product, then click Next. d. When the program has finished installing, click OK. e. If you have a previous version of MKS X/Server, an information pop‐up message appears. Click Yes to upgrade. f. In the next window, verify the destination folder for MKS X/Server, and then click Next. If it appears that the installation is not progressing, look for a minimized dialog, and then click OK in that dialog. If the upgrade of any third‐party application fails, note it and continue with this upgrade procedure to its completion. Then, for any failed third‐ party upgrade, refer to Appendix B, Third‐party Upgrades on page B‐4 to resolve the issue. 17. Complete the post‐installation configuration (see Post‐Installation Configuration on page 6‐1).
SDL XPP Installation and Upgrade Guide for Windows Upgrading XPP 5-7 Upgrading XPP Clients
5-8 Upgrading XPP SDL XPP Installation and Upgrade Guide for Windows Chapter 6 Post-Installation Configuration
Activating Your X Server For XPP
If you choose a different X Server (such as OpenText Exceed) or have more than one X Server installed on your client or server system, you must activate it through MKS Toolkit. 1. Open the Windows Control Panel. 2. Click Configure MKS Toolkit in the Control Panel window. 3. On the Runtime Settings tab, in the Category drop‐down list, click X Window System settings from the list. 4. Click Registered. 5. Click the X Server that you installed. MKS Toolkit places a green check mark in front of your choice. 6. Click Apply, and then click OK. 7. Close the Control Panel. Configuring MKS X/Server
Configuring MKS X/Server for XPP After upgrading or performing a new installation, perform this task on both XPP clients and XPP servers. 1. Do one of the following: • On an XPP server, log in as local administrator. • On an XPP client, log in as a network user. 2. In Windows, click Start > All Programs > MKS XServer > Configuration > MKS XServer Configuration.
SDL XPP Installation and Upgrade Guide for Windows Post-Installation Configuration 6-1 Configuring MKS X/Server
3. To verify TCP‐Unix availability, do the following: a. Under Edit Settings, click Communications. b. On the Transports tab, verify the following: • TCP‐Unix is in the list. • Status is Available. • Auto is set to Yes. c. Click OK. 4. To configure MKS X/Server automated behaviors: a. Under Edit Settings, click Global. b. Select Load MKS XServer at Windows startup. c. Select Automatically select display number. d. Click OK. 5. To configure MKS X/Server input device behavior, do the following: a. Under Properties, click Input Devices. b. Clear Keymap locked. c. Clear Local NumLock management. d. Select IntelliPoint support. e. Select Middle mouse button emulation. f. Click Advanced, verify that Mouse button events is selected, and then click OK. g. Click OK. 6. To include vuem fonts, do the following: a. Copy the %XYV_EXECS%\xfonts folder from the XPP Server to a local directory on the client. b. Under Properties, click Fonts. c. On the Fonts tab, click Add. d. Click Fonts folder, and then click Add. e. In the Choose a folder of fonts window, in the Look in box, navigate to the location of the %XYV_EXECS%\xfonts folder. f. Click Advanced. g. Click Select all. h. Under Type, click pcf. i. Click Add. j. Click OK. 7. Click Save. 8. In the Graphics window, click Optimize Now to optimize the display. 9. Click Close when the process is finished.
6-2 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for Windows Configuring MKS X/Server
Configuring MKS X/Server for an International Keyboard
Optionally, if you are using an X Server to work with XPP applications and you have a foreign keyboard set as the default on your PC, you must also configure the active keyboard in the X Server. 1. Click Start > Programs > MKS XServer > Configuration > MKS XServer Configuration. 2. Click Input Devices. 3. On the Devices tab, in the Keyboard Map field, select the appropriate language (depends on the foreign keyboard). 4. Click OK.
Compiling and Loading vuem Fonts in Exceed 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. Click Add Font Directory. In the Status field, State “Load” will be selected automatically. In the Match field, Physical Font Name Match Allowed is checked. 6. Browse to the XPP xfonts directory on your local drive, and then click OK. 7. Use the Move Up button to relocate the xfonts directory from the bottom of the list to the top. 8. In the left pane, click Validate and Apply Changes under Common Actions.
Updating X Servers for Cut, Copy, and Paste The following changes must be made to the X servers to use the cut, copy, and paste functionality. Perform this procedure on each windows client on which you want to be able to cut, copy, and paste text to and from XyView and Sdedit.
SDL XPP Installation and Upgrade Guide for Windows Post-Installation Configuration 6-3 Configuring MKS X/Server
MKS X/Server 1. In X/Server Properties/Clipboard configuration, set the following: • Mode: Automatic • Selection: Clipboard • Targets: UTF8_STRING 2. Restart the X server.
Exceed 1. In Configuration > Copy, Paste, and X selection, set the following: • X Selection Associated with Edit Operations: CLIPBOARD • Select Auto Copy X selection. • Clear Copy on Focus Loss. • Select Auto Paste to X Selection. • Grab Clipboard Retry Time (ms): 200 • Auto Paste Delay Time (ms): 200 2. Click Security. 3. Click System Administration, 4. Clear X Server Copy/Paste. 5. Click Validate and Apply Changes. 6. Restart the X server.
Other X Servers 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’s documentation.
6-4 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for Windows UNC Format
UNC Format
This section applies only if you intend to have XPP clients of this XPP server.
Document Paths If you chose a location other than the default path of the xz and sd_liz directories, the installation program installs the software to the specified locations using the local drive letters. Your server would find the necessary path information and location of data, but the client machines would not. 1. In Windows, click Start > Programs > XyEnterprise > XML Professional Publisher > XPP > Administrative Tools. 2. Click File > Document Paths. 3. In the Job Handle list box, select the handle to edit. 4. Change the {XPP_home} prefix of the job handle to the \\servername\{XPP_share} prefix. Do this for each job handle. 5. Click Set. 6. Click Apply.
Environment Variables If XPP is running under a server/clients model, ensure the following environment variables are set correctly: 1. Click Start. 2. In the Search programs and files type‐in field, enter path. 3. Click Edit the system environment variables. The Environment Variables pane opens. Note:These steps may differ slightly, depending on your version of Windows.
Table 6-1: Environment Variables
Environment Variable Path
%XYV_EXECS% \\servername\{XPP_share}\xz
%XYV_STYLES% \\servername\{XPP_share}\sd_liz
%XYV_TMPS% C:\Users\SAPPLE~1\AppData\Local\Temp\2
SDL XPP Installation and Upgrade Guide for Windows Post-Installation Configuration 6-5 UNC Format
Table 6-1: Environment Variables
Environment Variable Path
%PATH% C:\Program Files\MKS XServer\system\;C:\Program Files\MKS XServer\;C:\Program Files (x86)\Common Files\MKS X Server\;C:\Perl\Perl\site\bin;C:\Perl\Per l\bin;C:\PROGRA~1\NuTCRoot\bin64;C:\PROGR A~1\NuTCRoot\bin;C:\PROGRA~1\NuTCRoot\bin \X11;C:\PROGRA~1\NuTCRoot\mksnt;C:\Perl\s ite\bin;C:\Perl\bin;C:\Perl\site\C:\Perl\ bin;C:\Perl\site\C:\Perl\bin;C:\Perl\site \C:\Perl\bin;%SystemRoot%\system32;%Syste mRoot%;%SystemRoot%\System32\Wbem;%SYSTEM ROOT%\System32\WindowsPowerShell\v1.0\; \\servername\{XPP_share}\xz\bin
Graphics Paths If XPP is running under a server/clients model, ensure the following graphics paths are set correctly: 1. Click Start > All Programs > XML Professional Publisher > XPP > Administrative Tools. 2. Click File > Graphics Configuration. The Master im config pane opens.
Table 6-2: Graphics Variables
Graphics Variable Path
$XYV_EXECS%/distr/ \\servername\{XPP_share}\xz\distr\ graphics graphics
c:/Progra~2/XyEnte~1 \\servername\{XPP_share}\glibs\ /XMLPro~1/glibs/ $(XYV_LIBNAME) $(XYV_LIBNAME)
6-6 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for Windows Distribution and Destination Directories
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 6-3: Distribution and Destination Directories
Files Function Delivered To/Destination Directory
XYwyg Customizes attributes of the Delivered to: XyView window, including %XYV_EXECS%\distr\app-defaults foreground and background colors, Line Editor window or your home directory. Files in your font and position, Status home directory take precedence over window font and position, system files. X‐menu sidebar font and position.
Sdedit Style editor resources. Delivered to: %XYV_EXECS%\distr\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
SDL XPP Installation and Upgrade Guide for Windows Post-Installation Configuration 6-7 Distribution and Destination Directories
Table 6-3: 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_EXEC%\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 tables styles, fonts, color, conversion, \Llibrary and composition and Keyboard maps pagination parameters. Destination: Kerning pairs $XYV_STYLES/Llibrary Font width specs for standard 35 PostScript fonts
6-8 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for Windows Distribution and Destination Directories
Table 6-3: 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
SDL XPP Installation and Upgrade Guide for Windows Post-Installation Configuration 6-9 Distribution and Destination Directories
Table 6-3: 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
6-10 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for Windows Configuring System Processes
Table 6-3: 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
Configuring System Processes
Once you have successfully installed XPP on the server, set u..p 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 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. Also, see Completing an Upgrade of XPP Server on page 6‐12.
SDL XPP Installation and Upgrade Guide for Windows Post-Installation Configuration 6-11 Completing an Upgrade of XPP 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 for more information).
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.
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 XML Professional Publisher: Command Line Utilities 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.
6-12 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for Windows Installing the Shakespeare CSS Demo
2. Enter the following command at the command line prompt: cnv_tree This utility converts your divisions and local specs to run on XPP. For more information, run the following command in a terminal window: xyhelp cnv_tree 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 command line, enter %XYV_EXECS%\procs\sc\pdfsetup.pl
SDL XPP Installation and Upgrade Guide for Windows Post-Installation Configuration 6-13 Configuring Print Directly to PDF
6-14 Post-Installation Configuration SDL XPP Installation and Upgrade Guide for Windows 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
This section 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. Because users and groups, who are registered only on a particular Windows workstation or server, are so limited, SDL recommends that all users and groups be configured as Domain users and groups.
System Default Configuration Ensure that XPP application and data servers are physically secure and protected against unauthorized access via User Rights and Policies. Also ensure that all drives in your Windows domain are formatted as NTFS. Remove “Everyone” privileges from all resources (drivers, printers, etc.), substituting “A u t h e n t i c a t e d Users” or other desired group(s). If desired, you can set up an XPP users login script that automatically runs when the users log on.
SDL XPP Installation and Upgrade Guide for Windows Establishing Secure Access (Optional) A-1 XPP and Security
XPP and Security
This section describes establishing XPP security on Windows platforms on two levels: file permissions and application permissions. XPP file permissions are set up with a domain local user group. Only users included in the group can execute the XPP application and access XPP data. However, there is no distinction between user group members regarding their permissions within the XPP application. XPP application permissions are set up with application groups named xyadmin, xystyle, and xyjstyle. Although you create and add users to these groups on the Windows domain, their permissions are defined in the XPP application itself.
Pre-Installation Configuration Before you install XPP, set up file permissions for the XPP data as follows: 1. Create a domain local group for your XPP users. Note: The examples in this and the following section use the group name xppusers but you can use any valid group name. 2. Add all XPP users and the Domain Administrator account to this XPP user group xppusers. If you have a user account for SDL Technical Support personnel to use for remote diagnostics, include this account in the group as well. 3. Log in as an xppusers group member with administrative privileges, then install the XPP software according to the procedure in Installing XPP on page 4‐1. 4. Note the following recommendations: • Install XPP and its accompanying third‐party products to a drive that contains enough free space to hold the software and XPP data. • Share the XPP paths for access by XPP clients and define correct share permissions for the xppusers group. • Ensure that all clients map XPP shares to the same drive letters or else use UNC pathing exclusively.
Post-Installation Configuration After you install XPP, do the following: 1. Configure the Auto‐processing and Background‐processing services on the XPP server(s). 2. Remove Everyone permissions from all XPP paths. 3. Give the XPP users’ group xppusers full permissions. Check the boxes for both files and subdirectory. Steps 2 and 3 restrict access to XPP applications and data to members of the xppusers group only.
A-2 Establishing Secure Access (Optional) SDL XPP Installation and Upgrade Guide for Windows XPP and Security
4. To further control XPP access, you can set up the xyadmin, xystyle, xyjstyle, and xyperuse groups with appropriate members (see Special Domain Groups and XPP Permissions on page A‐3).
Special Domain Groups and XPP Permissions XPP defines and manages application permissions through domain local groups named xyadmin, xystyle, xyjstyle, and xyperuse. These groups have the following XPP application permissions: • xyadmin Group members can run XPP administrative tools and modify XPP style files at either the system library or the local job level. If you establish this group, include your Windows system administrator as a member. • 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. When you create a group, XPP restricts access to the tools, libraries, and specs to users of that group. If you do not create the groups, no XPP restrictions apply. For example, if you create the xyadmin group, a user who is not a member of the group is unable to run the XPP Administrative tool. Users must be assigned to a group to run the tool. However, if you do not create the xyadmin group, all XPP users can run the XPP Administrative tool.
Note: If you remove any one of these groups after its creation, all client systems must reboot for the permission changes to take effect.
Application Permissions Groups and Multiple Domains
If you establish the xyadmin, xystyle, xyjstyle, or xyperuse groups in one domain you affect user access in ALL domains. Thus, if these groups are defined anywhere, they affect users everywhere. It is up to the Windows system administrator to ensure that all valid XPP users from ALL domains are included in the appropriate group(s), and that appropriate trust relationships have been established between domains.
SDL XPP Installation and Upgrade Guide for Windows Establishing Secure Access (Optional) A-3 XPP and Security
XPP Security Lock-Down Mode To implement XPP Security, XPP queries the domain (or the Active Directory forest) for the existence of the special XPP application groups. Certain network problems can prevent XPP from successfully discovering the security groups. If this happens, XPP will go into “XPP security lock‐down mode” and deny non‐Administrator users access to XyAdmin and deny edit access to style specs and jobs. This is because these groups are application groups for security; if XPP cannot determine whether the groups exist (and who belongs to them), then for security reasons XPP must assume that the groups exist and that the current user does not belong to them. A typical scenario where this “XPP security lock‐down mode” may occur is when the special security groups are not being used, but a domain controller in the AD forest has malfunctioned or has been removed from the forest without having updated the network. Because XPP cannot successfully query the entire defined network for the existence of the security groups, it goes into lock‐down mode and denies access to some operations. When the XyAdmin/PathFinder applications are started, the user may be presented with a window with messages like the following (from XyAdmin): CheckGroup(xyadmin) - unexpected LookupAccountName() error (error 1788: the trust relationship between the primary domain and the trusted domain failed.) Problem specifically with trusted domain DOM XPP will act like you do not belong to the 'xyadmin' group You are also not running as an administrator (possibly due to UAC) You do not have permission to use XyAdmin The solution is to diagnose and fix the network problems. The example diagnostic messages shown above indicate that DOM is the domain that is not responding. Temporary solutions to allow XPP users to continue working until the network problems are resolved might include the following: 1. Run XyAdmin and/or PathFinder using “Run as administrator”. This may be necessary, including an Administrator user account, if Windows UAC (User Access Control) is enabled as that may be preventing the user account from running with Administrator access. The administrator permissions enabled in XyAdmin and PathFinder will be inherited by any process initiated from those applications. 2. Temporarily define the special XPP security groups on the local domain (or the local machine) and add all XPP users (or the xppusers group, if defined, or “Everyone”) to the groups. If XPP security groups were not being used, it should only be necessary to temporarily define the xyadmin security group. Once the network problems are resolved, remove any XPP security groups that have been temporarily defined. The XyAdmin and PathFinder applications have some built‐in diagnostics to try to determine what network error is occurring. For the 1788 network error (shown in the previous example), the messages will indicate which domain is not responding to the request for the existence (and definitions) of the XPP security groups. The messages will also indicate that XPP has to deny access to certain operations.
A-4 Establishing Secure Access (Optional) SDL XPP Installation and Upgrade Guide for Windows XPP and Security
These diagnostics only occur when the XyAdmin and PathFinder applications are started (other XPP applications like Sdedit and XyView do check for the XPP security groups, but they do not contain the extra diagnostics). If such network errors occur after they are already running, and users have write access denied to style specs or jobs, then restart the XyAdmin or PathFinder application to learn whether there are any diagnostic messages given that will help in determining what network problem has occurred. On the pop‐up error message window, by default only the last diagnostic message is visible. Click on the Details >> button (and expand the size of the window) to display the full set of diagnostic messages.
Source of Access The xyadmin, xystyle, xyjstyle, and xyperuse groups control access via XPP applications (xzplorer, sdedit, and xyview) only. To control back door access (like delete from the command line or Windows Explorer), manually set file system and share permissions on the local file systems where XPP resides. The following table provides recommended share permissions for the XPP directories for the XPP users (xppusers), xyadmin, xystyle, and xyjstyle groups. The xyperuse group can be assigned the same permissions as the xppusers group or made a member of the xppusers group.
Table A-1: Recommended Share Permissions
Folder xppusers xyadmin xystyle xyjstyle
path\xz\bin Read Full Control Read* Read*
path\xz\sys\config Read Full Control Read* Read*
path\sd_liz Read Full Control Full Control Read*
path\xz\help Read S.A. Read* Read* r, w, x, d
%XYV_JOB% S.A. Full Control S.A. S.A. r, w, x, d r, w, x, d r, w, x, d or Full Control
where: • * indicates you do not have to assign these group permissions if group members are also members of the xppusers group. • path represents the user‐defined location(s) for the xz and sd_liz directories. • %XYV_JOB% represents the job handles set up under Start > Programs > XyEnterprise > XML Professional Publisher > XPP > Administrative Tools, and then in XyAdmin, File > Document Paths. • S.A. r, w, x, d is SPECIAL ACCESS: read, write, execute, delete.
SDL XPP Installation and Upgrade Guide for Windows Establishing Secure Access (Optional) A-5 XPP and Security
Share Permissions Setting the permissions above must be done on the local file systems where the specific XPP trees physically reside. It is entirely possible to have xz, sd_liz and %XYV_JOB% all living on different machines, so be sure you set the permissions on the machine where the tree lives. As for sharing these directories so XPP clients can access them, there is not much to worry about once the local file system permissions have been assigned. When local permissions and share permissions are consulted by Windows, the most restrictive wins. So, you can share the XPP trees with full control for everyone provided that the correct local file system permissions have been applied.
A-6 Establishing Secure Access (Optional) SDL XPP Installation and Upgrade Guide for Windows Appendix B Troubleshooting
Troubleshooting
Problem Area Description/Solution
General Having two identical logins—one defined for your PC and one defined for a domain—can cause some XPP functionality to fail, for example, the save/restore function considers this configuration as being two different users.
Installation You may encounter error messages if you write to a temporary folder using remote access. Remote access software sometimes points to a folder that is not writable or no longer exists. Check the XYV_TMPS path variable. You may need to provide the full path when writing to temp files.
When installing the Reprise License Manager, you may encounter the error message “Installer User Interface Mode Not Supported” and the Reprise installation will fail. This may be due to your admin login user name containing special characters (for example, “!”).
Fonts You may add “Windows fonts” but do not check ‘‘Plotter Fonts.’’ Doing so causes memory to run away if you try to edit a Color spec. You can select everything else and set the size range from 4 to 186 points.
If you run setup and add 100 dpi fonts (done after normal XPP install, including MKS X/Server install component), when you upgrade XPP and include MKS X/Server to be installed again, it will delete your 100 dpi fonts. You will have to redo setup again and reinstall them.
Keyboard mapping Select a key you do not use to map “Print.” It is recommended that you use the Left‐Alt key for PI/PI# characters; MKS X/Server does not let you map it to the Right‐Alt key.
SDL XPP Installation and Upgrade Guide for Windows Troubleshooting B-1 Troubleshooting
Problem Area Description/Solution
Network Protocols Use the Remove buttons to delete any unnecessary protocols. Having a protocol, such as netBEUI, on your server or workstation results in every network call being broadcast to all machines on the network. Windows notifies you that you must restart your computer before the Bindings settings take effect. You have the option to restart your computer at this time, or later.
Third‐party software If XPP or third‐party products do not function properly, check the PATH variable. On occasion, multiple installations truncate the PATH variable. The XPP installation backs up PATH before beginning an upgrade or install. The installation program writes the backup to %XYV_TMPS%\PrevPath.txt. See also, Third‐party Upgrades on page B‐4
Unable to open a division Check the MKS Toolkit settings (see Activating Your X after installing XPP. Server For XPP on page 6‐1).
Unable to open a division by If enabled, firewall settings require an exception for an double‐clicking (or right‐ outbound rule to allow Ports 5053 and 5054 access: clicking and choosing Open Outbound rule from the pop‐up menu) after installing XPP. TCP On the Domain Local Port (all ports) Remote Port 5053, 5054 Check the firewall settings (see Changing the Port Number on page C‐1).
Get the following error When attempting to run XPP, you may encounter this message: Bad server error message as the XPP application fails. This may be hostname in license file or due to either an incorrect hostname in the license file, or if port@host an sdlxysoft_LICENSE environment variable exists, an incorrectly entered hostname in this environment variable.
Softpad key is not working Check the NumLock Management settings (see properly. Activating Your X Server For XPP on page 6‐1).
Get the following error Check TCP‐Unix Availability (see Activating Your X message: PROFILE IS Server For XPP on page 6‐1). ALREADY RUNNING
MKS X/Server does not Check MKS X/Server Profiles settings (see Activating launch when you try to open Your X Server For XPP on page 6‐1). a division.
B-2 Troubleshooting SDL XPP Installation and Upgrade Guide for Windows MKS X/Server Creates Excessive Network Traffic
Problem Area Description/Solution
Users are denied access to Network problems may be causing XPP to deny access to XyAdmin or are denied edit some operations (see XPP Security Lock‐Down Mode access to style specs or jobs. on page A‐4).
MKS X/Server Creates Excessive Network Traffic
MKS X/Server installs with a broadcast mode to locate other hosts on the network. This can cause excessive network traffic even when XPP is not running. You may want to turn off broadcast mode. 1. Click Start > Programs > MKS XServer > Configuration > MKS XServer Configuration. 2. Under Edit Settings, click Services > Configuration Window. 3. On the Host Finder tab, uncheck Vision Hosts, XDM Hosts, and Modem in the Host types section. 4. Uncheck Enabled in the Startup Settings section. 5. Click Apply, then click OK. Bringing Forms to the Foreground
In some cases, when using drop‐down boxes to fill out forms, the form goes to the background and XPP is unable to execute the task. This is an Exceed problem. 1. Click Start > Programs > OpenText Xceed 14 > Exceed Tools > Xconfig. 2. Click Screen Definition under Pick a Task in Classic View. 3. On the Advanced Settings tab, check On Focus Raise Window to Top at the bottom of the Native Window Manager pane. 4. Click Validate and Apply Changes in the Common Activities box. 5. Click Yes to close all X Server applications and restart the server.
SDL XPP Installation and Upgrade Guide for Windows Troubleshooting B-3 Third-party Upgrades
Third-party Upgrades
If a third‐party application failed to upgrade, do the following:
First Attempt 1. Rerun XPP install 2. Select Third‐party Products only 3. Select the product(s) that failed to upgrade 4. Execute the upgrades If this attempt is successful, your upgrade is complete. Second Attempt 1. Uninstall the offending 3rd‐party application(s) 2. Rerun XPP install 3. Select Third‐party Products only 4. Select the product(s) that failed to upgrade 5. Execute the upgrades Because this results in a new install of the third‐party application(s), you will need to perform the appropriate configuration steps for each: • MKS Toolkit: See Activating Your X Server For XPP on page 6‐1. • MKS X/Server: Configuring MKS X/Server on page 6‐1.
B-4 Troubleshooting SDL XPP Installation and Upgrade Guide for Windows Appendix C Licensing Across a Firewall
This appendix explains how to change the port number in the license file on the XPP server. 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 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. [drive]:\Program Files\XyEnterprise\SDL_License or [drive]:\Program Files (x86)\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 sdlxysoft server).
SDL XPP Installation and Upgrade Guide for Windows Licensing Across a Firewall C-1 Changing the Port Number
5. Restart the license manager. Use the service control panel to stop and restart the license server. For example, on Windows Server 2008 click Start > Administrative Tools > Services. The Service name is SDL_License.
C-2 Licensing Across a Firewall SDL XPP Installation and Upgrade Guide for Windows
SDL Group 201 Edgewater Drive Wakefield, MA 01880‐6216