EMC Documentum Documentum® System Version7.2 DeploymentQuickStartGuide EMCCorporation CorporateHeadquarters: Hopkinton,MA01748-9103 1-508-435-1000

EMC®®® Documentum®®®

System

Version 7.2

Deployment Quick Start Guide

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-91031-508-435-1000www.EMC.com

Legal Notice

Copyright © 2012-2015 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change withoutnotice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NOREPRESENTATIONS ORWARRANTIES OF ANY KINDWITH RESPECT TO THE INFORMATION IN THIS PUBLICATION,AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. Adobe and Adobe PDFLibrary are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. All other trademarks usedherein are the property of their respective owners.

Documentation Feedback

Your opinion matters. We want to hear from you regarding our product documentation. If you have feedback about how we canmake our documentation better or easier to use, please send us your feedback directly at [email protected].

Table of Contents

Chapter 1 Getting Started ............................................................................................... 7Deployment Environments Overview ................................................................. 7Deployment Methods........................................................................................ 7Choosing the Right Deployment Method ........................................................... 8

Chapter 2 Using xMS to Provision Documentum Environment ......................................11Provisioning Overview ......................................................................................11Prerequisites....................................................................................................12Preparing Documentum Component Installers....................................................13Provisioning Considerations..............................................................................14Clustered Environments....................................................................................15

Chapter 3 Manually Provisioning a Documentum Environment .....................................17Provisioning Overview ......................................................................................17Prerequisites....................................................................................................17Preparing Documentum Component Installers....................................................18Installing Documentum Content Server and Repository.......................................19Installing Thumbnail Server...............................................................................19Installing xPlore................................................................................................20Installing Content Intelligence Services ..............................................................20Installing Content Transformation Services ........................................................20Deploying Documentum Administrator ...............................................................21

EMC Documentum System Version 7.2 Deployment Quick Start Guide 3

PrefaceThis guide describes the EMC Documentum deployment methodologies for a Documentum system.

Intended Audience

The information in this guide is for administrators who need to deploy a new Documentum system.

Revision History

The following table lists changes in this guide:

Revision Date Description

February 2015 Initial publication.


Chapter 1

Getting Started

This chapter contains the following topics:

• Deployment Environments Overview• Deployment Methods• Choosing the Right Deployment Method

Deployment Environments OverviewDeployment of Documentum requires installation of both the EMC® Documentum® components andthe additional infrastructure hardware and software prerequisites.

• Common Documentum components include:

– Documentum Administrator– Documentum Content Server– Documentum High Volume Server– Documentum Thumbnail Server– Documentum XML Store– Documentum xPlore (packaged with Content Server)

• Additional extended services include:

– Documentum Content Intelligent Services– Documentum Content Storage Services– Documentum Advanced Document Transformation Services (ADTS)– Documentum Audio Video Transformation Services (AVTS)– Documentum Media Transformation Services (MTS)– Documentum Foundation Services– Documentum Trusted Content Services

Make sure you have the appropriate licensing for each component in order to download, install,and execute EMC software.

Deployment MethodsYou can provision environments through the xCelerated Management System (xMS) or manually. Thefollowing table compares the available methods of provisioning an environment:


Getting Started

ProvisioningMethod

xMSComponents

Machines Infrastructure DocumentumSoftwareComponents

Registration

Automated You set up xMSTools and installxMS Server.

xMS Servercreates virtualmachines(VMs).

xMS Serverdeploys toVMware.

xMS Serverinstallscomponents.

xMS Serverregisters theenvironment.

Orchestrated You set up xMSTools and installxMS Server.

You providethe machines(virtual orphysical).

You provideand configureall necessaryinfrastructure

xMS Serverinstallscomponents.

xMS Serverregisters theenvironment.

Manual NA You providethe machines(virtual orphysical).

You provideand configureall necessaryinfrastructure

You installcomponents.

NA

The term Documentum software components refers to the programs listed in Deployment EnvironmentsOverview, page 7 . The following table describes each provisioning method in more detail:

Method Description

Automated xMS manages environments. It provisions deployment environments into the VMwareinfrastructure as virtual applications (vApps). The resulting VMs appear in either vSphereClient or vCloud Director. Provisioning Overview, page 11 and the EMC DocumentumxCelerated Management System Deployment Guide provide more details.

