HP ControlPoint 4.3 Installation Guide (English)h30359. Governance...Notice This documentation is a...

HP ControlPointVersion: 4.3

Installation Guide

Document Release Date: June 2014

Software Release Date: June 2014

NoticeThis documentation is a proprietary product of HP Autonomy and is protected by copyright laws and international treaty. Information in this documentation is subject to change without notice and does not represent a commitment on the part of HP Autonomy. While reasonable efforts have been made to ensure the accuracy of the information contained herein, HP Autonomy assumes no liability for errors or omissions. No liability is assumed for direct, incidental, or consequential damages resulting from the use of the information contained in this documentation.

The copyrighted software that accompanies this documentation is licensed to the End User for use only in strict accordance with the End User License Agreement, which the Licensee should read carefully before commencing use of the software. No part of this publication may be reproduced, transmitted, stored in a retrieval system, nor translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, without the prior written permission of the copyright owner.

This documentation may use fictitious names for purposes of demonstration; references to actual persons, companies, or organizations are strictly coincidental.

Trademarks and CopyrightsCopyright © 2014 Audit Center, Autonomy Consolidated Archive, Autonomy Express Search, Autonomy iManage ConflictsManager, Autonomy iManage RecordsManager, Autonomy Interaction Control Element (ICE), Autonomy Message Manager, Autonomy Notification Server, Autonomy Records Manager, Autonomy Windows Extension, DeskSite, Connected, Digital Safe, Digital Supervisor, EAS On-Demand, EAS, Enterprise Archive Solution, FileShare, FileSite, iManage WorkSite MP, iManage WorkSite, iManage, Interwoven, Introspect, LiveVault, Meridio, OffSite, Scrittura, WorkDocs, WorkPortal, WorkRoute, WorkSite MP, WorkSite, WorkTeam, Zantaz, and all related titles and logos are trademarks of Autonomy Corporation plc and its affiliates, which may be registered in certain jurisdictions.

Microsoft is a registered trademark, and MS-DOS, Windows, Windows 95, Windows NT, SharePoint, and other Microsoft products referenced herein are trademarks of Microsoft Corporation.

UNIX is a registered trademark of The Open Group.

AvantGo is a trademark of AvantGo, Inc.

Epicentric Foundation Server is a trademark of Epicentric, Inc.

Documentum and eRoom are trademarks of Documentum, a division of EMC Corp.

FileNet is a trademark of FileNet Corporation.

Lotus Notes is a trademark of Lotus Development Corporation.

mySAP Enterprise Portal is a trademark of SAP AG.

Oracle is a trademark of Oracle Corporation.

Adobe is a trademark of Adobe Systems Incorporated.

Novell is a trademark of Novell, Inc.

Stellent is a trademark of Stellent, Inc.

Android is a trademark of Google Inc.

All other trademarks are the property of their respective owners.

AcknowledgementsRSA Data Security, Inc. MD5 Message-Digest Algorithm; zlib general purpose compression library, Jean-loup Gailly and Mark Adler; Info-ZIP, more information at ftp://ftp.info-zip.org/pub/infozip/license.html; HTML-to-RTF Pro DLL 1.8 © 2002-2007 SautinSoft.

Notice to Government End UsersIf this product is acquired under the terms of a DoD contract: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of 252.227-7013. Civilian agency contract: Use, reproduction or disclosure is subject to 52.227-19 (a) through (d) and restrictions set forth in the accompanying end user agreement. Unpublished-rights reserved under the copyright laws of the United States. Autonomy, Inc., One Market Plaza, Spear Tower, Suite 1900, San Francisco, CA. 94105, US.

Installation Guide

HP ControlPoint (4.3) of 35

Contents

Contents 3

About This Document 7Documentation Updates 7

Related Documentation 9

Conventions 9

Notational Conventions 9

Command-Line Syntax Conventions 10

Notices 11

Autonomy Product References 11

Autonomy Customer Support 11

Contact Autonomy 12

Chapter 1: Introduction 13HP ControlPoint 13

HP’s IDOL Platform 13

HP ControlPoint Architecture 14

Components 14

ControlPoint Dashboard 14

ControlPoint Engine 14

ControlPoint Client Classifiers 15

ControlPoint Data Analysis Service 15

ControlPoint IDOL 15

Chapter 2: Plan for an HP ControlPoint Installation 17Introduction 17

Prerequisites 17

ControlPoint IDOL Deploy Tool 17

ControlPoint IDOL Package 18

ControlPoint 18

Supported Browsers 18

