HP TRIM Installation and Setup Guide · 2017-12-04 · Windows Vista, Windows 7 and Windows Server 2008 ... Securing the print drivers ... This guide assumes you are qualified IT

HP TRIM Software Version: 7.12

Installation and Setup Guide

Document Release Date: June 2012

Software Release Date: June 2012

Legal Notices

Warranty

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notices

© Copyright 2008-2012 Hewlett-Packard Development Company, L.P.

Trademark Notices

Microsoft®, Windows®, Windows® XP and Windows Vista® are U.S. registered trademarks of Microsoft Corporation. Oracle is a registered trademark of Oracle and/or its affiliates.

Documentation Updates

The title page of this document contains the following identifying information: • Software Version number, which indicates the software version. • Document Release Date, which changes each time the document is updated. • Software Release Date, which indicates the release date of this version of the software. To check for recent updates or to verify that you are using the most recent edition of a document, go to: http://h20230.www2.hp.com/selfsolve/manuals This site requires that you register for an HP Passport and sign-in. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html Or click the New users - please register link on the HP Passport login page. You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.

http://h20230.www2.hp.com/selfsolve/manuals

http://h20229.www2.hp.com/passport-registration.html

Support

Visit the HP Software Support web site at: www.hp.com/go/hpsoftwaresupport This Web site provides contact information and details about the products, services, and support that HP Software offers. HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by using the support web site to: • Search for knowledge documents of interest • Submit and track support cases and enhancement requests • Download software patches • Manage support contracts • Look up HP support contacts • Review information about available services • Enter into discussions with other software customers • Research and register for software training Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html To find more information about access levels, go to: http://h20230.www2.hp.com/new_access_levels.jsp

http://h20229.www2.hp.com/passport-registration.html

http://h20230.www2.hp.com/new_access_levels.jsp

Contents

1 Installation and Setup Guide ...................................................................... 9

Introduction ........................................................................................................................................................ 9

Audience .............................................................................................................................................................. 9

Chapters Summary ............................................................................................................................................ 9

Related Documents ............................................................................................................................................. 9

2 About HP TRIM software .......................................................................... 10

HP TRIM architecture ...................................................................................................................................... 10

Workgroup Server ...................................................................................................................................... 11 HP TRIM Web Client ................................................................................................................................. 11 Dataset ........................................................................................................................................................ 12 Electronic document store ......................................................................................................................... 12 Document content index ............................................................................................................................ 12 HP TRIM client .......................................................................................................................................... 12 HP TRIM Desktop ...................................................................................................................................... 12 HP TRIM thin client .................................................................................................................................. 12 HP TRIMWatcher ...................................................................................................................................... 13

Citrix launched Offline Records ......................................................................................................... 13 Relational Database Management System (RDBMS) requirements ............................................................ 14

RDBMS resource allocation and management ........................................................................................ 14 Ongoing dataset storage ...................................................................................................................... 14

3 HP TRIM Installation ................................................................................ 15

Installation media ............................................................................................................................................ 15

HP TRIM environment ..................................................................................................................................... 16

Prerequisites ............................................................................................................................................... 16 Installation overview ................................................................................................................................. 17 64-bit installation ....................................................................................................................................... 18 Installing HP TRIM ................................................................................................................................... 19 Windows Vista, Windows 7 and Windows Server 2008 ........................................................................... 19 All other operating systems ....................................................................................................................... 19

4 Installation types ..................................................................................... 20

Network installation ......................................................................................................................................... 20

Network installation prerequisites ........................................................................................................... 20 Network installation steps ........................................................................................................................ 20 Administrative installation ....................................................................................................................... 21

Overview .............................................................................................................................................. 21 Administrative installation steps ....................................................................................................... 21

Group Policy installation ........................................................................................................................... 23 Batch file installation ................................................................................................................................ 24

Batch file parameters .......................................................................................................................... 25 Thin client ......................................................................................................................................................... 29

Thin client installation prerequisites ....................................................................................................... 29 Installing HP TRIM thin client ................................................................................................................. 29 Repairing a thin client installation ........................................................................................................... 30 Upgrading a thin client installation ......................................................................................................... 31 Removing a thin client installation........................................................................................................... 31 Utility TRIMThinClientSetup.exe ............................................................................................................ 31

Demonstration installation .............................................................................................................................. 32

Demonstration installation prerequisites ................................................................................................ 32 Installing HP TRIM for demonstrations .................................................................................................. 32 Running HP TRIM for demonstrations .................................................................................................... 34

Maintenance installation ................................................................................................................................. 35

Repair .......................................................................................................................................................... 35 Repairing an installation .................................................................................................................... 35

Remove ........................................................................................................................................................ 36 Removing an installation .................................................................................................................... 36

Modify ......................................................................................................................................................... 37 Modifying an installation .................................................................................................................... 37

Installation dialog boxes .................................................................................................................................. 38

Missing Prerequisites dialog box .............................................................................................................. 48 Installation using .msi file rules and behavior ............................................................................................... 49

Automatic deployment tool .............................................................................................................................. 50

AutoDeploy changes to the current user .................................................................................................. 51 Current user configuration ........................................................................................................................ 51 Deactivating HP TRIMAutoDeploy .......................................................................................................... 52

Applying to Group Policy .................................................................................................................... 52

5 Upgrading HP TRIM ................................................................................ 53

Version support ................................................................................................................................................. 53

Customized client toolbars and menus ........................................................................................................... 53

Upgrading from HP TRIM 6.2 ......................................................................................................................... 54

About upgrading from TRIM 6.2 ............................................................................................................... 54 Upgrade steps from HP TRIM 6.2 to 7.x .................................................................................................. 54

Upgrading from HP TRIM 7 ............................................................................................................................ 57

Upgrade steps from HP TRIM 7.x ............................................................................................................. 57 Upgrading client computers from version 7 .................................................................................................... 58

Upgrading HP TRIM peripheral applications from version 7 ................................................................. 58 Upgrading WebDrawer ISAPI from version 7 ................................................................................... 58

Mixed environments ......................................................................................................................................... 59

Upgrade steps for mixed environments .......................................................................................................... 59

Upgrading Offline Records ............................................................................................................................... 60

6 Removing HP TRIM ................................................................................. 61

7 Server and Client Configuration Options ................................................... 62

Client folder locations ....................................................................................................................................... 62

Client application data paths .................................................................................................................... 62 Windows application data path .......................................................................................................... 62 Local application data path ................................................................................................................ 62 My documents data path or personal folders ..................................................................................... 63

Server folder locations ...................................................................................................................................... 63

Server application data ....................................................................................................................... 63 Server local data .................................................................................................................................. 63

Local document store caching .......................................................................................................................... 63

Log file registry keys ........................................................................................................................................ 64

Log file location .......................................................................................................................................... 64 Novell authentication ....................................................................................................................................... 65

Registry settings per installation computer ............................................................................................. 65 Network users group and the TRIMServices account .................................................................................... 66

8 Backing up and Restoring your Data ......................................................... 67

Reasons for backing up ..................................................................................................................................... 67

Backup strategy ................................................................................................................................................ 67

Dataset components ................................................................................................................................... 68 Backup techniques ..................................................................................................................................... 69 Recovery techniques ................................................................................................................................... 69

A Steps to setting up a working system ......................................................... 70

B Troubleshooting ...................................................................................... 72

Troubleshooting the Workgroup Server .......................................................................................................... 72

Workgroup Server does not start .............................................................................................................. 72 Crashdump files ......................................................................................................................................... 72

C Rendering module configuration ............................................................... 73

Security ............................................................................................................................................................. 73

Overview ..................................................................................................................................................... 73 Securing the print drivers ......................................................................................................................... 73 Securing the service and render monitor ................................................................................................. 74 Remote access ............................................................................................................................................. 74

Printing preferences ......................................................................................................................................... 75

Overview ..................................................................................................................................................... 75 Changing the settings ................................................................................................................................ 75

Using multiple servers ..................................................................................................................................... 75

Setup example ............................................................................................................................................ 75 All records of Record Type 3 and finalized ......................................................................................... 75 All records of Record Type 15 and registered 5 or more days ago .................................................... 75

Queuing ....................................................................................................................................................... 76 Processing ................................................................................................................................................... 76

Print verbs ......................................................................................................................................................... 76

Overview ..................................................................................................................................................... 76 Changing a print verb ................................................................................................................................ 76

Troubleshooting ................................................................................................................................................ 77

Rendering module output does not appear ............................................................................................... 77

D Database and dataset maintenance tasks .................................................. 78

Overview ............................................................................................................................................................ 78

Steps ............................................................................................................................................................ 78


Page 9 of 80

1 Installation and Setup Guide

Introduction

This HP TRIM software installation and setup guide describes HP TRIM software and the process of installing, upgrading, removing, configuring and backing up HP TRIM and its core components and data. Even if you are familiar with HP TRIM from earlier versions, it is recommended you read this guide in its entirety before you set out to deploy HP TRIM.

Audience

This guide assumes you are qualified IT support personnel with extensive knowledge of Microsoft Windows and the client server architecture and system administrator with a sound understanding of Windows Services and Group Policy.

Chapters Summary

Chapter 2 describes HP TRIM software, its architecture and components. Chapter 3 gives a broad overview of the installation process and its requirements. Chapter 4 contains step-by-step instructions for the different installation types. Chapter 5 contains high level configuration options. Chapter 6 gives an overview of backing up your HP TRIM application and data. Appendix A lists the steps you need to take to create a working HP TRIM system. Appendix B contains troubleshooting tips.

Related Documents

• HP TRIM Specifications and Requirements TRIM7.12_Spec.pdf for system specifications and requirements

• HP TRIM Enterprise Studio Help TRIMEnterpriseStudio.chm for post-installation dataset and server configuration and maintenance

• HP TRIM Help file TRIM.chm for post-installation system setup


Page 10 of 80

2 About HP TRIM software

HP TRIM architecture

HP TRIM is an n-tiered application with a number of server-side components that are scalable and extensible. An n-tiered or multi-tier application is an application that uses more than two tiers or layers between user and data. Advantages of a multi-tier architecture:

• Reduction of network traffic

• Reduction of the effects caused by network latency

• Reduction of the load on the database server

• Spreading of the processing workload (load balancing) The HP TRIM architecture has a server component that you can run as a service. Communication between the server and client is using RCF (Remote Call Framework) based on Open SSL. An organization with multiple branches can run a wide area network (WAN) to allow functionality for all branches while centralizing management functions such as backup and disaster recovery. The typical deployment model is to put a Workgroup Server in each branch and the database and store in a central location. The WAN then acts only as the conduit to update the metadata about documents. The Workgroup Server’s cache, other defined items and the authoritative document are stored centrally. HP TRIM 7 contains the option to use a Workgroup Server on the database LAN for querying the dataset, whereas updates to the database would still use the Workgroup Server on the WAN. Especially for organizations using Oracle RDBMS, this can lead to significantly better performance for searches.


Page 11 of 80

Workgroup Server

The Workgroup Server is the key component in the HP TRIM architecture for:

• Supporting client connectivity

• Providing connections to — primary database — content index — document stores

HP TRIM supports database and object replication and Workgroup Servers enable local users to connect with locally replicated databases and document stores to reduce the impact of the system on network bandwidth. Clients connect to a named primary Workgroup Server; you can also configure a secondary Workgroup Server for event that the connection to the primary server fails. There is no limit to the number of Workgroup Servers within the system; you can use additional Workgroup Servers for load balancing and performance tuning to improve the speed of access to the database for remote users. The Workgroup Server performs the following functions:

• Managing connections to the database

• Local caching of some of the control tables

• Local caching of documents, e-mail and other objects from the electronic document store

• Event processing Events are actions that can be processed in bulk at specific times or continuously. HP TRIM events include: — Document content indexing — Word indexing — Schedule event triggers — Mail notification — Audit log — Billing log — User defined events

HP TRIM Web Client

HP TRIM Web Client is a zero footprint, platform independent Web application.


Page 12 of 80

Dataset

A HP TRIM dataset represents a full document and records management system with all the data elements, record objects and repositories. The dataset consists of a database component on a Relational Database Management System (RDBMS) and a storage component on any storage device on the network. Each dataset exists independently of others. There is no communication or connection between datasets. You can use the client software to switch between different datasets while server components manage multiple datasets simultaneously. The dataset contains record metadata and pointers to the electronic documents in the electronic document store HP TRIM datasets are stored in a back-end database. This database contains all the information that is unique to the dataset. HP TRIM works with SQL Server, SQL Server Express for installation for demonstrations, and Oracle.

Electronic document store

The electronic document store is the location where the electronic files are stored. The document store can be in any location to which you can map a UNC path.

Document content index

HP TRIM can index the content of electronic documents for searching. This document content index can be in any location to which you can map a UNC path.

HP TRIM client

The HP TRIM client contains all the functionality to manage the HP TRIM application including the client interfaces for end users, records managers and system administrators.

HP TRIM Desktop

TRIM Desktop enables users below administrator level to access the HP TRIM search and edit functions without having to use the full HP TRIM client.

HP TRIM thin client

The HP TRIM thin client enables you to use MS Office functions like Open and Save and HP TRIM functions like checking in and out from MS Office applications that have been integrated with HP TRIM without having to use the HP TRIM client interface. It is designed for users who need to use only HP TRIM integrations and none of the more sophisticated features of the HP TRIM rich client.


Page 13 of 80

HP TRIMWatcher

TRIMWatcher is a process activated by a HP TRIM application and designed to monitor when files are created, modified or deleted on a client computer. It is triggered by the HP TRIM Software Development Kit (SDK) and is resident until the client logs off the computer. Its main purpose is to provide dynamic refresh capabilities to HP TRIM compliant applications using the SDK. TRIMWatcher has no data recording functionality. Once started, TRIMWatcher will continue to run until the current Windows session is closed.

Citrix launched Offline Records

HP TRIM uses a registry key to stop TRIMWatcher when a user closes Offline Records. This stops Citrix from keeping unused sessions open: HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP TRIM \TopDrawer\AllowUnload. The value is 18000 by default, which represents milliseconds of inactivity before trimwatcher.exe shuts down. 18000 milliseconds are six seconds. Change this registry key to change the time trimwatcher.exe waits before it shuts down.


Page 14 of 80

Relational Database Management System (RDBMS) requirements

See the HP TRIM Specifications and Limitations document TRIM7.12_Spec.pdf on the installation CD or in your installation folder for detailed RDBMS requirements.

RDBMS resource allocation and management

Ongoing dataset storage

As a rule of thumb, the space necessary to store the HP TRIM metadata should be equal to the number of records times 5000, expressed in bytes. For example, if your site anticipates storing 100,000 items, then you will need to allocate 500MB. However, you should allow room for growth. Additionally, you need to allocate space to store electronic documents - for example, word processing files, e-mail messages, spreadsheets, etc. - in your document stores and for the document content index. The space required to store electronic documents in your document stores depends on the amount of electronic document data in the dataset. For sizing requirements for your document content index, see Document Content Index in HP TRIM Enterprise Studio Help.

Oracle

You should identify at least one tablespace with the required storage or create a new tablespace for the express purpose of storing HP TRIM data. You should make this tablespace the default tablespace for the account you created in RDBMS Resource Allocation and Management.

Microsoft SQL Server

Identify at least one filegroup with the required storage - usually the default PRIMARY filegroup - or create a new filegroup for the HP TRIM data. While we recommend you use at least two logical storage areas - one for data and one for indexes - it is not required and you can disregard this recommendation if you choose to implement advanced storage features such as RAID.


Page 15 of 80

3 HP TRIM Installation

Installation media

You will find the installation files on the installation media. Media file structure:

• HP TRIM — Install

• HP TRIM installation .msi packages

• Supplementary files

Note

• All applications should be closed on the computer before installing HP TRIM

software • When an application that conflicts with the installation is running - for

example, Microsoft Word - the installation process will either attempt to close it or display a warning message advising you to close the application.

• If you are using the silent installation method, the application cannot be closed and the message to close this program will not appear. This should not be a problem, as silent installations generally run on startup and no programs will be running.


Page 16 of 80

HP TRIM environment

• HP TRIM is a key desktop application. By design, HP TRIM should be installed on each computer and per-machine

• HP TRIM's functionality can only be fully realized when it is integrated with other key desktop applications such as word processors, mail systems, spreadsheet applications etc.

• All HP TRIM documentation assumes that you followed the recommended method of deployment

Note

Contact HP Software or your national distributor if you have difficulty installing HP TRIM or for further explanation of any features or functions that may not be fully detailed in either the HP TRIM Installation and Setup Guide TRIM7.12_Install.pdf, HP TRIM Enterprise Studio Help or HP TRIM Help.

Prerequisites

For full specifications and requirements, see TRIM7.12_Spec.pdf. To install the following HP TRIM features, you must have elevated user rights:

• WebDrawer ISAPI

• Web Service

• Web Client

• Web Content Management (WCM)


Page 17 of 80

Installation overview

For a demonstration database installation, see Demonstration installation.

1 HP TRIM Workgroup Servers

a Determine the layout of your network architecture including the computers that will host the server components of HP TRIM

Note

All required components of HP TRIM are installed on each computer for component recognition. During installation, the administrator determines the components to install on each target computer - for example, the Workgroup Server component only on the Workgroup Servers and the client components only on client computers. It depends on the network environment which components to install on each computer.

b Ensure that HP TRIM supports the server operating system and that it has all the necessary components installed. See TRIM7.12_Spec.pdf.

c Ensure you have the correct RDBMS client software. See RDBMS requirements.

d Determine the kind of electronic store to set up:

– Windows File System

– FTP – not recommended

– Integrated Archive Platform In the HP TRIM Help file, see Creating Document Stores.

2 Network settings

a Create the new domain user HP TRIM uses to create the database and run the Workgroup Servers. Typically, this is TRIMServices. See Network users group and the TRIMServices account.

b Add the user to the Workgroup Servers

Note

This account must be a member of the local administrators group and should also have Log on as a Service policy rights.

c Create and add a user with full access permissions to the administration group for your RDBMS

d Create a domain group - the HP TRIM users group - and add all the network users that require access to HP TRIM, e.g. TRIMUsers


Page 18 of 80

e Install the HP TRIM components on the appropriate servers. Find instructions for installing and enabling the components of HP TRIM in Network installation.

f Using HP TRIM Enterprise Studio, create the HP TRIM dataset. See HP TRIM Enterprise Studio Help – Creating datasets.

g Add the account to your HP TRIM dataset as Location. User type Administrator with Top security and All Caveats profile is recommended. In HP TRIM Help, see Creating Locations.

h Register the HP TRIM Server components as Windows Services. See Network Users Group and the TRIMService Account.

Note

For ease of administration, maintenance and secure access, it is recommended you install the HP TRIM components as Windows Services

3 HP TRIM client

a Ensure the client computer has a supported operating system and all the necessary components installed. See TRIM7.12_Spec.pdf.

b Install HP TRIM on the client computer

c Create the user as a HP TRIM Location in the dataset. In HP TRIM Help, see Creating Locations.

64-bit installation

Install HP TRIM in 64-bit environments using the same instructions as for 32-bit environments. On a 64-bit operating system, 64-bit HP TRIM installs to C:\Program Files. On a 64-bit operating system, 32-bit HP TRIM installs to C:\Program Files (x86) On a 64-bit operating system, 64 bit HP TRIM uses the same part of the registry as an installation in a 32-bit environment, e.g. HKEY_LOCAL_MACHINE\Software\Hewlett Packard\... On a 64-bit operating system, 32-bit HP TRIM uses the registry folders under HKEY_LOCAL_MACHINE\Software\WOW6432node\Hewlett Packard\...


Page 19 of 80

Installing HP TRIM

You can run the installation manually or automated using Group Policy or batch files. Both full and Service Pack .msi files enable you to install HP TRIM:

• over a network – see Network installation

• locally – see Installation dialog boxes

• for demonstration purposes – see Demonstration installation

Windows Vista, Windows 7 and Windows Server 2008

Follow these steps if you are installing HP TRIM on the above operating systems and are not using Group Policy:

1 Click Start, point to All Programs, and then click Accessories.

2 Right-click Command Prompt and then click Run as administrator.

3 Type msiexec.exe /i “<file path>\HPTRIM_xNN.msi” with the correct .msi file name and press Enter

4 Continue the installation from Installation dialog boxes

All other operating systems

1 Install HP TRIM on all required computers using one of these methods:

— Graphical installation - the .msi file prompts you with a graphical user interface for HP TRIM installation options

— Administrative installation – you create an installation package and distribute it to the target computers


Page 20 of 80

4 Installation types

Network installation

This is the most common installation for most organizations.

Network installation prerequisites

• A system administrator with a sound understanding of Windows Services

• You must have administrator or elevated access rights for the target computers

Note

• The domain account running the HP TRIM Server requires the Log on as

Service access permission if it is configured as Windows Service • HP TRIM software is an essential desktop application and therefore, you

should install it on a per-machine basis using Group Policy.

Network installation steps

1 Follow the steps in Administrative installation

2 Follow the steps in Group Policy -- or – Follow the steps in Batch file installation

3 After completing the installation, continue setup by working through Appendix A Steps to setting up a working system


Page 21 of 80

Administrative installation

Overview

1 Perform an administrative installation and set the desired properties using the administrative installation dialog boxes

2 Using Group Policy, use the .msi file that was saved to the administrative install point to install HP TRIM on the target computers. If you are not using Group Policy, use a batch file to run the .msi file which was copied to the administrative installation point. This file will use the properties you selected during the administrative installation.

Administrative installation steps

1 Install VBRuntimes_x86.msi using your own rollout strategy. This step is not necessary for 64-bit installations.

2 Install VS2008Runtimes_xNN.msi using your own rollout strategy

3 Use the Windows Run function and type msiexec.exe /a followed by the path to the .msi installation file For example, msiexec.exe /a "C:\Users\<username>\Desktop\HPTRIM_x86.msi" <targetdirectory>

The target directory should follow the format \\server\path. The Administrative Installation dialog appears:

— Network installation point - type or browse for the folder to save the administrative installation files to


Page 22 of 80

Note

It depends on the options you select in each screen which dialog boxes appear. Follow the on-screen instructions as the steps here are just an example of an administrative installation process.

4 Click Next.

The Select Features dialog appears. By default, all features are selected. See Select Features for details.

5 Click Next. The HP TRIM Default Connection Settings dialog appears.

6 Set up your default Workgroup Server connection and click Next.

The HP TRIM Client Configuration dialog appears.

7 Choose the installation options for the HP TRIM client and click Next.

The HP TRIM Server Configuration dialog appears.

8 Enter the server configuration details, if needed, and click Next.

The Existing Web Sites on the Server dialog box appears if you are installing WebDrawer ISAPI:

9 Fill in the fields:

— Web Site Description

— Web Site Port Number

— Web Site IP

— Web Site Header Information

10 Click Next. The License Settings dialog box appears.

11 Enter your HP TRIM license details.

12 Click Next.


Page 23 of 80

The Administrative Installation Verify Ready dialog appears:

13 Click Next to create the installation package.

Once completed, the confirmation dialog appears.

14 Click Finish to complete the administrative installation.

Group Policy installation

1 You must have carried out the steps described in Administrative installation before installing HP TRIM through Group Policy.

2 Use Group Policy to install the configured .msi package on the target computers:

a HP TRIM Workgroup Servers

b HP TRIM clients

Note

One advantage of a Group Policy rollout is that the installation runs with elevated access rights on the target computer and all repairs or modifications to the installation on the target computer run with elevated access rights.


Page 24 of 80

Batch file installation

Note

Batch file installation is an option to install HP TRIM software instead of using Group Policy. You do not need to use batch file installation if you are using Group Policy installation as described in Group Policy installation

1 You must have carried out the steps described in Administrative installation before installing HP TRIM through a batch file.

2 Create a batch file according to the installation requirements for the client computers. The HP TRIM .msi installation does not support a parameter file; therefore, you must set each property that you want to install on the command line.

3 Run the batch file on the target computer. HP TRIM installs with the features you selected.

Note

Batch file installations of HP TRIM cannot ensure that the target computer has Group Policy set so that installations run using elevated access rights. If the installation does not use elevated access rights at all or only for the installation and not for any post-installation tasks, then these tasks may not complete correctly, for example, self-repair. If elevated access rights are not available for the target computer, it is recommended that either:

• All users logging on to that computer have sufficient access permissions to perform installation tasks, including writing and deleting files to the Program Files and System32 folders and writing to the registry. -- or --

• You make the installation functions in the Windows Control Panel → Programs and Features function unavailable. This will prevent users from performing repairs or modifications to the installation.


Page 25 of 80

Batch file parameters

When you are using a batch file to install HP TRIM, all installation parameters must be in a single line.

Example

The sample batch file shows all the variables. You can copy it to have a working batch file - although you may have to change paths, network information etc:

Rem ADDLOCAL lists the features you want installed. The example below lists all available features Rem These properties only need to be included if you are installing WebdrawerISAPI and only the first two are mandatory:- Rem WEBSITE="Default Web Site" Rem WEBSITE_PORT=80 Rem WEBSITE_IP Rem WEBSITE_HEADER Rem These properties are required to enter licence information. If NUMBER_OR_DATE="Number" then use the LICENSE_NUMBER property but if NUMBER_OR_DATE="Date" then use the EXPIRY_DATE property. Rem LICENSE_NAME Rem EXPIRY_DATE Rem LICENSE_NUMBER Rem NUMBER_OR_DATE Needs a value of "Number" or "Date" Rem PRODUCT_KEY Rem The licence details are an example and will not allow HP TRIM to run. Rem If using Novell then use the property NOVTREE to set the Novell tree name. "C:\Documents and Settings\username\Desktop\HPTRIM_x86.msi"/q /l*vx C:\Install.txt INSTALLDIR="C:\Program Files\Hewlett-Packard\HP TRIM\"ADDLOCAL=HPTRIM,Client,TRIMSCAN,Lotus,StandardData,Server,TRIMWORKGROUP,TRIMENTERPRISESTUDIO,DEMODBSQL,TRIMRENDER,TRIMPORT,WebdrawerISAPI SERVER_DATA_FOLDER="C:\HPTRIM02\ServerData" SERVER_LOCAL_DATA_FOLDER="C:\HPTRIM02\ServerLocalData" EXCEL_ON="1" PROJECT_ON="1" POWERPOINT_ON="1" WORD_ON="1" WGS1="PrimaryWorkgroupName" WGS2="SecondaryWorkgroupName" WINDOMAIN="1" DOMAINNAME="mynetwork" SERVICEUSER="myusername" SERVICEPASS="mypassword" WEBSITE="Default Web Site" WEBSITE_PORT=80 DEFAULTDBNAME="DemoDB" DEFAULTDB="45" PORTNO="1137" LICENSE_NAME="Licence" NUMBER_OR_DATE="Date" EXPIRY_DATE="2010/12/10" PRODUCT_KEY="ABCD-1234-EFGH-5678-IJKL-9012-MNOP-3456-QRST-7890-UVWX-1234-YZAB-5678" LANG="EN" ALLUSERS="1" TRIM_DSK="1" EMAIL="TIO" ODMA="TRIM" TRIMREF="DSK" ODMALOCAL="1"

The parameters and values:

• Application parameters

• Client parameters

• Integration parameters


Page 26 of 80

Application parameters

Use ADDLOCAL to install HP TRIM features, separated by commas:

• HPTRIM – HP TRIM

• Client – client features

• TRIMSCAN – HP TRIMScan

• Lotus – HP TRIM Lotus Notes integration

• StandardData – standard HP TRIM sample data

• Server – server features

• TRIMWORKGROUP – HP TRIM Workgroup Server

• TRIMENTERPRISESTUDIO – HP TRIM Enterprise Studio

• DEMODBSQL – demonstration database

• TRIMRENDER – HP TRIM Rendering module

• TRIMPORT – HP TRIMPort

• WebdrawerISAPI – WebDrawer ISAPI Extension

Client parameters

• ALLUSERS — 1 – per machine installation

• SETUPTYPE – installation type — Demonstration – demonstration database only — Custom – all other installations

• WGS1 – primary Workgroup Server name

• WGS2 - secondary Workgroup Server name

• PORTNO – Workgroup Server port number

• WINDOMAIN – the type of network HP TRIM will run on — 0 – Novell network — 1 – Windows domain - default

• DOMAINNAME – domain name

• NOVTREE – the name of the Novell tree to use when resolving the HP TRIM login name

• SERVICEUSER – user name — <domainname>\<username>

• SERVICEPASS – user password

• INSTALLDIR – installation folder with path — C:\Program Files\Hewlett-Packard\HP TRIM is default

• SERVER_DATA_FOLDER – Workgroup Server data path — By default, C:\HPTRIM\ServerData\

• SERVER_LOCAL_DATA_FOLDER - Workgroup Server local data path


Page 27 of 80

— By default, C:\HPTRIM\ServerLocalData\

• LANG – client language — EN – English (International) is default — US – English (US) — FR – French — NL – Dutch — DE – German — IT – Italian — ES – Spanish — BR – Portuguese (Brazil)

• DEFAULTDBNAME – default demonstration database name

• DEFAULTDB – default demonstration database identifier

• TRIMREF – application to use for HP TRIM reference files (*.tr5) — TRIM – HP TRIM — DSK – HP TRIM Desktop

Integration parameters

• EMAIL – e-mail integration — None – no e-mail integration — TIO – HP TRIM in Outlook — GW – HP TRIM in GroupWise

• ODMA - ODMA integration — None — TRIM – HP TRIM — DSK – HP TRIM Desktop

• ODMALOCAL – local ODMA behavior — 0 – no access to Windows File – Open and Save dialogs — 1 – enables access to Windows File – Open and Save dialogs

• EXCEL_ON

— 1 – integration with Microsoft Excel.

Leave this property out of the command line for no integration.

• PROJECT_ON

— 1 – integration with Microsoft Project. Leave this property out of the command line for no integration.

• POWERPOINT_ON

— 1 – integration with Microsoft PowerPoint. Leave this property out of the command line for no integration.


Page 28 of 80

• WORD_ON

— 1 – integration with Microsoft Word. Leave this property out of the command line for no integration.


Page 29 of 80

Thin client

Thin client installation prerequisites

The prerequisites are the same as those of the rich client using a network installation. See Network installation.

Installing HP TRIM thin client

To install the HP TRIM thin client, you must use a batch file installation as described in Batch file installation by using HPTRIM_x86.msi for a 32-bit installation or HPTRIM_x64.msi for a 64-bit installation. The batch file must contain certain parameters that are exclusive to the thin client installation. The commands must be on a single line or else you should use line continuation characters (^). It is recommended you use the example batch file below and edit it as required: Rem Command Line for Thin Client installation "C:\Users\Username\Desktop\HPTRIM_x86.msi" /q /l*vx C:\temp\InstallBatch.txt

INSTALLDIR="C:\Program Files\Hewlett-Packard\HPTRIM\" TRIMTHINCLIENT="1" OFFSHORT_ON="1" EXCEL_ON="1" PROJECT_ON="1" POWERPOINT_ON="1" WORD_ON="1" WGS1="SLWin7En" WINDOMAIN="1" DEFAULTDBNAME="DemoDB" DEFAULTDB="45" PORTNO="1137" EMAIL="TIO"

You may have to edit:

• Path and name of the .msi file

• Path and name of the log file. The sequence /l*vx C:\InstallBatch.txt creates the log file InstallBatch.txt in its path.

• Other properties as required The batch file properties are the same as for the standard batch file installation except these additional properties to integrate with Office 2007 with hotfix or later. For installations under other versions of Microsoft Office, see additionally Utility TRIMThinClientSetup.exe.

Note

To make these parameters work under Office 2007, you should first apply the Microsoft Office 2007 hotfix described in http://support.microsoft.com/kb/976477/.

http://support.microsoft.com/kb/976477/


Page 30 of 80

• TRIMTHINCLIENT - activates the thin client installation

• EXCEL_ON – registers the HP TRIM thin client add-in with MS Excel

• PROJECT_ON – registers the HP TRIM thin client add-in with MS Project

• POWERPOINT_ON - registers the HP TRIM thin client add-in with MS PowerPoint

• WORD_ON – registers the HP TRIM thin client add-in with MS Word

• OFFSHORT_ON – installs the shortcut TRIM – Office Integration in the Start menu with Office 2003 and Office 2007 without hotfixes

Another relevant property is EMAIL, which also exists for the standard batch file installation and uses these parameters:

• EMAIL – e-mail integration — TIO – HP TRIM in Outlook

When there is no need for MS Outlook integration installation, just leave the property out of the batch file.

Note

With a thin client batch file installation, you should not use the property ADDLOCAL.

1 Follow the steps under Administrative installation

2 Follow the steps under Batch file installation by using the batch file described in Installing HP TRIM thin client. HP TRIM thin client installs without user interaction.

3 Verify the installation by checking that HP TRIM is installed in the folder you specified in the batch file.

Repairing a thin client installation

1 To repair a HP TRIM thin client installation, use a command prompt with elevated user rights and enter a line similar to this example with parameters appropriate to your environment: "C:\Users\Username\Desktop\HPTRIM_x86.msi" /q /l*vx C:\temp\RepairBatch.txt TRIMTHINCLIENT="1" MaintenanceMode="Repair"

HP TRIM attempts to restore HP TRIM thin client to its default settings.


Page 31 of 80

Upgrading a thin client installation

You can upgrade any HP TRIM 7 thin client installation to a HP TRIM rich client installation. However, you cannot modify a HP TRIM rich client installation to a thin client installation.

1 To upgrade a HP TRIM thin client installation, use a command prompt with elevated user rights and enter a line similar to this example with parameters appropriate to your environment: "C:\Users\Username\Desktop\HPTRIM_x86.msi"

The Application Maintenance dialog appears.

2 Follow the steps under Modify to select features and complete the upgrade

Removing a thin client installation