Orchestrated xMS manages environments. You provide the machines (either physical or virtual).You also configure networking and domain on those machines, if needed. You can useMicrosoft Windows Remote Management (WinRM) as an IP-based communicationprotocol. xMS installs components on those machines. Provisioning Overview, page 11and the EMC Documentum xCelerated Management System Deployment Guide providemore details.

Manual You can build a physical or virtual Documentum deployment environment by manuallyinstalling EMC Documentum components and third-party software. ProvisioningOverview, page 17 provides more details. Use the installation guides for each of the EMCDocumentum components to plan and install each component.

If you choose the automated or orchestrated provisioning method, xMS accelerates the deploymentof your environment. The pre-certified blueprint XML files direct the automatic installation of thenecessary software infrastructure and further allow you to configure and provision the environment.

Choosing the Right Deployment MethodUse the automated method to provision Documentum deployment environments when:

• You want to accelerate deployment through automation processes.• You want xMS to create virtual machines for the environment.• You want to deploy the Documentum system on Microsoft Windows Server.• You can leverage VMware infrastructure in your organization.

Use the orchestrated method to provision Documentum deployment environments when:

8 EMC Documentum System Version 7.2 Deployment Quick Start Guide

Getting Started

• You want to accelerate deployment through automation processes.

• You want to provide your own physical or virtual machines.

• You want to deploy the Documentum system on Microsoft Windows Server.

Use the manual method to provision Documentum deployment environments when:

• You want to deploy the Documentum system on Red Hat Linux or Microsoft Windows Server.

• You want to provide your own physical or virtual machines.

• You cannot leverage VMware based automation in your organization.


Chapter 2Using xMS to Provision DocumentumEnvironment


• Provisioning Overview• Prerequisites• Preparing Documentum Component Installers• Provisioning Considerations• Clustered Environments

Provisioning OverviewYou can use xMS to provision, administer, and monitor Documentum system environments. Unlessotherwise indicated, the EMC Documentum xCelerated Management System Deployment Guideprovides detailed instructions for each step.1. Prepare your system. Build your infrastructure. Prerequisites, page 12 provides details.2. Prepare xMS:

a. Set up xMS Tools. This process installs the xMS command-line interface and creates the folderstructure containing important configuration files such as blueprints, environment profiles,properties files, and manifest files. This process also establishes ${xms-tools-home} and${media-location}.

b. Install and configure the xMS Server.c. Set up one or more xMS Server users.

3. (Optional) If you want to set up monitoring of provisioned environments, install a Hyperic serverand the initial Hyperic agent.

4. Download all the required EMC Documentum installers. Preparing Documentum ComponentInstallers, page 13 provides details.

5. (Optional) Prepare an environment template.

This step is optional because you can provision your environment using a default environmenttemplate in the xMS Management Center.

6. Determine which provisioning options to use. Provisioning Considerations, page 14 providesdetails.

7. Provision the Documentum System environment.

Provisioning includes configuring deployment parameters and endpoints, and using xMS toconfigure machines based on an environment template. xMS manages the configuration of allDocumentum and third-party software needed in the environment.

8. (Optional) Monitor the environment.


Using xMS to Provision Documentum Environment

Once you have provisioned Documentum environment using xMS, you can manually add licensesusing the Content Server configurator program or manually install compatible applications.

PrerequisitesThe following table lists documents that contain information about the prerequisites for Documentumsystem environments:

Prerequisites for Sources of information

Each Documentum component EMC Documentum Environment and System Requirements Guide

Preparing Documentum Component Installers, page 13 describes thelocation to place each component file

Any third-party software, such asdatabase software, tc Server, andHyperic

Third-party documentation

xMS Server and xMS Tools EMC Documentum xCelerated Management System DeploymentGuide

The following table lists the ports that need to be unlocked because they are used by otherDocumentum products:

Documentum product Port

Documentum Content Intelligence Services (CIS) • Default port is 8079.

• Default JMX agent port is 8061.

• RMI port is 1099.

• Ports: 3690, 4445, 7130-7229, 9000, 10000-11000,32000-32999, 37579, 40002, 55550-55649.

Documentum xPlore • Default base port for the server is 9300. The next100 consecutive ports must be available.