Windows Server 2008 and 2008 R2 IIS Requirement 18


Windows Server 2012 Requirement 19

Deployment Examples 19

Small Size Deployment 19

Server 1 19

Server 2 19

Medium Size Deployment 20

Server 1 20

Server 2 20

Server 3 20

Large Size Deployment 20

Server 1 20

Server 2 20

Server 3 21

Server 4 21

Chapter 3: Install HP ControlPoint IDOL and Connectors 22Overview 22

Create Deployment Packages 22

Configure Deployment Packages 22

Save Deployment Package Configuration 27

Build Deployment Packages 27

Install Deployment Packages 27

Prerequisites 27

Installation 28

Start Windows Services 28

Stop Windows Services 28

Uninstall Deployment Packages 29

Chapter 4: Install HP ControlPoint Components 30Overview 30

Install ControlPoint Database 30

Install ControlPoint and ControlPoint Engine 32

Install ControlPoint Client Classifiers 33

Installation GuideContents


Configure ControlPoint 33

Database Settings 34

IIS Settings 34

Engine Settings 34

Workflow 34

Data Analysis Settings 35

IDOL Settings 35

Security Settings 35



of 35HP ControlPoint (4.3)


About This DocumentThis document is for system administrators who have to install Autonomy ControlPoint.

l Documentation Updates

l Related Documentation

l Conventions

l Autonomy Product References

l Support

l Contact Autonomy

Documentation UpdatesThe information in this document is current as of HP ControlPoint version 4.3. The content was last modified June 2014.

You can retrieve the most current product documentation from the HP Autonomy Knowledge Base on the Customer Support Site.

A document in the Knowledge Base displays a version number in its name, such as IDOL Server 7.5 Administration Guide. The version number applies to the product that the document describes. The document may also have a revision number in its name, such as IDOL Server 7.5 Administration Guide Revision 6. The revision number applies to the document and indicates that there were revisions to the document since its original release.

Autonomy recommends that you periodically check the Knowledge Base for revisions to documents for the products your enterprise is using.

To access Autonomy documentation

1. Go to the Autonomy Customer Support site:

https://customers.autonomy.com

2. Click Login.

3. Type the login credentials that you were given, and then click Login.

The Customer Support Site opens.

4. Click Knowledge Base.

The Knowledge Base Search page opens.


https://customers.autonomy.com/

5. Search or browse the Knowledge Base.

To search the knowledge base:

n In the Search box, type a search term or phrase and click Search.

Documents that match the query display in a results list.

To browse the knowledge base:

n Select one or more of the categories in the Browse list. You can browse by:

o Repository. Filters the list by Documentation produced by technical publications, or Solutions to Technical Support cases.

o Product Family. Filters the list by product suite or division. For example, you could retrieve documents related to the iManage, IDOL, Virage or KeyView product suites.

o Product. Filters the list by product. For example, you could retrieve documents related to IDOL Server, Virage Videologger, or KeyView Filter.

o Version. Filters the list by product or component version number.

o Type. Filters the list by document type. For example, you could retrieve Guides, Help, Packages (ZIP files), or Release Notes.

o Format. Filters the list by document format. For example, you could retrieve documents in PDF or HTML format. Guides are typically provided in both PDF and HTML format.

6. To open a document, click its title in the results list.

To download a PDF version of a guide, open the PDF version, click the Download icon in the PDF reader, and save the PDF to another location.

To download a documentation ZIP package, click Get Documentation Package under the document title in the results list. Alternatively, browse to the desired ZIP package by selecting either the Packages document Type or the ZIP document Format from the Browse list.

Installation GuideAbout This Document


Autonomy welcomes your comments.

To send feedback on Autonomy documentation

l send email to [email protected]

l provide:

n full document title with version and revision number

n location: heading, a snippet of text or screen capture

n your comments

n your contact information in the event we need clarification

Related DocumentationThe following documents provide more details on ControlPoint.

l ControlPoint Console Administration Guide

l ControlPoint Upgrade Technical Note

ConventionsThe following conventions are used in this document.

Notational ConventionsThis document uses the following conventions.

Convention Usage

Bold User-interface elements such as a menu item or button. For example:

Click Cancel to halt the operation.

Italics Document titles and new terms. For example:

l For more information, see the IDOL Server Administration Guide.

l An action command is a request, such as a query or indexing instruction, sent to IDOL Server.



mailto:[email protected]

Convention Usage

monospace font

File names, paths, and code. For example:

The FileSystemConnector.cfg file is installed in C:\Program Files\FileSystemConnector\.