1 To remove a HP TRIM thin client installation, use a command prompt with elevated user rights and enter a line similar to this example with parameters appropriate to your environment: "C:\Users\Username\Desktop\HPTRIM_x86.msi"

The Application Maintenance dialog appears.

2 Follow the steps under Remove to remove the installation

Utility TRIMThinClientSetup.exe

This stand-alone application is required for certain environments with versions of Microsoft Office before Office 2007 for integration with HP TRIM to work correctly. It ensures that the Office add-ins are registered as expected. It also enables you to change the thin client settings after installation in these environments, or to repair the settings when the thin client installation did not work correctly. It is in the HP TRIM installation folder. Thin client installations under MS Office 2007 with hotfix or later should work without this utility.

1 When you run it, a dialog box appears with the options: Integrate HP TRIM with the following Microsoft Office applications:

Microsoft Word

Microsoft Excel

Microsoft PowerPoint

Microsoft Project

Microsoft Outlook

2 Select the applications to integrate the HP TRIM thin client with and click Test to test the integration

3 Click OK when the test is successful


Page 32 of 80

Demonstration installation

For testing, evaluation, demonstration and training purposes, it is recommended to install the HP TRIM demonstration database on a single computer.

Demonstration installation prerequisites

• You must have administrator or elevated access rights for the target computer to install HP TRIM

• The target computer must have Microsoft SQL Server 2005 or 2008 or one of their Express Editions installed

• The user must be a member of the computer group SQLServer2005MSSQLUser$<computer name>$SQLEXPRESS or their equivalents

Installing HP TRIM for demonstrations

1 Install VBRuntimes_x86.msi.

This step is not necessary for 64-bit installations.

2 Install VS2008runtimes_xNN.msi

3 Run HPTRIM_xNN.msi from the command line with elevated user rights. The Welcome dialog appears.

4 Click Next. The License Agreement dialog appears.

5 Select I accept the license agreement and click Next. The Destination Folder dialog appears. — Destination Folder – click Browse to change the folder to install HP TRIM in.

The default is C:\Program Files\Hewlett-Packard\HP TRIM.

6 Click Next. The Select Features dialog appears.

7 Select the following features to install HP TRIM for demonstrations either: — To run on a single computer:

– Client

– Workgroup Server

– Enterprise Studio

– Demonstration Database

-- OR --


Page 33 of 80

— To run server and client on separate computers:

a On computer 1, install:

– Client

b On computer 2, install:

– Workgroup Server

– Enterprise Studio

– Demonstration Database The HP TRIM Default Connection Settings dialog appears.

8 Enter your settings and click Next. The HP TRIM Client Configuration dialog box appears.

9 Enter your settings and click Next. The HP TRIM Server Configuration dialog appears.

10 Enter your network settings and click Next. The License Settings dialog appears.

11 Enter your license details and click Next. The Ready to Install the Application dialog appears.

12 Click Next to start the installation process. When the installation is finished, the confirmation dialog appears.

13 Click Finish to complete the installation. HP TRIM is now installed for demonstration purposes with Workgroup Server and HP TRIM Enterprise Studio.

Note

• You can install the HP TRIM Workgroup Server either as Windows Services

or as stand-alone servers which will only run when a HP TRIM client is running

• The demonstration database, its backup file TRIMDemoDB.bak, database file TRIMDemoDB_Data.mdf, database log TRIMDemoDB_Log.ldf, document store and document content index install to C:\HPTRIM\ServerData\DEMODB to ensure compatibility with newer Windows operating systems


Page 34 of 80

Running HP TRIM for demonstrations

1 Click its shortcut in the Start menu → All Programs → HP TRIM folder.

2 The first time you run HP TRIM for demonstrations, enter your license details and click OK

3 In the toolbar, click Save and then Deploy to update the configuration on the Workgroup Servers

4 Close HP TRIM Enterprise Studio

5 You will be automatically logged on to the HP TRIM demonstration database as the HP TRIM administrator


Page 35 of 80

Maintenance installation

Use a maintenance installation to change the installed features.

1 Using your Windows installation function, select HP TRIM and click the appropriate Change button. The Application Maintenance dialog box appears:

2 Select one of the options and click Next: — Repair - see Repair — Remove - see Remove — Modify - see Modify

Repair

Repair re-installs only the features which were selected during the installation or the latest modification to the installation. If you have HP TRIM Servers running as services, then you will need to re-type the user password for the services to be re-installed correctly.

Repairing an installation

1 In the Application Maintenance dialog box, select Repair and click Next. The Ready to Install the Application dialog box appears.

2 Click Next to start the repair. The dialogue HP TRIM has been successfully installed appears.

3 Click Finish.

The HP TRIM installation has been repaired.


Page 36 of 80

Remove

Remove removes HP TRIM from your computer. Before removing HP TRIM, see Removing HP TRIM.

Removing an installation

1 In the Application Maintenance dialog box, select Remove and click Next.

2 The HP TRIM Uninstall dialog box appears:

3 Click Next to uninstall HP TRIM

4 Follow the on-screen instructions. The dialogue HP TRIM has been successfully installed appears.

5 Click Finish.

The HP TRIM installation has been removed from the computer.


Page 37 of 80

Modify

Modify enables you to add or remove HP TRIM features. It will only add or remove the features you choose. It will not perform a full reinstallation.

Modifying an installation

1 In the Application Maintenance dialog box, select Modify and click Next.

2 The Select Features dialog box appears.

3 Select the features you want to install

4 Click Next.

5 The HP TRIM Server Configuration dialog box appears.

6 Fill in the details and click Next.

The Click Next to begin installation dialog box appears. 7 Click Next to complete the modification.

The dialog HP TRIM has been successfully installed appears.

8 Click Finish. The HP TRIM installation has been modified.


Page 38 of 80

Installation dialog boxes

This section describes the dialog boxes that appear during a graphical installation. The order in which the dialog boxes appear depends on the features you select. Therefore, this section is a listing rather than step-by-step instructions. For a demonstration installation, see Demonstration installation.

1 When you run the HP TRIM installation locally, the Welcome dialog appears:

2 Click Next.

The License Agreement dialog appears:

3 Select I accept the license agreement and click Next.


Page 39 of 80

The Destination Folder dialog appears.

— Destination Folder – click Browse to change the folder to install HP TRIM in.

The default is C:\Program Files\Hewlett-Packard\HP TRIM.

4 Click Next. The Select Features dialog box appears:

The installation options for each feature: — Will be installed on local hard drive

— Entire feature will be installed on local hard drive

— Entire feature will be unavailable


Page 40 of 80

5 Select the features to install: HP TRIM Default: Will be installed on local hard drive. — Client - client features.

Default: Will be installed on local hard drive.

– Standard Data – installs standard report layouts, noise words, post codes, samples for desktop integration. Includes standard report layouts, Australian noise words and postal codes import files and Web publish layouts for importing. Recommended to install. Default: Will be installed on local hard drive.

– TRIMScan – installs a scanning application which enables you to scan documents, images etc. and check them directly in to HP TRIM. Not available for 64-bit installation.

– Lotus Notes Integration - select to integrate HP TRIM with Lotus Notes mail clients. Default: Entire feature will be unavailable. Lotus Notes files are installed in the folder HP TRIM\Lotus. Not available for 64-bit installation.

– TRIMPort - installs HP TRIM's data import/export utility. It is recommended for HP TRIM administrators only. Default: Entire feature will be unavailable. Not available for 64-bit installation.


Page 41 of 80

— Server

– Workgroup Server - installs and registers a HP TRIM Workgroup Server on this computer. Default: Will be installed on local hard drive. Workgroup Servers do the bulk of the work in a networked installation of HP TRIM and should be positioned in your network to provide distribution of load.

– Enterprise Studio - installs utility to manage HP TRIM Workgroup Servers, datasets and the operating environment. It is recommended for HP TRIM administrators only. Default: Will be installed on local hard drive.

– Demonstration Database - installs a database on your local drive you can use for demonstration purposes. Default: Entire feature will be unavailable.

– WebDrawer ISAPI Extension - installs the WebDrawer ISAPI components. WebDrawer provides read-only Web access to HP TRIM. Default: Entire feature will be unavailable.

– TRIM Render- installs a utility to render documents and add the rendition to the record in a fully automated process. This module is available under a separate license. Default: Entire feature will be unavailable.

Note

Before choosing to install TRIM Render, ensure the following:

• Your system meets the requirements for the module as specified in TRIM7.12_Spec.pdf

• You have your HP TRIM dataset connection information for the HP TRIM Default Connection Settings dialog box, which you will need to enter during the installation process

• You use the TRIMServices account or equivalent to install and run TRIM Render to ensure access to important HP TRIM functions like the document stores

After installing TRIM Render initially, follow the instructions in Appendix C to configure the printer drivers, security settings and to find information on multiple server installations.

– Disk Usage - displays the HP TRIM Setup dialog

– Reset - sets all the above options to their defaults


Page 42 of 80

6 Click Next.

The order in which the next dialog boxes appear depend on the features you selected and whether they are needed: The License Settings dialog box:

Fill in the fields: — License Name

— License Number -- or –

— License Expiry Date

— HP TRIM Registration Key - fourteen sections of four numbers or letters, e.g.: ABCD-1234-EFGH-5678-IJKL-9012-MNOP-3456-QRST-7890-UVWX-1234-YZAB-5678

The HP TRIM Default Connection Settings dialog box:


Page 43 of 80

Use this dialog to set up your HP TRIM client to Workgroup Server default connection settings. You can change these settings using the HP TRIM client. — Default Database ID - the unique identifier for the dataset to which the client should

connect. This identifier is set when you create the dataset. Set to 45 by default - the HP TRIM demonstration dataset ID.

Note

Lower case characters are not supported for the dataset ID; always use upper case characters.

— Default Database Name – name of database, for example, companyDB — Primary Workgroup Server – name of the computer that runs the Workgroup Server

to which the client should connect — Secondary Workgroup Server – name of the computer that runs the Workgroup

Server to which the client should connect if it cannot connect to its primary Workgroup Server after three attempts.

— Port Number – port the client should use to connect to the Workgroup Server

Note

The Primary and Secondary Workgroup Server fields are for the HP TRIM client to search for a backup secondary Workgroup Server in case the primary Workgroup Server is unavailable due to server failure, maintenance, etc. HP TRIM switches to the secondary Workgroup Server seamlessly after a short delay when the primary one is not available. When the secondary Workgroup Server fails and the primary one is available again, HP TRIM will switch back to the primary Workgroup Server. If both Workgroup Servers are unavailable, HP TRIM will display a message that the Workgroup Server is unavailable. The addresses in the two fields should not point to two different datasets.


Page 44 of 80

The HP TRIM Client Configuration dialog box:

Use this dialog to set up the HP TRIM client. You can change these settings using the HP TRIM client. — File Association - select the type of HP TRIM client to use to open HP TRIM

reference (.tr5) files

– HP TRIM Desktop - HP TRIM Desktop

– HP TRIM - HP TRIM client — ODMA Integration – HP TRIM can integrate with ODMA (Open Document

Management API) applications. Not available for 64-bit installation. Select the type of HP TRIM client to use when integrating with ODMA compliant applications:

– No ODMA Integration - no ODMA integration

– Integrate HP TRIM with all ODMA compliant applications - installs the ODMA integration functions for HP TRIM Desktop

– Use ODMA directly with HP TRIM – select to set HP TRIM to not use Offline Records integration

– Allow access to Windows File Open and Save Dialogs - enables users to navigate to the standard File → Open and File → Save dialogs from ODMA applications. To force users to save to Offline Records or HP TRIM, do not select this option.

