OpenText Runtime and Core Services 10.2.1 - Installation Guide English (ELCS100201-IGD-En-3)

8/11/2019 OpenText Runtime and Core Services 10.2.1 - Installation Guide English (ELCS100201-IGD-En-3)

http://slidepdf.com/reader/full/opentext-runtime-and-core-services-1021-installation-guide-english-elcs100201-igd-en-3 1/124

OpenText Runtime and Core Services

Installation Guide

This documentation describes the planning, installation, andupgrading of OpenText Runtime and Core Services 10.2.1 andOpenText Directory Services 10.2.1.

ELCS100201-IGD-EN-3



OpenText Runtime and Core Services

Installation Guide

ELCS100201-IGD-EN-3Rev.: 2012-Jan-27

This documentation has been created for software version 10.2.1.

It is also valid for subsequent software versions as long as no new document version is shipped with the product or is

published at https://knowledge.opentext.com.

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111

Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440

Fax: +1-519-888-0677

Email: [email protected]

FTP: ftp://ftp.opentext.com

For more information, visit http://www.opentext.com

Copyright © by Open Text Corporation, Open Text Inc.

Open Text Corporation is the owner of the trademarks Open Text, OpenText, The Content Experts, OpenText ECM Suite,

OpenText eDOCS, eDOCS, OpenText FirstClass, FirstClass, OpenText Exceed, OpenText HostExplorer, OpenText Exceed

OnDemand, OpenText Exceed 3D, OpenText Exceed Freedom, OpenText Exceed PowerSuite, OpenText Exceed XDK,

OpenText NFS Solo, OpenText NFS Client, OpenText NFS Server, OpenText NFS Gateway, OpenText Everywhere, OpenText

Real Time, OpenText Eloquent Media Server, OpenText Integrated Document Management, OpenText IDM, OpenText

DocuLink, Livelink, Livelink ECM, Artesia, RedDot, RightFax, RKYV, DOMEA, Alchemy, Vignette, Vizible, Nstein,

LegalKEY, Picdar, Hummingbird, IXOS, Alis Gist-in-Time, Eurocortex, Gauss, Captaris, Spicer, Genio, Vista Plus, Burntsand,

New Generation Consulting, Momentum Systems, DOKuStar, and RecoStar among others. This list is not exhaustive.

All other products or company names are used for identification purposes only, and are trademarks of their respective own-

ers. All rights reserved.

https://knowledge.opentext.com/


mailto:[email protected]

ftp://ftp.opentext.com/


http://www.opentext.com/



mailto:[email protected]





ELCS100201-IGD-EN-3 OpenText Runtime and Core Services iii

Table of Contents

PRE Introduction ............................................................................... 7

i Documentation Conventions....................................................................7

ii Contact Information.................................................................................. 8

1 Planning to Install Runtime and Core Services....................... 9

1.1 System Requirements.............................................................................. 9

1.1.1 Operating System .................................................................................... 9

1.1.2

Java Environment ..................................................................................10 1.1.3 Application Server .................................................................................. 10

1.1.4 Database................................................................................................ 10

1.1.5 Configurations........................................................................................ 11

1.1.6 Unstructured Data Storage ....................................................................12

1.1.7 Load Balancer ........................................................................................ 12

1.1.8 Support of IPv6 ......................................................................................12

1.2 Administering Runtime and Core Services ............................................ 12

1.3 Runtime and Core Services Installation Checklist................................. 13

2 Installing on Windows............................................................. 15

2.1 Installing Prerequisites for Windows......................................................15

2.1.1 Prerequisites for Clustering on Windows...............................................15

2.1.2

Installing and Configuring Tomcat on Windows..................................... 16

2.1.2.1 To Install Tomcat.................................................................................... 17

2.1.2.2 To Configure Java Options for Optimal Performance............................ 17

2.1.2.3

To Configure Tomcat for Secure Sockets Layer (SSL) .........................18

2.1.3 Installing and Configuring NetWeaver on Windows............................... 19

2.2

Installing Runtime and Core Services using Setup................................ 21

2.3

Installing Directory Services Externally.................................................. 37

2.4

Installing Runtime and Core Services Silently.......................................42

2.5

Configuring Application Servers after Installation .................................. 46

3 Installing on UNIX or Linux..................................................... 49

3.1 Installing Prerequisites for UNIX or Linux .............................................. 49

3.1.1

Prerequisites for Clustering on UNIX or Linux....................................... 49

3.1.2 Installing and Configuring Tomcat on UNIX or Linux............................. 50

3.1.2.1 To Install and Configure Tomcat............................................................ 51

3.1.2.2 To Configure Java Options for Optimal Performance............................ 52

3.1.2.3 To Configure Tomcat for Secure Sockets Layer (SSL) .........................52

3.1.2.4 To Start or Stop Tomcat Using Scripts ..................................................53

3.1.3 Installing and Configuring NetWeaver on UNIX or Linux....................... 54



Table of Contents

iv OpenText Runtime and Core Services ELCS100201-IGD-EN-3

3.2 Installing Runtime and Core Services.................................................... 56

3.3 Installing Directory Services Externally.................................................. 63

3.4 Installing Runtime and Core Services Silently on UNIX or Linux .......... 65

3.5

Configuring Application Servers after Installation .................................. 68

4 Installing OpenText Administration Client.............................71

4.1 Prerequisites ..........................................................................................71

4.2 Installing Administration Client ............................................................... 71

4.3 Accessing Logging Information .............................................................. 72

4.4 Removing Administration Client............................................................. 72

5 Securing Your Server ..............................................................73

5.1 Enabling SSL on Runtime and Core Services ....................................... 73

5.2 Enabling SSL for JMS Server ................................................................73

5.3 Securing Your Runtime and Core Services Database........................... 75

6 Configuring Runtime and Core Services Clusters ................77

6.1 Configuring Clusters and Services on Tomcat ...................................... 77

6.1.1 Configuring Vertical Clusters Manually .................................................. 79

6.1.2 Configuring Automatic Failover for Vertical Clusters ............................. 80

6.1.3 Using the Administration Client to Manage Vertical Clusters ................80

6.1.4 Configuring Horizontal or Mixed Clusters ..............................................81

6.2 Understanding Singleton Services and Failover Scenarios in Clusters.83

6.2.1 Alphabetic Node Elector ........................................................................ 84

6.2.2 Configurable Node Elector..................................................................... 84

6.2.3 Preserve Singleton Node Elector........................................................... 84

7 Configuring Runtime and Core Services in a High-

Availability Cluster...................................................................85

7.1 Prerequisites ..........................................................................................85

7.2 Installing Tomcat in a High-Availability Cluster...................................... 86

7.3 Configuring your High-Availability Cluster .............................................86

7.4 Installing Runtime and Core Services on the Primary Node .................87

7.5 Installing Directory Services Externally in a High-Availability Cluster.... 88

8 Removing Runtime and Core Services ..................................95

8.1 Removing Runtime and Core Services on Windows............................. 95

8.1.1 Removing Runtime and Core Services on Tomcat................................ 95

8.1.2 Removing Runtime and Core Services on NetWeaver .........................97

8.1.3 Removing Externally Installed Directory Services .................................98

8.2

Removing Runtime and Core Services on UNIX or Linux ..................... 98

8.2.1 Removing Runtime and Core Services and Tomcat.............................. 98

8.2.2 Removing Runtime and Core Services Without Removing Tomcat...... 99

8.2.3 Removing Runtime and Core Services and NetWeaver ..................... 101

8.2.4 Removing Runtime and Core Services Without RemovingNetWeaver ...........................................................................................102

8.2.5

Removing Externally Installed Directory Services ............................... 103



Table of Contents

ELCS100201-IGD-EN-3 Installation Guide v

9 Backing Up and Restoring Runtime and Core Services..... 105

9.1 Backing Up Runtime and Core Services.............................................. 105

9.2 Restoring Runtime and Core Services................................................. 106

10

Upgrading Runtime and Core Services and DirectoryServices ................................................................................. 107

10.1 Upgrading from Version 10.1.0 to 10.2.1 ............................................. 107

10.1.1 Prerequisites for Upgrading Runtime and Core Services.................... 108

10.1.2 Upgrading Runtime and Core Services on Windows........................... 109

10.1.3 Upgrading Runtime and Core Services on UNIX or Linux................... 110

10.2 Upgrading from Version 10.2.0 to 10.2.1 with CAP............................. 112

10.2.1 To Back Up Runtime and Core Services for Manual Upgrade ............113

10.2.2 To Remove Runtime and Core Services for Manual Upgrade ............113

10.2.3 To Remove Runtime and Core Services 10.2.0 Database Entries .....114

10.2.4 To Upgrade Other Services Manually.................................................. 114

10.2.5 To Revert Runtime and Core Services After Upgrading...................... 114

11

Changing Directory Services Connection Properties......... 117

11.1 Changing Directory Services Connection Properties on Windows ...... 117

11.2 Changing Directory Services Connection Properties on UNIX orLinux..................................................................................................... 122

IDX Index....................................................................................... 123





ELCS100201-IGD-EN-3 OpenText Runtime and Core Services vii

Preface

Introduction

OpenText Runtime and Core Services provides a runtime environment and a set offundamental services including OpenText Directory Services.

This documentation describes the planning, installing, changing, and upgrading ofOpenText Runtime and Core Services and OpenText Directory Services.

i Documentation Conventions

User interface

This format is used for elements in the graphical user interface (GUI), such asbuttons, names of icons, menu items, and fields.

Filenames , commands , and sample data This format is used for file names, paths, URLs, and commands at the commandprompt. It is also used for example data, text to be entered in text boxes, andother literals.

Note: If you copy command line examples from a PDF, be aware that PDFscan contain hidden characters. OpenText recommends copying from theHTML version of the document, if it is available.

KEY NAMESKey names appear in ALL CAPS, for example:Press CTRL+V.

<Variable name>Angled brackets < > are used to denote a variable or placeholder. The userreplaces the brackets and the descriptive content with the appropriate value. Forexample, <server_name> becomes serv01.

Internal cross-referencesClick the cross-reference to go directly to the reference target in the currentdocument.

External cross-referencesExternal cross-references are usually text references to other documents.However, if a document is available in HTML format, for example, in theKnowledge Center, external references may be active links to a specific section inthe referenced document.



Introduction

viii OpenText Runtime and Core Services ELCS100201-IGD-EN-3

Warnings, notes, and tips

Caution

Cautions help you avoid irreversible problems. Read this informationcarefully and follow all instructions.

Important

Important notes help you avoid major problems.

Note: Notes provide additional information about a task.

Tip: Tips offer you quicker or easier ways of performing a task.

ii Contact Information