monospace bold

Data typed by the user. For example:

l Type run at the command prompt.

l In the User Name field, type Admin.

monospace italics

Replaceable strings in file paths and code. For example:

user UserName

Command-Line Syntax ConventionsThis document uses the following command-line syntax conventions.

Convention Usage

[ optional ] Brackets describe optional syntax. For example:

[ -create ]

| Bars indicate “either | or” choices. For example:

[ option1 ] | [ option2 ]

In this example, you must choose between option1 and option2.

{ required } Braces describe required syntax in which you have a choice and that at least one choice is required. For example:

{ [ option1 ] [ option2 ] }

In this example, you must choose option1, option2, or both options.

required Absence of braces or brackets indicates required syntax in which there is no choice; you must type the required syntax element.

variable

<variable>

Italics specify items to be replaced by actual values. For example:

-merge filename1

(In some documents, angle brackets are used to denote these items.)

. . . Ellipses indicate repetition of the same pattern. For example:

-merge filename1, filename2 [, filename3 ... ]

where the ellipses specify, filename4, and so on.



NoticesThe use of punctuation—such as single and double quotes, commas, periods—indicates actual syntax; it is not part of the syntax definition.

This document uses the following notices:

Caution: A caution indicates an action can result in the loss of data.

Note: A note provides information that emphasizes or supplements important points of the main text. A note supplies information that may apply only in special cases—for example, memory limitations, equipment configurations, or details that apply to specific versions of the software

Tip: A tip provides additional information that makes a task easier or more productive.

Autonomy Product ReferencesThis document references the following Autonomy products.

l HP IDOL

Autonomy Customer SupportAutonomy Customer Support provides prompt and accurate support to help you quickly and effectively resolve any issue you may encounter while using Autonomy products. Support services include access to the Customer Support Site (CSS) for online answers, expertise-based service by Autonomy support engineers, and software maintenance to ensure you have the most up-to-date technology.

To access the Customer Support Site

l go to https://customers.autonomy.com

The Customer Support Site includes:

l Knowledge Base. The CSS contains an extensive library of end user documentation, FAQs, and technical articles that is easy to navigate and search.

l Case Center. The Case Center is a central location to create, monitor, and manage all your cases that are open with technical support.

l Download Center. Products and product updates can be downloaded and requested from the



https://customers.autonomy.com/

Download Center.

l Resource Center. Other helpful resources appropriate for your product.

To contact Autonomy Customer Support by e-mail or phone

l go to http://www.autonomy.com/work/services/customer-support

Contact AutonomyYou can contact Autonomy by email at [email protected].

For office addresses, and other contact information, visit www.autonomy.com.



http://www.autonomy.com/work/services/customer-support

mailto:[email protected]

http://www.autonomy.com/

Chapter 1: IntroductionThis section provides an overview of Autonomy HP ControlPoint.

l "HP ControlPoint"

l "HP’s IDOL Platform"

l "HP ControlPoint Architecture"

HP ControlPointThe HP ControlPoint Web application allows you to centrally manage information assets. Managing information from more than 1000 different file types and over 400 different repositories, ControlPoint can apply actions such as legal hold and disposition over a company’s wide area network.

ControlPoint delivers a broad set of functionalities, specifically designed to address the information governance challenges within the enterprise.

l Seamless integration. You can apply consistent Information Governance and eDiscovery across corporate repositories.

l Automated information management using Dashboard views. Customized dashboards provide alerting and transparency to information management processes throughout the enterprise, increase visibility and streamline governance actions such as legal hold and disposition.

l Management of content in place. This process eliminates the need to replicate the content within repositories and across other servers. It also ensures that information related to a legal hold or regulatory matter is not accidentally deleted while in use.

l Enhanced analytics, security and reporting mechanisms. ControlPoint provides support for a rich feature-set for analyzing enterprise content, such as clustering, faceted navigation and visualizations.

l Improved performance. ControlPoint reduces costs and improves performance over wide area networks by providing alternatives to native applications stores (such as SQL Server for SharePoint). It also allows for content to be moved to cheaper storage solutions without interfering with the user experience.

HP’s IDOL PlatformAt the core of HP ControlPoint is HP’s Intelligent Data Operating Layer (IDOL). IDOL gathers and processes unstructured, semi-structured, and structured information in any format from multiple repositories using a global relational index. It can automatically form a contextual understanding of the information in real time, linking disparate data sources together based on the concepts contained within them. For example, IDOL can automatically link concepts contained in an e-mail