— E-mail Integration - select the type of e-mail integration to use with HP TRIM. Lotus Notes is not listed as it requires additional software to be installed.

– No E-mail Integration

– Microsoft Outlook - HP TRIM in Outlook

– Novell GroupWise - enables HP TRIM File menu commands in Novell GroupWise


Page 45 of 80

— Install the Desktop shortcuts for HP TRIM – select to install shortcuts in the Desktop folder for:

– HP TRIM client

– HP TRIM Desktop

– HP TRIM Queue Processor — Automatically Get Global Settings on first startup of TRIM – select for HP TRIM to

initially download the settings your HP TRIM administrator has set for all users The HP TRIM Server Configuration dialog:

Use this dialog to set up your HP TRIM Server configuration.

Note

• You do not need to use these settings if you are configuring HP TRIM to run

only as a client • You cannot change these settings using the HP TRIM client

HP TRIM uses the information from this dialog to configure the access permissions set up in your HP TRIM environment and provide the necessary access to users. The HP TRIM Workgroup Server and WebDrawer Web Server are installed and registered as Windows Services. The account to run the services is the TRIMServices account. It depends on the installation method you are using which options are available in this dialog. — Network Type - select the type of network you are installing HP TRIM on:

– Windows Domain - default

– Novell Network

– Novell Tree - for a Novell network, enter the Novell tree to which this computer is connected. HP TRIM will use this tree for Novell login name resolution.


Page 46 of 80

Note

For a Novell network, the Network Type field defaults to Novell Network and the dialog also contains a Novell Tree field. See also Novell authentication.

— Domain Name - for a Windows domain, enter the domain name on which the HP

TRIM services will be running. HP TRIM appends it to the user name below to create the path domainname\username, under which HP TRIM services will run, for example, mydomain\TRIMServices

Note

If you intend to use a local user to run your services:

a Type the name of your computer in the Domain Name field

b Specify a local user in the User Name field to run your HP TRIM Services

— User Name - type the name of the user you wish to use to run the HP TRIM services

under - usually TRIMServices. The HP TRIM Workgroup Service and WebDrawer Service log on with this user name. The user you enter here should have Log on as a Service policy rights on the computer and sufficient permissions to run a Windows Service. This user also has access permissions to the HP TRIM Workgroup Server.

— User Password - type the password for the TRIMServices domain account user name — Server Data Folder – select the server data folder.

It is recommended to keep the default. — Server Log Files Folder – select the folder for the server log files.

It is recommended to keep the default.


Page 47 of 80

The Existing Web Sites on this Server dialog box appears if you are installing WebDrawer ISAPI:

Select the Web site to install WebDrawer ISAPI to.

7 Click Next The Ready to Install the Application dialog appears:

8 Click Next.


Page 48 of 80

HP TRIM installs on the computer and the dialog box HP TRIM has been successfully installed appears:

9 Click Finish.

HP TRIM is installed. Because of changed file paths, some features require your computer to reboot after installation. See Steps to setting up a working system for what to do next.

Missing Prerequisites dialog box

This dialog lists HP TRIM features that have failed to meet their installation requirements.

For a full list of requirements for HP TRIM features, see TRIM7.12_Spec.pdf.


Page 49 of 80

Installation using .msi file rules and behavior

• The HP TRIM installation is managed. This means that Windows Installer keeps tabs on the components of HP TRIM that are installed on the computer.

• You need to run the installation with administrator access rights and in some cases with elevated access rights. If you are not running the installation via group policy, you can set these on a computer using Group Policy set by the domain wide Group Policy or on a local computer.

• If the administrator performs the installation through Group Policy, elevated access rights apply to the installation for its life If the system administrator does not perform the installation through Group Policy, the installation will repair, modify etc. as long as the person doing the repair has elevated access rights - for example, is a local administrator or the computer has elevated access rights set for Windows Installer in its Group Policy If this is not the case, some installation tasks such as repair or modify will fail because they need elevated access rights to write to the registry and to delete or write files on the computer.

• HP TRIM Servers are set to start automatically; however, the .msi package does not start them. Therefore, when a server shuts down or needs to be rebooted, its services start automatically after the reboot.


Page 50 of 80

Automatic deployment tool

The HP TRIM AutoDeploy tool assists in updating the current user configuration of HP TRIM. It is also used to keep the current user's configuration details up to date. If the current user has not accessed the computer, the HP TRIM AutoDeploy tool will create the registry keys and files required to run HP TRIM. Once installed, it launches a software update, if there is one available.

Note

• You must have Group Policies set to allow .msi files to install with elevated access rights for ordinary users.

• This feature will not update HP TRIM Workgroup Servers. On the initial software rollout to desktop computers, the rollout parameters should include the primary Workgroup Server for each computer. AutoDeploy checks this server to see whether a software update is available. When a user logs on, AutoDeploy checks whether a file called AutoDeploy.ini exists in a share named AutoDeploy on the desktop computer's designated primary Workgroup Server. The share must allow users read permission for itself and its contents. If the file does not exist, AutoDeploy will exit after checking the current user's configuration. If the file does exist, AutoDeploy will look up two values from the .ini file. AutoDeploy will expect the .ini file to be formatted like this: [AutoDeploy Detail] Auto_DepVersion=6.2.X.XXXX Script_Name='Setup.bat'

• Auto_DepVersion is the full version of the upgrade

• Script_Name is the name of the script that AutoDeploy must execute if the Service Pack upgrade of that date has not yet been installed on this computer. This can be any executable file or the .msi file itself. It should not include a path and the file is expected to be in the AutoDeploy share. For example, the script name could be HPTRIM_x86.msi, which should be in the AutoDeploy share. If the value of Auto_DepVersion is different to the version of HP TRIM installed on the computer – HP TRIM Enterprise Studio will check the version of HP.HPTRIM.SDK.dll - the script will be executed to install the latest Service Pack upgrade. The registry update will run after that.


Page 51 of 80

AutoDeploy changes to the current user

• AutoDeploy sets HP TRIMAppData, HP TRIMLocalAppData paths if they were configured in the rollout parameters. If they were not, the registry will have blank values for these keys and HP TRIM will use the defaults.

• If the current user has not executed HP TRIM previously, AutoDeploy configures the ODMA settings

• It sets the spelling checker defaults and the location of user spelling checker dictionaries

• If no default database is set for the current user, it copies the computer default

• If Microsoft Outlook mail clients are registered and the required current user settings are not available, AutoDeploy sets them for the current user

Current user configuration

Initial software installation can mostly configure details for the computer (All Users) and for new users on that computer - those with no existing profile. However, due to local environment inconsistencies, configuring a computer environment for a user with an existing profile can be quite difficult. The HP TRIM AutoDeploy tool handles this challenge using the file TRIMAutoDeploy.exe. It is set to run when a user logs on to a computer that has HP TRIM installed. It checks:

• Whether this user has a configured HP TRIM environment

• Whether the environment was configured no earlier than the initial HP TRIM software installation or last update using a Service Pack upgrade

HP TRIM AutoDeploy does this by comparing the registry key date values of:

• HKEY_CURRENT_USER\Software\Hewlett-Packard\HP TRIM\MSI Setup\CuDepDate with

• HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP TRIM\MSI Setup\Depdate

— If the first one is not equal to the second one or does not exist at all, then either this user is not configured to run HP TRIM or their configuration may need updating. In this case, HP TRIM AutoDeploy reads the registry to determine the original rollout, installation or update parameters stored in HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP TRIM \MSI Setup and implements a current user configuration accordingly - under the key, HP TRIM looks for a string value containing a server name. It then checks whether this server has a shared directory called AutoDeploy.


Page 52 of 80

Note

Autodeploy will not trigger an update if the computer you are using is running a Workgroup Server or Event Server. It needs to be a client only installation.

The registry key value of HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP TRIM\MSI Setup\Depdate updates when you first install HP TRIM or when you perform a Service Pack upgrade.

Deactivating HP TRIMAutoDeploy

You can use the following script and Group Policy object to turn off HP TRIM AutoDeploy through the registry for non-HP TRIM users of a computer. The registry key for HPTRIM_AutoDeploy.wsm called TRIMAutoDeploy_On is in HKEY_CURRENT_USER\Software\Hewlett-Packard\HP TRIM\MSISettings and has a default value of 1. TRIMAutoDeploy.exe checks this value and will only run if it is set to 1. You can change this through Group Policy to be 0 for users that are not supposed to see HP TRIM. The process works through a combination of a script and a Group Policy object. The following script will prevent TRIMAutoDeploy from creating HKCU registry keys. It should be saved in the %system%\system32 \GroupPolicy\User\Scripts\Logon folder. Set Sh = CreateObject("WScript.Shell") Key = "HKEY_CURRENT_USER\" SH.RegWrite Key & "Software\Hewlett-Packard\HP TRIM\MSI Setup\TRIMAutoDeploy_On", 0, "REG_DWORD"

Applying to Group Policy

1 From the Start menu, select Run and type GPedit.msc

2 Select User Configuration → Windows Settings → Scripts (Logon/Logoff) → Logon

3 Right-click and select Properties

4 Click Add.

5 The logon script you saved earlier should appear in the default scripts folder.

6 Select it and click OK twice.


Page 53 of 80

5 Upgrading HP TRIM Before upgrading your HP TRIM environment, it is strongly recommended you perform a trial upgrade on a copy of your dataset in a test environment. This test environment should be isolated from your live environment with no chance of confusing any live and test data.

Note

Before any upgrade, backing up your data is essential.

Use HPTRIM_xNN.msi and the relevant other .msi files from the installation media. An upgrade installation searches for an installed instance of HP TRIM, installs the new version and removes the previous version, if there is one. If there is no previous installation, the installer performs a standard installation.

Version support

You can upgrade to this version of HP TRIM only from HP TRIM 6.2 or later. If you are using older versions of TRIM, upgrade your existing environment to HP TRIM 6.2 first before upgrading to HP TRIM 7.x. On your TRIM 6.2 installation media, see TRIMCap2Con.pdf for upgrades from TRIM Captura to TRIM Context and TRIMCon2Con.pdf for upgrades from TRIM Context to TRIM 6.2.

Customized client toolbars and menus

During the upgrade process, HP TRIM resets all toolbars and menus to the defaults.


Page 54 of 80

Upgrading from HP TRIM 6.2

About upgrading from TRIM 6.2

The upgrade does not preserve the TRIM 6.2 user environment, i.e. shortcuts, favorites, etc. You may have to recreate it manually after the upgrade. The upgrade resets the data for global settings, which is only available after upgrading the servers and should not be used before the server upgrade is complete. The way peripheral applications are installed has changed significantly and does not always allow for an upgrade from TRIM 6.2 using a .msi file. Therefore, make sure you follow the recommended steps exactly to avoid removing 6.2 data or being unable to fully remove 6.2 peripheral applications. HP TRIM peripheral applications should always be the same version and build number as the HP TRIM main client software.

Upgrade steps from HP TRIM 6.2 to 7.x

Upgrade HP TRIM from version 6.2 in the following order:

1 Perform database and dataset maintenance tasks as described in Appendix D below

2 Upgrade HP TRIM and its peripheral applications on all the HP TRIM client computers: In addition to the main HP TRIM client software, client computers may have different HP TRIM peripheral applications and extensions installed. Upgrade steps for client computers:

a If the computer has Microsoft Excel add-ins for earlier versions of TRIM installed, remove them according to the instructions in your Microsoft Excel add-in documentation