• Default base port for the index agent is 9200. Thenext 20 consecutive ports must be available.

Documentum Content Server • Default port is 9080.

• Default connection broker port is 1489. The nextconsecutive port number (1490) must be available.

Documentum Content Transformation Services (CTS) • Default port is 9095.

• Default content transformation serviceswebservices port is 9096.

Documentum Thumbnail Server • Default Thumbnail Server port is 8081.

• Default administration port is 8008.

You can override default port values during a manual installation.



Preparing Documentum Component InstallersThe Documentum system requires all components unless otherwise indicated.

1. Download the installer files for the Documentum components listed in the following table.Documentum components are available on EMC Online Support https://support.emc.com. Copy thefiles to the locations within the ${media-location}\installs folder, as specified in the following table.

Main components Location and file name

Documentum Content IntelligenceServices (CIS)

\CIS\<version>\Content_Intelligence_Services_<ver-sion>_windows.zip

CIS DAR file \CIS\<version>\dar\cis_artifacts.dar

Documentum Content Server \Repository\<version>\Content_Server_<version>_win-dows64_sql.zip

or

\Repository\<version>–Oracle\Content_Server_<ver-sion>_windows64_oracle.zip

Documentum Content TransformationServices (CTS)

• \CTS\<version>\ADTS_<version>_windows.zip

• \CTS\<version>\AVTS_<version>_windows.zip

• \CTS\<version>\MTS_<version>_windows.zip

CTS DAR files \CTS\<version>\dars\CTSAspects.dar, Rich_Media_Ser-vices.dar, and Transformation.dar

Documentum Administrator (DA) \DA\<version>\da.war

Documentum Thumbnail Server \ThumbnailServer\<version>\Thumbnail_Server_<ver-sion>_windows.zip

Documentum xPlore \Search\xPlore<version>\xPlore_<version>_windows-x64.zip

xMS Server \xMS_server\1.2\xms-server.war

Hereafter, all EMC Documentum products are referred to by their product names. For example,Documentum Content Intelligence Services (CIS) is referred to as Content Intelligence Services orCIS.

In cases where you have a choice of paths or filenames for a component, the system uses theone specified in the blueprint file.

2. Download the installer files for the components listed in the following table. Copy the listed installerfiles of third-party components to the locations within ${media-location}\installs as follows:

Prerequisite software Location and file name

(Optional) Apache Web Server supports a blueprintconfigured for clustering.

\3rdparty\ApacheServer\<version>\httpd-<full-version>-win32-x86-no_ssl.msi

(Optional) Hyperic Enterprise managementapplication supports monitoring.

\3rdparty\Hyperic\<version>\hyperic-hq-agent-<full-version>-win32.zip andhyperic-hq-installer-<full-version>-win32.zip

Java Development Kit (JDK) \3rdparty\JDK\<version>\jdk-<full-version>-windows-x64.exe



Prerequisite software Location and file name

JDBC drivers supports early error detection such asvalidating database credentials.

\3rdparty\JdbcDrivers\sqljdbc <version>.jar orojdbc <full-version>.jar

Oracle Client supports Content Server for Oracle. \3rdparty\OracleClient\<version>\win64_<full-version>_client.zip

SqlTools supports Content Server for SQL Server. \3rdparty\SqlTools\<version>\SqlCmdLnUtils.msiand sqlncli.msi

Application server supports the automatedprovisioning method.

\3rdparty\tcServer\<version>-SE\vfabric-tc-server-standard-<full-version>.RELEASE.zip

or

3rdparty\tomcat\<version>\apache-tomcat-<version>.zip

In cases where you have a choice of paths or filenames for a component, the system uses theone specified in the blueprint file.

Provisioning Considerations

Automated Provisioning Considerations

The following table lists various options which can help if you use the automated provisioning method:

Considerations Description

Log file redirectionfor centralizedtroubleshooting

Allows you to redirect logs of components such as Content Server (cs-logs),xPlore (xPlore-logs), Content Transformation Services (cts-logs), or ContentIntelligence Services (cis-logs) to a single location in their respective VMs. Bydefault, each Documentum component creates logs in different locations. TheEMC Documentum xCelerated Management System Deployment Guide providesmore information.

Automated and Orchestrated Provisioning Considerations