OpenText Online (http://online.opentext.com/) is a single point of access for theproduct information provided by OpenText. You can access the following supportsources through OpenText Online:

• Communities

• Knowledge Center

OpenText Online Communities(http://communities.opentext.com/communities/livelink.exe/open/OpenTextOnlineCommunity) provide the following resources:

• Usage tips, help files, and best practices for customers and partners.

• Information on product releases.

• User groups and forums where you can ask questions of OpenText experts.

The OpenText Knowledge Center (https://knowledge.opentext.com) is OpenText'scorporate extranet and primary site for technical support. The Knowledge Center isthe official source for the following:

• Product downloads, patches, and documentation including Release Notes.

• Discussion forums, Online Communities, and the Knowledge Base.

• OpenText Developer Network (OTDN), which includes developer

documentation and programming samples for OpenText products.

If you need additional assistance, you can find OpenText Corporate SupportContacts at http://support.opentext.com/.

http://online.opentext.com/

http://communities.opentext.com/communities/livelink.exe/open/OpenTextOnlineCommunity



http://support.opentext.com/

http://online.opentext.com/




http://support.opentext.com/



ELCS100201-IGD-EN-3 OpenText Runtime and Core Services 9

Chapter 1

Planning to Install Runtime and Core Services

This section describes the environment that you need to install or upgrade Runtimeand Core Services.

1.1 System Requirements

Runtime and Core Services supports single-server configurations and clusterconfigurations including high-availability clusters. Before installing Runtime andCore Services, you must install and configure a supported application server and a

database for storing configuration data.Note: You must have administrative privileges to install Runtime and CoreServices and its software prerequisites.

To verify your environment, see the following sections:

• “Operating System” on page 9

• “Java Environment” on page 10

• “Application Server” on page 10

• “Database” on page 10

• “Configurations” on page 11

• “Unstructured Data Storage” on page 12

• “Load Balancer” on page 12

• “Support of IPv6” on page 12

1.1.1 Operating System

Runtime and Core Services is supported on the following 64-bit Windows®, UNIX® ,and Linux® operating systems:

• Microsoft Windows Server 2008 R2• Oracle® Solaris• IBM® AIX®

• HP-UX®

• Novell® SUSE® Linux® Enterprise Server• Red Hat® Enterprise Linux®

See the Runtime and Core Services Release Notes athttps://knowledge.opentext.com/knowledge/cs.dll/fetch/2001/3551166/1462759

https://knowledge.opentext.com/knowledge/cs.dll/fetch/2001/3551166/14627590/13609768/customview.html?func=ll&objId=13609768&objAction=browse




Chapter 1 Planning to Install Runtime and Core Services

10 OpenText Runtime and Core Services ELCS100201-IGD-EN-3

0/13609768/customview.html?func=ll&objId=13609768&objAction=browse for themost current supported operating system versions.

1.1.2 Java EnvironmentRuntime and Core Services requires Java 6. Java development environments areavailable on the Java Download Center athttp://java.sun.com/javase/downloads/index.jsp.

See the Runtime and Core Services Release Notes athttps://knowledge.opentext.com/knowledge/cs.dll/fetch/2001/3551166/14627590/13609768/customview.html?func=ll&objId=13609768&objAction=browse for themost current supported JRE/JDK versions.

1.1.3 Application Server

One of the following application servers must be installed before installing Runtimeand Core Services:

Apache Tomcat™ See “Installing and Configuring Tomcat on Windows”on page 16 or “Installing and Configuring Tomcat onUNIX or Linux” on page 50.

SAP NetWeaver® CompositionEnvironment

See “Installing and Configuring NetWeaver on Win-dows” on page 19 or “Installing and ConfiguringNetWeaver on UNIX or Linux” on page 54.

See the Runtime and Core Services Release Notes athttps://knowledge.opentext.com/knowledge/cs.dll/fetch/2001/3551166/14627590/13609768/customview.html?func=ll&objId=13609768&objAction=browse for themost current supported application server versions.

1.1.4 Database

Runtime and Core Services requires a database to store and retrieve configurationdata. The database must be available before installing Runtime and Core Services.You must also create a database user with permission to administer the database.OpenText recommends using a unique database user for Runtime and CoreServices.

Tip: Select a typical installation and accept default settings during theinstallation of your database server. There are no specific language or caserequirements for Runtime and Core Services. Core services that use Runtimeand Core Services may have additional database server requirements. For moreinformation, see part 1 "Setting Up Enterprise Library" in OpenText EnterpriseLibrary - Installation and Upgrade Guide (EL-IGD).

You can create the database in one of the following database servers:

• Microsoft® SQL Server® (Windows only)


http://java.sun.com/javase/downloads/index.jsp





http://java.sun.com/javase/downloads/index.jsp







1.1 System Requirements

ELCS100201-IGD-EN-3 Installation Guide 11

On Microsoft SQL Server, the database user requires CREATE TABLE privileges.

• Oracle® Database

On Oracle Database, the user requires CREATE

TABLE, CREATE

VIEW , CREATE

SEQUENCE and CREATE SESSION privileges. The Oracle Database user can also begranted the role RESOURCE, which is the equivalent of CREATE

TABLE and CREATE

SEQUENCE privileges.

See the Runtime and Core Services Release Notes athttps://knowledge.opentext.com/knowledge/cs.dll/fetch/2001/3551166/14627590/13609768/customview.html?func=ll&objId=13609768&objAction=browse for themost current supported database versions.

1.1.5 Configurations

Single serverconfiguration

A single-server configuration consists of clients running applications through asingle server. This is the simplest configuration of Runtime and Core Services and issufficient for small and medium-sized installations in which concurrent access byclients is limited. There is one instance of Runtime and Core Services running on asingle server.

Clusterconfiguration

A cluster consists of clients running applications through multiple Runtime andCore Services servers, all of which share a common unstructured storage location. Ina horizontal cluster configuration, there is one instance of Runtime and CoreServices running on each server. In a vertical cluster, multiple instances of Runtimeand Core Services run on one server. A cluster configuration may include bothhorizontal and vertical clusters. A cluster is useful for larger deployments withlarger numbers of clients accessing Runtime and Core Services concurrently.Clustering distributes the work evenly over the servers that are connected to thecommon storage location.

Clusters provide the following benefits:

• Automatic load balancing: Incoming client connections are directed to a Runtimeand Core Services node using the load balancer-specific algorithm that youconfigure. Runtime and Core Services requires the use of a third-party loadbalancer to configure automatic load balancing. For more information, see “LoadBalancer” on page 12.

• Hardware failover protection: If one server fails, only the clients connected tothat specific server will be affected. Clients connected to the other Runtime andCore Services servers will continue running.

• Vertical scalability: Vertical clusters allow you to make use of all the capabilities

of your existing hardware by running multiple instances of Runtime and CoreServices on your server.

High-AvailabilityClusters

Runtime and Core Services can also be deployed in a high-availability operatingsystem cluster. High-availability (HA) clusters operate by having redundant serversor nodes which are used to provide service when system components fail. A high-availability cluster is a minimum of two computers that work together running one









Tomcat instance with a common cluster storage location that is only accessed by oneserver at a time. High-availability clusters are also known as failover clusters orserver clusters. For more information on setting up a high-availability cluster, seethe Microsoft Failover Cluster Step-by-Step Guide at http://technet.microsoft.com/en-

us/library/cc731844(WS.10).aspx.

For more information on configuring your HA Runtime and Core Services cluster,see “Configuring Runtime and Core Services in a High-Availability Cluster” onpage 85.

1.1.6 Unstructured Data Storage

Runtime and Core Services requires an unstructured storage location for datastorage. OpenText recommends that this location be a shared, highly-availablestorage location in the network that is accessible by all Runtime and Core Servicesservers.

For a single-server configuration, this location can be on the local machine on whichRuntime and Core Services is installed, however, it is not recommended. For acluster configuration, the shared storage location must not be on any of the clusternodes but must be on a shared, highly-available storage location in the networksuch as network attached storage (NAS).

1.1.7 Load Balancer

Runtime and Core Services requires the use of a third-party load balancer to providea common access point for connections to the cluster and to distribute the loadacross all servers in the cluster. For detailed installation and configurationinstructions, see the product documentation for the installed load balancer.

1.1.8 Support of IPv6

Internet Protocol Version 6 (IPv6) is the next generation protocol for networkaddresses. IPv6 offers several advantages over the current protocol (InternetProtocol Version 4, or IPv4), and it will become the dominant protocol when IPv4addresses are depleted.

Runtime and Core Services supports Web service access using IPv6. The OpenTextAdministration Client can also be used to access Runtime and Core Services from anIPv6 environment.

1.2 Administering Runtime and Core Services

Runtime and Core Services is administered through the use of the OpenTextAdministration Client and the Runtime and Core Services Administration WebInterface. The administration of Runtime and Core Services is described in OpenTextRuntime and Core Services - Administration Guide (ELCS-AGD). The Runtime and CoreServices Administration Web Interface is described in section 10 "Runtime and Core

http://technet.microsoft.com/en-us/library/cc731844(WS.10).aspx






1.3 Runtime and Core Services Installation Checklist


Services Administration Web Interface" in OpenText Runtime and Core Services - Administration Guide (ELCS-AGD).

NetWeaver Administrator can also be used for administering and monitoring

Runtime and Core Services installed on a SAP NetWeaver application server. Formore information, see section 11 "Integrating Runtime and Core Services withNetWeaver Administrator" in OpenText Runtime and Core Services - AdministrationGuide (ELCS-AGD).

Installations, upgrades, and patches installed on Runtime and Core Services serverscan be recorded in the OpenText Solution Registry. For more information, seeOpenText Solution Registry - Configuration and Administration Guide (LDS-AGD).

1.3 Runtime and Core Services Installation Checklist

1. Log on as an administrator or ensure that your user account has administratorprivileges.

2. Install the required Java Runtime Environment (JRE) or a Java Development Kit(JDK). To verify your Java environment, use the command java -version or gothe Java Download Center at http://java.com/en/download/index.jsp.

3. Install and configure an application server as a single-server, horizontal cluster,vertical cluster, or mixed cluster. For more information, see “Installing Prerequisites for Windows” on page 15 or “Installing Prerequisites for UNIX orLinux” on page 49. OpenText recommends deciding how many nodes are inyour server configuration before installing Runtime and Core Services.

4. Create your database and database administrator account. Ensure that yourdatabase administrator has permission to create and update tables. OpenTextrecommends giving full database owner permissions to your database

administrator.

5. Install Runtime and Core Services. The installation process will create a Runtimeand Core Services administrator who will be responsible for administeringRuntime and Core Services. For more information, see “Installing on Windows”on page 15 or “Installing on UNIX or Linux” on page 49.

6. Perform post-installation tasks to optimize the application server. For moreinformation, see “Configuring Application Servers after Installation” on page 46 or “Configuring Application Servers after Installation” on page 68.

7. Secure your server using Secure Sockets Layer (SSL) before starting yourRuntime and Core Services server. For more information, see “Securing YourServer” on page 73.

8. Install the Microsoft Management Console (MMC) Administration Client onWindows. Once your Administration Client is installed, verify that yourRuntime and Core Services installation is correct by adding your server andsigning in using your otadmin credentials.

9. Configure Runtime and Core Services. See OpenText Runtime and Core Services - Administration Guide (ELCS-AGD). To configure Directory Services synchroniza-

http://java.com/en/download/index.jsp






tion and authentication, see OpenText Directory Services - Administration Guide(OTDS-AGD).




Chapter 2

Installing on Windows

This section covers the following topics for installing Runtime and Core Services onWindows servers:

• “Installing Prerequisites for Windows” on page 15

• “Installing Runtime and Core Services using Setup” on page 21

• “Installing Directory Services Externally” on page 37

• “Installing Runtime and Core Services Silently” on page 42

• “Configuring Application Servers after Installation” on page 46

Note: Upgrading an existing installation of Runtime and Core Services isdescribed in “Upgrading Runtime and Core Services and Directory Services”on page 107.

2.1 Installing Prerequisites for Windows

You must install an application server (Tomcat or NetWeaver) to use Runtime andCore Services. Application servers are set up under the Local System account forthe computer they are installed on by default. For more information, see “Installingand Configuring Tomcat on Windows” on page 16 or “Installing and ConfiguringNetWeaver on Windows” on page 19.

If you are installing a cluster, review “Prerequisites for Clustering on Windows” onpage 15 and “Configuring Runtime and Core Services Clusters” on page 77.

2.1.1 Prerequisites for Clustering on Windows

Clusterrequirements

If you are installing a Runtime and Core Services cluster, the followingrecommendations apply:

• The servers must access the RCS

workspace directory using the UniversalNaming Convention (UNC) path. Therefore, the service accounts must bechanged from a Local System account to a domain user account that has fullread/write access to the UNC path.

• The RCS workspace directory must not be hosted on any of the cluster nodes butmust be on a shared, highly-available storage location in the network such asnetwork attached storage (NAS).

• The installation must use a mapped drive if you are installing from a networkwith the OpenText Installation master setup. Do not use an unmapped UNCpath because the post-installation steps will fail to run.



Chapter 2 Installing on Windows


NetWeavercluster

requirements

If you are installing a NetWeaver cluster, Runtime and Core Services must beinstalled on the Primary Application Server node only. NetWeaver willautomatically deploy Runtime and Core Services on the other nodes. For moreinformation, see “Installing and Configuring NetWeaver on Windows” on page 19.

Tomcat verticalcluster

requirements

If you are installing a Tomcat cluster, you must install a load balancer to distributework evenly around the vertical cluster.

2.1.2 Installing and Configuring Tomcat on Windows

OpenText recommends the following steps to install and configure Tomcat beforeinstalling Runtime and Core Services on Windows:

• Disable User Account Control (UAC) settings to avoid prompts to allow theRuntime and Core Services installer to run. If you cannot disable UAC in yourenvironment, you may configure UAC to elevate without prompting or use theRun as administrator option. If UAC is enabled, being logged on with anAdministrator account is not sufficient.

For more information, see User Account Control Best Practices in the MicrosoftTechNet Library at http://technet.microsoft.com/en-us/library/ee679793(WS.10).aspx and the User Account Control Step-by-Step Guide at http://technet.microsoft.com/en-us/library/cc709691%28WS.10%29.aspx#BKMK_S2.

Important

You must configure UAC to Never notify for silent installations.

• Install Tomcat and prepare for vertical or horizontal clusters. For moreinformation, see “To Install Tomcat” on page 17.

• Configure Java options before installing Runtime and Core Services to optimizeperformance and prepare for Directory Services. For more information, see “To Configure Java Options for Optimal Performance” on page 17.

• Configure SSL for Tomcat and Java in order for Directory Services to trust Run-time and Core Services. For more information, see “To Configure Tomcat for Se-cure Sockets Layer (SSL)” on page 18.

Important

When enabling Secure Sockets Layer (SSL), OpenText recommends usinga server certificate from a Certificate Authority that has a root certificatethat is trusted by the JRE and is correctly installed in the keystore of the

JRE. For example, <JAVA _HOME >/lib/security/cacerts.

For detailed information on enabling SSL, see SSL Configuration How-to athttp://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html.

http://technet.microsoft.com/en-us/library/ee679793(WS.10).aspx


http://technet.microsoft.com/en-us/library/cc709691%28WS.10%29.aspx#BKMK_S2


http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html










2.1.2.1 To Install Tomcat

To install Tomcat:

1. Download the Tomcat software version 6.0.32 Windows Service Installer fromhttp://tomcat.apache.org/download-60.cgi.

2. Run apache-tomcat-6.0.32.exe to install the Tomcat software.

Tip: In the Choose Components window of the Apache Tomcat Setup,select a Normal type of install.

3. If you are installing a vertical cluster, download the Tomcat software version6.0.32 Windows zip from http://tomcat.apache.org/download-60.cgi andextract it to a <zip directory>. Copy all the Tomcat batch files from your <zip directory >\bin to <Tomcat _home >\bin.

The service.bat file in <Tomcat _home >\bin will be used to set up the

Windows services for the additional vertical cluster nodes. For moreinformation, see Clustering/Session Replication How-to athttp://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html.

4. If you are installing a horizontal cluster, install Tomcat on each server in thehorizontal cluster.

2.1.2.2 To Configure Java Options for Optimal Performance

To configure Java options for optimal performance:

1. Start the Monitor Tomcat tool from Programs > Apache Tomcat > MonitorTomcat or by starting bin\tomcat6w.exe from the <Tomcat _home > directory.

2. Click the Java tab.

3. In the Java Options area, include the following line to increase your permanentgeneration (permgen) memory:

-XX:MaxPermSize=256m

Important

This setting is required for OpenText Directory Services.

4. In the Java Options area, include the following lines to enable concurrentgarbage collection:

-XX:+CMSClassUnloadingEnabled

-XX:+UseConcMarkSweepGC

-XX:+CMSIncrementalPacing

http://tomcat.apache.org/download-60.cgi


http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html








Note: For more information, seehttp://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.html.

5. In the Java Options area, include the following lines to avoid writing INFO logmessages to the <Tomcat _home >/log/catalina.*.log:

-Dorg.apache.commons.logging.Log=com.opentext.ecm.components.logg

ing.wrappers.JCLBootLogger

-Drcs.console.loglevel=WARN

6. In the Initial memory pool box, specify 256 MB.

7. In the Maximum memory pool box, specify 1024 MB.

Important

This setting is required for OpenText Directory Services.

8. Click OK.

2.1.2.3 To Configure Tomcat for Secure Sockets Layer (SSL)

If you are using Secure Sockets Layer (SSL), change the ports Tomcat is using toallow Tomcat to automatically redirect users who access a page with a securityconstraint specifying that SSL is required. You might have to open ports on yourrouters to add ports for SSL.

To change or add Tomcat ports for Secure Sockets Layer:

1. From the <Tomcat _home >\conf directory, open server.xml in an editor.

2. After the line <Service

name="Catalina">, define an SSL connector port andchange the redirectPort to match the SSL connector port.

Example:

A "Connector" represents an endpoint by which requests

are received and responses are returned. Define a non-SSL

HTTP/1.1 Connector on port 8080

<Connector port="8080"

protocol="HTTP/1.1"connectionTimeout="20000"

redirectPort="8090" />

Define a SSL HTTP/1.1 Connector on port 8090


http://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.html









protocol="HTTP/1.1"

scheme="https"

secure="true"

SSLEnabled="true"

maxHttpHeaderSize="8192"

maxThreads="150"

acceptCount="100"

keystoreType="JKS"

sslProtocol="TLS"

clientAuth="false"

disableUploadTimeout="true"

enableLookups="false"

Parameters required for SSL, some are optional,

see the SSL documentation

keystoreFile="<path to .keystore file >"keystorePass="<password for the .keystore >"

truststoreFile="<yourTruststoreFile >"

keyAlias="<yourKeyalias >"

/>

3. Save the file and restart Tomcat.

2.1.3 Installing and Configuring NetWeaver on Windows

OpenText recommends adjusting NetWeaver settings before installing Runtime andCore Services on Windows.

Note: The NetWeaver installer creates the <sapsid>adm user that enables

interactive administration of the NetWeaver system. NetWeaver recommendslogging in as the <sapsid>adm user and using the NetWeaver Administrator todeploy or undeploy applications such as Runtime and Core Services. That is,do not log in as a Windows Administrator or UNIX root to administerNetWeaver.

RecommendedSettings

OpenText recommends adjusting NetWeaver settings in each Java instance profileand configuring additional settings before installing Runtime and Core Services.These adjustments will improve performance under heavy load and allow you towork with large documents.

Tip: Use the NetWeaver Administrator application and the NetWeaver Configtool to change NetWeaver settings. To start the Config Tool, use theconfigtool or consoleconfig script file in<SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. For more information, contact your NetWeaver administrator orconsult the NetWeaver help at http://help.sap.com.

http://help.sap.com/







To install NetWeaver:

• Follow the SAP NetWeaver documentation.

To adjust NetWeaver performance settings in the Java instance profile:

1. Allow an unrestricted content length for HTTP requests by inserting:icm/HTTP/max_request_size_KB

= -1

2. Disable caching for unfound objects by inserting:icm/HTTP/server_cache_0/ufo_codelist

= ""

3. Disable cache for SSL (assuming that the sequence number for the SSL port is 4)by inserting:icm/HTTP/server_cache_4/ufo_codelist = ""

4. Increase TIMEOUT and PROCTIMEOUT. For example: icm/server_port_0 =PROT=HTTP,PORT=50000,TIMEOUT=60,PROCTIMEOUT=1200

5. Increase icm/max_threads, icm/req_queue_len, icm/max_conn, andicm/max_sockets according to the NetWeaver documentation.

6. Disable SAP Java Script filter by inserting csi/enable = 0.

7. Improve performance of HTTP GET requests by deactivating Automatic HTTPresponse compression using the Configuring Rules for HTTP ResponsesCompression athttp://help.sap.com/saphelp_nw73/helpdata/en/4a/93b0d5d7cf38dbe10000000a42189b/frameset.htm.

Tip: You can also set the CompressedOthers property to false to improveperformance.

To disable caching of dynamic responses:

1. Using NetWeaver Administrator, select Configuration Management >Infrastructure > Java System Properties > Services > Web Container .

2. Change DisableDynamicResponseCaching from false to true.

To allow long running parallel HTTP request processing to avoid timeoutissues:

1. Using the NetWeaver Config tool, select cluster-data > template > services >http.

2. Increase FCAServerThreadCount (default value 5).

3. Select cluster-data > managers > Threadmanager.

4. Increase MaxThreadCount (default value 100).

5. Increase MaxRQSize (default 5000).

http://help.sap.com/saphelp_nw73/helpdata/en/4a/93b0d5d7cf38dbe10000000a42189b/frameset.htm







2.2 Installing Runtime and Core Services using Setup


To use Secure Sockets Layer (SSL) with NetWeaver:

• Configure the SSL port using the Configuring SSL procedures in the SAPNetWeaver Process Integration Security Guide at

http://help.sap.com/saphelp_nw73/helpdata/en/4a/015cc68d863132e10000000a421937/frameset.htm.

2.2 Installing Runtime and Core Services using

Setup

When you have installed all prerequisites, log on as a user with administrator rightsand start the Runtime and Core Services installation.

To install Runtime and Core Services:

1. In the Welcome window, click Next.

2. If you started the Runtime and Core Services installer directly, read the licenseagreement, select the I accept the terms in the License Agreement check box,and click Next.

3. In the Runtime and Core Services workspace window, enter the path to adirectory to be used for storing configuration files. Use the default or browse toan alternate location using Browse . Setup will create this directory if it doesnot already exist. Click Next.

Note: The RCS

workspace directory must be accessible by the file serversand the application server. OpenText recommends using a secure locationthat is backed up frequently.

http://help.sap.com/saphelp_nw73/helpdata/en/4a/015cc68d863132e10000000a421937/frameset.htm









4. In the Application Server window, select Apache Tomcat 6.0 or SAPNetWeaver CE 7.3. Click Next.

5. If you are using Tomcat as an application server, enter the following in theApache Tomcat Parameters window:

a. In the Path to the Apache Tomcat installation directory box, enter the pathto the Tomcat installation or browse the file system by clicking Browse .





b. In the Apache Tomcat service name box, enter the name of the Tomcatservice.

Note: The default (tomcat6) works with a standard Tomcat 6.0.32

installation. If problems occur, contact your Tomcat administrator.c. Click Next. The installer tries to find the Tomcat installation.

d. In the Runtime and Core Services cluster installation window, leave the

Install a vertical or horizontal RCS cluster check box cleared if you areinstalling a single Runtime and Core Services instance. Click Next.

Note: If you are installing a vertical cluster and you did not copy theTomcat batch files from the Tomcat zip directory, a warning will bedisplayed and you will not be allowed to continue with theinstallation. See step 3 in “To install Tomcat:” on page 17 and click OK to continue.





e. In the Runtime and Core Services cluster installation window, selectInstall a vertical or horizontal RCS cluster if you are installing a verticalcluster or a server in a horizontal cluster.

• Enter a root directory to store configuration information for additionalnodes on this machine. Use the default C:\Program Files\Apache

Software Foundation\Tomcat 6.0_instances\ or browse to analternate location using Browse . Setup will create this directory if itdoes not already exist.

• Enter the total number of nodes that will be installed in this cluster onthis machine.

Tip: To manually increase the total number of nodes in a clusterafter Runtime and Core Services is installed, see “To manuallyconfigure vertical cluster nodes after installing Runtime and CoreServices:” on page 79.

Note: The maximum vertical node count is limited by thehardware. OpenText recommends one node per processor formaximum performance up to a maximum of two nodes perprocessor.

• Click Next.





6. If you are using NetWeaver as an application server, enter the following in theApplication Server Parameters window:

a. In the Deployment Port box, enter the NetWeaver port to use; default:50004.

b. In the Deployment User box, enter the name of the NetWeaverAdministrator user.

c. In the Deployment Password box, enter the password of the NetWeaver

Administrator user.

d. In the Confirm Password box, reenter the password.

e. In the Service name box, enter the name of the service with whichNetWeaver Java EE instance is started. For example, SAP<sapsid >_00.

f. In the Path to the SAP NetWeaver CE instance directory box, enter the pathto the NetWeaver instance directory (\usr\sap\<sapsid >\J00\) or browsethe file system by clicking Browse .





g. Click Next. The installer tries to find the NetWeaver installation.

7. In the Authentication Method window, choose an authentication methodaccording to the table. Click Next.

Table 2-1: Authentication Methods

Select this check box When you want to use this authentica-

tion method

Install OpenText Directory Services Install OpenText Directory Services, cre-ating a Directory Services server. If this isa single node using Tomcat, the reposi-tory for storing OTDS user informationwill be deployed in the RCS workspace directory. In all other cases, you willspecify where the OTDS user informationwill be deployed.

Use an existing OpenText DirectoryServices installation

Install Runtime and Core Services, con-necting to an existing Directory Servicesserver.

Install Legacy authentication Install Runtime and Core Services, using

Legacy (CAP) authentication.





8. If you chose Install OpenText Directory Services in the AuthenticationMethod window, specify the Directory Services connection parameters.

Important

If you are installing Directory Services in NetWeaver or in a cluster, youwill supply these parameters to create an otds.dsd.properties filewhich will be used when you are installing Directory Servicesexternally. For more information, see “Installing Directory ServicesExternally” on page 37.

Table 2-2: New Directory Services Connection Parameters

Parameter Description

LDAP administration port The port that will be used for administra-tion traffic. (Default 4440).

LDAP communication port The port number that Directory Servicesuses for communication with your LDAPdirectory server. Also known as theLDAP Listener Port. (Default 389 for

Windows. Default 1389 for UNIX).






Configure LDAPS communication checkbox

Select this check box if you want to useLDAP over SSL (LDAPS) between

Runtime and Core Services and yourexternal Directory Services server. TheLDAPS communication port will becomeavailable. This check box is only availableif you are installing Directory Servicesexternally.

Important: It is not possible tochange the communication methodused to communicate with DirectoryServices after installation.

LDAPS communication port The port to use to communicate with theDirectory Server (OpenDS). (Default 636

for Windows. Default is 1636 for UNIX).This property is only available if you areinstalling Directory Services externallyand you are using LDAPS.

Directory Server install host The server name or IP address of theserver for storing Directory Servicesinformation. This is the fully-qualifiedname of the machine that will hostOpenDS. For example, WIN-ROAGTITHIV9.opentext.net . OpenDSwill be installed by the Directory Servicesinstaller. See “Installing DirectoryServices Externally” on page 37. Thisproperty is only available if you areinstalling Directory Services externally.

Important: Use a fully qualified hostname. Do not use localhost.

RCS load balancer URL The Runtime and Core Services load bal-ancer. This is an HTTP address of theload balancer. For example, http://WIN-ROAGTITHIV9:81. This property is onlyavailable if you are installing DirectoryServices externally.





Important

The protocol used by Directory Services when it is embedded inRuntime and Core Services is determined by the current <SSLEnabled>

setting in server.xml. HTTPS will be used if SSLEnabled=true. HTTPwill be used if <SSLEnabled=false> or is not set. OpenText recommendsusing secure SSL connections when connecting to a local DirectoryServices server.

Note: Setup will automatically create a Local RCS resource in theDirectory Services > Resources object to represent this OpenTextDirectory Services server. For more information about resources, seesection 4 "Resources" in OpenText Directory Services - Administration Guide(OTDS-AGD).

If you reinstall this OpenText Directory Services server, you will need to

change the connection properties of other Runtime and Core Servicesinstallations that connect to this OpenText Directory Services server. Formore information, see “Changing Directory Services Connection Properties” on page 117.

9. If you chose Use an existing OpenText Directory Services installation in theAuthentication Method window, specify the connection properties for yourexisting Directory Services server.





Table 2-3: Existing Directory Services Connection Parameters


Protocol HTTP(H) or HTTPS(S). The connectionprotocol used to communicate betweenthis new server and an existing DirectoryServices server. (Default HTTPS). ForHTTPS, the certificate in use by the Direc-tory Services server must be trusted bythis server. You may need to install thecertificate into the JRE's CACERTS file.

Server name The name of the physical machine of yourexisting Directory Services server. Thiscan be the name of the physical machineor the IP address.

Port Default is 8443 for HTTPS and 8080 for

HTTP. These ports must correspond tothe ports defined for your Directory Ser-vices server.

Resource ID This is the resource identifier of the re-source that was created in Directory Ser-vices to represent the current installationof Runtime and Core Services. You mustcreate this resource in Directory Servicesbefore installing Runtime and Core Ser-vices. For more information on configur-ing resources, see section 4 "Resources"in OpenText Directory Services - Admini-stration Guide (OTDS-AGD).





10. If you chose Install Legacy Authentication in the Authentication Method window, there are no additional parameters to configure.

11. In the Runtime and Core Services Administrator window, enter a password for

the global RCS Administrator User name ([email protected] for OpenTextDirectory Services authentication and otadmin for Legacy authentication).

Note: The RCS Administrator User name password must be a minimumof eight characters. Runtime and Core Services ignores leading and trailingblanks in the password.

The default user ([email protected] or otadmin) is created by the Runtimeand Core Services installation when you are installing OpenText DirectoryServices authentication or Legacy authentication.

If you are connecting to an existing Directory Services installation, you will notbe asked for the RCS Administrator user name and password.

The following users and groups are added to the RCSAdmin role during theRuntime and Core Services installation when OpenText Directory Servicesauthentication is selected:

[email protected] The default RCS administrator.

[email protected] The default group containing all Open-Text administrators [email protected] . This group is in-tended to be used for administrators whocan administer all OpenText productsincluding Directory Services.





[email protected] The default group containing all RCSadministrators. This group that can onlyadminister Runtime and Core Services.

The otadmin user is added to the RCSAdmin role when Legacy authentication isselected.

12. In the Database Selection window, select the Use external database system check box and chose either MS SQL Server or Oracle. Click Next.

Important

It is only valid to clear the Use external database system check box forthe following scenarios:

Remote Document Pipeline In this scenario, Runtime and Core Ser-vices hosts a service that is used to feeddocuments into the Document Pipelineremotely.

Archive Cache Server In this scenario, Archive Web Servicesdelivers functionality for remote archiv-ing.

Note: If you clear the Use external database system check box and clickNext, an information window will open warning you that an internaldatabase is in use. You will not be prompted for Database parameters.





13. In the Database Parameters window, specify the connection settings for thedatabase:

a. In the Server Name box, enter the name of the computer hosting the

database. Do not use localhost. If you are using an Microsoft SQL Servernamed instance, enter the named instance as<server _name >\<instance _name >.

b. In the Port box, enter the port; default: 1433 (Microsoft SQL Server), 1521 (Oracle Database).

Note: If you are using an Microsoft SQL Server named instance, youmust configure static ports for a named instance because Runtime andCore Services does not support dynamic ports.

To configure static ports for a named instance:

1. In Microsoft SQL Server 2008 > Configuration Tools > SQL

Server Configuration Manager, expand SQL Server NetworkConfiguration.

2. Select Protocols for <instance name>.

3. Select TCP/IP and right-click to select Properties.

4. In the IP Addresses tab, clear TCP Dynamic Ports for all IP areasand enter a static port number in the TCP Port that does notconflict with the default named instance port. For example, use1100.

5. Restart the service as instructed.

c. In the Database Name (Microsoft SQL Server) or the Oracle Service Name (Oracle Database), enter the name of the database to be used.

Notes:

• The database entered in Database name has to already exist for theconnection setting to work.

• If you are connecting to an Oracle Database or an Oracle RACsystem (Real Application Clusters), do not use the System Identifier(SID) for the Oracle Service Name.





d. In the Database User Name box, enter the name of the database user withadministrative access to the specified database.

Note: This database user must have CREATE TABLE privileges. If youare specifying an Oracle Database, the Oracle Database user requiresCREATE TABLE, CREATE VIEW , CREATE SEQUENCE, and CREATE SESSION privileges.

e. In the Password box, enter the password of the database user.

Click Next.





14. If the total number of vertical nodes to be installed on this machine is greaterthan 1 or this is an additional server in a horizontal cluster, the ClusterInstallation window opens with an information message. You shouldunderstand your port configuration to ensure that the ports in each server.xml file do not conflict with other software on this machine. For more information,see “Configuring Automatic Failover for Vertical Clusters” on page 80. ClickNext.





15. In the Ready to Install window, click Install. The installation process takesplace.

16. When the installation procedure has finished, click Finish.

17. If this installation requires Directory Services installed externally, see “InstallingDirectory Services Externally” on page 37.



2.3 Installing Directory Services Externally


Important

Ensure that OpenDS is started before starting your application server.

18. Start your application server.

If you are using a Tomcat application server, you must start Tomcat manuallyonce after the installation. You must restart vertical Tomcat nodes sequentiallyand you must wait for each node to finish starting before starting the next node.Runtime and Core Services will continue to start up after Tomcat has started.After this initial manual startup, Tomcat nodes will start correctly in sequenceautomatically.

Tip: Use your Windows Task Manager to determine if Runtime and CoreServices has completed startup or monitor the rcs.log files in<Tomcat _home >\logs to determine if all RCS services have started

successfully. Thercs.log

will indicateSTARTING RUNLEVEL 9 : MAX

.If you are using a NetWeaver application server, use the following steps:

a. Open a command window and change to the deploy tool directory. Forexample, cd

<RCS workspace >\staging\deploy\tool.

b. Undeploy the old SCA file if it exists. For example, run

eardeployer.bat -operation=undeploy -user=<deployment user >

-password=<password of deployment user >

Tip: If the undeploy succeeded, the application directory,usr\sap\<sapsid >\J00\j2ee\cluster\apps\opentext.com will beempty.

c. Recreate the SCA file by running earcreator.bat.

d. Deploy the new SCA file using eardeployer.bat. For example,

run eardeployer.bat -operation=deploy -user=<deployment user >


19. OpenText recommends that you back up Runtime and Core Services afterinstalling. For more information, see “Backing Up and Restoring Runtime andCore Services” on page 105.

2.3 Installing Directory Services ExternallyIf you are installing Directory Services in NetWeaver or in a cluster, you will need toinstall Directory Services externally using the master installer or the DirectoryServices msi after Runtime and Core Services has been installed. This installsOpenDS as a service to manage user and group information. During the Runtimeand Core Services installation, an otds.dsd.properties file is created in the RCS

workspace directory. This file is required by the Directory Services installer and





must be copied from your Runtime and Core Services server to the server whereyou are installing Directory Services.

To install Directory Services externally:

1. On your Runtime and Core Services server, locate the otds.dsd.properties file and copy it to a known location on the server where you will installDirectory Services externally or copy it to a read-only file share that is accessibleover the network.

2. On the server where you will install Directory Services externally, start theOpenText Directory Services 10.2.1 installation and click Next in the Welcome window.

3. In the License Agreement window, read the license agreement and click Agree to accept the license agreement.

4. In the Directory Server Install Location window, enter the location where youwould like to install a Directory Services server (OpenDS) or browse to anexisting location using Browse .

Important

Do not use the RCS workspace directory.





5. In the Directory Services Connection Properties window, enter the location ofotds.dsd.properties created by the Runtime and Core Services installation orbrowse to a location using Browse .

Note: If the OpenText Directory Services 10.2.1 installer detects thatOpenDS is already installed it will not overwrite the existing installation.

Tip: The Runtime and Core Services installation creates this file in the RCS

workspace directory. You must copy this file from your Runtime and CoreServices server to your external Directory Services server or copy it to a fileshare accessible across the network.





6. If you selected Configure LDAPS communication when you installed Runtimeand Core Services with Directory Services, configure your secure access fromDirectory Services to OpenDS.

Select the directory that contains the .keystore file that contains the certificatethat has to be used by LDAPS protocol and enter the password of the.keystore file. This window will not appear if you did not select ConfigureLDAPS communication between Directory Services and OpenDS.





7. In the OpenText Directory Services Ready to Install window, click Install.

8. Click Finish and confirm that the OpenDS service has been startedautomatically.





2.4 Installing Runtime and Core Services Silently

You can use Windows Installer to perform silent installations of Runtime and CoreServices. The standard msiexec.exe command line options are supported. Youshould enable logging when performing silent installations.

For example, use /l*v

<path >\core_services-10.2.1.silent.log.

Important

You must configure UAC to Never

notify for silent installations.

Tip: Enclose parameter values in double quotes if they contain spaces.

You must specify the following custom properties as part of the silent installation:

FILESTORE or UPGRADEWORKSPACEThe path to the RCS

workspace directory. If this is a new installation, use theFILESTORE parameter. If this is an upgrade and you do not want to overwrite theexisting filestore directory, use the UPGRADEWORKSPACE parameter.

APPSRVTYPE

The application server type. Choose Tomcat or NetWeaver.

If APPSRVTYPE=TOMCAT, supply the following parameters:

SERVICENAME The name of the Tomcat service. For example,SERVICENAME=tomcat6 .

TOMCAT The path to the <Tomcat _home > directory. For ex-ample, TOMCAT="C:\Program Files\Apache

Software Foundation\Tomcat 6.0\".

APPSRVPATH The path to the application server home directory.If APPSRVTYPE=TOMCAT, this is the same as theTOMCAT property. For example, APPSRVPATH="C:\Program Files\Apache

Software Foundation\Tomcat 6.0\".

If APPSRVTYPE=NETWEAVER, supply the following parameters:

CSAPPSRVPORT The NetWeaver deployment port.

CSAPPSRVUSER The NetWeaver deployment user. This is the Net-Weaver Administrator.

CSAPPSRVPASSWORD The password of the NetWeaver deployment user.

CSAPPSRVDEPLOYDIR The path to the NetWeaver instance directory.

NETWEAVERSERVICE The name of the NetWeaver service. For example,NETWEAVERSERVICE=SAPCE1_00.





CSCONFIGCLUSTER

Whether or not this installation is a cluster installation or a single Runtime andCore Services instance. Enter CSCONFIGCLUSTER=true if this will be a vertical orhorizontal cluster on Tomcat. Enter CSCONFIGCLUSTER=false if this is a single

instance on Tomcat.

Note: This parameter is not required for NetWeaver installations.

If CSCONFIGCLUSTER=true, supply the following parameters:

NUMNODESTHISMACHINE If CSCONFIGCLUSTER=true is supplied, thisparameter is required to indicate how many nodeswill be installed. Set NUMNODESTHISMACHINE=<n >where <n> is the total number of nodes to beinstalled in this instance. IfCSCONFIGCLUSTER=true but the number of nodesisn't specified, the installer will assume that there isone node in this instance. If

CSCONFIGCLUSTER=false or not supplied,NUMNODESTHISMACHINE is not required.

Note: The maximum vertical node count islimited by the hardware. OpenText recom-mends one node per processor for maximumperformance up to a maximum of two nodesper processor.

NODESROOTDIR If CSCONFIGCLUSTER=true is supplied, this pa-rameter can be used to indicate that the installershould place vertical cluster instances in an exist-ing directory. If this parameter is not supplied andCSCONFIGCLUSTER=true , the installer will create a

default directory, <Tomcat _home >_instances tostore vertical cluster instances. The value for thisparameter is added to boot.properties ascs.nodes.dir=<nodesrootdir >. IfCSCONFIGCLUSTER=false or not supplied,NODESROOTDIR is not required.

CSAUTHENTICATIONMETHOD

Defaults to OTDS. Set to CAP for legacy authentication. Set to REMOTE_OTDS whenconnecting to an existing Directory Services server.

When CSAUTHENTICATIONMETHOD=OTDS, supply the following parameters:

OTDS_DIRECTORY_SERVER_ ADMIN_CONNECTOR_PORT

LDAP administration port. Default is 4440. Thisparameter is not required if you are accepting thedefault.

OTDS_DIRECTORY_SERVER_COMM_

PORT

LDAP communication port. Default is 389. Thisparameter is not required if you are accepting thedefault.





When CSAUTHENTICATIONMETHOD=REMOTE_OTDS, supply the followingparameters:

OTDS_URL <Protocol>://<Server name> : < port> of the existing

Directory Services server where < protocol> can beHTTP or HTTPS. Required whenCSAUTHENTICATIONMETHOD=REMOTE _OTDS.

OTDS_EXISTING_RESOURCE Resource identifier supplied when component re-source was created in Directory Services. Requiredwhen CSAUTHENTICATIONMETHOD=REMOTE _OTDS.

CSPASSWORD

The Runtime and Core Services administrator account password. CSPASSWORD isnot needed for a silent upgrade or when connecting to an existing OTDS server;the existing CSPASSWORD will be used.

Note: The RCS Administrator User name password must be a minimum ofeight characters. Runtime and Core Services ignores leading and trailingblanks in the password.

CSDBNEEDED

Set to true if an external database is being used. This parameter must be set totrue if this is a clustered installation.

Note: CSDBNEEDED must be set to true if CSCONFIGCLUSTER is set to true.

If CSDBNEEDED=true, supply the following parameters:

CSDBTYPE The type of database. You can choose MSSQL orOracle.

CSDBSERVER The database server name. To specify a SQL Servernamed instance, use the following syntax:

<Server name >\<Instance name >.

CSDBPORT The database server port. For SQL Server, thedefault is 1433. For Oracle Database, the default is1521.

Note: If you are using an Microsoft SQLServer named instance, you must configurestatic ports for a named instance because Run-time and Core Services does not support dy-namic ports.

CSDBNAME The service name of the database.

Note: If you are connecting to an Oracle Da-tabase or an Oracle RAC system (Real Appli-cation Clusters), do not use the System Identi-fier (SID) for the Oracle Service Name.





CSDBUSER The name of the default user account for the data-base.

CSDBPASSWORD The password of the default user account for the

database.

Note: The Apache Tomcat service should be stopped for the duration of theinstallation process. You should schedule the installation for a time that has theleast impact on other applications that are also using Tomcat.

The following command shows an example of a silent installation of Runtime andCore Services with legacy authentication:

Example:

msiexec /norestart /qn /package path\core_services-10.2.1.msi /l*v

path\core_services-10.2.1.msi.log

FILESTORE=path\workspace\ APPSRVTYPE=Tomcat SERVICENAME=tomcat6

TOMCAT="C:\Program Files\Apache Software Foundation\Tomcat 6.0\"

APPSRVPATH="C:\Program Files\Apache Software Foundation\Tomcat 6.0\"

CSAUTHENTICATIONMETHOD="CAP" CSPASSWORD=password CSDBNEEDED=true

CSDBTYPE=MSSQL CSDBSERVER=server-name CSDBPORT=1433

CSDBNAME=rcsdb CSDBUSER=rcsdbuser CSDBPASSWORD=password2

The following command shows an example of a silent installation of Runtime andCore Services installation with a new Directory Services server:

Example:






CSAUTHENTICATIONMETHOD="OTDS"

OTDS_DIRECTORY_SERVER_ ADMIN_CONNECTOR_PORT=4440

OTDS_DIRECTORY_SERVER_COMM_PORT=389 CSPASSWORD=password

CSDBNEEDED=true CSDBTYPE=MSSQL CSDBSERVER=server-name CSDBPORT=1433


The following command shows an example of a silent installation of Runtime andCore Services installation with an existing Directory Services server:

Example:










CSAUTHENTICATIONMETHOD="REMOTE_OTDS" OTDS_URL="HTTP://otds-s-2k8-

99.domain.net:80"

OTDS_EXISTING_RESOURCE="fcd84f5c-d606-43bc-bdf9-8ffeb32c2516"

CSDBNEEDED=true CSDBTYPE=MSSQL CSDBSERVER=server-name CSDBPORT=1433


The following command shows an example of a silent installation of Runtime andCore Services with a vertical cluster with three nodes:

Example:

msiexec /norestart /qn /package path\core_services-10.2.1.msi

/l*v path\core_services-10.2.1.msi.log FILESTORE=path\workspace\

APPSRVTYPE=Tomcat

SERVICENAME=tomcat6 TOMCAT="C:\Program Files\Apache Software

Foundation\Tomcat 6.0\"


CSAUTHENTICATIONMETHOD="CAP" CSPASSWORD=password CSDBNEEDED=true

CSDBTYPE=MSSQL CSDBSERVER=server-name CSDBPORT=1433CSDBNAME=rcsdb CSDBUSER=rcsdbuser CSDBPASSWORD=password2

CSCONFIGCLUSTER="true" NUMNODESTHISMACHINE="3"

2.5 Configuring Application Servers after Installation

You should adjust the application servers after Runtime and Core Services has beeninstalled.

Note: Refer to section 13 "Troubleshooting Runtime and Core Services" inOpenText Runtime and Core Services - Administration Guide (ELCS-AGD) for helptroubleshooting common performance problems.

By default, multicasting is enabled to support clustering if you have installedRuntime and Core Services with an external database. Therefore, Runtime and CoreServices will create some network traffic which is harmless and unnecessary ifclustering is not in use. If you want to reduce your network traffic, you can enableloopback to disable multicasting on Tomcat.

To enable loopback on Tomcat to reduce network traffic:

1. From the <Tomcat _home >\lib directory, open boot.properties in an editor.

2. Change the value of the cs.use.loopback.smessage parameter to true. Forexample:cs.use.loopback.smessage=true


To permit the application server to access the RCS workspace directory:

1. In the file system, browse to the RCS workspace directory specified in step 3 on page 21.





2. Open the context menu of the directory and click Sharing and Security.

3. On the Security tab, change each service account from a local user account to adomain user account that has full read/write access to the UNC path to the RCS

workspace directory.

Important

All user accounts and passwords must be the same for all nodes on allmachines in a cluster.

4. On the Security tab, select the domain user that will be running the applicationserver, and grant Full Control.

5. Click OK.






Chapter 3

Installing on UNIX or Linux

This section covers the following topics for installing Runtime and Core Services onUNIX or Linux servers:

• “Installing Prerequisites for UNIX or Linux” on page 49

• “Installing Runtime and Core Services” on page 56

• “Installing Directory Services Externally” on page 63

• “Installing Runtime and Core Services Silently on UNIX or Linux” on page 65

• “Configuring Application Servers after Installation” on page 68

Note: Upgrading an existing installation of Runtime and Core Services isdescribed in “Upgrading Runtime and Core Services and Directory Services”on page 107.

3.1 Installing Prerequisites for UNIX or Linux

You must install and configure an application server to use Runtime and CoreServices. For more information, see “Installing and Configuring Tomcat on UNIX orLinux” on page 50 or “Installing and Configuring NetWeaver on UNIX or Linux” onpage 54.

If you are installing a cluster, review “Prerequisites for Clustering on UNIX orLinux” on page 49 and “Configuring Runtime and Core Services Clusters” onpage 77.

3.1.1 Prerequisites for Clustering on UNIX or Linux

Clustering onUNIX or Linux

If you are installing a Runtime and Core Services cluster, the followingrecommendations apply:

• The shared RCS

workspace directory must not be hosted on any of the clusternodes but must be on a shared, highly available storage location in the networksuch as network attached storage (NAS).

• The servers must access the shared RCS workspace directory in a network filesystem, for example, NFS.

• The mount points for the shared RCS

workspace directory must be identical onall nodes.



Chapter 3 Installing on UNIX or Linux


NetWeaverClusters on

UNIX or Linux

If you are installing a NetWeaver cluster, Runtime and Core Services must beinstalled on the Primary Application Server node only. NetWeaver willautomatically deploy Runtime and Core Services on the other nodes. For moreinformation, see “Installing and Configuring NetWeaver on UNIX or Linux” on

page 54.

3.1.2 Installing and Configuring Tomcat on UNIX or Linux

OpenText recommends the following steps to install and configure Tomcat beforeinstalling Runtime and Core Services on UNIX or Linux:

• Install a supported UNIX or Linux operating system and create the user <otuser >and group <otgroup> to be used with Tomcat. See “To Install and ConfigureTomcat” on page 51.

• Configure Java options before installing Runtime and Core Services to optimizeperformance and prepare for Directory Services. See “To Configure Java Options

for Optimal Performance” on page 52.

• Configure SSL for Tomcat and Java in order for Directory Services to trust Run-time and Core Services. See “To Configure Tomcat for Secure Sockets Layer (SSL)” on page 52.

Important

When enabling Secure Sockets Layer (SSL), OpenText recommends usinga server certificate from a Certificate Authority that has a root certificatethat is trusted by the JRE and is correctly installed in the keystore of the

JRE. For example, <JAVA _HOME >/lib/security/cacerts.

For detailed information on enabling SSL, see SSL Configuration How-to athttp://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html.

• Start Tomcat as <otuser > after installing Runtime and Core Services. Runtimeand Core Services provides two scripts for your use: <Tomcat _home > /bin/ot-startnode.sh and <Tomcat _home >/bin/ot-shutnode.sh. These scripts set en-vironment variables before invoking the Tomcat startup.sh and shutdown.sh scripts and can be used to issue Tomcat start and stop commands. See “ToStart or Stop Tomcat Using Scripts” on page 53.

Important

Do not use Tomcat startup.sh and shutdown.sh scripts to start or stopTomcat.






3.1.2.1 To Install and Configure Tomcat

To install Tomcat:

1. Download the Apache Tomcat software version 6.0 fromhttp://tomcat.apache.org/download-60.cgi.

Important

Do not use the Solaris Package Manager. The Solaris Package Managerinstalls Tomcat partially in /usr/tomcat6 and partially in/var/tomcat6. The Runtime and Core Services installer assumes thatTomcat is installed within a single directory.

2. If necessary, create the operating system installation user <otuser > and group<otgroup> to be used with Tomcat. Ensure that <otgroup> is configured as theprimary group for <otuser >. For more information, see your UNIX or Linux op-erating system documentation.

Important

Do not use root. It can create security vulnerabilities when running theapplication server using a root (or equivalent) user.

When configuring a horizontal cluster with a shared RCS

workspace directory, ensure the Tomcat user and group have the same useridentifier (UID) and group identifier (GID) on all machines in thecluster.

3. Log on as this user.

4. Install the Tomcat software according to the documentation.

To configure special settings for IBM AIX:

1. Extract the aix_tomcat_endorsed.zip from the platform specific installerdirectory under tomcat_patch to the <Tomcat _home >/endorsed directory.

2. If the owner and group of the unzipped files is not the same as the applicationserver process user and group, change them using the chown and chgrp commands.







3.1.2.2 To Configure Java Options for Optimal Performance

To configure Java options for optimal performance:

1. In the <Tomcat _home >/bin/setenv.sh file created by the Runtime and CoreServices installation, edit the following Java options to optimize memory pooland heap size for your operating system:

CATALINA_OPTS="-Dcs.instancename=node001 -XX:MaxPermSize=256m –

Xmx1024M $CATALINA_OPTS"

2. For Solaris and HP-UX, include -d64 in CATALINA_OPTS in<Tomcat _home >/bin/setenv.sh. For example,

CATALINA_OPTS="-Dcs.instancename=node001 -XX:MaxPermSize=256m –

Xmx1024M -d64 $CATALINA_OPTS"

3. In the <Tomcat _home >/bin/setenv.sh file created by the Runtime and CoreServices installation, edit the following Java options to avoid writing INFO logmessages to the <Tomcat _home >/log/catalina.*.log:

CATALINA_OPTS="-

Dorg.apache.commons.logging.Log=com.opentext.ecm.components.loggi

ng.wrappers.JCLBootLogger $CATALINA_OPTS"

4. Restart Tomcat.

3.1.2.3 To Configure Tomcat for Secure Sockets Layer (SSL)

You may have to change the ports that Tomcat is using to allow Tomcat toautomatically redirect users who access a page with a security constraint specifyingthat SSL is required. You may have to open ports on your routers in order to addports for SSL.

To configure Tomcat for Secure Sockets Layer:

1. From the <Tomcat installation >/conf directory, open server.xml in aneditor.

2. After the line <Service name="Catalina">, change the file according to thisexample:

A "Connector" represents an endpoint by which requests

are received and responses are returned. Define a non-SSLHTTP/1.1 Connector on port 8080


protocol="HTTP/1.1"

connectionTimeout="20000"

redirectPort="8090" />





Define a SSL HTTP/1.1 Connector on port 8090


protocol="HTTP/1.1"

scheme="https"secure="true"

SSLEnabled="true"

maxHttpHeaderSize="8192"

maxThreads="150"

acceptCount="100"

keystoreType="JKS"

sslProtocol="TLS"

clientAuth="false"

disableUploadTimeout="true"

enableLookups="false"

Parameters required for SSL, some are optional,see the SSL documentation

keystoreFile="<path to .keystore file >"

keystorePass="<password for the .keystore >"

truststoreFile="<yourTruststoreFile >"

keyAlias="<yourKeyalias >"

/>


3.1.2.4 To Start or Stop Tomcat Using Scripts

RCS scripts, ot-startnode.sh and ot-shutnode.sh in <Tomcat _home >/bin, mustbe used to start and stop RCS nodes.

Important

If you have not installed the most current RCS patch, you must start RCSnodes sequentially for the first time only and you must wait for each node tofinish starting before starting the next node.

See the Runtime and Core Services Release Notes athttps://knowledge.opentext.com/knowledge/cs.dll/fetch/2001/3551166/14627590/13609768/customview.html?func=ll&objId=13609768&objAction=browse for additional information about starting RCS nodes when installingthe most recent RCS patch.

Versions of the scripts are also available in the<Tomcat _home >_instances/inst<nnn >/bin directories. These node-specific scriptsdo not need a inst<nnn > parameter. These scripts call the common scripts found in<Tomcat _home >/bin. For example, <Tomcat _home >_instances/inst003/bin/ot-startnode003.sh will start the inst003 RCS node.










To start or stop Tomcat using the Runtime and Core Services scripts:

1. Use the ot-startnode.sh command to start your Runtime and Core Servicesnode supplying inst<nnn > where <nnn> is the number of the RCS node. For

example, <Tomcat _home >/bin/ot-startnode.sh inst001 will start theinst001 RCS node.

2. Use the ot-shutnode.sh command to stop your RCS node and kill the Tomcatprocess. For example, <Tomcat _home >/bin/ot-shutnode.sh inst001 will shutdown the inst001 RCS node and kill the Tomcat process in 60 seconds.

Note: The Tomcat process will be killed 60 seconds after the shutnode.sh command is used. This is the RCS default delay. This delay is used toensure that complex RCS installations are fully stopped before the Tomcatprocess is killed.

Tip: The RCS scripts automatically kill the Tomcat process after the delay.If you are using other non-RCS scripts to stop Tomcat, you must kill the

Tomcat process using the kill <processid > UNIX command aftershutting down RCS. Use ps -ef | grep java to find the < processid>.

3. To kill the Tomcat process within 5 seconds, supply the -force option. This isthe Tomcat default delay. For example, <Tomcat _home >/bin/ot-startnode.sh

inst001 -force will shut down the inst001 RCS node and kill the Tomcatprocess in 5 seconds.

4. To override the default delay time, supply the <nn > -force option with aspecific delay time. For example, <Tomcat _home >/bin/ot-startnode.sh

inst001 30 -force will shut down the inst001 RCS node and kill the Tomcatprocess in 30 seconds.

3.1.3 Installing and Configuring NetWeaver on UNIX or LinuxOpenText recommends adjusting NetWeaver settings before installing Runtime andCore Services on UNIX or Linux.

Note: The NetWeaver installer creates the <sapsid>adm user that enablesinteractive administration of the NetWeaver system. NetWeaver recommendslogging in as the <sapsid>adm user and using the NetWeaver Administrator todeploy or undeploy applications such as Runtime and Core Services. That is,do not log in as a Windows Administrator or UNIX root to administerNetWeaver.

RecommendedSettings

OpenText recommends adjusting NetWeaver settings in each Java instance profileand configuring additional settings before installing Runtime and Core Services.These adjustments will improve performance under heavy load and allow you towork with large documents.

Tip: Use the NetWeaver Administrator application and the NetWeaver Configtool to change NetWeaver settings. To start the Config Tool, use the





configtool or consoleconfig script file in<SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. For more information, contact your NetWeaver administrator orconsult the NetWeaver help at http://help.sap.com.

To install NetWeaver:

• Follow the SAP NetWeaver documentation.

To adjust NetWeaver performance settings in the Java instance profile:

1. Allow an unrestricted content length for HTTP requests by inserting:icm/HTTP/max_request_size_KB = -1

2. Disable caching for unfound objects by inserting:icm/HTTP/server_cache_0/ufo_codelist = ""

3. Disable cache for SSL (assuming that the sequence number for the SSL port is 4)

by inserting:icm/HTTP/server_cache_4/ufo_codelist

= ""

4. Increase TIMEOUT and PROCTIMEOUT. For example: icm/server_port_0 =PROT=HTTP,PORT=50000,TIMEOUT=60,PROCTIMEOUT=1200

5. Increase icm/max_threads, icm/req_queue_len, icm/max_conn, andicm/max_sockets according to the NetWeaver documentation.

6. Disable SAP Java Script filter by inserting csi/enable = 0.

7. Improve performance of HTTP GET requests by deactivating Automatic HTTPresponse compression using the Configuring Rules for HTTP ResponsesCompression at

http://help.sap.com/saphelp_nw73/helpdata/en/4a/93b0d5d7cf38dbe10000000a42189b/frameset.htm.

Tip: You can also set the CompressedOthers property to false to improveperformance.

To disable caching of dynamic responses:

1. Using NetWeaver Administrator, select Configuration Management >Infrastructure > Java System Properties > Services > Web Container .

2. Change DisableDynamicResponseCaching from false to true.

To allow long running parallel HTTP request processing to avoid timeout

issues:

1. Using the NetWeaver Config tool, select cluster-data > template > services >http.

2. Increase FCAServerThreadCount (default value 5).

3. Select cluster-data > managers > Threadmanager.













4. Increase MaxThreadCount (default value 100).

5. Increase MaxRQSize (default 5000).

To use Secure Sockets Layer (SSL) with NetWeaver:

• Configure the SSL port using the Configuring SSL procedures in the SAPNetWeaver Process Integration Security Guide athttp://help.sap.com/saphelp_nw73/helpdata/en/4a/015cc68d863132e10000000a421937/frameset.htm.

3.2 Installing Runtime and Core Services

When you have installed all prerequisites start the Runtime and Core Servicesinstallation.

Important

The user accounts specified during installation of NetWeaver and Runtimeand Core Services must be the same. The NetWeaver installation creates a<sapsid>adm. Specify this user when asked by Runtime and Core Servicesinstallation for Installation user name.

To set up the environment for Runtime and Core Services installation:

1. Log on as root to the computer on which to install Runtime and Core Services.

2. Set the JAVA_HOME environment variable to point to the base directory of your Java installation. For example, JAVA_HOME=/usr/java/jre6.

3. If you are using a Tomcat application server, set the CATALINA_HOME environment variable to the base directory of your Tomcat installation.

4. Make sure that JRE 1.6 is included in the PATH environment variable.

Tip: Use java –version to verify your JAVA version. If the result is“command not found” or if the version displayed is not 1.6, update thePATH variable to include the location of a valid JRE. For example:

PATH=/usr/java/jre6/bin:$PATH

5. For IBM AIX, HP-UX , or Solaris, make sure that /usr/sbin is included in thePATH environment variable.

For Linux, make sure that/bin

is included in thePATH

environment variable.Tip: Use echo

$PATH to verify your path.

To install Runtime and Core Services:

1. Run the setup script by typing ./mastersetup or ./setup.sh. To continuewhen using the master setup, press n, ENTER.










2. Read the license agreement. To accept it, press a or y depending on which setupscript you are using, and press ENTER.

3. If you are using the master setup, select Directory Services from the

Deployment Scenarios to install Runtime and Core Services 10.2.1 withOpenText Directory Services and press n, ENTER until all selections have beenmade.

Note: Other deployment scenarios, such as Enterprise

Library

Services, will also indicate that Runtime and Core Services 10.2.1 isrequired as a component of Core Services and Other Components.

4. If you are using the master setup, enter the following global parameters andpress i, ENTER to install:

Global

parameter

1/2

"Installation

user

name"

Enter the name of an existing UNIX or Linux user under which theapplication server process runs and confirm with ENTER.

Global parameter 2/2 "Installation group name"

Enter the name of an existing UNIX or Linux group under which theapplication server process runs and confirm with ENTER. The group has toexist and the Installation User must be a member of this group.

5. >> Parameter APPSRVTYPE:

To select Apache Tomcat 6.0 as the application server , press T, ENTER. Toselect SAP NetWeaver CE 7.3 as the application server, press N, ENTER.

6. >> Parameter TOMCAT:

If you are using Tomcat, enter the path to the <Tomcat _home > directory andpress ENTER. The default for TOMCAT is CATALINA_HOME.

7. >>

Parameter

FILESTORE:

Enter the path to the RCS workspace directory for the configuration files andconfirm with ENTER. Default is /opentext/rcs/workspace.

Note: The RCS workspace directory must be created for cluster installa-tions and for all NetWeaver installations before installing Runtime andCore Services. The same mount point to the RCS workspace directory is re-quired for all cluster nodes. The RCS workspace directory will be created ifthis is a single instance of Runtime and Core Services being installed onTomcat.

CautionDo not use the application server's webapps directory!

8. >>

Parameter

CSCONFIGCLUSTER:





To indicate that this node is part of a vertical or horizontal Tomcat cluster, pressy, ENTER. If this is a single node installation, press n, ENTER, and go to step 11.

Note: This parameter is not required when APPSRVTYPE

= N, even you are

creating a NetWeaver cluster.9. >>

Parameter

NUMNODESTHISMACHINE:

If you entered y to indicate that this was a vertical or horizontal clusterinstallation in step 8, enter the total number of nodes on this machine. Forexample, if this is a single node in a horizontal cluster, enter 1. If this is a verticalcluster, enter a number from 1-999 to indicate how many nodes will be in thevertical cluster.

Note: The maximum vertical node count is limited by the hardware.OpenText recommends one node per processor for maximum performanceup to a maximum of two nodes per processor.

10. >>

Parameter

NODESROOTDIR:

If you entered y to indicate that this was a vertical or horizontal cluster nodeinstallation in step 8, enter the path to the Cluster

Nodes

Configuration directory to contain configuration and service information for each cluster nodeor accept the default and confirm with ENTER.

11. >> Parameter CSDBNEEDED:

To use an external database with Runtime and Core Services, press y, ENTER.To continue without using an external database for Runtime and Core Services,press n, ENTER.

Note: If you entered y for the CSCONFIGCLUSTER parameter, this parameterwill not be presented to you because you must have an external database

for vertical or horizontal cluster installations.

Using an external database is recommended. You will be asked to confirmif you choose to use an internal database. Press y to select an externaldatabase, or n to continue with an internal database. It is only valid toinstall Runtime and Core Services with an internal database for thefollowing scenarios:

Remote Document Pipeline In this scenario, Runtime and CoreServices hosts a service that is used tofeed documents into the DocumentPipeline remotely.

Archive Cache Server In this scenario, Archive Web Services

delivers functionality for remote ar-chiving.

If you chose to use an external database or if you entered y for theCSCONFIGCLUSTER parameter, enter the following:





>> Parameter CSDBTYPE: Currently, only Oracle Database systems are sup-ported. Press ENTER.

>> Parameter CSDBSERVER: Type the name of the computer hosting the data-

base and confirm with ENTER.

>> Parameter CSDBNAME: Type the service name of the database to be used(default: orcl) and confirm with ENTER.

Note: If you are connecting to an Oracle Da-tabase or an Oracle RAC system (Real Appli-cation Clusters), do not use the System Iden-tifier (SID) for the Oracle Service Name.

>> Parameter CSDBPORT: Type the port (default: 1521) and confirm withENTER.

>> Parameter CSDBUSER: Type the name of the database user (default: rcs)and confirm with ENTER.

>> Parameter CSDBPASSWORD: Type the password of the database user and con-firm with ENTER. Repeat the password and thenconfirm with ENTER.

12. >>

Parameter:

CSAUTHENTICATIONMETHOD:

Type O if you are installing an OpenText Directory Services server.

Type E if you are connecting this RCS server to an existing remote DirectoryServices server.

Type L if you are installing an RCS Server with legacy authentication.

13. If you chose to use CSAUTHENTICATIONMETHOD=O, enter the followinginformation:

Important

If you are installing Directory Services in NetWeaver or in a cluster, youwill need to install Directory Services externally using a separateinstaller after Runtime and Core Services has been installed. For moreinformation, see “Installing Directory Services Externally” on page 63.

If you are installing Directory Services in a single Tomcat instance, itwill be embedded in Runtime and Core Services in the RCS


>> Parameter:

OTDS_DIRECTORY_SERVER_NAME:

The Directory Server (OpenDS) server name or IPaddress. This is the name of the machine thathosts OpenDS. This is required so that LDAP con-nections can be established by OTDS and LDAPclients.





>> Parameter:

OTDS_DIRECTORY_SERVER_ ADMIN_CONNECTOR_PORT:

The port that will be used for administrationtraffic. (Default 4440).

Important: The default of 4440 will not work

for IBM AIX. Choose an alternative port thatdoes not conflict with any other ports onyour server. For example, 14440.

>> Parameter:


PORT:

The port number that Directory Services uses forcommunication with your LDAP directory server.Also known as the LDAP Listener Port. (Default389 for Windows. Default 1389 for UNIX).

Important: The default of 1389 will not workfor IBM AIX. Choose an alternative port thatdoes not conflict with any other ports onyour server. For example, 11389.

>> Parameter: USE_LDAPS: Type Y if you want to use LDAP over SSL(LDAPS) between your Directory Services serverand your external OpenDS server.

>> Parameter:


PORT_LDAPS:

The port to use to communicate with the DirectoryServer (OpenDS). (Default 636 for Windows. De-fault is 1636 for UNIX). This property is onlyavailable if you are installing Directory Servicesexternally and you are using LDAPS.

>> Parameter:

LOAD_BALANCER_URL:

The Runtime and Core Services load balancer.This is an HTTP address of the load balancer. Thisis required because the OpenDS plug-in has toconnect back to OTDS.

14. If you chose to use CSAUTHENTICATIONMETHOD=E, enter the followinginformation:

>> Parameter:

OTDS_EXISTING_PROTOCOL:

HTTP(H) or HTTPS(S). The connection protocolused to communicate between this new server andan existing Directory Services server. (DefaultHTTPS). For HTTPS, the certificate in use by theDirectory Services server must be trusted by thisserver. You may need to install the certificate intothe JRE's CACERTS file.

>> Parameter:

OTDS_EXISTING_SERVER_NAME:

The name of the physical machine of your existingDirectory Services server. This can be the name ofthe physical machine or the IP address.

>> Parameter:

OTDS_EXISTING_PORT:

Default is 8443 for HTTPS and 8080 for HTTP.These ports must correspond to the ports definedfor your Directory Services server.





>> Parameter:

OTDS_EXISTING_RESOURCE:

This is the resource identifier of the resource thatwas created in Directory Services to represent thecurrent installation of Runtime and Core Services.You must create this resource in Directory Ser-

vices before installing Runtime and Core Services.For more information on configuring resources,see section 4 "Resources" in OpenText DirectoryServices - Administration Guide (OTDS-AGD).

15. If you chose to use CSAUTHENTICATIONMETHOD=L, continue with ENTER.

16. >>

Parameter

CSPASSWORD:

Type a password for the Runtime and Core Services administrator([email protected] or otadmin) and confirm with ENTER. Repeat thepassword and press ENTER.

Note: The RCS Administrator User name password must be a minimumof eight characters. Runtime and Core Services ignores leading and trailingblanks in the password.

17. If you are using NetWeaver, specify the following:

>> Parameter CSAPPSRVUSER

Enter the name of the NetWeaver deployment user and confirm withENTER. This is the SAP Instance Administrator and is used for installingservices in NetWeaver.

Note: Use the same user name as entered during the NetWeaverinstallation. Usually, the name is Administrator.

>> Parameter CSAPPSRVPASSWORD

Type a password for the NetWeaver user and confirm with ENTER. Repeatthe password and press ENTER.

>>

Parameter

CSAPPSRVPORT

Type the port NetWeaver uses and confirm with ENTER; default: 50004

>> Parameter CSAPPSRVDEPLOYDIR

Enter the path to the <NetWeaver > instance directory and press ENTER.

18. At the End Collecting Parameters, press y, ENTER to review your settingsand change any of the parameters or press n, ENTER to continue theinstallation.

If you press y, ENTER, the installation parameters are listed with an option to

change any of the input parameters. For example, see the following.

Installation Parameters:

[ 1] TOMCAT = /home/opentext/rcs/tomcat

[ 2] FILESTORE = /home/opentext/rcs/workspace

[ 3] NUMNODESTHISMACHINE = 2





[ 4] NODESROOTDIR = /home/opentext/rcs/tomcat_instances

[ 5] CSDBTYPE = Oracle

[ 6] CSDBSERVER = qamachine.opentext.net

[ 7] CSDBNAME = orc1

[ 8] CSDBPORT = 1521[ 9] CSDBUSER = rcs

[10] CSDBPASSWORD = *****

[11] OTDS_DIRECTORY_SERVER_NAME = rcsrh5

[12] OTDS_DIRECTORY_SERVER_ ADMIN_CONNECTOR_PORT = 4440

[13] OTDS_DIRECTORY_SERVER_COMM_PORT_LDAPS = 1636

[14] LOAD_BALANCER_URL = http://rcsrh5:80

[15] CSPASSWORD = *****

[16] INST_USER = rcsuser

[17] INST_GROUP = otsys

19. Press y, ENTER to start the configuration check. The installation parameters,including those that were set by the installation, will be displayed.

Tip: If you press n, ENTER to continue without the configuration check,you will be asked if you want to exit. Press y, ENTER to cancel theinstallation. Press n, ENTER to return to the configuration check. Youcannot continue with the installation until you complete the configurationcheck or cancel the installation.

20. If the configuration check returns any errors, solve the problem(s) and continue.If no errors are reported, press y, ENTER to perform the installation.

You can find detailed logging information in/tmp/opentext_instlog/R_CS/r_csInstall.log

21. If this installation requires Directory Services installed externally, see “Installing

Directory Services Externally” on page 63.

Important

Ensure that OpenDS is started before starting your application server(Tomcat) or deploying the new SCA file (NetWeaver).

22. Start your application server.

Important

Start your application server with the user you entered for theInstallation user name in step 4.

If you are using Tomcat, use the ot-startnode.sh inst001 script or the ot-

startnode001.sh script. For more information, see “To start or stop Tomcatusing the Runtime and Core Services scripts:” on page 54.





If you are using NetWeaver, use the following steps:

a. Open a command window and change to the deploy tool directory. Forexample, cd

<RCS workspace directory >/staging/deploy/tool.

b. Undeploy the old SCA file if it exists. For example, run

eardeployer.ksh -operation=undeploy -user=<deployment user >


Tip: If the undeploy succeeded, the application directory,usr/sap/<sapsid >/J00/j2ee/cluster/apps/opentext.com will beempty.

c. Recreate the SCA file by running earcreator.ksh.

d. Deploy the new SCA file using eardeployer.ksh. For example,

run eardeployer.ksh -operation=deploy -user=<deployment user >-password=<password of deployment user >

23. OpenText recommends that you back up your newly installed RCS workspace directory after installing Runtime and Core Services.


If you are installing Directory Services in NetWeaver or in a cluster, you will need toinstall Directory Services externally using the master installer or the DirectoryServices msi after Runtime and Core Services has been installed. This installsOpenDS as a service to manage user and group information. During the Runtimeand Core Services installation, an otds.dsd.properties file is created in the RCS

workspace directory. This file is required by the Directory Services installer andmust be copied from your Runtime and Core Services server to the server whereyou are installing Directory Services.

To install Directory Services externally:

1. Create the user and group to be used as the owner and group of the externalOpenDS files.

Important

Do not use root to install Directory Services externally. It can create

security vulnerabilities when running the application server using a root(or equivalent) user.

Tip: To create a user that will install and own the OpenDS files, seeRunning OpenDS as Nonroot athttp://developers.sun.com/identity/reference/techart/opends-namesvcs.html#2.

http://developers.sun.com/identity/reference/techart/opends-namesvcs.html#2








2. On your external Directory Services server, log on as this user.

3. Run the Directory Services setup script by typing ./setup.sh.

4. Read the license agreement. To accept it, press y and press ENTER.

5. >> Parameter DIRECTORY_LOCATION:

Location where a Directory Services server (OpenDS) should be installed.Default is DIRECTORY_LOCATION=/opentext/otds and OpenDS is installed in/opentext/otds/OpenDS-2.2.0.

Important

Do not use the RCS


6. >> Parameter CONN_PROPERTIES_LOCATION:

Location of the otds.dsd.properties file created by the Runtime and CoreServices installation.

Note: If the OpenText Directory Services 10.2.1 installer detects thatOpenDS is already installed it will not overwrite the existing installation.

Tip: The Runtime and Core Services installation creates this file in the RCS

workspace directory. You must copy this file from your Runtime and CoreServices server to your external Directory Services server or copy it to a fileshare accessible across the network.

7. >> Parameter KEYSTORE_LOCATION:

If you selected USE_LDAPS=Y when you installed Runtime and Core Services

with Directory Services, enter the location of .keystore file that contains thecertificate that has to be used by LDAPS protocol. For example,/opentext/rcs/security.

8. >>

Parameter

KEYSTORE_PASSWORD:

If you selected USE_LDAPS=Y when you installed Runtime and Core Serviceswith Directory Services, enter the password for the certificate to be used.

9. >> Parameter INST_USER:

Enter the name of an existing UNIX or Linux user under which the DirectoryServices server process will run and confirm with ENTER. This is the owner ofthe external OpenDS files that was created in step 1.

10. >> Parameter INST_GROUP:

Enter the name of an existing UNIX or Linux group under which the DirectoryServices server process will run and confirm with ENTER. The group has toexist and the INST_USER must be a member of this group.



3.4 Installing Runtime and Core Services Silently on UNIX or Linux


11. At the End Collecting Parameters, press y, ENTER to review your settingsand change any of the parameters or press n, ENTER to continue theinstallation.

If you press y, ENTER, the installation parameters are listed with an option tochange any of the input parameters.

12. Press y, ENTER to start the configuration check. The installation parameters,including those that were set by the installation, will be displayed.

Tip: If you press n, ENTER to continue without the configuration check,you will be asked if you want to exit. Press y, ENTER to cancel theinstallation. Press n, ENTER to return to the configuration check. Youcannot continue with the installation until you complete the configurationcheck or cancel the installation.

13. If the configuration check returns any errors, solve the problem(s) and continue.If no errors are reported, press y, ENTER to perform the installation.

You can find detailed logging information in/tmp/opentext_instlog/otdsds/otdsdsinstall.log

14. Start the OpenDS service using <DIRECTORY _LOCATION >/OpenDS-2.2.0/bin/start-ds.

3.4 Installing Runtime and Core Services Silently on

UNIX or Linux

You can use UNIX scripts to perform silent installations of Runtime and CoreServices on UNIX or Linux. You must create an <parameters >.Setup filecontaining your environment parameters and use this setup file with the UNIXinstallation script setup.sh and the –i option.

Example: ./setup.sh –e –i <parameters.Setup > –s

You must specify the following custom parameters in your < parameters.Setup> file:

Note: Parameters that are not specified or that are specified with empty valueswill be asked for interactively unless the –s option is used.

INST_USER

An existing UNIX or Linux user, which is the owner of the files and binaries thatwill be installed. This is the installation user name or the UNIX user name.

INST_GROUP

The existing UNIX or Linux group of INST_USER, which is the owner of the filesand binaries to be installed.

FILESTORE

The path to the RCS

workspace directory. For example,FILESTORE=/opentext/rcs/workspace.





APPSRVTYPE

The application server type. Use T for Tomcat or N for NetWeaver. If thisparameter is not set, Tomcat is assumed.

If APPSRVTYPE=T, use the following parameters:

TOMCAT The path to the <Tomcat_home> directory. For ex-ample, TOMCAT=/etc/apache-tomcat-6.0.32 .

If APPSRVTYPE=N, use the following parameters:

CSAPPSRVPORT The deployment port of NetWeaver. Required if APPSRVTYPE=N.

CSAPPSRVUSER The name of the NetWeaver deployment user. Thisis the SAP Instance Administrator and is used forinstalling services in NetWeaver. Required if

APPSRVTYPE=N.CSAPPSRVPASSWORD The password of CSAPPSRVUSER. Required if

APPSRVTYPE=N.

CSAPPSRVDEPLOYDIR The deployment directory of NetWeaver. Requiredif APPSRVTYPE=N.

CSCONFIGCLUSTER

Whether or not this installation is a cluster installation or a single Runtime andCore Services node. Enter CSCONFIGCLUSTER=yes or CSCONFIGCLUSTER=y if thiswill be a vertical or horizontal cluster. If this parameter is not included,CSCONFIGCLUSTER=n is assumed.

Note: This parameter is not required for NetWeaver installations.If CSCONFIGCLUSTER=y, use the following parameters:

NUMNODESTHISMACHINE If CSCONFIGCLUSTER=y is supplied, this parametercan be used to indicate how many nodes will beinstalled. Set NUMNODESTHISMACHINE=<n > where<n> is the total number of nodes to be installed inthis server. If CSCONFIGCLUSTER=y but the numberof nodes isn't specified, the installer will assumethat there is one node in this server. IfCSCONFIGCLUSTER=n or is not supplied,NUMNODESTHISMACHINE is not required.

Note: The maximum vertical node count islimited by the hardware. OpenText recom-mends one node per processor for maximumperformance up to a maximum of two nodesper processor.



3.4 Installing Runtime and Core Services Silently on UNIX or Linux


NODESROOTDIR If CSCONFIGCLUSTER=y is supplied, this parametercan be used to indicate if the installer should placevertical cluster instances in an existing directory.For example, NODESROOTDIR=</etc/apache-

tomcat-6.0.32_instances>. If this parameter isnot supplied and CSCONFIGCLUSTER=y, the installerwill create a default directory to store vertical clus-ter instances. If CSCONFIGCLUSTER=n or is not sup-plied, NODESROOTDIR is not required.

CSAUTHENTICATIONMETHOD

Set to O to install OpenText Directory Services authentication. Set to E to use anexisting Directory Services server. Set to L for Legacy (CAP) authentication.

When CSAUTHENTICATIONMETHOD=O, set the following parameters:

OTDS_DIRECTORY_SERVER_NAME The Directory Server (OpenDS) server name. Re-

quired if CSCONFIGCLUSTER=yes orAPPSRVTYPE =NetWeaver.

OTDS_DIRECTORY_SERVER_ ADMIN_CONNECTOR_PORT=4440

LDAP administration port. Default is 4440.


PORT

LDAP communication port. Default is 1389.

USE_LDAPS Set to USE_LDAPS=Y if you want to use LDAP overSSL (LDAPS) between your Directory Servicesserver and your external OpenDS server.


PORT_LDAPS

LDAPS communication port. Default is 1636. Re-quired if USE_LDAPS=Y.

LOAD_BALANCER_URL <Protocol>://<Server name> : < port> of the existingDirectory Services server where < protocol> can beHTTP or HTTPS. Required ifCSCONFIGCLUSTER=yes or APPSRVTYPE

=NetWeaver.

For example, LOAD_BALANCER_URL= HTTP://ot-

rcs.domain.net:80 .

When CSAUTHENTICATIONMETHOD=E, set the following parameters:

OTDS_EXISTING_RESOURCE Resource identifier supplied when component re-source was created in Directory Services. For ex-

ample, OTDS_EXISTING_RESOURCE=<fcd84f5c-d506-43bc-bcf9-8ffeb32c2516> .

OTDS_URL <Protocol>://<Server name> : < port> of the existingDirectory Services server where < protocol> can beHTTP or HTTPS.





CSDBNEEDED

Set to y if an external database is being used. This parameter must be set to y ifthis is a clustered installation. If CSDNBEEDED is set to y, enter the followingparameters:

CSDBTYPE The type of database. Only CSDBTYPE=Oracle issupported.

CSDBSERVER The database server name.

CSDBPORT The database server port. For Oracle Database, thedefault is 1521.

CSDBNAME The Oracle ServiceName.

CSDBUSER The name of the default user account for the data-base.

CSDBPASSWORD The password of the default user account for thedatabase.

CSUSER

The Runtime and Core Services administrator. This property will be ignored if itis supplied since it is automatically set by the Runtime and Core Servicesinstaller.

CSPASSWORD

A password for the CSUSER. This parameter is only required when installing anew instance of Runtime and Core Services.

Note: The RCS Administrator User name password must be a minimum ofeight characters. Runtime and Core Services ignores leading and trailingblanks in the password.


You should adjust the application servers after installing Runtime and CoreServices.

Note: Refer to section 13 "Troubleshooting Runtime and Core Services" inOpenText Runtime and Core Services - Administration Guide (ELCS-AGD) for helptroubleshooting common performance problems.

By default, multicasting is enabled to support clustering if you have installedRuntime and Core Services with an external database. Therefore, Runtime and CoreServices will create some network traffic, which is harmless and unnecessary if

clustering is not in use. If you want to reduce your network traffic, you can enableloopback to disable multicasting on Tomcat by setting thecs.use.loopback.smessage to true:

To enable loopback on Tomcat to reduce network traffic:

1. From the <Tomcat _home >/lib directory, open boot.properties in an editor.





2. Change the value of the cs.use.loopback.smessage parameter to true.

Example: cs.use.loopback.smessage=true

cs.use.loopback.smessage=true







Chapter 4

Installing OpenText Administration Client

This section describes how to install the OpenText Administration Client toconfigure Runtime and Core Services, Directory Services, and other OpenTextcomponents. For more information, see the following sections:

• “Prerequisites” on page 71

• “Installing Administration Client” on page 71

• “Accessing Logging Information” on page 72

• “Removing Administration Client” on page 72

4.1 Prerequisites

Administration Client can be installed on any Windows computer that can connectto the server that you want to administer. Prerequisites, supported environments,and supported platforms for Administration Client can be found in theAdministration Client Release Notes in the OpenText Knowledge Center.

Administration Client 10.2.1 requires .NET

Framework

3.5.1/SP1. On MicrosoftWindows Server 2008 R2, .Net framework 3.5.1 must be installed using the ServerManager. This action must be performed as a domain user.

To install Microsoft .NET Framework 3.5 on Microsoft Windows Server 2008:

1. Start Server Manager and expand Features.

2. In the Features Summary section, click Add Features.

3. Select .NET Framework 3.0 Features.

4. Click Install.

4.2 Installing Administration Client

You must have administrative privileges for the installation of AdministrationClient.

To install Administration Client:

1. In the OpenText Administration Client welcome window, click Next.

2. If the license agreement appears, read the license agreement, select I accept theterms in the License Agreement and click Next.






Chapter 5

Securing Your Server

This section describes how to configure your Runtime and Core Services serversecurely. For more information, see the following sections:

• “Enabling SSL on Runtime and Core Services” on page 73

• “Enabling SSL for JMS Server” on page 73

• “Securing Your Runtime and Core Services Database” on page 75

5.1 Enabling SSL on Runtime and Core ServicesSecure Socket Layer (SSL) is a technology that allows application servers tocommunicate over a secured connection. You should use SSL whenever possible. Inorder to enable SSL, you must configure the necessary settings in server.xml. See“To change or add Tomcat ports for Secure Sockets Layer:” on page 18 for Windowsor “To configure Tomcat for Secure Sockets Layer:” on page 52 for UNIX or Linux.OpenText recommends using a certificate from a Certificate Authority that has aroot certificate that is trusted by your Java Virtual Machine (JVM). For detailedinformation on enabling SSL, see SSL Configuration How-to athttp://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html.

Important

SSL certificate files must be protected by file system permissions such thatonly the application server service user can read them.

5.2 Enabling SSL for JMS Server

You should also ensure that all Java Message Service (JMS) communication usingApache ActiveMQ (AAMQ) is secured using SSL connections. If your applicationserver is configured for SSL, the existing SSL settings can be used to configure asecured JMS Server connection and a secured Directory Services connection. Youcan also use dedicated SSL configuration settings for your JMS Server whether yourapplication server is configured for SSL or not.

SSL can be enabled for your JMS Server using the SSL Configuration Option in theAdministration Client. JMS Server currently only supports the Java Secure SocketExtension (JSSE) implementation of SSL. The SSL Configuration Option defaults toUSE_ APPSRV_SSL which configures your JMS Server to use your Tomcat JSSE SSLsettings. There are three options to configure SSL for a JMS Server:





Chapter 5 Securing Your Server


USE_NO_SSLThe JMS Server will not use SSL for secured communication with JMS clients.This setting is not intended for production usage.

USE_APPSRV_SSLThe JMS Server will use Tomcat JSSE SSL configuration for securedcommunication with JMS clients. If Tomcat JSSE SSL is configured, then JMSServer will use all Tomcat JSSE SSL configurations as its own SSL configuration.If Tomcat JSEE SSL is not configured, then JMS Server will not configure SSL.

USE_JMS_SSL JMS Server will use its dedicated SSL configuration for secured communicationwith the JMS clients. Therefore all the SSL settings in the Administration Clientmust be configured.

Figure 5-1: JMS Server SSL Configuration Options

You also need to set the following configuration parameters in the AdministrationClient. Tomcat must be restarted for the changes to take effect. For moreinformation, see section 11 "JMS Server parameters" in OpenText Runtime and CoreServices - Configuration Parameters (ELCS-RCP).

SSL KeyAlias The alias used to identify the server/clientcertificate in the keystore.

SSL KeyStore The pathname of the keystore file whereyou have stored the server/client certificateto be loaded.



5.3 Securing Your Runtime and Core Services Database


SSL KeyStore Password The password used to access theserver/client certificate from the specifiedkeystore file.

SSL TrustStore The trust store file to use to validateserver/client certificates.

SSL TrustStore Password The password to access the trust store.

5.3 Securing Your Runtime and Core Services

Database

To install Runtime and Core Services, you need a database to store and retrieveconfiguration data. For an Microsoft SQL Server database, you must have a uniquedatabase user with at least CREATE TABLE privileges. For an Oracle Database, youmust have a unique database user with CREATE TABLE, CREATE VIEW , CREATE

SEQUENCE, and CREATE SESSION privileges. However, when the Runtime and CoreServices installation is complete and has been verified by signing in to your serverusing Administration Client, some of these privileges are no longer required.

In a highly secure environment, for example in a bank, the ability to create tables,indexes, and views is controlled and audited. After Runtime and Core Services hasbeen installed and verified, the database user privileges can be changed to removeCREATE TABLE and CREATE VIEW privileges for the Runtime and Core Servicesdatabase user.

Note: This only describes the privileges required by Runtime and Core Ser-vices. Applications installed in Runtime and Core Services may have additionalrequirements for database access.






Chapter 6

Configuring Runtime and Core Services Clusters

This section covers the following topics for managing Runtime and Core Servicescluster installations on Windows and UNIX or Linux servers:

• “Configuring Clusters and Services on Tomcat” on page 77

• “Understanding Singleton Services and Failover Scenarios in Clusters” onpage 83

6.1 Configuring Clusters and Services on Tomcat

Runtime and Core Services servers can be configured as horizontal, vertical, ormixed clusters. A horizontal cluster is set up by installing Runtime and CoreServices on each machine in the cluster while using a common RCS workspace directory. A vertical cluster is set up by installing Runtime and Core Services onceon the machine and indicating how many nodes are in the cluster. Vertical nodescan be set up in these ways:

• By specifying that this is a vertical cluster during setup and indicating that thereis more than 1 node on this machine. For more information, see step 5.e onpage 24 on Windows and step 8 on page 57 on UNIX or Linux.

• By specifying additional nodes in <Tomcat _home >/lib/boot.properties afterthe Runtime and Core Services installation is complete. For more information,

see “Configuring Vertical Clusters Manually” on page 79.

The Runtime and Core Services installation uses the service.bat files found in the<Tomcat _home >/bin directory to create services for each Runtime and Core Servicesnode on your machine. The Runtime and Core Services install provides ot-startnode###.bat and ot-shutnode###.bat scripts for Windows or ot-startnode###.sh and ot-shutnode###.sh scripts for UNIX or Linux which canthen be used to start nodes from the command line.

Each machine has cluster-wide settings and cluster information in<Tomcat _home >/lib/boot.properties. These settings are included inboot.properties for both horizontal and vertical clusters. This allows you to addadditional nodes to your cluster easily. An example is shown below:

Example:

#added by installation

#Thu Apr 08 11:33:17 EDT 2010

rcs.config.Engine=MSSQL

rcs.config.Connect=jdbc\:sqlserver\://vm20003ent0101\:1433;DatabaseNa

me\=rcsdb



Chapter 6 Configuring Runtime and Core Services Clusters


rcs.config.Driver=com.microsoft.sqlserver.jdbc.SQLServerDriver

rcs.config.DatabaseName=rcsdb

rcs.config.UserName=loginrcsdb

rcs.config.Password={HcEncode}{HcEncode}\#eW/"uSN$.-;"ep*

cs.fsdir=C\:ProgramData\\Open Text\\Runtime and Core Services10.2.1\\Workspace

cs.localservername=vm20003ent0101.ottawa.hcl.com

cs.use.loopback.smessage=false

cs.cluster.configured=true

cs.num.nodes.this.machine=1

cs.nodes.dir=C\:\\Program Files\\Apache Software Foundation\\Tomcat

6.0_instances

The primary node of a horizontal or vertical cluster is found in the<Tomcat _home >/Tomcat 6.0 directory. If this is a vertical cluster, an additionaldirectory, <Tomcat _home >/Tomcat 6.0_instances, is created to contain eachadditional instance in the vertical cluster. Instances appear in this directory as

inst<nnn > folders. Settings specific to a cluster instance are found in the<Tomcat _home >/Tomcat

6.-0_instances/inst<nnn >/ directory.

Each node has the minimum cluster configuration elements added to itsserver.xml in <Tomcat _home >/Tomcat

6.-0_instances/inst<nnn >/conf/. Themembership address and membership port are the same for each node in a clusterand unique for each cluster running in the same subnetwork. The receiver

address is automatically determined by Tomcat, the autobind element specifiesthat the port is statically defined and cannot be changed by Tomcat. The receiverport is assigned a unique number for each node in the cluster. This clusterconfiguration supports deterministic failover because each process binds to a uniqueport reserved for it. This is shown in the following example:

Example:

<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster">

<Channel className="org.apache.catalina.tribes.group.GroupChannel">

<Membership address="228.0.0.14"

className="org.apache.catalina.tribes.membership.McastService"

port="45574"/>

<Receiver address="auto" autoBind="0"

className="org.apache.catalina.tribes.transport.nio.NioReceiver"

port="4001"/>

</Channel>

</Cluster>

Note: You must ensure that all ports used in server.xml do not conflict with

ports used for other software on this machine to ensure that automatic failoverof cluster nodes functions correctly. For more information, see “ConfiguringAutomatic Failover for Vertical Clusters” on page 80.

For each instance of a vertical cluster, an equivalent Tomcat service is created. Theseservices appear as Apache Tomcat 6 Open Text RCS node<nnn >. Each of theseservices must be started independently after installing a Runtime and Core Servicesvertical cluster for the first time.





6.1.1 Configuring Vertical Clusters Manually

OpenText recommends understanding your cluster before installing and using theinstaller to create your vertical cluster automatically.

You can convert a single Runtime and Core Services installation to a verticalRuntime and Core Services cluster or add additional instances to an existingRuntime and Core Services cluster. For more information, see “To manuallyconfigure vertical cluster nodes after installing Runtime and Core Services:” onpage 79.

You can also manually remove a vertical cluster node from a Runtime and CoreServices cluster. For more information, see “To manually remove a vertical clusternode from a Runtime and Core Services cluster:” on page 79.

To manually configure vertical cluster nodes after installing Runtime and CoreServices:

1. Ensure that you have a external database configured in Runtime and CoreServices.

2. If this is not already a Runtime and Core Services cluster, addcs.cluster.configured=true to <Tomcat _home >/Tomcat 6.0/lib/boot.-

properties.

3. In <Tomcat _home >/Tomcat 6.0/lib/boot.properties, increasecs.num.nodes.this.machine by the number of additional vertical instances tobe created.

4. Restart Tomcat.

To manually remove a vertical cluster node from a Runtime and Core Servicescluster:

1. Stop the Apache Tomcat 6 Open Text RCS node<nnn > node.

2. On Windows, remove the service using <Tomcat _home >\bin\ot-

removeservice.bat node<nnn >.

3. In the Administration Client, use the RCS Nodes object to remove the clusternode entry from the configuration database tables so that the static viewmatches the dynamic view. For more information, see “Using theAdministration Client to Manage Vertical Clusters” on page 80.

4. Delete the appropriate \inst<nnn > directory and its contents.

5. In <Tomcat _home >/Tomcat 6.0/lib/boot.properties, decreasecs.num.nodes.this.machine by the number of additional vertical instances tobe removed.





6.1.2 Configuring Automatic Failover for Vertical Clusters

The multicast channel should be unique for each cluster running in the samesubnetwork. To avoid interference between multiple clusters within the same

network, ensure the multicast address=<IP Address > and port=<port number >are unique.

To configure vertical cluster nodes for automatic failover:

1. Stop all Tomcat services.

2. Edit each vertical node's server.xml in <Tomcat _home >/Tomcat 6.-

0_instances/inst<nnn >/conf/ including node 1's in <Tomcat _home >/conf/.For each node, ensure that the following attributes are set:


<Channel

className="org.apache.catalina.tribes.group.GroupChannel"><Membership address="IP address"

className="org.apache.catalina.tribes.membership.McastService"

port="port number">


className="org.apache.catalina.tribes.transport.nio.NioReceiver"

port="4001">

</Channel>

</Cluster>

Note: Port numbers must be different for vertical nodes but they can be thesame for horizontal clusters.

This cluster configuration supports the deterministic failover of processes, becauseeach process binds to a unique TCP port. The autoBind attribute specifies that thisport is statically defined by the port attribute and cannot be changed by Tomcat.For detailed information, see the Apache Tomcat Clustering/Session Replication HOW-TO at http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html.

6.1.3 Using the Administration Client to Manage Vertical

Clusters

Runtime and Core Services defines two internal cluster views.

• Each node in a vertical Runtime and Core Services cluster registers itself at

startup. This is referred to as thestatic view

and is stored in the configurationdata as the RCS Nodes object.

• The dynamic view of Runtime and Core Services vertical nodes is obtained fromTomcat's group communication channel. This view can be different on differentservers if cluster splitting has occurred.






These two views are used to detect and react to Tomcat cluster splitting. A Runtimeand Core Services administrator must maintain a consistent view in which the staticview matches the dynamic view otherwise the Runtime and Core Services clusterwill switch to restricted mode. Some distributed caching operations are prohibited

in restricted mode because a Runtime and Core Services cluster cannot guaranteethat the distributed cache is consistent on all cluster nodes.

To switch Runtime and Core Services to full mode, an administrator should resolvethe problem that caused the cluster to split and then modify the RCS Nodes objectusing the Administration Client so that the static view of the cluster matches thedynamic view of the cluster. Runtime and Core Services is notified and switches tofull mode without restarting the Tomcat cluster.

Figure 6-1: Horizontal Cluster Information window

6.1.4 Configuring Horizontal or Mixed Clusters

During the installation of Runtime and Core Services, the installer determines thatthis is a horizontal cluster when it detects an existing RCS workspace directorycontaining a /modules/install directory. The Horizontal Cluster Installation window appears with the information message that this machine will create or joina Runtime and Core Services cluster installation.





When the installation is finished, the cluster must be configured and customizedbased on the number of applications, the number of nodes, the database type, andthe hardware speed:

1. The RCS workspace directory must be accessible and updatable from all nodesin the horizontal cluster.

2. The service accounts for each node in the horizontal cluster must be able to up-date the RCS workspace directory. Each service account can be changed from alocal user account to a domain user account that has full read/write access tothe RCS


Important

All user accounts and passwords must be the same for all nodes on allmachines in a cluster.

3. Each machine in the cluster must know the fully qualified name of all othermachines in the cluster to allow concurrent startup of horizontal nodes in ahorizontal or mixed cluster. To achieve this, either ensure that your DNS serverprovides fully qualified names; or, in the host configuration file on each

machine, ensure that the fully qualified host name for each node is included.For example, in the windows/system32/drivers/etc/host files for a two-nodehorizontal cluster you might see the following:

From machine A:

# localhost name resolution is handled within DNS itself.

# 127.0.0.1 localhost



6.2 Understanding Singleton Services and Failover Scenarios in Clusters


# ::1 localhost

10.2.53.253 RCS-server-A.mydomain.com

And from machine B:

# localhost name resolution is handled within DNS itself.# 127.0.0.1 localhost

# ::1 localhost

10.2.53.114 RCS-server-B.mydomain.com

4. The parameter rcs.startup.attempts=<n > can be added in<Tomcat _home >/lib/boot.properties if this is a cluster installation withmany services installed on multiple nodes.

The parameter rcs.startup.attempts is a cluster startup tuning parameter.This parameter defines the number of times RCS will attempt to start up anRCS node or instance when other nodes are preventing it from starting up. Eachattempt has a 1 second delay before the next attempt.

As more applications are installed into Runtime and Core Services, or morenodes are added, this parameter may need to be increased until all nodes startproperly. The default, rcs.startup.attempts=600, may not be sufficient.

6.2 Understanding Singleton Services and Failover

Scenarios in Clusters

Singleton services are services that must run on only one node in a cluster but aredeployed on all nodes. Only one instance of a singleton service is active in a cluster.This active instance processes all the requests arriving to all the cluster nodes. Theother instances of the singleton service that are running on other nodes are onlyproxies of the active instance. This is transparent to the client that uses the singletonservice.

If the active node, the node that runs the singleton service instance, is stopped,Runtime and Core Services chooses one of the running nodes to be the new activenode for a new instance of the singleton service. The singleton service instance willbe started on the new active node, and all the other nodes (the proxies) will sendrequests to the new singleton service instance. This failover process is transparentlydone for the clients of the singleton service.

When a cluster is started or during a failover scenario, Runtime and Core Servicesmust find the singleton node that should run the singleton service instance. Thisprocess of choosing the active node and subsequently defining the proxy nodes isbased on an elector that defines the algorithm used to select the next node in the

cluster to become the active node or the singleton node.

Three configuration parameters are available in the Administration Client toconfigure this process of choosing the active node:

• The parameter rcs.singleton.retries determines the number of retries toattempt when connecting to the remote singleton service. The default is 60.





• The parameter rcs.singleton.sleeptime determines the interval to sleepbetween retries, in milliseconds. The default is 1000 milliseconds.

• The parameter rcs.singleton.nodes determines the list of preferred singleton

nodes to be used by the configurable node elector. For more information see“Configurable Node Elector” on page 84.

6.2.1 Alphabetic Node Elector

The alphabetic elector is the default elector used by Runtime and Core Services. Thenext candidate for the singleton node is selected in alphabetical order.

6.2.2 Configurable Node Elector

The configurable node elector uses a configured list of nodes to select the nextcandidate for the singleton node. This list can be found in thercs.singleton_nodes property in the Runtime and Cores Services object of theAdministration Client. The configured list of nodes has the structure<hostname >;node<n > where the nodes are delimited in the list by a “|” character.For example, de05178.opentext.net;node1|de05178.opentext.net;node2. Thelist is scanned in order and the first running node is elected as the singleton node. Ifthe list is empty or not defined, or none of the nodes in the list are available, then thealphabetic elector will be used.

6.2.3 Preserve Singleton Node Elector

The preserve singleton node elector tries to manage the migration of the singletonframework from one node to the other. The singleton node id is written into theshared configuration data available to all cluster nodes in the

rcs.singleton.instance parameter. If this singleton node is running, the preservesingleton elector tries to connect to it. If this singleton node is not running, then theconfigurable node elector will be used to decide which node should be elected as thesingleton node.

After the singleton service successfully starts, the rcs.singleton.instance parameter value will contain the new singleton node.

Note: The rcs.singleton.instance is a read-only parameter.




Chapter 7

Configuring Runtime and Core Services in a High-Availability Cluster

This section describes how to configure Runtime and Core Services in a high-availability cluster. For more information, see the following sections:

• “Prerequisites” on page 85

• “Installing Tomcat in a High-Availability Cluster” on page 86

• “Configuring your High-Availability Cluster” on page 86

• “Installing Runtime and Core Services on the Primary Node” on page 87

• “Installing Directory Services Externally in a High-Availability Cluster” onpage 88

7.1 Prerequisites

OpenText recommends the following prerequisites when configuring high-availability clusters using Microsoft Failover Clustering:

• One Shared Network Attached Storage (NAS) or Internet Small Computer Sys-tem Interface (iSCSI) formatted disk with New Technology File System (NTFS)and at least 10GB.

Important

Mount the shared disk as a drive letter. The drive letter must be the samein all server instances in the cluster. This drive letter cannot changewithout reconfiguring Runtime and Core Services.

• A minimum of 2 GB RAM

• Fixed IP addresses

To install Microsoft Failover Clustering on your server:

1. Start Server Manager and expand Features.

2. In the Features Summary section, click Add Features.

3. Select Failover Clustering .

4. Click Install.



Chapter 7 Configuring Runtime and Core Services in a High-Availability Cluster


7.2 Installing Tomcat in a High-Availability Cluster

To install Runtime and Core Services in a high-availability (HA) cluster, one Tomcatinstance must be installed in an HA cluster and configured to use a new high-availability service.

To install Tomcat in a high-availability cluster:

1. Mount the shared disk on the drive letter you have reserved for this disk andensure that you are logged in with a domain account that has Full control security settings on the shared disk.

2. Install Tomcat on this shared disk and verify that Tomcat is working on<Server1> where <Server1> is the primary node of your HA cluster.

Important

Stop Tomcat before continuing.

3. Dismount the shared disk from <Server1>.

4. Mount the shared disk on <Server2> using the same drive letter that was usedfor <Server1> in step 2.

5. Rename or delete the Tomcat installation directories from the shared disk.

6. Install Tomcat into this shared disk again using the same parameters as the firstinstallation. This is to define all of the appropriate registry keys for Tomcat.

7. Start Tomcat and verify that Tomcat is working <Server2> .

Important

Stop Tomcat.

7.3 Configuring your High-Availability Cluster

The next step in creating a Runtime and Core Services high-availability cluster is tocreate and configure a high-availability service.

To configure your High-Availability Runtime and Core Services cluster:

1. Log in using domain credentials and start the Server Manager.

2. Expand Features and select Failover Cluster Manager > <your cluster >>Services and Applications.

3. Create a Generic service using the creation assistant.

a. Choose the Tomcat service from the supplied list.



7.4 Installing Runtime and Core Services on the Primary Node


b. Create a unique virtual name. This name will be registered in the localdomain name system (DNS).

Tip: OpenText recommends using OPENTEXT. The name MSCS will

return an error if the name already exists within the networkc. Set the service to use a fixed IP address.

d. Choose the shared disk used in the Tomcat installation in step 6 on page 86.Ensure that it will use the correct drive letter.

e. Complete the generic service creation assistant, configuring your additionalrequirements for high availability.

4. Start Tomcat.

5. Verify that Tomcat functions using the server name created in step 3.b onpage 87 and test that it fails over to the other server when one server is stopped.This will ensure that you have a working service before installing Runtime and

Core Services.

6. Stop Tomcat.

7.4 Installing Runtime and Core Services on the

Primary Node

The next step in creating a Runtime and Core Services high-availability cluster is toinstall Runtime and Core Services using a RCS workspace directory in the shareddevice.

To install Runtime and Core Services on the primary node in a high-availability

cluster:

1. Create an RCS workspace directory on the shared disk and verify that thepermissions of this directory are set to Full Control for the domain user that willbe running the service.

Important

The permissions on this RCS workspace directory must be set to FullControl for the domain user that will be running the service that youcreated in step 3 on page 86.

2. Install Runtime and Core Services using setup with the following exceptions:

a. Select Apache Tomcat 6.0 as your application server. SAP NetWeaver CE7.3 is not supported in high-availability clusters.

b. Select the directory of the high-availability Tomcat.

c. Do not select Install a vertical or horizontal RCS cluster.





d. Select any database choice: Internal database, Microsoft SQL Server, orOracle Database. The physical location of the database is a function ofhardware capability and performance required. That is, the database can beinstalled within the same cluster if the machine can handle the load, but is

generally not recommended.

Note: In a high-availability configuration with a local database, thedatabase must be stored on a shared disk so that when a failoveroccurs the database will still be available.

3. Complete the installation but do not start Tomcat. For more information, see“To install Runtime and Core Services:” on page 21.

4. Open <shared drive >/Tomcat 6.0/lib/boot.properties and updatecs.localservername to use the fully qualified server name created in step 3.bon page 87.

Important

If Tomcat is started before step 4 on page 88, the installation will bemisconfigured and you will need to remove and reinstall Runtime andCore Services.

5. Configure any additional options required for the service using the propertiestab, for example, Monitoring, Failover speed, and so on.

Tip: Service Policies control how fast the service will fail over to anothernode.

6. Start Tomcat.

7. If you have installed embedded Directory Services, use the MMC to verify thatthe following parameters contain the cluster virtual name:• Runtime and Core Services > Configuration > Directory Services >

Authentication Service Principal Name • Runtime and Core Services > Configuration > Runtime and Core Services

> OTDS web service URL

8. Once Tomcat has successfully started, use the Failover Cluster Manager to testthat failover works as expected.

7.5 Installing Directory Services Externally in a High-

Availability ClusterTo install Directory Services externally in an HA cluster:

1. Make <Server1> active, where <Server1> is the primary node of your HA cluster.

2. Copy the otds.dsd.properties file from the RCS workspace directory to alocal directory.



7.5 Installing Directory Services Externally in a High-Availability Cluster


3. Install OpenText Directory Services using setup:

a. In the Directory Server Install Location window, enter the location ofwhere you would like to install Directory Services. Click Next.

b. In the Directory Services Connection Properties window, enter thedirectory where the otds.dsd.properties file is located. Click Next.

c. Click Install.

4. In your Server Manager, ensure that the OpenDS Windows service has started.





5. Create an OpenDS windows service on this node also.

a. Make <Server2> active.

b. Open a command window as Administrator.

c. Cd to the directory <OtdsDsd installation directory >\OpenDS-2.2.0\-

bat.

d. Run windows-service.bat

-e to create an OpenDS windows service onthis node.

6. Make <Server1> active.

7. In the Failover Cluster Manager, click Add a resource to create a new clusterresource as a generic service using the New resource wizard.



7.5 Installing Directory Services Externally in a High-Availability Cluster


8. In the Select Service window, select the OpenDS service.

9. In the Confirmation window, click Next.





10. In the Summary window, click Finish. The resource will appear in the FailoverCluster Manager.

11. Configure the dependencies of the newly created resource.

a. Right click on the new resource and select Properties.

b. Click the Dependencies tab.








Chapter 8

Removing Runtime and Core Services

This section describes how to remove OpenText Runtime and Core Services andOpenText Directory Services from Windows and UNIX or Linux servers. For moreinformation, see the following sections:

• “Removing Runtime and Core Services on Windows” on page 95

• “Removing Runtime and Core Services on UNIX or Linux” on page 98

8.1 Removing Runtime and Core Services on

Windows

Runtime and Core Services can be removed from the Control Panel on Windows.

Note: If Runtime and Core Services was installed with Directory Servicesembedded, Directory Services will be removed when Runtime and CoreServices is removed.

If Runtime and Core Services was installed with Directory Services externallyinstalled using the Directory Services installer, Directory Services must beremoved explicitly. See “Removing Externally Installed Directory Services” onpage 98.

8.1.1 Removing Runtime and Core Services on Tomcat

To remove Runtime and Core Services on Tomcat:

1. Stop all Tomcat services on this machine.

2. In the Windows Control Panel, select OpenText Runtime and Core Services andselect Uninstall/Change.

3. In the Welcome to OpenText Runtime and Core Services 10.2.1 window, clickNext.

4. In the Change or Remove Runtime and Core Services window, select Remove.



Chapter 8 Removing Runtime and Core Services


5. In the Remove user data window, select the Remove the RCS Workspacedirectory check box if you want to delete all configuration data created byRuntime and Core Services.

Select the Remove the Nodes Configuration directory check box to delete theCluster Nodes Configuration directory.

Click Next.

Important

Remove the RCS

workspace directory only when you are removing asingle node, a standalone vertical cluster, or the last node in a horizontalcluster.



8.1 Removing Runtime and Core Services on Windows


6. In the Ready to Remove window, click Remove.

7. In the Completing the removal of OpenText Runtime and Core Services 10.2.1 window, click Finish.

8. In the appropriate database manager, delete all tables from your Runtime andCore Services database if they are no longer required or if you would like toinstall a clean copy of Runtime and Core Services. Do not remove databasetables if they are still required by a horizontal cluster.

8.1.2 Removing Runtime and Core Services on NetWeaver

To remove Runtime and Core Services on NetWeaver:

Important

Do not interrupt the undeploy operation until NetWeaver has finished theprocess. If the undeploy operation is interrupted, the RCS workspace directory could become corrupt.

1. With NetWeaver operational, from the <RCS workspace directory >/staging/deploy/tool directory, execute the eardeployer usingthe following command:

-operation=undeploy -user=Administrator -password=<password >

2. Use the Windows Control Panel to remove Runtime and Core Services.





3. Select the option Remove user data if you want to delete the RCS workspace directory upon completion of the removal.

4. Click Remove.


8.1.3 Removing Externally Installed Directory Services

To remove externally installed Directory Services:

1. In the Windows Control Panel, select OpenText Directory Services and selectChange to remove Directory Services.

2. In the Welcome to OpenText Directory Services 10.2.1 window, click Next.3. In the Remove user data window, select Remove user data to remove all user

and group information stored in Directory Services. Click Next. This willremove the OpenDS service.

4. Click Remove.

5. Click Finish.

8.2 Removing Runtime and Core Services on UNIX

or Linux

Runtime and Core Services must be removed manually on UNIX or Linux.Note: If Runtime and Core Services was installed with Directory Servicesembedded, Directory Services will be removed when Runtime and CoreServices is removed.

If Runtime and Core Services was installed with Directory Services externallyinstalled using the Directory Services installer, Directory Services must beremoved explicitly. See “Removing Externally Installed Directory Services” onpage 103.

8.2.1 Removing Runtime and Core Services and Tomcat

To remove all Runtime and Core Services components including Tomcat:

1. Stop all Tomcat services using the ot-shutnode.sh inst<nnn> scripts. Formore information, see “To Start or Stop Tomcat Using Scripts” on page 53.

Tip: The RCS scripts automatically kill the Tomcat process after the delay.If you are using other non-RCS scripts to stop Tomcat, you must kill the



8.2 Removing Runtime and Core Services on UNIX or Linux


Tomcat process using the kill

<processid > UNIX command aftershutting down RCS. Use ps -ef | grep java to find the < processid>.

2. Delete the <Tomcat _home > directory.

3. In the /etc/opentext/inst_dirs directory, delete the .inst files. Forexample, delete R_CS.inst to remove Runtime and Core Services.

4. Optionally, delete the RCS workspace directory.

Important

Remove the RCS workspace directory only when you are removing asingle node, a standalone vertical cluster, or the last node in a horizontalcluster.

5. In the appropriate database manager, delete all tables from your Runtime andCore Services database if they are no longer required or if you would like to in-stall a clean copy of Runtime and Core Services. Do not remove database tablesif they are still required by a horizontal cluster.

Important

Do not remove the database tables if you are manually upgrading fromRCS 10.2.0 to RCS 10.2.1.

8.2.2 Removing Runtime and Core Services Without

Removing Tomcat

To remove Runtime and Core Services without removing Tomcat:

1. Stop all Tomcat services using the ot-shutnode.sh inst<nnn> scripts. Formore information, see “To Start or Stop Tomcat Using Scripts” on page 53.

Tip: The RCS scripts automatically kill the Tomcat process after the delay.If you are using other non-RCS scripts to stop Tomcat, you must kill theTomcat process using the kill <processid > UNIX command aftershutting down RCS. Use ps

-ef

| grep

java to find the < processid>.

2. Record all WAR files in the <RCS workspace directory >/modules/install directory.

3. Delete all webapps, including all WAR files and exploded WAR file directoriesrecorded in the previous step, from the <Tomcat _home >/webapps

directory.

4. From the <Tomcat _home >/conf directory, open server.xml in an editor anddelete the Resource, Listener, and Cluster elements if they have been addedor modified by your installation or revert to server.xml.bak. For example:

Example:





<Resource auth="Container"

factory="org.apache.naming.factory.BeanFactory"

name="bean/CSStarter"

type="com.opentext.ecm.services.kernel.j2ee.tomcat.CSStarterBean"

/><Listener

className="com.opentext.ecm.services.kernel.j2ee.tomcat.TomcatSer

verLifecycleListener"/>


<Channel

className="org.apache.catalina.tribes.group.GroupChannel">

<Membership address="228.0.0.14"

className="org.apache.catalina.tribes.membership.McastService"por

t="45574"/>


className="org.apache.catalina.tribes.transport.nio.NioReceiver"p

ort="4002">

</Channel></Cluster>

5. Delete the following files in <Tomcat _home > if they are present:• capserver.pem

• derby.log

• installedfiles.log

• key.der

• mapping.xml

• server.der

• web-app_2_3.dtd

6. Delete the following files in <Tomcat _home >/endorsed:• jaxb-api.jar

• jaxws-api.jar• xercesImpl.jar (present only on IBM AIX)

7. Delete the following files in <Tomcat _home >/bin if they are present:• ot-configservice.bat

• ot-removeservice.bat

• ot-rcs-tomcat.pid

• ot-startnode.sh • ot-shutnode.sh

• ot-startnode001.sh • ot-shutnode001.sh

• setenv.sh

Note: If setenv.sh was present before the Runtime and Core Servicesinstall, delete setenv.sh and restore setenv.sh.bak.

8. Delete the <Tomcat _home >/conf/Catalina directory.

9. Delete the following files and directories in <Tomcat _home >/lib if they arepresent:• boot.properties







Important

Remove the RCS workspace directory only when you are removing asingle node, a standalone vertical cluster, or the last node in a horizontal

cluster.


8.2.4 Removing Runtime and Core Services Without

Removing NetWeaver

To remove Runtime and Core Services without removing NetWeaver:

Important

Do not interrupt the undeploy operation until NetWeaver has finished theprocess. If the undeploy operation is interrupted, the RCS workspace directory could become corrupt.

1. With NetWeaver operational, from the <RCS workspace directory >/staging/deploy/tool directory, execute the eardeployer usingthe following command:

-operation=undeploy -user=Administrator -password=<password >

2. In the /etc/opentext/inst_dirs directory, delete the .inst files. Forexample, delete R_CS.inst to remove Runtime and Core Services.

3. Optionally, delete the RCS


Important

Remove the RCS workspace directory only when you are removing asingle node, a standalone vertical cluster, or the last node in a horizontalcluster.




8.2 Removing Runtime and Core Services on UNIX or Linux


8.2.5 Removing Externally Installed Directory Services

To remove externally installed Directory Services:

1. Stop OpenText Directory Services (OpenDS) by executing<DIRECTORY _LOCATION >/OpenDS-2.2.0/bin/stop-ds.

2. Delete the <DIRECTORY _LOCATION >/OpenDS-2.2.0 directory.

3. Delete the otds.dsd.properties file from<CONN_PROPERTIES_LOCATION >.

4. If you selected USE_LDAPS=Y when you installed Runtime and Core Serviceswith Directory Services, delete the .keystore file from <KEYSTORE _LOCATION >.For example, /opentext/rcs/security.






Chapter 9

Backing Up and Restoring Runtime and CoreServices

This section describes how to back up the RCS workspace directory, the database,and your application server immediately after configuring your environment. Youshould also back up Runtime and Core Services before making any major changes tothe system, for example, before installing new applications or upgrading to a newversion of Runtime and Core Services. For more information, see the followingsections:

• “Backing Up Runtime and Core Services” on page 105 • “Restoring Runtime and Core Services” on page 106

9.1 Backing Up Runtime and Core Services

To create a backup of Runtime and Core Services:

1. Stop your application server and back up any application server data files.

a. On Tomcat, perform the following steps:

• Stop all Tomcat instances on all Runtime and Core Services servers.

• Back up the <Tomcat _home > directory.• Back up the <Tomcat _home >_instances directory if it exists.

b. On NetWeaver, stop the opentext.com/ot-content-services applicationusing NetWeaver Administrator.

2. Back up the RCS workspace directory using the backup system you have inplace.

Tip: Verify that your backup is accessible.

3. On UNIX or Linux, back up the /etc/opentext/inst_dirs/R_CS.inst directory.

4. If you have additional modules or applications installed into Runtime and CoreServices, review the documentation for these modules and perform anynecessary backups.

5. Back up your external Runtime and Core Services database.

Tip: See your DBMS documentation for back up procedures correspondingto your DBMS.



Chapter 9 Backing Up and Restoring Runtime and Core Services


6. Restart your application server.

a. On Tomcat, restart Tomcat on all Runtime and Core Services servers.

b. On NetWeaver, restart the opentext.com/ot-content-services application using NetWeaver Administrator.

9.2 Restoring Runtime and Core Services

To restore Runtime and Core Services from a backup:

1. Resolve any problems and restore your operating system to a working state.

2. Reinstall and configure your application server and any other prerequisites. Formore information, see “Installing Prerequisites for Windows” on page 15 or“Installing Prerequisites for UNIX or Linux” on page 49.

3. On UNIX or Linux, back up the /etc/opentext/inst_dirs/R_CS.inst directory and remove it so that this does not appear to be an upgrade ofRuntime and Core Services.

4. Reinstall Runtime and Core Services using a new RCS

workspace directory anddatabase.

Note: The RCS

workspace directory must have the same name and locationas the backed up RCS

workspace directory. You will replace this workspace

directory with your backed up workspace directory in step 6 on page 106.

5. Restore any additional modules or applications according to theirdocumentation.

6. Restore the RCS


7. Restore the external Runtime and Core Services database.

Note: The database name must have the same name used prior to thebackup.

8. Restore and restart your application server.

a. On Tomcat, perform the following steps:

• Restore the <Tomcat _home > directory that you saved in your backup.

• Restore the <Tomcat _home >_instances directory if you saved it in yourbackup.

•Restart Tomcat on all Runtime and Core Services servers.

b. On NetWeaver, restart the opentext.com/ot-content-services application using NetWeaver Administrator.




Chapter 10

Upgrading Runtime and Core Services andDirectory Services

This section describes how to upgrade your Runtime and Core Services server toversion 10.2.1. The following scenarios are described:

• “Upgrading from Version 10.1.0 to 10.2.1” on page 107

• “Upgrading from Version 10.2.0 to 10.2.1 with CAP” on page 112

10.1 Upgrading from Version 10.1.0 to 10.2.1You can upgrade Runtime and Core Services 10.1.0 on Tomcat without removingthe previous version of the program. The Runtime and Core Services 10.1.0<filestore > directory will be migrated to a new Runtime and Core Services 10.2.1<workspace > directory without removing the <filestore > directory. Validupgrade scenarios are shown in Table 10-1. With any other scenario, upgrading isnot possible.

Note: You can only upgrade Runtime and Core Services automatically if it isinstalled on a Tomcat application server.

If Runtime and Core Services is installed on a NetWeaver application server,you must remove Runtime and Core Services and install Runtime and Core

Services 10.2.1.

Table 10-1: Valid 10.1.0 to 10.2.1 Upgrade Scenarios

You can upgrade

from this installa-

tion:

With this configu-

ration:

To this installation: With this configu-

ration:

<filestore > andLegacy Authentica-tion (CAP)

with an internal da-tabase and LegacyAuthentication(CAP)

<filestore >and

Legacy Authentica-tion (CAP)

a new external da-

tabase and LegacyAuthentication(CAP)

Single RCS 10.1.0node

an external databaseand Legacy Authen-tication (CAP)

Single node RCS10.2.1

the same externaldatabase and Leg-acy Authentication(CAP)



Chapter 10 Upgrading Runtime and Core Services and Directory Services


There are three ways to upgrade Runtime and Core Services:

• The core_services-10.2.1.msi on Windows or the setup.sh shell on UNIXor Linux.

• The OpenText Installation master setup.

• A silent upgrade from RCS 10.1.0 to RCS 10.2.1. Make sure the databaseparameters of the silent upgrade do not conflict with the existing Runtime andCore Services installation. Use the UPGRADEWORKSPACE parameter instead of theFILESTORE parameter to avoid overwriting an existing RCS 10.1.0 filestore directory. For more information, see “Installing Runtime and Core Services Silently” on page 42.

10.1.1 Prerequisites for Upgrading Runtime and Core Services

You cannot upgrade an existing database during a Runtime and Core Servicesupgrade. If you wish to upgrade or change your external database, you mustupgrade your database before starting the Runtime and Core Services upgrade.

You can upgrade from a Runtime and Core Services 10.1.0 installation that does nothave an external database to Runtime and Core Services 10.2.1 with an externaldatabase. The upgrade detects that you have no external database and offers you theopportunity to use a new external database.

Important

Do not remove Tomcat 5.5 before upgrading Runtime and Core Services.

Patch RCS-1010-004 or higher must be installed before upgrading Runtimeand Core Services from 10.1.0 to 10.2.1.

To prepare your Runtime and Core Services server for upgrading:

1. Back up your <filestore > directory, your RCS database, and your Tomcat 5.5installation.

2. Verify that each of these backups are successful and accessible.

3. Stop Tomcat 5.5 on all cluster nodes.

4. Upgrade your Java Runtime Environment to JRE 6. To verify your Javaenvironment, use the command java

-version or go the Java Download Centerat http://java.com/en/download/index.jsp.

5. Optionally for Windows, upgrade your Microsoft .NET framework if you areupgrading Administration Client.

6. Install Tomcat 6.0 or upgrade your Tomcat application server to Tomcat 6.0. Forinformation on how to migrate a Tomcat 5.5 application server to Tomcat 6.0,see the Apache Tomcat Migration Documentation athttp://tomcat.apache.org/migration.html.


http://tomcat.apache.org/migration.html






10.1 Upgrading from Version 10.1.0 to 10.2.1


If you are installing a vertical cluster, download the Tomcat software version6.0.32 Windows zip from http://tomcat.apache.org/download-60.cgi andextract it to a <zip directory>. Copy all the Tomcat batch files from your <zip directory >\bin to <Tomcat _home >\bin.

10.1.2 Upgrading Runtime and Core Services on Windows

When you have met all prerequisites, start the Runtime and Core Servicesinstallation on Windows.

Note: If you have started the upgrade using the OpenText Installation mastersetup, select Runtime and Core Services, and skip step 1.

To upgrade Runtime and Core Services on Windows:

1. Start the Runtime and Core Services installation.

2. In the Runtime and Core Services welcome window, click Next.3. Read the license agreement, select I accept the terms in the License Agreement

and click Next.

4. Enter the path to a new RCS workspace directory.

Important

Choose a new directory. Do not overwrite the existing Runtime andCore Services 10.1.0 <filestore > directory.

5. Continue to follow the procedure to install Runtime and Core Services 10.2.1 on

Windows. For more information, see step 5 in “To install Runtime and CoreServices:” on page 21.

6. If there is no external database currently configured, the upgrade will ask you ifyou want to Use external database system. An external database is required forcluster installations. For more information, see step 13 in “To install Runtimeand Core Services:” on page 21.

Note: The upgrade assistant will detect an existing Microsoft SQL Serveror Oracle Database. Database configuration settings will be createdautomatically.

7. Click Install to begin the upgrade.

8. When the upgrade procedure has finished, click Finish.Note: If the master setup was used for updating Runtime and CoreServices, the necessary post-installation tasks will occur. If the task fails,contact OpenText Customer Support.







9. Secure your server using Secure Sockets Layer (SSL) before starting yourRuntime and Core Services server. For more information, see “Securing Your Server” on page 73.

10. Restart your application server.

Note: To remove RCS 10.1.0 after upgrading to RCS 10.2.1, see RemovingRuntime and Core Services on Windows in the OpenText Runtime and Core Services10.1.0 Installation Guide in the Knowledge Center athttps://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=15687898&objAction=browse&viewType=1.

To revert Runtime and Core Services on Windows after upgrading:

1. Stop Tomcat 6.0 and revert back to JRE 1.5.

2. Remove RCS 10.2.1. For more information, see “Removing Runtime and Core

Services” on page 95.3. Remove Tomcat 6.0, removing everything from the <Tomcat _home > directory.

4. Restore the RCS database, the RCS <filestore >, and Tomcat 5.5.

5. Restart Tomcat.

10.1.3 Upgrading Runtime and Core Services on UNIX or Linux

When you have met all prerequisites, start the Runtime and Core Services upgradeon UNIX or Linux as root.

To upgrade Runtime and Core Services on UNIX or Linux:

1. Make sure that JAVA_HOME is set. For more information, see step 2 on page 56.

2. Make sure that JDK 1.6 is included in your PATH environment variable. For moreinformation, see “To set up the environment for Runtime and Core Services installation:” on page 56.

3. Run the master setup script by typing ./mastersetup and pressing ENTER.Select Runtime and Core Services from the Installation Scenarios underthe Library Web Services selection and press n, ENTER until all selectionshave been made.

4. Read the license agreement. To accept it, press a, ENTER.

Note: The upgrade will check that you have sufficient disk space and willindicate whether your upgrade from 10.1.0 to 10.2.1 is possible.

5. Continue to follow the procedure to install Runtime and Core Services 10.2.1 onUNIX or Linux. For more information, see step 6 in “To install Runtime andCore Services:” on page 56.

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=15687898&objAction=browse&viewType=1






10.1 Upgrading from Version 10.1.0 to 10.2.1


Important

Choose a new directory. Do not overwrite the existing Runtime andCore Services 10.1.0 <filestore > directory.

6. If there is no external database currently configured, the upgrade will ask you ifyou want to Use

external

database

system. Press y, ENTER to enter externaldatabase configuration parameters. For more information, see step 11 in “Toinstall Runtime and Core Services:” on page 56.

7. At the end of collecting parameters, press y, ENTER to start the configurationcheck.

Tip: If you press n, ENTER to continue without the configuration check,you will be asked if you want to exit. To cancel the upgrade, press y,ENTER. To return to the configuration check, press n, ENTER. You cannot

continue with the upgrade until you complete the configuration check orcancel the upgrade.

8. If the configuration check returns any errors, solve the problem(s) and restartthe upgrade. If no errors are reported, press y, ENTER to perform the upgrade.

The master setup will run the necessary post-upgrade tasks. If the tasks fail,contact OpenText Customer Support. You can find detailed logging informationin /tmp/opentext_instlog/R_CS/r_csInstall.log

9. Secure your server using Secure Sockets Layer (SSL) before starting yourRuntime and Core Services server. For more information, see “Securing YourServer” on page 73.

10. Restart Tomcat.

Important

• Start Tomcat with the user you used for the installation; see step 4 onpage 57.

• Back up your newly upgraded RCS

workspace directory after install-ing Runtime and Core Services.

To revert Runtime and Core Services on UNIX or Linux after upgrading:

1. Stop Tomcat 6.0 and revert back to JRE 1.5.

2. Remove RCS 10.2.1. For more information, see “Removing Runtime and CoreServices” on page 95.

3. Remove Tomcat 6.0 and remove everything from the <Tomcat _home > directory.

4. Restore the RCS database, the RCS <filestore >, and Tomcat 5.5.

5. Restore the /etc/opentext/inst_dirs/R_CS.inst directory.





6. Restart Tomcat.

10.2 Upgrading from Version 10.2.0 to 10.2.1 with

CAPUpgrading from Runtime and Core Services 10.2.0 to Runtime and Core Services10.2.1 with CAP requires manual steps. You can only upgrade in the followingscenarios:

Table 10-2: Valid 10.2.0 to 10.2.1 Upgrade Scenarios

From this installation: To this installation:

RCS 10.2.0 using an internal database(Derby)

RCS 10.2.1 using Derby

RCS 10.2.0 using Oracle Database 11.2 RCS 10.2.1 using Oracle Database 11.2

RCS 10.2.0 using Microsoft SQL Server 2008 RCS 10.2.1 using Microsoft SQL Server 2008(Windows only)

Note: You cannot upgrade from a single RCS 10.2.0 installation to a clusteredRCS 10.2.1 installation.

The manual upgrade of RCS 10.2.0 using CAP to RCS 10.2.1 using CAP requires thefollowing steps:

1. Back up your Runtime and Core Services 10.2.0 installation. See “To Back Up Runtime and Core Services for Manual Upgrade” on page 113.

2. Remove Runtime and Core Services 10.2.0, deleting the RCS workspace

directory manually. See “To Remove Runtime and Core Services for Manual Upgrade” on page 113.

3. Optionally, upgrade your Tomcat version. For more information on Tomcatversions for Runtime and Core Services 10.2.1 see “Application Server” onpage 10.

4. Install Runtime and Core Services 10.2.1 with Legacy Authentication and noclustering using the database that was previously used for Runtime and CoreServices 10.2.0.

Caution

Do not start Tomcat. Wait until you have removed the RCS 10.2.0database entries.

Note: On UNIX or Linux, ignore any messages that indicate that upgradeis not possible because Runtime and Core Services is not installed.



10.2 Upgrading from Version 10.2.0 to 10.2.1 with CAP


5. Remove Runtime and Core Services 10.2.0 specific entries from your database.See “To Remove Runtime and Core Services 10.2.0 Database Entries” onpage 114.

6. Start Tomcat and sign in to the Administration Client using the otadmin password that you used for Runtime and Core Services 10.2.0.

7. Optionally, upgrade other services that use Runtime and Core Servicesmanually. See “To Upgrade Other Services Manually” on page 114.

10.2.1 To Back Up Runtime and Core Services for Manual

Upgrade

To back up Runtime and Core Services for manual upgrade:

1. Back up the RCS

workspace directory. This also backs up the internal databasein the rcsConfigDb directory if it is in use.

2. For UNIX or Linux, back up the /etc/opentext/inst_dirs/R_CS.inst directory.

3. Back up the <Tomcat_home> directory. This backs up all Runtime and CoreServices related cars, jars and files.

4. Back up your database. If you are using an Microsoft SQL Server database, seeHow to Back up a Database in the Microsoft Developer Network athttp://msdn.microsoft.com/en-us/library/ms187510.aspx. If you are using anOracle Database, use an appropriate tool such as Oracle Recovery Manager.

10.2.2 To Remove Runtime and Core Services for Manual

Upgrade

To remove Runtime and Core Services for manual upgrade:

1. On Windows, remove Runtime and Core Services, clearing the Remove theRCS Workspace check box in the Remove user data window. For moreinformation, see Removing Runtime and Core Services on Windows in the OpenTextRuntime and Core Services 10.2.0 Installation Guide in the Knowledge Center athttps://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=18002304&objAction=browse&viewType=1.

2. On UNIX or Linux, remove Runtime and Core Services manually. For moreinformation, see Removing Runtime and Core Services on UNIX or Linux in the

OpenText Runtime and Core Services 10.2.0 Installation Guide in the KnowledgeCenter athttps://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=18002304&objAction=browse&viewType=1.

http://msdn.microsoft.com/en-us/library/ms187510.aspx















Note: Ensure that the /etc/opentext/inst_dirs/R_CS.inst directoryhas been removed so that this does not appear to be an upgrade ofRuntime and Core Services.

3. Delete the RCS workspace directory.

10.2.3 To Remove Runtime and Core Services 10.2.0 Database

Entries

To remove Runtime and Core Services database entries:

1. If you are deleting properties from an internal Derby database, copy the backedup rcsConfigDb directory to the new Runtime and Core Services 10.2.1workspace directory and set schema rcsConfigDb.

2. In an appropriate database manager, locate the rcs_config_property table.Remove the Runtime and Core Services entries using these commands:• DELETE FROM rcs_config_property WHERE

prop_key='rcs.services.JMSServerProxy.class'• DELETE FROM rcs_config_property WHERE

prop_key='rcs.installed.version'• DELETE FROM rcs_config_property WHERE prop_key like 'installed.files%'• DELETE FROM rcs_config_property WHERE prop_key like '%10:2:0%'

10.2.4 To Upgrade Other Services Manually

To upgrade other services manually:

1. Stop your application server.

2. Install the 10.2.1 CAR or WAR files of any other services into the RCS

workspace/-

modules/install directory.

3. Remove any database entries that are specific to Runtime and Core Services10.2.0 for the deployed services.

4. Restart Tomcat to deploy the services.

10.2.5 To Revert Runtime and Core Services After Upgrading

To revert Runtime and Core Services after upgrading:

1. Remove RCS 10.2.1. For more information, see “Removing Runtime and CoreServices” on page 95.

2. If the Tomcat 6.0 version was upgraded, remove Tomcat 6.0 and everythingfrom its <Tomcat_home> directory. Revert back to the previous version ofTomcat.



10.2 Upgrading from Version 10.2.0 to 10.2.1 with CAP


3. Restore the RCS database, the RCS workspace directory and the previousversion of Tomcat 6.0. On UNIX or Linux, also restore the/etc/opentext/inst_dirs/R_CS.inst directory.

4. Restart Tomcat.






Chapter 11

Changing Directory Services Connection Properties

This section describes how to change the connection properties of a Runtime andCore Services server. There are two scenarios that can be changed:

Runtime and Core Services using an existing remote Directory Services serverIf you install Runtime and Core Services using an existing Directory Servicesserver for authentication, you must supply connection parameters as shown instep 9 of “To install Runtime and Core Services:” on page 21. If this existingDirectory Services server is changed because Runtime and Core Services isupgraded or reinstalled, your connection parameters to this Directory Services

server will be invalid. In order to reactivate authentication using your updatedDirectory Services server, you must update the connection parameters that pointto this server.

Note: You can only change the connection parameters for servers that pointto a remote Directory Services server. You cannot change the resourceidentifier of the local Directory Services server.

Runtime and Core Services with Directory Services (OpenDS) installed externallyIf you install Runtime and Core Services with Directory Services installedexternally, you specified connection properties to your Directory Services serverin step 8 of “To install Runtime and Core Services:” on page 21. You may want tochange these connection properties if your Directory Services server is updated.

To change the externally installed Directory Services server, please see section 11"Changing an External Directory Services Server" in OpenText Directory Services - Administration Guide (OTDS-AGD).

11.1 Changing Directory Services Connection

Properties on Windows

To change the Directory Services connection parameters:

1. From your server, open the installed programs list in the Control Panel, selectyour OpenText Runtime and Core Services installation, and selectUninstall/Change.



Chapter 11 Changing Directory Services Connection Properties


2. In the Welcome window, click Next.

3. In the Change or Remove Runtime and Core Services window, click Change.



11.1 Changing Directory Services Connection Properties on Windows


4. In the Installation Options window, choose which properties you want tochange:

Resource identifier and connection propertiesChoose this option to change the connection parameters for a new orchanged Directory Services server.

Directory Server connection propertiesChoose this option to change the connection parameters for a new orchanged externally installed Directory Services server (OpenDS) location.





5. If you are changing your resource identifier and connection properties, in theDirectory Services Parameters window, enter your new connection parameters.These parameters are the same as in the installation setup. For moreinformation, see Table 2-3 on page 30. For examples of when to change yourconnection parameters see Table 11-1.

Table 11-1: New Directory Services Connection Parameters


Server Name Change this property when your IP ad-dress or your host name has changed. Forexample, when you have set up a newDirectory Services server during an up-grade of your network.

Port Change this property when your port haschanged. For example, if you havechanged your configuration to use SSL toaccess your Directory Services server.

Protocol Change this property if you are changingthe protocol used to access your Direc-tory Services server. You may also need

to change the Port if this parameter ischanged.



11.1 Changing Directory Services Connection Properties on Windows



Resource ID Change this property when Runtime andCore Services has been upgraded or rein-

stalled on your Directory Services server.You will need to create a new resource torepresent your local Runtime and CoreServices server.

Activate Select this check box to activate authenti-cation using your new Directory Servicesserver. If you clear this check box, au-thentication will not be activated.

6. If you are changing your Directory Services server connection properties, in theDirectory Services Parameters window, enter your new connection parameters.These parameters are the same as in the installation setup. For moreinformation, see Table 2-2 on page 27.

Note: You should change the first four connection properties if yourDirectory Server (OpenDS) has changed. The Load Balancer URL shouldonly be changed if Runtime and Core Services was changed





7. Click Install.

8. Click Finish.

9. On NetWeaver, restart the opentext.com/ot-content-services andopentext.com/ot-netweaver-adapter applications in SAP MMC.

11.2 Changing Directory Services Connection

Properties on UNIX or LinuxChanging the Directory Services connection parameters is not currently supportedon UNIX or Linux.




Index

A

Administration Client

installing 71

logging 72

prerequisites 71

Apache Tomcat

See “ Tomcat”

B

backing up 105

Runtime and Core Services 105

C

clusters 77

Administration Client 80

failover 80, 83

high-availability 85

horizontal 81

mixed 81

singleton services 83 Tomcat 77

UNIX or Linux 49

vertical 79

conventions 7

D

Directory Services

changing 117

installing externally 37, 63

I

installingsilent 42, 65

J

Java options

UNIX or Linux 52

Windows 17

L

load balancers 16

log files


logging


N

NetWeaver

prerequisites 19, 54 SSL 21, 56

O

OpenText Online 8

P

post-installation tasks

UNIX or Linux 68

Windows 46

prerequisites


clustering 15 Linux 49

NetWeaver (UNIX or Linux) 54

NetWeaver (Windows) 19

Tomcat (UNIX) 50

Tomcat (Windows) 16

UNIX 49

Windows 15

R

restoring 105


reverting on UNIX or Linux

Runtime and Core Services 110 reverting on Windows


Runtime and Core Services

administration 12

application servers 10

backing up and restoring 105



Index

clusters 11

installation checklist 13

installing (UNIX or Linux) 56

installing (Windows setup) 21

installing silently 42 installing silently (UNIX or Linux) 65

Java environment 10

load balancers 12

operating systems 9

securing databases 75

supported databases 10

system requirements 9

upgrading 107

S

SAP NetWeaver

See “NetWeaver” scripts

Tomcat (UNIX) 50

server.xml file 18, 52

silent installation

UNIX or Linux 65

Windows 42

SSL

JMS Server 73


T

Tomcat

changing ports (Windows) 18 configuring (UNIX or Linux) 52

horizontal cluster 17

uninstalling


UNIX or Linux 98

Windows 95

upgradingRuntime and Core Services 107

upgrading on UNIX or Linux


upgrading on Windows


V

vertical cluster

Tomcat 17, 109

Documents

OpenText Runtime and Core Services 10.2.1 - Installation Guide English (ELCS100201-IGD-En-3)