b Using the Windows Programs function, check which HP TRIM peripheral applications and extensions are installed on the computer and make a note of the ones that need to be available in HP TRIM 7.

c If you need to upgrade any Web based applications or applications based on the HP TRIM Software Development Kit (SDK), prepare and remove them from the upgrade folder, if necessary:

– Web Content Management (WCM) - WCM 6.2 is not compatible with WCM 7. Make notes about its settings to be able to use them for the new installation.

– WebDrawer ISAPI – if the folders that their virtual directories point to are under the folder Program Files\TRIM Context, copy them to a location unaffected by the upgrade

– WebService – if you have created additional Web sites other than the default HP TRIM site, and if these Web site’s virtual directories point to folders under Program Files\TRIM Context, move these folders to a location unaffected by the upgrade

– SDK applications – if they are in the folder Program Files\TRIM Context, copy them to a location unaffected by the upgrade


Page 55 of 80

d Remove all peripheral HP TRIM applications from the computer by using the Windows Programs function

e Remove TRIM Windows Runtimes by using the Programs function

f Ensure the client computer has a supported operating system and all the necessary components installed. See TRIM7.12_Spec.pdf.

g Install VBRuntimes_x86.msi. This step is not necessary for 64-bit installations.

h Install VS2008Runtimes_xNN.msi

i Upgrade the main HP TRIM client software using HPTRIM_xNN.msi from the installation media

j If needed, use it to also install these features that were separate peripheral application .msi files in TRIM 6.2: — HP TRIM Rendering module — HP TRIMScan — HP TRIM SAP integration

k Install the remaining peripheral HP TRIM applications using the respective .msi files from the installation media. Difference in installation between 6.2x and 7.x:

– Excel integration does not require a separate installation

l If you had to back up Web or SDK application files in step c, move the files back to the HP TRIM installation folder, by default Program Files\Hewlett-Packard\HP TRIM. Alternatively, move your Web files to a more appropriate location and update the virtual directory and other references to reflect the new file locations.

3 Make HP TRIM unavailable for users. In HP TRIM Enterprise Studio Help, see Dataset availability and messaging.

4 Back up all HP TRIM data. See Backing up and Restoring your Data.

5 Shut down all the Workgroup Servers

6 Upgrade the HP TRIM Workgroup Server software on all Workgroup Servers. Use HPTRIM_xNN.msi.

7 Nominate one computer as designated administrator computer and install HP TRIM Enterprise Studio on it using HPTRIM_xNN.msi.

8 On the administrator computer you set up in step 7, run the new version of HP TRIM Enterprise Studio. To preserve your 6.2x TRIM Enterprise Studio settings as much as possible, copy the file TRIMconfig.tcfg from your TRIM 6.2x administrator computer folder ServerData. It may be in a subfolder. Paste it to the HP TRIM 7 administrator computer you set up in step 7, folder ServerData\TRIM. By default, the folder is in C:\HPTRIM.


Page 56 of 80

9 In HP TRIM Enterprise Studio, on the File menu, use Open to open the file TRIMconfig.tcfg that you just copied. Upgrade the dataset schema - in HP TRIM Enterprise Studio Help, see Upgrading a dataset schema.

10 Perform the additional dataset and database maintenance recommended in Appendix D below

11 In HP TRIM Enterprise Studio, review the Workgroup Server configuration, in particular event processing. In HP TRIM Enterprise Studio Help, see Configuring event processing.

12 Make changes as necessary and save the new configuration

13 Start the HP TRIM Workgroup Servers

14 In HP TRIM Enterprise Studio, deploy the new configuration

15 If there are outstanding events in the event processing monitor, convert them using the Repair function in the event processing monitor. In HP TRIM Enterprise Studio Help, see Monitor Event Processing dialog box.

16 Bring HP TRIM online The upgrade is complete.

Note

If you are using an ISYS document content index, after upgrading to 64-bit Workgroup Servers, re-create your entire document content index, as the 64-bit version does not recognize the existing indexes. In HP TRIM Enterprise Studio, see Recreating a document content index.


Page 57 of 80

Upgrading from HP TRIM 7

Upgrade steps from HP TRIM 7.x

Upgrade HP TRIM from version 7.x in the following order:

1 Back up all HP TRIM data. See Backing up and Restoring your Data.

2 Upgrade all the HP TRIM clients. See Upgrading client computers from version 7.

3 Make HP TRIM unavailable for users. In HP TRIM Enterprise Studio Help, see Dataset availability and messaging.

4 Shut down all the Workgroup Servers

5 Upgrade the HP TRIM Workgroup Server software on all Workgroup Servers. Use HPTRIM_xNN.msi.

6 Nominate one computer as designated administrator computer and install HP TRIM Enterprise Studio on it using HPTRIM_xNN.msi.

7 On the administrator computer you set up in step 6, run the new version of HP TRIM Enterprise Studio and use it to upgrade the dataset schema. In HP TRIM Enterprise Studio Help, see Upgrading a dataset schema.

8 In HP TRIM Enterprise Studio, review the Workgroup Server configuration, in particular event processing. In HP TRIM Enterprise Studio Help, see Configuring event processing.

9 Make changes as necessary and save the new configuration

10 Start the HP TRIM Workgroup Servers

11 In HP TRIM Enterprise Studio, deploy the new configuration

12 Bring HP TRIM online The upgrade is complete.

Note

If you are using an ISYS document content index, after upgrading to 64-bit Workgroup Servers, re-create your entire document content index, as the 64-bit version does not recognize the existing indexes. In HP TRIM Enterprise Studio, see Recreating a document content index.


Page 58 of 80

Upgrading client computers from version 7

In addition to the main HP TRIM client software, client computers may have different HP TRIM peripheral applications and extensions installed. These should always be the same version and build number as the HP TRIM main client software. Upgrade steps for client computers:

1 If the computer has Microsoft Excel add-ins for earlier versions of TRIM installed, remove them according to the instructions in your Microsoft Excel add-in documentation

2 Using the Windows Programs function, check which HP TRIM peripheral applications and extensions are installed on the computer

3 Remove those peripheral applications which are no longer required on the computer by using the Windows Programs function

4 Ensure the client computer has a supported operating system and all the necessary components installed. See TRIM7.12_Spec.pdf. Upgrade the main HP TRIM client software using HPTRIM_xNN.msi from the installation media.

5 Restart the computer

6 Upgrade the remaining peripheral HP TRIM applications using the respective .msi files from the installation media. See Upgrading HP TRIM peripheral applications from version 7.

Upgrading HP TRIM peripheral applications from version 7

Upgrading WebDrawer ISAPI from version 7

1 Take a note of all WebDrawer ISAPI configuration details

2 Remove WebDrawer ISAPI 7.x

3 Install new version of WebDrawer ISAPI

4 Configure new version of WebDrawer ISAPI manually according to the instructions in TRIM7.12_WebDrawer.pdf


Page 59 of 80

Mixed environments

To minimize downtime in very large organizations, HP TRIM 7.x runs in mixed environments, i.e. environments with clients and servers using the same version of HP TRIM (e.g. 7), but different build numbers. 2.0.x represents the build number. You can see version and build numbers in the HP TRIM client by clicking Help → Setup Information → Software Versions. However, as a general rule, HP TRIM clients in mixed environments must have build numbers the same or later than the HP TRIM Workgroup Server/s they communicate with. For example, with a Workgroup Server on version 7.1.0.75, the clients should not use any build of version 7.0 or 6. However, they could use HP TRIM 7.1.0.92, for example. Without this ability, downtime would include the time it takes to roll out HP TRIM 7 to all clients. With this backward compatibility, in most cases, you can reduce the downtime to the dataset and server upgrades. This can make a significant operational difference where HP TRIM is now considered to be a critical system. With the above in mind, a mixed environment provides an acceptable level of functionality for the period of the rollout, but it cannot:

• provide the full functionality of the latest release

• provide the same degree of stability of a single-build implementation. Mixed environments are not suitable for either testing or training purposes.

Upgrade steps for mixed environments

Upgrade in the following order:

1 Client computers See Upgrading client computers.

2 Server computers

3 Database schema, if necessary

Note

All Workgroup Servers must be at the same revision level.


Page 60 of 80

Upgrading Offline Records

It is recommended users check in their Offline Records files and folders before an upgrade to version 7. Before upgrading to a 64-bit HP TRIM client, you must check in all documents from Offline Records to prevent data loss. HP TRIM 7 converts an existing TRIM 6.2 Offline Records Jet database in the default location to an Offline Records database and deletes the Jet database when the user accesses Offline Records for the first time. HP TRIM 7 does not take a backup of the Jet database, however, after a successful conversion, you will find the old copied database as trimtd.mdb.copied in the folder. The Offline Records database is stored in the file OfflineRecords.dat in the user's data folders along with the actual Offline Records documents. After accessing Offline Records for the first time, users should press F6 in HP TRIM to see the records. Offline Records must be in its default location.


Page 61 of 80

6 Removing HP TRIM 1 Use the Windows Control Panel → Programs function to remove all peripheral HP TRIM

applications, modules and components, for example: — LabeLink — Kofax, etc.

2 Remove HP TRIM using the Windows Control Panel → Programs function

3 Remove HP TRIM Microsoft VB runtimes, if necessary

4 Remove HP TRIM Microsoft runtimes for VS2008 The installer requires the Microsoft .NET Framework3.5 SP1 to remove HP TRIM. You can remove it when all HP TRIM components are removed.

Note

User data folders – the installation program does not remove the user's Application Data and Local Settings → Application Data folders when removing HP TRIM, as these folders may contain user-created data. By default, these folders are located in the user's profile area, for example, C:\Documents and Settings\<USER>\Application Data\Hewlett-Packard\HP TRIM and C:\Documents and Settings\<USER>\Local Settings\Application Data\Hewlett-Packard\HP TRIM.


Page 62 of 80

7 Server and Client Configuration Options By default, HP TRIM uses the Windows Documents and Settings user profile folders for storing information about the HP TRIM application and cached files. The HP TRIM installation enables you to relocate each folder for the client computers from the default folder to the folder you require. These folder locations are set in the system registry. You can manually create and relocate these folders, the server folders and registry keys - see Client folder location for information.

Client folder locations

You can make changes to the folder locations on the client computer. However, the path must point to a folder that is unique to the user.

Client application data paths

Windows application data path

Contains the user's HP TRIM configuration and their Offline Records stored in their local drive. Typically, this path points to a sub-folder of the user's local folder. By default, in Windows XP, the value of HKEY_CURRENT_USER\SOFTWARE\Hewlett-Packard\HP TRIM\DataPaths\TRIMAppData is C:\Documents and Settings\<username>\Application Data\Hewlett-Packard\HP TRIM or its equivalent in other operating systems.

Local application data path

You can further separate the Offline Records document storage location by changing the registry key HKEY_CURRENT_USERS\SOFTWARE\Hewlett-Packard\HP TRIM\DataPaths\TRIMLocalAppData. The default value depends on the operating system - for Windows XP, it is C:\Documents and Settings\<user>\Local Settings\Application Data\Hewlett-Packard\HP TRIM\ or its equivalent in other operating systems.


Page 63 of 80

My documents data path or personal folders

This path enables HP TRIM to store the HP TRIM client document cache on the user's local computer. It is recommended not to change this path from the client computer path as this is redundant cache data for efficiency purposes only. By default, the server data paths point to: C:\HPTRIM.

Server folder locations

Server application data