message to a recorded phone conversation, which can be associated with a stock trade. This information is then imported into a format that is easily searchable, adding advanced retrieval, collaboration, and personalization to an application that integrates the technology.

For more information on IDOL, refer to the IDOL Concepts Guide and the IDOL Server Getting Started Guide.

HP ControlPoint ArchitectureHP ControlPoint is a Web application user interface. The functionality is available through Dashboards that you can integrate with Portal.NET.

ComponentsControlPoint includes the following components:

l ControlPoint Dashboard

l ControlPoint Engine

l ControlPoint Client Classifiers

l ControlPoint Data Analysis

l ControlPoint IDOL

ControlPoint DashboardThe ControlPoint Dashboard provides administrators an interface to establish and review allocation of policy, and monitor system activity and health.

The following services are included in the ControlPoint:

l ControlPoint Web Interface. An IIS web application that serves as the ControlPoint user interface.

l CPWS (optional). Web services that provide access to ControlPoint resources for ControlPoint Client Classifiers and Workflow capability.

l Classifier Services (optional). Central infrastructure used by ControlPoint Client Classifiers.

ControlPoint EngineThe ControlPoint Engine provides the central capability needed to manage policy content within an organization.

The following services are included in the ControlPoint Engine:

Installation GuideChapter 1: Introduction


l ControlPoint Engine service. A Windows service that executes all scheduled tasks.

l CallbackHandler. An IIS web application that receives notifications from IDOL connectors.

ControlPoint Client ClassifiersControlPoint Client Classifiers allow end users to apply policy or classification tags within applications that are appropriate for the associated source repository—for example, within Windows Explorer for content residing in a file share.

ControlPoint Data Analysis ServiceControlPoint Data Analysis allows organizations to analyze and understand and deal with the unstructured data contained in their legacy repositories. uses IDOL to index the documents in the repositories, analyze them, and present the results of the statistical analysis visually in a dynamic user interface.

ControlPoint IDOLControlPoint IDOL delivers an index of all content that ControlPoint manages. All repositories that are to be considered by ControlPoint for policy application must be indexed into IDOL.

The following services are included in ControlPoint IDOL:

l The ControlPoint IDOL service which contains the central index.

l The ControlPoint Content services which index all of the content and serves search requests.

l The ControlPoint OGS (Omni Group Server) service which collects and aggregates user and group security information from a variety of repositories.

l The ControlPoint FileSystem Connector service which indexes content from file shares.

l The ControlPoint FileSystem Connector Framework service, the interface between the file system connector and IDOL indexing.

l The ControlPoint HP Records Manager Connector service, which archives content into and indexes content from HP Records Manager repositories.

l The ControlPoint HP Records Manager Connector Framework service, the interface between the HP Records Manager connector and IDOL indexing.

l The ControlPoint TRIM Connector service, which archives content into and indexes content from TRIM repositories.



l The ControlPoint TRIM Connector Framework service, the interface between the TRIM connector and IDOL indexing.

l The ControlPoint SharePoint Connector service which indexes content from SharePoint sites.

l The ControlPoint SharePoint Connector Framework service, the interface between the SharePoint connector and IDOL indexing.

l The ControlPoint WorkSite Connector service which archives content into WorkSite repositories.

l The ControlPoint WorkSite Connector Framework service, the interface between the WorkSite connector and IDOL indexing.

l The ControlPoint Distributed Connector service which distributes connector calls to the appropriate connector.

l The ControlPoint IDOL License Server service which controls the licensing of all ControlPoint functionality.



Chapter 2: Plan for an HP ControlPoint Installation

This section describes prerequisites for an HP ControlPoint installation and provides some deployment examples.

l "Introduction"

l "Prerequisites"

l "Deployment Examples"

IntroductionWhen you install ControlPoint, you must also consider the IDOL infrastructure that will be used by ControlPoint to discover items that should have policy applied to them. The ControlPoint installation package includes IDOL software and a number of IDOL connectors for common repository types. Connectors are pre-configured for use with ControlPoint.

The high-level steps you must perform to install ControlPoint are:

1. Identify or install IDOL and appropriate connectors. For more information about installing ControlPoint IDOL using the included Deploy Tool package, see "Install HP ControlPoint IDOL and Connectors" on page 22.

2. Install ControlPoint and ControlPoint Engine.

3. Once you have identified or installed your IDOL infrastructure, you can install the ControlPoint software. For more information about installing ControlPoint components, see "Install ControlPoint and ControlPoint Engine" on page 32.