The following table lists various options which can help if you use the automated or orchestratedprovisioning method:


Clustered deploymentenvironments

Using xMS, you can set up clusters of Documentum components or services toenable load balancing, scalability, and high availability. Configuring a componentin a clustered configuration can improve throughput and availability, and it canmatch computing resources to actual demand. The EMC Documentum xCeleratedManagement System Deployment Guide describes how to provision clusteredenvironments.

Non-clustereddeploymentenvironments

Using xMS, you can also set up non-clustered deployment environments. TheEMC Documentum xCelerated Management System Deployment Guide describeshow to provision non-clustered environments.




Data storage for highavailability

By default, the Content Server repository service uses data storage on the samemachine where you installed the Content Server. However, for clustering or highavailability, you can configure the Content Server repository service to use datastorage outside of that machine, which provides the following benefits:

• If you have only one Content Server machine in your Documentum environmentand that Content Server fails, data storage outside that machine enables easierdisaster recovery.

• If you build a cluster of Content Servers and if a Content Server node in thatcluster fails, other Content Server nodes can continue to access the data.

Data storage outside the Content Server machine can be internal or external tothe Documentum environment. The EMC Documentum xCelerated ManagementSystem Deployment Guide provides more information.

External connectionbroker to bridge externaland internal networks

Provisions an environment that uses two connection brokers: one using the internalnetwork and the other listening on an external network. For example, when aclient application is on a network separate from the provisioned environment andneeds to connect to components within the provisioned environment, the systemneeds two connection brokers. The system always installs the internal connectionbroker with the repository service by default. For external IP configuration, installan additional connection broker. The EMC Documentum xCelerated ManagementSystem Deployment Guide provides more information.

Database details Provisions an environment to work with a specific external database. For example,provision an environment to enable the Documentum repository to use an externalOracle database. The EMC Documentum xCelerated Management SystemDeployment Guide provides more information.

Environment mode Indicates an environment running in a production mode. The EMC DocumentumxCelerated Management System Deployment Guide provides more information.

Clustered EnvironmentsConfiguring a component in a clustered configuration can improve throughput and availability, and itcan match computing resources to actual demand. Setting up clusters of components or services isan optional method. Using xMS, you can set up clusters of components or services to enable loadbalancing, scalability, and high availability.

The following table lists the components that you can set up as logical service clusters in yourenvironment:Component Corresponding Service Support Details

Content Server Repository Service • Multi-instance

• Active-active mode

Application Server App Host Service • Multi-instance

• Apache HTTP Server as a loadbalancer

xPlore Search Service • Multi-instance

• Active-active mode



Component Corresponding Service Support Details

MTS MTS Service Multi-instance

ADTS ADTS Service Multi-instance

AVTS AVTS Service Multi-instance

The Documentum clustered environment blueprint file contains the default property values for acomponent cluster. If you want to provision an environment with new property values for a componentcluster, do so in the environment profile file or in the xMS Management Center:

• When you use a command to provision an environment, xMS references the Documentum clusteredenvironment blueprint and Documentum clustered environment profile files, and instantiates theminimum number of nodes.

• When you use the xMS Management Center, xMS references the hosts and other values you haveconfigured.

At provisioning time, you can set the size (the number of nodes) for each cluster. The EMCDocumentum xCelerated Management System Deployment Guide provides more information aboutprovisioning clustered deployment environments.

The Documentum clustered environment blueprint file contains a cluster for the repository componentand its property values as shown in the following example:<vm-cluster name="repoVM" affinity="ANTI_AFFINITY" key="R"><size>${repoVM.cluster.size=2}</size><cpu>${repoVM.cpu=2}</cpu><memory>${repoVM.memory=2GB}</memory><vm-template nameref="windowsTemplate" /></vm-cluster>

In the Documentum clustered environment profile file, you can provide new property values withinthe <configuration-context> element for the repository component as shown in the followingexample:<configuration-context><property name="repoVM.cpu" value="4"><property name="repoVM.memory" value="4GB">...</configuration-context>


Chapter 3Manually Provisioning a DocumentumEnvironment


• Provisioning Overview• Prerequisites• Preparing Documentum Component Installers• Installing Documentum Content Server and Repository• Installing Thumbnail Server• Installing xPlore• Installing Content Intelligence Services• Installing Content Transformation Services• Deploying Documentum Administrator