The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP TRIM\DataPaths\TrimAppData stores the path. The default value depends on the operating system - for Windows 2003, it is C:\HPTRIM\ServerData.

Server local data

The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP TRIM\TrimLocalAppData and the default value is C:\HPTRIM\ServerLocalData..

Local document store caching

You can use a local document store cache on a user's computer. See HP TRIM Help topic Store Caching tab.


Page 64 of 80

Log file registry keys

Log file location

While the .msi interface enables you to modify the location of the server log files folder using the HP TRIM Server Configuration dialog box, you can also modify it by using a command line like hptrim_x86.msi SERVER_LOCAL_DATA_FOLDER=d:\<folder path>. Alternatively, you can create the folders, registry keys, sub-keys and their values manually and then export and import them to other computers:

1 Open the registry keys — Client

HKEY_CURRENT_USER\Software\Hewlett-Packard\HP TRIM\DataPaths

— Server HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP TRIM\DataPaths

2 Create the relevant sub-keys — Client

TRIMAppData

— Server TRIMLocalAppData

3 Create the sub-key values. They are the folder paths where you want the log files to be. These folders can be in any location. Examples: — Client

C :\Documents and Settings\<username>\Application Data\Hewlett-Packard\HP TRIM\TRIMAppData\

or D:\HP TRIM User Log Files\

— Server C :\Documents and Settings\<username>\Application Data\Hewlett-Packard\HP TRIM\TRIMLocalAppData\

or D:\HP TRIM Server Log Files\

5 Create the folders where you want the log files to be, for example, D:\HP TRIM Server Log Files\


Page 65 of 80

Novell authentication

HP TRIM can retrieve the Novell user credentials when the user's Windows login is different from the Novell login This authentication process is set during the installation process and uses Novell authentication.

Registry settings per installation computer

• HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP TRIM \Network\Resource=<NOVELL_TREE> (String)

• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\LegacyAuthentication = 1 (DWORD) This must be set to 1.

These are set when you install the client and Workgroup Server with the option Novell Network selected


Page 66 of 80

Network users group and the TRIMServices account

1 In Computer → Manage → Local Users and Groups, create the individual network user names that will log on to HP TRIM, if they do not exist

2 Add these network login names eventually to the HP TRIM database so that the users can log on to HP TRIM directly using their network logins

3 Create a TRIMServices account which will be used to run HP TRIM Server components

Note

• Write down the account name and password you have chosen as you will

need it later. • Ensure you have created the account with the necessary permissions before

proceeding. You will need no other accounts for the RDBMS.

Caution

The installation process does not add the services user to the Log on as a Service policy for any computer running a HP TRIM service. To start any of the HP TRIM services, include the services user in the Log on as a Service policy on the computer; otherwise the services will fail to start and cause the error message: Services Could not start the HP TRIM Workgroup Server services on Local Computer. Error 1069: The Services did not start due to a logon failure. The solution is to re-type the password for the services user in the properties of one of the services, which will add the user to the Log on as a Service policy and return the message: Services The account mydomain\trimservices has been granted the Log On As A Service right. The Log on as a Service policy is in Local Security Settings under User Rights Assignments.

The TRIMServices account is the proxy that enables communication between the HP TRIM Servers.


Page 67 of 80

8 Backing up and Restoring your Data It is important that you back up the contents of your HP TRIM dataset including electronic stores regularly, preferably daily. You will find the recommended backup strategy in the following topics of this document. Remember that this is your data and it is your responsibility to make adequate backups. Your business relies on this data to survive; therefore it is very important that you make appropriate backups to protect your data. We urge you not to be complacent. Loss of data is quite a common occurrence. Some of the reasons for losing data are listed in the following topics.

Reasons for backing up

A number of factors can result in the loss of data:

• Power fluctuation or blackout

• System failure

• Theft

• Operator error

• Communications (network) failure

• Malicious damage

Backup strategy

To ensure optimum performance of your HP TRIM dataset, we recommend regular maintenance and to consider the following as part of a comprehensive backup and recovery plan. This is not an exhaustive list:

• Back up before initial installation and upgrades

• Back up daily - this is the minimum recommended

• Maintain multiple generations of backups to protect against backup corruption, for example, three generations of each backup media before re-use

• Backup media should be verified regularly

• Make sure you know how to restore from your backup, should the need arise, i.e. regular practice of restoration to verify the process and ensure personnel are familiar with the requirements

• Off-site storage of backup media in case of fire, theft, local disaster etc.


Page 68 of 80

Dataset components

The components that should be backed up on a regular basis for your particular environment require thought and planning. All the components combine to create a matched set of data. To ensure the integrity of your data, it is recommended you back up the data as one set and if necessary, restore it as a complete set. In most instances, all data as one set would be ideal; but as a minimum, you should back up all primary data. Splitting the database components into primary and ancillary data results in these lists: Primary data

• Database tables (relational database metadata)

• Electronic document stores

• Document content search indexes

• Audit logs

Ancillary data

• User Offline Records folders

• User configuration files

• Queue processing folders

• Document content search indexes

• Audit logs Both document content search indexes and audit logs appear under each of the headings above. Whether either is considered primary or ancillary data is site specific. You can regenerate the entire structure of document content search indexes from the documents themselves; therefore you may consider these non-core structures. However, it can take so much time to regenerate a full set of content indexes that you should consider them to be primary data. Audit logs are used to varying degrees depending on the implementation of HP TRIM. Whether you consider audit logs primary or ancillary data depends on the use of such logs by your organization - simple reference item, critical security feature or something else? A backup and recovery plan must decide under which category each falls, and treat them appropriately. The purpose of backups is to ensure that you can recover your data, should something go wrong. Whatever the reason for the loss of data may have been - if you have adequate backups, you can minimize or even eliminate loss of service and data. Backups are an integral part of your everyday computer housekeeping and should be regular practice. You should use incremental backup mechanisms only with extreme care and after due consideration.


Page 69 of 80

Backup techniques

You can perform two types of backups on a database:

• Hot - while the database is online and usable

• Cold – while the database is closed and not available to users A cold backup for a HP TRIM environment is straightforward: All components - relational database, document stores, etc. - are captured in their inactive state. For a hot backup, you need to be careful and consider how to back up all the primary and optionally ancillary data components of a HP TRIM system. You essentially need to ensure the backup can capture the primary disk structures, like electronic stores, in a stable fashion at the same point in time you are performing a hot backup on the relational database. Some options to consider:

• Using utility software to take a snapshot of the files and folders • Using software or hardware replication or mirroring techniques, for example RAID, and

associated mirror breaking and recovering features to capture one copy of the files and folders as a point-in-time snapshot

• Using a combination of the above or custom approaches Always remember, treat your primary and optionally ancillary HP TRIM data as one set.

Recovery techniques

Many systems include recovery facilities that enable you to restore to a particular point in time - which may not necessarily be the same point in time of a backup. Such point-in-time recovery features usually use a database's transaction log to replay activity since a known backup point. This is sometimes referred to as rolling forward. While you can use such a facility with your HP TRIM relational database, remember the collateral impact and therefore steps required on other primary and ancillary data structures. File systems, FTP Servers etc. that hold your other HP TRIM data structures do not have a transaction log on which to rely - so rolling forward or rolling back your database requires some effort by you to keep these structures synchronized. Several options are available if you need a point-in-time recovery:

• Roll forward/back only to a point in time at which a synchronized set of backups is available

• Roll forward/back to a desired point with a plan to accommodate any orphaned or ghost information

Always remember, treat your primary and optionally ancillary HP TRIM data as one set.


Page 70 of 80

A Steps to setting up a working system This section outlines a sequence of steps you need to go through to set up a working system. This is often the task of a system administrator. Some of the points below are mandatory for any system to work, whereas some functions are optional. It depends on how you choose to administer your paper and electronic records. Refer to the HP TRIM Help file TRIM.chm topics and chapters specified for a detailed explanation of each function and further guidance on how to complete each step. Bookmark this section so that you can come back to it while you complete the steps. The mandatory steps have an asterisk behind them.

1 Install RDBMS software on the server to host the dataset*

2 Install HP TRIM software on the designated Workgroup Server computers*

3 Using HP TRIM Enterprise Studio, create and register the HP TRIM dataset*

4 Using HP TRIM:

a Set up the security levels and security caveats.* See Security levels administration and Security caveats administration.

b Set up postcodes. See Chapter 31 - Postal codes.

c Set up the internal and external Locations (Contacts and Organisations)*. See Chapter 13 - Locations.

d Set up user profiles - login accounts for staff who will use HP TRIM*. See Profile tab.

e Set up a Thesaurus. See Chapter 16 - Thesaurus.

f Set up Classifications. See Chapter 17 - Classifications.

g Set up Archive Retention Schedules. See Chapter 20 - Archive Retention Schedules.

h Set up system options. See System Options.

i Set up the HP TRIM calendar. See Calendar editor for administrators.

j Set up noise words, title words and notes words. See Chapter 22 - Word indexes.

k Recreate word indexes to index the Classifications, Retention Schedules, Thesaurus and other text fields. See Recreate word indexes.

l Set up document stores. See Document stores.


Page 71 of 80

m Set up Record Types - after you have set up your Record Types, you can begin to create records*. See Chapter 15 - Record Types.

n Set up New Record forms. See Creating New Record forms.

o Set up Additional Fields. See Chapter 28 - Additional Fields.

p Set up Lookup Sets. See Creating Lookup Sets.

q Set up Actions and Procedures. See Chapter 18 - Action tracking.

r Set up Workflow and Workflow Activities. See Chapter 14 - Workflow.

s Set up record Holds. See Chapter 21 - Holds.

t Set up report layouts. See Report layouts.

u Set up Web publisher layouts. See Chapter 24 - Web Publisher.

v Set up barcode scanners. See Chapter 25 - Barcode scanners.

w Set up Space management - the storage space environment that will contain your archived or stored records. See Chapter 27 - Space management.

x Set up electronic document management - desktop integration with other software packages. See Chapter 8 - Electronic document management.

y Set up the user layout options of your HP TRIM interface. See Chapter 33 - Options and Customising and creating toolbars.

HP TRIM is configured. You can now start creating records. See HP TRIM Help topic Creating records.


Page 72 of 80

B Troubleshooting

Troubleshooting the Workgroup Server

Workgroup Server does not start

1 Check login parameters

2 Check Windows event viewer

3 Check the Workgroup Server log files

Crashdump files

When the Workgroup Server experiences a general protection fault, by default, it creates:

• one large .dmp file per crash per hour. You can adjust the frequency by using the registry dword crashdumpfrequency and the value means files per day.

• one small .dmp file per crash

• one log file per crash You can use a registry key to modify the type of data that the large .dmp file includes: HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\HP TRIM\WorkgroupServerConnection with the dword CrashDumpType. The value should be one of the ones listed in this site: http://msdn.microsoft.com/en-us/library/ms680519(VS.85).aspx, for example 0x1227. A Workgroup Server saves the diagnostic files to: C :\Program Files\Hewlett-Packard\HP TRIM\ServerLocalData\Log\<crash-filenumber>.log C :\Program Files\Hewlett-Packard\HP TRIM\ServerLocalData\Log\<crash-filenumber>. dmp A HP TRIM client computer by default, saves crashdump files to: C:\Documents and Settings\<user>\Application Data\Hewlett-Packard\HP TRIM\<dataset ID>\Temp. Contact HP TRIM Software Support to examine the log file to identify the cause of errors.


Page 73 of 80

