Professional Documents
Culture Documents
Installation Guide
Release 6.2
1999-2007 Interwoven, Inc. All rights reserved. No part of this publication (hardcopy or electronic form) may be reproduced or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Interwoven. Information in this manual is furnished under license by Interwoven, Inc. and may only be used in accordance with the terms of the license agreement. If this software or documentation directs you to copy materials, you must first have permission from the copyright owner of the materials to avoid violating the law which could result in damages or other remedies. Interwoven, ConfirmSite, ContentServices, ControlHub, DataDeploy, DeskSite, FileSite, iManage, LiveSite, MediaBin, MetaCode, MetaTagger, OffSite, OpenDeploy, Primera, Scrittura, TeamPortal, TeamSite, VisualAnnotate, WorkDocs, WorkPortal, WorkRoute, WorkSite, WorkTeam, the respective taglines, logos and service marks are trademarks of Interwoven, Inc., which may be registered in certain jurisdictions. All other trademarks are owned by their respective owners. Some or all of the information contained herein may be protected by patent numbers: US # 6,505,212, GBRI # 1053523, US # 6,480,944, US# 5,845,270, US #5,430,812, US #5,754,704, US #5,347,600, AUS #735365, AU 7830068, GB #GB2333619, US #5,845,067, US #6,675,299, US #5,835,037, AUS #632333, CAN #2,062,965, FRAN / GRBI / SPAI / SWED #480941, GERM #69020564.3, KORS 10-0576487, JAPA #2968582, MX #219522, NZ #516340, SING #109524, SG #89006, SG #89086, SG #74973, SG #85502 US #5,065,447, US #6,609,184, US #6,141,017, US #5,990,950, US #5,821,999, US #5,805,217, US #5,838,832, US #5,867,221, US #5,923,376, US #6,434,273, US #5,867,603, US #4,941,193, US #5,822,721, US #5,923,785, US #5,982,938, US #5,790,131, US #5,721,543, US #5,982,441, US #5,857,036, US #6,697,532, US #6,792, 454, US #6,928,149, US #7,092,969 or other patents pending application for Interwoven, Inc.
Interwoven, Inc. 160 East Tasman Drive San Jose, CA 95134 http://www.interwoven.com OpenDeploy Installation Guide Part 03-003-02-EN November 2007
Table of Contents
List of Figures About This Book 5 7
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Notation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Chapter 1:
Preparation
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 OpenDeploy Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Base and Receiver Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Administration Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Reporting Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 ContentServices Foundation Access Service Software . . . . . . . . . . . . . . . . . . . .12 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Base Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Administration Package Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Administration and Reporting Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 ContentServices Foundation Access Service . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 RMI Registry Service Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Enabling DOS-Compatible 8.3 Format File Names for Windows . . . . . . . . . . . .16
Chapter 2:
Installation
19
Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Installing the Base Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Installing the Receiver Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Installing the Administration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Installing the ContentServices Access Service. . . . . . . . . . . . . . . . . . . . . . . . . . .24 Configuring the Bootstrap Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Installing the Base Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Installing the Receiver Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Installing the Administration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 Installing the ContentServices Foundation Access Service . . . . . . . . . . . . . . . . .28 Configuring the Bootstrap Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Platform-Specific Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Upgrading OpenDeploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 Upgrading From a Previous Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 Administration Package Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Operations Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Updating OpenDeploy Home Value in Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Installing Multiple Releases of OpenDeploy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Installation Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Configuring OpenDeploy Home Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Uninstalling OpenDeploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Contents
Chapter 3:
Licensing
39
Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Base Server Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Receiver Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Administration Package LIcensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Add-On Module Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Licensing Hosts with Multiple Host Names and Interfaces . . . . . . . . . . . . . . . . .41 Licensing Cluster Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Licensing OpenDeploy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Single License Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Batch Server Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Remote Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Suggested Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Upgrade Installation File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Specifying Shortened Upgrade File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Distributing the Target Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Collecting License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Distributing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Upgrading from OpenDeploy 5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 Performing Remote Upgrades on UNIX Target Hosts as a Non-Root User . . . . .58 Expired License Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Chapter 4:
Remote Upgrades
61
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Suggested Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Preparation for Remote Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Upgrade Installation File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Specifying Shortened Upgrade File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64 Distributing the Target Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Monitoring the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Collecting License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Configuring a New License Identification Deployment . . . . . . . . . . . . . . . . . . . .70 Distributing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Configuring a New License Distribution Deployment . . . . . . . . . . . . . . . . . . . . .72 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 Upgrading from OpenDeploy 5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 Reboot Required After Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73 Remote Upgrade Configuration File Location for OpenDeploy 5.6 Targets . . . .73 Remote Upgrades on UNIX Target Hosts as a Non-Root User . . . . . . . . . . . . . . . . .74
Index
77
Interwoven, Inc.
List of Figures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Base Server Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Administration Package Installation Program . . . . . . . . . . . . . . . . . . . . . .23 ContentServices Foundation Installation Program . . . . . . . . . . . . . . . . . . .24 Remote Upgrade Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Remote Upgrade Window Software Distribution Configurations . . . . .50 Remote Upgrade Window Software Distribution Configurations (cont.) . 50 Remote Upgrade Window Software Distribution Configurations (cont.) . 51 Start Deployment Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Remote Upgrade Window License Identification Configurations . . . . .53 Remote Upgrade Window License Identification Configurations . . . . .54 License Distribution Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 License Distribution Windows for New Configurations . . . . . . . . . . . . . .56 Remote Upgrade Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Remote Upgrade Window Software Distribution Configurations . . . . .65 Remote Upgrade Window Software Distribution Configurations (cont.) . 66 Remote Upgrade Window Software Distribution Configurations (cont.) . 67 Start Deployment Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Remote Upgrade Window License Identification Configurations . . . . .69 Remote Upgrade Window License Identification Configurations . . . . .70 License Distribution Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 License Distribution Windows for New Configurations . . . . . . . . . . . . . .72
List of Figures
Interwoven, Inc.
Intended Audience
This manual is for those tasked with installing and configuring OpenDeploy software. If you are using OpenDeploy in conjunction with TeamSite , you should also know TeamSite functionality and terminology. Many of the operations described in this manual require root or Administrator access to the OpenDeploy server host. If you do not have root or Administrator access to the OpenDeploy server host, consult your system administrator.
This manual uses the term Windows to indicate any supported version of the Microsoft Windows operating system, such as Windows NT or Windows 2000.
This manual uses the term UNIX to indicate any supported flavor of the UNIX operating system.
Windows: Users should be familiar with either IIS or Netscape Web servers, and with basic Windows server operations such as adding users and modifying Access Control Lists (ACLs). UNIX: Users of this manual should be familiar with basic UNIX commands and be able to use an editor such as emacs or vi. It is also helpful to be familiar with regular expression syntax. If you are not familiar with regular expressions, consult a reference manual such as Mastering Regular Expressions by Jeffrey Friedl.
Notation Conventions
This manual uses the following notation conventions: Table 1 Bold Notation Conventions
Definition and Usage
Convention
Text that appears in a GUI element such as, a menu item, button, or element of a dialog box, and command names are shown in bold. For example: Click Edit File in the Button Bar. Book titles appear in italics. Terms are italicized the first time they are introduced. Important information may be italicized for emphasis. Commands, command-line output, and file names are in monospace type. For example: The iwextattr command-line tool allows you to set and look up extended attributes on a file. Monospaced italics are used for command-line variables.For example:
iwckrole role user
Italic
Monospace
Monospaced italic
This means that you must replace role and user with your values.
Monospaced bold
Monospaced bold represents information you enter in response to system prompts. The character that appears before a line of user input represents the command prompt, and should not be typed. For example:
iwextattr -s project=proj1 //IWSERVER/default/main/dev/WORKAREA/andre/products/ind ex.html
Monospaced bold italic text is used to indicate a variable in user input. For example:
iwextattr -s project=projectname workareavpath
means that you must insert the values of projectname and workareavpath when you enter this command.
[] |
Square brackets surrounding a command-line argument mean that the argument is optional. Vertical bars separating command-line arguments mean that only one of the arguments can be used.
This guide also uses the following conventions: The term Windows indicates any supported version of the Microsoft Windows operating system, such as Windows NT or Windows 2000.
Directory paths use UNIX conventions. These conventions mandate using forward slashes (/) in path names. (Windows systems use backward slashes.) The Windows convention is used when referring to a Windows-specific directory. For example:
UNIX: docroot/news/front.html Windows: docroot\news\front.html
Interwoven, Inc.
Chapter 1
Preparation
This chapter describes the installed components of the OpenDeploy software, and provides information to help you install your software successfully.
System Requirements
Refer to the OpenDeploy Release Notes for the latest information on the following installation-related topics: Supported operating systems Localized operating system support RAM requirements Storage requirements Patch requirements Supported browsers Certified reporting server databases Compatibility between OpenDeploy releases Compatibility between OpenDeploy and other Interwoven products Supplemental information regarding installation on particular operating systems
Chapter 1: Preparation
Interwoven, Inc.
10
Chapter 1: Preparation
However, you can select another parent directory if you want. On UNIX, you must select the parent directory. The following locations are typical home directories for the base server or receiver software: Windows - C:\Interwoven\OpenDeployNG UNIX - /usr/Interwoven/OpenDeployNG The base server or receiver home directory is indicated in this manual by the term:
od-home
However, you can select another parent directory if you want. On UNIX, you must select the parent directory. The following locations are typical home directories for the administration server software: Windows - C:\Interwoven\AdminServer UNIX - /usr/Interwoven/AdminServer The administration server home directory is indicated in this manual by the term:
admin-home
Tomcat Server
One component of the administration server is the Tomcat server. The Tomcat server helps manage and generate the OpenDeploy user interface. OpenDeploy installs and uses its own Tomcat server, even if other Tomcat server software resides on your OpenDeploy server host.
11
Chapter 1: Preparation
However, you can select another parent directory if you want. On UNIX, you must select the parent directory. The following locations are typical home directories for the administration server software: Windows - C:\Interwoven\CSF UNIX - /usr/Interwoven/CSF The administration server home directory is indicated in this manual by the term:
csf-home
Interwoven, Inc.
12
Chapter 1: Preparation
Installation Prerequisites
The following sections describe the information and decisions you must provide for each software component installation. Refer to the OpenDeploy Release Notes for any additional installation-related information, such as those for installation on a specific operating system.
Base Server
Installation of the base server software includes the following tasks: Accepting the license agreement. Specifying where the base server software is to be installed. You can accept the default installation location or specify your own. Specifying the port number for RMI registry service. The default port number is 9173. To avoid conflicts with the RMI registry service, it is strongly recommended that you do not include non-Interwoven applications that might need to use these ports in your OpenDeploy environment. Specifying the listening port number for incoming deployments. The default port number is 20014. Whether to enable or disable the reporting feature. The default setting is enabled. Select the platform (Windows or UNIX) of the bootstrap user. The bootstrap user is the first user to access your OpenDeploy server from the browser-based user interface. Using the bootstrap administrator, you can subsequently create other users with access to your server. Indicating the user name and domain (Windows only) assigned to the bootstrap administrator. By default, the following values listed as bootstrap users: Windows - hostname\Administrator UNIX - root Any additional user name and domain you enter will be added as the bootstrap administrator to the service configuration file (deploy.cfg) of the OpenDeploy server.
13
Chapter 1: Preparation
License Types
When you first install the base server software, you have full usage of its features and functionality for 30 days. However, after that time you must provide the appropriate license to use it further. You can provide one of the following license types: Full - the full-featured version with no time limit. EasyDeploy - a restricted-feature version you can use with no time limit. EasyDeploy is sometimes included as part of other Interwoven products. EasyDeploy does not support the following OpenDeploy features and functionality: Fan-out deployment Multi-tiered deployment Secure data transfer Multiple base server instances on one host Use of delivery adapters Use of payload adapters See Chapter 3, Licensing for more information on licensing your base server.
Receiver
Installation of the receiver software includes the following tasks: Accepting the license agreement. Specifying where the receiver software is to be installed. You can accept the default installation location or specify your own. Specifying the port number for RMI registry service. The default port number is 9173. To avoid conflicts with the RMI registry service, it is strongly recommended that you do not include non-Interwoven applications that might need to use these ports in your OpenDeploy environment. Specifying the port number for incoming deployments. The default port number is 20014. Whether to enable or disable the reporting feature. The default setting is disabled. Indicating the user name and domain (Windows only) assigned to the bootstrap administrator. This user and domain will be added as the bootstrap administrator to the service configuration file (deploy.cfg) of the OpenDeploy server.The bootstrap user is the first user to access your OpenDeploy server from the browser-based user interface. Using the bootstrap administrator, you can subsequently create other users with access to your server. (Windows only) Specifying the location for the TMP system environmental variable.
Interwoven, Inc.
14
Chapter 1: Preparation
15
Chapter 1: Preparation
and click OK. The Registry Editor window is displayed. 3. Navigate to the following directory path in the Registry Editor window:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
The following item appears under the Name column as part of the contents of the FileSystem folder on the right pane of the Registry Editor window:
NtfsDisable8Dot3NameCreation
If DOS-compatible 8.3 format file names support is enabled, the corresponding value is displayed under the Data column:
0x00000000 (0)
Interwoven, Inc.
16
Chapter 1: Preparation
No further modification is required, and you can close the Registry Editor window. If DOS-compatible 8.3 format filenames support is disabled, this value is displayed as:
0x00000001 (1)
You must continue with the following steps to enable the DOS-compatible 8.3 format file names. 4. Highlight the NtfsDisable8Dot3NameCreation entry, and select Edit > Modify to open the Edit DWORD Value window. 5. Change the value from 1 to 0 in the Value data box and click the OK. This enables the feature, which is indicated by the corresponding Data column value in the Registry Editor window being displayed as:
0x00000000 (0)
No further modification is necessary, and you can close the Registry Editor window.
17
Chapter 1: Preparation
Interwoven, Inc.
18
Chapter 2
Installation
This chapter describes the installation procedure for your OpenDeploy software. Install the appropriate components, one at a time, on the servers making up your OpenDeploy environment. See OpenDeploy Software Components on page 10 to determine the requirements for each component. Check the OpenDeploy Release Notes for any additional information regarding installing your OpenDeploy software before going any further.
Windows
Installation of OpenDeploy on a Windows host requires the following tasks: Ensuring the DOS-compatible 8.3 format file names feature is enabled, and if necessary, enabling it yourself. See Enabling DOS-Compatible 8.3 Format File Names for Windows on page 16 for more information. Installation of the base server or receiver software Installation of the administration package, which include the administration server and reporting server software pieces. You must have Administrator privileges to install OpenDeploy on your Windows server. Close all other open applications before installing OpenDeploy software on your Windows server. You must close the Services window (not just minimize it) prior to installing OpenDeploy on a Windows host. Otherwise, the Windows registry keys will not get updated properly.
19
Chapter 2: Installation
where xxxx indicates the product release number and yyyyy indicates the build number of the final shipping product. 2. Double-click the installation file to start the installation program to start the installation program (Figure 1): Figure 1 Base Server Installation Program
3. Click Next to continue. 4. Read the license agreement and click Yes to accept its conditions. Clicking No quits the installation program. 5. Select the parent directory where the base server software will be installed and click Next. The default location is:
C:\Interwoven
Upon installation, the base server software will reside in the following location:
parent-dir\OpenDeployNG
6. Enter the port number for the RMI registry in the Registry box. The default value is 9173. 7. Enter the listening port number for incoming deployment in the Deploy box. The default value is 20014. Click Next to continue.
Interwoven, Inc.
20
Chapter 2: Installation
8. Click Enable (default) or Disable to indicate whether or not you want your base server to broadcast event reporting. Click Next to continue. If you selected Enable, go to the next step. Otherwise, skip to step 11. 9. Enter the TCP port number for event reporting in the TCP Port box. The default value is 9171. 10. Enter the JNDI port number for event reporting in the JNDI Port box. The default value is 9172. Click Next to continue. 11. Click Windows or UNIX to indicate whether the host is a Windows or UNIX operating system. This step is required to determine the format of the bootstrap administrator. Click Next to continue. The Bootstrap User Information window is displayed. The bootstrap administrator is a user account that can access the browser-based user interface (through the administration server) initially after installation. Depending on which operating system you chose, the following default bootstrap administrator user values are displayed: Windows: Name: Administrator Domain: host_name UNIX: Name: root If you want to specify another bootstrap administration user in addition to the default one displayed, proceed to the next step. If you want to use the default bootstrap administrator listed, click Next to continue and skip the next step. 12. (If you are specifying your own bootstrap administrator user) Enter the bootstrap name in the Name box, and (if necessary) domain to which it belongs in the Domain box. Click Next to continue. 13. Verify the settings you want in the Summary Report window and click Next. The base server installer program installs the base server on your host. If you accepted the default installation locations, the installed software resides in the following location:
C:\Interwoven\OpenDeployNG
21
Chapter 2: Installation
where xxxx indicates the product release number and yyyyy indicates the build number of the final shipping product, to start the installation program. Follow the installation instructions described in Installing the Base Server Software on page 20 to install the receiver software. You cannot install the receiver software on a host that already has base server software installed.
where xxxx indicates the product release number and yyyyy indicates the build number of the final shipping product.
Interwoven, Inc.
22
Chapter 2: Installation
2. Double-click the installation file to start the installation program (Figure 2). Figure 2 Administration Package Installation Program
3. Click Next to continue. 4. Read the license agreement and click Yes to accept its conditions. Clicking No quits the installation program. 5. Select the parent location where the administration server and reporting server software will be installed and click Next. The default location is:
C:\Interwoven
You can also click Browse and navigate to another location. Upon installation, the administration and reporting server software will reside in the following location:
parent-dir\AdminServer
6. Enter the port number for the administration server and click Next. The default port number is 8081. 7. Verify the settings you want in the Summary Report window and click Next. The administration package installer program installs the administration server and reporting server on your host. If you accepted the default installation locations, the installed software resides in the following location:
C:\Interwoven\AdminServer
When the administration and reporting servers have been installed, the ContentServices Foundation (CSF) installer automatically begins. The following section describes the installation of the CSF access service.
23
Chapter 2: Installation
1. Read the license agreement and click the option to accept its conditions. Click Next to continue. 2. Select the parent location where the ContentServices Foundation software will be installed and click Next. This path cannot contain any multi-byte characters. The default location is:
C:\Interwoven
Upon installation, the ContentServices Foundation software will reside in the following location:
parent-dir\CSF
3. Enter the appropriate port number in the AccessService HTTP port number box. The default port number is 12973. If you specify a non-default port number, you must perform additional configuration. See Using a Non-Default CSF Port on page 16 for more information. 4. Enter the appropriate resolvable host name or IP address in the Access Service HTTP hostname or IP address box. The default value is the name of the host on which the CSF software is being installed. Click Next to continue. A new window appear summarizing the settings you specified for the installation. 5. Click Install to proceed with the installation. When the installation is completed, restart the host. The ContentServices Foundation access service will start automatically. If you accepted the default installation locations, the installed software resides in the following location:
C:\Interwoven\CSF
Interwoven, Inc.
24
Chapter 2: Installation
UNIX
You must have root privileges to install OpenDeploy on your UNIX server.
where xxxx indicates the product release number, yyyyy indicates the build number of the final shipping product, and UNIX_OS indicates the particular UNIX platform. 2. Use one of the following methods to unzip and untar the base server installation file: Unzip the installation file by entering the following command at the prompt (use the installation file appropriate for your base server version):
gzip -d IWOVopendeployBaseFull.6.x.x.x.x.Buildyyyyy. UNIX_OS.tar.gz
Next, untar the installation file by entering the following command at the prompt (use the installation file appropriate for your base server version):
tar -xvf IWOVopendeployBaseFull.6.x.x.x.x.yyyyy.UNIX_OS.tar
25
Chapter 2: Installation
Unzip and untar the installation file by entering the following command at the prompt (use the installation file appropriate for your base server version):
gzip -c -d IWOVopendeployBaseFull..6.x.x.x.x.Buildyyyyy. UNIX_OS.tar.gz | tar -xvpf -
directory (for the full version of the base server software) file file
ODNG_base_full.tar
file
file
3. Start the installation script by entering the following command at the prompt:
./startinstall_od
Ensure you are in your installation working directory before running this command. 4. Accept the licensing agreement by pressing Enter. 5. Enter the location where the base server software will be installed, for example /usr. 6. Enter a port number for the RMI registry. The default value is 9173. 7. Enter the name for the default scheduler database. The default name is schedDB. 8. Enter a listening port number for incoming deployment. The default value is 20014. 9. Indicate whether (y) or not (n) you want to enable your base server to broadcast event reporting. 10. (If event reporting is enabled) Enter a TCP port for event reporting. The default value is 9171. 11. (If event reporting is enabled) Enter a JNDI port for event reporting. The default value is 9172. 12. Indicate whether or not you want to add a bootstrap administrator user in addition to the default bootstrap administrator root. The bootstrap administrator is a user account that can access the browser-based user interface (through the administration server) immediately after installation. 13. (If you are adding an additional bootstrap administrator user) indicate whether the host platform is Windows (1) or UNIX (2). 14. (If you are adding an additional bootstrap administrator user) Enter the additional bootstrap administrator user name. If the host platform is Windows, you must also add the domain. The base server installer now installs the software on your host in the following location:
/parent_dir/OpenDeployNG
where parent_dir is the location you selected for the software installation.When you have completed the installation, delete the installation file to save room on your server.
Interwoven, Inc.
26
Chapter 2: Installation
where xxxx indicates the product release number, yyyyy indicates the build number of the final shipping product, and UNIX_OS indicates the particular UNIX platform. Follow the installation instructions described in Installing the Base Server Software on page 25 to install the receiver software. You cannot install the receiver software on a host that already has base server software installed.
where xxxx indicates the product release number and yyyyy indicates the build number of the final shipping product and UNIX_OS indicates the particular UNIX platform. 2. Use one of the following methods to unzip and untar the installation file: Unzip the installation file by entering the following command at the prompt:
gzip -d IWOVopendeployAdmin.6.x.x.x.x.Buildyyyyy.UNIX_OS.tar.gz
Next, untar the installation file by entering the following command at the prompt:
tar -xvf IWOVopendeployAdmin.6.x.x.x.x.Buildyyyyy.UNIX_OS.tar
Unzip and untar the installation file by entering the following command at the prompt:
gzip -c -d IWOVopendeployAdmin.6.x.x.x.x.Buildyyyyy. UNIX_OS.tar.gz | tar -xvpf -
IWOVadmin.tar
README_ADMINSERVER
27
Chapter 2: Installation
OpenDeploy_admin_pkg_license.txt startinstall_admin
file
file
3. Start the installation script by entering the following command at the prompt:
./startinstall_admin
Ensure you are in your installation working directory before running this command. 4. Accept the licensing agreement by pressing Enter. 5. Enter the location where the administration server and reporting server software will be installed, for example /usr. 6. Enter the port number for the administration server. The default port number is 8081. The administration package installer program now installs the administration server and reporting server on your host in the following location:
/parent_dir/AdminServer
where parent_dir is the location you selected for the software installation.When you have completed the installation, delete the installation file to save room on your server. After you have installed all the base server or receiver software, as well as any other OpenDeploy components, you must configure your bootstrap administrator before restarting the host. Refer to Configuring the Bootstrap Administrator on page 117 in the OpenDeploy Administration Guide for more information. When the administration and reporting servers have been installed, the ContentServices Foundation (CSF) installer automatically begins. The following section describes the installation of the CSF access service.
Interwoven, Inc.
28
Chapter 2: Installation
4. Accept the default port number, 12973, or enter an alternative after the Access Service HTTP port number prompt. Then press Enter. If you specify a non-default port number, you must perform additional configuration. See Using a Non-Default CSF Port on page 16 for more information. 5. Accept the default host name, the name of the host the software is being installed on, or enter an alternative after the Web Services HTTP hostname or IP address prompt. Then press Enter. 6. Press Enter to proceed with the installation. After you have installed the ContentServices Foundation, you can configure it. Refer to ContentServices Foundation Developer Guide for more information.
29
Chapter 2: Installation
Upgrading OpenDeploy
The following sections describe upgrading from a previous release of OpenDeploy to the current release. In addition to the upgrade methods described here, you can also use the remote upgrade feature to update multiple OpenDeploy base server and receivers to OpenDeploy 6.1 and later simultaneously. See Remote Upgrades on page 46 for more information.
Interwoven, Inc.
30
Chapter 2: Installation
If you are installing the administration package, it will prompt you to either upgrade or exit. You cannot install a new administration package alongside a legacy release of the same component. Upgrading the administration server requires manual updating of the reporting database. See Administration Package Upgrades on page 32 for more information. When you choose to upgrade, the installer program automatically uninstalls the old software and installs the current version. The new installation automatically uses your existing port settings and other configurations. For new features, you are prompted to input the required information.
NOTE
Upgrading to the current version of OpenDeploy on Windows requires that the Windows host be rebooted.
31
Chapter 2: Installation
where MYDATABASEDEPLOYPORT is the internal port used by the OpenDeploy base server or receiver for database deployment support. 3. Save and close your OpenDeploy server configuration file.
Interwoven, Inc.
32
Chapter 2: Installation
Operations Server
If you are upgrading from a previous release of OpenDeploy that used the operations server, that software is no longer needed with this release. After upgrading the OpenDeploy administration package, you should uninstall the operations server software.
The uninstallation script removes the entire directory. You must save any log and configuration files you want to preserve to another location prior to uninstalling the software.
33
Chapter 2: Installation
UNIX - the home file was /etc/defaultiwodhome This change is to allow you to have both the current release of OpenDeploy, and one of the supported legacy releases, for example release 5.6, installed on the same host. If you have scripts that use the previous OpenDeploy home directory variable, you must modify them to apply to the current release. Future releases of OpenDeploy are expected to have their release numbers incorporated into the home value in the same manner as this release. Therefore, you should configure your scripts in such a manner that you are not required to manually update them to the next OpenDeploy release when you upgrade. For example: Windows - set the IWODHOME system environment variable to equal the IWOD60HOME system environment variable. UNIX: Configure a well known wrapper to point to /etc/defaultiwod60home. Program your scripts to look for the wrapper instead of /etc/defaultiwod60home. If you upgrade from this release to a later one, you only need to change the wrapper instead of your custom scripts. Create a symbolic link from /etc/defaultiwodhome to /etc/defaultiwod60home or any future release. Following the above techniques will not allow you to reuse the same scripts against all the co-existing release versions. You can only use the scripts against the designated OpenDeploy version.
Interwoven, Inc.
34
Chapter 2: Installation
Refer to Running Multiple Releases of OpenDeploy on page 30 in the OpenDeploy Release Notes for those supported legacy releases, and any other specific information. If you are installing the current base server or receiver on a host that already contains an OpenDeploy 5.x release of the same software component, the installer may ask you whether you want to install this release of OpenDeploy as an upgrade to your existing software, or whether you want to install it in addition to your existing software. You should indicate that you want to install it in addition to the your existing software.
Installation Order
If you are performing fresh installations of the current base server or receiver software, as well as the supported legacy release, you must install the software in the following order: Install the legacy OpenDeploy release. Install the latest legacy OpenDeploy service pack release. Install the current release. Install the latest current OpenDeploy service pack release (if available).
This is a change from previous OpenDeploy releases where you could reference the OpenDeploy home directory simply as iwodhome, for example: Windows - the system environment variable is IWOD60HOME UNIX - the home file is /etc/defaultiwod60home See Updating OpenDeploy Home Value in Scripts on page 33 for suggestions on managing changes in the OpenDeploy releases home value.
Uninstalling OpenDeploy
Uninstall OpenDeploy software components one at a time, similar to the way you installed them. In some cases you will want to remove all of the components on a server. In other cases you might only want to remove some components, such as if you have a single-host installation of all the components on a single server and you want to spread them out over several servers. Uninstallation of OpenDeploy software varies depending on the server platform.
35
Chapter 2: Installation
Windows
You must have Administrator privileges to uninstall OpenDeploy software on a Windows host. To uninstall each OpenDeploy software component, you must perform the following tasks in order: Stop the OpenDeploy service for each corresponding software component. Uninstall the software component itself, using the Windows Add/Remove Programs tool. Remove any remaining files and directories as necessary. Even after uninstallation, OpenDeploy leaves some legacy files and directories, such as od-home/conf. This allows you to retain files such as customized configuration files that you might want to maintain even if you decide to reinstall OpenDeploy.
Interwoven, Inc.
36
Chapter 2: Installation
4. Repeat this procedure for the remaining OpenDeploy software components you want to remove. Follow the order listed in step 2. Certain files and directories remain on your server after the uninstallation, such as log files and configuration files. This allows you to keep a record of your OpenDeploy activities even after the software is removed. If you want to remove these files as well, you can manually delete them from within the Windows Explorer.
UNIX
You must be root to uninstall OpenDeploy software on a UNIX host. To uninstall each OpenDeploy software component, you must perform the following tasks in order: Stop the OpenDeploy daemon for each corresponding software component. Uninstall each software component using the uninstallation script provided for that component. The uninstallation script removes the entire directory. You must save any log and configuration files you want to preserve to another location prior to uninstalling the software. The following sections describe the uninstallation of each software component.
37
Chapter 2: Installation
Interwoven, Inc.
38
Chapter 3
Licensing
This chapter describes the licensing requirements for OpenDeploy software. It also describes the process of obtaining and installing the required license keys. Software activation of base servers and receivers is required for OpenDeploy 6.1 and later. Earlier software does not require activation. The software activation process requires that you purchase a license entitlement for each OpenDeploy base server, receiver, and add-on module. If you have servers in excess of your license entitlement, you must license those additional servers separately. Contact your OpenDeploy sales representative for further information on purchasing the necessary licenses for your OpenDeploy software. After you install your OpenDeploy software, you must obtain a license key file from the Interwoven support site for each OpenDeploy base server and receiver, and subsequently deploy or manually place these files in each installation. You have the option of requesting from the Interwoven support site a single OpenDeploy license key for a particular server in your environment, or obtaining a batch set of license keys for a group of OpenDeploy server.
39
Chapter 3: Licensing
Licensing Requirements
You must perform the necessary software activation following installation of each OpenDeploy base server and receivers on their respective hosts.
Receiver Licensing
You must license and activate each OpenDeploy receiver installation. An expired receiver will only accept incoming license deployments.
Interwoven, Inc.
40
Chapter 3: Licensing
These modules do not have separate license files. Instead, the appropriate add-on module licenses are incorporated into your base server license. When you go to the Interwoven Support Web site to request your base server license, you will be prompted to indicate which add-on modules you have purchased. If you select any modules that you have not purchased, your base server license will still activate that module. An Interwoven sales representative will contact you at a later date to purchase the necessary module license.
Licensing OpenDeploy
You can license OpenDeploy base servers and receivers using one of the following methods: Single license activation - a license for a single OpenDeploy server is requested. Required information is provided manually, and the generated license is manually placed in the server host. Batch license activation - licenses for multiple OpenDeploy servers are requested. License deployments are used to collect the required information, and to distribute the generated licenses to their corresponding targets.
41
Chapter 3: Licensing
The OpenDeploy single license generator page has a link on the Support sites main page. 2. Provide the information required on the page and submit your request. Some of this information can be obtained by following the instructions described in Obtaining Host Information on page 43. You will subsequently be sent an e-mail with the OD.lic license file attached.
NOTE
You should provide the primary host name of the OpenDeploy servers host. IP addresses are not supported. 3. Place the OD.lic license file in the following location:
od-home/etc
Interwoven, Inc.
42
Chapter 3: Licensing
This information also is written to the file whose name and path you specified as the output-file variable.
NOTE
Obtaining the host name and domain is not necessary if you are performing a batch license activation. This information is obtained automatically.
43
Chapter 3: Licensing
3. Open licidentification.xml using your favorite text or XML editor, and update its replication farm to include the appropriate targets. 4. Save the updated licidentification.xml file using a different unique name. Your original licidentification.xml file should remain unchanged so you can use it as the basis for future license identification deployments. 5. Run the license identification deployment, either from the browser-based user interface, or from the command line. The information collected is written to file odlicreq_datetimestamp.zip residing on the following location of the host running the deployment:
od-home/install/batch/req
Only those targets listed in the updated replication farm (see step 3) will have their information written to the file. So ensure that each OpenDeploy server requiring activation is included in replicationFarm element in the deployment configuration. Refer to Target Replication Farms on page 27 in the OpenDeploy Deployment Configuration Guide fore more information. 6. Access the OpenDeploy batch license generator page from the Interwoven Support site:
http://support.interwoven.com
The OpenDeploy batch license generator page has a link on the Support sites main page. Follow the instructions on the OpenDeploy batch license generator page for uploading the generated .zip file to the Interwoven Support Web site.
odbatchlic.zip,
You will subsequently receive an email from Interwoven containing the file which contains the bundled set of license files required for activating your OpenDeploy servers.
Interwoven, Inc.
44
Chapter 3: Licensing
The following section describes how to distribute the licenses you received.
Use the licdistribute.xml file as a basis for creating your own license distribution deployment. The licdistribute.xml deployment is a license distribution deployment that will pick up the odbatchlic.zip file from its location and deploy the appropriate license file into the following location on each server host: The licdistribute.xml file resides in the following location:
od-home/conf/licDist
2. Open the file licdistribute.xml using your favorite text or XML editor, and update its replication farm to include the targets (similar to what you did for your license identification deployment). 3. Save the updated licdistribute.xml file using a different unique name. Your original licdistribute.xml file should remain unchanged so you can use it as the basis for future license distribution deployments. 4. Run the license distribution deployment, either from the browser-based user interface, or from the command line. When the license distribution deployment is successfully run, each target will have its own OD.lic license file deployed to the following location:
od-home/etc
Your OpenDeploy target server will automatically accept the license file in this location. It is not necessary to configure an allowed directory for it.
45
Chapter 3: Licensing
Remote Upgrades
The remote upgrade feature allows you to deploy software upgrades automatically to a user-specified list of OpenDeploy base servers and receivers. This type of deployment relieves you of having to manually upgrade your OpenDeploy server individually, saving you large amounts of labor and time. Software upgrades can include new versions of OpenDeploy, service packs to existing versions, and patches. Remote upgrades use pre-configured deployments to perform the following tasks: Perform the software distribution - upgrade installation packages are deployed to the target server hosts, and run automatically to upgrade the existing software to the new desired version. License identification - information needed for the proper licensing of each target server is collected and combined into a .zip file. You then upload this license identification file to the Interwoven Support Web site as part of your request for the OpenDeploy server licenses associated for the upgraded servers. License distribution - deploy the licenses received from Interwoven. You can also place each license individually in target servers.
Prerequisites
The following prerequisites apply to your OpenDeploy servers participating in remote upgrades: The sending server must be release 6.1 or later. The target servers being upgraded must be release 5.6 or later. The upgrade must result in the target servers being release 6.1 or later. The server host must have a resolvable host name. You must perform the following prerequisite tasks before performing the upgrade deployment: Ensure each target server host is listed in the sending servers nodes configuration file (by default odnodes.xml). Refer to Defining Target Nodes on page 126 in the OpenDeploy Administration Guide for more information. Create a directory on the target servers host outside the od-home directory to which the sending server can deploy files. Update the configuration file of each target server to include the sending server host as an allowed host, and the directory you created in the previous step as an allowed directory. Refer to Specifying Allowed Hosts for Received Deployments on page 169 and Specifying Allowed Directories for Deployments on page 170 in the OpenDeploy Administration Guide for more information.
Interwoven, Inc.
46
Chapter 3: Licensing
Limitations
The following limitations apply to the remote upgrade feature: Only equivalent OpenDeploy software can be upgraded, for example, you can only upgrade a receiver to another receiver. You cannot upgrade a receiver to a base server. The target must be a standalone OpenDeploy installation, rather than an installation of Content Provisioning Solution (CPS). Administration package software cannot be upgraded using this method. Upgrade deployments using the routed deployment feature is not supported. Upgrade deployments using the multi-tiered deployment feature is not supported. Only the initial OpenDeploy instance of the sending server can be used to perform the upgrade deployment, and only the initial instance of the target server is restarted after the upgrade. If your remote upgrade targets include one or more OpenDeploy 5.6 servers, all configuration files associated with the remote upgrade, including licensing, must reside in the /conf directory, rather than their default deployment group locations. See Remote Upgrade Configuration File Location for OpenDeploy 5.6 Targets on page 57 for more information. The target host can have only one installation of an OpenDeploy base server or receiver. The remote upgrade feature is not supported on hosts that have both OpenDeploy 5.x and 6.x server software installed.
47
Chapter 3: Licensing
You can specify an alternate location for the upgrade installation files by adding the upgradeBitsMap element to your sending base servers configuration file (by default odbase.xml). For example:
<deployServerConfiguration> ... <upgradeBitsMap ...> </deployServerConfiguration>
Specify the full path on your host where the upgrade installation files reside as the value for the upgradeBitsMap elements dirPath attribute, for example:
<upgradeBitsMap dirPath="/upgrades">
You can map individual shortened logical names to some or all of these files by adding the alias element as a child element of the upgradeBitsMap element, for example:
<upgradeBitsMap ...> <alias ...> </upgradeBitsMap>
For example:
relPath="IWOVopendeployBaseFull.6.1.1.0.0.Build12345.Windows.exe"
Interwoven, Inc.
48
Chapter 3: Licensing
You must specify a separate alias element for each upgrade installation file to which you want to assign a shortened name. For example:
<upgradeBitsMap ...> <alias name="ODBase611" relPath="IWOVopendeployBaseFull.6.1.1.0.0. Build12345.Windows.exe"/> <alias name="ODRcvr611" relPath="IWOVopendeployRcvr.6.1.1.0.0. Build12345.Windows.exe"/> </upgradeBitsMap>
If you want to assign short names to your upgrade installation files, but do not want to change their default location on the sending server, modify your base server configuration file with the upgradeBitsMap and alias elements as necessary, but omit the dirPath attribute.
2. Select the base server that will perform the software distribution deployment from the Selected Server list.
49
Chapter 3: Licensing
3. Select Software Distribution from the Configuration Type list to display the Remote Upgrade window for software distribution configurations (Figure 5). Figure 5 Remote Upgrade Window Software Distribution Configurations
This window displays a listing of any existing software distribution deployments, along with the ability to start, schedule, or view each one. 4. Click New Configuration. The window (Figure 6) is updated with items for you to complete that will determine how the software distribution deployment will be configured. Figure 6 Remote Upgrade Window Software Distribution Configurations (cont.)
It also contains a separate listing for each replication farm (with its member target nodes listed underneath) and individual target node present in your sending servers nodes configuration file. 5. Enter the name of the software distribution deployment in the Configuration Name box, for example, upgradeTest. 6. Select the software distribution installation file you want to deploy from the Upgrade Package list. The value you enter here is automatically applied to each target node listed. However, you can change this value for any individual listing. You can also leave this box unselected and select the upgrade package for each target node separately. 7. Enter the destination directory on the targets for the software installation file in the Target Directory box. The value you enter here is automatically applied to each target node listed. However, you can change this value for any individual listing. You can also leave this box empty and enter the target directory for each target node separately.
Interwoven, Inc.
50
Chapter 3: Licensing
8. Select one of the following options from the Encryption list: None - no encryption. SSL - secure data transfer using Secure Sockets Layer-based (SSL) encryption. Key File - weak (40-bit) symmetric key file-based encryption. Refer to Chapter 8, Encryption in the OpenDeploy Administration Guide for more information. 9. Check the box in front of each target node listing to indicate that those targets are participating in the software distribution. Those node listings that are not checked will not receive the deployed software distribution installation file. At least one target node listing must be checked to generate the configuration file. 10. Click Save. The window reappears with your new software distribution configuration included in the list (Figure 7). Figure 7 Remote Upgrade Window Software Distribution Configurations (cont.)
The software distribution deployment configuration is generated and stored in the following location:
od-home/conf/softDist
In addition, the configuration files needed for acquiring information about the target nodes, and for distributing the licenses, are also created in the following locations, respectively:
od-home/conf/licID od-home/conf/licDist
Each of these locations includes an XML-based file with the same name as the one created in the od-home/conf/softDist directory. These will be used in later tasks. If any of the upgrade targets are OpenDeploy version 5.6, see Upgrading from OpenDeploy 5.6 on page 57 for additional information.
51
Chapter 3: Licensing
11. Click the Start button associated with the software distribution deployment you want to run. The Start Deployment window appears (Figure 8). Figure 8 Start Deployment Window
12. Click Start Deployment. The upgrade installation file is deployed to each target host listed in the deployment, along with a script that allows the installation file to begin running after it is deployed. 13. (Upgrades from OpenDeploy 5.6 on Windows only) Reboot your target server host. After deploying the installation file and script, a Deploy and Run script is invoked. The Deploy and Run first performs validation checks before the installation begins. If the validation is successful, the Deploy and Run then begins the installation. You can view details on how the upgrade performed in the sender and receiver target logs.
- specify the amount of time in minutes between polling of the target. Default value is 2.
Interwoven, Inc.
52
Chapter 3: Licensing
The name of the license identification deployment in this directory is the same as the associated software distribution deployment. To run the license identification deployment, follow these steps: 1. Select Servers > Remote Upgrade to display the Remote Upgrade window. 2. Select License Identification from the Configuration Type list to display the Remote Upgrade window for license identification configurations (Figure 9). Figure 9 Remote Upgrade Window License Identification Configurations
This window displays a listing of any existing license identification deployments, including the one generated automatically when you created the software distribution deployment. Here you can start, schedule, or view any of the ones listed by clicking the appropriate associated button. If you want to run the license identification deployment associated with the software distribution deployment you have already ran, click its associated Start button. The Start Deployment window appears, where you can run the license identification deployment as you would a regular deployment. The information collected is written to file odlicreq_datetimestamp.zip residing on the following location of the host running the deployment:
od-home/install/batch/req
After you have run the license identification deployment, continue on starting with step 6 of Batch Server Activation on page 43.
53
Chapter 3: Licensing
To configure a new license identification deployment, follow these steps: 1. Enter a name for the license identification deployment in the Configuration Name box. 2. Select one of the following options from the Encryption list: None - no encryption. SSL - secure data transfer using Secure Sockets Layer-based (SSL) encryption. Key File - weak (40-bit) symmetric key file-based encryption. Refer toChapter 8, Encryption in the OpenDeploy Administration Guide for more information. 3. Check those targets that you want included in your deployment. You must select at least one target. 4. Click Save. The original License Identification window reappears with your new license identification deployment included in the list. The license identification deployment is created in the following location:
od-home/conf/licID
An accompanying license distribution deployment configuration file with the same name is also generated automatically in the following location:
od-home/conf/licDist
Interwoven, Inc.
54
Chapter 3: Licensing
Distributing Licenses
After you have run the license identification deployment and sent the collected information to the Interwoven Support Web site, you will receive the batch license file odbatchlic.zip. This file contains licenses for the OpenDeploy servers that were part of your license identification deployment. After you receive this file, place it in the following location:
od-home/install/batch
You must run the license distributing deployment associated with your license identification deployment. This will deploy the license to each target and activate it. At the time a software distribution deployment configuration or a license identification deployment is generated, OpenDeploy also generates a corresponding license distribution deployment configuration in the following location:
od-home/conf/licDist
The name of the license distribution deployment configuration file in this directory is the same as the associated software distribution or license identification deployment. To distribute the licenses, follow these steps: 1. Select Servers > Remote Upgrade to display the Remote Upgrade window. 2. Select License Distribution from the Configuration Type list to display the Remote Upgrade window for license distribution configurations (Figure 11). Figure 11 License Distribution Window
The window displays a listing of any existing license distribution deployment configurations, including the one generated automatically when you created the software distribution or license identification deployment configuration file. Here you can start, schedule, or view any of the ones listed by clicking the appropriate associated button. If you want to run the license distribution deployment associated with the software distribution or license identification deployment you have already ran, click its associated Start button. The Start Deployment window appears, where you can run the license distribution deployment as you would a regular deployment. After the license distribution deployment is run, those targets that successfully received their license files are now fully operable.
55
Chapter 3: Licensing
To configure a new license distribution deployment, follow these steps: 1. Enter a name for the license distribution deployment in the Configuration Name box. 2. Select one of the following options from the Encryption list: None - no encryption. SSL - secure data transfer using Secure Sockets Layer-based (SSL) encryption. Key File - weak (40-bit) symmetric key file-based encryption. Refer to Chapter 8, Encryption in the OpenDeploy Administration Guide for more information. 3. Check those targets that you want included in your license distribution deployment. You must select at least one target. 4. Click Save. The original License Distribution window reappears with your new license distribution deployment configuration included in the list. The new license distribution configuration file is created in the following location:
od-home/conf/licDist
Interwoven, Inc.
56
Chapter 3: Licensing
Logging
The remote upgrade script which runs on each target host generates the log file od_remote_upgrade.log. This file contains entries detailing the upgrade including any errors. The od_remote_upgrade.log file resides in the following locations on each remote upgrade target host:
od-home/install
The directory on the target host that receives the deployed upgrade installation file.
57
Chapter 3: Licensing
You should exercise caution and understand the risks of this type of operation before beginning.
To perform remote upgrades on UNIX target hosts as a non-root user, follow these steps: 1. Configure a software distribution deployment as described in Distributing the Target Server Software on page 49. Ensure you have the appropriate permissions to write to the target directory specified in the deployment. 2. Install Sudo (superuser do) on each target host. This is free software available from the following Web site:
http://www.courtesan.com/sudo/
You must have root access on each target host to install and configure Sudo. 3. Open the software distribution deployment using your favorite text or XML editor. Each target has its own corresponding DeployNRun element. Within this DeployNRun element, there are two script elements, one for validation and one for remote installation. 4. Remove the following attribute and value from each of the script elements:
as="root"
5. Add the absolute path to the Sudo command to the beginning of each of the script elements cmd attribute value. For example:
cmd="/usr/local/bin/sudo /path/unixupgrade.sh VALIDATE /path/ IWOVopendeployBaseFull.6.1.1.0.0.Build55148.SunOS.tar.gz"
and
cmd="/usr/local/bin/sudo /path/unixupgrade.sh REMOTE_INSTALL /path/ IWOVopendeployBaseFull.6.1.1.0.0.Build55148.SunOS.tar.gz"
6. Save and close the file. 7. Configure Sudo on each target host to allow unixupgrade.sh to be run as root without requiring a password. Sudo is configured by modifying the /etc/sudoers file using the visudo command that comes with the sudo package.
Interwoven, Inc.
58
Chapter 3: Licensing
One method to configure the required access is by adding the following lines to the /etc/sudoers file:
User_Alias ODREMOTEUPGRADERS = user Cmnd_Alias ODREMOTEUPGRADE = /path/unixupgrade.sh ODREMOTEUPGRADERS targetHostName = (root) NOPASSWD: ODREMOTEUPGRADE
8. Run the software distribution deployment and verify that the target OpenDeploy servers have been successfully upgraded. 9. Reverse the changes made to the /etc/sudoers file so that a password is once again required. If you attempt to run a remote upgrade as a non-root user without performing the steps described in this section, the remote upgrade will fail. An error message will be entered in the od_remote_upgrade.log file. See Logging on page 57 for more information.
59
Chapter 3: Licensing
Interwoven, Inc.
60
Chapter 4
Remote Upgrades
This chapter describes how to configure your OpenDeploy base server to upgrade the software and licenses of its target servers. The remote upgrade feature allows you to deploy software upgrades automatically to a user-specified list of OpenDeploy base servers and receivers. This type of deployment relieves you of having to manually upgrade your OpenDeploy server individually, saving you large amounts of labor and time. Software upgrades can include new versions of OpenDeploy, service packs to existing versions, and patches. Remote upgrades use pre-configured deployments to perform the following tasks: Perform the software distribution - upgrade installation packages are deployed to the target server hosts, and run automatically to upgrade the existing software to the new desired version. License identification - information needed for the proper licensing of each target server is collected and combined into a .zip file. You then upload this license identification file to the Interwoven Support Web site as part of your request for the OpenDeploy server licenses associated for the upgraded servers. License distribution - deploy the licenses received from Interwoven. You can also place each license individually in target servers.
Prerequisites
The following prerequisites apply to your OpenDeploy servers participating in remote upgrades: The sending server must be release 6.1 or later. The target servers being upgraded must be release 5.6 or later. The upgrade must result in the target servers being release 6.1 or later. The server host must have a resolvable host name. You must perform the following prerequisite tasks before performing the upgrade deployment: Ensure each target server host is listed in the sending servers nodes configuration file (by default odnodes.xml). Refer to Defining Target Nodes on page 126 in the OpenDeploy Administration Guide for more information.
61
Create a directory on the target servers host outside the od-home directory to which the sending server can deploy files. Update the configuration file of each target server to include the sending server host as an allowed host, and the directory you created in the previous step as an allowed directory. Refer to Specifying Allowed Hosts for Received Deployments on page 169 and Specifying Allowed Directories for Deployments on page 170 in the OpenDeploy Administration Guide for more information.
Limitations
The following limitations apply to the remote upgrade feature: Only equivalent OpenDeploy software can be upgraded, for example, you can only upgrade a receiver to another receiver. You cannot upgrade a receiver to a base server. The target must be a standalone OpenDeploy installation, rather than an installation of Content Provisioning Solution (CPS). Administration package software cannot be upgraded using this method. Upgrade deployments using the routed deployment feature is not supported. Upgrade deployments using the multi-tiered deployment feature is not supported. Only the initial OpenDeploy instance of the sending server can be used to perform the upgrade deployment, and only the initial instance of the target server is restarted after the upgrade. If your remote upgrade targets include one or more OpenDeploy 5.6 servers, all configuration files associated with the remote upgrade, including licensing, must reside in the /conf directory, rather than their default deployment group locations. See Remote Upgrade Configuration File Location for OpenDeploy 5.6 Targets on page 73 for more information. The target host can have only one installation of an OpenDeploy base server or receiver. The remote upgrade feature is not supported on hosts that have both OpenDeploy 5.x and 6.x server software installed.
Interwoven, Inc.
62
You can specify an alternate location for the upgrade installation files by adding the upgradeBitsMap element to your sending base servers configuration file (by default odbase.xml). For example:
<deployServerConfiguration> ... <upgradeBitsMap ...> </deployServerConfiguration>
Specify the full path on your host where the upgrade installation files reside as the value for the upgradeBitsMap elements dirPath attribute, for example:
<upgradeBitsMap dirPath="/upgrades">
63
You can map individual shortened logical names to some or all of these files by adding the alias element as a child element of the upgradeBitsMap element, for example:
<upgradeBitsMap ...> <alias ...> </upgradeBitsMap>
For example:
relPath="IWOVopendeployBaseFull.6.1.1.0.0.Build12345.Windows.exe"
You must specify a separate alias element for each upgrade installation file to which you want to assign a shortened name. For example:
<upgradeBitsMap ...> <alias name="ODBase611" relPath="IWOVopendeployBaseFull.6.1.1.0.0. Build12345.Windows.exe"/> <alias name="ODRcvr611" relPath="IWOVopendeployRcvr.6.1.1.0.0. Build12345.Windows.exe"/> </upgradeBitsMap>
If you want to assign short names to your upgrade installation files, but do not want to change their default location on the sending server, modify your base server configuration file with the upgradeBitsMap and alias elements as necessary, but omit the dirPath attribute.
Interwoven, Inc.
64
2. Select the base server that will perform the software distribution deployment from the Selected Server list. 3. Select Software Distribution from the Configuration Type list to display the Remote Upgrade window for software distribution configurations (Figure 14). Figure 14 Remote Upgrade Window Software Distribution Configurations
This window displays a listing of any existing software distribution deployments, along with the ability to start, schedule, or view each one.
65
4. Click New Configuration. The window (Figure 15) is updated with items for you to complete that will determine how the software distribution deployment will be configured. Figure 15 Remote Upgrade Window Software Distribution Configurations (cont.)
It also contains a separate listing for each replication farm (with its member target nodes listed underneath) and individual target node present in your sending servers nodes configuration file. 5. Enter the name of the software distribution deployment in the Configuration Name box, for example, upgradeTest. 6. Select the software distribution installation file you want to deploy from the Upgrade Package list. The value you enter here is automatically applied to each target node listed. However, you can change this value for any individual listing. You can also leave this box unselected and select the upgrade package for each target node separately. 7. Enter the destination directory on the targets for the software installation file in the Target Directory box. The value you enter here is automatically applied to each target node listed. However, you can change this value for any individual listing. You can also leave this box empty and enter the target directory for each target node separately. 8. Select one of the following options from the Encryption list: None - no encryption. SSL - secure data transfer using Secure Sockets Layer-based (SSL) encryption. Key File - weak (40-bit) symmetric key file-based encryption. Refer to Chapter 8, Encryption in the OpenDeploy Administration Guide for more information. 9. Check the box in front of each target node listing to indicate that those targets are participating in the software distribution. Those node listings that are not checked will not receive the deployed software distribution installation file. At least one target node listing must be checked to generate the configuration file.
Interwoven, Inc.
66
10. Click Save. The window reappears with your new software distribution configuration included in the list (Figure 16). Figure 16 Remote Upgrade Window Software Distribution Configurations (cont.)
The software distribution deployment configuration is generated and stored in the following location:
od-home/conf/softDist
In addition, the configuration files needed for acquiring information about the target nodes, and for distributing the licenses, are also created in the following locations, respectively:
od-home/conf/licID od-home/conf/licDist
Each of these locations includes an XML-based file with the same name as the one created in the od-home/conf/softDist directory. These will be used in later tasks. If any of the upgrade targets are OpenDeploy version 5.6, see Upgrading from OpenDeploy 5.6 on page 73 for additional information. 11. Click the Start button associated with the software distribution deployment you want to run. The Start Deployment window appears (Figure 17). Figure 17 Start Deployment Window
12. Click Start Deployment. The upgrade installation file is deployed to each target host listed in the deployment, along with a script that allows the installation file to begin running after it is deployed. 13. (Upgrades from OpenDeploy 5.6 on Windows only) Reboot your target server host. After deploying the installation file and script, a Deploy and Run script is invoked. The Deploy and Run first performs validation checks before the installation begins. If the validation is successful, the Deploy and Run then begins the installation. You can view details on how the upgrade performed in the sender and receiver target logs.
67
- specify the amount of time in minutes between polling of the target. Default value is 2.
The name of the license identification deployment in this directory is the same as the associated software distribution deployment. To run the license identification deployment, follow these steps: 1. Select Servers > Remote Upgrade to display the Remote Upgrade window.
Interwoven, Inc.
68
2. Select License Identification from the Configuration Type list to display the Remote Upgrade window for license identification configurations (Figure 18). Figure 18 Remote Upgrade Window License Identification Configurations
This window displays a listing of any existing license identification deployments, including the one generated automatically when you created the software distribution deployment. Here you can start, schedule, or view any of the ones listed by clicking the appropriate associated button. If you want to run the license identification deployment associated with the software distribution deployment you have already ran, click its associated Start button. The Start Deployment window appears, where you can run the license identification deployment as you would a regular deployment. The information collected is written to file odlicreq_datetimestamp.zip residing on the following location of the host running the deployment:
od-home/install/batch/req
After you have run the license identification deployment, continue on starting with step 6 of Batch Server Activation on page 43.
69
To configure a new license identification deployment, follow these steps: 1. Enter a name for the license identification deployment in the Configuration Name box. 2. Select one of the following options from the Encryption list: None - no encryption. SSL - secure data transfer using Secure Sockets Layer-based (SSL) encryption. Key File - weak (40-bit) symmetric key file-based encryption. Refer to Chapter 8, Encryption in the OpenDeploy Administration Guide for more information. 3. Check those targets that you want included in your deployment. You must select at least one target. 4. Click Save. The original License Identification window reappears with your new license identification deployment included in the list. The license identification deployment is created in the following location:
od-home/conf/licID
An accompanying license distribution deployment configuration file with the same name is also generated automatically in the following location:
od-home/conf/licDist
Interwoven, Inc.
70
Distributing Licenses
After you have run the license identification deployment and sent the collected information to the Interwoven Support Web site, you will receive the batch license file odbatchlic.zip. This file contains licenses for the OpenDeploy servers that were part of your license identification deployment. After you receive this file, place it in the following location:
od-home/install/batch
You must run the license distributing deployment associated with your license identification deployment. This will deploy the license to each target and activate it. At the time a software distribution deployment configuration or a license identification deployment is generated, OpenDeploy also generates a corresponding license distribution deployment configuration in the following location:
od-home/conf/licDist
The name of the license distribution deployment configuration file in this directory is the same as the associated software distribution or license identification deployment. To distribute the licenses, follow these steps: 1. Select Servers > Remote Upgrade to display the Remote Upgrade window. 2. Select License Distribution from the Configuration Type list to display the Remote Upgrade window for license distribution configurations (Figure 20). Figure 20 License Distribution Window
The window displays a listing of any existing license distribution deployment configurations, including the one generated automatically when you created the software distribution or license identification deployment configuration file. Here you can start, schedule, or view any of the ones listed by clicking the appropriate associated button. If you want to run the license distribution deployment associated with the software distribution or license identification deployment you have already ran, click its associated Start button. The Start Deployment window appears, where you can run the license distribution deployment as you would a regular deployment. After the license distribution deployment is run, those targets that successfully received their license files are now fully operable.
71
To configure a new license distribution deployment, follow these steps: 1. Enter a name for the license distribution deployment in the Configuration Name box. 2. Select one of the following options from the Encryption list: None - no encryption. SSL - secure data transfer using Secure Sockets Layer-based (SSL) encryption. Key File - weak (40-bit) symmetric key file-based encryption. Refer to Chapter 8, Encryption in the OpenDeploy Administration Guide for more information. 3. Check those targets that you want included in your license distribution deployment. You must select at least one target. 4. Click Save. The original License Distribution window reappears with your new license distribution deployment configuration included in the list. The new license distribution configuration file is created in the following location:
od-home/conf/licDist
Interwoven, Inc.
72
Logging
The remote upgrade script which runs on each target host generates the log file od_remote_upgrade.log. This file contains entries detailing the upgrade including any errors. The od_remote_upgrade.log file resides in the following locations on each remote upgrade target host:
od-home/install
The directory on the target host that receives the deployed upgrade installation file.
73
These requirements apply to remote upgrades of a mix of OpenDeploy 5.6 and 6.0.x targets, as well as just OpenDeploy 5.6 targets alone.
You should exercise caution and understand the risks of this type of operation before beginning.
To perform remote upgrades on UNIX target hosts as a non-root user, follow these steps: 1. Configure a software distribution deployment as described in Distributing the Target Server Software on page 65. Ensure you have the appropriate permissions to write to the target directory specified in the deployment. 2. Install Sudo (superuser do) on each target host. This is free software available from the following Web site:
http://www.courtesan.com/sudo/
You must have root access on each target host to install and configure Sudo. 3. Open the software distribution deployment using your favorite text or XML editor. Each target has its own corresponding DeployNRun element. Within this DeployNRun element, there are two script elements, one for validation and one for remote installation. 4. Remove the following attribute and value from each of the script elements:
as="root"
5. Add the absolute path to the Sudo command to the beginning of each of the script elements cmd attribute value. For example:
cmd="/usr/local/bin/sudo /path/unixupgrade.sh VALIDATE /path/ IWOVopendeployBaseFull.6.1.1.0.0.Build55148.SunOS.tar.gz"
and
cmd="/usr/local/bin/sudo /path/unixupgrade.sh REMOTE_INSTALL /path/ IWOVopendeployBaseFull.6.1.1.0.0.Build55148.SunOS.tar.gz"
Interwoven, Inc.
74
7. Configure Sudo on each target host to allow unixupgrade.sh to be run as root without requiring a password. Sudo is configured by modifying the /etc/sudoers file using the visudo command that comes with the sudo package. One method to configure the required access is by adding the following lines to the /etc/sudoers file:
User_Alias ODREMOTEUPGRADERS = user Cmnd_Alias ODREMOTEUPGRADE = /path/unixupgrade.sh ODREMOTEUPGRADERS targetHostName = (root) NOPASSWD: ODREMOTEUPGRADE
8. Run the software distribution deployment and verify that the target OpenDeploy servers have been successfully upgraded. 9. Reverse the changes made to the /etc/sudoers file so that a password is once again required. If you attempt to run a remote upgrade as a non-root user without performing the steps described in this section, the remote upgrade will fail. An error message will be entered in the od_remote_upgrade.log file. See Logging on page 73 for more information.
75
Interwoven, Inc.
76
Index
A
administration package 10 installation 22, 27 administration server 11 installation 15 software 10 Tomcat server 11 uninstallation 37 alias element 48, 64 attributes checkIntervalInMins 52, 68 dirPath 48, 63 maxIterations 52, 68 name (alias) 48, 64 relPath 48, 64 alias 48, 64 upgradeBitsMap 48, 63
I
installation 10, 19, 27 administration package 10, 22, 27 administration server 10, 15 base server 10, 13, 20, 25 ContentServices Access Service 24 ContentServices Foundation Access Service 28 ContentServices Foundation access service 10, 12, 15 DOS-compatible 8.3 format 16 home values 35 information requirements 13 multiple releases 34 order 35 platform-specific requirements 29 receiver 10, 14, 22, 27 reporting server 10, 15 Tomcat server 11 UNIX 25 upgrades 30 Windows 19
B
base server 10 installation 13, 20, 25 license types 14 software 10 uninstallation 38 bootstrap administrator 25, 29
C
checkIntervalInMins attribute 52, 68 ContentServices Access Service installation 24 ContentServices Foundation Access Service installation 28 ContentServices Foundation access service 38 installation 12, 15 non-default port configuration 16 software 10 uninstallation 38
L
licensing 39, 40, 41 add-on modules 40 administration package 40 base server 40 batch 43 cluster 41 distribution 45 EasyDeploy 40 expired 59 multiple host names 41 receiver 40 requests 44 single 42 software activation 39
D
dirPath attribute 48, 63
E
EasyDeploy 14, 40 elements
M
maxIterations attribute 52, 68
77
Index
N
name (alias) attribute 48, 64
T
target servers installation 10 Tomcat server installation 11
O
OpenDeploy administration server 11 base server 10 configuration 19 home values 35 installation 10, 19, 25, 35 licensing 41 multiple releases 34 receiver 10 reporting server 12 uninstalling 35 upgrades 30 OpenDeploy licensing 39, 40 OpenDeploy Release Notes 9
U
uninstallation 35 administration server 37 base server 38 receiver 38 UNIX 37 Windows 36 upgradeBitsMap element 48, 63 upgrades 30 configuration files 31 DAS and database deployments 32 event reporting 32 home values, updating 33 multiple instances 32 non-Administrator 31 non-root 31 operations server 33 previous releases 30 remote 46, 61 reporting server 32
R
receiver 10 installation 10, 14, 22, 27 uninstallation 38 relPath attribute 48, 64 remote upgrades 46, 61 best practices 47, 63 installation file location 48, 63 license distribution 55, 71 license requests 53, 68 limitations 47, 62 logging 57, 73 monitoring 52, 68 non-root user 58, 74 OpenDeploy 5.6 57, 73 preparation 63 prerequisites 46, 61 short names, specifying 48, 64 target software, distributing 49, 65 reporting server 12 installation 15 software 10 upgrades 32 RMI registry service 16
S
software activation 39 source servers installation 10
Interwoven, Inc.
78