4. (optional) Install ControlPoint Client Classifiers.

5. For information, see "Install ControlPoint Client Classifiers" on page 33.

PrerequisitesThis section lists the prerequisites for installing the various ControlPoint components.

ControlPoint IDOL Deploy ToolYou must run the ControlPoint IDOL Deploy Tool on a server with a Java Runtime Environment installed.


ControlPoint IDOL PackageYou must install ControlPoint IDOL packages on a server that has the following products installed:

l Microsoft Visual C++ 2005 Redistributable Package


ControlPointYou must install ControlPoint on a server that has the following products installed:

l Microsoft Internet Information Server (IIS) version 7.5 or 8.0.

l Microsoft .Net Framework 4.5

In addition, SQL Server 2008 R2 or higher must be accessible from the ControlPoint server.

Supported Browsers l Internet Explorer 9 or higher when installed on Windows Server

l Internet Explorer 8 or higher when installed on Windows Citrix

l Google Chrome

l Mozilla Firefox

Windows Server 2008 and 2008 R2 IIS RequirementOn Microsoft Windows Server 2008 and 2008 R2, you must add the Windows Authentication Role, which is not installed by default.

To add the Windows Authentication Role

1. In the Windows Start menu, click Administrative Tools > Server Manager.

Windows Server Manager opens.

2. In the hierarchy pane, expand Roles and click Web Server (IIS).

The Web Server (IIS) pane opens.

3. Scroll to the Role Services section and click Add Role Services.

The Add Role Services wizard opens.

Installation GuideChapter 2: Plan for an HP ControlPoint Installation


4. Select Windows Authentication and click Next.

The Confirm Installation Selections page opens.

5. Click Install.

The role is installed and the Results page opens.

6. Click Close.

Windows Server 2012 RequirementOn Windows Server 2012, you must enable Windows Communication Foundation (WCF) Services HTTP Activation. For more information, refer to the Windows Server 2012 documentation.

Deployment ExamplesThis section describes a few typical configurations for a distributed ControlPoint installation.

Small Size Deployment

Server 1 l ControlPoint DiSH

l ControlPoint IDOL

l ControlPoint Content(s)

l Distributed Connector

l Connectors

l ControlPoint OGS

Server 2 l ControlPoint




Medium Size Deployment


l ControlPoint IDOL


Server 2 l Distributed Connector

l Connectors

l ControlPoint OGS



Large Size Deployment


l ControlPoint IDOL


Server 2 l Distributed Connector

l Connectors

l ControlPoint OGS




l ControlPoint Engine 1

Server 4 l ControlPoint Engine 2



Chapter 3: Install HP ControlPoint IDOL and Connectors

This section describes how to install ControlPoint IDOL and connectors.

l "Overview"

l "Create Deployment Packages"

l "Install Deployment Packages"

OverviewTo install ControlPoint IDOL and Connectors

1. Create deployment packages for the target server(s).

2. Copy the deployment packages to the target server(s) and install them.

Create Deployment PackagesThe ControlPoint IDOL Deploy Tool automates the creation of deployment packages for ControlPoint IDOL and connectors. The Deploy Tool does not install IDOL software directly; rather, it builds deployment packages that you must copy to the target server(s) for subsequent installation. Deployment packages are pre-configured by the Deploy Tool and the software requires no further configuration for use with ControlPoint after installation on the target server(s).

Note: You can run the Deploy Tool on any server to create ControlPoint IDOL deployment packages.

You can use the Deploy Tool to configure, save, and build deployment packages.

Configure Deployment PackagesUse the information in this section to configure deployment packages.

To configure deployment packages

1. Start the ControlPoint IDOL Deploy Tool by running setup.bat in the Deploy Tool folder.

The Deploy Tool package build dialog displays with four tabs: General, IDOL, Connectors and Components.

2. On the General tab, enter the following information:


n Deployment Mode. Select Pilot when you are configuring an IDOL system appropriate for a pilot or model office environment. The following defaults are used:

o Log levels for all services are set to FULL.

o The number of threads is reduced for applicable services for use on a small or shared server.

o Memory usage is decreased for applicable services for use on a small or shared server.

o The synchronization times for services are reduced so that index data is updated more frequently.

Otherwise, select Production.

n Host Installation Directory. Specify the directory where components will be installed on the target deployment server(s).

The default location is C:\Program Files\Autonomy.

n Zip File. This option outputs the deployment packages as compressed (zip) archives. This is useful when the deployment packages are to be transferred to different servers - the package size can be in excess of 1 GB.