Provisioning OverviewYou can provision a Documentum environment manually using the following steps:1. Install all prerequisite software into a physical or virtual environment.2. Download and install Documentum components into a physical or virtual environment. Preparing

Documentum Component Installers, page 18 provides details.

PrerequisitesThe following table describes where to find information about the prerequisites for Documentumsystem environments:

Prerequisites for Sources of information

Each Documentum component EMC Documentum Environment and SystemRequirements Guide

Any third-party software, such as database softwareand application server

Third-party documentation

Prerequisites, page 12 lists the ports that need to be unlocked because they are used by otherDocumentum products.


Manually Provisioning a Documentum Environment

Preparing Documentum Component Installers1. Install each of the components listed in the following table, in the order listed, into a physical or

virtual environment. Download all components from EMCOnline Support https://support.emc.com,except third-party software. The EMC Documentum System Upgrade and Migration Guideprovides more information about various components of Documentum that must be installed.

Component Source of information

JDK JDK documentation

Content Serverand DocumentumMessaging Services(DMS)

EMC Documentum Content Server Installation Guide

Thumbnail Server EMC Documentum Thumbnail Server Installation Guide

xPlore EMC Documentum xPlore Deployment Guide

CIS EMC Documentum Content Intelligence Services Installation Guide

CTS EMC Documentum Content Transformation Services Installation Guide

DA EMC Documentum Administrator Deployment Guide

Application server EMC Documentum Environment and System Requirements Guide

2. Record information about your environment. You may need the following information later:

• Search Index Agent username and password

• Search Dsearchadmin password

• Repository administrator username and password

• Repository name

• Repository port

• Repository host (IP address or host name)

• xPlore host (IP address or host name)

• xPlore Server Search port

• xPlore Index Agent port

• xPlore Server URL

• Index Agent URL

• Process Integrator URL

• DA URL

• CTS host (IP address or host name)

• CIS host (IP address or host name)



Installing Documentum Content Server andRepositoryContent Server software manages repositories and provides content management capabilities. Arepository consists of three main components—a file store containing the content assets, attributetables within a relational database, and full-text indexes. Content Server and repository can be installedin different ways to support different scenarios. The basic installation model installs a single ContentServer and at least one repository and connection broker on a single host.

A basic installation of Content Server consists of several interrelated components:

• File store: Contains the content files for objects stored in the repository.

• Relational database: Stores metadata for the content files.

• Content Server: Manages repositories. Content Server consists of several distinct processes andcomponents, including an application server reserved for its internal use.

• Repositories: Consists of one or more repositories. You need to designate one of these repositoriesas the global registry.

• Connection broker: Provides repository connection information to client applications.

• Documentum Foundation Classes (DFC): Provides the programming interface that clientapplications use to communicate with Content Server.

• SMTP server: Content Server uses this SMTP server to send tasks and notification messages to usermailboxes, when necessary.

You can install Content Server in different configurations. In production environments, the ContentServer and database are almost always installed on different hosts for increased performance. TheEMC Documentum Content Server Installation Guide provides more information about DocumentumContent Server and Documentum repository.

Installing Thumbnail ServerThumbnail Server serves graphic files from a thumbnail file store on the Content Server host. Itprovides these thumbnails to Web client applications. Thumbnails are renditions created by ContentTransformation Services when a file is imported or checked in to the repository. Thumbnail ServerInstaller installs the Thumbnail Server software and sets the base_url attribute for file store objects,which are defined for repositories residing on the host thumbnail storage areas.

The base_url is set to a URL that identifies the Thumbnail Server. Its value is used by applications toconstruct complete URLs for files in the thumbnail storage area. A file store is a thumbnail storagearea when its media_type attribute is set to 1.

The Thumbnail Server is installed as a service, set to start automatically upon system restart.

Thumbnail Server must be installed on the same host as your Documentum Content Server. Downloadthe Thumbnail Server Installer from EMC Online Support https://support.emc.com. The EMCDocumentum Thumbnail Server Installation Guide provides more information about installing andconfiguring the Thumbnail Server.



Installing xPlorexPlore provides query and indexing services that can be integrated into external content sources suchas the Documentum content management system. External content source clients like CenterStage, orcustom Documentum DFC clients, can send indexing requests to xPlore.