C Rendering module configuration

Security

Overview

As users may choose to render high security or classified documents, HP Software recommend you use security settings for the printer driver, folders, services and the render monitor. These settings ensure that all documents used with HP TRIM Render are secure from unauthorized access. If you wish to modify the security settings for these elements, please do so in accordance with your IT infrastructure policy.

Securing the print drivers

Follow the process of applying security settings to the driver TRIMRender_PDF. Repeat the process for the driver TRIMRender_TIFF driver.

1 In the Windows Printers dialog box, right-click TRIMRender_PDF

2 Click Properties. The TRIMRender_PDF Properties window appears.

3 Select the Security tab

4 Click Add to add the TRIMServices account and the other Groups/users that need to

administer the printer

5 Click the Advanced button.


Page 74 of 80

The Advanced Security Settings for TRIMRender_PDF window appears.

6 Click Add or Edit. The Select User, Computer, or Group window appears.

7 Select the users, computers or group you want to apply security settings for

8 Click OK. The Permission Entry for TRIMRender_PDF window appears.

9 Make your selections for Apply to and Permissions

10 Click OK

11 In the Advanced Security Settings for TRIMRender_PDF window, choose the settings you require

12 Click OK twice to apply the settings and close the dialog boxes

13 Repeat steps 1-12 for the driver TRIMRender_TIFF

Securing the service and render monitor

You may want to apply additional security settings to comply with the security policy of your organization. You can set up a local Security Group on the server called Render Administrators. Using Group Policy, you can then grant the group access to objects on the server that are locked for unauthorized access. This allows you also to deny the Rendering Administrators Group access to other files on the server.

Remote access

HP TRIM Render runs locally on a server. In case the Rendering Administrators do not have physical access to the server, you need to give them remote access. Apply security settings in accordance with your IT infrastructure policy.


Page 75 of 80

Printing preferences

Overview

The HP TRIM Rendering module uses the Black Ice print driver to render documents into renditions. The drivers come with default settings which may not necessarily suit your needs.

Changing the settings

1 In the Printers and Faxes folder, right-click the TRIMRender_PDF driver and select Properties. The TRIMRender_PDF Properties window appears.

2 Click the button Printing Preferences. The TRIMRender_PDF Printing Preferences window appears.

3 In the Device Settings tab, change the Paper Size settings to suit your needs:

a Select a specific paper size to scale the source document to fit

b Select Variable Paper Size from the drop-down list to render the source document to the same size

c Change the Graphic Resolution settings to suit your needs

d Apply more printing preferences as needed

Using multiple servers

Setup example

All records of Record Type 3 and finalized

1 Using the Select tab, set it to add records that are Finalized

2 Using the Filter tab, set it up to Include only Records of Record Type 3. Rendering Server 1 will add all records of Record Type 3 AND that are finalized to the queue.

All records of Record Type 15 and registered 5 or more days ago

1 Using the Select tab, set it up to add records With Date Registered Older Than 5 days.

2 Using the Filter tab, set it up to Include only Records of Record Type 15. Rendering Server 2 will add all records of Record Type 15 AND that were registered 5 days ago or longer to the queue.


Page 76 of 80

Queuing

The HP TRIM Rendering module maintains only one queue; therefore, all the records the different processors select will be added to the same queue.

Processing

The HP TRIM Rendering module service processes all the records in the queue. It simply selects the next 20 records for processing. There is no filtering at the processing stage. Like in the example above, you may have set up two servers to put specific items in the queue; however, the two or more rendering services that are running will process the next 20 records from the queue respectively, regardless of how they were added to the queue and what criteria they match.

Print verbs

Overview

In a Windows environment, when you right-click a file in Windows Explorer and click Print, the associated application, e.g. XYZ, opens, prints the file and exits, displaying as little as necessary to complete the task. It does so because it invokes the verb print. The HP TRIM Rendering module also invokes the verb print programmatically during the rendering process. When the installed application is not printing .xyz documents correctly and you want to print them using a command other than the default print verb, it may be necessary to manually edit the print verbs in the registry.

Changing a print verb

Warning

Only qualified Administrators should make changes to the registry. Please make a backup of your registry before proceeding. Mistakes changing registry settings can lead to unrecoverable errors and the computer being unusable.

For more information on print verbs and how to print, for example, .xyz files with a different application that has a command line switch for printing, please refer to Microsoft documentation. Depending on your knowledge, this could be a starting point: http://msdn2.microsoft.com/en-us/library/aa969321.aspx#anyfiletype See TRIMRender.chm for information about functionality and operation of the HP TRIM Rendering module.

http://msdn2.microsoft.com/en-us/library/aa969321.aspx#anyfiletype


Page 77 of 80

Troubleshooting

Rendering module output does not appear

When the HP TRIM rendering module fails to render the long-term storage format of documents, it may record the message in the render log file: Error: Printer output file did not appear: [7: printer file failed to appear within timeout] [Info: C:\Users\trimservices\AppData\Local\Hewlett-Packard\HP TRIM\out.pdf]

This is usually due to incorrect print processor configuration. To fix this issue:

1 In the Windows Printers dialog box, right-click TRIMRender_PDF, click Properties. The TRIMRender_PDF Properties window appears.

2 On the Advanced tab, click Print Processor

3 For Print processor, select ColorPlus Print Processor TS and for Default data type, select NT EMF 1.003


Page 78 of 80

D Database and dataset maintenance tasks

Overview

The following steps are recommended to best prepare existing production datasets of HP TRIM versions 5.2, 6.1, 6.2 and 7.x for upgrades, but also for regular maintenance. Not all steps apply to all versions. These instructions are intended for HP TRIM administrators and database administrators. Back up all databases before performing maintenance. If in doubt about a step, contact your regional HP TRIM Support team.

Steps

1 Using HP TRIM Enterprise Manager/Studio depending on your version of TRIM, run an integrity/constraint check on the HP TRIM production dataset. See HP TRIM Enterprise Manager/Studio Help for detailed instructions. If errors are listed at the end of the log file, run the check again with the option Repair… selected. If errors still remain, contact HP TRIM Support for assistance.

2 Use HP TRIM Enterprise Manager/Studio to run a schema repair

3 Use the HP TRIM rich client as an administrator to run a document store integrity check. See HP TRIM Help for detailed steps.

4 If files are missing, the HP TRIM administrator has to decide whether to run it again with the option Repair… selected, which replaces missing files with a textual stub, or find the files from a backup and restore them

5 Clean up the table TSEVENTDAT: Delete from tseventdat where edDateTime < (select min(epLastEventTime) from tseventpro where uri > 0) and uri > 0

This SQL statement removes all processed events and leaves only currently queued events. Ideally, all events have been processed before the upgrade. Quite often, the backlog of this table becomes very large. In HP TRIM 7, this table no longer keeps a record of processed events, and instead deletes them immediately after processing.

6 Clean up the table TSEVENTPRO: DELETE FROM TSEVENTPRO

This SQL statement removes the Event Server configuration. This includes all errant entries not cleared from migrations, i.e. Workgroup or Event Servers that are no longer in use. HP TRIM recreates this table automatically after restarting the HP TRIM services and after using the HP TRIM Enterprise Studio command Deploy.


Page 79 of 80

7 Clean up the table TSURICLAIM: DELETE FROM TSURICLAIM WHERE ucTableId > 0

This SQL statement removes all URI claims, especially those that may be lingering from migrations, i.e. Workgroup or Event Servers that are no longer in use. HP TRIM recreates these URI claims automatically after restarting the HP TRIM services and after using the HP TRIM Enterprise Studio command Deploy and using the particular HP TRIM business object (records, Locations, Schedules, etc).

8 Verify the dataset identifier is correct in the database: SELECT value FROM TSTWRSYS WHERE code = 'DBID'

It should match the production dataset identifier in the HP TRIM Enterprise Manager/Studio dataset properties. If the dataset identifiers do not match, update it: UPDATE TSTWRYS SET value = '<proper DBID>' WHERE code = 'DBID'

9 In preparation to rebuild the word index in HP TRIM 7, manually clear out the indexing tables in the following order:

a DELETE FROM TSLOCWORDA WHERE uri > 0

Deleting from TSLOCWORDA is only necessary for 6.2.x datasets.

b DELETE FROM TSTMWORD WHERE uri > 0

c DELETE FROM TSSCHWORD WHERE uri > 0

d DELETE FROM TSFPWORD WHERE uri > 0

e DELETE FROM TSRECWORD WHERE uri > 0

f DELETE FROM TSINDEXWOR WHERE uri > 0

10 When upgrading, follow the next upgrade steps on page 54 until after the schema upgrade

Additional maintenance after the schema has been upgraded:

11 Using HP TRIM Enterprise Studio, rebuild the word index.

12 Using HP TRIM Enterprise Studio, rebuild the document content index. Because HP TRIM 7 uses new and improved ways of content indexing, this is much easier to create than using an existing one. You can find detailed instructions for rebuilding in HP TRIM Knowledge Base article KM506601. To optimize document content indexing, you can rebuild as a parallel process. You can find detailed instructions for rebuilding in HP TRIM Knowledge Base article KM762544.

If you are migrating HP TRIM to a development/test/staging environment before the production dataset upgrade, please also refer to HP TRIM Knowledge Base article KM762551, which describes steps for migrating a dataset.


Page 80 of 80

64-bit installation, 18

About HP TRIM software, 10

access levels, 4

access permissions, 17, 20, 24, 25, 32, 46, 49

administrative installation, 19, 20, 21, 24

architecture, 10

AutoDeploy. See Automatic Deployment Tool

Automatic deployment tool, 50

Backing up, 66

batch file installation, 24, 59

client. See HP TRIM client

Client Configuration dialog box, 44

configuration options, 61

customer support, 4

Dataset, 12

Default Connection Settings dialog box, 42

Demonstration installation, 17, 19, 29, 32, 38

dialog boxes, 38

Document content index, 12

documentation updates, 3

Electronic document store, 12

e-mail integration, 44

Enterprise Studio. See HP TRIM Enterprise Studio

environment, 16

Group Policy installation, 24

HP TRIM client, 12, 13, 18, 22, 27, 33, 42, 43, 44, 45, 56, 57, 62, 71

HP TRIM Desktop, 28, 44, 45

HP TRIM Enterprise Studio, 18, 26, 50, 54, 55, 69

HP TRIMWatcher, 13

HPTRIM_xNN.msi, 19, 21, 32, 53, 54, 55, 57

installation, 15

installing HP TRIM, 19

Installing under Windows Vista, 7 and Server 2008, 19

integrate HP TRIM, 44

restricted rights, 2 warranty, 2

log file, 63

Log on as a Service, 17

maintenance installation, 35

mixed version, 56

Modify, 37

msi file rules and behavior, 49

Network installation, 18, 20, 21

Novell authentication, 64

Offline Records, 58

prerequisites, 16, 48

Primary Workgroup Server, 43

RDBMS resource allocation and management, 14

related documents, 9

Relational Database Management System (RDBMS) requirements, 14

Remove, 36

Removing HP TRIM, 60

Rendering module, 26, 41, 72, 73, 75, 76, 77

Repair, 36

restricted rights legend, 2

Secondary Workgroup Server, 43

setup steps, 69

support, 4

technical support, 4

TRIM Render. See Rendering module

TRIMPort, 40

TRIMServices, 45, 46, 65

Troubleshooting, 71

Upgrading, 53

warranty, 2

Web client, 11

WebDrawer ISAPI, 41

Workgroup Server, 11