n Host Package Build Location. Specify the directory where deployment packages will be created when you run the Deploy Tool. The default location is C:\Temp\Autonomy.

n Host Operating System. Select 32-bit or 64-bit depending on the architecture of the host operating system.

n Default Deployment Host. Enter the name of the server that the ControlPoint IDOL Server software will be installed on. The names of servers that will host other components can be defined on the Components tab.

n Default Language Type. Enter the default language type to be used by the ControlPoint IDOL Server. The default language is englishUTF8.

3. On the IDOL tab, enter the following information:

n Number of IDOL Content Engines. Enter the number of ControlPoint Content services that should be created.

n Enable IDOL Mirror Mode. Check this setting if you want to install a mirrored IDOL system.

n Default IDOL Backup Host. Enter the name of the default backup host to be used by your IDOL system.

4. On the Connectors tab, select the connectors you wish to deploy.

Installation GuideChapter 3: Install HP ControlPoint IDOL and Connectors


Available connectors are:

n TRIM Connector

n HP Records Manager Connector

n File System Connector

n SharePoint 2010 Connector

n SharePoint 2007 Connector

n SharePoint Remote Connector

n Exchange Connector

n WorkSite Connector

Each selected connector must be configured.

5. Click the Config button to configure each connector.

The connector configuration dialog opens. The information you must provide depends on the type of connector.

6. Enter the following information for a TRIM Connector:

n Connector Group Name. Enter the name of the connector group.

n Number of Connectors in Group. Enter the number of connectors in the group. The maximum number is 9.

n Deployment Host(s). Enter the server names to which the connectors will be deployed. Each server will host one connector; however, if the number of specified servers is smaller than the number of connectors, the final server in the list will host all remaining connectors.

7. Enter the following information for an HP Records Manager Connector.






8. Enter the following information for a File System Connector:




9. Enter the following information for a SharePoint 2007 or 2010 Connector:




n SharePoint Host. Enter the name of the SharePoint server that hosts the connector web service.

n SharePoint Port. Enter the port number of the connector web service.

n SharePoint Credentials Username. Enter the name of the user to be used when authenticating with the SharePoint server.

n SharePoint Credentials Password. Enter the password for the user to be used when authenticating with the SharePoint server.

10. Enter the following information for a SharePoint Remote Connector.




n SharePoint Credentials Username. Enter the name of the user to be used when authenticating with the SharePoint server.



n SharePoint Credentials Password. Enter the password for the user to be used when authenticating with the SharePoint server.

n SharePoint Credentials Domain. Enter the domain of the specified user.

11. Enter the following information for an Exchange Connector:




n LDAP and Exchange Web Service User Domain. Enter the user domain to use when connecting to both LDAP and the Exchange web service.

n LDAP and Exchange Web Service Username. Enter the user name to use when connecting to both LDAP and the Exchange web service.

n LDAP and Exchange Web Service Password. Enter the password to use when connecting to both LDAP and the Exchange web service.

12. Enter the following information for a WorkSite Connector.




n WorkSite Database Host. Enter the name of the WorkSite SQL Server database.

n WorkSite Database Port. Enter the port number of the WorkSite SQL Server database.

n WorkSite Database Name. Enter the name of the WorkSite SQL Server database.

n WorkSite Mobility Server Host. Enter the name of the WorkSite Mobility Server for iOS.

n WorkSite Mobility Server Port. Enter the port number of the WorkSite Mobility Server for iOS.



n WorkSite Library. Enter the WorkSite library synchronized by the connector.

n IDOL Data Source. Enter the name of the IDOL data source that the content will be indexed into.

n WorkSite Insert Default Username. Enter the name to use when inserting documents into WorkSite.

n WorkSite Insert Default Password. Enter the password to use when inserting documents into WorkSite.

n WorkSite Insert Default Folder ID. Enter the folder where documents will be inserted if no folder is specified in Insert actions.

13. On the Components tab, click the Config button next to a component name to configure that component.

You can configure the following for each component:

n Host. The name of the server that this component will be deployed to.

n Path. The installation location for this component.

Save Deployment Package ConfigurationTo save all configuration settings to a file, select Save or Save As from the File menu.

Build Deployment PackagesTo build deployment packages, click the Deploy button or select Deploy from the Actions menu. The packages are built in the Host Package Build Location you specified on the General tab of the Deploy Tool.

Install Deployment PackagesDeployment packages are created by the Deploy Tool in the location identified by the Host Package Build Location option. Underneath this location are subfolders or compressed (.ZIP) files for each target server. You should move these sub-folders or .ZIP files to the appropriate target server(s) for installation.