Each document source is configured as a domain in xPlore. xPlore provides a web-based administrationconsole and you can set up domains using xPlore Administrator. For Documentum environments,the Documentum index agent creates a domain for each repository and a default collection withinthat domain.

Documents are provided in an XML representation to xPlore for indexing through the indexing APIs.In a Documentum environment, the Documentum index agent prepares an XML representation of eachdocument. The document is assigned to a category, and each category corresponds to one or morecollections as defined in xPlore. To support faceted search in Documentum repositories, you can definea special type of an index called an implicit composite index.

The Documentum xPlore Installation Guide provides more information about xPlore.

Installing Content Intelligence ServicesThe Content Intelligence Services (CIS) is the content analytics component for EMC Documentum.Use content analytics to analyze the textual content of documents and know what the documentsare about without having to read them. Enable users to find documents rapidly by enriching searchfacets with discovered metadata and get the summary of a document by viewing discovered metadatawith the document.

CIS includes these key components:

• The CIS client can be used for creating, managing, or displaying the taxonomy used for categorizingdocuments. Examples of CIS clients are Documentum Administrator, Webtop, or any customapplication using the Content Intelligence Application Programming Interface (CI API). UseDocumentum Administrator to configure CIS. The CI API handles communication amongst theCIS client, the CIS server, and the repository.

• The CIS server performs the automatic categorization of documents based on taxonomy andcategory definitions. It also performs the pattern detection, and triggers the entity detection.

• The entity detection server performs the entity detection analysis using cartridges.• A repository is also required to store CIS data (such as taxonomy definitions, document setdefinitions, and discovered metadata).

The EMC Documentum Content Intelligence Services Installation Guide provides procedures forinstalling the Content Intelligence Services.

Installing Content Transformation ServicesContent Transformation Services (CTS) encapsulates the functionality of all transformationcomponents that includes Advanced Document Transformation Services, Media TransformationServices and Audio Video Transformation Services.



Install CTS products using separate installers, depending on your needs. If necessary, you can installall three CTS products on the same CTS host:

• Documentum Advanced Document Transformation Services (ADTS)

• Documentum Audio Video Transformation Services (AVTS)

• Documentum Media Transformation Services (MTS)

You need to install Content Transformation Services DAR files before configuring ContentTransformation Services. Install the DAR files in the global repository and in each repository whereContent Transformation Services must be configured. Install the following DAR files:

• Rich Media Services

• Transformation

• CTS Aspects

You can use the DAR installer program to provide installation, repository, and global registryinformation dynamically.

DFC must be installed in the same location as Content Transformation Services. The EMCDocumentum Content Transformation Services Installation Guide provides procedures for installingthe Content Transformation Services.

Deploying Documentum AdministratorDocumentum Administrator is a Content Server and repository administration tool. DocumentumAdministrator runs on an application server host.

Before Documentum Administrator can connect to repositories, you must provide connection brokerand global registry values in dfc.properties. Documentum Administrator requires a Content Serverversion 6 or later global registry. The global registry is a central repository that serves several purposes:

• Deploys service-based business objects (SBOs)

• Stores network location objects

The EMC Documentum Administrator Deployment Guide provides more information about deployingthe Documentum Administrator on the application server host.


Index

Aactive-active mode, 15Apache Web Server, 13application server, 14automated provisioning method, 8

Cclustered environment, 15connection broker, 15Content Intelligence Services, 13content server, 19Content Server, 13Content Transformation Services, 13

DDARCIS, 13CTS, 13

data storage, 15databaseOracle, 14SQL Server, 14

Documentumcomponents, 7ports, 12

Documentum Administrator, 13Documentum installationorder, 18

Documentum Messaging Services, 18

Eenvironment template, 11environmentsclustered, 14non-clustered, 14

external database, 15

HHyperic agent, 11Hyperic application, 13Hyperic server, 11

JJDK, 13

Llog file, redirection, 14

Mmanual provisioning method, 8mode, active-active, 15

Oorchestrated provisioning method, 8

Pproduction mode, 15provisioningmanual, 17xMS, 11

Rrepository, 19

TThumbnail Server, 13

XxCPcomponent installers, 13

xMSServer, 13

xPlore, 13