PrerequisitesThe following products must be installed on the target server(s) before you can install the Deployment Packages:





Required pre-requisite packages are included in the vcredist subfolder under the deployment package location.

InstallationPerform the steps listed in this section to install deployment packages.

To install a deployment package

1. Run the _deploy_services.bat Windows batch file to copy the components to the location defined in Host Installation Directory.

n If Windows UAC is enabled on the server, you must run the batch file manually from the command line:

i. Open a command prompt as an Administrator.

ii. Change the directory to the temporary location that contains the batch file.

iii. Run _deploy_services.bat.

2. Run the _install_services.bat Windows batch file to install the Windows services.

The user account information to use for each connector service is prompted for during installation.

3. Copy the IDOL license file to the IDOL License Server folder after installation and before services are started.

Start Windows ServicesTo start all of the Windows services, run the _start_services.bat Windows batch file.

If IDOL content engines are located on a different server than the IDOL connectors, it is recommended that you start and verify the IDOL services first before the connectors are started. Starting the connectors will start the indexing process for the locations identified when the connectors were configured in the Deploy Tool.

Stop Windows ServicesTo safely shut down all Windows services, run the _stop_services.bat Windows batch file.

To stop Individual components in isolation, run _stop_service.bat in the component folder.



Uninstall Deployment PackagesYou must manually uninstall Deployment packages by running the _uninstall_services.bat script.

To uninstall Individual components in isolation, run _uninstall_service.bat in the component folder.



Chapter 4: Install HP ControlPoint Components

This chapter describes how to install ControlPoint components.

l "Overview"

l "Install ControlPoint Database"

l "Install ControlPoint and ControlPoint Engine"

l "Install ControlPoint Client Classifiers"

l "Configure ControlPoint"

OverviewTo install ControlPoint, perform the following steps:

1. Install ControlPoint database.

2. Install ControlPoint and ControlPoint Engine.

3. (Optional) Install repository specific components.

4. (Optional) Install ControlPoint Client Classifiers.

Install ControlPoint DatabaseYou can install ControlPoint databases on SQL Server 2005 or later.

Three ControlPoint databases are installed:

l ControlPoint Database

l Audit Database

l Personalisation Database

To install ControlPoint databases

1. Run ControlPoint Database Installer.exe.

The database installer opens with the Welcome page.


2. Click Next to continue.

The Log Directory dialog box opens.

3. Change the path of the setup log file, if required, and click Next to continue.

The SQL Connection page opens.

4. Enter, or select from the dropdown, the required SQL Server and instance name.

5. Select the required authentication method, either Windows or SQL Server.

If you select SQL Server Authentication, you must also provide a Login and Password.

6. Click Test Connection to verify the server details.

7. Click Next to continue to the Databases & Reports page.

8. Select the databases to install from ControlPoint, Audit and Personalisation.

9. For each database, select Custom if you want to customise the database settings, or Default if you accept the default settings.

10. Select Upload Reports if you want to upload ControlPoint audit reports to the SQL Server.

11. You can specify the installation folder.

12. Click Next to continue.

If you selected Custom for any of the databases, the Configuration page appears allowing Data File Path, Data File Size, Log File Path, Log File Size and Collation to be changed from the default values.

13. Click Next to continue to the Database Connection page.

14. Enter the credentials that will be used for all database connections by ControlPoint software.

15. Click Next to continue to the Installation Confirmation screen.

16. Check the details on the Installation Confirmation screen and click Install to proceed with the installation or Back to change any settings.

17. On the final page review the installation log and click Finish.

To verify the database installation, run SQL Server Management Studio and check that the selected databases have been created on the appropriate SQL server.

Installation GuideChapter 4: Install HP ControlPoint Components


Install ControlPoint and ControlPoint EngineBefore you install ControlPoint and ControlPoint Engine, verify that the ControlPoint prerequisites listed in "Prerequisites" have been met.

To install ControlPoint Console and Engine

1. Click setup.exe in the appropriate folder, either ControlPoint x64 for 64-bit systems or ControlPoint x86 for 32-bit systems.

The Welcome dialog box opens.

2. Read the information, and click Next to continue.

The License Agreement displays.

3. Select I accept the terms in the license agreement, and then click Next.

The Customer Information screen opens.

4. Enter your User Name and Organization, and click Next.

The Setup Type screen appears.

5. Select the setup type that meets your requirements.

n Typical installs ControlPoint and ControlPoint Engine

n Full installs ControlPoint, Engine, Web Services and Classifier Services

n Custom allows individual components to be selected, as required

If you intend to install ControlPoint Client Classifiers, select Full or Custom and select Classifier Services.

6. Click Next.

The Destination Folder dialog opens.

7. Click Change if you want to change the default installation location.

8. Click Next to proceed to the confirmation screen.

9. Review the installation settings you have provided, and then click Install to proceed or Back to change any settings.

10. On the final page, click Finish to exit the installer.

If you check Launch Autonomy ControlPoint Configuration Manager, the Configuration Manager starts.



Install ControlPoint Client ClassifiersControlPoint Client Classifiers are available for file system. A zero footprint client classifier is also available, optionally installed as part of the ControlPoint and ControlPoint Engine deployment.

To install ControlPoint Classifier for File System

1. Run setup.exe in the ControlPoint Classifier for File System folder of your installation hierarchy.

The Welcome dialog box opens.

2. Read the information and click Next to continue.

The License Agreement displays.

3. Select I accept the terms in the license agreement, and then click Next.

The Customer Information screen opens.

4. Enter your User Name and Organization, and click Next.

The Destination Folder dialog opens.

5. Click Change if you want to change the default installation location.

6. Click Next to proceed to the web service URI selection screen.

7. Enter the URI of your ControlPoint Classifier Web Service.

This is typically http://servername/CPWS, where servername is the server on which the ControlPoint Console and Engine were installed.

8. Click Install to proceed, or Back to change any settings.

9. On the final page, click Finish to exit the installer.

Configure ControlPointThe ControlPoint Configuration Manager allows configuration of your ControlPoint system to be performed centrally. All ControlPoint components are configured by the Configuration Manager.

If you left the option checked, the ControlPoint Configuration Manager is launched when you exit the ControlPoint installer. In addition the Configuration Manager can be launched from the Start menu, under the ControlPoint program group.

To configure ControlPoint



1. Enter or select the ControlPoint SQL Server and instance.

2. Choose the connection method.

If you select SQL Server Authentication, you must also provide a Login and Password.

Settings are grouped by Configuration area and you can select them in the left menu. You must complete all mandatory settings before you can deploy the ControlPoint components by clicking the Deploy button.

Previously entered settings are displayed if found.

Database SettingsConnection settings entered during database installation are displayed.

Click Test Connection to verify the values entered.

Note: If you are using SQL Server Authentication, you can provide alternate login and password details. The login must exist in SQL Server.

IIS SettingsSelect the web site to deploy the ControlPoint web applications to. The deployed web applications can subsequently be retracted by selecting Not Deployed from the drop down menu.

Specify the User Account settings to be used the IIS Application Pool that is used by each of the ControlPoint web applications.

Engine SettingsTo update the account used as the identity for the ControlPoint Engine service, check Update Engine Service Account and enter the appropriate information.

Enter the number of threads to be used by the Engine (the recommended number of threads is the number of processors in the ControlPoint Engine server).

Policy execution requires a temporary location, accessible by all ControlPoint connectors. The Configuration Manager can create and use a default network share named ControlPointTempLocation on the local server or you can chose an alternate network share that you have created yourself.

WorkflowSelect the type of workflow to use when policies initiate workflows. You can select HP Process Automation or Windows Workflow Foundation.



Data Analysis SettingsSelect whether the current system should be the active Data Analysis Controller.

The SQL server name is the Data Analysis Controller Host; you can specify the Data Analysis Controller Port.

In the IDOL Statistics Server Settings section, specify the statistics server Host, Port, and Index Port.

IDOL SettingsEnter the name of the IDOL Server host and the Distributed Connector host and their port numbers. Also enter the index port number for IDOL Server.

ControlPoint policy execution requires configuration files to supply information for insert operations to target locations. These files can either be installed in a local folder or in a specific network share. A network share should be used if you intend to install multiple ControlPoint Engines so that the configuration files can be accessed by all Engines.

Select the Date Format that matches the date format used by your ControlPoint IDOL Server. Default should be chosen unless you are connecting to an Enterprise IDOL server that is configured to use a date format other than yyyyMMddHHmmss.

Security SettingsChoose whether to enable HP ControlPoint security. If enabled, specify the system administrator account, and the Active Directory server and distinguished name.



HP ControlPoint 4.3 Installation Guide (English)h30359. Governance...Notice This documentation is a...

Documents

Transcript of HP ControlPoint 4.3 Installation Guide (English)h30359. Governance...Notice This documentation is a...