Plan and Prepare

IBM FileNet P8
Version 4.5.1
Plan and Prepare Your Environment for IBM FileNet P8
GC19-2801-00
IBM FileNet P8
Version 4.5.1
Plan and Prepare Your Environment for IBM FileNet P8
GC19-2801-00
Note Before using this information and the product it supports, read the information in Notices on page 251.
This edition applies to version 4.5.1 of IBM FileNet Content Manager (product number 5724-R81), version 4.5.1 of IBM FileNet Business Process Manager (product number 5724-R76), and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2001, 2009. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
ibm.com and related resources . . . . vii
How to send your comments . . . . . . . . vii Contacting IBM. . . . . . . . . . . . . viii Configuring Windows for Enterprise Manager, .NET and COM compatibility clients . . . . . . . . . . . . Configuring Windows for Content Engine on active directory . . . . . . . . Configuring Windows for Process Engine Configuring Windows for Content Search Engine . . . . . . . . . . . . Configuring network . . . . . . . . Prerequisites to configuring your network Synchronizing time and date . . . . Preparing storage areas for object stores . . Configuring file servers for file storage areas . . . . . . . . . . . . Users and groups . . . . . . . . Configuring the remote access protocol on the client machine . . . . . . . . Preparing storage areas to support content search functionality . . . . . . . . Security administrator installation tasks . . . Security planning considerations . . . . Configuring directory server. . . . . . Configuring Windows Active Directory . Configuring Active Directory Lightweight Directory Services (AD LDS). . . . . Configuring Sun Java system directory server . . . . . . . . . . . . Configuring Novell eDirectory . . . . Configuring Oracle Internet Directory . Configuring IBM Tivoli Directory Server. Specifying IBM FileNet P8 accounts . . . Creating Content Engine directory server accounts . . . . . . . . . . . Creating Process Engine directory server accounts . . . . . . . . . . . Creating Application Engine or Workplace XT accounts . . . . . . . . . . Creating accounts for Content Search Engine . . . . . . . . . . . . Database administrator installation tasks . . Creating Content Engine database accounts. Creating Process Engine database accounts . Preparing Microsoft SQL Server . . . . Microsoft SQL Server planning considerations . . . . . . . . . Verifying that Microsoft SQL Server is ready for IBM FileNet P8 . . . . . . Running Process Engine pre-installation scripts (SQL Server) . . . . . . . Configuring Microsoft SQL Server client for Process Engine . . . . . . . . . . Creating the Process Engine ODBC data source and testing the connection . . . Installing Microsoft SQL Server client software for Process Engine . . . . . Preparing Oracle server . . . . . . . . 37 . 37 38 . 40 . 40 41 . 41 . 41 . 43 . 44 . 46 . . . . . 46 47 47 50 51
Planning and preparing for IBM FileNet P8 installation . . . . . . . . . . . . 1

Planning the installation . . . . . . . . . . 1 FileNet P8 Platform sample architecture . . . . 1 Baseline configuration with expansion components. . . . . . . . . . . . . 2 Sample development architecture . . . . . 2 Sample demonstration architecture . . . . . 3 Planning your deployment . . . . . . . . 3 Planning Content Engine deployment . . . . 3 Application server planning considerations . . 4 WebSphere Application Server and WebLogic Server - Content Engine multi-server deployment . . . . . . . 5 JBoss Application Server Content Engine multi-server deployment . . . . . . . 6 Definition of installation roles . . . . . . . 6 Using the installation and upgrade worksheet . . 8 Running the Customize Worksheet macro . . 9 Autofiltering and sorting the Worksheet . . . 9 Performing the required installation preparation tasks. . . . . . . . . . . . . . . . . 10 IT administrator installation tasks . . . . . . 11 Creating Content Engine operating system accounts . . . . . . . . . . . . . 11 Creating Process Engine operating system accounts . . . . . . . . . . . . . 15 Configuring UNIX . . . . . . . . . . 22 Configuring UNIX for IBM FileNet P8 servers (all components) . . . . . . . 23 Configuring Content Engine servers (all UNIX) . . . . . . . . . . . . . 23 Configuring Content Search Engine servers (all UNIX) . . . . . . . . . . . . 24 Configuring Process Engine servers (all UNIX) . . . . . . . . . . . . . 25 Configuring Process Engine servers (AIX) 26 Configuring Process Engine servers (HP-UX) . . . . . . . . . . . . 28 Configuring Process Engine servers (Solaris) . . . . . . . . . . . . 31 Configuring Application Engine (Solaris) 35 Configuring Application Engine or Workplace XT servers (Linux) . . . . . 36 Configuring Application Engine or Workplace XT servers (HP-UX) . . . . . 36 Configuring Microsoft Windows . . . . . 36 Configuring Windows for IBM FileNet P8 servers . . . . . . . . . . . . . 37
. 52 . . . . . 52 53 54 54 55
. 56 . 60 . 61 . . . . . 62 64 65 66 72
. 72 . 73 . 76 . 80 . 80 . 81 . 82
Copyright IBM Corp. 2001, 2009
iii
Oracle planning considerations . . . . . 82 Verifying that Oracle server is installed for IBM FileNet P8 . . . . . . . . . . 83 Running Process Engine pre-installation scripts (Oracle) . . . . . . . . . . 90 Configuring Oracle client for Process Engine 95 Installing the Oracle client . . . . . . 95 Preparing DB2 for z/OS servers . . . . . 96 Verifying that DB2 for z/OS server is installed for IBM FileNet P8 . . . . . . 97 Preparing DB2 for Linux, UNIX and Windows servers . . . . . . . . . . . . . . 99 Verifying that DB2 for Linux, UNIX and Windows is installed for IBM FileNet P8 . 99 Configuring DB2 client . . . . . . . . 105 Installing DB2 client software (Process Engine) . . . . . . . . . . . . 105 Creating DB2 client instances for Process Engine . . . . . . . . . . . . 105 Cataloging the Process Engine DB2 server node . . . . . . . . . . . . . 105 Creating the Process Engine DB2 database alias . . . . . . . . . . . . . 106 Installing the DB2 for z/OS license and modifying the classpath for Content Engine and Process Engine . . . . . . 106 Verifying the ability to connect to the database . . . . . . . . . . . . . 106 Verifying the Process Engine database connection (Oracle) . . . . . . . . 106 Verifying the Process Engine database connection (DB2) . . . . . . . . . 107 Verifying the Process Engine database connection (Microsoft SQL Server) . . . 108 Application Server administrator installation tasks . . . . . . . . . . . . . . . 108 Creating Content Engine application server accounts . . . . . . . . . . . . . 109 Configuring WebSphere for Content Engine 110 Creating the WebSphere profile for Content Engine . . . . . . . . . . 111 Specifying the WebSphere environment variables . . . . . . . . . . . . 111 Setting the primary administrative user name . . . . . . . . . . . . . 113 Setting host aliases for deployment on multiple servers . . . . . . . . . 113 Setting permissions for the Configuration Manager user . . . . . . . . . . 113 Configuring WebLogic Server for Content Engine. . . . . . . . . . . . . . 114 Configuring JBoss Application Server for Content Engine . . . . . . . . . . . 116 Configuring JBoss Application Server clusters . . . . . . . . . . . . 118 Configuring WebSphere Application Server for Application Engine or Workplace XT . . 119 Configuring WebLogic Server for Application Engine or Workplace XT . . . . . . . . 119 Configuring JBoss Application Server for Application Engine or Workplace XT . . . 120
Configuring Process Engine clients for ORB 120 Configuring the documentation server . . . 121
Planning and preparing for IBM FileNet P8 Platform upgrade . . . . . 123

Planning the upgrade . . . . . . . . . . Upgrade overview. . . . . . . . . . . Standard upgrading from version 3.5 or version 4 . . . . . . . . . . . . . Staged upgrading from version 4 only . . . Staged upgrade scenario 1: upgrading Application Engine or Workplace XT first . Staged upgrade scenario 2: upgrading Content Engine first . . . . . . . . Staged upgrade scenario 3: upgrading Process Engine first . . . . . . . . Automatic upgrading of Content Engine . . Upgrading planning considerations . . . . . General requirements for all FileNet P8 Platform systems . . . . . . . . . . FileNet P8 Platform expansion product considerations . . . . . . . . . . . FileNet P8 eForms . . . . . . . . . Content Federation Services . . . . . FileNet Records Manager . . . . . . Third-party vendor software considerations Definition of upgrade roles . . . . . . . . Using the installation and upgrade worksheet Running the Customize Worksheet macro Autofiltering and sorting the Worksheet . . Performing the required upgrade preparation tasks IT administrator upgrade tasks . . . . . . Creating Content Engine operating system accounts for upgrade . . . . . . . . . Configuring UNIX. . . . . . . . . . Configuring UNIX for IBM FileNet P8 Platform servers (all components) . . . Configuring Content Engine servers (all UNIX) . . . . . . . . . . . . . Setting up Java SDK for Content Search Engine . . . . . . . . . . . . Configuring Content Search Engine servers (UNIX) . . . . . . . . . . Configuring Process Engine servers (all UNIX) . . . . . . . . . . . . . Configuring Process Engine servers (AIX) Configuring Process Engine servers (HP-UX) . . . . . . . . . . . . Configuring Process Engine servers (Solaris) . . . . . . . . . . . . Configuring Linux servers for Application Engine or Workplace XT. . . . . . . Configuring Application Engine or Workplace XT servers (HP-UX) . . . . Configuring Microsoft Windows . . . . . Configuring Windows for IBM FileNet P8 Platform servers (all components) . . . Configuring Windows for Enterprise Manager, .NET and COM compatibility clients . . . . . . . . . . . . . 123 123 124 124 125 134 143 150 150 151 152 153 153 153 153 154 155 156 157 157 158 159 159 160 160 161 161 162 164 165 169 173 173 173 174
174
iv
Planning for IBM FileNet P8
Configuring Windows for Content Engine on active directory . . . . . . . . Configuring Windows for Process Engine Configuring Windows for Content Search Engine . . . . . . . . . . . . Configuring network . . . . . . . . . Configuring your network . . . . . . Synchronizing time and date . . . . . Assigning directory permissions for Content Engine upgrade for 4.0 to 4.5 on UNIX . . . . . . . . . . . . . Preparing Process Engine for upgrade . . Security administrator upgrade tasks . . . . Security upgrade planning considerations Specifying IBM FileNet P8 accounts for upgrades . . . . . . . . . . . . . Creating Content Engine directory server accounts . . . . . . . . . . . . Database administrator upgrade tasks . . . . Database administrator planning considerations . . . . . . . . . . . General . . . . . . . . . . . . Oracle . . . . . . . . . . . . . Creating Content Engine database accounts for upgrades from version 3.5 . . . . . . Creating the Content Engine database for the Global Configuration Data (upgrades from 3.5) . . . . . . . . . . . . . . . Preparing DB2 for Linux, UNIX and Windows . . . . . . . . . . . . Preparing Oracle server . . . . . . . Preparing Microsoft SQL Server . . . . Configuring Process Engine Microsoft SQL Server databases . . . . . . . . . . Creating an ODBC data source . . . . Preparing SQL Client . . . . . . . . Installing SQL Server patches and service packs . . . . . . . . . . . . . Application Server administrator upgrade tasks Application server planning considerations (upgrades from 3.5) . . . . . . . . . All platforms . . . . . . . . . . WebSphere and WebLogic - Content Engine multi-server deployment . . . . JBoss Content Engine multi-server deployment . . . . . . . . . . . Application server considerations . . . Creating Content Engine application server accounts for upgrade . . . . . . . . . Configuring the application server for Content Engine (upgrades from 3.5) . . . . Configuring WebSphere for Content Engine . . . . . . . . . . . . Configuring WebLogic Server for Content Engine . . . . . . . . . . . . Configuring JBoss Application Server for Content Engine . . . . . . . . . . Configuring the application server for Content Engine (upgrades from 4.0) . . . . IBM FileNet P8 administrator upgrade tasks . .
175 175 177 178 178 178
Updating Process Engine 3.5 customer applications . . . . . . . . . .
. 213
Appendix A. Installing IBM FileNet P8 Platform in a non-English environment . . . . . . . . . . . . 215

Application Server administrator . . . . . . . Configuring character encoding on WebSphere Application Server . . . . . . . . . . Configuring character encoding (WebLogic Server) . . . . . . . . . . . . . . WebLogic Server . . . . . . . . . . . Security administrator . . . . . . . . . . Extended characters and user names . . . . Database administrator . . . . . . . . . . Installing Microsoft SQL Server . . . . . . Installing Oracle server . . . . . . . . . Installing Oracle client . . . . . . . . NLS_LANG environment variable charset . . . . . . . . . . . . Setting the NLS_LANG variable on Windows . . . . . . . . . . . . UNIX . . . . . . . . . . . . . . Setting the NLS_LANG environment variables . . . . . . . . . . . . Installing the DB2 server . . . . . . . . IT administrator . . . . . . . . . . . . Operating system considerations . . . . . . Microsoft Windows . . . . . . . . . . UNIX . . . . . . . . . . . . . . . Configuring support for other languages in X Windows UNIX system . . . . . . . . Setting the LANG, LC_TIME, and LC_MESSAGES environment variables . . . IBM FileNet P8 administrator . . . . . . . . Process Engine services . . . . . . . . . Configuring Process Task Manager for Application Engine and Workplace XT . . . . Limitations . . . . . . . . . . . . . . 215 215 216 216 216 216 216 217 217 218 218 219 220 220 221 222 222 223 223 223 223 224 224 224 224
179 180 180 181 183 183 189 190 190 191 191
193 193 194 194 195 195 196 196 197 198 198 199 199 199 199 203 203 206 209 212 213
Appendix B. IBM FileNet P8 ports
. . 227
Appendix C. New Content Engine classes and properties . . . . . . . 237

New in Content Engine 4.0.0 (for upgrades 3.5 only) . . . . . . . . . . . . New Content Engine classes in 4.0.0 . . New Content Engine properties in 4.0.0 New in Content Engine 4.5.0 (for upgrades 3.5 and from 4.0) . . . . . . . . . New Content Engine classes in 4.5.0 . . New Content Engine properties in 4.5.0 from . . . . . . from . . . . . . . 237 . 238 . 239 . 246 . 246 . 247
Notices . . . . . . . . . . . . . . 251
Trademarks . . . . . . . . . . . . . . 253
Index . . . . . . . . . . . . . . . 255
Contents
vi
ibm.com and related resources

Product support and documentation are available from ibm.com.
Support and assistance

Product support is available on the Web. Click Support from the product Web site at: FileNet Content Manager Support http://www.ibm.com/software/data/content-management/filenet-contentmanager/support.html
Information center
You can view the product documentation in an Eclipse-based information center that you can install when you install the product. By default, the information center runs in a Web server mode that other Web browsers can access. You can also run it locally on your workstation. See the information center at http://publib.boulder.ibm.com/infocenter/p8docs/v4r5m1/index.jsp.
PDF publications
You can view the PDF files online using the Adobe Acrobat Reader for your operating system. If you do not have the Acrobat Reader installed, you can download it from the Adobe Web site at http://www.adobe.com. See the following PDF publications Web sites:
Product Web site
Product Documentation for FileNet http://www.ibm.com/support/docview.wss?rs=3278 P8 Platform &uid=swg27010422
How to send your comments Your feedback is important in helping to provide the most accurate and highest quality information. Contacting IBM on page viii To contact IBM customer service in the United States or Canada, call 1-800-IBM-SERV (1-800-426-7378).
How to send your comments

Your feedback is important in helping to provide the most accurate and highest quality information. Send your comments by using the online reader comment form at https://www14.software.ibm.com/webapp/iwm/web/signup.do?lang=en_US &source=swg-rcf.
vii
Consumability survey
You are invited to tell IBM how to improve the consumability of software products. If you want to help IBM make IBM FileNet P8 easier to use, take the Consumability Survey at http://www.ibm.com/software/data/info/ consumability-survey/.
Contacting IBM
To contact IBM customer service in the United States or Canada, call 1-800-IBM-SERV (1-800-426-7378). To learn about available service options, call one of the following numbers: v In the United States: 1-888-426-4343 v In Canada: 1-800-465-9600 For more information about how to contact IBM, see the Contact IBM Web site at http://www.ibm.com/contact/us/.
viii
Planning and preparing for IBM FileNet P8 installation

To prepare to install IBM FileNet P8 Platform, you must review the planning information before you begin. You must also complete the prerequisite tasks assigned to the various roles. Planning the installation You must review the installation planning information before your IBM FileNet P8 Platform installation so that you know what kind of deployments are supported, understand how the tasks in the installation tasks are organized by role, and know how to use the Installation and Upgrade Worksheet. Performing the required installation preparation tasks on page 10 To efficiently carry out the required installation preparation tasks, you must assign your staff to carry out the tasks that are organized by administrative role.
Planning the installation

You must review the installation planning information before your IBM FileNet P8 Platform installation so that you know what kind of deployments are supported, understand how the tasks in the installation tasks are organized by role, and know how to use the Installation and Upgrade Worksheet. FileNet P8 Platform sample architecture You can distribute IBM FileNet P8 Platform components and expansion products across a variety of machines. Planning your deployment on page 3 Content Engine, Process Engine, and Application Engine, or Workplace XT, can all be installed as standalone, single instance applications, or as multiple instances with different names on the same server, or in a cluster. Definition of installation roles on page 6 The tasks in this guide and the rows in the Installation and Upgrade Worksheet are organized by administrative roles. Your organization might have different roles, and some of the responsibilities of listed roles will vary from those assigned by default in this documentation. Using the installation and upgrade worksheet on page 8 The Installation and Upgrade Worksheet is a Microsoft Excel spreadsheet (p8_worksheet.xls). The worksheet describes the properties and parameters required to complete IBM FileNet P8 installation, upgrade, and configuration programs, and provides a way to record the values you assign to these properties and parameters.
FileNet P8 Platform sample architecture

You can distribute IBM FileNet P8 Platform components and expansion products across a variety of machines. Baseline configuration with expansion components on page 2 A production environment includes required components plus one or more optional expansion components. Sample development architecture on page 2 To provide an application development configuration, you can install the components that the application is based on and also the required API toolkits on developer workstations.
Sample demonstration architecture on page 3 You can install required and any expansion components on a single server in order to support demonstrations, proof-of-concepts, and single-server development. Because Enterprise Manager runs only on Windows, a single-server installation that includes this administration tool must be on a Windows server.
Baseline configuration with expansion components

A production environment includes required components plus one or more optional expansion components.
Platform components
Expansion components
External client workstation
Process Engine server
Documentation server Content Engine server

CFS, CFS-IS
eForms Designer workstation Image Services server Business Process Framework server Process Analyzer server Rendition Process Engine Simulator server server Business Process Monitor server
Enterprise Manager workstation Client workstation

Ethernet
Application Engine or Workplace XT servers
File storage server
Content Search Engine server Database server
Directory server
Figure 1. Baseline configuration with expansion components
To understand this graphic, keep in mind the following details: v You must set up Content Engine, Application Engine, and the documentation server on application servers. v IBM FileNet P8 Platform supports several different operating systems. However, Enterprise Manager runs only on Windows. v The graphic does not show components in a high availability or clustered configuration. v For information about collocating components on a single server, see IBM FileNet P8 Hardware and Software Requirements. v Not all expansion components are shown, for example IBM FileNet P8 Portlets and Image Services Resource Adapter. Check with your service representative for availability of other expansion products.
Sample development architecture

To provide an application development configuration, you can install the components that the application is based on and also the required API toolkits on developer workstations.
Refer to the IBM FileNet P8 Developer Help topic IBM FileNet P8 Documentation Developer Help Developer Roadmap Introduction for information on setting up your development environment and installing the IBM FileNet P8 API toolkits.
Sample demonstration architecture

You can install required and any expansion components on a single server in order to support demonstrations, proof-of-concepts, and single-server development. Because Enterprise Manager runs only on Windows, a single-server installation that includes this administration tool must be on a Windows server. Installing many FileNet P8 components on the same server is likely to affect system performance. For more information, see the IBM FileNet P8 Hardware and Software Requirements and the IBM FileNet P8 Performance Tuning Guide.
Planning your deployment

Content Engine, Process Engine, and Application Engine, or Workplace XT, can all be installed as standalone, single instance applications, or as multiple instances with different names on the same server, or in a cluster. Planning Content Engine deployment You can deploy Content Engine in either a stand-alone, multi-instance single-server, or cluster environment. Application server planning considerations on page 4 To prepare your application servers, you must carry out certain tasks including create administrative accounts, specifying environmental variables, and making sure your JDBC drivers are at a supported level.
Planning Content Engine deployment

You can deploy Content Engine in either a stand-alone, multi-instance single-server, or cluster environment.
Standalone deployment
When you deploy Content Engine as a standalone application, you configure a single application server. You must configure your Content Engine instances and deploy those Content Engine instances on a single server, using a single directory for the configuration files.
Multi-instance single-server deployment

When you deploy multiple Content Engine instances on a single server, you configure a single application server. Each Content Engine instance is isolated from the others, and there is no exchange of information between the instances. For example, you can dedicate a Content Engine instance for use by the Research and Development department, and you can dedicate a Content Engine instance for use by the Human Resources department. Each instance has its own set of object stores. You will perform all the procedures for each instance on a single server, using a different directory for the configuration files for each instance. It is a best practice to deploy only a single instance into a cluster.
Managed deployment
When you deploy Content Engine in a WebSphere Application Server managed environment, it is a best practice to install and configure Content Engine on the network deployment node to avoid cross-network configuration issues. If you cannot use the network deployment node, install Content Engine on one of the managed nodes. You can then deploy Content Engine to any managed nodes and associated application servers from that node. When you deploy Content Engine in an Oracle WebLogic Server managed environment, it is a best practice to install and configure Content Engine on the administrative node to avoid cross-network configuration issues. If you cannot use the administrative deployment node, install Content Engine on one of the managed nodes. You can then deploy Content Engine to any managed nodes and associated application servers from that node. JBoss Application Server has no managed deployment capability.
Non-managed deployment
When you deploy Content Engine in a WebSphere Application Server non-managed environment, install and configure Content Engine on each server in the environment, creating a distinct EAR file on each server. The contents of the EAR files have comparable configuration information (possibly with different directory paths). When you deploy Content Engine in a JBoss Application Server non-managed environment, install and configure Content Engine on an initial server in the environment, and then copy the Content Engine EAR file from the initial server to the other servers in the environment.
Cluster deployment
Cluster deployments can be used for load balancing or to provide high availability. Refer to the IBM FileNet P8 High Availability Technical Notice for details on how to set up your FileNet P8 system using clusters, farms, and other high availability software and hardware.
Application server planning considerations

To prepare your application servers, you must carry out certain tasks including create administrative accounts, specifying environmental variables, and making sure your JDBC drivers are at a supported level. Content Engine and Application Engine are J2EE application server-based applications. (Process Engine is not.) You must install Content Engine and Application Engine in a homogeneous J2EE environment in which all of your application servers and their version numbers are identical for both components. Assuming that a user application is required for your system and that you have not built or customized one using the IBM FileNet P8 API toolkits, you can install either of the following general user interfaces: v Workplace XT v Application Engine /Workplace
Even if you have your own customized application, it is a best practice to install one of these applications for testing and support purposes. The applications must use Enterprise Java Bean (EJB) transport. If the application server where Content Engine will be deployed is running on a 32-bit JVM, it is a best practice to create no more than 75 Content Engine object stores. On a 64-bit JVM, it is a best practice to create no more than 150 Content Engine object stores. Content Engine is a resource-intensive enterprise application. Running Content Engine and other J2EE applications on the same machine is possible but not a best practice. Other J2EE applications will compete with Content Engine for the same CPU, memory, and disk I/O resources, and increase the complexity of the installation and the risk of the deployment, because configurations will not match what has been qualified by IBM FileNet P8 Engineering. Although you might need to host Content Engine and other applications on the same machine, it is preferable to host Content Engine on its own machine or logical partition. If an architecture requires Content Engine and a non-P8 J2EE application to be on the same machine, be sure to thoroughly test the configuration in your integration environment before deploying them into production. Note the impact of deploying Content Engine on multiple application server nodes. If you intend to deploy Content Engine to multiple server nodes in your production environment, the type of environment will determine how you install Content Engine, as described in: v WebSphere Application Server and WebLogic Server - Content Engine multi-server deployment v JBoss Application Server Content Engine multi-server deployment on page 6 See the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Authentication for reference information about support for EJB and Web Services transports. WebSphere Application Server and WebLogic Server - Content Engine multi-server deployment In an environment of load-balanced or highly-available farmed (or clustered) application servers, you will initially install Content Engine on the Deployment Manager node (IBM WebSphere Application Server) or the Administrator node (WebLogic Server). JBoss Application Server Content Engine multi-server deployment on page 6 JBoss Application Server does not have a central management server. In an environment of multiple physical servers that are farmed or clustered, you will install Content Engine initially on one physical server (using the all instance), and then copy pertinent files and directories to the other servers. WebSphere Application Server and WebLogic Server - Content Engine multi-server deployment: In an environment of load-balanced or highly-available farmed (or clustered) application servers, you will initially install Content Engine on the Deployment Manager node (IBM WebSphere Application Server) or the Administrator node (WebLogic Server). To install Content Engine in centrally managed servers in farms or clusters, see the IBM FileNet P8 High Availability Technical Notice.
Note the impact of deploying centrally managed servers not in farms or clusters. In an environment in which multiple Content Engine instances are geographically dispersed, and where each instance might have its own local Application Engine or Workplace XT server, you will install Content Engine on the Deployment Manager node (WebSphere Application Server) or the Administrator node (WebLogic Server). After installing Content Engine, you will use Configuration Manager to deploy it to other servers. JBoss Application Server Content Engine multi-server deployment: JBoss Application Server does not have a central management server. In an environment of multiple physical servers that are farmed or clustered, you will install Content Engine initially on one physical server (using the all instance), and then copy pertinent files and directories to the other servers. Note the impact of deploying non-managed servers that are farmed or clustered. To install Content Engine in such an environment, see the IBM FileNet P8 High Availability Technical Notice. Note the impact of deploying non-managed servers that are not farmed or clustered. In an environment in which standalone application servers are individually managed and not farmed or clustered, and where the servers are geographically dispersed, you will install Content Engine on each server. Each Content Engine instance will point to the same directory service and GCD database. The data sources you create for each instance will also point to the same object store databases.
Definition of installation roles

The tasks in this guide and the rows in the Installation and Upgrade Worksheet are organized by administrative roles. Your organization might have different roles, and some of the responsibilities of listed roles will vary from those assigned by default in this documentation.
Installation administrator
v Runs IBM FileNet P8 installers during initial setup. v Runs the Configuration Manager tool during initial setup, followed by starting IBM FileNet Enterprise Manager. v Runs IBM FileNet P8 Upgrade programs during upgrades. v Abbreviated as IA. Responsible for coordinating the information described in this worksheet. The information itself will require the input from the other roles. The role of IA is usually filled by an IBM FileNet Certified Professional (FCP).
Information technology administrator

v Responsible for the networking and operating systems settings required by IBM FileNet P8. v Responsible for performing certain security configurations. v Abbreviated as ITA. Responsible for providing the information in the rows in the Installation and Upgrade Worksheet with a value of ITA in the Role column.
Security administrator
v Responsible for configuring the directory servers required by IBM FileNet P8 components, including Content Engine and Application Engine.
v Creates and maintains directory server user and group accounts. v Abbreviated as SA. Responsible for providing the information in the rows in the Installation and Upgrade Worksheet with a value of SA in the Role column.
Database administrator
v Creates, configures, maintains database installations and database or table spaces. v Responsible for creating database accounts needed by IBM FileNet P8. v For purposes of this documentation, the database administrator is expected to have responsibilities regarding the JDBC data sources. v Abbreviated as DBA. Responsible for providing the information in the rows in the Installation and Upgrade Worksheet with a value of DBA in the Role column.
Application server administrator

v Responsible for providing the application servers required by IBM FileNet P8. v Responsible for application server administrative accounts. v Abbreviated as ASA. Responsible for providing the information in the rows in the Installation and Upgrade Worksheet with a value of ASA in the Role column.
IBM FileNet P8 administrator

v This role designation actually refers to the administrator or administrators who perform regular maintenance of Content Engine, Process Engine Application Engine, Workplace or Workplace XT. v The administrator who logs on to Enterprise Manager by using the gcd_admin account or an object_store_admin account is considered an IBM FileNet P8 administrator. v Abbreviated as P8A. Responsible for providing the information in the rows of the Installation and Upgrade Worksheet with a value of P8A in the Role column.
E-mail Administrator
v Creates an e-mail account that will be used to configure the Notification Tab of the Process Task Manager so that Process Engine can send e-mail notifications to end users. (Required only if you use this feature.) v Abbreviated as EA.
Related concepts Using the installation and upgrade worksheet The Installation and Upgrade Worksheet is a Microsoft Excel spreadsheet (p8_worksheet.xls). The worksheet describes the properties and parameters required to complete IBM FileNet P8 installation, upgrade, and configuration programs, and provides a way to record the values you assign to these properties and parameters. IT administrator installation tasks on page 11 The Information Technology administrator must prepare the network and operating systems, and carry out certain security configurations to prepare your environment for IBM FileNet P8 Platform. Security administrator installation tasks on page 47 The Security administrator must prepare the security environment for IBM FileNet P8 Platform, including planning the security environment, configuring the directory server, and creating accounts. Application Server administrator installation tasks on page 108 The Application Server Administrator must prepare the application servers for IBM FileNet P8 Platform, including planning deployment, creating administrative accounts, and configuring JDBC drivers for both Content Engine and Application Engine. Related tasks Database administrator installation tasks on page 64 The Database administrator must prepare the databases required for IBM FileNet P8, including gathering information about data sources, creating databases and database accounts, and installing client software.
Using the installation and upgrade worksheet

The Installation and Upgrade Worksheet is a Microsoft Excel spreadsheet (p8_worksheet.xls). The worksheet describes the properties and parameters required to complete IBM FileNet P8 installation, upgrade, and configuration programs, and provides a way to record the values you assign to these properties and parameters. Administrators who are preparing the environment for installation or upgrade of IBM FileNet P8 components must use the worksheet during their preparation tasks to record the appropriate values and provide them to the Installation Administrator who runs the installation or upgrade programs. Some of the features of the Installation and Upgrade Worksheet are: v Instructions: describes the worksheet and includes a button that runs the Customize Worksheet macro. v The two highlighted columns, Property or Parameter and ENTER YOUR VALUE HERE, provide the simplest view of the requirement. The others add identifying information and help you sort and filter the rows usefully. v The Role column assigns each row to an administrator and uses the following acronyms: ITA: Information Technology Administrator ASA: Application Server Administrator DBA: Database Administrator SA: Security Administrator P8A: IBM FileNet P8 Administrator v Property definitions are contained in the column titled Description.
v Some rows, though not all, contain a hyperlink in the PPG Links column. Click this hyperlink to run a query against the IBM Information Center, which opens with the Search Results pane showing the topics that contain the words in the query phrase. Browse the search results until you have enough information to be able to enter a value in the Worksheet row. Running the Customize Worksheet macro The Customize Worksheet macro lets you extract only those rows that describe your environment. Autofiltering and sorting the Worksheet There are several ways to organize the Worksheet to make finding properties and entering values easier.
Running the Customize Worksheet macro

The Customize Worksheet macro lets you extract only those rows that describe your environment. Important: For support of the full range of built-in filter and macro features, use Microsoft Excel to view the Installation and Upgrade Worksheet file. You can use other spreadsheet programs to view the file; however, filter and macro support can vary. For example, in Calc from OpenOffice.Org, the column filters work as expected, but the Customize Worksheet button does not. To run the Customize Worksheet macro: 1. Open the Installation and Upgrade Worksheet (p8_worksheet.xls) and click the Instructions worksheet (also called a tab). 2. Scroll down until you see the button representing the Customize Worksheet macro. Click the button. 3. Select the components and options that describe the environment you are preparing for IBM FileNet P8. v Installation or Upgrade v FileNet P8 Components v Application Server type Operating system Database type Directory Server type Number of object stores (adds new sets of rows for creating additional data sources) v Name of customized sheet 4. Click OK. The macro copies the rows that fulfill your selection criteria into a new worksheet with the name you entered. Enter the values for your environment into this new worksheet. 5. Click the name of the new worksheet at the bottom of the Excel window. Add your preparation values into this new worksheet. 6. Notice that the new worksheet has buttons at the top titled Show Installer View and Show Full View, depending on its state. The Show Installer View displays only those columns that you need while running installation or configuration programs. v v v v
Autofiltering and sorting the Worksheet

There are several ways to organize the Worksheet to make finding properties and entering values easier.
AutoFiltering is a quick way to display only those rows that meet a certain criteria. To use AutoFilter: 1. Make sure AutoFiltering is enabled. (Select the entire row with the column headers, then click Data Filter Autofilter.) AutoFilter arrows will appear to the right of the column labels. 2. Click the AutoFilter arrow in the Installation or Configuration Program column header and select the program you are interested in (for example, PE installer). 3. Click the AutoFilter arrow in the Setup Type column header, select Custom, and specify Setup Type contains Installation. 4. For a custom AutoFilter, click the AutoFilter in any column header, select Custom, and specify Setup Type contains Installation. 5. To turn off AutoFiltering in a column, click the column AutoFilter arrow and select (All). 6. To reorder rows alphabetically, do a Sort: a. Click anywhere in a column, for example, Column A Role. The only possible values in the Role column are ASA, SA, DBA, ITA, and P8A. Sorting on Role therefore groups the rows by this attribute, in alphabetic order. Several other columns also have a limited number of possible values which means they can be usefully sorted. b. Click the Sort Ascending icon in the Excel toolbar, or use the Data Sort menu command. The rows sort on Role. Sorting the Worksheet reassigns row numbers. If you refer to rows by number, be aware that row numbers change if you change the sort order.
Performing the required installation preparation tasks

To efficiently carry out the required installation preparation tasks, you must assign your staff to carry out the tasks that are organized by administrative role. Some tasks require input that results from other preparation tasks performed by other administrator roles. While performing the tasks, record results in the Installation and Upgrade Worksheet. See the Using the installation and upgrade worksheet on page 8 topic for details. To prepare the IBM FileNet P8 environment, perform the tasks assigned to the following roles. IT administrator installation tasks on page 11 The Information Technology administrator must prepare the network and operating systems, and carry out certain security configurations to prepare your environment for IBM FileNet P8 Platform. Security administrator installation tasks on page 47 The Security administrator must prepare the security environment for IBM FileNet P8 Platform, including planning the security environment, configuring the directory server, and creating accounts. Database administrator installation tasks on page 64 The Database administrator must prepare the databases required for IBM FileNet P8, including gathering information about data sources, creating databases and database accounts, and installing client software. Application Server administrator installation tasks on page 108 The Application Server Administrator must prepare the application servers for
10
IBM FileNet P8 Platform, including planning deployment, creating administrative accounts, and configuring JDBC drivers for both Content Engine and Application Engine.
IT administrator installation tasks

The Information Technology administrator must prepare the network and operating systems, and carry out certain security configurations to prepare your environment for IBM FileNet P8 Platform. v Review all rows assigned to the IT administrator (ITA) in the Using the installation and upgrade worksheet on page 8. While you complete the following preparation tasks, provide values for the rows that are appropriate to your installation. Tip: With the Data Filter AutoFilter command enabled, as it is by default in the shipping worksheet file (p8_worksheet.xls), perform the following actions to quickly see only the properties assigned to a particular role: Click the AutoFilter drop-down arrow in the Role column header and select ITA. Further filter the result set by clicking the AutoFilter drop-down arrow in any of the other columns and selecting a value or clear a filter by selecting All. v If you are installing in a non-English environment, review the considerations and procedures in IBM FileNet P8 Non-English Support Guide before you begin your preparation tasks. Creating Content Engine operating system accounts The IT Administrator must create several operating system accounts required by FileNet P8 components during installation. Creating Process Engine operating system accounts on page 15 Create new or designate existing operating system accounts for Process Engine, as shown in the following table. Configuring UNIX on page 22 The IBM FileNet P8 system components require some specific configuration settings on the UNIX machines where you install them. Configuring Microsoft Windows on page 36 You must perform certain operating system procedures on all Windows-based servers where you will installFileNet P8, including planning for adequate disk and temp space and port requirements, and installing required levels of Microsoft .NET Framework and Web Services Enhancements (WSE). Configuring network on page 40 You must perform certain configurations on the network before installing IBM FileNet P8 Platform. Preparing storage areas for object stores on page 41 To prepare for file storage, you must prepare the locations where file stores will go, configure remote access protocol, and, if you plan to implement content-based retrieval, perform security configurations.
Creating Content Engine operating system accounts

The IT Administrator must create several operating system accounts required by FileNet P8 components during installation. The IT Administrator should perform this task. To create operating system accounts:
11
Create the following users and groups:

User or group name Description
Application Server Installation Administrator: An operating system user account you used (WebSphere Application Server, WebLogic to install your application server. Server, JBoss Application Server): Use your local machines administrative tools ce_appserver_install_user to grant ce_appserver_install_user at least the following permissions: v For Windows, ce_appserver_install_user must be a member of the local administrators group. v For UNIX, ce_appserver_install_user must have read, write, and execute permissions to the Content Engine installation directory. Later in the installation process, the ce_appserver_install_user performs the following tasks: v Create and configure the application server/domain/profile for Content Engine. v Start or stop the application server when needed. v Modify the application server files or directories as needed for deploying the Content Engine application using the Configuration Manager tool. v Provide create, read and write permissions for directories on devices or drives that are used for external Content Engine file storage. ce_appserver_install_user must be a member of the ce_appserver_install_group. Application Server Installation Group: ce_appserver_install_group Create an operating system group account and add to it the following accounts: v ce_appserver_install_user v ce_install_user (Windows) or ce_install_user (UNIX). v config_mgr_user Use the user accounts in ce_appserver_install_group to do the following tasks: v Give operating system privileges to the directories used for the Content Engine Installation and for the application servers instance/domain/profile. v Configure and deploy the Content Engine EAR files which require access to the application servers instance/domain/ profile directories. v Have permissions on devices/drives to read and write that are designated for external Content Engine file storage.
12
User or group name Content Engine Installer (Windows): ce_install_user
Description An operating system account you will use to log on to a machine to launch Content Engine install wizard. ce_install_user can be the same user as the ce_appserver_admin. Use Windows administrative tools to add ce_install_user to the Local Administrators group and to the ce_appserver_install_group.
Content Engine Installer: (UNIX): ce_install_user
An operating system account you will use to log on to a machine to launch Content Engine installer. Use your UNIX administrative tools to grant this account at least the following permissions: v Read, write, and execute permissions to the device or location where: Content Engine is to be installed. The application server instance/domain/profile has been installed. v Write permission to the directories where you will create file storage areas, index areas, and content caches. v Write permission on the /tmp directory. v Membership in the ce_appserver_install_group. ce_install_user can be the same user as the ce_appserver_admin.
Database user name (DB2 for Linux, UNIX and Windows): ce_db_user
Operating system user accounts on the database server. These users are granted database permissions for Content Engine access to the DB2 databases. Use one account for the GCD database (for example, ce_db_user1) and one for each object store database (for example, ce_db_user2, ce_db_user3, and so on). A user can be configured to access multiple object store databases, depending on your installation requirements. Permissions granted by the database administrator determine which object store databases any user can access.
13
User or group name Database user name (DB2 for z/OS):ce_db_user DB2 for z/OS does not allow underscores in account names.
Description Operating system user accounts on the database server. These users are granted database permissions for Content Engine access to the DB2 database. Use one account for the GCD (for example, ce_db_user1) and one for each object store (for example, ce_db_user2, ce_db_user3, and so on) A user can be configured to access multiple object stores, depending on your installation requirements. Permissions granted by the database administrator determine which object store database any user can access.
Accounts required for DB2 for Linux, UNIX and Windows database installation and administration: v Groups: instance owner primary group ce_db_db2_group v Users: instance owner ce_db_db2_ instanceowner Configuration Manager user (WebSphere, WebLogic, JBoss): config_mgr_user
Operating system users and groups that must exist on the database server. The user will create databases and set a number of configuration parameters.
The operating system account you will use to run Configuration Manager. At several points in Plan and Prepare Your Environment for IBM FileNet P8 you will be instructed to grant additional permissions to config_mgr_user, including the following permissions: Add config_mgr_user to the ce_appserver_install_group. (Windows only) Using Active Directory tools, add config_mgr_user to either the Power Users group or the Local Administrators group. At several points in the IBM FileNet P8 Platform Installation and Upgrade Guide you will be instructed to grant additional permissions to config_mgr_user, including the following permissions: v Execute permission to the Configuration Manager tool executable file, configmgr.exe (Windows) or configmgr.sh (UNIX). v Write permission to the directory where the Configuration Manager tool will create the configuration XML files. For example: the directory you specify using the optional -path parameter when you run the tool the default directory, CE_install_path/tools/ configurationmanager/tasks, if you dont specify a path parameter v Read and write permission on the contents of the directory specified by -path parameter, or the default directory.
14
User or group name Content Engine Operating System user: ce_os_user
Description An operating system account you must log on as to create and configure the shared root directory of a file storage area or content cache area. See Preparing storage areas for object stores on page 41. Windows For Windows-based Content Engine and file storage areas, ce_os_user must reside in the same Windows domain or in trusted Windows domains as the servers that host Content Engine and the file storage area. UNIX For UNIX-based Content Engine and file storage areas, configuring security requires the use of NFS.
Creating Process Engine operating system accounts

Create new or designate existing operating system accounts for Process Engine, as shown in the following table. The IT Administrator should perform this task. Create several operating system users and groups for Process Engine. This includes DB2 database users if you are using DB2 as your database. Requirements for database permissions for the DB2 users are documented with tasks related to the DB Administrator. Create the following users and groups:
User or group name The operating system user Process Engine uses to start and stop software (UNIX): fnsw Description This user is an operating system user that is used to start and stop Process Engine software. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation program asks if default users will be used or if aliases for the users will be defined. If a user name other than the default FNSW is defined, indicate to the Process Engine installation program that aliases will be defined. When prompted, provide the fnsw name to the installation program. Assign fnusr as the primary group for the fnsw user. Assign the fnsw user to the following secondary groups: v fnadmin v fnop
15
User or group name The operating system user Process Engine uses to start and stop software and services (Windows): fnsw
Description This user is an operating system user that is used to start and stop Process Engine software and services. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation program asks if default users will be used or if aliases for the users will be defined. If a user name other than the default FNSW is defined, indicate to the Process Engine installation program that aliases will be defined. When prompted, provide the fnsw name to the installation program.Assign the fnsw user to the following groups: v fnusr v fnadmin v fnop v Administrators The Process Engine installation program sets the following policies automatically: v Act as part of the operating system v Adjust memory quotas for a process v Log on as a service v Replace a process level token
The password for the fnsw user (UNIX): fnsw_password
This password is for the fnsw user. Record this value in the Installation and Upgrade Worksheet. This password is for the fnsw user. Record this value in the Installation and Upgrade Worksheet. Process Engine installation program on Windows prompts for the fnsw_password. Leaving the field for the fnsw_password blank during Process Engine installation causes the installation program to set the default password, BPMtemp1pzwd. On Windows the IMS ControlService and Process Engine Services Manager service are configured to start with the fnsw user and the fnsw_password that is entered during Process Engine installation. If this password does not match the operating system password, these services will not start. Set this password to never expire. Process Engine activity ceases if the fnsw_password expires.
The password for the fnsw user (Windows): fnsw_password
16
User or group name An operating system group for Process Engine: fnop
Description This operating system group is a group account for Process Engine whose members have operator non-administrator privileges on Image Services used by Process Engine. Record this value in the Installation and Upgrade Worksheet. Add the fnsw user to this group. The Process Engine installation asks if default users and groups will be used or if aliases will be defined. If a group name other than the default fnop is assigned, indicate to the Process Engine installation program that aliases will be defined and provide this name to the installation program as an alias for the default group.
An operating system group for Process Engine (Windows): fnusr
This operating system group is a group account for Process Engine whose members have non-administrator privileges on Process Engine files and databases. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation asks if default users and groups will be used or if aliases will be defined. fnusr is the default group name. If a group name other than the default is assigned, indicate to the Process Engine installation program that aliases will be defined and provide this name to the installation program as an alias for the fnusr group.Assign the following users to the fnusr group: v fnsw v Administrator
An operating system group for Process Engine (UNIX): fnusr
This operating system group is a group account for Process Engine whose members have non-administrator privileges on Process Engine files and databases. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation asks if default users and groups will be used or if aliases will be defined. fnusr is the default group name. If a group name other than the default is assigned, indicate to the Process Engine installation program that aliases will be defined and provide this name to the installation program as an alias for the fnusr group.Assign the following users to the fnusr group: v fnsw v root v Oracle user oracle
17
User or group name An operating system group for Process Engine (Windows): fnadmin
Description This operating system group is a group account for Process Engine whose members have all privileges on Process Engine files and databases. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation asks if default users and groups will be used or if aliases will be defined. fnadmin is the default group name. If a group name other than the default is assigned, indicate to the Process Engine installation program that aliases will be defined and provide this name to the installation program as an alias for the fmadmin group.Add the following users to this group: v fnsw v Administrator
An operating system group for Process Engine (UNIX): fnadmin
This operating system group is a group account for Process Engine whose members have all privileges on Process Engine files and databases. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation asks if default users and groups will be used or if aliases will be defined. fnadmin is the default group name. If a group name other than the default is assigned, indicate to the Process Engine installation program that aliases will be defined and provide this name to the installation program as an alias for the fmadmin group.Add the following users to this group: v fnsw v root
An operating system group for Process Engine (Windows): pe_install_user
This is a Windows operating system account that can be used to install Process Engine software. This is a Windows administrator for the local machine. This user must also have administrator privileges on the database if you plan to run the database SQL scripts from the Process Engine installation program using OS authentication. You can log in as the local Windows Administrator or create a user (with the specified permissions) expressly for the purpose of running the Process Engine installation program.
18
User or group name An operating system user for Process Engine (UNIX): oracle
Description Create or modify an Oracle user for Process Engine. If the Oracle database is local to Process Engine,this user and the dba group might exist as a result of installing the Oracle software. If the database is remote, define the user and group on the server where Process Engine will be installed. Record this value in the Installation and Upgrade Worksheet to use as the OracleUID for Process Engine installations on UNIX with Oracle databases. Assign the oracle user to the following UNIX groups: Primary dba Secondary fnusr
An operating system group for Process Engine (UNIX):dba
Create or modify an Oracle group for Process Engine. Members of the group act as database administrators Record this value in the Installation and Upgrade Worksheet to use as the OracleGID for Process Engine installations on UNIX with Oracle databases. Assign the oracle user to the dba group
The database runtime user for Process Engine (DB2 for Linux, UNIX and Windows): f_sw
This user is the primary Process Engine DB2 for Linux, UNIX and Windows database run time user and is used only by the Process Engine software to access the DB2 database. For systems using SERVER or SERVER_ENCRYPT authentication, create this user on the database server. For systems using CLIENT authentication, create this user on the Process Engine server. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation program asks if default users will be used or if aliases for the users will be defined. If a user name other than the default f_sw is defined, indicate to the Process Engine installation program that aliases will be defined. When prompted, provide the f_sw name to the installation program. After creating the new users and setting their group memberships, log off as root user, log on as each of the new users, and change the password to avoid connection problems the first time they are used. In a farmed configuration, each Process Engine must have the same run time user name.
19
User or group name The password for the database runtime user for Process Engine (DB2 for Linux, UNIX and Windows): f_sw_password
Description This is the password for the f_sw user. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation program prompts for this password.The password entered during installation will be used to create a file containing an encrypted version of this password. If the encrypted version of the password does not match the operating system version of the password, Process Engine will fail to connect to the database. If the f_sw_password field is left blank during installation, the value will be set to filenet, which is the default.
The database maintenance user for Process Engine (DB2 for Linux, UNIX and Windows): f_maint
This user is the primary database maintenance user for Process Engine with DB2 for Linux, UNIX and Windows and is used only by the Process Engine software to access the DB2 database. For systems using SERVER or SERVER_ENCRYPT authentication, create this user on the database server. For systems using CLIENT authentication, create this user on the Process Engine server. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation program asks if default users will be used or if aliases for the users will be defined. If a user name other than the default f_maint is defined, indicate to the Process Engine installation program that aliases will be defined. When prompted, provide the f_maint name to the installation program. After creating the new users and setting their group memberships, log off as root user, log on as each of the new users, and change the password to avoid connection problems the first time they are used. In a farmed configuration, ensure that each Process Engine has the same run time user name.
20
User or group name The password for the database maintenance user for Process Engine(DB2 for Linux, UNIX and Windows): f_maint_password
Description This is the password for the f_maint user. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation program prompts for this password. The password entered during installation will be used to create a file containing an encrypted version of this password. If the encrypted version of the password does not match the operating system version of the password, Process Engine will fail to connect to the database. If the f_maint_password field is left blank during installation, the value will be set to change$this_obnoxiou$_passwrd, which is the default.
The database instance owner for Process Engine(DB2 for Linux, UNIX and Windows and DB2 for z/OS): instance_owner
This is the instance owner for the Process Engine DB2 database instance. The user will create databases and set a number of configuration parameters. Record this value in the Installation and Upgrade Worksheet. The instance owner is identified when the DB2 database instance is created. It is also identified to the Process Engine installation program. If the database is remote, this is the instance_owner for the client instance on the Process Engine server.
The database runtime user for Process Engine (DB2 for z/OS): f_sw DB2 for z/OS does not allow underscores in account names.
This user is the primary database run time user for Process Engine with DB2 for z/OS. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation program asks if default users will be used or if aliases for the users will be defined. If a user name other than the default f_sw is defined, indicate to the Process Engine installation program that aliases will be defined. When prompted, provide the f_sw name to the installation program. For DB2 for z/OS you must choose to define aliases, because the default value f_sw violates naming rules for that database. This user does not need to have a separate file system for a home directory. After creating the user and setting group memberships, log off as root user, log on as the new user, and change the password to avoid connection problems the first time they are used.
21
User or group name The password for the database runtime user for Process Engine(DB2 for z/OS): f_sw_password
Description This is the password for the f_sw user Record this value in the Installation and Upgrade Worksheet.This is the password for the f_sw user. The Process Engine installation program prompts for this password. The password entered during installation will be used to create a file containing an encrypted version of this password. If the encrypted version of the password does not match the operating system version of the password, Process Engine will fail to connect to the database. This user is the primary database maintenance user for Process Engine with DB2 for z/OS. Record this value in the Installation and Upgrade Worksheet. For DB2 for z/OS you must choose to define aliases, because the default value f_maint violates naming rules for that database. This user does not need to have a separate file system for a home directory. After creating the user and setting group memberships, log off as root user, log on as the new user, and change the password to avoid connection problems the first time they are used.
The database maintenance user for Process Engine(DB2 for z/OS): f_maint DB2 for z/OS does not allow underscores in account names.
The password for the database maintenance user for Process Engine(DB2 for z/OS): f_maint_password
This is the password for the f_maint user. Record this value in the Installation and Upgrade Worksheet. The Process Engine installation program prompts for this password. The password entered during installation is used to create a file containing an encrypted version of this password. If the encrypted version of the password does not match the operating system version of the password, Process Engine will fail to connect to the database.
Configuring UNIX
The IBM FileNet P8 system components require some specific configuration settings on the UNIX machines where you install them. Configuring UNIX for IBM FileNet P8 servers (all components) on page 23 When configuring UNIX ensure the hosts file contents, ensure the minimum require disk and temp space, and determine your port requirements. Configuring Content Engine servers (all UNIX) on page 23 For Content Engine running on a UNIX-based application server, you must use the UNIX utility program umask to set the default file-creation permissions mask for the JVM instance that will host Content Engine server so that the owner (the user running JVM) and the members of the owners group have read, write, and execute access permissions, and all others have no access. Configuring Content Search Engine servers (all UNIX) on page 24 The IBM FileNet P8 Content Search Engine component requires some specific configuration settings on the UNIX machines where you install it.
22
Configuring Process Engine servers (all UNIX) on page 25 The following operating system prerequisites apply to all UNIX-based IBM FileNet P8 Process Engine servers. Configuring Process Engine servers (AIX) on page 26 The following operating system prerequisites apply to AIX IBM FileNet P8 Process Engine servers. Configuring Process Engine servers (HP-UX) on page 28 The following operating system prerequisites apply to HP-UX IBM FileNet P8 Process Engine servers. Configuring Process Engine servers (Solaris) on page 31 The operating system prerequisites in this subsection pertain to Solaris-based Process Engine servers. Configuring Application Engine (Solaris) on page 35 When Solaris starts up, it takes the first several ports, called anon ports, to use for its communication daemons. Configuring Application Engine or Workplace XT servers (Linux) on page 36 To configure Linux-based servers for Application Engine or Workplace XT, you must ensure that Linux libraries are installed. Configuring Application Engine or Workplace XT servers (HP-UX) on page 36 Add an entry to the /etc/nsswitch.conf to enable communication with Process Engine tools. Configuring UNIX for IBM FileNet P8 servers (all components): When configuring UNIX ensure the hosts file contents, ensure the minimum require disk and temp space, and determine your port requirements. To configure UNIX for FileNet P8 Servers: 1. Ensure hosts file contents. On each UNIX-based FileNet P8 server that does not use DNS (Domain Name Service) or NIS (Network Information Service), the /etc/hosts file must contain the name and Internet Protocol (IP) address of all servers it will communicate with, including the remote database server, if applicable. Process Engine has additional requirements for hosts file entries. See Configuring the /etc/hosts file on page 26 for additional information. 2. Ensure minimum required disk space and temp space for installation. See the IBM FileNet P8 4.5 Hardware and Software Requirements guide. 3. Determine port requirements. Consult with the application server, database, and FileNet P8 administrators to determine port requirements for all the servers in your installation environment. 4. If you intend to install FileNet P8 components interactively, ensure that each UNIX-based FileNet P8 server uses the X Window system. And if you are going to install components from a remote machine, verify that the remote machine has an X Window terminal emulator. Configuring Content Engine servers (all UNIX): For Content Engine running on a UNIX-based application server, you must use the UNIX utility program umask to set the default file-creation permissions mask for the JVM instance that will host Content Engine server so that the owner (the user running JVM) and the members of the owners group have read, write, and execute access permissions, and all others have no access.
umask u=rwx,g=rwx,o=
23
This mask setting ensures that the access permissions on files and directories created by Content Engine server are identical to those you must specify when creating file storage areas on UNIX file servers. This umask setting is also required for the user running Content Engine setup (ce_install_user). The umask must be in the .profile file for the user running JVM and also for ce_install_user. Configuring Content Search Engine servers (all UNIX): The IBM FileNet P8 Content Search Engine component requires some specific configuration settings on the UNIX machines where you install it. Important: Ensure that the file compression utilities, gzip and gunzip, are at version 1.3 (or higher) on any UNIX machine where you will install Autonomy K2 locale files. Setting up Java SDK for Content Search Engine Content Search Engine requires Java SDK on UNIX machines where you intend to install additional locales (other than English). Configuring HP-UX servers for Content Search Engine To install Content Search Engine (Autonomy K2) on HP-UX, you must manually configure the kernel with following minimum-value parameters before you begin the Autonomy K2 Master Administration Server installation. Setting up Java SDK for Content Search Engine: Content Search Engine requires Java SDK on UNIX machines where you intend to install additional locales (other than English). To set up Java SDK: On each UNIX machine where you intend to install an additional locale (other than English), complete the following substeps: 1. Install the Java 1.4 SDK. 2. Set the PATH environment variable to install_path/Java14/bin, where install_path is the path to where you installed Java 1.4 SDK. Configuring HP-UX servers for Content Search Engine: To install Content Search Engine (Autonomy K2) on HP-UX, you must manually configure the kernel with following minimum-value parameters before you begin the Autonomy K2 Master Administration Server installation. Tip: Depending on the version of your operating system, some of the following values are not used.
Value maxdsiz maxfiles maxfiles_lim maxssiz max_thread_proc maxswapchunks Setting 1.9 Gbytes (0x7B033000) 2048 2048 160 Mbytes (0xA000000) 1024 8192
24
Value maxtsiz maxuprc maxusers nkthread nproc
Setting 1 Gbyte (0x40000000) 512 128 1024 517
Important: To run Autonomy K2 server software on the HP-UX Itanium PA-RISC emulator for 64-bit and 32-bit applications, you must complete the following steps to work around a resource limitation: Run the following command and then restart the machine: kctune -B pa_maxssiz_32bit=468713472 In the default directory of the user (root) that will own all the Autonomy K2 processes, create a file named .ariesrc containing the following line, terminated by a carriage return:
/ -heap_ssz 360000
Configuring Process Engine servers (all UNIX): The following operating system prerequisites apply to all UNIX-based IBM FileNet P8 Process Engine servers. Configuring UNIX servers for Process Engine Perform the following prerequisite tasks in any order. Configuring the /etc/hosts file on page 26 Information related to Process Engine IP address, server name and optional load balancer must be entered into either the servers DNS table or the hosts file. Configuring UNIX servers for Process Engine: Perform the following prerequisite tasks in any order. (AIX only): Permissions must be set correctly on the /fnsw and /fnsw/local mount points and the file systems before and after mounting the file systems. Solaris volume management software might use port 32776. This is the default for the Process Engine Communication Port (IOR port). To configure UNIX servers: v Ensure minimum /tmp size. The /tmp directory must have 510 MB free. v Save the following files for the root user. .cshrc .Xdefaults .Xresources .dbxinit .dtprofile .env .login
25
.mwmrc .xinitrc .profile v Before installing Process Engine verify that your operating system is set up with a correctly configured volume manager. Process Engine requires the presence of several partitions. You can use the volume manager provided with the operating systems or an equivalent Veritas volume manager.
Volume Name fnsw local Mount Point /fnsw file system /fnsw/local file system Minimum Size 2 GB 10 GB User fnsw fnsw Group fnusr fnusr Mode 775 775
Configuring the /etc/hosts file: Information related to Process Engine IP address, server name and optional load balancer must be entered into either the servers DNS table or the hosts file. For non-farmed configurations, the information can be in either the DNS table or the hosts file on the server. For farmed configurations, the information must be entered into the host file. In a farmed environment, entries must exist for every Process Engine server in the farm. Process Engine can be configured to run with IPv4, IPv6, or a dual stack network. Entries must use the following format for each Process Engine server. The load balancer name must also be associated with the appropriate server in a farmed configuration.
IP_addr hostname load_balancer_name
IP_addr The IP address of the Process Engine server. hostname The corresponding host name, also referred to as the network name. This name must be < 32 characters and cannot contain any dots. Record this value in the Installation and Upgrade Worksheet as the network name and provide it to the Process Engine installation program. load_balancer_name The name of the load balancer in a farmed configuration. In the following example there are IPv4 and IPv6 addresses and cmepwin11 is the hostname (network name). If the server is configured for a dual stack network, both IPv4 and IPv6 entries must exist for the same hostname.
127.0.0.1 localhost ::1 localhost 2007:0:0:0:9:181:124:192 cmepwin11 #fe80::fda2:48f4:7106:2f19%10 cmepwin11 123.45.6.78 cmepwin11
Configuring Process Engine servers (AIX):
26
The following operating system prerequisites apply to AIX IBM FileNet P8 Process Engine servers. Configuring AIX servers for Process Engine Perform the following prerequisite tasks on the AIX server on which Process Engine will be installed. You can perform these tasks in any order. Modifying /etc/rc.dt for AIX 5.3 and 6.1 Configure network ports by modifying /etc/rc.dt. Configuring AIX servers for Process Engine: Perform the following prerequisite tasks on the AIX server on which Process Engine will be installed. You can perform these tasks in any order. To configure AIX servers for Process Engine: v Set the kernel to 64-bit mode. v Set the swap space to 1.5 - 2 times RAM. v Set the Maximum Number of Processes allowed per user to at least 400. v Set the Maximum KB of real memory allowed for MBUFS to 0. Setting the MBUFS parameter to 0 causes the system to use the default amount of available memory. This default amount is approximately 1/8 to 1/4 the amount of real memory. v Set the Maximum Number of FIXED licenses (Num) to a minimum of 16. v Install and commit the following filesets: bos.adt.libm bos.adt.lib bos.adt.base bos.perf.perfstat bos.perf.libperfstat bos.adt.debug v Review and change the time zone parameters if necessary. In SMIT, choose System Environments Change/Show Date and Time Change Time Zone Using System Defined Values. Choose the Daylight Savings Time option if applicable. At the CUT Time Zone menu, choose the option associated with your site. For example, in California, the time zone needs to be set to the Pacific time zone (PST8PDT) Pacific U.S.; Yukon (cut -8). Modifying /etc/rc.dt for AIX 5.3 and 6.1: Configure network ports by modifying /etc/rc.dt. To modify the network ports: 1. As the root user, run the following commands:
/usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no -p -p -p -p -p -p -p -p -o -o -o -o -o -o -o -o tcp_sendspace=16384 tcp_recvspace=16384 tcp_keepidle=80 tcp_keepintvl=20 tcp_ephemeral_high=65535 tcp_ephemeral_low=42767 udp_ephemeral_high=65535 udp_ephemeral_low=42767
This should result in these entries in the /etc/tunables/nextboot file:
27
no: tcp_ephemeral_high = "65535" tcp_ephemeral_low = "42767" tcp_keepidle = "80" tcp_keepintvl = "20" tcp_recvspace = "16384" tcp_sendspace = "16384" udp_ephemeral_high = "65535" udp_ephemeral_low = "42767"
2. If the CDE bundle is installed, the dtlogin daemon may bind to a required port before the kernel parameters listed above take effect. In order to avoid this problem, add the following statements at the beginning of the /etc/rc.dt file:
/usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no -o -o -o -o -o -o -o -o tcp_sendspace=16384 tcp_recvspace=16384 tcp_keepidle=80 tcp_keepintvl=20 tcp_ephemeral_high=65535 tcp_ephemeral_low=42767 udp_ephemeral_high=65535 udp_ephemeral_low=42767
In some circumstances you may need to create an /etc/rc.dt file containing the commands above even if the CDE bundle is not installed. This is indicated by an error message when trying to start Process Engine similar to the following, where myserver is the name of the machine running Process Engine:
Retrying to connect to host 'myserver'... initfnsw: connect() failed with error 'connection refused'! Is TM_daemon running?
3. Restart the server (shutdown -Fr) for these settings to take effect. Executing the commands at the command line is not sufficient. The parameters must be in effect at boot time to avoid bind failures. 4. Check the values by executing the following commands:
no -a | grep ephemeral no -a | grep tcp
5. Check that the ports required by the Process Engine software have not been bound. The following command, entered as a single command line, should not produce any output:
for port in 32768 32769 32770 32771 32772 32773 32774 do netstat -an | grep $port done
Configuring Process Engine servers (HP-UX): The following operating system prerequisites apply to HP-UX IBM FileNet P8 Process Engine servers. Configuring HP-UX servers for Process Engine on page 29 Perform the following prerequisite tasks in any order. Performing symbolic links for X11 libraries on page 29 Create symbolic links for X11 libraries on HP-UX servers Configuring kernel parameters on page 29 Ensure that the following parameters are set to at least the values shown unless otherwise noted. The values are appropriate for both HP PA-RISC and Integrity operating systems unless noted otherwise. These values are sufficient to install and initialize the software but system tuning will be required, specifically for the nfiles and maxfiles parameters.
28
Checking and optionally modifying the timezone settings on page 30 HP-UX has two timezone settings: the kernel parameter timezone and the environment variable TZ. The value of both timezone settings must match. Review and, if necessary, change these settings on all servers. Configuring HP-UX servers for Process Engine: Perform the following prerequisite tasks in any order. To configure HP-UX servers for Process Engine: v On each HP-UX 11 or HP-UX 11i machine where you will install a JVM-based IBM FileNet P8 component (such as Content Engine), or where an associated JVM-based component (such as WebLogic or WebSphere) will run, increase the values of the kernel parameters max_thread_proc (maximum number of threads per process) and nkthread (maximum number of kernel threads in the system) beyond their default values, which are too small for IBM FileNet P8 applications. v Refer to the HP web page Programmers guide for Java 2 HP-UX configuration for Java support for tools to determine values of these two kernel parameters that are sufficient for IBM FileNet P8. v The physical memory must be at least 512 MB. v The kernel must be set to 64-bit mode. v The swap space must be set in the following way: Two times RAM if RAM < 1GB 1.5 times RAM if RAM between 1GB and 2GB Equal to RAM if between 2GB and 8GB .75 times RAM if > 8GB v The /etc/nsswitch.conf file should have the following entry:
hosts: files [NOTFOUND=continue] dns
Performing symbolic links for X11 libraries: Create symbolic links for X11 libraries on HP-UX servers To perform symbolic links for X11 libraries: 1. Log on as the root user. 2. At the prompt, run the following commands:
cd ln ln ln ln ln ln ln ln ln /usr/lib -s /usr/lib/libX11.3 libX11.sl -s /usr/lib/libXIE.2 libXIE.sl -s /usr/lib/libXext.3 libXext.sl -s /usr/lib/libXhp11.3 libXhp11.sl -s /usr/lib/libXi.3 libXi.sl -s /usr/lib/libXm.4 libXm.sl -s /usr/lib/libXp.2 libXp.sl -s /usr/lib/libXt.3 libXt.sl -s /usr/lib/libXtst.2 libXtst.sl
Configuring kernel parameters: Ensure that the following parameters are set to at least the values shown unless otherwise noted. The values are appropriate for both HP PA-RISC and Integrity operating systems unless noted otherwise. These values are sufficient to install and initialize the software but system tuning will be required, specifically for the nfiles and maxfiles parameters.
29
Kernel Parameter maxdsiz maxfiles nproc maxuprc nfile ninode semmns semmni shmmax shmseg semmnu semume msgmni msgseg msgtql msgmap dbc_max_pct
PA-RISC Minimum Setting 0x10000000 or 268435456 (256MB) 512 1005 400 1024 1085 2000 2000 0x10000000 or 268435456 (256MB) 120 1000 500 2048 16384 6640 msgtql + 2 1 to 10 (the value can not be greater than 30) 5 Set appropriately 65535 65535
Minimum Setting on Integrity V2 and V3 unless noted otherwise 0x10000000 or 268435456 (256MB) 1024 1005 400 2048 1085 2000 2000 0x20000000 or 536870912 (512MB) 120 1000 500 2048 16384 (obsolete in HP 11i V3) 6640 msgtql + 2 (obsolete in HP 11i V3 1 to 30 (the value can not be greater than 30) (obsolete in HP 11i V3) 5 (obsolete in HP 11i V3) Set appropriately 65535 65535
dbc_min_pct timezone msgmnb (DB2 only) msgmax (DB2 only)
Checking and optionally modifying the timezone settings: HP-UX has two timezone settings: the kernel parameter timezone and the environment variable TZ. The value of both timezone settings must match. Review and, if necessary, change these settings on all servers. To 1. 2. 3. check the timezone settings: As the root user, enter: sam Select the kernel Configuration option. Select the Configurable Parameters option, then check the Pending Value for the timezone parameter. The default value is 420 minutes west of Greenwich Mean Time (GMT), which is the U.S. Mountain timezone. Determine the number of minutes east or west of GMT for your location by multiplying the number of hours east or west of GMT by 60 minutes per hour. For example, the U.S. Pacific timezone is 8 hours west of GMT. Multiply 8 x 60 to get 480 minutes. If your timezone location is east of GMT, you should use a
30
negative number. For example, Middle European Time is one hour east of GMT. Multiply -1 x 60 to get -60 minutes for MET (Middle European Time). 4. If the Pending Value for the timezone parameter is not correct, change the timezone kernel parameter value: a. Select the timezone parameter by pressing the spacebar and then press Tab to go to Actions menu. b. Select the Modify Configurable Parameter option from the Actions menu and press Return. In the popup window that displays, the Specify New Formula/Value option should already be selected. c. Tab to the Formula/Value field and type the new value. d. Tab to OK and press Return. When the popup window disappears, you should see the new value in the Pending Value column. e. Rebuild the kernel to make your change take effect: 1) Press the F4 key to access the menu bar. 2) From the Action menu, select the Create a New Kernel option using the Arrow keys and press Return. 3) Answer Yes when prompted about creating the kernel now. 4) On the next screen, make sure the Move Kernel into Place and Shutdown/Reboot the System Now option is selected, tab to OK and press the Return key to reboot the system and make the new changes take affect. 5. After the Pending Value for the timezone parameter is correct, enter the following as the root user to check the current value of the TZ environment variable: echo $TZ 6. If the current setting is not correct, enter the following to set the correct timezone: /sbin/set_parms timezone Choose the appropriate timezone from the menus displayed. Remember that the value must match that of the timezone kernel parameter. If you change the current setting, you will be prompted to reboot the server. If the HP-UX set_parms command is not available on your server, the timezone might be set via the SAM interface using the Kernel Parameters option in the same manner that other parameters are set. The System Administrator should consult the HP-UX operating system documentation to determine the appropriate way to set the TZ environment variable. Configuring Process Engine servers (Solaris): The operating system prerequisites in this subsection pertain to Solaris-based Process Engine servers. Enabling ports on page 32 When Solaris starts up, it takes the first several ports, called anon ports, to use for its communication daemons. Verifying national language character set and time settings on page 32 Verify the national language character set and time settings on a Solaris-based Process Engine server. Increasing the operating system kernel limits (Solaris 9) on page 33 Increase or verify Solaris 9 operating system kernel limits before installing Process Engine software. Increasing the operating system kernel limits (Solaris 10) on page 33 Increase or verify Solaris 10 operating system kernel limits before installing Process Engine software.
31
Enabling ports: When Solaris starts up, it takes the first several ports, called anon ports, to use for its communication daemons. By default, the maximum tcp_smallest_anon_port is 32768. IBM FileNet P8 uses several ports higher than 32768. To use these ports on Solaris-based systems, you must first enable the ports by setting the smallest anon port to 32778. By doing so, the ports used by Solaris communication daemons will be 32778 or greater, leaving 32777 available for IBM FileNet P8 use. The Solaris platform provides several different tools, such as the netstat command, to determine if a port is in use. 1. Determine the current tcp_smallest_anon_port setting. From a command prompt, enter the following command: ndd -get /dev/tcp tcp_smallest_anon_port. 2. Enable port 32777. If the port returned in the step above is less than 32778, you must enable port 32777. Solaris 9 Edit the /etc/rc2.d/S69inet file. Add the following line before the exit 0 entry at the bottom of the file:
ndd -set /dev/tcp tcp_smallest_anon_port 32778
Solaris 10 Edit the /lib/svc/method/net-init file. Add the following line before the exit 0 entry at the bottom of the file:
3. Reboot the Process Engineserver to force the release of ports required by Process Engine that might be in use by the operating system. Failure to reboot after these changes are made can result in the port being unavailable, generating OpenSocket errors. Verifying national language character set and time settings: Verify the national language character set and time settings on a Solaris-based Process Engine server. To verify the national language character set and time settings: 1. The default time mask varies on UNIX depending on the LANG and LC_TIME environment settings. Verify the current LC_TIME settings by entering: locale -k t_fmt The result might appear similar to this:
t_fmt=%r
2. The default mask must not be %r. To change to a default mask that can be used with NLT, reset the LC_TIME environment to C, then run the t_fmt=%r command again to verify the change. 3. Modify the default shell environment to use the C time format. 4. Change the /etc/profile for the entire system or change .profile files for each user that runs sh or ksh to include the following lines:
LC_TIME=C export LC_TIME
32
5. Verify the current LANG settings by entering locale at the shell prompt. This example shows the U.S. character set, ISO 8859-1. Be sure it is consistent with the database character set unless your database character set is AL32UTF8 (Unicode).
LANG=en_US.ISO8859-1 LC_CTYPE=en_US.ISO8859-1 LC_NUMERIC=en_US.ISO8859-1 LC_TIME=en_US.ISO8859-1 LC_COLLATE=en_US.ISO8859-1 LC_MONETARY=en_US.ISO8859-1 LC_MESSAGES=en_US.ISO8859-1 LC_ALL=
Increasing the operating system kernel limits (Solaris 9): Increase or verify Solaris 9 operating system kernel limits before installing Process Engine software. To increase the operating system kernel limit: 1. Make a copy of the system file (with a new name). Log on as root, and enter a command similar to the following: cp /etc/system /etc/system.save 2. Edit the /etc/system file, using your preferred editor (for example, vi):
vi /etc/system
3. Ensure that the following parameters are listed and are set to at least the values shown.
set semsys:seminfo_semmap=50 set semsys:seminfo_semmni=2000 set semsys:seminfo_semmns=2000 set semsys:seminfo_semmnu=500 set semsys:seminfo_semmsl=512 set semsys:seminfo_semopm=256 set semsys:seminfo_semume=500 set semsys:seminfo_semvmx=32767 set semsys:seminfo_semaem=16384 set shmsys:shminfo_shmmax=4294967295* set shmsys:shminfo_shmmin=0 set shmsys:shminfo_shmmni=2000 set shmsys:shminfo_shmseg=100 set msgsys:msginfo_msgmni=2048 set max_nprocs=1000 set fnsod:sod_Debug=0 set rlim_fd_max=1024 set rlim_fd_cur=256 noexec_user_stack=1
DB2 also requires these settings:

set msgsys:msginfo_msgmax=65535 set msgsys:msginfo_msgmnb=65536
Increasing the operating system kernel limits (Solaris 10): Increase or verify Solaris 10 operating system kernel limits before installing Process Engine software. The values of the parameters in the project file override the values of the parameters in the /etc/system file. Make sure that the values of the parameters in the project file are the same as or greater than the values of the parameters in the /etc/system file.
33
Solaris 10 provides the Resource Control Facility feature for setting kernel parameters. Refer to the Solaris 10 documentation on the Sun Web site for information about this feature. Kernel parameter changes should be made to the Solaris Resource Control Facility whether or not you are using zones in Solaris 10. In a configuration with zones, make these changes in the global zone. To increase the operating system kernel limits: 1. Log on as fnsw. 2. At a shell prompt enter prctl $$. 3. Verify the values are set to at least the minimum values indicated for Process Engine.
Kernel Parameter max-sem-nsems max-sem-ops max-sem-ids max-shm-ids max-msg-ids max-shm-memory max_nprocs Rlim_fd_max Rlim_fd_cur Noexec_user_stack max-msg-qbytes Msgtql (process.max-msgmessages) Solaris 10 default 512 512 128 128 128 1/4 Physical memory 10 + (16 x maxusers)* 65536 256 0 65536 8192 Solaris 10 for Process Engine 1024 1024 2048 2048 2048 1/4 Physical memory default 65536 256 1 65536 65536
* maxusers - 2048 or server physical memory (in MB), whichever is less. 4. Logged on as the root user, copy the project and the system file.
cp /etc/project /etc/project.save mv /etc/system /etc/system.save
5. View the current settings for the fnsw user, and the Oracle user. For the FileNet software user, enter:
su - fnsw projects -l
For Oracle user, enter:

su - oracle projects -l
6. Return to the user with root privileges. 7. If a project does not exist for the fnsw user, enter the following command to add one:
projadd -U fnsw -K "project.max-shm-memory=(priv,7G,deny)" user.fnsw
8. If a project does exist for the fnsw user, enter the following command:
projmod -sK "project.max-shm-memory=(priv,7G,deny)" user.fnsw
Update other kernel parameters required for the fnsw user in /etc/project, for example:
34
projmod -sK "project.max-shm-ids=(priv,2048,deny)" user.fnsw projmod -sK "project.max-msg-ids=(priv,2048,deny)" user.fnsw projmod -sK "project.max-sem-ids=(priv,2048,deny)" user.fnsw projmod -sK "process.max-msg-messages=(priv,65536,deny)" user.fnsw projmod -sK "process.max-msg-qbytes=(priv,65536,deny)" user.fnsw projadd -U fnsw -K "project.max-shm-memory=(priv,7G,deny)" user.fnsw projmod -sK "project.max-sem-nsems=(priv,1024,deny)" user.fnsw projmod -sK "project.max-sem-ops=(priv,1024,deny)" user.fnsw projmod -sK "project.max-device-locked-memory=(priv,3.9G,deny)" user.fnsw projmod -sK "project.max-shm-ids=(priv,2k,deny)" user.fnsw projmod -sK "process.max-msg-messages=(priv,1.02k,deny)" user.fnsw projmod -sK "process.max-sem-ops=(priv,1k,deny)" user.fnsw projmod -sK "process.max-sem-nsems=(priv,1.02k,deny)" user.fnsw
9. If a project does not exist for the RDBMS software user, such as oracle, enter the following command to create one:
projadd -U oracle -K "project.max-shm-memory=(priv,7G,deny)" user.oracle
10. If a project does exist for the RDBMS user, such as oracle, enter the following command:
projmod -sK "project.max-shm-memory=(priv,7G,deny)" user.oracle
11. Update the following kernel parameters. These changes are not necessary if the value is already set to a higher value.
projmod -sK "project.max-shm-memory=(priv,7G,deny)" user.root projmod -sK "project.max-shm-memory=(priv,7G,deny)" system projmod -sK "project.max-shm-memory=(priv,7G,deny)" default
12. Make a copy of the system file (with a new name):

cp /etc/system /etc/system.save
13. Edit the /etc/system file, using your preferred editor (for example, vi):
vi /etc/system
Add the following value to the file:

set noexec_user_stack=1
14. Exit the file and save your changes. 15. Verify the new active kernel values for both FileNet and Oracle users match the projects -l output you saw in 5 on page 34. For fnsw user, enter:
su - fnsw prctl $$
For Oracle user, enter:

su - oracle prctl $$
16. Verify the /etc/system file by entering:

more /etc/system
Configuring Application Engine (Solaris):
35
When Solaris starts up, it takes the first several ports, called anon ports, to use for its communication daemons. By default, the maximum tcp_smallest_anon_port is 32768. IBM FileNet P8 uses several ports higher than 32768. To use these ports on Solaris-based systems, you must first enable the ports by setting the smallest anon port to 32778. By doing so, the ports used by Solaris communication daemons will be 32778 or greater, leaving 32777 available for IBM FileNet P8 use. The Solaris platform provides several different tools, such as the netstat command, to determine if a port is in use. 1. Determine the current tcp_smallest_anon_port setting. From a command prompt, enter the following command: ndd -get /dev/tcp tcp_smallest_anon_port 2. Enable port 32777. If the port returned in the step above is less than 32778, you must enable port 32777. Solaris 9 Edit the /etc/rc2.d/S69inet file. Add the following line before the exit 0 entry at the bottom of the file:
3. Reboot the Application Engine server to force the release of ports required by the Application Engine that might be in use by the operating system. Failure to reboot after these changes are made can result in the port being unavailable, generating OpenSocket errors. Configuring Application Engine or Workplace XT servers (Linux): To configure Linux-based servers for Application Engine or Workplace XT, you must ensure that Linux libraries are installed. To install Application Engine or Workplace XT on Linux, several legacy libraries are required. You must install the compat-libstdc++ packages on your Red Hat system before beginning your install of Application Engine or Workplace XT. Configuring Application Engine or Workplace XT servers (HP-UX): Add an entry to the /etc/nsswitch.conf to enable communication with Process Engine tools. On each HP-UX 11 or HP-UX 11i machine where you will install Application Engine or Workplace XT, add the following entry to the /etc/nsswitch.conf file:
Configuring Microsoft Windows

You must perform certain operating system procedures on all Windows-based servers where you will installFileNet P8, including planning for adequate disk and temp space and port requirements, and installing required levels of Microsoft .NET Framework and Web Services Enhancements (WSE).
36
Configuring Windows for IBM FileNet P8 servers To configure Windows for IBM FileNet P8 servers, ensure the minimum disk and temporary space and determine the port requirements. Configuring Windows for Enterprise Manager, .NET and COM compatibility clients You must first install Microsoft .NET Framework and Web Services Enhancements (WSE) before you can install .NET API Clients, COM Compatibility clients, or IBM FileNet Enterprise Manager. Configuring Windows for Content Engine on active directory If Windows Active Directory is your directory service, set the primary DNS server IP address on your Content Engine machine to the IP address of the machine where DNS is installed. Configuring Windows for Process Engine on page 38 You must perform certain operating system procedures on all Windows-based servers where you will installProcess Engine, including verifying TCP/IP settings and configuring the hosts file. Configuring Windows for Content Search Engine on page 40 To configure Content Search Engine servers: Configuring Windows for IBM FileNet P8 servers: To configure Windows for IBM FileNet P8 servers, ensure the minimum disk and temporary space and determine the port requirements. To configure Windows for IBM FileNet P8 servers: v Ensure minimum required disk space and temporary space for installation. See IBM FileNet P8 4.5 Hardware and Software Requirements. v Determine port requirements. Consult with the application server, database, and FileNet P8 administrators to determine port requirements for all the servers in your installation environment. Configuring Windows for Enterprise Manager, .NET and COM compatibility clients: You must first install Microsoft .NET Framework and Web Services Enhancements (WSE) before you can install .NET API Clients, COM Compatibility clients, or IBM FileNet Enterprise Manager. To configure Windows for Enterprise Manager, .NET, and COM compatibility clients: On any Windows machine where you are going to install .NET API clients, COM Compatibility clients, or IBM FileNet Enterprise Manager, you must first install the following components: v Microsoft .NET Framework v Web Services Enhancements (WSE) Check the IBM FileNet P8 Hardware and Software Requirements for the latest version requirements of these two components. Enterprise Manager requires no other Content Engine services or files. Configuring Windows for Content Engine on active directory:
37
If Windows Active Directory is your directory service, set the primary DNS server IP address on your Content Engine machine to the IP address of the machine where DNS is installed. Configuring Windows for Process Engine: You must perform certain operating system procedures on all Windows-based servers where you will installProcess Engine, including verifying TCP/IP settings and configuring the hosts file. Verifying TCP/IP parameter settings (Windows) To verify TCP/IP parameter settings, log on as the administrator and run regedit. Adding inbound rules to the Windows 2008 firewall Configure inbound rules in the Windows 2008 firewall to allow the following Process Engine ports access. Configuring the /etc/hosts file Information related to Process Engine IP address, server name and optional load balancer must be entered into either the servers DNS table or the hosts file. Configuring Process Engine clients for ORB (Windows) on page 39 Process Engine clients require either the IBM or the Sun Object Request Broker (ORB). Verifying TCP/IP parameter settings (Windows): To verify TCP/IP parameter settings, log on as the administrator and run regedit. 1. Log on as the Administrator user and run regedit to verify the following registry key values. These values are decimal. The default in Registry Editor is hexadecimal.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ Tcpip\Parameters\MaxUserPort => 65534 (default = 5000) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ Tcpip\Parameters\TcpTimedWaitDelay => 90 (default = 240, or 4 min)
2. If necessary, add or modify a new DWORD value with the values as described above and save the changes. Adding inbound rules to the Windows 2008 firewall: Configure inbound rules in the Windows 2008 firewall to allow the following Process Engine ports access.
Port 32768 32769 32770 Protocol TCP TCP UDP
Configuring the /etc/hosts file: Information related to Process Engine IP address, server name and optional load balancer must be entered into either the servers DNS table or the hosts file.
38
For non-farmed configurations, the information can be in either the DNS table or the hosts file on the server. For farmed configurations, the information must be entered into the host file. In a farmed environment, entries must exist for every Process Engine server in the farm. Process Engine can be configured to run with IPv4, IPv6, or a dual stack network. Entries must use the following format for each Process Engine server. The load balancer name must also be associated with the appropriate server in a farmed configuration.
IP_addr The IP address of the Process Engine server. hostname The corresponding host name, also referred to as the network name. This name must be < 32 characters and cannot contain any dots. Record this value in the Installation and Upgrade Worksheet as the network name and provide it to the Process Engine installation program. load_balancer_name The name of the load balancer in a farmed configuration. In the following example there are IPv4 and IPv6 addresses and cmepwin11 is the hostname (network name). If the server is configured for a dual stack network, both IPv4 and IPv6 entries must exist for the same hostname.
127.0.0.1 localhost ::1 localhost 2007:0:0:0:9:181:124:192 cmepwin11 #fe80::fda2:48f4:7106:2f19%10 cmepwin11 123.45.6.78 cmepwin11
Configuring Process Engine clients for ORB (Windows): Process Engine clients require either the IBM or the Sun Object Request Broker (ORB). This applies to the following configurations: v J2EE application server clients such as Workplace or Workplace XT v Content Engine when using the workflow subscription processor to launch workflows v Non-J2EE or custom applications Therefore, if you have Windows-based non-J2EE or custom applications, configure the Java installation on those servers with either the IBM or the Sun ORB.
Application server IBM WebSphere Application Server with the IBM JVM JBoss Application Server Installed by unzipping binaries with the IBM or the Sun JVM Changes No changes are required. No changes are required.
JBoss Application Server Installed via JEMS No changes are required if you installed the JBoss Enterprise Middleware System Installer JBoss Application Server by installing the with IBM or Sun JVM JBoss Enterprise Middleware Software with the Default option.
39
Application server Oracle WebLogic Server with the Sun JVM WebLogic Server with the JRockit JVM
Changes No changes are required. Replace the default JBoss Application Server ORB with the Sun ORB by adding the following code to your application server startup file. Enter without carriage returns: set JAVA_OPTIONS=%JAVA_OPTIONS% -Dorg.omg.CORBA.ORBClass =com.sun.corba.se.impl.orb.ORBImpl set JAVA_OPTIONS=%JAVA_OPTIONS% -Dorg.omg.CORBA.ORBSingletonClass =com.sun.corba.se.impl.orb.ORBSingleton
Configuring Windows for Content Search Engine: To configure Content Search Engine servers: 1. Set the k2_os_user user as an administrator on each Windows Content Search Engine server. See Specifying IBM FileNet P8 accounts on page 55 for details on creating required users and groups. 2. On each Windows machine where you intend to install an additional locale (other than English), complete the following substeps: a. Install the Java 1.4 SDK. b. Set the PATH environment variable to install_path\Java14\bin, where install_path is the path to where you installed Java 1.4 SDK. 3. Set the JAVA_HOME environment variable on each machine where you will install Content Search Engine software: a. Open the System control panel. b. Click the Advanced tab. c. Click Environment Variables . d. Click New under System Variables. e. Set the variable information in the following way: Variable name: JAV A_HOME Variable value: Java (JDK) install path Important: The Content Search Engine installation program will not allow you proceed until the JAVA_HOME environment variable is set. 4. Set the PATH environment variable in the following way: a. Open the System control panel. b. Click the Advanced tab. c. Click Environment Variables. d. Click PATH under System Variables. e. Append the following variable information: ;%JAVA_HOME%\bin
Configuring network
You must perform certain configurations on the network before installing IBM FileNet P8 Platform. Prerequisites to configuring your network on page 41 Perform the following prerequisite tasks in any order.
40
Synchronizing time and date System users will experience a variety of problems if one or more servers are not synchronized with the rest of the system. Prerequisites to configuring your network: Perform the following prerequisite tasks in any order. v Assign all IBM FileNet P8 servers a static IP address. v Ensure TCP/IP settings. Verify TCP/IP configuration settings on all UNIX and Windows servers and Enterprise Manager clients intended for IBM FileNet P8 so that they can all communicate with one another. v Ensure NetBIOS over TCP/IP is enabled on Windows. v Ensure availability of required port numbers. Several port numbers are required by the various IBM FileNet P8 components. Synchronizing time and date: System users will experience a variety of problems if one or more servers are not synchronized with the rest of the system. The Process Engine database server (the machine that hosts the database used by Process Engine) is considered the master time keeper; the UTC time of that machine is considered the correct time. The server hosting the Process Engine API and the server hosting Content Engine must have the UTC time set. v To change the time on the machine hosting Process Engine, you must stop the server. In a farmed Process Engine system, if you want to change the time of one of the servers in the farm, you must stop only that server. v To change the time in the machine hosting the Process Engine API, be sure it is not connected to any Process Engine system. If the API is connected to a Process Engine server, and you change the time, you will experience authentication errors, and you might need to log on again. v If your Content Engine server is being used with a Process Engine server, and you change the time on the Content Engine server, you will experience authentication errors in Process Engine and you might need to log on again.
Preparing storage areas for object stores

To prepare for file storage, you must prepare the locations where file stores will go, configure remote access protocol, and, if you plan to implement content-based retrieval, perform security configurations. An object store can have up to three types of storage areas for the content of documents and business objects: file storage area A file storage area stores content in a network-accessible directory. The path name to this directory specifies the location of the file storage area. For information about file storage areas, see the IBM FileNet P8 help topic FileNet P8 Administration Content Engine Administration Content storage File storage areas. fixed storage area A fixed storage area is a file storage area on a large-capacity, (possibly) write-once, fixed content device.
41
For information about fixed storage areas, see the IBM FileNet P8 help topic FileNet P8 Administration Content Engine Administration Content storage File storage areas. database storage area A database storage area stores content as binary large objects (BLOBs) in a database. v In this document, file storage area refers only to a network-accessible directory that is not on a fixed content device. v The names of file storage areas and database storage areas must be unique within an object store. v File storage areas on encrypted NTFS devices are not supported. However, the Decru, Vormetrics, and IBM Encryption Expert hardware-based encryption solutions are supported. By default, the Create Object Store wizard creates a database storage area. If your object stores will use database storage areas only, you can skip the rest of this task, provided that one of the following conditions is met: v Your database type is non-DB2. v Your database type is DB2 and your database storage areas will not contain large content elements (larger than 300 MB, for example). Besides creating a database storage area, the Create Object Store wizard allows you to create an initial file storage area or initial fixed storage area. But the wizard requires that you first do at least one of the following, depending on the type of storage areas you want for your object stores: v For fixed storage areas, create at least one fixed content device (typically via Enterprise Manager). Multiple fixed storage areas can share the same fixed content device, or a fixed storage area can have its own fixed content device. If the content of all your object stores will be in fixed storage areas only, create your fixed content devices now, and skip the rest of this topic. To create a fixed content device, refer to the procedures in IBM FileNet P8 help topic FileNet P8 Administration Content Engine Administration Content storage File storage areas. v For file storage areas, prepare locations on one or more file servers (which usually are not a machine where you installed Content Engine), as shown in the remainder of this task. Configuring file servers for file storage areas on page 43 In this section you will configure file servers for the initial file storage areas of the object stores to be created, and for additional file storage areas of existing object stores. Users and groups on page 44 The following table shows the operating system users and groups involved in securing file storage areas. These users and groups must be defined in the directory service that the operating system uses to authenticate users, which is not necessarily the same directory service that Content Engine Server uses. Configuring the remote access protocol on the client machine on page 46 When configuring the remote file access protocol (NFS or CIFS), the client machine is the one where Content Engine Server or Content Search Engine are running. Configuring the remote access protocol (NFS or CIFS) means designating a directory (where content is be stored) so that it appears to be on the a local file system of the client machine.
42
Preparing storage areas to support content search functionality on page 46 To prepare your system for index area creation, each file storage area that will be full-text indexed must be accessible by both the Content Engine the Autonomy K2 server that will perform the full-text indexing. Configuring file servers for file storage areas: In this section you will configure file servers for the initial file storage areas of the object stores to be created, and for additional file storage areas of existing object stores. Refer to the IBM FileNet P8 Hardware and Software Requirements for currently supported operating systems for file servers. Configuring a file server for file storage areas involves the following general steps, which are described in more detail in the procedures later in this task. Ton configure file servers for file storage areas: 1. Create or designate an existing top-level directory on the file server where file storage areas will reside. 2. Secure the directory so only Content Engine Server and Content Search Engine can access it. 3. Expose the directory via the remote file access protocol that applies to the operating system of the file server. 4. (Best practice) Under the top-level directory, create a subdirectory for each file storage area you intend to create. If you decide to put a file storage area directly within a top-level directory, rather than in a subdirectory, and you later decide to create an additional file storage area on this file server, you will have to create another top-level directory for it, because you will not be able to use the previously created top-level directory. Remote file access protocols The supported remote file access protocols between Content Engine and a file server are: Common Internet File System (CIFS), Network File System (NFS), and Distributed File System (DFS). Remote file access protocols: The supported remote file access protocols between Content Engine and a file server are: Common Internet File System (CIFS), Network File System (NFS), and Distributed File System (DFS). DFS is supported if you are using it to manage a file storage area; however, the replication feature of DFS is not supported. For details on setting up a link to DFS, see the IBM FileNet P8 help topic FileNet P8 Administration Content Engine Administration Content storage File storage areas How to...Create DFS link. The communication method between the Content Engine machine and the file server depends on the operating systems running on the two machines, as shown in the following table:
Content Engine Operating System Windows 2003 UNIX File Server Operating System Windows 2003 UNIX File Access Protocol CIFS NFS
43
Content Engine Operating System UNIX
File Server Operating System Windows 2003
File Access Protocol NFS
Install a UPS power supply backup system on each file server to enable graceful shutdown. Loss or corruption of data will result if a file server does not shut down gracefully. Users and groups: The following table shows the operating system users and groups involved in securing file storage areas. These users and groups must be defined in the directory service that the operating system uses to authenticate users, which is not necessarily the same directory service that Content Engine Server uses. The user and group account variables in this table are placeholders for the actual account names that you designate.
Users and Groups Content Engine operating system user (ce_os_user) K2 operating system user (k2_os_user) Role The user under which Content Engine Server runs (typically, the user that starts Content Engine Server). The user under which Content Search Engine runs (typically, the user that starts Content Search Engine). The group in which the Content Engine operating system user and the K2 operating system user are members.
Content Engine operating system group (ce_os_group)
For details on file storage area security, see the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Authorization Storage Area Security. Configuring a UNIX-based file server You need to create a directory and specify permissions for the Content Engine operating system user before you can create a storage area. Configuring a Windows-based file server for a Windows client using CIFS on page 45 You must configure security permissions on the directories where file storage areas are going to be located. Configuring a Windows-based file server for a UNIX client using NFS on page 45 To configure Windows Services for NFS, use the procedures in Microsoft documentation. Configuring a UNIX-based file server: You need to create a directory and specify permissions for the Content Engine operating system user before you can create a storage area. To configure a UNIX-based file server: 1. Log on to the UNIX file server as a user with read/write access to the device where you want to create a storage area.
44
2. Create or designate a directory for the first storage area where content will be stored (as in, fsa1). For example:
$ mkdir /opt/filenet/file_stores/fsa1
3. Set the Content Engine operating system user as the owner of fsa1 and give group access permission to the Content Engine operating system group. For example:
chown ce_os_user:ce_os_group fsa1
Tip: The UID (user ID) for ce_os_user and the GID (group ID) for ce_os_group on the file server must match the UID and GID for the same user and group on the machine where Content Engine and Content Search Engine are running. This will normally be true if all machines use the same directory service, but they might be different. 4. Change the permissions on fsa1 so that ce_os_user and ce_os_group both have read/write/execute privileges and all other users have no privileges:
chmod 0770 fsa1
5. Via NFS, export fsa1. Alternatively, if the file server will host more than one file storage area, export the parent directory. In the latter case, for example, export /opt/filenet/file_stores, rather than /opt/filenet/file_stores/fsa1, and then create a separate subdirectory to serve as the root of each file storage area. Tip: It is a best practice to restrict trusted hosts to just those on which an instance of Content Engine Server or Content Search Engine is executing. Root access should also be restricted. Refer to the UNIX administrator manual for details on exporting files in NFS. Configuring a Windows-based file server for a Windows client using CIFS: You must configure security permissions on the directories where file storage areas are going to be located. To configure a Windows-based file server: 1. Log on to the Windows file server as ce_os_user. 2. Create (or designate) a directory fsa1 where content will be stored. For example:C:\> md c:\filenet\file_stores\fsa1 3. Navigate in Windows Explorer to fsa1, right-click the file icon, and choose Properties. 4. In the Security tab, click Advanced. 5. In the Advanced Security Settings dialog box: a. Grant Full Control to ce_os_user and ce_os_group, and select This Folder, subfolders, and files from the Apply onto drop-down list. b. c. 6. In a. b. Remove all other users and groups in the Permission entries table. Click OK. the Sharing tab, perform the following tasks: Click Share this folder and click Permissions. Grant Full control to ce_os_user and ce_os_group.
c. Remove all other users and groups in the Permission entries table. d. Click OK. Configuring a Windows-based file server for a UNIX client using NFS:
45
To configure Windows Services for NFS, use the procedures in Microsoft documentation. 1. Do all the steps in Configuring a Windows-based file server for a Windows client using CIFS on page 45. 2. Use the procedures in Microsoft documentation to configure Windows Services for NFS to expose fsa1. Tip: v Windows Services for NFS is an optional Windows component bundled with Windows Server 2003 R2. v As part of configuring Windows Services for NFS, you must set up a mapping of Windows users and groups to UNIX users and groups. When setting up the mapping for ce_os_user and ce_os_group, you must specify the same UID (UNIX user ID) and GID (UNIX group ID) that these accounts have on the machine where Content Engine Server is installed. Configuring the remote access protocol on the client machine: When configuring the remote file access protocol (NFS or CIFS), the client machine is the one where Content Engine Server or Content Search Engine are running. Configuring the remote access protocol (NFS or CIFS) means designating a directory (where content is be stored) so that it appears to be on the a local file system of the client machine. To configure remote access protocol: v To configure UNIX-based Content Engine Server to talk to a UNIX or Windows file server via NFS: 1. On the application server where you are going to deploy Content Engine Server, log on as the user who launched the application server. 2. Mount the exported NFS file system (from step 5 on page 45 of Configuring a UNIX-based file server on page 44) onto a local directory on the Content Engine machine. The mount point must be in the same location on all machines where Content Engine Server and Content Search Engine are going to be installed in the local file system. For example:
mount -t nfs filesrv :/opt/filenet/file_stores/home/filenet/file_stores
where filesrv is the host name of Content Engine machine. In this example, all Content Engine Server machines (including machines that are part of the same server farm or cluster) must mount the remote file system at /home/filenet/file_stores. v To configure Windows-based Content Engine Server to talk to a Windows file server via CIFS: 1. If both Content Engine Server and the file server are in the same Windows domain, no action is required. If they are in different domains, establish access to the file server machine from the machine where you will install Content Engine Server before creating the file storage areas. Preparing storage areas to support content search functionality: To prepare your system for index area creation, each file storage area that will be full-text indexed must be accessible by both the Content Engine the Autonomy K2 server that will perform the full-text indexing.
46
Content Engine Operating System User must have permissions to the following directories: v File storage area directories (read and write) v Collections directory (read and write) v Collections temp directory (read and write) K2 Operating System User must have permissions to the following directories: v File storage area directories (read) v Collections directory (read and write) v Collections Temp directory (read and write) If Content Engine and Autonomy K2 are installed on separate machines, then the file store must be mounted and accessible to both the Content Engine and the Autonomy K2 servers. For Windows, the file store path must be a UNC path name accessible to the Autonomy K2 machine. For UNIX, the file store must be NFS-mounted on the Autonomy K2 machine with the same name as it appears on all other machines.
Security administrator installation tasks

The Security administrator must prepare the security environment for IBM FileNet P8 Platform, including planning the security environment, configuring the directory server, and creating accounts. Review all rows assigned to the Security administrator (SA) in the Installation and Upgrade Worksheet. While you complete the following preparation tasks, provide values for the rows that are appropriate to your installation. With the Data Filter AutoFilter command enabled, as it is by default in the shipping worksheet file (p8_worksheet.xls), perform the following actions to quickly see only the properties assigned to a particular Role: v Click the AutoFilter drop-down arrow in the Role column header and select SA. v Further filter the result set by clicking the AutoFilter drop-down arrow in any of the other columns and selecting a value or clear a filter by selecting All. Security planning considerations Information in this section is provided to assist in the security planning process but is not a complete description of any security feature or level of support. Configuring directory server on page 50 The Security administrator must perform certain configurations on the directory server that will provide the authentication repository for your IBM FileNet P8 system. Specifying IBM FileNet P8 accounts on page 55 Included in this topic you will find a set of tables that describe all the accounts you must specify to set up IBM FileNet P8 components.
Security planning considerations

Information in this section is provided to assist in the security planning process but is not a complete description of any security feature or level of support. For complete information about IBM FileNet P8 security, consult the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security. The Security Help sections that are especially applicable to installation are Authentication, Directory Service Providers, and Users and Groups.
47
Authentication and authorization are separate processes. Authentication (logon security) is separate from authorization (object and process security). You must configure your JAAS login on the Content Engine application server so that any user or group that can successfully log on to IBM FileNet P8 resources can also be authorized to work within IBM FileNet P8 interfaces, using the Content Engine directory service provider connection. Configuration Manager captures configuration information to create your application server authentication provider; or you can use an authentication provider that already exists on the application server. Immediately following the initial Content Engine deployment, you will use Enterprise Manager to configure theContent Engine authorization by creating a Directory Configuration. Logins are done through JAAS. IBM FileNet P8 uses Java Authentication and Authorization Service (JAAS) for authentication, which is a process that occurs between a J2EE client application, a J2EE application server, and one or more JAAS login modules. This process does not involve any IBM FileNet P8 code. IBM FileNet P8 Platform uses JAAS for authentication only, not for authorization on stored objects. Also, it does not support Java Security Manager. Determine single sign-on (SSO) requirements. Content Engine ability to use JAAS-based authentication means that if a single sign-on (SSO) provider writes a JAAS LoginModule for a supported application server, then clients of IBM FileNet P8 applications hosted in that application server can use that SSO solution. See Single Sign-On Solutions for IBM FileNet P8 at ibm.com/redbooks for more information. Determine Kerberos applicability. You can use Kerberos for SSO authentication between IBM FileNet Enterprise Manager and Content Engine, provided you use Windows Active Directory as the directory server. See the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Authentication Kerberos for Content Engine. This guide does not provide specific instructions for installing or configuring your SSO provider. For detailed reference information, see the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Authentication. Decide how many authentication realms you require. At least one authentication realm is required, which you create during an initial installation by running Configuration Managers Configure LDAP task. For an explanation of how to configure multiple realms, see the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security How to Configure multiple realms. Make sure that you have a directory service provider in place. Authentication in IBM FileNet P8 Platform is provided by the following supported directory servers: v Microsoft Windows Active Directory v Microsoft Active Directory Lightweight Directory Services (AD LDS, formerly named ADAM)
48
v v v v
Oracle Internet Directory Novell eDirectory Sun Java System Directory Server IBM Tivoli Directory Server
You can find detailed reference information in the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Directory Service Providers. IBM FileNet P8 supports only homogenous directory server environments. In other words, a single IBM FileNet P8 domain can be configured to use only one of the supported directory servers. Understand the users and groups required for IBM FileNet P8. All general administrative users and groups needing access to IBM FileNet P8-based applications must reside in one of the supported directory servers. This Plan and Prepare Your Environment for IBM FileNet P8 provides instructions for creating the administrative accounts required for installation and initial configuration. For detailed reference information, see the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Users and groups. Process Engine delegates authentication to Content Engine. Start with the IBM FileNet P8 Platform 4.0.0 release, Process Engine no longer has a direct connection to a directory server for authentication purposes, as it did in earlier releases. Instead, it delegates authentication tasks to Content Engine. (WebLogic only) Any WebLogic authentication provider must be dedicated to IBM FileNet P8. For performance reasons, do not share any authentication provider used by WebLogic for deployed IBM FileNet P8 components with applications used for other purposes. You can configure Content Engine to use email or UPN for login You can assign the directory servers email attribute or, for Active Directory, the userPrincipalName (UPN) to be the user short name used for login. Instructions in the IBM FileNet P8 Platform Installation and Upgrade Guide provide a link to a procedure that explains how to do this. (WebSphere only) Choose Stand-alone or Federated repository type. There is an option in Configuration Managers Configure LDAP task to select whether the WebSphere Application Server repository type is Stand-alone LDAP registry or Federated repositories. In order to have Configuration Manager use your repository type setting, you must select the Configuration Manager option to Set as current active user registry. If you choose Stand-alone LDAP registry Configuration Manager changes the administrative console user login to the new account you enter as the Administrative console user name (ce_appserver_console_name). This new account must reside in the Stand-alone LDAP registry location. The existing administrative console user login, if any, becomes invalid. In order to have Configuration Manager replace an existing Stand-alone LDAP registry configuration, you must enable the Configuration Manager option Overwrite existing repository.
49
If you choose Federated repositories By choosing the Federated repositories option in Configuration Manager, you are adding a new LDAP realm to an existing Federated LDAP repository. The administrative console user name (ce_appserver_console_name) you provide must be a unique user across all federated realms. Avoid overlapping realm definitions In the Configuration Manager task Configure LDAP, if you set the Websphere Application Server LDAP repository type option to Federated repositories, do not enter repositories with overlapping suffixes as they are not supported. For example, the following two repositories with overlapping Base entry distinguished names are not supported: v dc=ibm,dc=com v dc=filenet,dc=ibm,dc=com This restriction especially applies to Active Directory parent and child domains, since by definition parent/child domains in AD have overlapping suffixes. The repositories in the next example are supported, because they are sibling repositories and do not overlap: v dc=tivoli,dc=ibm,dc=com v dc=filenet,dc=ibm,dc=com Administrative security must be enabled Configuration Manager does not change the state of WebSphere administrative security. If it was on before running Configuration Manager, then it stays on; if it was off before, then it stays off. (Note, however, that Process Engine administrative security must be enabled before starting Content Engine. The IBM FileNet P8 Platform Installation and Upgrade Guide contains steps for enabling WebSpheres administrative security.) For more information on federated LDAP repositories, consult the IBM WebSphere Application Server information center, and search for the keywords federated repositories.
Configuring directory server

The Security administrator must perform certain configurations on the directory server that will provide the authentication repository for your IBM FileNet P8 system. Configuring Windows Active Directory on page 51 Use this task to configure Microsoft Windows Active Directory before you install IBM FileNet P8 Platform. Configuring Active Directory Lightweight Directory Services (AD LDS) on page 52 Use this task to configure Active Directory Lightweight Directory Services (AD LDS) before you install IBM FileNet P8 Platform. Configuring Sun Java system directory server on page 52 Use this task to configure Sun Java System Directory Server on a Windows or UNIX server before you install IBM FileNet P8 Platform. Configuring Novell eDirectory on page 53 Use this task to prepare Novell eDirectory before you install IBM FileNet P8 Platform.
50
Configuring Oracle Internet Directory on page 54 Use this task to prepare Oracle Internet Directory before you install IBM FileNet P8 Platform. Configuring IBM Tivoli Directory Server on page 54 Use this task to prepare IBM Tivoli Directory Serverbefore you install IBM FileNet P8 Platform. Configuring Windows Active Directory: Use this task to configure Microsoft Windows Active Directory before you install IBM FileNet P8 Platform. For a complete list of IBM FileNet P8-supported Windows Active Directory features, refer to FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Directory service providers Windows Active Directory. In a multi-domain Active Directory environment, a logon will fail for any account whose user name and password in a parent/child domain does not match those in a child/parent domain. If you have an Active Directory failover configuration, you can configure IBM FileNet P8 to follow this failover sequence whenever Content Engine attempts to authorize an already authenticated user. You can do this during Content Engine installation while running the Create a Directory Configuration wizard, or at any time after. See FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Directory service providers Windows Active Directory Active Directory failover. Server Side Sorting (SSS) must be enabled. This is because Process Engine and other IBM FileNet P8 components call on Content Engine to perform searches using a sorted paging mechanism. Without SSS, you will experience errors such as in Workplace when retrieving a document, when trying to open Process Designer via Workplace, or when starting a Connection Point on Application Engine. Note that SSS is normally enabled by default but is sometimes disabled due to concerns with performance. DNS forwarders provide external DNS lookup functionality. If you are working in an isolated network, a DNS forwarder is not required. However, if you want to access the Internet or other network resources, then a DNS forwarder pointing to a DNS server that serves the external resources (for example, the Internet) is required. To enable DNS forwarders: 1. On the machine that is configured as the Windows DNS Server, log on with an account that can configure the DNS components. 2. Start DNS. For example, on Windows 2003, choose Start All Programs Administrative Tools DNS . 3. Right-click the your_computer_name container and select Properties. 4. Select the Forwarders tab and verify the check box for Enable forwarders is selected. If this feature is grayed out (unavailable), you must reconfigure your DNS server. 5. If you selected the check box, add an appropriate IP address and click OK. This IP address can be the IP address of a DNS server that allows traffic to the Internet.
51
Configuring Active Directory Lightweight Directory Services (AD LDS): Use this task to configure Active Directory Lightweight Directory Services (AD LDS) before you install IBM FileNet P8 Platform. Server Side Sorting (SSS) must be enabled. This is because Process Engine and other IBM FileNet P8 components call on Content Engine to perform searches using a sorted paging mechanism. Without SSS, you will experience errors such as in Workplace when retrieving a document, when trying to open Process Designer via Workplace, or when starting a Connection Point on Application Engine. Note that SSS is normally enabled by default but is sometimes disabled due to concerns with performance. You can use AD LDS as a standalone directory service, or you can synchronize AD LDS with Active Directory, using Microsofts built-in tools. Synchronization is invisible to IBM FileNet P8 applications and authentication. It is a best practice to establish the connection between Active Directory and AD LDS before installing IBM FileNet P8. Consult your AD LDS documentation for full information. For a complete list of directory server features that IBM FileNet P8 supports, refer to the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Directory Service Providers Windows Active Directory Lightweight Application Mode (AD LDS). Configuring Sun Java system directory server: Use this task to configure Sun Java System Directory Server on a Windows or UNIX server before you install IBM FileNet P8 Platform. On Windows servers, Sun Java System Directory Server should be installed on an NTFS hard drive partition. If there are more than 2,000 users in the Directory Server, you must increase the resource limits to correctly display users in IBM FileNet P8. IBM recommends setting this limit to -1 (unlimited). You can either set this limit for the entire LDAP server or for the individual IBM FileNet P8 users. Server Side Sorting (SSS) must be enabled. This is because Process Engine and other IBM FileNet P8 components call on Content Engine to perform searches using a sorted paging mechanism. Without SSS, you will experience errors such as in Workplace when retrieving a document, when trying to open Process Designer via Workplace, or when starting a Connection Point on Application Engine. Note that SSS is normally enabled by default but is sometimes disabled due to concerns with performance. For a complete list of IBM FileNet P8-supported Sun Java System Directory Server features, refer to the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Directory Service Providers Sun Java System Directory Server. Setting the resource limits for the entire Directory Server (v 5.2) on page 53 User resource limits take precedence over server resource limits. Existing users who have a value specified for resource limits will not be affected by the changes made in the following steps. Setting the resource limits for individual IBM FileNet P8 users on page 53 You must perform these steps any time you add IBM FileNet P8 users.
52
Setting the resource limits for the entire Directory Server (v 5.2): User resource limits take precedence over server resource limits. Existing users who have a value specified for resource limits will not be affected by the changes made in the following steps. To set the resource limits: 1. On the server where Sun Java System Directory Server is installed, log in with an account that has rights to modify the Sun Java System Directory Server environment. 2. Run the Sun Java System Directory Server console and log in. 3. Expand the Domain Server Group containers and select your Directory Server. Right-click and select Open. Select the Configuration tab. Select the Performance container. Select the Client Control tab. For the LDAP group box, ensure that Size limit and Look-through limit are both set to Unlimited. 9. If changes were made, click Save. 10. Select the Tasks tab and Restart the Directory Server if changes were made. 4. 5. 6. 7. 8. Setting the resource limits for individual IBM FileNet P8 users: You must perform these steps any time you add IBM FileNet P8 users. To set the resource limits for individual users: 1. From the Sun Java System Directory Server console, expand the Domain Server Group containers and select your Directory Server. Then click Open. 2. Select the Directory tab. 3. From the left pane, select the Object (OU, etc.) that contains the user(s) you want to change. 4. For each IBM FileNet P8 user whose limit you want to change, complete the following steps: a. From the right pane, double-click on the user name. b. Select Properties. c. On the left pane of the Properties dialog box, select Account. d. Enter -1 in the Look through limit and size limit fields. e. Click OK. 5. Restart the Directory Server. Configuring Novell eDirectory: Use this task to prepare Novell eDirectory before you install IBM FileNet P8 Platform. Make sure to consider the following requirements: v The Windows server where Novell eDirectory Server is installed, must have an NTFS hard drive partition. v The Novell eDirectory administrator might have to create an index if the sorting attribute is not in the list of default attributes shipped by eDirectory.
53
v Access control settings in IBM FileNet P8 require that all users have Browse access on the directory server. If you do not want to set Browse access at the individual user level, it is a best practice to establish a Public trustee for the realm. v IBM FileNet P8 supports cross-realm group memberships. This means that IBM FileNet P8 supports a configuration in which a group is in one realm while some or all of its users are in another. v Server Side Sorting (SSS) must be enabled. This is because Process Engine and other IBM FileNet P8 components call on Content Engine to perform searches using a sorted paging mechanism. Without SSS, you will experience errors such as in Workplace when retrieving a document, when trying to open Process Designer via Workplace, or when starting a Connection Point on Application Engine. Note that SSS is normally enabled by default but is sometimes disabled due to concerns with performance. For a complete list of IBM FileNet P8-supported Novell eDirectory features, refer to the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Directory Service Providers Novell eDirectory. Configuring Oracle Internet Directory: Use this task to prepare Oracle Internet Directory before you install IBM FileNet P8 Platform. Make sure to consider the following requirements: v When installing Oracle Internet Directory (OID) using the Oracle Universal Installer, you must at a minimum select to install the Oracle Internet Directory component. The Oracle Universal Installer will ensure that certain other components that OID requires will also be installed. v If Oracle Internet Directory is installed on a Windows server, it must have an NTFS hard drive partition. v The security administrator might have to create an index if the sorting attribute is not in the list of default attributes shipped by Oracle Internet Directory. v Access control settings in IBM FileNet P8 require that all users have Browse access on the directory server. If you do not want to set Browse access at the individual user level, it is a best practice to establish a Public trustee for the realm. v Server Side Sorting (SSS) must be enabled. This is because Process Engine and other IBM FileNet P8 components call on Content Engine to perform searches using a sorted paging mechanism. Without SSS, you will experience errors such as in Workplace when retrieving a document, when trying to open Process Designer via Workplace, or when starting a Connection Point on Application Engine. Note that SSS is normally enabled by default but is sometimes disabled due to concerns with performance. For a complete list of features supported by IBM FileNet P8, refer to the help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Directory Service Providers Oracle Internet Directory. Configuring IBM Tivoli Directory Server: Use this task to prepare IBM Tivoli Directory Serverbefore you install IBM FileNet P8 Platform.
54
Server Side Sorting (SSS) must be enabled. This is because Process Engine and other IBM FileNet P8 components call on Content Engine to perform searches using a sorted paging mechanism. Without SSS, you will experience errors such as in Workplace when retrieving a document, when trying to open Process Designer via Workplace, or when starting a Connection Point on Application Engine. Note that SSS is normally enabled by default but is sometimes disabled due to concerns with performance. For a complete list of IBM FileNet P8-supported IBM Tivoli Directory Server features, refer to the IBM FileNet P8 Help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Directory Service Providers Tivoli Directory Server.
Specifying IBM FileNet P8 accounts

Included in this topic you will find a set of tables that describe all the accounts you must specify to set up IBM FileNet P8 components. This task assumes that you have completed the tasks required for your directory server in Configuring directory server on page 50. Although these accounts are collected here under the Security administrator tasks because of their relationship to overall system security concerns, you will notice mention of other administrators who are likely to have the actual responsibility to create the accounts and put them to use. The following procedures direct you to create or designate the accounts needed to install and configure IBM FileNet P8. For a complete list of the user and group roles, accounts, and responsibilities required to install, configure, and maintain an IBM FileNet P8 system, see the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Users and groups. Accounts are referred to in documentation in the following ways: v By a display name; for example, Database User Name. An accounts display name is how the IBM FileNet P8 user interface, such as an installation program or dialog box, refers to the account. Many accounts have both a display name and a variable. v By a variable designator; for example ce_db_user, using lower-cased italics and underscores. The variable is intended to show that you must designate your own account to act in the role described by the variable. Accounts that do not appear in an interface or configuration file will have only a variable designator. If you see a reference to an account that you do not understand, search the Plan and Prepare Your Environment for IBM FileNet P8 guide and find the account table that defines it. Creating Content Engine directory server accounts on page 56 Create new or designate existing directory server installation accounts for Content Engine. Creating Process Engine directory server accounts on page 60 Create new or designate existing directory server installation accounts for Process Engine, as shown in the following table. Creating Application Engine or Workplace XT accounts on page 61 Create new or designate existing directory server accounts for Application Engine or Workplace XT.
55
Creating accounts for Content Search Engine on page 62 If you are installing Content Search Engine, you must create new or designate existing Autonomy K2 security accounts. Creating Content Engine directory server accounts: Create new or designate existing directory server installation accounts for Content Engine. The Security Administrator should perform this task. To create directory server accounts: Create the following users and groups:
User or group name Bootstrap user name: ce_bootstrap_admin Description A directory service and application server account that is stored in the CEMPBoot.properties file that is archived in the Content Engine EAR file. Also known as Content Engine System User. Content Engine uses ce_bootstrap_admin to establish a connection with the application server, access the application servers JNDI tree, and look up the data sources for accessing the GCD. You should not use this account as an all-purpose administrative account. For example, if you had to log on to some other application using the ce_bootstrap_admin account and provided the wrong password several times, thereby exceeding the number of allowable login failures, this account could be locked out of the directory server, which would mean that Content Engine would not start. Restriction: If you are deploying Content Engine on an application server with federated user repositories and with multiple realms in your FileNet P8 domain, be sure that no two realms contain the same short name for this user; otherwise, this user will not be able to create the GCD. See the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Users and groups for information on how ce_bootstrap_admin is the account used to create the initial FileNet P8 domain.
56
User or group name GCD Administrator: gcd_admin
Description A directory service account that has Full Control access to the domain object forContent Engine. The initial gcd_admin is created by Configuration Manager using the account entered into its Create Bootstrap Properties panel for the Bootstrap user (ce_bootstrap_admin). Log on as gcd_admin in order to: v Create the GCD by launching the Configure New Domain Permissions wizard the first time you start Enterprise Manager to establish the IBM FileNet P8 domain (see in the IBM FileNet P8 Platform Installation and Upgrade Guide). v Carry out administrative tasks for the FileNet P8 domain. For more information, see the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Users and groups.
Object Store Administrator: object_store_admin, object_store_admin_group
A directory service account that can administer an object store by having Full Control access to it. You can also grant Full Control to an object store to group accounts, thereby making all members of the group object store administrators. Use Enterprise Managers Create an Object Store wizard to specify which user or group accounts should be object_store_admin_group (see inst_ce_create_obj_store in the IBM FileNet P8 Platform Installation and Upgrade Guide). Each object store could have a different set of object store administrators, depending on your security design.
57
User or group name Directory service user: Active Directory (Referred to as Directory service bind user name in Configuration Manager.):ce_service_user
Description An Active Directory user account that Content Engine uses to connect to Active Directory. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific FileNet P8 object after a user has been authenticated. Using Active Directory tools, grant ce_service_user at least the following permissions: v Member of the Pre-Windows 2000 Compatible Access Group in each desired domain in the Active Directory forest. Provide the fully qualified distinguished name of ce_service_user as the directory service bind user name while running Configuration Manager and also when you run the Enterprise Manager Directory Configuration Wizard.
Directory service user: Windows Active Directory Lightweight Directory Services (AD LDS, formerly known as ADAM, referred to as Directory service bind user name in Configuration Manager.): ce_service_user
An AD LDS user account that Content Engine uses to connect to a single Microsoft AD LDS partition. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific FileNet P8 object after a user has been authenticated. Using AD LDS administrative tools, grant ce_service_user at least the following permissions: v Ability to see the other users in the partition. (For a procedure, see the entry for the AD LDS directory service user in FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Users and groups.) Provide the fully qualified distinguished name of ce_service_user as the LDAPBindDN while running Configuration Manager and also when you run theEnterprise Manager Directory Configuration Wizard.
58
User or group name Directory service user: Sun Java System Directory Server (Referred to as Directory service bind user name in Configuration Manager.): ce_service_user
Description A Sun Java System Directory Server user account that Content Engine uses to connect to the Sun Java System Directory server. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific FileNet P8 object after a user has been authenticated. Using Sun Java System Directory Server tools, grant ce_service_user at least the following permissions: v Read v Search v Compare Provide the fully qualified distinguished name of this account as the LDAPBindDN while running the Configuration Manager tool and also when you run theEnterprise Manager Directory Configuration Wizard.
Directory service user: Novell eDirectory (Referred to as Directory service bind user name in Configuration Manager.): ce_service_user
A Novell eDirectory user account that Content Engine uses to connect to Novell eDirectory. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific FileNet P8 object after a user has been authenticated. Using Novell eDirectory tools, grant ce_service_user at least the following permissions: v Read v Compare Provide the fully qualified distinguished name of this account as the LDAPBindDN while running the Configuration Manager tool and also when you run theEnterprise Manager Directory Configuration Wizard.
59
User or group name Directory service user: IBM Tivoli Directory Server (Referred to as Directory service bind user name in Configuration Manager.): ce_service_user
Description An IBM Tivoli Directory Server user account that Content Engine uses to connect to IBM Tivoli Directory Server. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific Workplace object after a user has been authenticated. Using IBM Tivoli Directory Server tools, grant ce_service_user at least the following permissions: v Read v Search v Compare Provide the fully qualified distinguished name of ce_service_user as the LDAPBindDN while running the Configuration Manager tool and also when you run theEnterprise Manager Directory Configuration Wizard.
Directory service user: Oracle Internet Directory (Referred to as Directory service bind user name in Configuration Manager.): ce_service_user
An Oracle Internet Directory user account that Content Engine uses to connect to OID. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific Workplace object after a user has been authenticated. Using Oracle Internet Directory tools, grant ce_service_user at least the following permissions: v Read v Search v Compare Provide the fully qualified distinguished name of ce_service_user as the LDAPBindDN while running the Configuration Manager tool and also when you run theEnterprise Manager Directory Configuration Wizard.
Creating Process Engine directory server accounts: Create new or designate existing directory server installation accounts for Process Engine, as shown in the following table.
60
This task should be performed by the Security Administrator.

User or Group Process Engine service user: pe_service_user Description Process Engine uses the pe_service_user when connecting to the Content Engine server. This user must belong to the Process Engine Administrator group. Record this value in the Installation and Upgrade Worksheet. The name will be required input when configuring the Process Task Manager. Process Engine administrators group: pe_admin_group Members of this group automatically have administrative privileges for Process Engine. Record this value in the Installation and Upgrade Worksheet. The name will be required input when configuring the Process Task Manager. Process Engine configuration group: pe_config_group (Optional) A valid group name. Members of this group automatically have configuration privileges for the Process Engine workflow database. If this group is used to configure security on Process Task Manager, members of this group or of the Process Engine Administrator Group can make configuration changes to the workflow database. If the Process Engine Configuration group is not used during this configuration, anyone can make these changes. Record this value in the Installation and Upgrade Worksheet. The name will be input when configuring the Process Task Manager.
Creating Application Engine or Workplace XT accounts: Create new or designate existing directory server accounts for Application Engine or Workplace XT. This task should be performed by the Application Engine Administrator. To create Application Engine or Workplace XT accounts: Create the following users and groups. All IBM FileNet Workplace accounts, as well as accounts for other client applications and expansion products that use Content Engine or Application Engine, must have passwords.
User or group name Description
Application Engine or Workplace XT installer The account you will use to log on to a account (Windows):ae_install_user, Windows machine and launch the wpxt_install_user Application Engine or Workplace XT installation program. This account must be a Windows Local administrator or a user with equivalent permissions.
61
User or group name
Description
Application Engine or Workplace XT installer The account you will use to log on to a account (UNIX): ae_install_user, UNIX machine and launch the Application wpxt_install_user Engine or Workplace XT installation program. This account must have read/write/execute access to the directory where you will install Application Engine or Workplace XT. Application server account: ae_deploy_user, wpxt_deploy_user This account will have permissions to deploy an application. The account can be the same as the Application Engine or Workplace XT installer account. These accounts will serve in the role of Application Engine administrator. The role applies to both Application Engine or Workplace XT. You will specify these accounts as members of the Application Engine administrator role when you set bootstrap preferences. These accounts must have passwords.
Application Engine Administrators: ae_admin_user, wpxt_admin_user
In addition to the requirements above, the installer account (ae_install_user or wpxt_install_user) and the Application server account (ae_deploy_user or wpxt_deploy_user) and need read/write/execute permission to these directories and files: Installation paths Grant ae_install_user read and write permission to the ae_install_path. Grant wpxt_install_user read and write permission to the wpxt_install_path. WebSphere Application Server WAS_HOME/profiles/default/installedApps/node_name/ app_engine_war.ear/app_engine.war WAS_HOME/profiles/default/config/cells/machine_name/Node01cell/ nodes/machine_name/Node01/serverindex.xml WebLogic 9.x BEA_Home/bea/user_projects/domains/domain_name/bin/startWebLogic.sh or startWebLogic.cmd BEA_home/bea/user_projects/domains/domain_name/config/config.xml WebLogic 10.x BEA_Home/bea/wlserver_10.0/server/bin/startWLS.sh or start WLS.cmd BEA_home/bea/user_projects/domains/domain_name/config/config.xml JBoss JBOSS_home/bin/run.sh or run.bat JBOSS_home/server/default/conf/login-config.xml (on both Content Engine and Application Engine servers) Creating accounts for Content Search Engine: If you are installing Content Search Engine, you must create new or designate existing Autonomy K2 security accounts. The IT Administrator should perform this task. To create accounts for Content Search Engine:
62
Create the following users and groups:

User or group name K2 Security Group: k2_sec_group Description Autonomy K2 security group used to secure K2 collections. Later, you will specify this group in the User Group field of the Verity Domain Configuration tab when you configure CBR in the Enterprise Manager root domain property sheet. Windows Active Directory group when Autonomy K2 is installed on a machine in a Windows domain. Windows local group when Autonomy K2 is installed on a machine in a Windows workgroup. UNIX K2 Security User: k2_sec_user UNIX operating system group.
Autonomy K2 security user account, used by Content Engine when logging onto the Autonomy K2 Master Administration Server to perform Content-Based Retrieval (CBR). Later, you will specify this account in the Verity Username field in the Verity Domain Configuration when you configure CBR in Enterprise Manager. This user must be a member of the k2_sec_group and must be defined as an authorized K2 administrator in the K2 dashboard. The k2_sec_user and k2_os_user can be the same user. All permissions listed for both users must be assigned. Windows services will run as this user. This user must be given administrator privileges for Windows on all machines on which the Autonomy K2 software will be installed. UNIX processes will run as this user. k2_os_user can be an unprivileged user; however, the vspget process must run as the root user. (The IBM FileNet P8 Platform Installation and Upgrade Guide explains how to do this.) This user also requires read/write permissions to the K2 collections directory, the collections temp directory and to the file system that contains the file storage areas and full-text index collections. The Autonomy K2 software needs to read the file storage areas and write the full text index collections as part of the full text indexing operation.
K2 Operating System User: k2_os_user
63
Database administrator installation tasks

The Database administrator must prepare the databases required for IBM FileNet P8, including gathering information about data sources, creating databases and database accounts, and installing client software. v Review all rows assigned to the Database administrator (DBA) in the Installation and Upgrade Worksheet. While you complete the following preparation tasks, provide values for the rows that are appropriate to your installation. (Your organization might have different roles, and some of the responsibilities of listed roles will vary from those assigned by default in this documentation.) Tip: With the Data Filter AutoFilter command enabled, as it is by default in the shipping worksheet file (p8_worksheet.xls), perform the following actions to quickly see only the properties assigned to a particular Role: Click the AutoFilter drop-down arrow in the Role column header and select DBA. Further filter the result set by clicking the AutoFilter drop-down arrow in any of the other columns and selecting a value or clear a filter by selecting (All). As an alternative, you can use the Customize Worksheet filtering macro, embedded in the worksheet files Instructions tab. v If you are installing in a non-English environment, review the considerations and procedures in Appendix A, Installing IBM FileNet P8 Platform in a non-English environment, on page 215 before you begin your preparation tasks. Creating Content Engine database accounts on page 65 Use your database tools to create new or designate existing database accounts for Content Engine, as shown in the following table. After the IT Administrator creates operating system users and groups for DB2 databases, you must grant database permissions. Creating Process Engine database accounts on page 66 You must create new or designate existing database accounts for Process Engine. Preparing Microsoft SQL Server on page 72 Plan the SQL Server installation and configuration, install the software, and configure database components for IBM FileNet P8 components after reviewing the requirements. Configuring Microsoft SQL Server client for Process Engine on page 80 To configure your database clients for Process Engine, you must create ODBC data sources and, if required, install Microsoft SQL Server Client software for Process Engine. Preparing Oracle server on page 82 To prepare your Oracle databases, you must install the database software, and configure database components for IBM FileNet P8. Configuring Oracle client for Process Engine on page 95 Install the Oracle Client software to prepare for the installation of Process Engine. Content Engine does not require installation of Oracle Client software. Preparing DB2 for z/OS servers on page 96 Plan the DB2 for z/OS installation and configuration, install the software, and configure database components for IBM FileNet P8 components. Preparing DB2 for Linux, UNIX and Windows servers on page 99 Plan and prepare your IBM DB2 for Linux, UNIX and Windows servers for IBM FileNet P8 installation.
64
Configuring DB2 client on page 105 Configure the DB2 client. Configuration requirements will be different for Content Engine and Process Engine and will vary between DB2 for Linux, UNIX and Windows and DB2 for z/OS. Verifying the ability to connect to the database on page 106 Verify the ability to connect to the Process Engine database. These procedures can be run after initial configuration of the database and immediately prior to installation of Process Engine software. Run these steps on the database server or the client according to whether the database is local to or remote from Process Engine.
Creating Content Engine database accounts

Use your database tools to create new or designate existing database accounts for Content Engine, as shown in the following table. After the IT Administrator creates operating system users and groups for DB2 databases, you must grant database permissions. The database administrator should perform this task. To create database accounts: Create the following users and groups:
User or group name Database user name (Microsoft SQL Server):ce_db_user Description The database accounts that Content Engine uses to access SQL Server, depending on whether you use one account for all Content Engine databases, or use one (for example, ce_db_user ) for the GCD database and different accounts for each object store (for example, ce_db_user1 , ce_db_user2 , and so on). ce_db_user should be a SQL Server account. It does not have to be an account in the configured directory service. Grant each ce_db_user at least the following database access permissions: v public v db_owner Add these accounts to SQL Servers master database and grant the public role to each. When you perform the procedure Configuring the JDBC distributed transaction components on page 76, these accounts will also be granted the SqlJDBCXAUser role.
65
User or group name Database user name (Oracle): ce_db_user
Description The tablespace owner accounts that Content Engine uses to access Oracle. Use one account for each object store tablespace and one for the GCD tablespace. Grant each ce_db_user at least the following permissions: v CREATE SESSION v CREATE TABLE v CREATE SEQUENCE (object store tablespaces only) v SELECT on pending_trans$ v SELECT on dba_2pc_pending v SELECT on dba_pending_transactions v EXECUTE on dbms_system
Database user name (DB2 for Linux, UNIX and Windows): ce_db_user
Grant the following database permissions to this user: v Connect to the database v Create tables in the tablespace (CREATETAB) v Use the tablespace (USE OF) for User and User Temp tablespaces
Database user name (DB2 for z/OS):ce_db_user DB2 for z/OS does not allow underscores in account names.
Grant the following database permissions to this user: v GRANT SYSADM TO ce_db_user v GRANT USE OF STOGROUP storagegroupname TO ce_db_user v GRANT USE OF BUFFERPOOL BP32K TO ce_db_user v GRANT SELECT ON SYSCAT.DATATYPES TO ce_db_user v GRANT SELECT ON SYSIBM.SYSVERSIONS TO ce_db_user where: ce_db_user is the operating system user name created for the CE database user. storagegroupname is the name of the storage groupUse one account for the GCD (for example, ce_db_user1) and one for each object store (for example, ce_db_user2, ce_db_user3, and so on).
Creating Process Engine database accounts

You must create new or designate existing database accounts for Process Engine. The Database Administrator should perform this task. After the IT Administrator creates operating system users and groups for DB2 databases, you must grant database permissions. You create database users on
66
Oracle and SQL Server databases for Process Engine by running SQL scripts. The scripts create default user names and passwords, or they can be edited to change the user names and passwords for your installation. Database permissions are also granted from the SQL scripts. Create the following users and groups:
User or group name The database runtime user for Process Engine (DB2 for Linux, UNIX and Windows): f_sw Description Grant the following database permissions to this user if you are using SERVER and SERVER_ENCRYPT authentication: v permission to connect v permission to create tables in the tablespaces (CREATETAB) v permission to use the tablespaces (USE OF) Grant SYSADM permission to this user if you are using CLIENT authentication. The password for the database runtime user for Process Engine (DB2 for Linux, UNIX and Windows): f_sw_password This is the password for the f_sw user. The Process Engine installation program prompts for this password.The password entered during installation will be used to create a file containing an encrypted version of this password. If the encrypted version of the password does not match the operating system version of the password, Process Engine will be unable to connect to the database. If the f_sw_password field is left blank during installation, the value will be set to filenet, which is the default.
67
User or group name
Description
The database maintenance user for Process This user is the primary Process Engine DB2 Engine (DB2 for Linux, UNIX and for Linux, UNIX and Windows database Windows): f_maint maintenance user and is used only by the Process Engine software to access the DB2 database. For a database using SERVER or SERVER_ENCRYPT authentication for the Process Engine database, this user: v Is recommended to be member of group having SYSADM authority of the DB2 instance that will be used by the Process Engine software v Does not need to have separate file systems for a home directory v Must belong to the primary group of the instance owner Grant SYSADM permission to this user if you are using CLIENT authentication. After creating the new users and setting their group memberships, log off as root user, log on as each of the new users, and change the password to avoid connection problems the first time theyre used. In a farmed configuration, ensure that each Process Engine has the same run time user name. This is the password for the f_maint user. The password for the database rmaintenance user for Process Engine (DB2 The Process Engine installation program for Linux, UNIX and Windows): prompts for this password. f_maint_password The password entered during installation will be used to create a file containing an encrypted version of this password. If the encrypted version of the password does not match the operating system version of the password, Process Engine will be unable to connect to the database. If the f_maint_password field is left blank during installation, the value will be set to change$this_obnoxiou$_passwrd, which is the default. The database instance owner for Process Engine (DB2 for Linux, UNIX and Windows and DB2 for z/OS): instance_owner This is the instance owner for the Process Engine DB2 for Linux, UNIX and Windows database instance. The instance owner is identified when the DB2 database instance is created. It is also identified to the Process Engineinstallation program.
68
User or group name The database runtime user for Process Engine (DB2 for z/OS): f_sw DB2 for z/OS does not allow underscores in account names.
Description This user is the primary Process Engine DB2 for z/OS database run time userThis Process Engine user is: v Used only by the Process Engine software to access the DB2 database. v Must have DBADM authority of the DB2 instance that will be used by the Process Engine software. Grant the following permissions to each user you created: v GRANT DBADM ON DATABASE databasename TO operatingsystemuser; v GRANT USE OF STOGROUP storagegroupname TO operatingsystemuser; v GRANT USE OF BUFFERPOOL BP8K TO operatingsystemuser; where: databasename is the name of the Process Engine database. operatingsystemuser is the name of the operating system user, f_sw storagegroupname is the name of the storage group assigned to the Process Engine database.
The password for the database runtime user for Process Engine (DB2 for z/OS): f_sw_password DB2 for z/OS does not allow underscores in account names.
This is the password for the f_sw userThis is the password for the f_sw user. The Process Engine installation program prompts for this password. The password entered during installation will be used to create a file containing an encrypted version of this password. If the encrypted version of the password does not match the operating system version of the password, Process Engine will be unable to connect to the database.
69
User or group name
Description
The database maintenance user for Process This Process Engine user is: Engine (DB2 for z/OS): f_maint v Mainly used by the customer for database maintenance DB2 for z/OS does not allow underscores v Recommended to have DBADM authority of in account names. the DB2 instance that will be used by the Process Engine software. v The Process Engine database maintenance user. Grant the following permissions to each user you created: v GRANT DBADM ON DATABASE databasename TO operatingsystemuser; v GRANT USE OF STOGROUP storagegroupname TO operatingsystemuser; v GRANT USE OF BUFFERPOOL BP8K TO operatingsystemuser; where: databasename is the name of the Process Engine database. operatingsystemuser is the name of the operating system user, f_maint storagegroupname is the name of the storage group assigned to the Process Engine database. The password for the database maintenance user for Process Engine (DB2 for z/OS):f_maint_password DB2 for z/OS does not allow underscores in account names. This is the password for the f_maint user. The Process Engine installation program prompts for this password. The password entered during installation will be used to create a file containing an encrypted version of this password. If the encrypted version of the password does not match the operating system version of the password, Process Engine will be unable to connect to the database. The database runtime user for Process Engine. The user is defined when the pe_filenet_site.sql script runs. The default value is set to f_sw. The script can be edited to change the user name. Record the value for this user in the Installation and Upgrade Worksheet.
The database runtime user for Process Engine (Oracle): f_sw
70
User or group name The password for the database runtime user for Process Engine (Oracle): f_sw_password
Description The database runtime users password for Process Engine. The password is set when the pe_filenet_site.sql and pe_install_scripts.sql script runs. The default value is set to filenet. The script can be edited to change the password. Record the value for this user in the Installation and Upgrade Worksheet.
The database maintenance user for Process The database maintenance user for Process Engine (Oracle): f_maint Engine. The user is defined when the pe_filenet_site.sql script runs. The default value is set to f_maint. The script can be edited to change the user name. Record the value for this user in the Installation and Upgrade Worksheet. The password for the database maintenance user for Process Engine (Oracle): f_maint_password The database maintenance users password for Process Engine. The password is set when the pe_filenet_site.sql and pe_install_scripts.sql script runs. The default value is set to change$this_obnoxiou$_password. The script can be edited to change the password. Record the value for this user in the Installation and Upgrade Worksheet. The database runtime user for Process Engine (SQL Server): f_sw The database runtime user for Process Engine. The user is defined when the CreatePEinstallSP_1.sql script runs. The default value is set to f_sw. The script can be edited to change the user name. Record the value for this user in the Installation and Upgrade Worksheet. The password for the database runtime user for Process Engine (SQL Server): f_sw_password The database runtime users password for Process Engine. The password is set when the CreatePEinstallSP_1.sql script runs. The default value is set to filenet. The script can be edited to change the password. Record the value for this user in the Installation and Upgrade Worksheet. The database maintenance user for Process The database maintenance user for Process Engine (SQL Server): f_maint Engine. The user is defined when the CreatePEinstallSP_1.sql script runs. The default value is set to f_maint. The script can be edited to change the user name. Record the value for this user in the Installation and Upgrade Worksheet.
71
User or group name The password for the database maintenance user for Process Engine (SQL Server): f_maint_password
Description The database maintenance users password for Process Engine. The password is set when the CreatePEinstallSP_1.sql script runs. The default value is set to change$this_obnoxiou$_password. The script can be edited to change the password. Record the value for this user in the Installation and Upgrade Worksheet.
Preparing Microsoft SQL Server

Plan the SQL Server installation and configuration, install the software, and configure database components for IBM FileNet P8 components after reviewing the requirements. Microsoft SQL Server planning considerations Determine whether Microsoft SQL Server database components will be dedicated to individual IBM FileNet P8 components or shared, and whether the database will be local or remote, after reviewing the requirements Verifying that Microsoft SQL Server is ready for IBM FileNet P8 on page 73 To prepare your databases before installing IBM FileNet P8, you must install the SQL Server software and configure the database components for your installation. Running Process Engine pre-installation scripts (SQL Server) on page 76 Run SQL scripts to create Process Engine database users, passwords, and stored procedures. Microsoft SQL Server planning considerations: Determine whether Microsoft SQL Server database components will be dedicated to individual IBM FileNet P8 components or shared, and whether the database will be local or remote, after reviewing the requirements In a shared configuration, the IBM FileNet P8 components use the same instance. In a dedicated configuration, Content Engine, Process Engine, and Rendition Engine use separate instances. The following components can optionally share a SQL Server instance: v Content Engine (object store databases and GCD database) v Process Engine v Rendition Engine Process Engine and the optional Process Analyzer cannot share an instance. For information aboutSQL Server requirements for Process Analyzer Engine, see the IBM FileNet Process Analyzer Installation and Upgrade Guide SQL Server databases can be dedicated or shared by one or more of the following IBM FileNet P8 components: v Dedicated to Content Engine v Dedicated to Process Engine v Shared by two or more of Content Engine, Process Engine, and Rendition Engine v Shared with other applications
72
A database should not be shared by multiple Content Engine object stores. Backup and support activities are simplified if each object store has a separate database. For a SQL Server database dedicated to Rendition Engine, see the IBM FileNet Rendition Engine Installation and Upgrade Guide. A database is local if it is on a server where you will also be installing Content Engine, Process Engine, or Rendition Engine. A database is remote if it is on a separate server from the component that uses that database. Process Engine requires an ODBC data source for connection to the SQL Server database whether the database is local or remote. See Configuring Microsoft SQL Server client for Process Engine on page 80 for details on configuring the data source. Determine when to run SQL scripts for Process Engine. You must run a number of SQL scripts to create a stored procedures. These stored procedures are then used to create database users and other stored procedures required for Process Engine production. The Process Engine installation program will complete only if all these scripts run successfully. Run the scripts manually, before starting Process Engine installation, or run them from the Process Engine installation program. See Running Process Engine pre-installation scripts (SQL Server) on page 76 for information about execution modes and associated security requirements. If you run these scripts from the Process Engine installation program, install the SQL Server client software on the Process Engine Determine the maximum size of the content elements your users store. The size affects setting up database storage areas or file storage areas. When you create an object store, a database storage area is provided by default where you can store content as database BLOBs. You can also create one or more file storage areas to store content on local or remote file systems. If your users store large individual documents or other content elements, use only file storage areas. Otherwise, users can encounter memory-related errors when retrieving or indexing the large content. Controlled tests with limited concurrency exhibited errors when run with files that were 300 MB or larger. Factors affecting this file-size limitation include driver and application server memory demands, other activity such as concurrent retrieval, indexing of large content, and JVM memory allocations. Verifying that Microsoft SQL Server is ready for IBM FileNet P8: To prepare your databases before installing IBM FileNet P8, you must install the SQL Server software and configure the database components for your installation. Installing and configuring Microsoft SQL Server on page 74 Install and configure SQL Server software and create database instances for Content Engine and Process Engine. Creating a Microsoft SQL Server database for the GCD on page 75 Create a Microsoft SQL Server database for the GCD database, which is required for Content Engine installation. Creating a Microsoft SQL Server database for Content Engine object stores on page 75 Create a Microsoft SQL Server database for a Content Engine object store. Each object store you create requires an empty database. Create the database with an initial size of 200 MB minimum. Creating a Microsoft SQL Server database for Process Engine on page 75 Create a Microsoft SQL Server database and filegroup for Process Engine.
73
Modifying the tempdb database for Process Engine on page 75 Verify that the space allocated for the tempdb is at least 80 MB and that the collation settings match the Process Engine database. Enabling XA transactions on page 75 Configure the Windows server to enable XA transactions. Configuring the JDBC distributed transaction components on page 76 Run these steps to enable XA transactions on every Microsoft SQL Server that will have a Content Engine database. Installing and configuring Microsoft SQL Server: Install and configure SQL Server software and create database instances for Content Engine and Process Engine. Create and configure one or more database instances using these requirements. 1. Create one or more database instances for use by IBM FileNet P8 software or verify that such instances already exist. 2. If you create a new instance, indicate an appropriate name based on whether Content Engine (object store), GCD, Process Engine, or Rendition Engine will use the instance. 3. Verify that the authentication mode is Mixed Mode. 4. Select the database collation settings: Choose one of the following from the collation options: v Dictionary order, case-insensitive, for use with 1252 Character Set (or any case-insensitive SQL Server collation). Case-insensitive collation is the Microsoft default and the setting most used in IBM FileNet P8 environments (because it offers search results without regard to character case). v Dictionary order, case sensitive, for use with 1252 Character Set (or any case-sensitive SQL Server collation). Select case-sensitive SQL Server collation only if your site requires (and will continue to require) searches that must differentiate uppercase from lower-case characters. If you plan to use the Content Engine with CFS/IS, you must configure case sensitive. The Image Servicesdatabase is configured as case sensitive and the Content Engine database must match. Important: Select your SQL Server collation setting carefully. Switching collation settings after installation can be difficult and time-consuming, especially if you want to switch from case-sensitive to case-insensitive collation after significant user activity. If you have a case-sensitive database and you want to perform a case-insensitive search (programmatically or otherwise), you might encounter serious performance degradation on SQL Server because the database cannot use column, or property, indexes in these cases. 5. See IBM FileNet P8 Hardware and Software Requirements for required operating system and database patch sets and service packs. Verify that the required service pack is installed before proceeding. 6. Optional: If you want to disable the Named Pipes protocol for the database instance to be used by Process Engine, wait until after the Process Engine installation and configuration is complete. Disabling this protocol too early might cause Process Engine initialization to fail. 7. Record the following values in the Installation and Upgrade Worksheet: v The database server name, which is needed during Content Engine installation and configuration for the GCD and object stores. It is also needed to create the ODBC data source for Process Engine.
74
v The database instance name, which is needed to create the ODBC data source for Process Engine. Creating a Microsoft SQL Server database for the GCD: Create a Microsoft SQL Server database for the GCD database, which is required for Content Engine installation. 1. Create the database with a minimum size of 100 MB. 2. Record the GCD database name and the TCP/IP port number in the Installation and upgrade worksheet. Creating a Microsoft SQL Server database for Content Engine object stores: Create a Microsoft SQL Server database for a Content Engine object store. Each object store you create requires an empty database. Create the database with an initial size of 200 MB minimum. Record the object store database name and the TCP/IP port number in the Installation and upgrade worksheet. Creating a Microsoft SQL Server database for Process Engine: Create a Microsoft SQL Server database and filegroup for Process Engine. Create a database and filegroup for the Process Engine. Do not use the primary filegroup. 1. Create a database with a minimum size of 200 MB. 2. Assign a name to the database. The default name assigned by the Process Engine installation program is VWdb. 3. Assign a new file name for the database, for example, vw_data. 4. Specify a filegroup, for example, vwdata_fg. Do not use the Primary filegroup. 5. If you will be using the region recovery feature, create an additional filegroup for every region that is configured for recovery. 6. Record the values for the Process Engine database, database password, and filegroup in the Installation and upgrade worksheet. Modifying the tempdb database for Process Engine: Verify that the space allocated for the tempdb is at least 80 MB and that the collation settings match the Process Engine database. Enabling XA transactions: Configure the Windows server to enable XA transactions. Perform these steps on every Microsoft SQL Server that will contain a Content Engine database. 1. From Control Panel, open Administrative Tools, and then open Component Services. 2. Expand Component Services, right-click My Computer, and then select Properties. 3. (Windows 2008 only) Expand Distributed Transaction Coordinator and right-click Local DTC.
75
4. Click the MSDTC tab, and then click Security Configuration. 5. Select the Enable XA Transactions check box, and then click OK to restart the Microsoft DTC service. 6. Click OK again to close the Properties dialog box, and then close Component Services. 7. Stop and then restart the Microsoft SQL Server. Configuring the JDBC distributed transaction components: Run these steps to enable XA transactions on every Microsoft SQL Server that will have a Content Engine database. Take the following steps to enable XA transactions for Content Engine databases. 1. Download the Microsoft SQL Server JDBC Driver that is referenced in the IBM FileNet P8 Hardware and Software Requirements document for Content Engine SQL Server databases. 2. Copy the sqljdbc_xa.dll from the JDBC installation directory to the instances binn folder, although a pre-2.0 version of the driver also functions correctly from the tools\binn folder. If you are on a 32-bit processor, use the sqljdbc_xa.dll file in the x86 folder. If you are on a 64-bit processor, use the sqljdbc_xa.dll file in the x64 folder. 3. Log on as the sa administrator or as a user with equivalent permissions and execute the database script xa_install.sql on the master database on every SQL Server instance that will participate in distributed transactions. Important: Use SQL Server database credentials, not Windows credentials, to log on. Windows Integrated Logon to SQL Server is not supported with IBM FileNet P8. This script installs sqljdbc_xa.dll as an extended stored procedure and creates the SqlJDBCXAUser role in the Master database. 4. Add each database account (ce_db_user) that Content Engine uses to access SQL Server to the SqlJDBCXAUser role. This action grants permissions to those accounts to participate in distributed transactions with the JDBC driver. 5. Click Component Services > My Computer > Properties > MSDTC > Security Configuration and ensure that XA transactions are enabled. Running Process Engine pre-installation scripts (SQL Server): Run SQL scripts to create Process Engine database users, passwords, and stored procedures. The scripts to create Process Engine database users, passwords, and stored procedures for Microsoft SQL Server databases can run in several ways. v Run the scripts manually on the database server, before you run the Process Engine installation program. You can change the default runtime and maintenance users and passwords in the scripts before you run the scripts. v Run the scripts automatically from the Process Engine installation program, allowing the installation program to prompt for the sa password for SQL Server. You can change the default runtime and maintenance users and passwords in the scripts before you run the Process Engine installation program. v Run the scripts automatically from the Process Engine installation program by using operating system authentication. Use operating system authentication only in a trusted environment or when configured with a local database.
76
Scenarios for manually running SQL scripts for a Process Engine Microsoft SQL Server database Database user names and passwords are defined in SQL scripts and the same user names and passwords must be entered during Process Engine installation. Several scenarios are used to describe setting either default or custom values for the user names and passwords. Process Engine SQL scripts for Microsoft SQL Server on page 78 All the SQL scripts are located in the root of the Process Engine installation directory. The following scripts are for new Process Engine installations with SQL Server databases. Editing SQL scripts and changing default passwords (SQL Server) on page 78 Edit SQL scripts to change default passwords for the SQL Server database runtime and maintenance users for Process Engine. Running SQL scripts manually for a new installation (SQL Server) on page 79 Run the preinstallation scripts and optionally modify the runtime and maintenance user names and passwords. Scenarios for manually running SQL scripts for a Process Engine Microsoft SQL Server database: Database user names and passwords are defined in SQL scripts and the same user names and passwords must be entered during Process Engine installation. Several scenarios are used to describe setting either default or custom values for the user names and passwords. Scenario 1: Run SQL scripts manually before installing by using all default users and passwords To run the required SQL scripts manually before running the Process Engine installation program. All default users and passwords are defined in the scripts. 1. Before you install Process Engine, run the scripts manually on the database server. Do not change user names or passwords in the scripts. 2. When you install Process Engine, use default users for the database accounts. Do not set aliases. 3. Leave the f_sw and f_maint password fields blank to use the default values that were assigned when the scripts ran. 4. Reset the f_sw and f_maint passwords by running the Xdbconnect utility. Running Xdbconnect changes both the encrypted version of the password and the password in the database. Xdbconnect works only if the passwords in the encrypted file and the database match after installation. Scenario 2: Run SQL scripts manually before installing with nondefault users and passwords To run the required SQL scripts manually before running the Process Engine installation program, but nondefault users and passwords are set: 1. Edit the scripts to change the user names and passwords. 2. Run the scripts manually on the database server. 3. Install Process Engine and specify that aliases will be configured. The user names that are set when the scripts ran must be defined as the aliases for the f_sw and f_maint users. None of the fields for alias names can be left blank in the Process Engine installation window. However, you can use default values as needed.
77
4. Set the f_sw and f_maint passwords during Process Engine installation to the match the passwords that were set when the scripts were run manually. 5. Do not reset passwords by running Xdbconnect. Because nondefault passwords were used, there is no need to change them immediately after installation. Process Engine SQL scripts for Microsoft SQL Server: All the SQL scripts are located in the root of the Process Engine installation directory. The following scripts are for new Process Engine installations with SQL Server databases.
Script name CreatePEinstallSP_1.sql CreatePEinstallSP_2.sql CreatePEinstallSP_3.sql Action Creates the PE_createDbUsers stored procedure in the Process Engine database. Creates a stored procedure that is called during Process Engine installations. Creates the fn_error stored procedure.
The Process Engine scripts run with the following options: run_time_user This option value is one of the following: v f_sw - if you use the default database users when you run the Process Engine installation program. v alias for f_sw - if you define aliases for the operating system and database users when you run the Process Engine installation program. maintenance_user This option value is one of the following: v f_maint - if you use the default database users when you run the Process Engine installation program. v alias for f_maint - if you define aliases for the operating system and database users when you run the Process Engine installation program. PE_database_name (SQL Server) The database name that is entered during Process Engine installation. DSN (SQL Server only) The ODBC data source name that is entered during Process Engine installation. Editing SQL scripts and changing default passwords (SQL Server): Edit SQL scripts to change default passwords for the SQL Server database runtime and maintenance users for Process Engine. The Process Engine database runtime and maintenance users and their passwords are defined by running a series of scripts. The scripts can optionally be edited to change the default values to meet your requirements. Both passwords are defined in the CreatePEinstallSP_1.sql script and can be changed using the steps in this topic. 1. Open the CreatePEinstallSP_1.sql script with a text editor. 2. Modify the following line to change the default password for the user called run_time_user where filenet is the default password. Passwords must be enclosed in single quotation marks.
78
set @passwd1 = 'filenet'
3. Modify the following line to change the default password for the maintenance user where change$this_obnoxiou$_passwrd is the default password.
set @passwd2 = 'change$this_obnoxiou$_passwrd'
Running SQL scripts manually for a new installation (SQL Server): Run the preinstallation scripts and optionally modify the runtime and maintenance user names and passwords. Run the three SQL scripts to create users, passwords, and stored procedures. Optionally, modify the default user names and passwords created by the scripts. Record the values for the user names and passwords in the Installation and Upgrade Worksheet to refer to when installing Process Engine software. 1. Copy the CreatePEinstallSP_1.sql, CreatePEinstallSP_2.sql, and CreatePEinstallSP_3.sql script files from the Process Engine software package to the local disk on the SQL Server database server. 2. Create a text file named input.txt to identify the runtime and maintenance users. The file contains the following text:
PE_createDbUsers 'run_time_user', 'maintenance_user', 'PE_database_name'
The following is an example of the contents of the input.txt file.

PE_createDbUsers 'f_sw', 'f_maint', 'VWdb'
In this example: v The run_time_user is the default f_sw v The maintenance_user is the default f_maint v The database is VWdb 3. Edit the CreatePEinstallSP_1.sql script file to change the default passwords. Locate and modify the following two lines:
set @passwd1 = 'filenet' set @passwd2 = 'change$this_obnoxiou$_passwrd'
where @passwd1 is the runtime users password and @passwd2 is the maintenance users password. 4. Run the CreatePEinstallSP_3.sql script first, then run the CreatePEinstallSP_2.sql script, and then run the CreatePEinstallSP_1.sql script. The first example shows execution of the CreatePEinstallSP_3.sql script on the database server.
osql -E -d instance_name/PE_database_name -i CreatePEinstallSP_3.sql -n -o output3.log
Instead of using the parameter -E, you can use the following parameter:
-U sa -P sa password
The next example shows execution of CreatePEinstallSP_2.sql and CreatePEinstallSP_1.sql from a Process Engine server that is remote from the database server.
osql -D DSN -i CreatePEinstallSP_2.sql -n -o output2.log osql -D DSN -i CreatePEinstallSP_1.sql -n -o output1.log
The -D DSN parameter is the ODBC data source name. You do not need this parameter if the scripts are running on the database server.
79
The -d parameter is the database instance name and database name for Process Engine. If the default instance is being used, it does not need to be included in this parameter. The -E or alternative -U and -P parameters are not required if the scripts are running remotely from the database server. If the scripts run successfully, nothing is logged in the output3.log, output2.log, and output1.log files. 5. Run the script to create the runtime and maintenance users, using the input.txt file created earlier. The passwords set in the CreatePEinstallSP_1.sql script file will be assigned to the users. This example shows execution of the script from a Process Engine that is remote from the database server.
osql -D DSN -i input.txt
Configuring Microsoft SQL Server client for Process Engine

To configure your database clients for Process Engine, you must create ODBC data sources and, if required, install Microsoft SQL Server Client software for Process Engine. Creating the Process Engine ODBC data source and testing the connection Process Engine connections to a Microsoft SQL Server database at run time are handled through an ODBC data source. The 32-bit ODBC data source is required for both local and remote databases and must be created on the Process Engine server. Installing Microsoft SQL Server client software for Process Engine on page 81 Install Microsoft SQL Server client software if the Process Engine database is remote and if preinstallation scripts will be executed from the Process Engine installation program. Creating the Process Engine ODBC data source and testing the connection: Process Engine connections to a Microsoft SQL Server database at run time are handled through an ODBC data source. The 32-bit ODBC data source is required for both local and remote databases and must be created on the Process Engine server. Create a 64-bit ODBC data source if the preinstallation SQL scripts run from the Process Engine installation program on a 64-bit Windows 2008 server. This is in addition to the 32-bit ODBC data source required for Process Engine run time software. The following steps apply on a 32-bit version of the operating system. On a 64-bit operating system, locate and manually run the 32-bit version, which is typically located in C:\WINDOWS\SysWOW64\odbcad32.exe. To create the Process Engine ODBC data source and test the connection: 1. Click Start Program Administrator Tools Data Source (ODBC). 2. Click Add on the System DSN page. 3. Select SQL Server as the driver to use for the new data source and click Finish. 4. Enter a name and description for the data source. The name is required input for the Process Engine installation program when configuring for a SQL Server database.
80
5. Choose the SQL Server to connect to from the list of servers and click Next. If you see only a server name in the list, the connection is to the default instance. If there are named instances in the database, the server/instance name is in the list. 6. Click Next 7. Choose SQL Server authentication. 8. Select the option to get default settings for additional configuration options by connecting to the SQL Server. 9. Enter the login ID and Password to connect to the database. The database login ID information does not need to be for an administrator, and it is only used to connect to the database to get the default values for the remaining settings required to configure the data source. 10. Click Next 11. Change the default database to be the Process Engine database that was created earlier in Microsoft SQL Server planning considerations on page 72. 12. Enable Use ANSI null, paddings, and warning and enable Use ANSI quoted identifiers. 13. Enable Perform translation for character data and click Finish. 14. Verify the settings for the data source configuration and click Test Data Source. If the test is successful click OK. Otherwise resolve any problem before continuing. 15. Double-click SQL Server on the Connection Pooling page. 16. Select Dont pool connection to this driver and click OK. 17. Click OK on the ODBC Data Source Administrator window to finish configuration of the data source. 18. On the summary window, click Test Data Source. Installing Microsoft SQL Server client software for Process Engine: Install Microsoft SQL Server client software if the Process Engine database is remote and if preinstallation scripts will be executed from the Process Engine installation program. You must run a number of SQL scripts for the SQL Server database to create database users and stored procedures. v If the scripts are executed manually on the remote database server before you install Process Engine, you do not need to install SQL Server client. v If the scripts are executed from the Process Engine installation program, SQL Server client software must be installed on the Process Engine server. v If SQL Server client software is installed on the Process Engine Server, that software can be removed after successful installation and configuration of Process Engine software. To install Microsoft SQL Server client software: 1. Log on to the Process Engine server with an account that has local administrator privileges. 2. Install Workstation components, Books Online and development tools and from the Advanced options, select Client Components. 3. When the installation is complete, start the Client Network Utility and clear the Automatic ANSI to OEM conversion check box on the DB-Library Options page.
81
Preparing Oracle server

To prepare your Oracle databases, you must install the database software, and configure database components for IBM FileNet P8. Oracle planning considerations Plan the Oracle installation and configuration. Some rules apply to sharing of Oracle databases and tablespaces. Verifying that Oracle server is installed for IBM FileNet P8 on page 83 Install the Oracle software and configure the database components for your IBM FileNet P8 system. Running Process Engine pre-installation scripts (Oracle) on page 90 You must run several SQL scripts to create Process Engine users, passwords, tablespace defaults and privileges for the users, stored procedures, and synonyms for the stored procedures. These scripts for Oracle databases can be run in one of three ways. Oracle planning considerations: Plan the Oracle installation and configuration. Some rules apply to sharing of Oracle databases and tablespaces. General v Determine whether you want to use a dedicated or shared database. In this regard: Content Engine, Process Engine, and Rendition Engine can share a database engine, or they can each have a dedicated (unique) database engine. Content Engine, Process Engine, and Rendition Engine can each have a dedicated Oracle database instance, or they can share a database instance with one another or with non-IBM FileNet P8 applications. Content Engine, Process Engine, and Rendition Engine must each have their own tablespaces, even if they share a database engine. Each Process Engine isolated region configured for region recovery must have dedicated tablespaces. For detailed information regarding installation of Rendition Engine, see the IBM FileNet Rendition Engine Installation and Upgrade Guide. v Plan to use locally managed tablespaces. For performance reasons, IBM recommends that you create locally managed, rather than dictionary managed, tablespaces for Process Engine and Content Engine. (The tablespaces you create via Oracle Database assistant (dbca) are locally managed by default.) v Be aware of database client software requirements. For Process Engine, if the database is remote, you must install database client software on the Process Engine server. v An Oracle database must be remote if it is installed on a Linux server. Process Engine v Process Engine does not support Oracle Password Complexity Verification during the installation process. During installation this Oracle feature must be turned off if the Process Engine run-time user (f_sw or alias) or maintenance user (f_maint or alias) will use default passwords. After installation is complete and the passwords are changed, Oracles password complexity verification can be turned back on. v Oracle SQL scripts must be run. A number of SQL scripts must be run that: Create Oracle database accounts for IBM FileNet P8 Process Engine use.
82
Create a number of stored procedures. Grant access levels to the default tablespaces specified in the Process Engine installation program. v These scripts can be run manually, before starting Process Engine installation, or run from the Process Engine installation program. The Process Engine installation program will complete only if all these scripts run successfully. Verifying that Oracle server is installed for IBM FileNet P8: Install the Oracle software and configure the database components for your IBM FileNet P8 system. You can install and configure an Oracle database that is dedicated or shared by one or more IBM FileNet P8 components. An Oracle database can be: v dedicated to Content Engine v dedicated to Process Engine v dedicated to Rendition Engine v shared by two or more of Content Engine, Process Engine, and Rendition Engine In the shared configuration, the IBM FileNet P8 components use the same database, but different table spaces. You can also share the database with other non-IBM FileNet P8 applications. In the dedicated configuration, Content Engine, Process Engine, and Rendition Engine use separate databases. A database is local if it is on a machine where you will also be installing Content Engine, Process Engine, or Rendition Engine. A database is remote if it is on a separate server from the component using that database. For information regarding installation of Oracle Server and Rendition Engine, see the IBM FileNet Rendition Engine Installation and Upgrade Guide. v Make sure the machine that will host the database satisfies all pre-installation requirements specified in the Oracle installation documentation. v For Content Engine and Process Engine, IBM FileNet P8 supports the Oracle Advanced Security functionality of secure data transfer across network protocol boundaries. v If you will be installing Process Engine on a UNIX machine hosting the Oracle database, be sure that the value of the Oracle environment variable ORACLE_HOME (the path name for the Oracle Server software) is a string of at most 53 characters. If the string has more than 53 characters, the Process Engine installation program will not find the Oracle software, causing the installation to fail. v Refer to the IBM FileNet P8 Hardware and Software Requirements guide for required operating system and database patch sets, and service packs. The Oracle patches are available at the Oracle Web site. The Oracle patch installation procedure might be less complicated if you do it before you create any databases. v Transaction Processing is the required configuration type for the database that supports Content Engine. Choose this configuration type if your database will be dedicated to Content Engine or shared with Process Engine. v Record the values for the following settings as you work through the database installation. Enter this information in the Process Engine installer or Content
83
Engine installer sections of the Installation and Upgrade Worksheet, as appropriate. This information must be entered during subsequent installations. Be aware that the Process Engine installation program allows only alphanumeric characters and underscores. Oracle Home Global Database Name Oracle temporary tablespace name Oracle data tablespace name Oracle index tablespace name (optional) Oracle SID Installing an Oracle database engine Install the Oracle software and configure the database server. Configuring Oracle database character sets on page 85 Determine the Oracle database character set to use for the Content Engine and Process Engine databases. Creating an Oracle database on page 86 Create one or more databases, depending on whether one or more IBM FileNet P8IBM FileNet P8 components will share the database. Creating tablespaces for the GCD on page 86 Create an Oracle tablespaces for the GCD database. Creating Oracle tablespaces for Content Engine object stores on page 87 Create Oracle tablespaces for a Content Engine object store. Creating tablespaces for Process Engine on page 87 Create Oracle tablespaces for Process Engine. Setting environment variables for the Oracle and root users on UNIX database server on page 89 If your Process Engine Oracle database runs on a UNIX machine, set several environment variables in the .profile, .cshrc, or .login file before using the Oracle database. On Windows, the Oracle Universal Installer sets these variables. Configuring automatic transaction recovery on page 89 In a distributed database environment, Oracle MTS Recovery Service (automatically installed with Oracle Services for Microsoft Transaction Server) can resolve in-doubt transactions on the computer that started the failed transaction. Turning off Oracle password complexity verification on page 89 Process Engine does not support Oracle Password Complexity Verification during the installation process if default passwords are used for the database runtime and maintenance users. Installing an Oracle database engine: Install the Oracle software and configure the database server. The following procedure shows the minimal choices (specific to the needs of Content Engine and Process Engine) for installing a database engine. Consult Oracle installation documentation for complete preinstallation requirements and instructions. To install an Oracle database engine: 1. Choose the following from the list of available product components: v Oracle Server v Oracle Net Services
84
Oracle Net Listener v Oracle Development Kit Oracle Call Interface (OCI) v (Windows) Oracle Windows Interfaces Oracle Services for Microsoft Transaction Server v Oracle Documentation (recommended) 2. If a database is dedicated to Content Engine, or if it will be shared by Content Engine and Process Engine, then Transaction Processing (also known as OLTP) is the required configuration type. 3. If you are going to install Process Engine on this machine, verify/add/edit/uncomment the following lines in the file sqlnet.ora (create the file if it doesnt exist) while the Oracle services/processes are stopped:
NAMES.DIRECTORY_PATH=(TNSNAMES) SQLNET.AUTHENTICATION_SERVICES=(NTS)
If Oracle is configured to use LDAP, TNSNAMES must appear in the names.directory_path ahead of LDAP or ONAMES, for example: NAMES.DIRECTORY_PATH=(TNSNAMES,ONAMES,LDAP). sqlnet.ora is typically in $ORACLE_HOME/network/admin on UNIX or ORACLE_HOME\network\admin on Windows operating systems. 4. Refer to the IBM FileNet P8 Hardware and Software Requirements for required operating-system and database patch sets, and service packs. 5. Start the listener and the Oracle database service/processes (Windows/UNIX) if they have not started automatically. Configuring Oracle database character sets: Determine the Oracle database character set to use for the Content Engine and Process Engine databases. v If a database is dedicated to Content Engine or shared with Process Engine, the required character set is AL32UTF8 (Unicode 3.1 UTF-8 universal character set). v If an object store that is being upgraded uses a database with a character set other than AL32UTF8, you must convert that character set to AL32UTF8. When the character set is not AL32UTF8, applications that attempt to insert Unicode data, for example, when cutting and pasting from a word processing application into Workplace document properties, might (for some characters) experience data loss when stored in the database. v If the database is dedicated to Process Engine, choose a UNICODE, multibyte, or single-byte 8-bit character set. Be aware of the special NLS_LANG settings for character sets and locale on Process Engine machines. Consider the following requirements: v You must ensure that the NLS_LANG Oracle environment variable on an Process Engine machine matches the character set/locale of the operating system. v Under Windows, by default the Oracle Client installer sets the NLS_LANG value in the Windows registry to match the locale of the Oracle Client machines operating system. For Process Engine, you do not need to override the registry value with the user environment variable. The Oracle client NLS_LANG value is adequate for either database character sets of Unicode (for example, AL32UTF8) or non-Unicode (for example, WE8MSWIN1252) database character set.
85
v Under UNIX, the Oracle Client installer does not automatically set the NLS_LANG. For this reason, after you have installed Process Engine, you must manually set the locale and character set value on each UNIX Oracle Client machine from which users will access Process Engine. v Set the NLS_LANG value manually on Oracle Client machines using one of the following methods: (UNIX) Add NLS_LANG to the shell environment login files for each user who will be logging on to the machine to run IBM FileNet P8 software. (Windows) Set or modify the value of the NLS_LANG key using System Properties in the Control Panel for each user who will be logging on to the machine to run IBM FileNet P8 software. Creating an Oracle database: Create one or more databases, depending on whether one or more IBM FileNet P8IBM FileNet P8 components will share the database. IBM FileNet P8 requires the following settings for Oracle databases: Database configuration type If a database is dedicated to Content Engine, or if it will be shared by Content Engine and Process Engine, then Transaction Processing (also known as OLTP) is the required configuration type. Server process type Dedicated Server Mode Database character set Choose a database character set, specified in Configuring Oracle database character sets on page 85. Creating tablespaces for the GCD: Create an Oracle tablespaces for the GCD database. 1. Using Oracle Enterprise Manager or SQL*Plus, create a user (ce_db_user), password, and default tablespace in the Oracle database for the GCD that Content Engine will access. See Creating Content Engine database accounts for information about the user and required permissions. If one or more object store tablespaces and the GCD tablespace share a physical database, they must not share the same Oracle user. Create different, unique Oracle users for each in this case. 2. Tablespace names must contain only alphanumeric and underscore characters. Names must start with an alphabetic character and must be at most 18 characters long. For performance reasons, IBM recommends that you specify locally managed, instead of dictionary managed, tablespaces. (The tablespaces you create via Oracle Enterprise Manager are locally managed by default.) The following table shows the recommended minimum sizes of the permanent and temporary tablespaces for each object store that Content Engine will access. (The tablespace names shown in the table are arbitrary.)
Tablespace Name gcd tempgcd Tablespace Type Permanent Temporary Minimum Size 100 MB 2 GB Description Permanent tablespace for the GCD Temporary tablespace for the GCD
86
Creating Oracle tablespaces for Content Engine object stores: Create Oracle tablespaces for a Content Engine object store. To create Oracle tablespaces: 1. Using Oracle Enterprise Manager or SQL*Plus, create a user (ce_db_user), password, and default tablespace in the Oracle database for each object store that Content Engine will access. See Creating Content Engine database accounts for information about the user and required permissions. 2. Create separate users for every object store tablespace. Tablespace names used by Content Engine must contain only alphanumeric and underscore characters. Names must start with an alphabetic character and must be at most 18 characters long. For performance reasons, IBM recommends that you specify locally managed, instead of dictionary managed, tablespaces. (The tablespaces you create via Oracle Enterprise Manager are locally managed by default.) The following table shows the recommended minimum sizes of the permanent and temporary tablespaces for object stores that Content Engine will access. The temporary tablespace can be shared by multiple object stores.
Tablespace Name objectstore1 tempobjectstore1 Tablespace Type Permanent Temporary Minimum Size 200 MB 2 GB Description Permanent tablespace for object store Temporary tablespace for object store
Creating tablespaces for Process Engine: Create Oracle tablespaces for Process Engine. To create tablespaces: 1. Create the tablespaces shown in the following table for the Process Engine. Note that the index tablespace (vwindex_ts) is optional. Tablespace names used by Process Engine can contain only alphanumeric and underscore characters. Names must start with an alphabetic character and must be at most 18 characters long. 2. If you will use the region recovery feature in Process Engine, you must create the default tablespaces and an additional data and index tablespace for each region to be configured for recovery. The same runtime and maintenance users will be used for all Process Engine tablespaces. The following table shows the recommended tablespace names, types, and minimum sizes:
87
Tablespace Name vwdata_ts
Tablespace Type Permanent
Minimum Size (MB) 200
Description This is the default name of the data tablespace dedicated to Process Engine. This is the only data tablespace configured during Process Engine installation. Record the tablespace name in the Installation and Upgrade Worksheet.
vwtemp_ts
Temporary
400
This is the default name of the temporary tablespace dedicated to Process Engine. This is the only temp tablespace configured during Process Engine installation. Record the tablespace name in the Installation and Upgrade Worksheet.
vwindex_ts (optional)
Permanent
200
This is the default name of the optional default index tablespace. This is the only index tablespace configured during Process Engine installation. If you dont create an index tablespace the data tablespace will be used for indexes. Record the tablespace name in the Installation and Upgrade Worksheet.
region X data
Permanent
200
This is the data tablespace to be used by an individual region configured for recovery. This tablespace cannot be shared by any other region.
88
Tablespace Name region X index
Tablespace Type Permanent
Description This is the index tablespace to be used by an individual region configured for recovery. This tablespace cannot be shared by any other region.
Setting environment variables for the Oracle and root users on UNIX database server: If your Process Engine Oracle database runs on a UNIX machine, set several environment variables in the .profile, .cshrc, or .login file before using the Oracle database. On Windows, the Oracle Universal Installer sets these variables. To set environment variables:
Option For the Oracle user Description Set: v ORACLE_SID v ORACLE_HOME v Set PATH to:$ORACLE_HOME/bin (HP-UX only) v Set LD_LIBRARY_PATH to: $ORACLE_HOME/lib (HP-UX only) v Set LD_LIBRARY_PATH to:$ORACLE_HOME/lib32 (Solaris only) v Set LIBPATH to: $ORACLE_HOME/ lib32:$ORACLE_HOME/lib (AIX only) v Set SHLIB_PATH to: $ORACLE_HOME/lib32 (HP-UX only) For the root user Set ORACLE_HOME.
Configuring automatic transaction recovery: In a distributed database environment, Oracle MTS Recovery Service (automatically installed with Oracle Services for Microsoft Transaction Server) can resolve in-doubt transactions on the computer that started the failed transaction. v Enable automatic transaction recovery by performing the tasks shown in the section Scheduling Automatic Microsoft Transaction Server Recovery in Oracle Services for Microsoft Transaction Server Developers Guide (Oracle Part Number A95496-01). v If you are using an Oracle Fail Safe configuration, perform the procedure shown in Modifying Registry Values for Oracle Fail Safe Configurations in Oracle Services for Microsoft Transaction Server Developers Guide (Oracle Part Number A95496-01). Turning off Oracle password complexity verification: Process Engine does not support Oracle Password Complexity Verification during the installation process if default passwords are used for the database runtime and maintenance users.
89
If you are using the default passwords for the runtime (f_sw ) or maintenance (f_maint) users, turn off this Oracle feature and do not re-enable it until you have installed and configured Process Engine. Running Process Engine pre-installation scripts (Oracle): You must run several SQL scripts to create Process Engine users, passwords, tablespace defaults and privileges for the users, stored procedures, and synonyms for the stored procedures. These scripts for Oracle databases can be run in one of three ways. v Run them manually on the database server, before running the Process Engine installation program. If the scripts are run manually, both the default runtime and maintenance users and their passwords can be modified in the scripts before execution. v Run them automatically from the Process Engine installation program, allowing the installation program to prompt for the sys password for Oracle. v Run them automatically from the Process Engine installation program, running silently using operating system authentication. Use operating system authentication only in a trusted environment or when configured with a local database. Scenarios for manually running SQL scripts for a Process Engine Oracle database Several scenarios are used to describe Process Engine installation and configuration parameters and how to set them in each case. Process Engine SQL scripts for Oracle on page 91 All Process Engine SQL scripts are located in the root of the Process Engine installation directory. Changes made by pe_filenet_site.sql and pe_ora_users_defaults.sql on page 93 The information in columns 1, 2 and 3 is created or set by SQL script pe_filenet_site.sql. The information in column 5 is set by SQL script pe_ora_users_defaults.sql. Changes made by pe_create_stored_procedures.sql and pe_grant_sp_permissions.sql on page 93 The information in columns 1, 2 and 3 is created by pe_create_stored_procedures.sql. The information in columns 4 and 5 is created by pe_grant_sp_permissions.sql. Editing SQL scripts and changing default passwords (Oracle) on page 94 To change the default passwords in an Oracle database environment, you must edit the pe_filenet_site.sql and pe_install_scripts.sql script files. Running SQL scripts manually for a new installation (Oracle) on page 94 To run SQL scripts for a new installation, copy the scripts to the database server, start SQL Plus, and enter @pe_install_scripts.sql run_time_user maintenance_user data_tablespace index_tablespace temp_tablespace. Running SQL scripts manually for an upgrade (Oracle) on page 94 To run scripts for an upgrade, copy the scripts to the database server, start SQL Plus, and enter @pe_upgrade_scripts.sql run_time_user maintenance_user. Scenarios for manually running SQL scripts for a Process Engine Oracle database: Several scenarios are used to describe Process Engine installation and configuration parameters and how to set them in each case.
90
Scenario 1: Run SQL scripts manually before installing using all default users and passwords The DBA wants to run the required SQL scripts manually before running the Process Engine installation program. All default users and passwords are defined in the scripts. 1. Turn off Oracle password complexity. 2. Run the scripts manually, before running the Process Engine installation program, without making any changes in the scripts to passwords, setting the runtime user to f_sw and the maintenance user to f_maint. 3. Run Process Engine installation program and use default users for the database accounts (do not set aliases). 4. Leave the f_sw and f_maint password fields blank (using the defaults assigned with the scripts ran). 5. Turn Oracle password complexity back on. 6. Reset the f_sw and f_maint passwords by running Xdbconnect. This changes both the encrypted version of the password and the password in the database. Xdbconnect works only if the passwords in the encrypted file and the database match after installation. Scenario 2: Run SQL scripts manually before installing with non-default users and passwords The DBA wants to run the required SQL scripts manually before running the Process Engine installation program, but non-default users and passwords are set. 1. Do not turn off Oracle password complexity. 2. Edit the scripts to change the passwords. 3. Run the scripts, entering the desired runtime and maintenance users and passwords. 4. Run the Process Engine installation program and indicate that aliases will be configured. The user names set when the scripts ran must be defined as the aliases for f_sw and f_maint. None of the fields for alias names can be left blank in the Process Engine installation screen, but default values can be entered where default values are still wanted. 5. Set the f_sw and f_maint passwords during Process Engine installation to the match the passwords set when the scripts were run manually. 6. Do not reset passwords by running Xdbconnect. Because non-default passwords were used, there is no need to change them immediately after installation. Process Engine SQL scripts for Oracle: All Process Engine SQL scripts are located in the root of the Process Engine installation directory.
91
The pe_upgrade_scripts.sql script is the only script needed for upgrades.

Script Name pe_install_scripts.sql Action A wrapper script that runs the following scripts: pe_filenet_site.sql, pe_create_stored_procedures.sql, and pe_grant_sp_permissions.sql. The pe_install_scripts.sql script generates an Oracle output spool file. After the script completes, the Process Engine installation program scans the output file for errors. pe_filenet_site.sql Creates the database users for IBM FileNet P8. See Changes made by pe_filenet_site.sql and pe_ora_users_defaults.sql on page 93 for details.
pe_create_stored_procedures.sql Creates several stored procedures. See Changes made by pe_create_stored_procedures.sql and pe_grant_sp_permissions.sql on page 93 for details. pe_grant_sp_permissions.sql Runs grants and creates synonyms for stored procedures. See Changes made by pe_create_stored_procedures.sql and pe_grant_sp_permissions.sql on page 93 for details. Sets user tablespace defaults and privileges for IBM FileNet P8 users. See Changes made by pe_filenet_site.sql and pe_ora_users_defaults.sql on page 93 for details. A wrapper script that runs the following scripts: pe_create_stored_procedures.sql and pe_grant_sp_permissions.sql. The pe_upgrade_scripts.sql script generates an Oracle output spool file. After the script completes, the Process Engine installation program scans the output file for errors.
pe_ora_users_defaults.sql
pe_upgrade_scripts.sql
The Process Engine scripts run with the following options: run_time_user This option value is one of the following: v f_sw - if you use the default database users when you run the Process Engine installation program. v alias for f_sw - if you define aliases for the operating system and database users when you run the Process Engine installation program. maintenance_user This option value is one of the following: v f_maint - if you use the default database users when you run the Process Engine installation program. v alias for f_maint - if you define aliases for the operating system and database users when you run the Process Engine installation program. data _tablespace (Oracle only) The data tablespace name that will be entered during Process Engine installation.
92
index_tablespace (Oracle only) The index tablespace name that will be entered during Process Engine installation. This is an optional tablespace. If it does not exist, enter the data tablespace value. temp_tablespace (Oracle only) The temp tablespace name that will be entered during Process Engine installation. Changes made by pe_filenet_site.sql and pe_ora_users_defaults.sql: The information in columns 1, 2 and 3 is created or set by SQL script pe_filenet_site.sql. The information in column 5 is set by SQL script pe_ora_users_defaults.sql.
Granted permissions/ privileges/roles Create session, alter session, create table, create view, create sequence, create public synonym, drop public synonym, create procedure Select on sys.dba_users Select on sys.dba_ tablespaces Create public synonym Drop public synonym f_maint or alias DBA role change$this_ obnoxiou$_ password Yes Default, temp, and index Tablespace privileges*** Data tablespace set Temp tablespace set Index tablespace set Quota 0 on system Quota unlimited on default tablespace Quota unlimited on temp tablespace Quota unlimited on index tablespace
FileNet DB user created f_sw or alias
Default Initial password filenet
Can delete post-install? No
Passwords can be manually changed after installation with the Xdbconnect tool. *** Default data, temp, and index tablespace names are set during installation. These names are used to set database user privileges. The index tablespace is optional. If not specified, the data tablespace will be used. Changes made by pe_create_stored_procedures.sql and pe_grant_sp_permissions.sql: The information in columns 1, 2 and 3 is created by pe_create_stored_procedures.sql. The information in columns 4 and 5 is created by pe_grant_sp_permissions.sql.
93
Procedure name fn_error
Owner f_sw or alias
Description Displays text of a specified ORA error number. Calls SQL stored procedure fn_errortxt to get the text.
Grants Execute to public
Synonym fn_ error
fn_ oraversion
f_sw or alias
Displays version number of Oracle RDBMS. Calls SQL stored procedure fn_oraversiontxt.
Execute to public
fn_ oraversion
fn_errortxt
f_sw or alias f_sw or alias
Gets and returns the message text of a specified ORA SQL Error Code.
Execute to public
fn_ errortxt
fn_ oraversiontxt
Gets and returns the version Execute to number of the Oracle RDBMS. public
fn_ oraversiontxt
Editing SQL scripts and changing default passwords (Oracle): To change the default passwords in an Oracle database environment, you must edit the pe_filenet_site.sql and pe_install_scripts.sql script files. 1. Open the pe_filenet_site.sql script with a text editor. 2. Locate and edit the default runtime password (filenet) in the following command:
grant create session, alter session, create table, create view, create sequence, create public synonym, drop public synonym, create procedure to &1 identified by filenet;
3. Locate and edit the default maintenance password (change$this_obnoxiou$_passwrd) in the following command:
grant dba to &2 identified by change$this_obnoxiou$_passwrd;
4. Open the pe_install_scripts.sql script with a text editor. 5. Locate and edit the default runtime password (filenet) in the following command:
connect &1/filenet
Running SQL scripts manually for a new installation (Oracle): To run SQL scripts for a new installation, copy the scripts to the database server, start SQL Plus, and enter @pe_install_scripts.sql run_time_user maintenance_user data_tablespace index_tablespace temp_tablespace. 1. From the Process Engine software package, copy the scripts to the database server. 2. Start SQL Plus. For example, enter the command: sqlplus sys/password as sysdba 3. At the SQL prompt, enter: @pe_install_scripts.sql run_time_user maintenance_user data_tablespace index_tablespace temp_tablespace For example:
@pe_install_scripts.sql f_sw f_maint vwdata_ts vwindex_ts vwtemp_ts
Running SQL scripts manually for an upgrade (Oracle):
94
To run scripts for an upgrade, copy the scripts to the database server, start SQL Plus, and enter @pe_upgrade_scripts.sql run_time_user maintenance_user. 1. From the Process Engine software package, copy the scripts to the database server. 2. Start SQL Plus. For example, type the following command: sqlplus sys/password as sysdba 3. At the SQL prompt, enter: @pe_upgrade_scripts.sql run_time_user maintenance_user For example:@pe_upgrade_scripts.sql f_sw f_maint. Requirement: These scripts that are run via pe_upgrade_scripts.sql must be run for all upgrades.
Configuring Oracle client for Process Engine

Install the Oracle Client software to prepare for the installation of Process Engine. Content Engine does not require installation of Oracle Client software. For information regarding installation of Oracle Client and Rendition Engine, see the IBM FileNet Rendition Engine Installation and Upgrade Guide. v Install Oracle Client on any machine that will host Process Engine, Rendition Engine, or any other IBM FileNet P8 component except Content Engine (such as Enterprise Manager) that needs to access an Oracle database. v Install a 32-bit Oracle Client for Process Engine. v If you will be installing Process Engine on a UNIX machine hosting Oracle Client software, be sure that the value of the Oracle environment variable ORACLE_HOME (the path name for the Oracle Client software) is a string of at most 53 characters. If the string has more than 53 characters, the Process Engine installer will not find the Oracle software, causing the installation to fail. v Refer to the IBM FileNet P8 Hardware and Software Requirements for required operating system and database patch sets, and Service Packs. The Oracle patches are available at the Oracle website. The Oracle patch installation procedure might be less complicated if you do it before you create any databases. Installing the Oracle client The following procedure shows the minimal choices (specific to the needs of Process Engine) for installing a database client. Consult the Oracle installation documentation for complete preinstallation requirements and instructions. Installing the Oracle client: The following procedure shows the minimal choices (specific to the needs of Process Engine) for installing a database client. Consult the Oracle installation documentation for complete preinstallation requirements and instructions. To install the Oracle client: 1. Choose the following from the list of available product components: v Oracle10g Client or Oracle11g Client as appropriate v Oracle Network Utilities v Oracle Database Utilities v SQL*PLUS v (Windows) Oracle Windows Interfaces Oracle Services for Microsoft Transaction Server 2. Using Oracle Net Configuration Assistant, test the connection to the Oracle database server with an appropriate Oracle user and password.
95
3. If you are going to install Process Engine software on this machine, and your remote Oracle database uses the Unicode character set AL32UTF8, then for each user who will access Process Engine software on the machine, set the value of the Oracle environment variable parameter NLS_LANG to reflect the PE-supported locale and (non-Unicode) character set on the machine.
Option Windows UNIX Description Set/modify the value of the NLS_LANG key via System Properties in the Control Panel. Add NLS_LANG to the shell environment login files for each user who will be logging onto the machine to run IBM FileNet P8 software.
To affect the environment for only Process Engine, set NLS_LANG for just the fnsw user. (On Windows platforms, fnsw is created by the Process Engine installer; on UNIX platforms, you manually create fnsw as part of the Process Engine installation task.) 4. If you are going to install Process Engine software on this machine to connect to a remote Oracle database, set the value of an environment variable for the oracle user to a default connect identifier, such as the Oracle net service name or the database service name. The name of the environment variable depends on which operating system is on this machine:
Option Windows UNIX Description LOCAL TWO_TASK
5. If you are going to install Process Engine software on a UNIX machine to connect to a remote Oracle database, set the following environment variables in the startup file of the default oracle user. v ORACLE_HOME v Set PATH to: $ORACLE_HOME/bin (UNIX only) 6. If you are going to install Process Engine on this machine, verify that the sqlnet.ora file exists and that the following lines are in it.
NAMES.DIRECTORY_PATH=(TNSNAMES) SQLNET.AUTHENTICATION_SERVICES=(NTS)
If Oracle is configured to use LDAP, TNSNAMES must appear in the names.directory_path ahead of LDAP or ONAMES, for example:
NAMES.DIRECTORY_PATH=(TNSNAMES,ONAMES,LDAP)
sqlnet.ora is typically in $ORACLE_HOME/network/admin on UNIX or ORACLE_HOME\network\admin on Windows operating systems. 7. Install all required Oracle patches, as specified in the IBM FileNet P8 Hardware and Software Requirements. These patches are available at the Oracle Web site.
Preparing DB2 for z/OS servers

Plan the DB2 for z/OS installation and configuration, install the software, and configure database components for IBM FileNet P8 components.
DB2 for z/OS planning considerations

The database must be remote. The DB2 for z/OS database must be remote from Process Engine and Content
96
Engine. Process Engine and Content Engine do not run on z/OS. See the IBM FileNet P8 Hardware and Software Requirements guide for specifics on supported software versions and platforms. Determine whether you want to use a dedicated or shared database resource. In this regard: v Content Engine and Process Engine can share a database engine, or they can each have a dedicated (unique) database engine. v Content Engine and Process Engine can each have a dedicated DB2 instance, or they can share an instance with one another or with non-IBM FileNet P8 applications. v Each Content Engine and Process Engine must have their own databases and tablespaces. v The Content Engine GCD and object stores can be created in database tablespaces or schemas. Specific references to tablespaces in this procedure apply to either configuration.
Assign unique databases to the Content Engine global configuration data (GCD) and object stores. It is a best practice to create a separate database for the GCD and each object store for ease of maintenance, security control, and the like. Use System Managed Storage (SMS). Configure system managed storage for Process Engine and Content Engine databases. Use UTF-8 collation For both Content Engine and Process Engine, use UTF-8 collation settings by configuring CCSID UNICODE. Add SDSNLOD2 into the LNKLST. The SDSNLOD2 library must be added into the LNKLST when z/OS is configured. Use TCP/IP as the default protocol. For both Content Engine and Process Engine, set TCP/IP as the default network protocol. Determine the maximum size of the content elements your users store. This affects setting up database storage areas or file storage areas. When you create an object store, a database storage area is provided by default, allowing you to store content as database BLOBs. You can also create one or more file storage areas to store content on local or remote file systems. If your users store large individual documents or other content elements, use only file storage areas. Otherwise, users can encounter memory-related errors when retrieving or indexing the large content. Controlled tests with limited concurrency exhibited errors when run with files that were 300 MB or larger. Factors affecting this file-size limitation include driver and application server memory demands, other activity such as concurrent retrieval or indexing of large content, and JVM memory allocations. Verifying that DB2 for z/OS server is installed for IBM FileNet P8 Plan the DB2 for z/OS installation and configuration. Some rules apply to sharing of instances and databases. Verifying that DB2 for z/OS server is installed for IBM FileNet P8: Plan the DB2 for z/OS installation and configuration. Some rules apply to sharing of instances and databases.
97
You can also share the instance with other (non-IBM FileNet P8) applications. v dedicated to Content Engine v dedicated to Process Engine v shared by two or more of Content Engines and Process Engines Record the values for the following settings as you work through the database installation. This information must be entered during subsequent installations of Process Engine and Content Engine. Be aware that z/OS allows only alphanumeric characters. v DB2 Server name. Record both the TCP/IP address and the fully qualified domain name. v DB2 server database instance name(s) v Content Engine and Process Engine dedicated database names v DB2 instance port numbers v Process Engine runtime database user (fsw or alias) password v Process Engine maintenance database user (fmaint or alias) password v User IDs and passwords for Content Engine DB2 users (operating system users who have been granted permissions on the database) Determining page size and user fields When you create a DB2 database, you have a choice of several page sizes for your tablespace: 4 KB, 8 KB, 16 KB, and 32 KB. The page size you choose affects the number and size of the user-defined index fields and the maximum row length of the tables within that tablespace. Creating and updating the DB2 databases for Content Engine and Process Engine Create three DB2 for z/OS databases, one for Process Engine, one for the Content Engine GCD, and one for a single Content Engine object store. Determining page size and user fields: When you create a DB2 database, you have a choice of several page sizes for your tablespace: 4 KB, 8 KB, 16 KB, and 32 KB. The page size you choose affects the number and size of the user-defined index fields and the maximum row length of the tables within that tablespace. The important things to remember are: v The total row length of all the fields (including system and user) cannot be larger than the page size. v The DB2 page size you select when you create the database must be large enough to hold at least one complete record. v DB2 cannot retrieve a partial record or spread a single record onto two pages. v It is a best practice to assign 8 KB minimum page sizes for Process Engine databases. v 32 KB minimum page sizes are required for Content Engine databases. Creating and updating the DB2 databases for Content Engine and Process Engine: Create three DB2 for z/OS databases, one for Process Engine, one for the Content Engine GCD, and one for a single Content Engine object store. Record the names of the databases in the Installation and Upgrade Worksheet.
98
Preparing DB2 for Linux, UNIX and Windows servers

Plan and prepare your IBM DB2 for Linux, UNIX and Windows servers for IBM FileNet P8 installation. The following are planning considerations for DB2 for Linux, UNIX and Windows: v Determine whether DB2 server instances will be 64-bit or 32-bit. Use the version that is appropriate to the operating system where the server instance is installed. v Determine whether you want to use a dedicated or shared database. In this regard: Content Engine and Process Engine can share a database engine, or they can each have a dedicated (unique) database engine. Content Engine and Process Engine can each have a dedicated DB2 instance, or they can share an instance with one another or with non-IBM FileNet P8 applications. Each Content Engine and Process Engine must have their own databases and tablespaces. The Content Engine global configuration data (GCD) and each object store must have its own database. v Plan to use automatic storage for tablespaces. For performance reasons, IBM recommends that you create tablespaces using automatic storage, rather than database managed or system managed tablespaces for Process Engine and Content Engine. v Set DB2 collation. For Content Engine, use UTF-8. Process Engine will support the UTF-8 code set, code page 1208. Process Engine will also support all other single-byte character sets, for example:
Code Set ISO8859-15 ISO8859-1 Code Page # 923 819
v It is a best practice to use SERVER authentication. SERVER_ENCRYPT and CLIENT authentication are also supported. v Determine the maximum size of the content elements your users store. This affects setting up database storage areas or file storage areas. When you create an object store, a database storage area is provided by default, allowing you to store content as database BLOBs. You can also create one or more file storage areas to store content on local or remote file systems. If your users store large individual documents or other content elements, use only file storage areas. Otherwise, users can encounter memory-related errors when retrieving or indexing the large content. Important: Controlled tests with limited concurrency exhibited errors when run with files that were 300 MB or larger. Factors affecting this file-size limitation include driver and application server memory demands, other activity such as concurrent retrieval or indexing of large content, and JVM memory allocations. Verifying that DB2 for Linux, UNIX and Windows is installed for IBM FileNet P8 You can install and configure a DB2 instance that is dedicated or shared by one or more IBM FileNet P8 components. You can also share the instance with other (non-IBM FileNet P8) applications. Verifying that DB2 for Linux, UNIX and Windows is installed for IBM FileNet P8:
99
You can install and configure a DB2 instance that is dedicated or shared by one or more IBM FileNet P8 components. You can also share the instance with other (non-IBM FileNet P8) applications. Dedicated to Content Engine Dedicated to Process Engine Shared by two or more Content Engines or Process Engines In a shared configuration, the IBM FileNet P8 components use the same instance, but different databases. v Content Engine supports multiple object stores within the same DB2 database provided the users are properly partitioned via tablespace authorization. v v v v v Content Engine and Process Engine should not share tablespaces. A database is local if it is on a machine where you will also be installing Content Engine or Process Engine. A database is remote if it is on a separate server from the component using that database. When this procedure has been completed, proceed to Configuring DB2 client on page 105. Important: Record the values for the following settings as you work through the database installation. Enter this information in the appropriate sections of the Installation and Upgrade Worksheet. This information must be entered during subsequent installations of Process Engine and Content Engine. Be aware that the Process Engine installation program allows only alphanumeric characters and underscores. v DB2 Server name v DB2 server database instance names (for example, P8inst) v Content Engine and Process Engine dedicated database names (for example, VWdb) v Dedicated tablespace names (for example, vwdata) v DB2 instance port numbers v Process Engine runtime database user (f_sw or alias) password v Process Engine maintenance database user (f_maint or alias) password v User ID and password for Content Engine DB2 user Installing DB2 for Linux, UNIX and Windows and creating DB2 instances on page 101 Create DB2 for Linux, UNIX and Windows instances for Content Engine and Process Engine and set several instance values. Determining page size and user fields on page 101 When you create a DB2 database, you have a choice of several page sizes for your tablespace: 4 KB, 8 KB, 16 KB, and 32 KB. The page size you choose affects the number and size of the user-defined index fields and the maximum row length of the tables within that tablespace. Creating and updating the DB2 databases for Content Engine and Process Engine on page 101 To create and update the DB2 databases, log on as the database instance owner and update the configuration parameter. Creating the DB2 tablespaces for Process Engine on page 102 Create five tablespaces for Process Engine on DB2 for Linux, UNIX and Windows. The default data, index and BLOB tablespaces will be prompted for by the Process Engine installation program.
100
Creating the DB2 tablespaces for Content Engine on page 104 Create four tablespaces for Content Engine on DB2 for Linux, UNIX and Windows. Each additional object store will require an additional tablespace and a unique tablespace user. Installing DB2 for Linux, UNIX and Windows and creating DB2 instances: Create DB2 for Linux, UNIX and Windows instances for Content Engine and Process Engine and set several instance values. To install DB2 for Linux, UNIX and Windows and create DB2 instances: 1. Install the IBM DB2 for Linux, UNIX and Windows software. Make note of the TCP/IP port number assigned to the instance or instances, as the port number will be needed during the DB2 client configuration steps. The port number assigned can be found in the /etc/services file, associated with the DB2 instance(s) just created. After a successful installation, the DB2 instance should be up and running. 2. Refer to the IBM FileNet P8 Hardware and Software Requirements for required operating-system and database patch sets, and service packs. 3. Content Engine and Process Engine can share an instance, or each engine can have its own instance. Create the appropriate instances if they do not exist. 4. Set the optprofile value (Content Engine). The default value is NO. Set it to YES by logging on as the instance owner and executing: db2set DB2_OPTPROFILE=YES 5. (DB2 version 9.7 only) Set the DB2_WORKLOAD variable to FILENET_CM. Log on as the instance owner and set the variable by executing: db2set DB2_WORKLOAD=FILENET_CM 6. Set TCP/IP as the default protocol. Log on as the instance owner and set TCP/IP as the default protocol by executing: db2set DB2COMM=tcpip Determining page size and user fields: When you create a DB2 database, you have a choice of several page sizes for your tablespace: 4 KB, 8 KB, 16 KB, and 32 KB. The page size you choose affects the number and size of the user-defined index fields and the maximum row length of the tables within that tablespace. The important things to remember are: v The total row length of all the fields (including system and user) cannot be larger than the page size. v The DB2 page size you select when you create the database must be large enough to hold at least one complete record. v DB2 cannot retrieve a partial record or spread a single record onto two pages. v It is a best practice to assign 8 KB minimum page sizes for Process Engine databases. v 32 KB minimum page sizes are required for Content Engine databases. Creating and updating the DB2 databases for Content Engine and Process Engine: To create and update the DB2 databases, log on as the database instance owner and update the configuration parameter. To create and update the DB2 database:
101
1. Log on as the database instance owner as defined earlier. At least three databases must be created, one for Process Engine, one for the Content Engine GCD, and one for a single Content Engine object store. The database name needs to be unique and from 1 to 8 characters long. 2. For a database to be used by Content Engine object stores, update the following configuration parameter. Set the value, minimally, to the value indicated here:
APPLHEAPSZ 2560
Creating the DB2 tablespaces for Process Engine: Create five tablespaces for Process Engine on DB2 for Linux, UNIX and Windows. The default data, index and BLOB tablespaces will be prompted for by the Process Engine installation program. If you will be using the Process Engine region recovery feature, each Process Engine isolated region configured for region recovery must reside in dedicated data, index and BLOB tablespaces. If you are creating a tablespace for a new object store on an existing system, define the new tablespace with the same tablespace type and storage method used for existing object store tablespaces.
Actual Assigned Name Process Engine Tablespaces user temporary ts system temporary VWDATA_TS (default data tablespace) Configure as LARGE type and automatic storage. VWINDEX_TS (default index tablespace ) Configure as LARGE type and automatic storage. 200 must match the pagesize of VWDATA_TS Record the values in the worksheet. Minimum Minimum Page Size (MB) Actual Created Size Size (KB) 40 must match the pagesize of VWDATA_TS must match the pagesize of VWDATA_TS 8
40
200
102
Actual Assigned Name Process Engine Tablespaces VWBLOB_TS (default blob tablespace) Configure as LARGE type and automatic storage. region X data Data tablespace to be used by an individual PE region configured for recovery. Cannot be shared by any other region. Configure as LARGE type and automatic storage. region X index Index tablespace to be used by an individual PE region configured for recovery. Cannot be shared by any other region and must be separate from the default index tablespace. Configure as LARGE type and automatic storage. 200 must match the pagesize of VWDATA_TS 200 8 Record the values in the worksheet. Minimum Minimum Page Size (MB) Actual Created Size Size (KB) 200 8
103
Actual Assigned Name Process Engine Tablespaces region X blob BLOB tablespace to be used by an individual PE region configured for recovery. Cannot be shared by any other region and must be separate from the default index tablespace. Configure as LARGE type and automatic storage. Record the values in the worksheet. Minimum Minimum Page Size (MB) Actual Created Size Size (KB) 200 8
Creating the DB2 tablespaces for Content Engine: Create four tablespaces for Content Engine on DB2 for Linux, UNIX and Windows. Each additional object store will require an additional tablespace and a unique tablespace user. If you are creating a tablespace for a new object store on an existing system, define the new tablespace with the same tablespace type and storage method used for existing object store tablespaces.
Content Engine Tablespaces GCD_ts (for the GCD database) Configure as LARGE type and automatic storage. cedata_ts (for a single CE object store) Configure as LARGE type and automatic storage. user temporary ts 40 32 (required) 512 32 (required) Actual Assigned Name Minimum Size (MB) 256 Actual Created Size Minimum Page Size (KB) 32 (required)
104
Content Engine Tablespaces system temporary ts
Actual Assigned Name
Actual Created Size
Minimum Page Size (KB) 32 (required)
Configuring DB2 client

Configure the DB2 client. Configuration requirements will be different for Content Engine and Process Engine and will vary between DB2 for Linux, UNIX and Windows and DB2 for z/OS. Installing DB2 client software (Process Engine) Install the DB2 Administration Client or the DB2 Runtime Client. Creating DB2 client instances for Process Engine Depending upon your configuration, create at least one DB2 Client instance for Process Engine. The client instance is referred to as the local instance in the Process Engine installation program. Cataloging the Process Engine DB2 server node Catalog the Process Engine server node for the DB2 database. Creating the Process Engine DB2 database alias on page 106 Create an alias for the Process Engine DB2 for Linux, UNIX and Windows or DB2 for z/OS database. Installing the DB2 for z/OS license and modifying the classpath for Content Engine and Process Engine on page 106 Install the DB2 for z/OS license file on the Content Engine and Process Engine servers and add it to the classpath. Install the license jar in the same location as the JDBC driver jar (db2jcc_license_cisuz.jar). Installing DB2 client software (Process Engine): Install the DB2 Administration Client or the DB2 Runtime Client. Content Engine does not require DB2 client software. Creating DB2 client instances for Process Engine: Depending upon your configuration, create at least one DB2 Client instance for Process Engine. The client instance is referred to as the local instance in the Process Engine installation program. On Windows, a DB2 client instance is automatically created during installation of the client software. Use the default instance or create another for Process Engine. On UNIX, create a DB2 client instance for Process Engine. Cataloging the Process Engine DB2 server node: Catalog the Process Engine server node for the DB2 database. 1. Reboot the server and log on as the instance owner on the Process Engine. 2. Use the db2ca tool, or catalog the DB2 server node as follows:
db2 catalog tcpip node server_alias remote server_name server server_side_instance_tcpip_port_#
For example: db2 catalog tcpip node sampnod remote hqvwais20 server 60004
105
Creating the Process Engine DB2 database alias: Create an alias for the Process Engine DB2 for Linux, UNIX and Windows or DB2 for z/OS database. Use the db2ca tool, or create an alias for the Process Engine DB2 database. Record the alias name in the Installation and Upgrade Worksheet. For example: db2 catalog database PEDBAIX at node aix20nod [as alias name] Installing the DB2 for z/OS license and modifying the classpath for Content Engine and Process Engine: Install the DB2 for z/OS license file on the Content Engine and Process Engine servers and add it to the classpath. Install the license jar in the same location as the JDBC driver jar (db2jcc_license_cisuz.jar).
Verifying the ability to connect to the database

Verify the ability to connect to the Process Engine database. These procedures can be run after initial configuration of the database and immediately prior to installation of Process Engine software. Run these steps on the database server or the client according to whether the database is local to or remote from Process Engine. Verifying the Process Engine database connection (Oracle) Verify that the Oracle database instance used by Process Engine is accessible. How you log on to sqlplus will vary, depending upon how you will choose to run the SQL scripts. Verifying the Process Engine database connection (DB2) on page 107 Verify the connection to the DB2 Process Engine database by executing the following commands to start a command line processor. Verifying the Process Engine database connection (Microsoft SQL Server) on page 108 Take the following steps to verify that the Microsoft SQL Server database instance used by Process Engine is accessible. You must know both the Process Engine database and filegroup names. Make whatever corrections are necessary before proceeding. Verifying the Process Engine database connection (Oracle): Verify that the Oracle database instance used by Process Engine is accessible. How you log on to sqlplus will vary, depending upon how you will choose to run the SQL scripts. This procedure will verify that you can connect to the Oracle database in the same way the Process Engine installation program will. Make whatever corrections are necessary before proceeding. To verify the Process Engine database connection: 1. Run the following at a command prompt on the Process Engine:
su - oracle -c "sqlplus"
2. Enter one of the following commands at the SQLPlus prompt, as follows: v If the Process Engine pre-installation SQL scripts will be run from the Process Engine installation program by prompting for the sys password, type the following command:
106
sys/password as sysdba
v If the SQL scripts will be run from the Process Engine installation program by using operating system authentication, type the following command:
/ as sysdba
3. At the prompt, enter the following SQL command:

SQL> select instance_name, host_name, version from v$instance;
The following represents an example of the information returned: INSTANCE_NAME ---------------HOST_NAME ---------------------------------------------------------------VERSION ----------------p8dbshr HQVWBUCS 10.2.0.2.0 where: v p8dbshr is the instance ORACLE_SID. v HQVWBUCS is the database server name. v 10.2.0.2.0 is the Oracle server version. Verifying the Process Engine database connection (DB2): Verify the connection to the DB2 Process Engine database by executing the following commands to start a command line processor. 1. Log on to the DB2 Control Center tool on the Process Engine, as follows: Windows At a command prompt, start the DB2 Command Line Processor by typing the following command:
db2cmd
and, at the subsequently displayed prompt, enter the following command:

db2
UNIX Log on as the client instance owner and run the following at a command prompt:
db2
2. At the DB2 prompt, enter the following command indicating either the database alias or the instance name:
connect to database_alias or instance_name user f_sw using f_sw password
where: database_alias is the Process Engine DB2 for Linux, UNIX and Windows database alias for remote databases. For local databases, use the database name. instance_name is the Process Engine DB2 for z/OS database name f_sw is the Process Engine runtime user, either the default f_sw user or the assigned alias f_sw password is the runtime users password. DB2 will display the database connection information.
107
The following example shows the database connection command and the information returned:
db2 => connect to pedbinst user f_sw using fswpassword Database Connection Information Database server = DB2/AIX64 9.5.0 SQL authorization ID = F_SW Local database alias = PEDBINST
In this example, the database alias is pedbinst, the user is f_sw, and the f_sw user password is fswpassword. Verifying the Process Engine database connection (Microsoft SQL Server): Take the following steps to verify that the Microsoft SQL Server database instance used by Process Engine is accessible. You must know both the Process Engine database and filegroup names. Make whatever corrections are necessary before proceeding. 1. Log on to the Process Engine as a member of the local Administrators group or a user with equivalent permissions. The user you log on as must also be a database administrator. If the database is remote, the SQL connection must also be a trusted connection. 2. At a command prompt, enter:
osql -E -D DSN
where DSN is the ODBC data source name This command puts Process Engine into osql interactive mode. 3. At the osql prompt, enter:
1> use VWdb 2> go
where VWdb is the Process Engine database name This command verifies that the Process Engine database has been created. If you get another prompt with no error, you are attached to that database. 4. Verify that the correct Process Engine filegroup was created. At the osql prompt, enter:
1> select substring(groupname,1,20) from sysfilegroups where groupname= 'defined filegroup' 2> go
where defined filegroup is the default filegroup A listing of the Process Engine filegroups will display, for example:
___________ vwdata_fg
Application Server administrator installation tasks

The Application Server Administrator must prepare the application servers for IBM FileNet P8 Platform, including planning deployment, creating administrative accounts, and configuring JDBC drivers for both Content Engine and Application Engine. v Review all rows assigned to the Application Server Administrator (ASA) in the Installation and Upgrade Worksheet. While you complete the following preparation tasks, provide values for the rows that are appropriate to your installation.
108
Tip: With the Data Filter AutoFilter command enabled, as it is by default in the shipping worksheet file (p8_worksheet.xls), perform the following actions to quickly see only the properties assigned to a particular Role: Click the AutoFilter drop-down arrow in the Role column header and select ASA. Further filter the result set by clicking the AutoFilter drop-down arrow in any of the other columns and selecting a value or clear a filter by selecting (All). v If you are installing in a non-English environment, review the considerations and procedures in Appendix A, Installing IBM FileNet P8 Platform in a non-English environment, on page 215 before you begin your preparation tasks. v Review the following planning considerations: Application server planning considerations on page 4 Creating Content Engine application server accounts Create new or designate existing application server accounts for Content Engine, as shown in the following table. Configuring WebSphere for Content Engine on page 110 You must prepareIBM WebSphere Application Server before you install Content Engine. You must create a WebSphere profile for the Content Engine application and set the environment variables for the database connection. Configuring WebLogic Server for Content Engine on page 114 This task assumes you have already installed WebLogic Server on the machine where you are going to install and deploy Content Engine. Configuring JBoss Application Server for Content Engine on page 116 You must prepare the server with JBoss Application Server for Content Engine. Configuring WebSphere Application Server for Application Engine or Workplace XT on page 119 You must install WebSphere Application Server on the machine where you are going to install and deploy Application Engine or Workplace XT. Configuring WebLogic Server for Application Engine or Workplace XT on page 119 You must install Oracle WebLogic Server on the machine where you are going to install and deploy Application Engine or Workplace XT. Configuring JBoss Application Server for Application Engine or Workplace XT on page 120 You must install JBoss Application Server on the machine where you are going to install and deploy Application Engine or Workplace XT. Configuring Process Engine clients for ORB on page 120 Process Engine clients require either the IBM or the Sun Object Request Broker (ORB). Configuring the documentation server on page 121 Plan to install IBM FileNet P8 documentation on an application server so that you can access online help from within IBM FileNet P8 applications and use the full-text search feature.
Creating Content Engine application server accounts

Create new or designate existing application server accounts for Content Engine, as shown in the following table.
109
This task should be performed by the Application Server Administrator.

User/Group Application server administrator user name ce_appserver_admin Administrative Console user ce_appserver_console_admin Description An application server administrative account or accounts that can log on to the application server administration console. WebSphere Application Server: ce_appserver_admin must have Administrator permissions throughout the installation process. After installation is complete, you can reduce the accounts permissions to a lesser role, such as Configurator. If your site uses a FederatedLDAP registry, ce_appserver_console_admin must be a unique user across all federated realms. Otherwise, ce_appserver_admin and ce_appserver_console_admin can be the same account. WebLogic: ce_appserver_admin and ce_appserver_console_admin must be different accounts. JBoss does not require an administrative account. Log on to the application server as ce_appserver_admin to perform application tasks such as the following tasks: v Create directory service providers within the application server. v Create JDBC providers and/or data sources for db connectivity. v Deploy the Content Engine application. v Stop and restart servers and cluster members (WebSphere Application Server). v Stop and restart managed servers (WebLogic).
Configuring WebSphere for Content Engine

You must prepareIBM WebSphere Application Server before you install Content Engine. You must create a WebSphere profile for the Content Engine application and set the environment variables for the database connection. 1. Creating the WebSphere profile for Content Engine on page 111 You must create an IBM WebSphere Application Server profile for Content Engine if you do not already have a profile. 2. Specifying the WebSphere environment variables on page 111 You must specify the IBM WebSphere Application Server environment variables so that Content Engine can access its databases. 3. Setting the primary administrative user name on page 113 If you are using IBM WebSphere Application Server federated repositories for LDAP authentication, you must ensure that the name you entered for the WebSphere Application Server primary administrative user name is unique across all realms.
110
4. Setting host aliases for deployment on multiple servers on page 113 If you are deploying Content Engine to multipleIBM WebSphere Application Server servers on the same WebSphere node, you must define the host alias and port numbers. 5. Setting permissions for the Configuration Manager user on page 113 You must create an application server account with certain directory permissions that you will use later on to start the Configuration Manager tool. Creating the WebSphere profile for Content Engine: You must create an IBM WebSphere Application Server profile for Content Engine if you do not already have a profile. To create the WebSphere profile for Content Engine: 1. Run the command script at one of the following (default) locations to create a new profile.
Option AIX Other UNIX Windows Description /usr/IBM/WebSphere/AppServer/ manageprofiles.sh /opt/IBM/WebSphere/AppServer/ manageprofiles.sh C:\Program Files\IBM\WebSphere\AppServer\ bin\manageprofiles.bat
2. Record the path to your new profile in the Application server installation directory property in your installation worksheet, as you must specify the path later when you configure Content Engine. Specifying the WebSphere environment variables: You must specify the IBM WebSphere Application Server environment variables so that Content Engine can access its databases. Refer to the IBM FileNet P8 Hardware and Software Requirements for information on the JDBC driver file for the database type that you need for the Global Configuration Data (GCD) or for an object store you will be creating later. To specify the WebSphere environment variables: 1. Install JDBC drivers on the server where WebSphere Application Server is installed. a. Obtain the JDBC drivers for your database type. DB2 Find the latest version of the Redistributable DB2 JDBC Driver Type 4 driver from the IBM Web site by searching for JDBC Type 4.
Microsoft SQL Server Find theSQL Server JDBC Driver 2.0 at Microsoft Support. Oracle Access the http://www.oracle.com/technology/software/tech/ java/sqlj_jdbc/index.html Web site and find the JDBC driver file that matches the version of the JDK that is installed on the on the server where WebSphere Application Server is installed. b. Copy the JDBC driver file to the following suggested location: UNIX /opt/jars
111
Do not copy the file to ...WebSphere/AppServer/lib/ext. Windows C:\jars Do not copy the file to ...WebSphere\AppServer\lib\ext. 2. Start the WebSphere Application Server administrative console and log on to your Content Engine profile as ce_appserver_console_admin, the Administrator Console User. 3. Navigate to Environment WebSphere Variables and specify the JDBC driver path: a. Select Cell scope from the All scopes list. b. Click New to create a WebSphere Application Server variable whose name is one of the JDBC environment variables shown in the Database environment variables table below. c. Set the value of the variable to the JDBC driver path that you specified when you installed the JDBC drivers on the IBM WebSphere Application Server machine. d. Save your change to the master configuration. e. Select Node scope from the All scopes list. f. In the table of substitution variables, click the item name in the Name column that corresponds to the JDBC environment variable for your database type in the Database environment variables table below.
Table 1. Database environment variables Database SQL Server JDBC Environment Variable WebSphere Application Server 6.1 MSSQLSERVER_JDBC _DRIVER_PATH WebSphere Application Server 7 MICROSOFT_JDBC _DRIVER_PATH
Oracle DB2
ORACLE_JDBC _DRIVER_PATH DB2UNIVERSAL_JDBC _DRIVER_PATH
g. Set the value of the name_JDBC_DRIVER_PATH item to the JDBC driver path you specified (/opt/jars or C:\jars). h. Save your changes to the master configuration. 4. Navigate to Servers Application servers server1 Java and Process Management Process Definition Java Virtual Machine, and set the initial and maximum heap sizes, where server1 is the name of the server where you will deploy Content Engine. a. Set the values for the initial and maximum heap sizes:
Parameter Initial Heap Size Value (in MB) At least 512
112
Parameter Maximum Heap Size
Value (in MB) 1024 or a size consistent with available RAM on the machine where WebSphere Application Server is installed
b. Save your changes to the master configuration. 5. Optional: Navigate to Servers Application Servers server1 and set the transaction timeout value: a. Click the Runtime tab, and then click Transaction Service. b. Change the Total transaction lifetime timeout parameter value to at least 600 (seconds), and click Apply. Important: If the timeout value is not large enough, some administrative processes (such adding an expansion product) might fail. Changing the transaction lifetime timeout in the Runtime tab is not permanent. The setting reverts to the default when the application server is restarted, and subsequent administrative processes might fail. To make the change permanent, continue at the next step. c. Click the Configuration tab. In the Container Settings section, expand Container Services. d. Change the Total transaction lifetime timeout parameter value to at least 600 (seconds), and click Apply. 6. Repeat this procedure as needed for any object store that uses a different database type. Setting the primary administrative user name: If you are using IBM WebSphere Application Server federated repositories for LDAP authentication, you must ensure that the name you entered for the WebSphere Application Server primary administrative user name is unique across all realms. Setting host aliases for deployment on multiple servers: If you are deploying Content Engine to multipleIBM WebSphere Application Server servers on the same WebSphere node, you must define the host alias and port numbers. To set the host alias: 1. Log in to the WebSphere administrative console. 2. Navigate to Environment Virtual Hosts default host Host Aliases. 3. If you are using SSL, add an alias for the SSL port number, such as port 9081. 4. Add an alias for the non-SSL port number, such as port 9444. 5. Click Apply. Setting permissions for the Configuration Manager user: You must create an application server account with certain directory permissions that you will use later on to start the Configuration Manager tool. To set permissions for the Configuration Manager user:
113
Set permissions for the Configuration Manager user (config_mgr_user) on the WebSphere Application Server profile directory and all its subdirectories where Content Engine will be deployed:
Option UNIX Windows Description Read, write, and execute permissions Read & Execute, and Write permission
Configuring WebLogic Server for Content Engine

This task assumes you have already installed WebLogic Server on the machine where you are going to install and deploy Content Engine. Before installing and deploying Content Engine on a WebLogic Server machine, you must create a WebLogic Server domain and install JDBC drivers (The drivers must be installed on the WebLogic Server machine whether your database is collocated or not). To configure WebLogic Server: 1. Use the WebLogic Configuration Wizard to create a WebLogic Server domain for Content Engine. In the examples below, use the domain name FNCEDomain. Keep the following in mind as you configure the domain: a. Set the server start mode to Production mode. b. Select the appropriate Java Development Kit (JDK) for your environment, as specified in the IBM FileNet P8 Hardware and Software Requirements. 2. Use the WebLogic Administration Console to set the following: a. Optional: Create a WebLogic Server authentication provider. You can use the Content Engine Configuration Manager tool to create a WebLogic Server authentication provider later on, or you can create the provider now by using the WebLogic Console. Important: In some situations (for example, if you have a single-sign-on provider, such as Netegrity SiteMinder), Configuration Manager cannot configure a WebLogic authentication provider. b. For performance reasons set the parameters that control searches within the authentication provider, as shown in the following table:
Parameter Value Description Group searches are unlimited in depth Only direct group members are found
Group Membership Searching unlimited Max Group Membership Search Level 0
If you encounter performance problems, change the Group Membership Searching parameter value to limited. c. If you do not use Configuration Manager to configure your LDAP settings, set the Control Flag value. Set the Control Flag to REQUIRED to allow logons to FNCEDomain by LDAP-authenticated users in the Default Authenticator who are not in FNCEDomains active security realm. The Configuration Manager tool will set this flag when you run the Configure LDAP task. d. If you are using multiple authentication providers in an Active Directory environment of multi-forest domains, reorder (as needed) the list of
114
providers so that the most-frequently-used provider is first in the list, and the least-frequently-used is last. Reordering is necessary to prevent logon failures when IBM FileNet P8 Workplace is being accessed by many users simultaneously. e. Specify the following heap sizes for the JVM: Initial Java heap size (-Xms): 512 MB Maximum Java heap size (-Xmx): 1024 MB 3. Refer to the IBM FileNet P8 Hardware and Software Requirements guide for information on the JDBC driver file for the database type that you need for the GCD or for an object store you will be creating later. 4. Depending on your database, use one of the following procedures to install the JDBC drivers. DB2 a. Obtain the latest version of the Redistributable DB2 JDBC Driver Type 4 driver from the IBM web site by searching for JDBC Type 4. b. Add the db2jcc.jar and db2jcc_license_cu.jar files to the WebLogic Server classpath. by editing the file startWebLogic.cmd or startWebLogic.sh for the WebLogic Server domain you created. For example:
set CLASSPATH=%CLASSPATH%;c:\db2\jdbc\db2jcc.jar;c:\db2\ jdbc\db2jcc_license_cu.jar
Microsoft SQL Server a. Download and unzip SQL Server Driver JDBC Driver from Microsoft Support to a directory jdbc_path on your application server machine, such as: UNIX /opt/jars Windows C:\jars b. Perform the following step, depending on your operating system type. UNIX Edit the file startWebLogic.sh by inserting the following two lines immediately after the first occurrence of the line CLASSPATH=...
set JDBC_PATH=jdbc_path\sqljdbc_1.0\enu\sqljdbc.jar set CLASSPATH=%JDBC_PATH%;%CLASSPATH%
Windows Edit the file startWebLogic.cmd (by default, in the directory C:\bea\user_projects\domains\bin\FNCEDomain ) for the WebLogic domain you created. Insert the following two lines immediately after the first occurrence of the line CLASSPATH=...
Oracle a. Check to see if the Oracle JDBC Driver file is already on your WebLogic machine by searching for ojdbc##.jar in the
115
wls_install_path/server/lib directory, where wls_install_path is the WebLogic Server installation path, such as C:\bea\weblogic92. b. If no Oracle JDBC Driver file is present, download the file (the one that matches the version of the JDK on your WebLogic Server machine) from the Oracle JDBC Driver Downloads web site to a directory on the WebLogic machine. Restriction: If you intend to install AddOns (extensions to IBM FileNet P8 core components), and your Content Engine database is Oracle, your Oracle JDBC Driver file requirements might be more restrictive. For the required version and patch number, see the IBM FileNet P8 Hardware and Software Requirements. c. From the Oracle web site, apply the patch Oracle Patch Ojdbc##.jar. d. Edit the file startWebLogic.cmd or startWebLogic.sh for the WebLogic domain you created. Add the following lines immediately after the first line that starts with set CLASSPATH. UNIX
JDBC_PATH=<jdbc_path>/ojdbc##.jar CLASSPATH=$JDBC_PATH:$CLASSPATH
Windows
set JDBC_PATH=<jdbc_path>\ojdbc##.jar set CLASSPATH=%JDBC_PATH%;%CLASSPATH%
5. If your application server uses the IBM JVM, edit the JAVA_OPTIONS variable to improve performance. AIX (WebLogic version 9.2 with IBM Java 5 SR2 JDK only) Add the following line to the setDomainEnv.sh file file. Do not type any line breaks.
JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0"
UNIX Immediately before the SAVE_JAVA_OPTIONS=$JAVA_OPTIONS line in the startWebLogic.sh file, insert the following line. Do not type any line breaks.
JAVA_OPTIONS="$JAVA_OPTIONS -Dprogram.name=$PROGNAME -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5"
Windows Immediately before the set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS% line in the startWebLogic.cmd file, insert this line. Do not type any line breaks.
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dprogram.name=%PROGNAME% -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5
6. Stop and then start WebLogic Server. 7. Give the Configuration Manager user, config_mgr_user, the following permissions: a. Read, write, and execute permission on the domain directory ../users_projects/domains/your_domain. b. Read and execute permission on the ../common/bin directory.
Configuring JBoss Application Server for Content Engine

You must prepare the server with JBoss Application Server for Content Engine. Ensure that JBoss Application Server is installed on the machine where you intend to deploy Content Engine.
116
To prepare the web application server: 1. Navigate to the configuration file set directory.
Option Standard deployment Cluster deployment Description jboss_install_dir/server jboss_install_dir/all
2. Create a new configuration file set by copying the configuration file set to a new directory. For JBoss 5.0.1, the configuration file set is the standard subdirectory. For JBoss versions other than 5.0.1, the configuration file set is the default subdirectory.
Option Standard deployment Description Copy the configuration file set to a new directory within the /server directory. For example, copy the files to jboss_install_dir/server/server1. Copy the configuration file set to a new directory within the /all directory. For example, copy the files to jboss_install_dir/all/server1.
Cluster deployment
where jboss_install_dir is the directory where JBoss is installed. 3. Record the path to your configuration file set in your installation worksheet for the Server configuration directory property. 4. Edit the jboss_install_dir/bin/run.conf configuration file. a. Add a line to specify the path to the JAVA Development Kit (JDK) on the machine where JBoss Application Server is installed, as shown in the following example:
JAVA_HOME="path_to_Java_JDK"
b. In the JAVA_OPTS line, change the -Xms and -Xmx values from -Xms128m -Xmx512m to -Xms512m -Xmx1024m. c. Save your edits. 5. (JBoss 4.x only) Edit the jboss_install_dir/server/server1/conf/loginconfig.xml file, where server1 is the name of the JBoss server instance. a. In the <!DOCTYPE declaration, change "http://www.jboss.org/j2ee/dtd/ security_config.dtd" to jboss_install_dir/docs/dtd/ security_config.dtd". b. Save your change. 6. If your application server uses the IBM Java Virtual Machine (JVM,) edit the startup script file to improve performance. a. Change the JAVA_OPTS settings. UNIX Edit JBOSS_HOME/bin/run.sh. Find the JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME" line in run.sh, and change it to this line, without a carriage return:
JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME -Dfilenet .pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5"
Windows Edit JBOSS_HOME\bin\run.bat.
117
Find the set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% line in run.bat, and change it to this line, without a carriage return:
set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -Dfilenet .pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5
b. Save your edit. 7. Refer to theIBM FileNet P8 Hardware and Software Requirements for information on the JDBC driver file for the database type that you need for the GCD or for an object store you will be creating later. 8. Install JDBC drivers on the JBoss Application Server machine, as follows: a. Obtain the JDBC drivers, depending on your database type. DB2 Find the latest version of the Redistributable DB2 JDBC Driver Type 4 driver from the IBM Web site by searching for JDBC Type 4.
Microsoft SQL Server Find the Microsoft JDBC Driver, sqljdbc.jar, at Microsoft Support. Oracle Access the Oracle JDBC Driver Downloads Web site and find the JDBC driver file that matches the version of the JDK on the JBoss Application Server machine. b. Place the file JDBC driver file in the CLASSPATH. Standard deployment Copy the JDBC driver file to the jboss_install_dir/server/ server1/lib directory. Cluster deployment Copy the JDBC driver file to the jboss_install_dir/all/server1/ lib directory. 9. If you are deploying multiple instances of Content Engine of the same server, do the following for each additional instance: a. Copy the configuration file set that you just created and modified from the jboss_install_dir/server/server1 directory to a new directory. Use a separate directory for each instance. For example, copy the jboss_install_dir/server/server1 directory to jboss_install_dir/ server/server2 and jboss_install_dir/server/server3. b. Assign unique port numbers to each instance. Refer to your JBoss Application Server documentation for details. 10. If it is not already running, start the web application server as follows, and leave the command window open:
Option UNIX and JBoss version 4.01 UNIX and JBoss version 4.23 or higher Windows and JBoss version 4.01 Windows and JBoss version 4.23 or higher Description ./run.sh -c server1 ./run.sh -c server1 -b 0.0.0.0 run.bat -c server1 run.bat -c server1 -b 0.0.0.0
Configuring JBoss Application Server clusters JBoss Application Server servers can be grouped together into a cluster for performance or to provide high availability. This guide provides on minimal instructions for setting up a JBoss Application Server cluster. Configuring JBoss Application Server clusters:
118
JBoss Application Server servers can be grouped together into a cluster for performance or to provide high availability. This guide provides on minimal instructions for setting up a JBoss Application Server cluster. Refer to the IBM FileNet P8 High Availability Technical Notice for details on how to set up your IBM FileNet P8 system using clusters, farms, and other high availability software and hardware. Because JBoss Application Server clusters do not have an administrative server, you will choose a single JBoss Application Server on which to install and configure the first instance of Content Engine, then copy the necessary files to the rest of the nodes in the cluster.
Configuring WebSphere Application Server for Application Engine or Workplace XT

You must install WebSphere Application Server on the machine where you are going to install and deploy Application Engine or Workplace XT. Application Engine or Workplace XT can be collocated with Content Engine as long as the server is appropriately sized. However, each instance of the Application Engine or Workplace XT and each instance of the Content Engine must run in its own JVM. For assistance in sizing your system, contact your service representative. To configure WebSphere Application Server: 1. Verify that the application server is set to use JSESSIONID as default cookie name. To avoid forcing end users to log in individually applets such as Process Designer, Search Designer, and Process Simulator, configure the application server to use JSESSIONID as cookie name, and not use application-unique cookie names. Using JSESSIONID is typically the default setting for the supported application servers. Both Application Engine and Workplace XT use cookie names to pass session information between Application Engine or Workplace XT and the client browser. 2. Determine the Initial and Maximum Heap Size. Refer to your application server vendors recommendation for Initial and Maximum heap size values. You will use this information when you configure WebSphere Application Server after you install Application Engine or Workplace XT. For IBM specific recommendations, see the IBM FileNet P8 Performance Tuning Guide.
Configuring WebLogic Server for Application Engine or Workplace XT

You must install Oracle WebLogic Server on the machine where you are going to install and deploy Application Engine or Workplace XT. Application Engine or Workplace XT can be collocated with Content Engine as long as the server is appropriately sized. However, each instance of Application Engine or Workplace XT and each instance of the Content Engine must run in its own JVM. For assistance in sizing your system, contact your service representative. To configure WebLogic Server: 1. Verify that the application server is set to use JSESSIONID as default cookie name. To avoid forcing end users to log in individually applets such as Process Designer, Search Designer, and Process Simulator, configure the application server to use JSESSIONID as cookie name, and not use application-unique cookie names. Using JSESSIONID is typically the default setting for the
119
supported application servers. Both Application Engine and Workplace XT use cookie names for passing session information between Application Engine or Workplace XT and the client browser. 2. Create a WebLogic Server domain before installing and deploying Application Engine or Workplace XT. Refer to your WebLogic Server documentation for detailed instructions. Important: You will perform further configuration on Workplace XT after you perform the installation. 3. Enable trust between the Content Engine WebLogic domain and the Application Engine or Workplace XT WebLogic domain. If you have already configured a trust on the Content Engine, perform these steps only on the Application Engine or Workplace XT server. You must use the same password as the one used on the Content Engine. a. Prepare the WebLogic Administration Console for editing. b. In the advanced security settings for your domain, enter a password for the domain. You must enter the same password for both the Content Engine domain and the Application Engine or Workplace XT domain. c. Save and activate your changes. d. Restart the server if needed. e. Repeat this procedure in each domain for which you want to enable trust. Important: If you are enabling this feature in a managed server environment, you must stop the Administration server and all the Managed Servers in both domains and then restart them. If this step is not performed, servers that were not rebooted will not trust the servers that were rebooted. Refer to your BEA documentation for more information.
Configuring JBoss Application Server for Application Engine or Workplace XT

You must install JBoss Application Server on the machine where you are going to install and deploy Application Engine or Workplace XT. Application Engine and Workplace XT can be collocated with Content Engine as long as the server is appropriately sized. However, each instance of Application Engine or Workplace XT and each instance of the Content Engine must run in its own JVM. For assistance in sizing your system, contact your service representative. To configure JBoss Application Server: Verify that the application server is set to use JSESSIONID as default cookie name. To avoid forcing end users to log in individually applets such as Process Designer, Search Designer, and Process Simulator, configure the application server to use JSESSIONID as cookie name, and not use application-unique cookie names. Using JSESSIONID is typically the default setting for the supported application servers. Both Application Engine and Workplace XT use cookie names for passing session information between Application Engine or Workplace XT and the client browser. Important: You will perform further configuration on JBoss Application Server after you perform the installation.
Configuring Process Engine clients for ORB

Process Engine clients require either the IBM or the Sun Object Request Broker (ORB).
120
This applies to the following configurations: v J2EE application server clients such as Workplace or Workplace XT v Content Engine when using the workflow subscription processor to launch workflows v Non-J2EE and custom applications The default ORB varies by application server, so in most instances no changes are required. However, in certain configurations you must override the defaults as follows:
JBoss Application Server Installed via JEMS No changes are required if you installed the JBoss Enterprise Middleware System Installer JBoss Application Server by installing the with IBM or Sun JVM JBoss Enterprise Middleware Software with the Default option. Oracle WebLogic Server with the Sun JVM WebLogic Server with the JRockit JVM No changes are required. Replace the default JBoss Application Server ORB with the Sun ORB by adding the following code to your application server startup file. Enter without carriage returns: set JAVA_OPTIONS=%JAVA_OPTIONS% -Dorg.omg.CORBA.ORBClass =com.sun.corba.se.impl.orb.ORBImpl set JAVA_OPTIONS=%JAVA_OPTIONS% -Dorg.omg.CORBA.ORBSingletonClass =com.sun.corba.se.impl.orb.ORBSingleton
Configuring the documentation server

Plan to install IBM FileNet P8 documentation on an application server so that you can access online help from within IBM FileNet P8 applications and use the full-text search feature. Ensure that you have a supported application server. The application server can be one of the servers that you already prepared for Content Engine or Application Engine. After you have chosen the application server for the documentation, you can specify the value for the documentation URL. This is useful when recording the installation properties for the other IBM FileNet P8 components. To determine the documentation URL: 1. Choose the application server for the IBM FileNet P8 documentation. 2. Make a note of the server URL. This includes the server name and the port number in the following format: http://server_name:port/ecm_help. 3. Search the Installation and Upgrade Worksheet for documentation server properties in the Property or Parameter column. 4. Enter the URL value into the worksheet for each instance of that property for the components you are going to install.
121
122
Planning and preparing for IBM FileNet P8 Platform upgrade

To prepare to upgrade your IBM FileNet P8 Platform installation, you must review the upgrade planning information to determine what kind of upgrade you will carry out. You must also complete the prerequisite tasks assigned to the various Roles. Planning the upgrade Carefully review the information provided to plan your IBM FileNet P8 system upgrade. Review this information thoroughly before you start to upgrade IBM FileNet P8 components or required vendor software. Performing the required upgrade preparation tasks on page 157 To efficiently carry out the required upgrade preparation tasks, you must assign your staff to carry out the tasks that are organized by administrative role.
Planning the upgrade

Carefully review the information provided to plan your IBM FileNet P8 system upgrade. Review this information thoroughly before you start to upgrade IBM FileNet P8 components or required vendor software. Before you begin to upgrade the IBM FileNet P8 Platform, review the following information. Upgrade overview Several methods can be used to upgrade components to the 4.5 versions of the IBM FileNet Content Manager and IBM FileNet Business Process Manager products. Upgrading planning considerations on page 150 Review all upgrade planning information related to requirements for upgrading anIBM FileNet P8 Platform system and expansion products, as well as other vendor products associated with the IBM FileNet P8 Platform. Definition of upgrade roles on page 154 Your organization may have different roles, and some of the responsibilities of listed roles will vary from those assigned by default. Using the installation and upgrade worksheet on page 155 The Installation and Upgrade Worksheet is a Microsoft Excel spreadsheet (p8_worksheet.xls). The worksheet describes the properties and parameters required to complete IBM FileNet P8 installation, upgrade, and configuration programs, and provides a way to record the values you assign to these properties and parameters.
Upgrade overview
Several methods can be used to upgrade components to the 4.5 versions of the IBM FileNet Content Manager and IBM FileNet Business Process Manager products. The 4.5 version of Content Manager and FileNet Business Process Manager, which contains the core IBM FileNet P8 Platform components (Content Engine 4.5, Content Search Engine 4.5, Process Engine 4.5, and Application Engine 4.0.2) supports upgrades from either the 3.5 or 4.0 version series.
123
This support also covers the associated expansion components, such as those currently packaged as part of the Content Manager and FileNet Business Process Manager products, for example, IBM FileNet Workplace XT, Rendition Engine, IBM FileNet Content Federation Services, IBM FileNet Process Analyzer, and IBM FileNet Process Simulator. Other associated expansion products, such as IBM FileNet Records Manager, also support these dual upgrade starting points. See General requirements for all FileNet P8 Platform systems on page 151 for a list of product-component versions from which you can start an upgrade. Standard upgrading from version 3.5 or version 4 A standard upgrade sequence assumes that you will complete the upgrade of all installed components in one session, for example, over the course of a weekend. Staged upgrading from version 4 only If you want to upgrade your version 4 IBM FileNet P8 environment so that the entire system is offline only for short intervals, you can upgrade in stages. For each stage, you stop the system, upgrade specific components, and then restart the system. You can run your production FileNet environment after each stage. Automatic upgrading of Content Engine on page 150 Upon deploying version 4.5.1 of Content Engine, the upgrade of the Global Configuration Data (GCD) and the object stores will proceed without user input.
Standard upgrading from version 3.5 or version 4

A standard upgrade sequence assumes that you will complete the upgrade of all installed components in one session, for example, over the course of a weekend. The flow of procedural task topics in the upgrade section of this guide reflects a sequence that supports a standard upgrade from either the 3.5 or 4 product version.
Staged upgrading from version 4 only

If you want to upgrade your version 4 IBM FileNet P8 environment so that the entire system is offline only for short intervals, you can upgrade in stages. For each stage, you stop the system, upgrade specific components, and then restart the system. You can run your production FileNet environment after each stage. To upgrade in stages, you must already be running version 4.0 or later of the core IBM FileNet P8 Platform components and the supporting versions of expansion products. This means that you can upgrade one component and still have a working configuration without upgrading all components during the same upgrade session. Upgrade stages do not necessarily follow a specific sequence. You can upgrade core components in an order that fits your scheduling or resource requirements. The following tables and flow charts represent three staged upgrade scenarios. They show the relationship of particular components to one another and point out upgrade dependencies. Unless otherwise noted, components specified for upgrade in a particular stage table must be upgraded together. For example, when you upgrade Process Engine, you must also upgrade Process Analyzer and Process Simulator. Important: Staged upgrades can impact how and when you apply Content Engine, Content Search Engine, and Process Engine Client files to various server and client computers.
124
Staged upgrade scenario 1: upgrading Application Engine or Workplace XT first One option for an IBM FileNet P8 staged upgrade is to begin by upgrading your IBM FileNet Application Engine or IBM FileNet Workplace XT component. You can then redeploy the Workplace or Workplace XT application without immediately upgrading the other core IBM FileNet P8 components. At your discretion, your users can start working again while you prepare for the next stage of the systemwide upgrade. Staged upgrade scenario 2: upgrading Content Engine first on page 134 One option for an IBM FileNet P8 staged upgrade is to begin by upgrading your IBM FileNet Content Engine component, which includes server and client software. You can then run this upgraded software with other core IBM FileNet P8 components that are not yet upgraded. At your discretion, your users can start working again while you prepare for the next stage of the systemwide upgrade. Staged upgrade scenario 3: upgrading Process Engine first on page 143 One option for an IBM FileNet P8 staged upgrade is to begin by upgrading your IBM FileNet Process Engine component, which includes server and client software. You can then run this upgraded software with other core IBM FileNet P8 components that are not yet upgraded. At your discretion, your users can start working again while you prepare for the next stage of the systemwide upgrade. Staged upgrade scenario 1: upgrading Application Engine or Workplace XT first: One option for an IBM FileNet P8 staged upgrade is to begin by upgrading your IBM FileNet Application Engine or IBM FileNet Workplace XT component. You can then redeploy the Workplace or Workplace XT application without immediately upgrading the other core IBM FileNet P8 components. At your discretion, your users can start working again while you prepare for the next stage of the systemwide upgrade. The following high-level graphic shows how such an upgrade can be completed from this starting point.
125
Stage 1:
Begin the upgrade Upgrade Application Engine OR Upgrade Workplace XT
The system is operational
Stage 2:
Continue the upgrade
Option 1
Option 2
Upgrade Content Engine and Content Search Engine
Upgrade Process Engine
Stage 3:
Complete the upgrade Upgrade Process Engine Upgrade Content Engine and Content Search Engine
Figure 2. Staged upgrade scenario 1: upgrading Application Engine or Workplace XT first
The following tables describe which components you can upgrade in each stage and in what order if you want to upgrade Application Engine or Workplace XT first. Unless otherwise noted, components that are described in these tables must be upgraded together. For example, when you upgrade IBM FileNet Process Engine, you must also upgrade IBM FileNet Process Analyzer and IBM FileNet Process Simulator. After you upgrade Application Engine or Workplace XT and related components in stage 1, you must decide whether to upgrade IBM FileNet Content Engine or IBM FileNet Process Engine in the next stage. Stage 1: upgrading Application Engine or Workplace XT In stage 1 of this scenario, you upgrade the Application Engine or Workplace XT software.
126
You can optionally upgrade related components in this stage or wait until later as described in the table.
Table 2. Stage 1: upgrading Application Engine or Workplace XT Starting version Content Engine 4.0.1 or 4.5.0 IBM FileNet Content Search Engine 4.0.1 or 4.5.0 IBM FileNet Content Federation Services 4.0.0 or 4.5.0 IBM FileNet Records Manager 4.0.0 or 4.5.0 Upgrade version Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Comments
FileNet Records Manager 4.5.0
Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required. Deploy Workplace 4.0.2. If you are already running version 4.0.2, no additional upgrade is required. Deploy Workplace XT 1.1.4. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT.
Application Engine 4.0.1 or 4.0.2
Application Engine 4.0.2
Workplace XT 1.1.2 or 1.1.3 IBM FileNet P8 eForms 4.0.1
Workplace XT 1.1.4 FileNet P8 eForms 4.0.2
Process Engine 4.0.3 or 4.5.0 Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0
Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage.
IBM FileNet Business Process Defer upgrading in this stage. Business Process Framework Framework 4.1.0 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available. IBM FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1 FileNet Connector for Microsoft SharePoint 2.2.1 Upgrading is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade.
IBM Enterprise Content Management Widgets 4.5.1
IBM ECM Widgets 4.5.1
127
Table 2. Stage 1: upgrading Application Engine or Workplace XT (continued) Starting version IBM Lotus Quickr 1.0

Upgrade version Lotus Quickr 1.0
Comments If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
FileNet P8 Documentation 4.0.3 or 4.5.0
FileNet P8 Documentation 4.5.1
After you complete this upgrade stage, your system is operational even though the FileNet P8 upgrade is not complete. Now you must decide whether to upgrade Content Engine or Process Engine in stage 2. Stage 2, option 1: continuing the upgrade by upgrading Content Engine The following table describes which components you can upgrade with Content Engine in stage 2.
Table 3. Stage 2, option 1: continuing the upgrade by upgrading Content Engine Starting version Content Engine 4.0.1 or 4.5.0 Upgrade version Content Engine 4.5.1 Comments Also upgrade Content Engine Client to version 4.5.1 on computers that are running the following components: v Application Engine v Workplace XT v Process Engine v FileNet Records Manager v Business Process Framework v Custom clients IBM FileNet Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 or 4.5.0 Content Search Engine 4.5.1 Also upgrade Content Search Engine Client to version 4.5.1 on Content Engine servers.
Content Federation Services 4.5.1 FileNet Records Manager 4.5.0 unless upgraded in stage 1. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required.
Application Engine 4.0.1 or 4.0.2 Workplace XT 1.1.2 or 1.1.3 FileNet P8 eForms 4.0.1
Upgraded in stage 1. Upgraded in stage 1. FileNet P8 eForms 4.0.2 unless upgraded in stage 1. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT.
Process Engine 4.0.3 or 4.5.0
Defer upgrading in this stage.
128
Table 3. Stage 2, option 1: continuing the upgrade by upgrading Content Engine (continued) Starting version Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Business Process Framework 4.1.0 Upgrade version Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Business Process Framework 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available. FileNet Connector for Microsoft SharePoint 2.2.1 unless upgraded in stage 1. Upgrading is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage. Comments
FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1
IBM ECM Widgets 4.5.1 unless upgraded in stage 1.
Lotus Quickr 1.0
Lotus Quickr 1.0 unless installed in stage 1. FileNet P8 Documentation 4.5.1 unless upgraded in stage 1.
FileNet P8 Documentation 4.0.3 or 4.5
After you complete this upgrade stage 2 option, your system is operational. Continue with upgrading Process Engine in stage 3. Stage 2, option 2: continuing the upgrade by upgrading Process Engine The following table describes which components you can upgrade with Process Engine in stage 2.
Table 4. Stage 2, option 2: continuing the upgrade by upgrading Process Engine Starting version Content Engine 4.0.1 or 4.5.0 Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 Upgrade version Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Comments
129
Table 4. Stage 2, option 2: continuing the upgrade by upgrading Process Engine (continued) Starting version FileNet Records Manager 4.0.0 or 4.5.0 Upgrade version FileNet Records Manager 4.5.0 unless upgraded in a previous stage. Comments Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required.
Upgraded in stage 1. Upgraded in stage 1. FileNet P8 eForms 4.0.2 unless upgraded in stage 1. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. Also upgrade Process Engine Client to version 4.5.1 on computers that are running the following components: v Content Engine v Application Engine v Workplace XT v FileNet Records Manager v Business Process Framework v Custom clients
Process Engine 4.5.1
Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0
Process Analyzer 4.5.1 Process Simulator 4.5.1 IBM Cognos Now 4.6 The existing Business Activity Monitor component contains an older version of Cognos Now. When you upgrade to Cognos Now 4.6 and then upgrade to Process Analyzer 4.5.1, your Business Activity Monitor installation is replaced by a new Process Activity Monitor feature. Business Process Framework 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available.
Business Process Framework 4.1.0
130
Table 4. Stage 2, option 2: continuing the upgrade by upgrading Process Engine (continued) Starting version FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1 Upgrade version FileNet Connector for Microsoft SharePoint 2.2.1 unless upgraded in stage 1. Comments Upgrading is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
Lotus Quickr 1.0
Lotus Quickr 1.0 unless installed in stage 1. FileNet P8 Documentation 4.5.1 unless upgraded in stage 1.
After you complete this upgrade stage 2 option, your system operational. Continue with upgrading Content Engine in stage 3. Stage 3, option 1: completing the upgrade by upgrading Process Engine The following table describes which components you can upgrade with Process Engine in stage 3.
Table 5. Stage 3, option 1: completing the upgrade by upgrading Process Engine Starting version Content Engine 4.0.1 or 4.5.0 Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 Upgrade version Upgraded in stage 2. Upgraded in stage 2. Upgraded in stage 2. FileNet Records Manager 4.5.0 unless upgraded in a previous stage. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required. Comments
Upgraded in stage 1. Upgraded in stage 1. FileNet P8 eForms 4.0.2 unless upgraded in a previous stage. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT.
131
Table 5. Stage 3, option 1: completing the upgrade by upgrading Process Engine (continued) Starting version Process Engine 4.0.3 or 4.5.0 Upgrade version Process Engine 4.5.1 Comments Also upgrade Process Engine Client to version 4.5.1 on computers that are running the following components: v Content Engine v Application Engine v Workplace XT v FileNet Records Manager v Business Process Framework v Custom clients Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Process Analyzer 4.5.1 Process Simulator 4.5.1 IBM Cognos Now 4.6 The existing Business Activity Monitor component contains an older version of Cognos Now. When you upgrade to Cognos Now 4.6 and then upgrade to Process Analyzer 4.5.1, your Business Activity Monitor installation is replaced by a new Process Activity Monitor feature. Business Process Framework 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available. Upgrading is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
FileNet Connector for Microsoft SharePoint 2.2.1 unless upgraded in a previous stage. IBM ECM Widgets 4.5.1 unless upgraded in a previous stage.
Lotus Quickr 1.0
Lotus Quickr 1.0 unless installed in a previous stage. FileNet P8 Documentation 4.5.1 unless upgraded in a previous stage.
After you complete stage 3 option 1, your FileNet P8 upgrade is complete.
132
Stage 3, option 2: completing the upgrade by upgrading Content Engine The following table describes which components you can upgrade along with Content Engine in stage 3.
Table 6. Stage 3, option 2: completing the upgrade by upgrading Content Engine Starting version Content Engine 4.0.1 or 4.5.0 Upgrade version Content Engine 4.5.1 Comments Also upgrade Content Engine Client to version 4.5.1 on computers that are running the following components: v Application Engine v Workplace XT v Process Engine v FileNet Records Manager v Business Process Framework v Custom clients Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 or 4.5.0 Content Search Engine 4.5.1 Also upgrade Content Search Engine Client to version 4.5.1 on Content Engine servers.
Content Federation Services 4.5.1 FileNet Records Manager 4.5.0 unless upgraded in a previous stage. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required.
Upgraded in stage 1. Upgraded in stage 1. FileNet P8 eForms 4.0.2 unless upgraded in a previous stage. Upgraded in stage 2. Upgraded in stage 2. Upgraded in stage 2. Upgraded in stage 2. Upgraded in stage 2. FileNet Connector for Microsoft SharePoint 2.2.1 unless upgraded in a previous stage. Upgrade is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT.
Process Engine 4.0.3 or 4.5.0 Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Business Process Framework 4.1.0 FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1
133
Table 6. Stage 3, option 2: completing the upgrade by upgrading Content Engine (continued) Starting version IBM ECM Widgets 4.5.1 Upgrade version IBM ECM Widgets 4.5.1 unless upgraded in a previous stage. Comments No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
Lotus Quickr 1.0
After you complete stage 3 option 2, your FileNet P8 upgrade is complete. Staged upgrade scenario 2: upgrading Content Engine first: One option for an IBM FileNet P8 staged upgrade is to begin by upgrading your IBM FileNet Content Engine component, which includes server and client software. You can then run this upgraded software with other core IBM FileNet P8 components that are not yet upgraded. At your discretion, your users can start working again while you prepare for the next stage of the systemwide upgrade. The following high-level graphic shows how such an upgrade can be completed from this starting point.
134
Stage 1:
Begin the upgrade Upgrade Content Engine
Stage 2:
Option 1
Option 2
Upgrade Application Engine or Upgrade Workplace XT
Upgrade Process Engine
Stage 3:
Complete the upgrade Upgrade Process Engine Upgrade Application Engine or Upgrade Workplace XT
Figure 3. Staged upgrade scenario 2: upgrading Content Engine first
The following tables describe which components you can upgrade in each stage and in what order if you want to upgrade Content Engine first. Unless otherwise noted, components that are described in these tables must be upgraded together. For example, when you upgrade IBM FileNet Process Engine, you must also upgrade IBM FileNet Process Analyzer and IBM FileNet Process Simulator. After you upgrade Content Engine and related components in stage 1, you must decide whether to upgrade IBM FileNet Application Engine or IBM FileNet Workplace XT (option 1) or whether to upgrade IBM FileNet Process Engine (option 2). Stage 1: upgrading Content Engine In stage 1 of this scenario, you upgrade the Content Engine.
135
You can optionally upgrade related components in this stage or wait until later as described in the table.
Table 7. Stage 2: upgrading Content Engine Starting version Content Engine 4.0.1 or 4.5.0 Upgrade version Content Engine 4.5.1 Comments Also upgrade Content Engine Client to version 4.5.1 on computers that are running the following components: v Application Engine v Workplace XT v Process Engine v FileNet Records Manager v Business Process Framework v Custom clients IBM FileNet Content Search Engine 4.0.1 or 4.5.0 IBM FileNet Content Federation Services 4.0.0 or 4.5.0 IBM FileNet Records Manager 4.0.0 or 4.5.0 IBM FileNet Application Engine 4.0.1 or 4.0.2 IBM FileNet Workplace XT1.1.2 or 1.1.3 IBM FileNet P8 eForms 4.0.1 Process Engine 4.0.3 or 4.5.0 Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Content Search Engine 4.5.1 Also upgrade Content Search Engine Client to version 4.5.1 on Content Engine servers.
Content Federation Services 4.5.1 Defer upgrading in this stage. If you are already running version 4.5.0, no additional upgrade is required. Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage.
IBM FileNet Business Process Defer upgrading in this stage. Business Process Framework Framework 4.1.0 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available. IBM FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1 FileNet Connector for Microsoft SharePoint 2.2.1 or defer upgrading in this stage. Upgrading is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required.
136
Table 7. Stage 2: upgrading Content Engine (continued) Starting version IBM Enterprise Content Management Widgets 4.5.1 Upgrade version IBM ECM Widgets 4.5.1 Comments No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
IBM Lotus Quickr 1.0
Lotus Quickr 1.0
FileNet P8 Documentation 4.5.1 or defer upgrading in this stage.
After you complete this upgrade stage, you have an operational system even though FileNet P8 is not fully upgraded. Now you must decide whether to upgrade Application Engine or Workplace XT (option 1) or or whether to upgrade Process Engine (option 2). Stage 2, option 1: continuing the upgrade by upgrading Application Engine or Workplace XT The following table describes which components you can upgrade with Application Engine or Workplace XT.
Table 8. Stage 1: continuing the upgrade by upgrading Application Engine or Workplace XT Starting version Content Engine 4.0.1 or 4.5.0 Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 or 4.5.0 Upgrade version Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. FileNet Records Manager 4.5.0 or defer upgrading in this stage. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required. Deploy Workplace 4.0.2. If you are already running version 4.0.2, no additional upgrade is required. Deploy Workplace XT 1.1.4. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. Comments
Workplace XT 1.1.2 or 1.1.3 FileNet P8 eForms 4.0.1
Process Engine 4.0.3 or 4.5.0 Process Analyzer 4.0.1 or 4.5.0
Defer upgrading in this stage. Defer upgrading in this stage.
137
Table 8. Stage 1: continuing the upgrade by upgrading Application Engine or Workplace XT (continued) Starting version Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Business Process Framework 4.1.0 Upgrade version Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Business Process Framework 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available. FileNet Connector for Microsoft SharePoint 2.2.1 Upgrading is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Comments
Lotus Quickr 1.0
Lotus Quickr 1.0 unless installed in stage 1.
Upgrading is optional at this FileNet P8 Documentation 4.5.1 unless upgraded in stage stage. 1.
After you complete this upgrade stage 2 option, your system is operational. Continue with upgrading Process Engine in stage 3. Stage 2, option 2: continuing the upgrade by upgrading Process Engine The following table describes which components you can upgrade with Process Engine.
Table 9. Stage 2: continuing the upgrade by upgrading Process Engine Starting version Content Engine 4.0.1 or 4.5.0 Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 or 4.5.0 Application Engine 4.0.1 or 4.0.2 Upgrade version Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. Defer upgrading in this stage. If you are already running version 4.5.0, no additional upgrade is required. Defer upgrading in this stage. Comments
138
Table 9. Stage 2: continuing the upgrade by upgrading Process Engine (continued) Starting version Workplace XT 1.1.2 or 1.1.3 FileNet P8 eForms 4.0.1 Process Engine 4.0.3 or 4.5.0 Upgrade version Defer upgrading in this stage. Defer upgrading in this stage. Process Engine 4.5.1 Also upgrade Process Engine Client to version 4.5.1 on computers that are running the following components: v Content Engine v Application Engine v Workplace XT v FileNet Records Manager v Business Process Framework v Custom clients Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Process Analyzer 4.5.1 Process Simulator 4.5.1 IBM Cognos Now 4.6 The existing Business Activity Monitor component contains an older version of Cognos Now. When you upgrade to Cognos Now 4.6 and then upgrade to Process Analyzer 4.5.1, your Business Activity Monitor installation is replaced by a new Process Activity Monitor feature. Business Process Framework 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available. Comments
FileNet Connector for Upgrading is optional at this Microsoft SharePoint 2.2.1 or stage. If you are already defer upgrading in this stage. running version 2.2.1, no additional upgrade is required. IBM ECM Widgets 4.5.1 unless upgraded in stage 1. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required.
Lotus Quickr 1.0
Lotus Quickr 1.0 unless upgraded in stage 1.
139
Table 9. Stage 2: continuing the upgrade by upgrading Process Engine (continued) Starting version FileNet P8 Documentation 4.0.3 or 4.5.0 Upgrade version FileNet P8 Documentation 4.5.1 unless upgraded in stage 1. Comments Upgrading is optional at this stage.
After you complete this upgrade stage 2 option, your system is operational. Continue with upgrading Content Engine in stage 3. Stage 3, option 1: completing the upgrade by upgrading Process Engine The following table describes which components you can upgrade with Process Engine .
Table 10. Stage 3: completing the upgrade by upgrading Process Engine Starting version Content Engine 4.0.1 or 4.5.0 Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 Upgrade version Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. FileNet Records Manager 4.5.0 unless upgraded in stage 2. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required. Comments
Upgraded in stage 2. Upgraded in stage 2. FileNet P8 eForms 4.0.2 unless upgraded in stage 2. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. Also upgrade Process Engine Client to version 4.5.1 on computers that are running the following components: v Content Engine v Application Engine v Workplace XT v FileNet Records Manager v Business Process Framework v Custom clients
Process Engine 4.5.1
Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0
Process Analyzer 4.5.1 Process Simulator 4.5.1
140
Table 10. Stage 3: completing the upgrade by upgrading Process Engine (continued) Starting version Business Activity Monitor 4.0.0 or 4.5.0 Upgrade version IBM Cognos Now 4.6 Comments The existing Business Activity Monitor component contains an older version of Cognos Now. When you upgrade to Cognos Now 4.6 and then upgrade to Process Analyzer 4.5.1, your Business Activity Monitor installation is replaced by a new Process Activity Monitor feature. Business Process Framework 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available. Upgrading is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
Lotus Quickr 1.0
After you complete stage 3 option 1, your FileNet P8 upgrade is complete. Stage 3, option 2: completing the upgrade by upgrading Application Engine or Workplace XT The following table describes which components you can upgrade with Application Engine.
Table 11. Stage 3: completing the upgrade by upgrading Application Engine or Workplace XT Starting version Content Engine 4.0.1 or 4.5.0 Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 Upgrade version Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. Comments
141
Table 11. Stage 3: completing the upgrade by upgrading Application Engine or Workplace XT (continued) Starting version FileNet Records Manager 4.0.0 or 4.5.0 Upgrade version FileNet Records Manager 4.5.0 Comments Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required. Deploy Workplace 4.0.2. If you are already running version 4.0.2, no additional upgrade is required. Workplace XT 1.1.4 Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT.
Workplace XT 1.1.4 FileNet P8 eForms 4.0.2 unless upgraded in a previous stage. Upgraded in stage 2. Upgraded in stage 2. Upgraded in stage 2. Upgraded in stage 2. Upgraded in stage 2.
Process Engine 4.0.3 or 4.5.0 Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Business Process Framework 4.1.0
Business Process Framework 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available. Upgrade is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
Lotus Quickr 1.0
142
Staged upgrade scenario 3: upgrading Process Engine first: One option for an IBM FileNet P8 staged upgrade is to begin by upgrading your IBM FileNet Process Engine component, which includes server and client software. You can then run this upgraded software with other core IBM FileNet P8 components that are not yet upgraded. At your discretion, your users can start working again while you prepare for the next stage of the systemwide upgrade. The following high-level graphic shows how such an upgrade can be completed from this starting point.
Stage 1:
Begin the upgrade Upgrade Process Engine
Stage 2:
Option 1
Option 2
Upgrade Application Engine or Upgrade Workplace XT
Upgrade Content Engine
Stage 3:
Complete the upgrade Upgrade Content Engine Upgrade Application Engine or Upgrade Workplace XT
Figure 4. Staged upgrade scenario 3: upgrading Process Engine first
The following tables describe which components you can upgrade in each stage and in what order if you want to upgrade Process Engine first. Unless otherwise noted, components that are described in these tables must be upgraded together. For example, when you upgrade IBM FileNet Process Engine, you must also upgrade IBM FileNet Process Analyzer and IBM FileNet Process Simulator.
143
After you upgradeProcess Engine and related components in stage 1, you must decide whether to upgrade IBM FileNet Application Engine or IBM FileNet Workplace XT (option 1) or whether to upgrade IBM FileNet Content Engine (option 2) in the next stage. Stage 1: upgrading Process Engine In stage 1, you upgrade the Process Engine.
Table 12. Stage 2: upgrading Process Engine Starting version Content Engine 4.0.1 or 4.5.0 IBM FileNet Content Search Engine 4.0.1 or 4.5.0 IBM FileNet Content Federation Services 4.0.0 or 4.5.0 IBM FileNet Records Manager 4.0.0 or 4.5.0 IBM FileNet Application Engine 4.0.1 or 4.0.2 IBM FileNet Workplace XT1.1.2 or 1.1.3 IBM FileNet P8 eForms 4.0.1 Process Engine 4.0.3 or 4.5.0 Upgrade version Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Comments
Defer upgrading in this stage. If you are already running version 4.5.0, no additional upgrade is required. Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Process Engine 4.5.1 Also upgrade Process Engine Client to version 4.5.1 on computers that are running the following components: v Content Engine v Application Engine v Workplace XT v FileNet Records Manager v Business Process Framework v Custom clients
Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0
Process Analyzer 4.5.1 Process Simulator 4.5.1 IBM Cognos Now 4.6 The existing Business Activity Monitor component contains an older version of Cognos Now. When you upgrade to Cognos Now 4.6 and then upgrade to Process Analyzer 4.5.1, your Business Activity Monitor installation is replaced by a new Process Activity Monitor feature.
144
Table 12. Stage 2: upgrading Process Engine (continued) Starting version Upgrade version Comments Business Process Framework 4.1.0 runs on Process Engine 4.5, but this configuration is supported only as an upgrade. Before you upgrade to Process Engine 4.5.1, ensure that the supporting fix pack for Business Process Framework 4.1.0 is available.
IBM FileNet Business Process Business Process Framework Framework 4.1.0 4.1.0
IBM FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1
FileNet Connector for Upgrading is optional at this Microsoft SharePoint 2.2.1 or stage. If you are already defer upgrading in this stage. running version 2.2.1, no additional upgrade is required. IBM ECM Widgets 4.5.1 No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
IBM Enterprise Content Management Widgets 4.5.1
IBM Lotus Quickr 1.0
Lotus Quickr 1.0
FileNet P8 Documentation 4.5.1 or defer upgrading in this stage.
After you complete this upgrade stage, your system is operational even though the FileNet P8 upgrade is not complete. In stage 2, you must decide whether to upgrade Application Engine or Workplace XT (option 1) or whether to upgrade Content Engine (option 2). Stage 2, option 1: continuing the upgrade by upgrading Application Engine or Workplace XT The following table describes which components you can upgrade along with Application Engine or Workplace XT in stage 2.
Table 13. Stage 1: continuing the upgrade by upgrading Application Engine or Workplace XT Starting version Content Engine 4.0.1 or 4.5.0 Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 or 4.5.0 Upgrade version Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. FileNet Records Manager 4.5.0 or defer upgrading in this stage. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required. Comments
145
Table 13. Stage 1: continuing the upgrade by upgrading Application Engine or Workplace XT (continued) Starting version Application Engine 4.0.1 or 4.0.2 Upgrade version Application Engine 4.0.2 Comments Deploy Workplace 4.0.2. If you are already running version 4.0.2, no additional upgrade is required. Deploy Workplace XT 1.1.4. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT.
Process Engine 4.0.3 or 4.5.0 Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Business Process Framework 4.1.0 FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1
Done in stage 1. Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. FileNet Connector for Microsoft SharePoint 2.2.1 Upgrading is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must treat version 4.5.1 as a new installation. If you are already running version 1.0, no additional upgrade is required.
Lotus Quickr 1.0
Lotus Quickr 1.0 unless installed in stage 1.
Upgrading is optional at this FileNet P8 Documentation 4.5.1 unless upgraded in stage stage. 1.
After you complete this upgrade stage 2 option, your system is operational. Continue with upgrading Content Engine. Stage 2, option 2: continuing the upgrade by upgrading Content Engine The following table describes which components you can upgrade with Process Engine.
146
Table 14. Stage 2: continuing the upgrade by upgrading Content Engine Starting version Content Engine 4.0.1 or 4.5.0 Upgrade version Content Engine 4.5.1 Comments Also upgrade Content Engine Client to version 4.5.1 on computers that are running the following components: v Application Engine v Workplace XT v Process Engine v FileNet Records Manager v Business Process Framework v Custom clients Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 or 4.5.0 Application Engine 4.0.1 or 4.0.2 Workplace XT 1.1.2 or 1.1.3 FileNet P8 eForms 4.0.1 Process Engine 4.0.3 or 4.5.0 Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Business Process Framework 4.1.0 FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1 Content Search Engine 4.5.1 Also upgrade Content Search Engine Client to version 4.5.1 on Content Engine servers.
Content Federation Services 4.5.1 Defer upgrading in this stage. If you are already running version 4.5.0, no additional upgrade is required. Defer upgrading in this stage. Defer upgrading in this stage. Defer upgrading in this stage. Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. Upgrading is optional at this FileNet Connector for Microsoft SharePoint 2.2.1 or stage. If you are already defer upgrading in this stage. running version 2.2.1, no additional upgrade is required. IBM ECM Widgets 4.5.1 unless upgraded in a previous stage. Lotus Quickr 1.0 unless installed in a previous stage. FileNet P8 Documentation 4.5.1 unless upgraded in a previous stage. No upgrade exists between version 4.5.0 and 4.5.1. You must treat version 4.5.1 as a new installation. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
Lotus Quickr 1.0
147
After you complete this upgrade stage 2 option, you again have an operational system. Now continue with upgrading Application Engine or Workplace XT in stage 3. Stage 3, option 1: completing the upgrade by upgrading Content Engine The following table describes which components you can upgrade with Content Engine in stage 3.
Table 15. Stage 3: completing the upgrade by upgrading Content Engine Starting version Content Engine 4.0.1 or 4.5.0 Upgrade version Content Engine 4.5.1 Comments Also upgrade Content Engine Client to version 4.5.1 on computers that are running the following components: v Application Engine v Workplace XT v Process Engine v FileNet Records Manager v Business Process Framework v Custom clients Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 Content Search Engine 4.5.1 Also upgrade Content Search Engine Client to version 4.5.1 on Content Engine servers.
Content Federation Services 4.5.1 FileNet Records Manager 4.5.0 unless upgraded in stage 2. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required.
Upgraded in stage 2. Upgraded in stage 2. FileNet P8 eForms 4.0.2 unless upgraded in stage 2. Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT.
Process Engine 4.0.3 or 4.5.0 Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Business Process Framework 4.1.0
Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1.
148
Table 15. Stage 3: completing the upgrade by upgrading Content Engine (continued) Starting version FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1 Upgrade version FileNet Connector for Microsoft SharePoint 2.2.1 unless upgraded in a previous stage. IBM ECM Widgets 4.5.1 unless upgraded in a previous stage. Comments Upgrading is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage.
Lotus Quickr 1.0
After you complete stage 3 option 1, your FileNet P8 upgrade is complete. Stage 3, option 2: completing the upgrade by upgrading Application Engine or Workplace XT The following table describes which components you can upgrade with Application Engine or Workplace XT in stage 3.
Table 16. Stage 3: completing the upgrade by upgrading Application Engine Starting version Content Engine 4.0.1 or 4.5.0 Content Search Engine 4.0.1 or 4.5.0 Content Federation Services 4.0.0 or 4.5.0 FileNet Records Manager 4.0.0 or 4.5.0 Upgrade version Upgraded in stage 2. Upgraded in stage 2. Upgraded in stage 2. FileNet Records Manager 4.5.0 Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. If you are already running version 4.5.0, no additional upgrade is required. Deploy Workplace 4.0.2. If you are already running version 4.0.2, no additional upgrade is required. Workplace XT 1.1.4 Upgrading is optional at this stage. Upgrade any time after you upgrade Application Engine or Workplace XT. Comments
Workplace XT 1.1.4 FileNet P8 eForms 4.0.2 unless upgraded in a previous stage. Upgraded in stage 1.
149
Table 16. Stage 3: completing the upgrade by upgrading Application Engine (continued) Starting version Process Analyzer 4.0.1 or 4.5.0 Process Simulator 4.0.0 or 4.5.0 Business Activity Monitor 4.0.0 or 4.5.0 Business Process Framework 4.1.0 FileNet Connector for Microsoft SharePoint 2.1.0, 2.2.0, or 2.2.1 Upgrade version Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. Upgraded in stage 1. FileNet Connector for Microsoft SharePoint 2.2.1 unless upgraded in a previous stage. IBM ECM Widgets 4.5.1 unless upgraded in a previous stage. Upgrade is optional at this stage. If you are already running version 2.2.1, no additional upgrade is required. No upgrade exists between version 4.5.0 and 4.5.1. You must install version 4.5.1 as a new installation, not an upgrade. If you are already running version 1.0, no additional upgrade is required. Upgrading is optional at this stage. Comments
Lotus Quickr 1.0
Automatic upgrading of Content Engine

Upon deploying version 4.5.1 of Content Engine, the upgrade of the Global Configuration Data (GCD) and the object stores will proceed without user input. Automatic upgrade of the GCD and the object stores starts when you have finished deploying version 4.5.1 of Content Engine, provided you are upgrading from version 4.0.1 or 4.5.0 of Content Engine. If you are upgrading from version 3.5, you must run the Content Engine Upgrader tool to upgrade the GCD and the object stores. It is a best practice to back up the GCD and the object store databases before starting to upgrade Content Engine software.
Upgrading planning considerations

Review all upgrade planning information related to requirements for upgrading anIBM FileNet P8 Platform system and expansion products, as well as other vendor products associated with the IBM FileNet P8 Platform. Review this section thoroughly before you start to upgrade FileNet P8 Platform components or required vendor software. General requirements for all FileNet P8 Platform systems on page 151 It is best practice to plan and test the upgrade on a designated test system first. Verify the upgrade is successful by running functionality and stress tests.
150
FileNet P8 Platform expansion product considerations on page 152 To upgrade the FileNet P8 Platform expansion products, in addition to the tasks described in those products own Installation and Upgrade Guides, you must carry out certain tasks regarding Content Engine. Third-party vendor software considerations on page 153 The 3.5, 4.0, and 4.5 versions of IBM FileNet P8 Platform components support common levels of independent software vendor (ISV) products.
General requirements for all FileNet P8 Platform systems

It is best practice to plan and test the upgrade on a designated test system first. Verify the upgrade is successful by running functionality and stress tests. v Apply the required minimum level IBM FileNet P8 Platform software updates for the release you are currently running before you upgrade. Before you begin your upgrade to FileNet P8 Platform 4.5, use the information in the following table to verify that each component is using the minimum fix pack level or higher. This information applies to standard upgrades from version 3.5 or 4.0. For information related to staged upgrades, review the IBM FileNet P8 Compatibility Matrix at http://www.ibm.com/software/data/support/.
3.5 Fix Component Pack Content Engine Process Engine Application Engine CE-3.5.2002 3.5 Software Build kl195.025 4.0 Software 4.0 Fix Pack Build CE 4.0.1-002 dap435.032 PE 4.0.3 pe430.060a and pui430.052 per410. 041d raptor305A .006 rec200.056 4.5 Release CE 4.5 PE 4.5 4.5 Software Build dap440 pe450 pui450 AE 4.0.2 eForms 4.0.2 RM 4.5 per450 raptor330 rec210
PE 3.5.3-002 pe197.011 and pui197.005 AE-3.5.1003 per185. 027.a01 raptor220. 004 rec190.007
AE-4.0.12 eForms 4.0.1 4.0.0
IBM FileNet P8eF-3.5.1 P8 eForms IBM FileNet 3.7.0 Records Manager IBM FileNet 1.1.2 Workplace XT IBM FileNet Content Federation Services No direct upgrade from 3.5 to CFS 4.5
orion210
1.1.2
orion210
Workplace orion300 XT 1.1.3 CFS 4.5 hel440.237a
hel195
4.0.0-001
hel435. 010
IBM FileNet PA-3.5.2 Process Analyzer
pa190.015b
PA-4.0.1. 001 PS-4.0.0. 006
pa435.014
PA 4.5
ps450
IBM FileNet PS-3.5.2-005 ps185.023 Process Simulator IBM FileNet BAM-3.6Business 001.001 Activity Monitor IBM FileNet RE-3.5.1 Rendition Engine
ps420.027c
PS 4.5
ps450
bam195.002 BAM-3.6001.001
bam195.002 BAM 4.5
bam450
re400
RE-4.0.1
re400
RE 4.5
re440.007
151
3.5 Fix Component Pack Content Search Engine IBM FileNet BPF 3.6 Business Process Framework
3.5 Software Build
4.0 Software 4.0 Fix Pack Build CSE 4.0.1 cse435
4.5 Release CSE 4.5
4.5 Software Build cse440
BPF 4.1
bpf405.008
If you have IBM FileNet Business Process Framework installed in your current IBM FileNet P8 environment, do not upgrade Content Engineor Process Engine components to version 4.5.1 until a Business Process Framework fix pack has been released to support this configuration. Contact your IBM representative for details. Application Engine 4.0.1 is the minimum unless you are running Business Process Framework 4.1 where the minimum is Application Engine 4,0,1-000.001 interim fix, or you are running SharePoint 2.2, where the minimum is the Application Engine 4.0.1-003 fix pack. Run the version tool, as documented in the IBM FileNet P8 Version Tools Technical Notice to determine the software build. Use the table above to map the software build number to the minimum software update. If any FileNet P8 Platform component is below the minimum software level documented here, update that component accordingly. Applying a fix pack for one component might require fix packs for other components. Prior to applying any fix pack, review the IBM FileNet P8 Compatibility Matrix on the http://www.ibm.com/software/data/support/ to assure compatibility between all installed components. BAM 450 is the terminal release of this product. IBM FileNet P8 version 4.5.1 supports direct CognosNow! integration through the FileNet Process Monitor Feature.
FileNet P8 Platform expansion product considerations

To upgrade the FileNet P8 Platform expansion products, in addition to the tasks described in those products own Installation and Upgrade Guides, you must carry out certain tasks regarding Content Engine. FileNet P8 eForms on page 153 If you have the IBM FileNet P8 eForms expansion product installed you must uninstall it before upgrading Application Engine. Content Federation Services on page 153 IBM FileNet Content Federation Services 4.0 or later is not compatible with Content Engine version 4.5 or later. You should shut down CFS Exporter before you begin the upgrade to Content Engine 4.5 or later, and leave it shut down until you finish the upgrade to Content Federation Services version 4.5. Therefore, you should plan to upgrade IBM FileNet Content Federation Services as soon as possible after you upgrade Content Engine . FileNet Records Manager on page 153 The Content Engine Upgrader tool will fail if run on a file plan object store (FPOS) unless the object store has been updated to the version 4.5.1 or later
152
data model. This limitation only applies to FPOS; you can update record object stores (ROS) without first updating the data model. FileNet P8 eForms: If you have the IBM FileNet P8 eForms expansion product installed you must uninstall it before upgrading Application Engine. Content Federation Services: IBM FileNet Content Federation Services 4.0 or later is not compatible with Content Engine version 4.5 or later. You should shut down CFS Exporter before you begin the upgrade to Content Engine 4.5 or later, and leave it shut down until you finish the upgrade to Content Federation Services version 4.5. Therefore, you should plan to upgrade IBM FileNet Content Federation Services as soon as possible after you upgrade Content Engine . For more information, see the Upgrade overview topic in IBM FileNet Content Federation Services Installation and Upgrade Guide. FileNet Records Manager: The Content Engine Upgrader tool will fail if run on a file plan object store (FPOS) unless the object store has been updated to the version 4.5.1 or later data model. This limitation only applies to FPOS; you can update record object stores (ROS) without first updating the data model. v (3.7 to 4.5.1 only) You must update the IBM FileNet Records Manager (RM) data model on each FPOS before you install Content Engine version 4.5.1. For more information about the RM37PreUpgrader tool, see the topic Prepare to Upgrade Object Stores in IBM FileNet Records Manager Installation and Upgrade Guide. Important: To complete and confirm your IBM FileNet P8 Platform upgrade you must update at least one object store. If your configuration contains only FileNet Records Manager object stores, you must either update at least one of them or create a non-FileNet Records Manager object store prior to upgrading and use that object store to confirm the upgrade. If your site preferences reside on a FileNet Records Manager object store, you must update that object store to complete the IBM FileNet P8 Platform upgrade. Alternatively, you can move the site preferences to another object store before the upgrade. v Do not install Enterprise Manager version 4.5.1 or later on any machine running Enterprise Manager version 3.5 or later until the FileNet Records Manager upgrade to version 4.5 or later is complete. This includes updating all FileNet Records Manager object stores to version 4.5 or later. Installing Enterprise Manager version 4.5.1 will cause unexpected behavior with the FileNet Records Manager Data Upgrade tool.
Third-party vendor software considerations

The 3.5, 4.0, and 4.5 versions of IBM FileNet P8 Platform components support common levels of independent software vendor (ISV) products. Exceptions are listed in the IBM FileNet P8 Hardware and Software Requirements.
153
Definition of upgrade roles

Your organization may have different roles, and some of the responsibilities of listed roles will vary from those assigned by default. The tasks in this guide as well as the rows in the Installation and Upgrade Worksheet are organized by administrative roles, listed below.
Installation administrator
Runs the IBM FileNet P8 Platform component installers during initial setup. Runs the FileNet Configuration Manager tool during initial setup, followed by launching Enterprise Manager. v Runs the IBM FileNet P8 Platform component upgrade programs during upgrades. v Abbreviated as IA. Responsible for coordinating the information described in this worksheet. The information itself will require the input from the other roles. v v The role of IA is usually filled by an IBM FileNet P8 Certified Professional (FCP).
Information technology administrator

v v v Responsible for the networking and operating systems settings required by the IBM FileNet P8 Platform components. Responsible for performing certain security configurations. Abbreviated as ITA. Responsible for providing the information in the rows in the Installation and Upgrade Worksheet with a value of ITA in the Role column.
For tasks assigned to the ITA, see IT administrator upgrade tasks on page 158.
v v v Responsible for configuring the directory servers required by IBM FileNet P8 Platform components, including Content Engine and Application Engine. Creates and maintains directory server user and group accounts. Abbreviated as SA. Responsible for providing the information in the rows in the Installation and Upgrade Worksheet with a value of SA in the Role column.
For tasks assigned to the SA, see Security administrator upgrade tasks on page 180.
Creates, configures, maintains database installations and databases or table spaces. v Responsible for creating database accounts needed by FileNet P8 Platform components. v For purposes of this documentation, the database administrator is expected to have responsibilities regarding the Java Database Connectivity (JDBC) data sources. v Abbreviated as DBA. Responsible for providing the information in the rows in the Installation and Upgrade Worksheet with a value of DBA in the Role column. v For tasks assigned to the DBA, see Database administrator upgrade tasks on page 189.
154
Application server administrator

v Responsible for providing the application servers required by FileNet P8 Platform components. v Responsible for application server administrative accounts. v Abbreviated as ASA. Responsible for providing the information in the rows in the Installation and Upgrade Worksheet with a value of ASA in the Role column. For tasks assigned to the ASA, see Application Server administrator upgrade tasks on page 197.

v This role designation actually refers to the administrator or administrators who perform regular maintenance of Content Engine, Process Engine, Application Engine (Workplace) or Workplace XT.
The administrator who logs on to Enterprise Manager using the gcd_admin account or an object_store_admin account is considered an IBM FileNet P8 administrator. v Abbreviated as P8A. Responsible for providing the information in the rows of the Installation and Upgrade Worksheet with a value of P8A in the Role column.
For tasks assigned to the P8A, see IBM FileNet P8 administrator upgrade tasks on page 213.
E-mail administrator
v Creates an e-mail account that will be used to configure the Notification Tab of the Process Task Manager so that Process Engine can send e-mail notifications to end users. (Required only if you use this feature.) v Abbreviated as EA. Tip: The E-mail Administrator role is not used in an upgrade, but is included in this topic for completeness.
Using the installation and upgrade worksheet

The Installation and Upgrade Worksheet is a Microsoft Excel spreadsheet (p8_worksheet.xls). The worksheet describes the properties and parameters required to complete IBM FileNet P8 installation, upgrade, and configuration programs, and provides a way to record the values you assign to these properties and parameters. Administrators who are preparing the environment for installation or upgrade of IBM FileNet P8 components must use the worksheet during their preparation tasks to record the appropriate values and provide them to the Installation Administrator who runs the installation or upgrade programs. Some of the features of the Installation and Upgrade Worksheet are: v Instructions: describes the worksheet and includes a button that runs the Customize Worksheet macro. v The two highlighted columns, Property or Parameter and ENTER YOUR VALUE HERE, provide the simplest view of the requirement. The others add identifying information and help you sort and filter the rows usefully. v The Role column assigns each row to an administrator and uses the following acronyms:
155
ITA: Information Technology Administrator ASA: Application Server Administrator DBA: Database Administrator SA: Security Administrator P8A: IBM FileNet P8 Administrator
v Property definitions are contained in the column titled Description. v Some rows, though not all, contain a hyperlink in the PPG Links column. Click this hyperlink to run a query against the IBM Information Center, which opens with the Search Results pane showing the topics that contain the words in the query phrase. Browse the search results until you have enough information to be able to enter a value in the Worksheet row. Running the Customize Worksheet macro The Customize Worksheet macro lets you extract only those rows that describe your environment. Autofiltering and sorting the Worksheet on page 157 There are several ways to organize the Worksheet to make finding properties and entering values easier.
Running the Customize Worksheet macro

The Customize Worksheet macro lets you extract only those rows that describe your environment. Important: For support of the full range of built-in filter and macro features, use Microsoft Excel to view the Installation and Upgrade Worksheet file. You can use other spreadsheet programs to view the file; however, filter and macro support can vary. For example, in Calc from OpenOffice.Org, the column filters work as expected, but the Customize Worksheet button does not. To run the Customize Worksheet macro: 1. Open the Installation and Upgrade Worksheet (p8_worksheet.xls) and click the Instructions worksheet (also called a tab). 2. Scroll down until you see the button representing the Customize Worksheet macro. Click the button. 3. Select the components and options that describe the environment you are preparing for IBM FileNet P8. v Installation or Upgrade v FileNet P8 Components Application Server type Operating system Database type Directory Server type Number of object stores (adds new sets of rows for creating additional data sources) v Name of customized sheet 4. Click OK. The macro copies the rows that fulfill your selection criteria into a new worksheet with the name you entered. Enter the values for your environment into this new worksheet. 5. Click the name of the new worksheet at the bottom of the Excel window. Add your preparation values into this new worksheet. v v v v v
156
6. Notice that the new worksheet has buttons at the top titled Show Installer View and Show Full View, depending on its state. The Show Installer View displays only those columns that you need while running installation or configuration programs.
Autofiltering and sorting the Worksheet

There are several ways to organize the Worksheet to make finding properties and entering values easier. AutoFiltering is a quick way to display only those rows that meet a certain criteria. To use AutoFilter: 1. Make sure AutoFiltering is enabled. (Select the entire row with the column headers, then click Data Filter Autofilter.) AutoFilter arrows will appear to the right of the column labels. 2. Click the AutoFilter arrow in the Installation or Configuration Program column header and select the program you are interested in (for example, PE installer). 3. Click the AutoFilter arrow in the Setup Type column header, select Custom, and specify Setup Type contains Installation. 4. For a custom AutoFilter, click the AutoFilter in any column header, select Custom, and specify Setup Type contains Installation. 5. To turn off AutoFiltering in a column, click the column AutoFilter arrow and select (All). 6. To reorder rows alphabetically, do a Sort: a. Click anywhere in a column, for example, Column A Role. The only possible values in the Role column are ASA, SA, DBA, ITA, and P8A. Sorting on Role therefore groups the rows by this attribute, in alphabetic order. Several other columns also have a limited number of possible values which means they can be usefully sorted. b. Click the Sort Ascending icon in the Excel toolbar, or use the Data Sort menu command. The rows sort on Role. Sorting the Worksheet reassigns row numbers. If you refer to rows by number, be aware that row numbers change if you change the sort order.
Performing the required upgrade preparation tasks

To efficiently carry out the required upgrade preparation tasks, you must assign your staff to carry out the tasks that are organized by administrative role. For information about assigning and defining these roles, see Definition of upgrade roles on page 154. Some tasks require input that results from other preparation tasks performed by other administrator roles. While performing the tasks, record the results in the Installation and Upgrade Worksheet. Some of the upgrade procedures in the following subsections apply only if you are upgrading from IBM FileNet P8 Platform version 3.5; others apply only if you are upgrading from version 4.0 or later. If not otherwise indicated, complete each procedure irrespective of the current version.
157
To prepare the IBM FileNet P8 environment, complete the tasks assigned to each role. IT administrator upgrade tasks The Information Technology administrator must prepare the network and operating systems, and carry out certain security configurations to prepare your environment for IBM FileNet P8 Platform upgrade. Security administrator upgrade tasks on page 180 The Security administrator must prepare the security environment for IBM FileNet P8 Platform upgrade, including planning the security environment, and creating accounts. Database administrator upgrade tasks on page 189 The Database administrator must prepare the databases required for IBM FileNet P8 upgrade, including installing patches, creating databases and database accounts, and installing client software. Application Server administrator upgrade tasks on page 197 The Application Server Administrator must prepare the application servers for IBM FileNet P8 Platform upgrade, including planning deployment, creating administrative accounts, and configuring JDBC drivers for both Content Engine and Application Engine. IBM FileNet P8 administrator upgrade tasks on page 213 The FileNet P8 Administrator must carry out several tasks to prepare your environment for your IBM FileNet P8 Platform upgrade.
IT administrator upgrade tasks

The Information Technology administrator must prepare the network and operating systems, and carry out certain security configurations to prepare your environment for IBM FileNet P8 Platform upgrade. v Review all rows assigned to the IT Administrator for Upgrade in the Installation and Upgrade Worksheet. Provide values for any rows appropriate to your installation that you have not yet completed. Tip: With the Data Filter AutoFilter command enabled, as it is by default in the shipping worksheet file (p8_worksheet.xls), perform the following actions to quickly see only the properties assigned to a particular role: Click the AutoFilter drop-down arrow in the Role column header and select ITA. Further filter the result set by clicking the AutoFilter drop-down arrow in any of the other columns and selecting a value or clear a filter by selecting All. v Configure the operating systems to prepare for component upgrade. Creating Content Engine operating system accounts for upgrade on page 159 Create new or designate existing installation accounts for Content Engine, as shown in the following table. Configuring UNIX on page 159 Prepare your UNIX-based server for the IBM FileNet P8 Platform upgrade. Configuring Microsoft Windows on page 173 Verify that any Windows server configuration changes have been made in preparation for upgrading IBM FileNet P8 software. Configuring network on page 178 Configure the network to prepare for your IBM FileNet P8 Platform upgrade.
158
Creating Content Engine operating system accounts for upgrade

Create new or designate existing installation accounts for Content Engine, as shown in the following table.
User or Group unique_name Configuration Manager user: (IBM WebSphere Application Server, Oracle WebLogic Server, JBoss Application Server): config_mgr_user Description The operating system account you will use to run the Configuration Manager. (Windows) Using Active Directory tools, add config_mgr_user to either the Power Users group or the Local Administrators group. After Content Engine is installed you must grant additional permissions to config_mgr_user: v Grant it permission to run the Configuration Manager executable file: configmgr.bat (Windows) or configmgr.sh (UNIX). v Grant it permission to write to the directory where Configuration Manager will create the configuration XML files. This location is one of the following directories: the directory you specify using the optional -path parameter when you run the tool the default directory, CE_install_path/tools/ configurationmanager/tasks, if you do not specify a path parameter v Grant it permission to read and write the contents of the directory specified by -path parameter, or the default directory. You will be instructed to grant additional permissions to config_mgr_user at several times in the Planning and Preparation Guide: v Setting permissions for the Configuration Manager user on page 206 (WebSphere Application Server) v Preparing DB2 for Linux, UNIX and Windows servers on page 99 (JBoss Application Server) v Configuring WebLogic Server for Content Engine on page 206
Configuring UNIX
Prepare your UNIX-based server for the IBM FileNet P8 Platform upgrade. Configuring UNIX for IBM FileNet P8 Platform servers (all components) on page 160 To ensure hosts file contents, the /etc/hosts file must have the Internet Protocol (IP) address of the servers to be used. Configuring Content Engine servers (all UNIX) on page 160 You must specify the default file-creation permissions for the user who will install Content Engine.
159
Setting up Java SDK for Content Search Engine on page 161 Content Search Engine requires Java SDK on UNIX machines where you intend to install additional locales (other than English). Configuring Content Search Engine servers (UNIX) on page 161 Content Search Engine requires that certain kernel parameters be specified and libraries installed. Configuring Process Engine servers (all UNIX) on page 162 Complete each of the following tasks to prepare the Process Engine server for upgrade. Configuring Process Engine servers (AIX) on page 164 The following operating system prerequisites apply to AIX-based Process Engine servers. Configuring Process Engine servers (HP-UX) on page 165 The following operating system prerequisites apply to HP-UX-based Process Engine servers. Configuring Process Engine servers (Solaris) on page 169 The operating system prerequisites in this subsection pertain to Solaris-based Process Engine servers. Configuring Linux servers for Application Engine or Workplace XT on page 173 Ensure that Linux libraries are installed. To install Application Engine or Workplace XT on Linux, several legacy libraries are required. You must install the compat-libstdc++ packages on your Red Hat system prior to beginning your install of Application Engine or Workplace XT. Configuring Application Engine or Workplace XT servers (HP-UX) on page 173 Add an entry to the /etc/nsswitch.conf to enable communication with Process Engine tools. Configuring UNIX for IBM FileNet P8 Platform servers (all components): To ensure hosts file contents, the /etc/hosts file must have the Internet Protocol (IP) address of the servers to be used. 1. Ensure hosts file contents. On each UNIX-based IBM FileNet P8 Platform server that does not use DNS (Domain Name Service) or NIS (Network Information Service), the /etc/hosts file must contain the name and IP address of all servers it will communicate with, including the remote database server, if applicable. Process Engine has additional requirements for hosts file entries. 2. Consult with the application server, database, and FileNet P8 administrators to determine port requirements for all the servers in your environment. For details, see Appendix B, IBM FileNet P8 ports, on page 227. Configuring Content Engine servers (all UNIX): You must specify the default file-creation permissions for the user who will install Content Engine. Content Engine running on a UNIX-based application server Use the UNIX utility program umask to set the default file-creation permissions mask for the Java Virtual Machine (JVM) instance that will host Content Engine so that the owner (the user running JVM) and the members of the owners group have read/write/execute access permissions, and all others have no access:
umask u=rwx,g=rwx,o=
160
This mask setting ensures that the access permissions on files and directories created by Content Engine are identical to those you must specify when creating file storage areas on UNIX file servers. Tip: This umask setting is required for the user who runs the Content Engine installer program, but does not need to be in the .profile file of the user. If you intend to move to UNIX for Content Engine when you upgrade from version 3.5 to 4.5 or later, consider the following. If you are upgrading from version 4.0 and want to move from Windows to UNIX, you must contact your IBM FileNet P8 representative and arrange a Professional Services engagement. v You must install Content Engine version 4.5 on UNIX as an initial step in the upgrade process. To migrate after you have completed the upgrade and begun using your system, you will have to contact your IBM FileNet P8 representative and arrange a Professional Services engagement. v You must temporarily leave your existing version 3.5.2 file stores (and associated index stores) on Windows to upgrade them using the IBM FileNet P8 Upgrader tool. This means that if you install Content Engine server on UNIX, you must have an NFS gateway in place (for example, Windows R2 Gateway or Samba) to enable communication between the new UNIX Content Engine server and Windows file storage areas and index areas. After they are upgraded, you can physically move the shared directories for the file storage areas and index areas to UNIX, but you must be sure to establish comparable security settings. For details on these settings, see the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Authorization Storage Area Security. Setting up Java SDK for Content Search Engine: Content Search Engine requires Java SDK on UNIX machines where you intend to install additional locales (other than English). To set up Java SDK: On each UNIX machine where you intend to install an additional locale (other than English), complete the following substeps: 1. Install the Java 1.4 SDK. 2. Set the PATH environment variable to install_path/Java14/bin, where install_path is the path to where you installed Java 1.4 SDK. Configuring Content Search Engine servers (UNIX): Content Search Engine requires that certain kernel parameters be specified and libraries installed. Configuring HP-UX servers for Content Search Engine To install Content Search Engine (Autonomy K2) on HP-UX, manually configure the kernel with following minimum-value parameters before you begin the Autonomy K2 Master Administration Server installation. Configuring HP-UX servers for Content Search Engine:
161
To install Content Search Engine (Autonomy K2) on HP-UX, manually configure the kernel with following minimum-value parameters before you begin the Autonomy K2 Master Administration Server installation. Tip: Depending on the version of your operating system, some of the following values are not used.
Value maxdsiz maxfiles maxfiles_lim maxssiz max_thread_proc maxswapchunks maxtsiz maxuprc maxusers nkthread nproc Setting 1.9 Gbytes (0x7B033000) 2048 2048 160 Mbytes (0xA000000) 1024 8192 1 Gbyte (0x40000000) 512 128 1024 517
Configuring Process Engine servers (all UNIX): Complete each of the following tasks to prepare the Process Engine server for upgrade. Configuring UNIX servers for Process Engine Verify that require configuration changes have been made on all UNIX-based Process Engine servers before upgrading. Configuring the /etc/hosts file on page 163 Information related to Process Engine IP address and server name must be entered into either the servers DNS table or the hosts file. Configuring UNIX servers for Process Engine: Verify that require configuration changes have been made on all UNIX-based Process Engine servers before upgrading. To configure UNIX servers for Process Engine, perform the following prerequisite tasks in any order: 1. Ensure the minimum /tmp directory size. The /tmp directory must have 510 MB free. 2. Save the following files for the root user: v .cshrc v .Xdefaults v .Xresources v .dbxinit v .dtprofile v .env v .login v .mwmrc
162
v .xinitrc v .profile 3. Process Engine requires the presence of several partitions. Before you install Process Engine, verify that your operating system is set up with a correctly configured volume manager. You can use the volume manager provided with the operating systems or an equivalent Veritas volume manager.
Volume Name fnsw Mount Point /fnsw file system local /fnsw/local file system 10 GB fnsw fnusr 775 Minimum Size 2 GB User fnsw Group fnusr Mode 775
Important: v (AIX 6.1 only) Permissions must be set correctly on both the /fnsw and /fnsw/local mount points and the file systems before mounting the file systems. v Solaris volume management software might use port 32776. This is the default for the Process Engine Communication Port (IOR port). v Allocate a minimum of 500 MB of additional disk space to the /fnsw disk volume. This space is required for upgrades and is in addition to the minimum space requirements called for in the IBM FileNet P8 Hardware and Software Requirements. Configuring the /etc/hosts file: Information related to Process Engine IP address and server name must be entered into either the servers DNS table or the hosts file. For non-farmed configurations, the information can be in either the DNS table or the hosts file on the server. For farmed configurations, the information must be entered into the host file. In a farmed environment, entries must exist for every Process Engine server in the farm. Entries must use the following format for each Process Engine server. The load balancer name must also be associated with the appropriate server in a farmed configuration.
IP_addr The IP address of the Process Engine server. hostname The corresponding host name, also referred to as the network name. This name must be < 32 characters and cannot contain any dots. Record this value in the Installation and Upgrade Worksheet as the network name and provide it to the Process Engine installation program. load_balancer_name The name of the load balancer in a farmed configuration. Following is an example of what entries in the hosts file might look like. In this example, both IPv4 and IPv6 addresses are included and cmepwin11 is the
163
hostname (network name). The NCH name should be in the file for existing Process Engine servers being upgraded. Do not remove it.
127.0.0.1 localhost ::1 localhost 2007:0:0:0:9:181:124:192 cmepwin11 cmepwin11-filenet-nch-server #fe80::fda2:48f4:7106:2f19%10 cmepwin11 cmepwin11-filenet-nch-server 123.45.6.78 cmepwin11 cmepwin11-filenet-nch-server
Configuring Process Engine servers (AIX): The following operating system prerequisites apply to AIX-based Process Engine servers. Configuring AIX servers for Process Engine You must change the time zone parameters to an option associated with your site. Modifying /etc/rc.dt for AIX 5.3 and 6.1 Configure network ports by modifying /etc/rc.dt. Configuring AIX servers for Process Engine: You must change the time zone parameters to an option associated with your site. Complete the following prerequisite tasks in any order: v The Kernel must be set to 64-bit mode. v The swap space must be set to 1.5 - 2 times RAM. v The Maximum Number of Processes allowed per user must be set to at least 400. v The Maximum Kbytes of real memory allowed for MBUFS must be set to 0. Setting the MBUFS parameter to 0 causes the system to use the default amount of available memory. This default amount is approximately 1/8 to 1/4 the amount of real memory. v The Maximum Number of FIXED licenses (Num) must be set to a minimum of 16. v The following filesets must be installed and committed: bos.adt.libm bos.adt.lib bos.adt.base bos.perf.perfstat bos.perf.libperfstat bos.adt.debug To configure AIX servers for Process Engine: 1. Review and change the time zone parameters if necessary. 2. In SMIT, choose System Environments Change/Show Date and Time Change Time Zone Using System Defined Values. 3. Choose the Daylight Savings Time option if applicable. 4. At the CUT Time Zone menu, choose the option associated with your site. For example, in California, the time zone needs to be set to the Pacific time zone (PST8PDT) Pacific U.S.; Yukon (cut -8). Modifying /etc/rc.dt for AIX 5.3 and 6.1: Configure network ports by modifying /etc/rc.dt.
164
To modify the network ports: 1. As the root user, run the following commands:
/usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no -p -p -p -p -p -p -p -p -o -o -o -o -o -o -o -o tcp_sendspace=16384 tcp_recvspace=16384 tcp_keepidle=80 tcp_keepintvl=20 tcp_ephemeral_high=65535 tcp_ephemeral_low=42767 udp_ephemeral_high=65535 udp_ephemeral_low=42767
This should result in these entries in the /etc/tunables/nextboot file:

no: tcp_ephemeral_high = "65535" tcp_ephemeral_low = "42767" tcp_keepidle = "80" tcp_keepintvl = "20" tcp_recvspace = "16384" tcp_sendspace = "16384" udp_ephemeral_high = "65535" udp_ephemeral_low = "42767"
2. If the CDE bundle is installed, the dtlogin daemon may bind to a required port before the kernel parameters listed above take effect. In order to avoid this problem, add the following statements at the beginning of the /etc/rc.dt file:
/usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no /usr/sbin/no -o -o -o -o -o -o -o -o tcp_sendspace=16384 tcp_recvspace=16384 tcp_keepidle=80 tcp_keepintvl=20 tcp_ephemeral_high=65535 tcp_ephemeral_low=42767 udp_ephemeral_high=65535 udp_ephemeral_low=42767
In some circumstances you may need to create an /etc/rc.dt file containing the commands above even if the CDE bundle is not installed. This is indicated by an error message when trying to start Process Engine similar to the following, where myserver is the name of the machine running Process Engine:
Retrying to connect to host 'myserver'... initfnsw: connect() failed with error 'connection refused'! Is TM_daemon running?
3. Restart the server (shutdown -Fr) for these settings to take effect. Executing the commands at the command line is not sufficient. The parameters must be in effect at boot time to avoid bind failures. 4. Check the values by executing the following commands:
no -a | grep ephemeral no -a | grep tcp
5. Check that the ports required by the Process Engine software have not been bound. The following command, entered as a single command line, should not produce any output:
for port in 32768 32769 32770 32771 32772 32773 32774 do netstat -an | grep $port done
Configuring Process Engine servers (HP-UX): The following operating system prerequisites apply to HP-UX-based Process Engine servers.
165
Configuring HP-UX servers for Process Engine Complete the following prerequisite tasks in any order. Performing symbolic links for X11 libraries Create symbolic links for X11 libraries on HP-UX servers. Configuring kernel parameters on page 167 Ensure that the following parameters are set to at least the values shown unless otherwise noted. The values are appropriate for both HP PA-RISC and Integrity operating systems unless noted otherwise. These values are sufficient to install and initialize the software but system tuning will be required, specifically for the nfiles and maxfiles parameters. Collecting kernel parameter information before you upgrade the Process Engine software on page 167 Before you upgrade, run the kmtune utility to collect current kernel parameter information and save the output. After the upgrade, use the HPjconfig utility to collect information on required patches and recommended kernel parameters. Checking and optionally modifying the timezone settings on page 168 HP-UX has two timezone settings: the kernel parameter timezone and the environment variable TZ. The value of both timezone settings must match. Review and, if necessary, change these settings on all Process Engine servers. Configuring HP-UX servers for Process Engine: Complete the following prerequisite tasks in any order. To configure HP-UX servers for Process Engine: v On each HP-UX 11 or HP-UX 11i machine where you will install a JVM-based IBM FileNet P8 Platform component (such as Content Engine), or where an associated JVM-based component (such as IBM WebSphere Application Server or Oracle WebLogic Server) will run, increase the values of the kernel parameters max_thread_proc (maximum number of threads per process) and nkthread (maximum number of kernel threads in the system) beyond their default values, which are too small for IBM FileNet P8 Platform applications. Refer to the HP web page Programmers guide for Java 2 HP-UX configuration for Java support for tools to determine values for these two kernel parameters that are sufficient for IBM FileNet P8 Platform. v Set the physical memory to at least 512 MB. v Set the Kernel to 64-bit mode. v Set the swap space as follows: Two times RAM if RAM < 1GB 1.5 times RAM if RAM between 1GB and 2GB Equal to RAM if between 2GB and 8GB .75 times RAM if > 8GB v Add the following entry to the /etc/nsswitch.conf file:
Performing symbolic links for X11 libraries: Create symbolic links for X11 libraries on HP-UX servers. 1. Log on as the root user. 2. At the prompt, run the following commands:
166
cd ln ln ln ln ln ln ln ln ln
/usr/lib -s /usr/lib/libX11.3 libX11.sl -s /usr/lib/libXIE.2 libXIE.sl -s /usr/lib/libXext.3 libXext.sl -s /usr/lib/libXhp11.3 libXhp11.sl -s /usr/lib/libXi.3 libXi.sl -s /usr/lib/libXm.4 libXm.sl -s /usr/lib/libXp.2 libXp.sl -s /usr/lib/libXt.3 libXt.sl -s /usr/lib/libXtst.2 libXtst.sl
Configuring kernel parameters: Ensure that the following parameters are set to at least the values shown unless otherwise noted. The values are appropriate for both HP PA-RISC and Integrity operating systems unless noted otherwise. These values are sufficient to install and initialize the software but system tuning will be required, specifically for the nfiles and maxfiles parameters.
Minimum Setting Minimum Setting Kernel Parameter maxdsiz maxfiles nproc maxuprc nfile ninode semmns semmni shmmax shmseg semmnu semume msgmni msgseg msgtql msgmap dbc_max_pct PA-RISC 0x10000000 or 268435456 (256MB) 512 1005 400 1024 1085 2000 2000 0x10000000 or 268435456 (256MB) 120 1000 500 2048 16384 6640 msgtql + 2 1 to 10 (the value can not be greater than 30) 5 Set appropriately 65535 65535 Integrity V2 and V3 unless noted otherwise 0x10000000 or 268435456 (256MB) 1024 1005 400 2048 1085 2000 2000 0x20000000 or 536870912 (512MB) 120 1000 500 2048 16384 (obsolete in HP 11i V3) 6640 msgtql + 2 (obsolete in HP 11i V3 1 to 30 (the value can not be greater than 30) (obsolete in HP 11i V3) 5 (obsolete in HP 11i V3) Set appropriately 65535 65535
dbc_min_pct timezone msgmnb (DB2 only) msgmax (DB2 only)
Collecting kernel parameter information before you upgrade the Process Engine software:
167
Before you upgrade, run the kmtune utility to collect current kernel parameter information and save the output. After the upgrade, use the HPjconfig utility to collect information on required patches and recommended kernel parameters. The HPjconfig utilitys recommendations for the kernel parameters are based on analysis of historical data on the server. See the HP Web site for configuration details. Checking and optionally modifying the timezone settings: HP-UX has two timezone settings: the kernel parameter timezone and the environment variable TZ. The value of both timezone settings must match. Review and, if necessary, change these settings on all Process Engine servers. To 1. 2. 3. check the timezone settings: As the root user, enter: sam Select the Kernel Configuration option. Select the Configurable Parameters option, then check the Pending Value for the timezone parameter. The default value is 420 minutes west of Greenwich Mean Time (GMT), which is the U.S. Mountain timezone. Determine the number of minutes east or west of GMT for your location by multiplying the number of hours east or west of GMT by 60 minutes per hour. For example, the U.S. Pacific timezone is 8 hours west of GMT. Multiply 8 x 60 to get 480 minutes. If your timezone location is east of GMT, you should use a negative number. For example, Middle European Time is one hour east of GMT. Multiply -1 x 60 to get -60 minutes for MET (Middle European Time). 4. If the Pending Value for the timezone parameter is correct, proceed to step 6. To change the value, continue with Step 5. 5. To change the timezone kernel parameter value: a. Select the timezone parameter by pressing the spacebar and then press Tab to go to the Actions menu. b. Select the Modify Configurable Parameter option from the Actions menu and press Return. c. In the popup window, the Specify New Formula/Value option should already be selected. d. Tab to the Formula/Value field and type the new value. e. Tab to OK and press Return. When the popup window disappears, you should see the new value in the Pending Value column. f. Rebuild the kernel to make your change take effect: 1) Press the F4 key to access the menu bar. 2) From the Action menu, select the Create a New Kernel option using the Arrow keys and press Return. 3) Answer Yes when prompted about creating the kernel now. 4) On the next screen, make sure the Move Kernel into Place and Shutdown/Reboot the System Now option is selected, tab to OK and press the Return key to reboot the system and make the new changes take affect. 6. As the root user, enter the following to check the current value of the TZ environment variable:
echo $TZ
168
7. If the current setting is not correct, enter the following to set the correct timezone:
/sbin/set_parms timezone
Choose the appropriate timezone from the menus displayed. Remember that the value must match that of the timezone kernel parameter. If you change the current setting, you will be prompted to reboot the server. If the HP-UX set_parms command is not available on your server, the timezone might be set via the SAM interface using the Kernel Parameters option in the same manner that other parameters are set. The System Administrator should consult the HP-UX operating system documentation to determine the appropriate way to set the TZ environment variable. Configuring Process Engine servers (Solaris): The operating system prerequisites in this subsection pertain to Solaris-based Process Engine servers. Enabling ports When Solaris starts up, it takes the first several ports, called anon ports, to use for its communication daemons. By default, the maximum tcp_smallest_anon_port is 32768. IBM FileNet P8 Platform uses several ports higher than 32768. Verifying national language character set and time settings on page 170 Verify the national language character set and time settings on a Solaris-based Process Engine server. Increasing the operating system kernel limits (Solaris 9) for Process Engine on page 170 Increase or verify Solaris 9 operating system kernel limits before upgrading Process Engine software. Increasing the operating system kernel limits (Solaris 10) for Process Engine on page 171 Increase or verify Solaris 10 operating system kernel limits before upgrading Process Engine software. Enabling ports: When Solaris starts up, it takes the first several ports, called anon ports, to use for its communication daemons. By default, the maximum tcp_smallest_anon_port is 32768. IBM FileNet P8 Platform uses several ports higher than 32768. See Appendix B, IBM FileNet P8 ports, on page 227 for details on which ports IBM FileNet P8 uses. To use these ports on Solaris-based systems, you must first enable the ports by setting the smallest anon port to 32778. By doing so, the ports used by Solaris communication daemons will be 32778 or greater, leaving 32777 available for IBM FileNet P8 use. The Solaris platform provides several different tools, such as the netstat command, to determine if a port is in use. 1. Determine the currenttcp_smallest_anon_port setting. 2. From a command prompt, enter the following command:
ndd -get /dev/tcptcp_smallest_anon_port
169
3. Enable port 32777. If the port returned in the step above is less than 32778, you must enable port 32777. Solaris 9 Edit the /etc/rc2.d/S69inet file. Add the following line before the exit 0 entry at the bottom of the file:
ndd -set /dev/tcptcp_smallest_anon_port 32778
ndd -set /dev/tcptcp_smallest_anon_port 32778
4. Reboot the Process Engine server to force the release of ports required by Process Engine that might be in use by the operating system. Failure to reboot after these changes are made can result in port 32776 being unavailable, generating OpenSocket errors. Verifying national language character set and time settings: Verify the national language character set and time settings on a Solaris-based Process Engine server. To verify the national language character set and time settings: 1. The default time mask varies on UNIX depending on the LANG and LC_TIME environment settings. Verify the current LC_TIME settings by entering:
locale -k t_fmt
The result might appear similar to this:

t_fmt=%r
2. The default mask must not be %r. To change to a default mask that can be used with NLT, reset the LC_TIME environment to C, then run the locale -k t_fmt command again to verify the change. 3. The default shell environment should be modified to use the C time format. 4. Change the /etc/profile for the entire system or change the .profile file for each user that runs sh or ksh to include the following lines:
LC_TIME=C export LC_TIME
5. Verify the current LANG settings by entering locale at the shell prompt. This example shows the U.S. character set, ISO 8859-1. Be sure it is consistent with the database character set unless your database character set is AL32UTF8 (Unicode).
LANG=en_US.ISO8859-1 LC_CTYPE=en_US.ISO8859-1 LC_NUMERIC=en_US.ISO8859-1 LC_TIME=en_US.ISO8859-1 LC_COLLATE=en_US.ISO8859-1 LC_MONETARY=en_US.ISO8859-1 LC_MESSAGES=en_US.ISO8859-1 LC_ALL=
Increasing the operating system kernel limits (Solaris 9) for Process Engine: Increase or verify Solaris 9 operating system kernel limits before upgrading Process Engine software. 1. Make a copy of the system file (with a new name). Log on as root, and enter a command similar to the following command:
170
vi /etc/system
3. Ensure that the following parameters are listed and are set to at least the values shown. Solaris 9
set semsys:seminfo_semmap=50 set semsys:seminfo_semmni=2000 set semsys:seminfo_semmns=2000 set semsys:seminfo_semmnu=500 set semsys:seminfo_semmsl=512 set semsys:seminfo_semopm=256 set semsys:seminfo_semume=500 set semsys:seminfo_semvmx=32767 set semsys:seminfo_semaem=16384 set shmsys:shminfo_shmmax=4294967295* set shmsys:shminfo_shmmin=0 set shmsys:shminfo_shmmni=2000 set shmsys:shminfo_shmseg=100 set msgsys:msginfo_msgmni=2048 set max_nprocs=1000 set fnsod:sod_Debug=0 set rlim_fd_max=1024 set rlim_fd_cur=256 noexec_user_stack=1
DB2 also requires these settings:

set msgsys:msginfo_msgmax=65535 set msgsys:msginfo_msgmnb=65536
Increasing the operating system kernel limits (Solaris 10) for Process Engine: Increase or verify Solaris 10 operating system kernel limits before upgrading Process Engine software. The values of the parameters in the project file override the values of the parameters in the /etc/system file. Make sure that the values of the parameters in the project file are the same as or greater than the values of the parameters in the /etc/system file. Solaris 10 provides the Resource Control Facility feature for setting kernel parameters. Refer to the Solaris 10 documentation on the Sun Web site for information about this feature. Kernel parameter changes should be made to the Solaris Resource Control Facility whether or not you are using zones in Solaris 10. In a configuration with zones, make these changes in the global zone. 1. Logon as fnsw. 2. Enter the following command at the shell prompt: prctl $$ 3. Verify the values are set to at least the minimum values indicated for Process Engine *maxusers - 2048 or server physical memory (in MB), whichever is less.
Kernel Parameter max-sem-nsems max-sem-ops max-sem-ids max-shm-ids Solaris 10 default 512 512 128 128 Solaris 10 for Process Engine 1024 1024 2048 2048
171
Kernel Parameter max-msg-ids max-shm-memory max_nprocs Rlim_fd_max Rlim_fd_cur Noexec_user_stack max-msg-qbytes Msgtql (process.max-msgmessages)
Solaris 10 default 128 1/4 Physical memory 10 + (16 x maxusers)* 65536 256 0 65536 8192
Solaris 10 for Process Engine 2048 1/4 Physical memory default 65536 256 1 65536 65536
4. Logged on as the root user, copy the project and the system file.
cp /etc/project /etc/project.save mv /etc/system /etc/system.save
5. View the current settings for the fnsw user, and the Oracle user. For theFileNet software user, enter:
su - fnsw projects -l
For the Oracle user, enter:

su - oracle projects -l
6. Return to the user with root privileges. 7. If a project does not exist for the fnsw user, enter the following command to add one:
projadd -U fnsw -K "project.max-shm-memory=(priv,7G,deny)" user.fnsw
8. If a project does exist for the fnsw user, enter the following command:
projmod -sK "project.max-shm-memory=(priv,7G,deny)" user.fnsw
Update other kernel parameters required for the fnsw user in /etc/project, for example:
projmod -sK "project.max-shm-ids=(priv,2048,deny)" user.fnsw projmod -sK "project.max-msg-ids=(priv,2048,deny)" user.fnsw projmod -sK "project.max-sem-ids=(priv,2048,deny)" user.fnsw projmod -sK "process.max-msg-messages=(priv,65536,deny)" user.fnsw projmod -sK "process.max-msg-qbytes=(priv,65536,deny)" user.fnsw projadd -U fnsw -K "project.max-shm-memory=(priv,7G,deny)" user.fnsw projmod -sK "project.max-sem-nsems=(priv,1024,deny)" user.fnsw projmod -sK "project.max-sem-ops=(priv,1024,deny)" user.fnsw projmod -sK "project.max-device-locked-memory=(priv,3.9G,deny)" user.fnsw projmod -sK "project.max-shm-ids=(priv,2k,deny)" user.fnsw projmod -sK "process.max-msg-messages=(priv,1.02k,deny)" user.fnsw projmod -sK "process.max-sem-ops=(priv,1k,deny)" user.fnsw projmod -sK "process.max-sem-nsems=(priv,1.02k,deny)" user.fnsw
9. If a project does not exist for the RDBMS software user, such as oracle, enter the following command to create one:
projadd -U oracle -K "project.max-shm-memory=(priv,7G,deny)" user.oracle
172
10. If a project does exist for the RDBMS user, such as oracle, enter the following command:
projmod -sK "project.max-shm-memory=(priv,7G,deny)" user.oracle
11. Update the following kernel parameters. These changes are not necessary if the value is already set to a higher value.
projmod -sK "project.max-shm-memory=(priv,7G,deny)" user.root projmod -sK "project.max-shm-memory=(priv,7G,deny)" system projmod -sK "project.max-shm-memory=(priv,7G,deny)" default
12. Make a copy of the system file (with a new name).

vi /etc/system
Add the following value to the file:

set noexec_user_stack=1
14. Exit the file and save your changes. 15. Verify the new active kernel values for both FileNet and Oracle users match the projects -l output you saw in step 5 on page 172. For the fnsw user, enter:
su - fnsw prctl $$
For the Oracle user, enter:

su - oracle prctl $$
16. Verify the /etc/system file by entering:

more /etc/system
Configuring Linux servers for Application Engine or Workplace XT: Ensure that Linux libraries are installed. To install Application Engine or Workplace XT on Linux, several legacy libraries are required. You must install the compat-libstdc++ packages on your Red Hat system prior to beginning your install of Application Engine or Workplace XT. Configuring Application Engine or Workplace XT servers (HP-UX): Add an entry to the /etc/nsswitch.conf to enable communication with Process Engine tools. On each HP-UX 11 or HP-UX 11i machine where you will install Application Engine or Workplace XT, add the following entry to the /etc/nsswitch.conf file:
Configuring Microsoft Windows

Verify that any Windows server configuration changes have been made in preparation for upgrading IBM FileNet P8 software. Configuring Windows for IBM FileNet P8 Platform servers (all components) on page 174 Upgrade to Windows 2003 before you begin the upgrade process to IBM FileNet P8 Platform version 4.5. Configuring Windows for Enterprise Manager, .NET and COM compatibility clients on page 174
173
On any Windows machine where you are going to install Content Engine or Enterprise Manager (Content Engine is a Java application that can optionally be installed on Windows; Enterprise Manager must be installed on Windows), you must first install Microsoft .NET Framework, and Web Services Enhancements (WSE). Configuring Windows for Content Engine on active directory on page 175 If you are using Windows Active Directory for your directory service, set the primary DNS. Configuring Windows for Process Engine on page 175 Configure the Windows server before upgrading Process Engine. Configuring Windows for Content Search Engine on page 177 To configure security for Content Search Engine servers, set k2_os_user as an administrator on each Windows Content Search Engine server. Configuring Windows for IBM FileNet P8 Platform servers (all components): Upgrade to Windows 2003 before you begin the upgrade process to IBM FileNet P8 Platform version 4.5. v See the IBM FileNet P8 Hardware and Software Requirements for details on any required Window 2003 Service Packs and patches. Important: (3.5 to 4.5 upgrades only) IBM FileNet P8 Platform field personnel indicate that most customers prefer to do a fresh installation of Windows 2003 rather than upgrading the Windows 2000 software. This will require you to install Content Engine 4.5 on its own Windows 2003 server (separate from the version 3.5. 2 Content Engine server). v (3.5 to 4.5 upgrades only) Ensure proper upgrade to Windows 2003 on your existing Content Engine version 3.5.2 servers prior to your IBM FileNet P8 Platform upgrade. If you do want to upgrade to Windows 2003 on your Content Engine version 3.5.2 servers and intend to run them for any length of time before you upgrade to Content Engine version 4.5, be sure to see the Configure Content Engine and SQL Servers for Windows 2003 in the IBM FileNet P8 Platform Installation and Upgrade Guide for version 3.5 for important details and procedures. v Ensure that you have the necessary Windows clients for Enterprise Manager version 4.5. Although Content Engine runs on UNIX as well as Windows, the Enterprise Manager administrative client still runs on Windows only. For upgrade purposes, it is a best practice to install Enterprise Manager version 4.5 on a separate client than the current Enterprise Manager version 3.5 or 4.0, so that you can access the version 3.5.2 or 4.0 object stores that have not been upgraded yet. If you install Enterprise Manager version 4.5 on a client running the previous version, the older version will be upgraded and you will not be able to access the previous version object stores from the version 4.5 Enterprise Manager. v Consult with the application server, database, and FileNet P8 administrators to determine port requirements for all the servers in your installation environment. For details, see Appendix B, IBM FileNet P8 ports, on page 227. Configuring Windows for Enterprise Manager, .NET and COM compatibility clients: On any Windows machine where you are going to install Content Engine or Enterprise Manager (Content Engine is a Java application that can optionally be
174
installed on Windows; Enterprise Manager must be installed on Windows), you must first install Microsoft .NET Framework, and Web Services Enhancements (WSE). Check the IBM FileNet P8 Hardware and Software Requirements for the latest version requirements of these two components. Enterprise Manager requires no other Content Engine services or files. Configuring Windows for Content Engine on active directory: If you are using Windows Active Directory for your directory service, set the primary DNS. If Windows Active Directory is your directory service, set the primary DNS server IP address on your Content Engine application server to the IP address of the machine where DNS is installed. Configuring Windows for Process Engine: Configure the Windows server before upgrading Process Engine. Verifying TCP/IP parameter settings (Windows) If you log on with administrative privileges, you can run regedit to verify registry key values and add or modify a REG_DWORD value. Adding inbound rules to the Windows 2008 firewall Configure inbound rules in the Windows 2008 firewall to allow the following Process Engine ports access. Configuring the /etc/hosts file on page 176 Information related to Process Engine IP address and server name must be entered into either the servers DNS table or the hosts file. Configuring Process Engine clients for ORB (Windows) on page 176 Process Engine clients require either the IBM or the Sun Object Request Broker (ORB). Verifying TCP/IP parameter settings (Windows): If you log on with administrative privileges, you can run regedit to verify registry key values and add or modify a REG_DWORD value. To verify TCP/IP parameter settings: 1. Log on as a user with administrative privileges and run regedit to verify the following registry key values. Important: The values below are decimal. The default in regedit is hexadecimal.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ MaxUserPort => 65534 (default = 5000) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ TcpTimedWaitDelay=> 90 (default = 240, or 4 min)
2. If necessary, add or modify a REG_DWORD value with the values as described above and save the changes. Adding inbound rules to the Windows 2008 firewall:
175
Configure inbound rules in the Windows 2008 firewall to allow the following Process Engine ports access.
Port 32768 32769 32770 Protocol TCP TCP UDP
Configuring the /etc/hosts file: Information related to Process Engine IP address and server name must be entered into either the servers DNS table or the hosts file. For non-farmed configurations, the information can be in either the DNS table or the hosts file on the server. For farmed configurations, the information must be entered into the host file. In a farmed environment, entries must exist for every Process Engine server in the farm. Entries must use the following format for each Process Engine server. The load balancer name must also be associated with the appropriate server in a farmed configuration.
IP_addr The IP address of the Process Engine server. hostname The corresponding host name, also referred to as the network name. This name must be < 32 characters and cannot contain any dots. Record this value in the Installation and Upgrade Worksheet as the network name and provide it to the Process Engine installation program. load_balancer_name The name of the load balancer in a farmed configuration. Following is an example of what entries in the hosts file might look like. In this example, both IPv4 and IPv6 addresses are included and cmepwin11 is the hostname (network name). The NCH name should be in the file for existing Process Engine servers being upgraded. Do not remove it.
127.0.0.1 localhost ::1 localhost 2007:0:0:0:9:181:124:192 cmepwin11 cmepwin11-filenet-nch-server #fe80::fda2:48f4:7106:2f19%10 cmepwin11 cmepwin11-filenet-nch-server 123.45.6.78 cmepwin11 cmepwin11-filenet-nch-server
Configuring Process Engine clients for ORB (Windows): Process Engine clients require either the IBM or the Sun Object Request Broker (ORB). This applies to the following configurations: v J2EE application server clients such as Workplace or Workplace XT v Content Engine when using the workflow subscription processor to launch workflows v Non-J2EE and custom applications
176
Therefore, if you have Windows-based non-J2EE and custom applications, configure the Java installation on those servers with either the IBM or the Sun ORB.
JBoss Application Server Installed via JEMS No changes are required if you installed the JBoss Enterprise Middleware System Installer JBoss Application Server by installing the with IBM or Sun JVM JBoss Enterprise Middleware Software with the Default option. Oracle WebLogic Server with the Sun JVM WebLogic Server with the JRockit JVM No changes are required. Replace the default JBoss Application Server ORB with the Sun ORB by adding the following code to your application server startup file. Enter without carriage returns: set JAVA_OPTIONS=%JAVA_OPTIONS% -Dorg.omg.CORBA.ORBClass =com.sun.corba.se.impl.orb.ORBImpl set JAVA_OPTIONS=%JAVA_OPTIONS% -Dorg.omg.CORBA.ORBSingletonClass =com.sun.corba.se.impl.orb.ORBSingleton
Configuring Windows for Content Search Engine: To configure security for Content Search Engine servers, set k2_os_user as an administrator on each Windows Content Search Engine server. Important: For Content Engine version 3.5. to version 4.5 upgrades, where Content Engine version 4.5 will be on UNIX, Content Search Engine version 4.5 must also be installed on a UNIX server. Ensure that the accounts required include the UNIX operating system accounts. To configure Windows for Content Search Engine: 1. Set the k2_os_user user as an administrator on each Windows Content Search Engine server. 2. On each Windows machine where you intend to install an additional locale (other than English), complete the following substeps: a. Install the Java 1.4 SDK. b. Set the PATH environment variable to install_path\Java14\bin, where install_path is the path to where you installed Java 1.4 SDK. 3. Set the JAVA_HOME environment variable on each machine where you will install Content Search Engine software, as follows: a. Open the System control panel. b. Click the Advanced tab. c. Click Environment Variables . d. Click New under System Variables. e. Set the variable information as follows: Variable name: JAV A_HOME
177
Variable value: Java (JDK) install path Important: The Content Search Engine installation program will not allow you proceed until the JAVA_HOME environment variable is set. 4. Set the PATH environment variable as follows: a. Open the System control panel. b. Click the Advanced tab. c. Click Environment Variables. d. Click PATH under System Variables. e. Append the variable information as follows: ;%JAVA_HOME%\bin
Configuring network
Configure the network to prepare for your IBM FileNet P8 Platform upgrade. Configuring your network Ensure that your TCP/IP settings are configured so that your servers and clients can communicate with one another. Synchronizing time and date System users will experience a variety of problems if one or more servers do not have time and date settings synchronized with the rest of the system. Assigning directory permissions for Content Engine upgrade for 4.0 to 4.5 on UNIX on page 179 For upgrades from Content Engine version 4.0 to 4.5 on UNIX, you change the installation user. Preparing Process Engine for upgrade on page 180 Repair any inconsistencies between Process Engine queues and rosters in the Process Engine database, reconcile user security information and prepare Process Analyzer data for upgrade. Configuring your network: Ensure that your TCP/IP settings are configured so that your servers and clients can communicate with one another. Complete the following prerequisite tasks in any order: v Assign all IBM FileNet P8 Platform servers a static IP address. v Ensure TCP/IP settings. Verify TCP/IP configuration settings on all UNIX and Windows servers and Enterprise Manager clients intended for IBM FileNet P8 Platform so that they can all communicate with one another. v Ensure NetBIOS over TCP/IP is enabled on Windows. v Ensure availability of required port numbers. Several port numbers are required by the various IBM FileNet P8 Platform components. Appendix B, IBM FileNet P8 ports, on page 227 v For information about proxy firewall configuration requirements, see the IBM FileNet P8 Hardware and Software Requirements for support information related to IBM FileNet P8 Platform components and database engines. Synchronizing time and date: System users will experience a variety of problems if one or more servers do not have time and date settings synchronized with the rest of the system.
178
The Process Engine database server (the machine that hosts the database used by Process Engine) is considered the master time keeper; the UTC time of that machine is considered the correct time. The server hosting the Process Engine API and the server hosting Content Engine must have the UTC time set to match the UTC time on the Process Engine database server, plus or minus 15 minutes. v To change the time on the machine hosting Process Engine, you must stop the server. In a farmed Process Engine system, if you want to change the time of one of the servers in the farm, stop only that server. v To change the time in the machine hosting the Process Engine API, be sure it is not connected to any Process Engine system. If the API is connected to a Process Engine server, and you change the time, you will experience authentication errors, and you might have to log on again. v If your Content Engine server is being used with a Process Engine server, and you change the time on the Content Engine server, you will experience authentication errors in Process Engine and you might have to log on again. Assigning directory permissions for Content Engine upgrade for 4.0 to 4.5 on UNIX: For upgrades from Content Engine version 4.0 to 4.5 on UNIX, you change the installation user. To assign directory permissions to the user (ce_upgrade_user) who will upgrade Content Engine: 1. Determine which user installed the current version of Content Engine. If you do not know who installed the current version, log on to the application server as any user and inspect the properties of the Content Engine install directory (the default install directory is Content Engine). Restriction: (AIX only) Only the root user is able to install the current (4.0) version of Content Engine. This restriction is not in effect for the new (4.5) version. 2. Designate the user, referred to as ce_upgrade_user, who will install the new version of Content Engine. The additional preparation, if any, that you must perform depends on two factors: v Whether the user who installed the current version of Content Engine is identical to the user who will install the new version. v The type of operating system on the machine that hosts the application server where Content Engine is deployed. 3. Continue on if either of the following conditions holds: v The two users are not identical, and Content Engine is deployed on UNIX. v The user who will install Content Engine is non-root, and Content Engine is deployed on AIX. If neither of the above conditions holds, skip the remainder of this procedure. 4. Log on to the application server as the user who installed the current version of Content Engine. 5. Navigate to the Content Engine directory and recursively give ownership of this directory and all its files and subdirectories to the user who will install the new version of Content Engine. For example, if Content Engine is installed at /opt/FileNet/ContentEngine , then to give ownership to ce_upgrade_user, the user who will install the new version, run the following command:
chown -R ce_install_user /opt/FileNet/ContentEngine
179
6. Delete all files and directories in the /tmp directory owned by the previous ce_install_user. 7. Log on to the server as the user who initially installed the application server and created the application server instance (profile for WebSphere Application Server, domain for WebLogic Server, server for JBoss Application Server). 8. Navigate to the application server instance directory, and give group rights to the ce_appserver_install_group (whos members are the ce_install_user and ce_appserver_install_user). For example:
chgrp -R ce_appserver_install_group /opt/IBM/Websphere/Appserver /profiles/Appsvr01
9. Give ce_appserver_install_group read/write permissions. For example:

chmod -R 775//opt/IBM/Websphere/Appserver/profiles/Appsvr01
10. Log off the application server and log back on as the user who will install the new version of Content Engine. 11. Grant read, write, and execute permissions on the Content Engine directories to the user who will install the new version of Content Engine, as follows:
chmod -R +rwx /opt/FileNet/ContentEngine
12. Copy the Install Shield directory from the $HOME directory of the user who installed the current version of Content Engine to the $HOME of the user who will install the new version and grant read, write, and execute permissions to the user who will install the new version. Preparing Process Engine for upgrade: Repair any inconsistencies between Process Engine queues and rosters in the Process Engine database, reconcile user security information and prepare Process Analyzer data for upgrade. v Use the vwverify program and see the IBM FileNet P8 help topic FileNet P8 Administration Process Engine Administration Administrative tools vwverify for information on the program. v (3.5 to 4.5) Reconcile the Process Engine user security information. The Process Engine duplicates certain parts of the user security information in its own database. Over time, the information in the directory service might be changed or updated. When this happens, the information in the environment records for Process Engine, whether cached or permanent, can end up containing old, invalid information about the Process Engine users and groups. During the Process Engine upgrade it is critical that this user information is correct and up to date. Before upgrading you must reconcile the cached and permanent user data environment records on the Process Engine with the possibly more-up-to-date data in an LDAP-based directory service. For more information, see the IBM FileNet P8 help topic FileNet P8 Administration Process Engine Administration Administrative tools vwtool Commands environment. v (3.5 to 4.5) If you are using the IBM FileNet Process Analyzer expansion product, several steps must be taken on the Process Analyzer, on the Process Engine database, and on Process Engine, before upgrading Process Engine.
Security administrator upgrade tasks

The Security administrator must prepare the security environment for IBM FileNet P8 Platform upgrade, including planning the security environment, and creating accounts.
180
v Review all rows assigned to the Security Administrator (SA) for upgrades in the Installation and Upgrade Worksheet. Provide values for any rows appropriate to your installation that you have not yet completed. Tip: With the Data Filter AutoFilter command enabled, as it is by default in the shipping worksheet file (p8_worksheet.xls), perform the following actions to quickly see only the properties assigned to a particular role: Click the AutoFilter drop-down arrow in the Role column header and select SA. Further filter the result set by clicking the AutoFilter drop-down arrow in any of the other columns and selecting a value or clear a filter by selecting All. Security upgrade planning considerations Review the security requirements for systems being upgraded. There are numerous changes and requirements for new users and groups as well as changes related to directory services. Specifying IBM FileNet P8 accounts for upgrades on page 183 You can create or designate the accounts needed to upgrade and configure IBM FileNet P8 by a display name, by a variable designator, by a name that looks like a variable but is not formatted in italics.
Security upgrade planning considerations

Review the security requirements for systems being upgraded. There are numerous changes and requirements for new users and groups as well as changes related to directory services. v (upgrades from 3.5 only) Complete any migration to a different directory service prior to the 4.5 upgrade. See the IBM FileNet P8 Platform 3.5 Directory Service Migration Guide for complete information. Migrating to a different directory service is not supported if you begin your upgrade from the 4.0 release or after you are running the 4.5 release. Contact your IBM FileNet representative if you intend to switch to IBM Tivoli Directory Server, which is supported for IBM FileNet P8 4.5, but not for 3.5. v Review updated user and group account requirements for release 4.5. The 4.5 release requires you to designate or create several new accounts (for example, the Configuration Manager user). For details, see Specifying IBM FileNet P8 accounts for upgrades on page 183. v (upgrades from 3.5 only) Determine whether you intend to use Secure Socket Layers (SSL). It is a best practice to use SSL to strengthen security. Configuring SSL for 4.5 is noticeably different than for 3.5. For example, Content Engine 4.5 now relies on its own application server to direct calls to your chosen authentication provider. v (upgrades from 3.5 only) Gather 3.5 authentication information and plan 4.5 authentication. In the 3.5 release, Content Engine authentication and authorization information are both specified by configuring one or more authentication providers, using Active Directory, Novell eDirectory, or Sun Java System Directory Server. For Novell and Sun authentication providers, the root of the configured 3.5 Directory Service contains one or many children, or naming contexts, each of which are used automatically by 3.5 Content Engine as IBM FileNet P8 authentication realms. For Windows Active Directory, the 3.5 Content Engine uses the Windows domain (also known as deployment domain) it resides in and automatically
181
gets all trusted domains, siblings, parents, children within the domains forest. By default, the deployment domain is the default realm. 3.5 authentication realms are viewable (but not editable) in Enterprise Managers root domain property sheet Authentication Provider DefaultRealm property. The names of all realms for the current IBM FileNet P8 domain appear as values in the drop-down list for this property. Important: If you are using the 3.5 Content Engine attributes DefaultRealm and RestrictToDefaultRealm to modify 3.5 authentication behavior, then you must carefully map out which 3.5 authentication realms are active and essential to your upgraded 4.5 Content Engine authentication scheme. The DefaultRealm and RestrictToDefaultRealm attributes are not supported by Content Engine 4.5, because of the introduction of the application server, which uses Java Authentication and Authorization Service (JAAS) for authentication. By contrast, in Content Engine 4.5, configuring authentication and authorization are two separate steps, both of which must be completed on the Content Engine 4.5 server environment before upgrading object stores from 3.5. Authentication is configured through the application servers administration console. Authorization is configured by creating one or more Directory Configuration objects in Content Engine 4.5 for the IBM FileNet P8 domain. (The 3.5 authentication information is not carried forward by the Content Engine 3.5.2 to 4.5 Upgrader tool.) Therefore, the following are prerequisites to upgrading a 3.5 domain: v Install and configure one of the supported J2EE application servers, using the application servers install tools. v Install a Content Engine 4.5 server as an application into the application server, using the Content Engine installation program. v Configure the authentication environment through Configuration Manager. v Create a Content Engine 4.5 domain, using the Enterprise Managers Add Domain Configuration wizard. v Create one or more Directory Configurations, using the Enterprise Managers Create a Directory Configuration wizard. One Directory Configuration is required for each distinct 3.5 authentication realm. There are several cases that might exist for this last bullet. In all cases, Directory Configurations must be created that preserve access to all users who have used the object stores being upgraded. Access to all users SIDs and group information is necessary for authorization to occur. v In the typical case, you will create one 4.5 Directory Configuration object for each realm used in 3.5, specifying the same directory server (LDAP) host and port information that was used in Content Engine 3.5. v In some cases customers might choose to do the following configurations: Configure the Content Engine 4.5 server to obtain directory configuration information from a different directory server than was used in Content Engine 3.5 (for instance by using a replica of the 3.5 directory service which contains the same user or group information). OR Expand the users of the Content Engine 4.5 domain being upgraded by adding additional realms. If this is the case, then the set of Directory Configurations that must be created for the new 4.5 domain could differ from the set of realms that were configured in 3.5. Just make sure that the 4.5 Directory Configurations contain the same user and group principals, with the exact same SIDs, as those used in Content Engine 3.5.
182
Remember that users in the newly added realms will have no authorization to access any Content Engine 4.5 objects until they are explicitly granted authorization to do so, typically by using Enterprise Manager in ways described in the Help for Content Engine Administration.
Specifying IBM FileNet P8 accounts for upgrades

You can create or designate the accounts needed to upgrade and configure IBM FileNet P8 by a display name, by a variable designator, by a name that looks like a variable but is not formatted in italics. For a complete list of the user and group roles, accounts, and responsibilities required to install, configure, and maintain an IBM FileNet P8 system, see the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Users and groups. Accounts are referred to in documentation in the following ways: v By a display name; for example, Database User Name. An accounts display name is how the IBM FileNet P8 user interface, such as a setup program or dialog box, refers to the account. Many accounts have both a display name and a variable. v By a variable designator; for example ce_db_user, using lower-cased italics and underscores. The variable is intended to show that you must designate your own account to act in the role described by the variable. Accounts that do not appear in an interface or configuration file will have only a variable designator. An example of this is ce_install_user , the account you log in as to run the Content Engine setup program. v By a name that looks like a variable but is not formatted in italics. Examples are the f_maint and f_sw required accounts for the Process Engine, which, because they are not italicized, are not to be replaced by accounts of your choosing. If you see a reference to an account that you do not understand, search the Plan and Prepare Your Environment for IBM FileNet P8 guide for that reference and find the account table that defines it. Creating Content Engine directory server accounts Create new or designate existing directory server installation accounts for Content Engine, as shown in the following table. Creating Content Engine directory server accounts: Create new or designate existing directory server installation accounts for Content Engine, as shown in the following table.
183
User or group name Bootstrap user name: ce_bootstrap_admin
Description An directory service and application server account that is stored in the CEMPBoot.properties file that is archived in the Content Engine EAR file. Also known as Content Engine System User. Content Engine uses ce_bootstrap_admin to establish a connection with the application server, access the application servers JNDI tree, and look up the data sources for accessing the GCD. If you are deploying Content Engine on an application server (IBM WebSphere Application Server 6.1.x or higher, Oracle WebLogic Server, or JBoss Application Server) with federated user repositories and with multiple realms in yourIBM FileNet P8 domain, be sure that no two realms contain the same short name for this user; otherwise, this user will not be able to create the GCD. See the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Users and groups for information on how ce_bootstrap_admin is the creator of the new IBM FileNet P8 domain. This user must also have read/write access to the root directories for the IBM FileNet P8 3.5 file stores. If version 3.5 file stores are on a SnapLock fixed content device, then this user must also have read/write access to the device.
Content Engine Upgrader tool user: ce_upgrade_user
The Windows operating system user who runs the Upgrader tool needs the following permissions: v Read access to the Content Engine 3.5 directory (default location is C:\Program Feils\IBM\FileNet\Content Engine). v Read access to the 3.5 version of sysinit.dat. v Read/write access to the root directories for the file storage areas
184
User or group name Content Engine Setup: Windows: ce_install_user
Description For upgrading from version 3.5, you can use the existing Content Engine install user, or designate a new user. An operating system account you will use to log on to a machine to launch Content Engine install wizard. ce_installer can be the same user as the ce_appserver_admin. Use Windows administrative tools to add ce_installer to the Local Administrators Group and to the ce_appserver_install_group.
Content Engine Setup (UNIX): ce_install_user
For upgrading from version 3.5, you can use the existing Content Engine install user, or designate a new user. An operating system account you will use to log on to a machine to launch Content Engine installer. Use your UNIX administrative tools to grant this account at least the following permissions: v Read, write, and execute permissions to the device or location where: Content Engine is to be installed. The application server instance/domain/profile has been installed. v Write permission to the directories where you will create file storage areas, index areas, and content caches. v Write permission on the /tmp directory. v Membership in the ce_appserver_install_group. ce_install_user can be the same user as the ce_appserver_admin.
185
User or group name GCD Administrator: gcd_admin
Description A directory service account that has Full Control access to the domain object forContent Engine. The initial gcd_admin is created by Configuration Manager using the account entered into its Create Bootstrap Properties panel for the Bootstrap user (ce_bootstrap_admin). Logon as gcd_admin in order to: v Create the GCD by launching the Configure New Domain Permissions wizard the first time you start Enterprise Manager to establish the IBM FileNet P8 domain. v Carry out administrative tasks for the IBM FileNet P8 domain. To perform upgrades, at least one IBM FileNet P8 4.5 GCD administrator must: v Also be an object store administrator (object_store_admin) for all object stores to be upgraded. Use IBM FileNet P8 3.5 IBM FileNet Enterprise Manager to ensure that the gcd_admin also has Full Control to each IBM FileNet P8 3.5.2 object store. v Have Full Control for the IBM FileNet P8 3.5 and IBM FileNet P8 4.5 domains. For more information, see the IBM FileNet P8 help topic FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Users and groups.
Object Store Administrator: object_store_admin, object_store_admin_group
It is not necessary to create new object store administrators for an upgrade. However, you can create new object store administrators as needed after completing the upgrade. The object_store_admin is a directory service account that can administer an object store by having Full Control access to it. You can also grant Full Control to an object store to group accounts, thereby making all members of the group object store administrators.
186
User or group name Directory service user: Active Directory (Referred to as Directory service bind user name in Configuration Manager.) ce_service_user
Description An Active Directory user account that Content Engine uses to connect to Active Directory. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific IBM FileNet P8 object after a user has been authenticated. Using Active Directory tools, grant ce_service_user at least the following permissions: v Member of the Pre-Windows 2000 Compatible Access Group in each desired domain in the Active Directory forest. Provide the fully qualified distinguished name of ce_service_user as the Directory service bind user name while running the Configuration Manager tool and also when you run Enterprise Managers Directory Configuration Wizard.
Directory service user: Windows Active Directory Application Mode (ADAM) (Referred to as Directory service bind user name in Configuration Manager.) ce_service_user
An ADAM user account that Content Engine uses to connect to a single Microsoft ADAM partition. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific IBM FileNet P8 object after a user has been authenticated. Using ADAM administrative tools, grant ce_service_user at least the following permissions: v Ability to see the other users in the partition. (For a procedure, see the entry for the ADAM directory service user in FileNet P8 Administration Enterprise-wide Administration FileNet P8 Security Users and groups.) Provide the fully qualified distinguished name of ce_service_user as the LDAPBindDN while running the Configuration Manager tool and also when you run Enterprise Managers Directory Configuration Wizard.
187
User or group name Directory service user: Sun Java System Directory Server (Referred to as Directory service bind user name in Configuration Manager.) ce_service_user
Description A Sun Java System Directory Server user account that Content Engine uses to connect to the Sun Java System Directory server. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific IBM FileNet P8 object after a user has been authenticated. Using Sun Java System Directory Server tools, grant ce_service_user at least the following permissions: v Read v Search v Compare Provide the fully qualified distinguished name of this account as the LDAPBindDN while running the Configuration Manager tool and also when you run Enterprise Managers Directory Configuration Wizard.
Directory service user: Novell eDirectory (Referred to as Directory service bind user name in Configuration Manager.) ce_service_user
A Novell eDirectory user account that Content Engine uses to connect to Novell eDirectory. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific IBM FileNet P8 object after a user has been authenticated. Using Novell eDirectory tools, grant ce_service_user at least the following permissions: v Read v Compare Provide the fully qualified distinguished name of this account as the LDAPBindDN while running the Configuration Manager tool and also when you run Enterprise Managers Directory Configuration Wizard.
188
User or group name Directory service user: IBM Tivoli Directory Server (Referred to as Directory service bind user name in Configuration Manager.) ce_service_user
Description An IBM Tivoli Directory Server user account that Content Engine uses to connect to Tivoli Directory Server. ce_service_user performs the following roles: v Acts as the bind user specified by the application server to search through realms to authenticate a user when the user logs in to a Content Engine client such as Workplace. v Acts as the user specified in the GCD that searches users and groups to authorize access to a specific IBM FileNet P8 object after a user has been authenticated. Using Tivoli Directory Server tools, grant ce_service_user at least the following permissions: v Read v Search v Compare Provide the fully qualified distinguished name of ce_service_user as the LDAPBindDN while running the Configuration Manager tool and also when you run Enterprise Managers Directory Configuration Wizard.
Database administrator upgrade tasks

The Database administrator must prepare the databases required for IBM FileNet P8 upgrade, including installing patches, creating databases and database accounts, and installing client software. v Review all rows assigned to the Database Server Administrator in the Installation and Upgrade Worksheet. While you complete the following preparation tasks, provide values for the rows that are appropriate to your installation. Tip: With the Data Filter AutoFilter command enabled, as it is by default in the shipping worksheet file (p8_worksheet.xls), perform the following actions to quickly see only the properties assigned to a particular role: Click the AutoFilter drop-down arrow in the Role column header and select DBA. Further filter the result set by clicking the AutoFilter drop-down arrow in any of the other columns and selecting a value or clear a filter by selecting All. v (Microsoft SQL Server). Upgrade SQL Server 2000 to SQL Server 2005 or 2008. Refer to your Microsoft documentation. v (Microsoft SQL Server). Update the Content Federation Services (CFS) database user (cfs_db_user) for CFS fixed content devices as follows. If your version 3.5 or 4.0 CFS fixed content devices use SQL Server databases, then perform the following steps for each database. 1. For each CFS database, add the following roles to the CFS user: System Administrators
189
Security Administrators Server Administrators Database Creators 2. For each CFS database, verify the following access permissions for the CFS database user: public db_owner Database administrator planning considerations You must review database patch requirements and carry out other planning tasks as part preparing for an upgrade. Creating Content Engine database accounts for upgrades from version 3.5 on page 191 Use your database tools to create new or designate existing database accounts for Content Engine, as shown in the following table. Creating the Content Engine database for the Global Configuration Data (upgrades from 3.5) on page 193 You must create a database for the Content Engine for the Global Configuration Data (GCD) when you upgrade from version 3.5. Configuring Process Engine Microsoft SQL Server databases on page 195 Prepare the Microsoft SQL Server database for the Process Engine upgrade.
Database administrator planning considerations

You must review database patch requirements and carry out other planning tasks as part preparing for an upgrade. General Update to the appropriate database patches before you upgrade IBM FileNet P8 components. Oracle on page 191 Ensure you have applied appropriate Oracle patches to Oracle clients as well as servers. Be sure that clients remote from Oracle database servers have patches that are comparable to the database server. General: Update to the appropriate database patches before you upgrade IBM FileNet P8 components. v For minimum patch requirements, see IBM FileNet P8 Hardware and Software Requirements. v (3.5 to 4.5 upgrades only): Plan for upgrade implications regarding Content Engine databases. If you are upgrading to version 4.5, you will continue to use existing object store databases. However, if you are upgrading from version 3.5, you must create a new database for the 4.5 global configuration data (GCD), which the Content Engine Upgrader Tool migrates from its 3.5 file-based format (sysinit.dat). v (3.5 to 4.5 upgrades only) Consider the following for Business Process Manager components (PE, PA, PS): The Process Engine database upgrade automatically renames the existing VWLog xxx_yyy tables to VWLog xxx_yyy. Archive and creates the new VWLog xxx_yyy table. The Process Engine Log SeqNumber starts from 21000. Process Analyzer gets its data from the Process Engine database. The 3.5 and 4.0 database schemas changed both on Process Engine and Process Analyzer.
190
The 3.5 data from Process Engine must be transmitted to Process Analyzer 3.5 before you upgrade either of these components to 4.5.0. For details, see the Process Engine pre-upgrade topic in the IBM FileNet P8 Platform Installation and Upgrade Guide Oracle: Ensure you have applied appropriate Oracle patches to Oracle clients as well as servers. Be sure that clients remote from Oracle database servers have patches that are comparable to the database server. v Oracle clients include any machines remote from the Oracle database server where Process Engine software is installed. You can download all the required Oracle database server patches from the Oracle Web site and install them. v Consider increasing the number of Oracle sessions and lowering the session timeout settings. Upgrading a Content Engine object store can use a large number of database sessions. The number of sessions required depends on the number of custom class definitions in the object store being upgraded. If the maximum number of sessions is exceeded during an object store upgrade, the upgrade will fail. To recover from such an upgrade failure, you will have to increase the number of sessions, decrease the session timeout settings, and then perform the following steps: In the Content Engine Upgrader Tool, note the steps that completed successfully during the object store upgrade, that is, those items that have green check marks next to them. Shut down the Content Engine Upgrader Tool. Shut down and then restart Oracle to release all database sessions and processes. Restart the Content Engine Upgrader Tool. Resume the object store upgrade and make sure to reset only the failed upgrade steps. To avoid a potential corruption of the object store, ensure that you have not chosen to rerun any upgrade steps that were already completed in the initial run of the Upgrader Tool. v Determine when to run SQL scripts. An upgrade SQL script must be run. This script can be run manually, before starting Process Engine Setup, or from Process Engine Setup.
Creating Content Engine database accounts for upgrades from version 3.5
Use your database tools to create new or designate existing database accounts for Content Engine, as shown in the following table.
191
User or Group Database user name: DB2 for Linux, UNIX and Windows ce_db_user
Description The database owner accounts that Content Engine uses to access DB2. Create a new account for the GCD tablespace. Your existing version 3.5 object store user accounts do not require changes for the upgrade. ce_db_user can be an operating system user on the database server. In the case of a remote database, no equivalent users are needed on the Content Engine server. Grant each ce_db_user at least the following DB2 database access permissions: v Connect to the database v Create tables in the tablespace (CREATETAB) v Use the tablespace (USE OF) for User and User Temp tablespaces
Database user name: Microsoft SQL Server ce_db_user
The database owner accounts that Content Engine uses to access SQL Server, depending on whether you use one account for all Content Engine databases, or use one (for example, ce_db_user) for the GCD database and different accounts for each object store (for example, ce_db_user1, ce_db_user2, and so on). ce_db_user can be a local account or a Windows domain account. It does not have to be an account in the configured directory service. For each object store you are going to upgrade, grant the associated 3.5 database user at least the following additional roles and access permissions: SQL Server roles: v System Administrators v Security Administrators v Database Creators Grant each ce_db_user at least the following database access permissions: v public v db_owner Add these accounts to SQL Servers master database and grant the public role to each. When you perform the procedure Configuring the JDBC distributed transaction components on page 194, these accounts will also be granted the SqlJDBCXAUser role.
192
User or Group Database user name: Oracle ce_db_user
Description The tablespace owner accounts that Content Engine uses to access Oracle. Create a new account for the GCD tablespace. Your existing object store user accounts do not require changes for the upgrade. Grant each ce_db_user at least the following permissions: v CREATE SESSION v CREATE TABLE v CREATE SEQUENCE (object store tablespaces only)
Creating the Content Engine database for the Global Configuration Data (upgrades from 3.5)
You must create a database for the Content Engine for the Global Configuration Data (GCD) when you upgrade from version 3.5. Preparing DB2 for Linux, UNIX and Windows You must create a DB2 for Linux, UNIX and Windows table space for the Content Engine Global Configuration Data (GCD). Preparing Oracle server on page 194 You must create an Oracle tablespace for theContent Engine Global Configuration Data (GCD). Preparing Microsoft SQL Server on page 194 You must create a Microsoft SQL Server database for the Content Engine Global Configuration Data (GCD). Preparing DB2 for Linux, UNIX and Windows: You must create a DB2 for Linux, UNIX and Windows table space for the Content Engine Global Configuration Data (GCD). To create the GCD table space: 1. Create a table space for the GCD with the following attributes. Use the same type and storage management method used for your existing object store table spaces. Do not use the requirements documented for new installations as some requirements have changed since version 3.5. For example, if your existing database was created using DMS, you cannot create a table space in that database that uses automatic storage.
IBM FileNet Tablespaces GCD_ts (for the GCD database) user temporary ts (for CE) system temporary ts (for CE) Actual Assigned Minimum Size Name (MB) 256 40 40 Actual Created Size Minimum Page Size (KB) 32 (required) 32 (required) 32 (required)
2. Record the database name where the GCD table space was created in the Installation and upgrade worksheet.
193
Preparing Oracle server: You must create an Oracle tablespace for theContent Engine Global Configuration Data (GCD). When you create the GCD table space, keep the following restrictions and recommendations in mind: v Tablespace names must contain only alphanumeric and underscore characters. Names must start with an alphabetic character and must be at most 18 characters long. v For performance reasons, IBM recommends that you specify locally managed, instead of dictionary managed, table spaces. The table spaces that you create via Oracle Enterprise Manager are locally managed by default. v The following table shows the recommended minimum sizes of the permanent and temporary table spaces for each object store that Content Engine will access. (The tablespace names shown in the table are arbitrary.)
Tablespace Name gcd tempgcd Tablespace Type Permanent Temporary Minimum Size 100 MB 2 GB Description Permanent tablespace for the GCD Temporary tablespace for the GCD
Preparing Microsoft SQL Server: You must create a Microsoft SQL Server database for the Content Engine Global Configuration Data (GCD). To create the GCD database: 1. Create the database with an initial size of 100 MB minimum. 2. Record the database name in the Installation and upgrade worksheet. Configuring the JDBC distributed transaction components You must configure Microsoft SQL Server to process JDBC distributed transactions for the Content Engine database. Configuring the JDBC distributed transaction components: You must configure Microsoft SQL Server to process JDBC distributed transactions for the Content Engine database. To configure the JDBC distributed transaction components: 1. Download the SQL Server 2005 JDBC Driver that is referenced in the IBM FileNet P8 Hardware and Software Requirements guide. 2. Copy the sqljdbc_xa.dll file from the JDBC installation directory to one of the following locations:
Option Using the default instance Using a named instance Description Program Files\Microsoft SQL Server\80\Tools\Binn Program Files\Microsoft SQL Server\MSSQL$instance name\Binn
194
3. 4.
5.
6.
If you are on a 32-bit processor, use the sqljdbc_xa.dll file in the x86 folder. If you are on a 64-bit processor, use the sqljdbc_xa.dll file in the x64 folder. Log on to the database server as the SA administrator, or equivalent permissions, by using SQL Server authentication. Run the database script xa_install.sql against the master database on every SQL Server instance that will participate in distributed transactions. This script installs the sqljdbc_xa.dll file as an extended stored procedure and creates the SqlJDBCXAUser role in the Master database. Add each ce_db_user database account that Content Engine uses to access SQL Server to the SqlJDBCXAUser role. This action grants permissions to those accounts to participate in distributed transactions with the JDBC driver. Navigate to Component Services My Computer Properties MSDTC Security Configuration, and make sure that XA transactions are enabled.
Configuring Process Engine Microsoft SQL Server databases

Prepare the Microsoft SQL Server database for the Process Engine upgrade. Creating an ODBC data source Create an ODBC data source on the Process Engine server. This procedure is necessary only if you are not already running a Microsoft SQL Server 2005 or 2008 database. Preparing SQL Client on page 196 Process Engine configurations with remote Microsoft SQL Server databases must have SQL Server client software installed on the Process Engine server before upgrading. Installing SQL Server patches and service packs on page 196 Verify that any required service pack for Microsoft SQL Server has been installed before proceeding. Creating an ODBC data source: Create an ODBC data source on the Process Engine server. This procedure is necessary only if you are not already running a Microsoft SQL Server 2005 or 2008 database. If SQL scripts are run from the Process Engine installation program on a 64-bit Windows 2008 server, a 64-bit ODBC data source must be created, in addition to the 32-bit ODBC data source required for Process Engine run time software. The 32-bit ODBC data source is required for both local and remote databases and must be created on the Process Engine server. The following steps apply on a 32-bit version of the operating system. On a 64-bit operating system locate and manually run the 32-bit version, typically located in: C:\WINDOWS\SysWOW64\odbcad32.exe. To create the Process Engine ODBC data source and test the connection: 1. Start Program Administrator Tools DataSource (ODBC). 2. Click Add on the System DSN tab. 3. Select SQL Server as the driver to use for the new data source and click Finish. 4. Enter a name and description for the data source. The name will be required input for the Process Engine installation program when configuring for a SQL Server database.
195
5. Choose the SQL Server to connect to from the dropdown list of servers and click Next. If only a server name appears in the list, the connection will be with the default instance. If there are named instances in the database, the name will appear as server / instance name 6. Do the following configuration: a. Choose SQL Server authentication. b. Select the option to get default settings for additional configuration options by connecting to the SQL Server. c. Indicate the Login ID and Password to connect to the database. This database login ID information need not be for an administrator and it is only used to connect to the database to get the default values for the remaining settings required to configure the data source. d. Click Next 7. Change the default database to be the Process Engine database. 8. Enable Use ANSI null, paddings, and warning and enable Use ANSI quoted identifiers. 9. Enable Perform translation for character data and click Finish. 10. Verify the settings for the data source configuration and click Test Data Source. If the test is successful click OK. Otherwise resolve the problem before continuing. 11. Double-click SQL Server on the Connection Pooling tab. 12. Select Dont pool connection to this driver and click OK. 13. Click OK on the ODBC Data Source Administrator window to finish configuration of the data source. 14. On the summary screen click Test Data Source. If error messages display, resolve them before proceeding. 15. Record the name of the ODBC datasource in the Installation and Upgrade Worksheet. Preparing SQL Client: Process Engine configurations with remote Microsoft SQL Server databases must have SQL Server client software installed on the Process Engine server before upgrading. Some 3.5 and 4.0 Process Engine servers may not have this software installed because of requirements for those releases, but the Process Engine upgrade will fail without the client software. To install SQL Server client software: 1. Log on with an account that has local administrator privileges on the computer where the SQL Server client software will be installed. 2. Install Workstation components, Books Online and development tools and from the Advanced options, select Client Components. 3. When the installation is complete, start the Client Network Utility and clear the Automatic ANSI to OEM conversion checkbox on the DB-Library Options tab. 4. Test the database connection. After a successful upgrade, the SQL Server client software can be removed. Installing SQL Server patches and service packs:
196
Verify that any required service pack for Microsoft SQL Server has been installed before proceeding. Refer to IBM FileNet P8 Hardware and Software Requirements for required operating-system and database patch sets, and service packs.
Application Server administrator upgrade tasks

The Application Server Administrator must prepare the application servers for IBM FileNet P8 Platform upgrade, including planning deployment, creating administrative accounts, and configuring JDBC drivers for both Content Engine and Application Engine. v Review all rows assigned to the Application Server Administrator (ASA) in the Installation and Upgrade Worksheet. While you complete the following preparation tasks, provide values for the rows that are appropriate to your installation. Tip: With the Data Filter AutoFilter command enabled, as it is by default in the shipping worksheet file (p8_worksheet.xls), perform the following actions to quickly see only the properties assigned to a particular role: Click the AutoFilter drop-down arrow in the Role column header and select ASA. Further filter the result set by clicking the AutoFilter drop-down arrow in any of the other columns and selecting a value or clear a filter by selecting All.
Upgrades from 3.5

v Review the following planning considerations: Application server planning considerations (upgrades from 3.5) on page 198 v Configure your application server for Content Engine according to your application server type. See the following task: Configuring the application server for Content Engine (upgrades from 3.5) on page 203
Upgrades from 4.0

If you configured Microsoft SQL Server data sources in version 4.0 of Content Engine, the FNDSHelper.jar file will continue to be used in version 4.5, and no further action is necessary. SQL Server data sources you configure in version 4.5 do not require the FNDSHelper.jar file. Application server planning considerations (upgrades from 3.5) on page 198 Determine the type of application server environment that will be needed for Content Engine. Creating Content Engine application server accounts for upgrade on page 199 Create new or designate existing application server accounts for Content Engine, as shown in the following table. Configuring the application server for Content Engine (upgrades from 3.5) on page 203 Set up the application server for Content Engine. Configuring the application server for Content Engine (upgrades from 4.0) on page 212 You can deploy Content Engine only on certain versions of application servers.
197
Therefore, you must determine if and when to upgrade the application server where version 4.0.1 of Content Engine is deployed before upgrading to version 4.5.1.
Application server planning considerations (upgrades from 3.5)

Determine the type of application server environment that will be needed for Content Engine. All platforms Content Engine and Application Engine are J2EE application server-based applications. (Process Engine is not.) WebSphere and WebLogic - Content Engine multi-server deployment on page 199 In an environment of load-balanced or highly-available farmed (or clustered) application servers, you will initially install Content Engine on the Deployment Manager node (IBM WebSphere Application Server) or the Administrator node (Oracle WebLogic Server). JBoss Content Engine multi-server deployment on page 199 JBoss Application Server does not have a central management server. In an environment of multiple physical servers that are farmed or clustered, you will install Content Engine initially on one physical server (using the all instance), and then copy pertinent files and directories to the other servers. Application server considerations on page 199 The choice of JVM (32-bit or 64-bit) depends on the number of object stores are to be upgraded. All platforms: Content Engine and Application Engine are J2EE application server-based applications. (Process Engine is not.) You must install Content Engine and Application Engine in a homogeneous J2EE environment in which all of your application servers (IBM WebSphere Application Server, Oracle WebLogic Server, or JBoss Application Server) and their version numbers are identical for both components. Also, the applications must use Enterprise Java Bean (EJB) transport. The Java Virtual Machine determines the maximum number of object stores. If the application server where Content Engine will be deployed is running on a 32-bit JVM, it is a best practice to create no more than 75 Content Engine object stores. On a 64-bit JVM, it is a best practice to create no more than 150 Content Engine object stores. Content Engine is a resource-intensive enterprise application. Running Content Engine and other J2EE applications on the same machine is possible but not a best practice. Other J2EE applications will compete with Content Engine for the same CPU, memory, and disk I/O resources, and increase the complexity of the installation and the risk of the deployment, because configurations will not match what has been qualified by IBM FileNet Engineering. Although you can host Content Engine and other applications on the same machine, it is preferable to host Content Engine on its own machine or logical partition. If an architecture requires Content Engine and a non-P8 J2EE application to be on the same machine, be sure to thoroughly test the configuration in your integration environment before deployment into production.
198
If you intend to deploy Content Engine to multiple server nodes in your production environment, the type of environment will determine how you install Content Engine. WebSphere and WebLogic - Content Engine multi-server deployment: In an environment of load-balanced or highly-available farmed (or clustered) application servers, you will initially install Content Engine on the Deployment Manager node (IBM WebSphere Application Server) or the Administrator node (Oracle WebLogic Server). To install Content Engine in such an environment, see the IBM FileNet P8 Platform High Availability Technical Notice. In an environment in which multiple Content Engine instances may be geographically dispersed, and where each instance may have its own local Application Engine or Workplace XT server, you will initially install Content Engine on the Deployment Manager node (WebSphere Application Server) or the Administrator node (WebLogic Server). You will then perform post-deployment steps using Configuration Manager to deploy it to other servers. JBoss Content Engine multi-server deployment: JBoss Application Server does not have a central management server. In an environment of multiple physical servers that are farmed or clustered, you will install Content Engine initially on one physical server (using the all instance), and then copy pertinent files and directories to the other servers. To install Content Engine in such an environment, see the IBM FileNet P8 High Availability Technical Notice. In an environment in which standalone application servers are individually managed and not farmed or clustered, and where the servers may be geographically dispersed, you will install Content Engine on each server. Each Content Engine instance will point to the same directory service and GCD database. The data sources you create for each instance will also point to the same object store databases. Application server considerations: The choice of JVM (32-bit or 64-bit) depends on the number of object stores are to be upgraded. (3.5 to 4.5 upgrades only): Determine whether the number of object stores to be upgraded will require you to run a 64-bit Java Virtual Machine (JVM) on your Content Engine application servers. If the 3.5 FileNet P8 domain you are upgrading contains more than 50 object stores, it is a best practice to install Content Engine on application servers running a 64-bit, rather than 32-bit, JVM. Otherwise, you might experience significant Content Engine performance issues.
Creating Content Engine application server accounts for upgrade

Create new or designate existing application server accounts for Content Engine, as shown in the following table.
199
User or Group Application server administrator user name: ce_appserver_admin Administrative Console User: ce_appserver_console_admin
Description An application server administrative account or accounts that can log on to the application server administration console. IBM WebSphere Application Server ce_appserver_admin must have Administrator permissions throughout the upgrade process. After the upgrade is complete, you can reduce the account permissions to a lesser role, such as Configurator. If your site uses a FederatedLDAP registry, ce_appserver_console_admin must be a unique user across all federated realms. Otherwise, ce_appserver_admin and ce_appserver_console_admin can be the same account. Oracle WebLogic Server ce_appserver_admin and ce_appserver_console_admin must be different accounts. JBoss Application Server does not require an administrative account. Log in to the application server as ce_appserver_admin to perform application configuration such as the following tasks: v Create directory service providers within the application server. v Create JDBC providers and/or data sources for db connectivity. v Deploy the Content Engine application. v Stop and restart servers and cluster members (WebSphere Application Server). v Stop and restart managed servers (WebLogic Server).
200
User or Group
Description
Application Server Installation Administrator: An operating system user account you used (WebSphere Application Server, WebLogic to install your application server. Server, JBoss Application Server): Use your local machines administrative tools ce_appserver_installer to grant ce_appserver_installer at least the following permissions: v For Windows, ce_appserver_installer must be a member of the Local Administrators Group. v For UNIX, ce_appserver_installer must have read, write, and execute permissions to the Content Engine installation directory. During the installation process, the ce_appserver_installer performs the following tasks: v Create and configure the application server/domain/profile for Content Engine. v Start or stop the application server when needed. v Modify the application server files or directories as needed for deploying the Content Engine application using the Configuration Manager tool. v Provide create, read and write permissions for directories on devices or drives that are used for external Content Engine file storage. This includes creating UNIX mounts to external NFS devices such as SnapLock shares, Autonomy K2 Content Search Engine collection shares, and NFS->NTFS mounts to access NTFS shares for Content Engine 3.5.2 upgrades when migrating to Content Engine 4.5 on UNIX. ce_appserver_installer must be a member of the ce_appserver_install_group.
201
User or Group Application Server Installation Group: ce_appserver_install_group
Description Create an operating system group account and add to it the following accounts: ce_appserver_admin An application server administrative account or accounts that can log on to the application server administration console. WebSphere Application Server: ce_appserver_admin must have Administrator permissions throughout the installation process. After installation is complete, you can reduce the accounts permissions to a lesser role, such as Configurator. ce_install_user (Windows) An operating system account you will use to log on to a machine to launch Content Engine install wizard. ce_install_user can be the same user as the ce_appserver_admin. Use Windows administrative tools to add ce_install_user to the Local Administrators group and to the ce_appserver_install_group. ce_install_user (UNIX) An operating system account you will use to log on to a machine to launch Content Engine installer. Use your UNIX administrative tools to grant this account at least the following permissions: v Read, write, and execute permissions to the device or location where: Content Engine is to be installed. The application server instance/domain/profile has been installed. v Write permission to the directories where you will create file storage areas, index areas, and content caches. v Write permission on the /tmp directory. v Membership in the ce_appserver_install_group. Use the user accounts in ce_appserver_install_group to do the following tasks:
202
v Give operating system privileges to the directories used for the Content Engine Installation and for the application servers instance/domain/profile.
Configuring the application server for Content Engine (upgrades from 3.5)
Set up the application server for Content Engine. Configuring WebSphere for Content Engine You must prepareIBM WebSphere Application Server before you install Content Engine. You must create a WebSphere profile for the Content Engine application and set the environment variables for the database connection. Configuring WebLogic Server for Content Engine on page 206 This task assumes you have already installed Oracle WebLogic Server on the machine where you are going to install and deploy Content Engine. Configuring JBoss Application Server for Content Engine on page 209 This task assumes you have already installed JBoss Application Server on the machine where you are going to deploy Content Engine. Configuring WebSphere for Content Engine: You must prepareIBM WebSphere Application Server before you install Content Engine. You must create a WebSphere profile for the Content Engine application and set the environment variables for the database connection. Creating the WebSphere profile for Content Engine You must create an IBM WebSphere Application Server profile for Content Engine if you do not already have a profile. Specifying the WebSphere environment variables on page 204 You must specify the IBM WebSphere Application Server environment variables so that Content Engine can access its databases. Setting the primary administrative user name on page 206 If you are using IBM WebSphere Application Server federated repositories for LDAP authentication, you must ensure that the name you entered for the WebSphere Application Server primary administrative user name is unique across all realms. Setting host aliases for deployment on multiple servers on page 206 If you are deploying Content Engine to multipleIBM WebSphere Application Server servers on the same WebSphere node, you must define the host alias and port numbers. Setting permissions for the Configuration Manager user on page 206 You must create an application server account with certain directory permissions that you will use later on to start the Configuration Manager tool. Creating the WebSphere profile for Content Engine: You must create an IBM WebSphere Application Server profile for Content Engine if you do not already have a profile. To create the WebSphere profile for Content Engine: 1. Run the command script at one of the following (default) locations to create a new profile.
Option AIX Description /usr/IBM/WebSphere/AppServer/ manageprofiles.sh
203
Option Other UNIX Windows
Description /opt/IBM/WebSphere/AppServer/ manageprofiles.sh C:\Program Files\IBM\WebSphere\AppServer\ bin\manageprofiles.bat
2. Record the path to your new profile in the Application server installation directory property in your installation worksheet, as you must specify the path later when you configure Content Engine. Specifying the WebSphere environment variables: You must specify the IBM WebSphere Application Server environment variables so that Content Engine can access its databases. Refer to the IBM FileNet P8 Hardware and Software Requirements for information on the JDBC driver file for the database type that you need for the Global Configuration Data (GCD) or for an object store you will be creating later. To specify the WebSphere environment variables: 1. Install JDBC drivers on the server where WebSphere Application Server is installed. a. Obtain the JDBC drivers for your database type. DB2 Find the latest version of the Redistributable DB2 JDBC Driver Type 4 driver from the IBM Web site by searching for JDBC Type 4.
Microsoft SQL Server Find theSQL Server JDBC Driver 2.0 at Microsoft Support. Oracle Access the http://www.oracle.com/technology/software/tech/ java/sqlj_jdbc/index.html Web site and find the JDBC driver file that matches the version of the JDK that is installed on the on the server where WebSphere Application Server is installed. b. Copy the JDBC driver file to the following suggested location: UNIX /opt/jars Do not copy the file to ...WebSphere/AppServer/lib/ext. Windows C:\jars Do not copy the file to ...WebSphere\AppServer\lib\ext. 2. Start the WebSphere Application Server administrative console and log on to your Content Engine profile as ce_appserver_console_admin, the Administrator Console User. 3. Navigate to Environment WebSphere Variables and specify the JDBC driver path: a. Select Cell scope from the All scopes list. b. Click New to create a WebSphere Application Server variable whose name is one of the JDBC environment variables shown in the Database environment variables table below. c. Set the value of the variable to the JDBC driver path that you specified when you installed the JDBC drivers on the IBM WebSphere Application Server machine.
204
d. Save your change to the master configuration. e. Select Node scope from the All scopes list. f. In the table of substitution variables, click the item name in the Name column that corresponds to the JDBC environment variable for your database type in the Database environment variables table below.
Table 17. Database environment variables Database SQL Server JDBC Environment Variable WebSphere Application Server 6.1 MSSQLSERVER_JDBC _DRIVER_PATH WebSphere Application Server 7 MICROSOFT_JDBC _DRIVER_PATH
Oracle DB2
ORACLE_JDBC _DRIVER_PATH DB2UNIVERSAL_JDBC _DRIVER_PATH
g. Set the value of the name_JDBC_DRIVER_PATH item to the JDBC driver path you specified (/opt/jars or C:\jars). h. Save your changes to the master configuration. 4. Navigate to Servers Application servers server1 Java and Process Management Process Definition Java Virtual Machine, and set the initial and maximum heap sizes, where server1 is the name of the server where you will deploy Content Engine. a. Set the values for the initial and maximum heap sizes:
Parameter Initial Heap Size Maximum Heap Size Value (in MB) At least 512 1024 or a size consistent with available RAM on the machine where WebSphere Application Server is installed
b. Save your changes to the master configuration. 5. Optional: Navigate to Servers Application Servers server1 and set the transaction timeout value: a. Click the Runtime tab, and then click Transaction Service. b. Change the Total transaction lifetime timeout parameter value to at least 600 (seconds), and click Apply. Important: If the timeout value is not large enough, some administrative processes (such adding an expansion product) might fail. Changing the transaction lifetime timeout in the Runtime tab is not permanent. The setting reverts to the default when the application server is restarted, and subsequent administrative processes might fail. To make the change permanent, continue at the next step. c. Click the Configuration tab. In the Container Settings section, expand Container Services.
205
d. Change the Total transaction lifetime timeout parameter value to at least 600 (seconds), and click Apply. 6. Repeat this procedure as needed for any object store that uses a different database type. Setting the primary administrative user name: If you are using IBM WebSphere Application Server federated repositories for LDAP authentication, you must ensure that the name you entered for the WebSphere Application Server primary administrative user name is unique across all realms. Setting host aliases for deployment on multiple servers: If you are deploying Content Engine to multipleIBM WebSphere Application Server servers on the same WebSphere node, you must define the host alias and port numbers. To set the host alias: 1. Log in to the WebSphere administrative console. 2. Navigate to Environment Virtual Hosts default host Host Aliases. 3. If you are using SSL, add an alias for the SSL port number, such as port 9081. 4. Add an alias for the non-SSL port number, such as port 9444. 5. Click Apply. Setting permissions for the Configuration Manager user: You must create an application server account with certain directory permissions that you will use later on to start the Configuration Manager tool. To set permissions for the Configuration Manager user: Set permissions for the Configuration Manager user (config_mgr_user) on the WebSphere Application Server profile directory and all its subdirectories where Content Engine will be deployed:
Option UNIX Windows Description Read, write, and execute permissions Read & Execute, and Write permission
Configuring WebLogic Server for Content Engine: This task assumes you have already installed Oracle WebLogic Server on the machine where you are going to install and deploy Content Engine. Before installing and deploying Content Engine on a WebLogic Server machine, you must create a WebLogic Server domain and install JDBC drivers. (The drivers must be installed on the WebLogic Server machine whether your database is collocated or not.) To configure WebLogic Server for Content Engine:
206
1. Use the WebLogic Server Configuration Wizard to create a WebLogic domain for Content Engine. In the examples below, use the domain name FNCEDomain. Keep the following in mind as you configure the domain: a. Set the server start mode to Production mode. b. Select the appropriate Java Development Kit (JDK) for your environment, as specified in the IBM FileNet P8 Hardware and Software Requirements. 2. Use the WebLogic Server Administration Console to configure the following settings: a. Optional: Create a WebLogic Server authentication provider. You can use the Content Engine Configuration Manager tool to create a WebLogic Server authentication provider later on, or you can create the provider now using the WebLogic Server Console. If you want to configure the LDAP later with See Configure Content Engine instances in the IBM FileNet P8 Platform Installation and Upgrade Guide for information on using the Configuration Manager tool to create the LDAP provider. In some situations (for example, if you have a single-sign-on provider, such as Netegrity SiteMinder), Configuration Manager cannot configure a WebLogic Server authentication provider. For performance reasons set the parameters that control searches within the authentication provider, as shown in the following table:
Parameter Value Description Group searches are unlimited in depth Only direct group members are found
Group Membership Searching unlimited Max Group Membership Search Level 0
If performance problems are encountered, change the Group Membership Searching parameter value to limited. b. If you do not use Configuration Manager to configure your LDAP settings, set the Control Flag value. Set the Control Flag to REQUIRED to allow logons to FNCEDomain by LDAP-authenticated users in the Default Authenticator who are not in the FNCEDomain active security realm. The Configuration Manager tool will set this flag when you run the Configure LDAP task. c. If you are using multiple authentication providers in an Active Directory environment of multi-forest domains, reorder (as needed) the list of providers so that the most-frequently-used provider is first in the list, and the least-frequently-used is last. Reordering is necessary to prevent logon failures when IBM FileNet Workplace is being accessed by many users simultaneously. d. Specify the following heap sizes for the JVM: v Initial Java heap size (-Xms): 512 MB v Maximum Java heap size (-Xmx): 1024 MB e. Optional: Adjust transaction-timeout value. Content Engine relies on the transaction-timeout value, whose default may be too short for some standard or administrative processes (such as adding an expansion product or upgrading to the latest version of Content Engine). Set the JTA node timeout in seconds to at least 600 seconds. 3. Refer to the IBM FileNet P8 Hardware and Software Requirements for information on the JDBC driver file for the database type that you need for the GCD or for an object store you will be creating later.
207
4. Depending on your database, use one of the following procedures to install the JDBC drivers. DB2 a. Obtain the latest version of the Redistributable DB2 JDBC Driver Type 4 driver from the http://www.ibm.com by searching for JDBC Type 4. b. Add the db2jcc.jar and db2jcc_license_cu.jar files to the WebLogic Server classpath. Edit the file startWebLogic.cmd or startWebLogic.sh for the WebLogic Server domain you created. For example:
set CLASSPATH=%CLASSPATH%;c:\db2\jdbc\db2jcc.jar; c:\db2\jdbc\ db2jcc_license_cu.jar
Microsoft SQL Server a. Download and unzip Microsoft SQL Server Driver 2005 JDBC Driver, sqljdbc.jar, from Microsoft Support to a directory jdbc_path on your application server machine, such as: UNIX /opt/jars Windows C:\jars b. Perform the following step, depending on your operating system type. Windows Edit the file startWebLogic.cmd (by default, in the directory C:\bea\user_projects\domains\bin\FNCEDomain) for the WebLogic Server domain you created. Insert the following two lines immediately after the first occurrence of the line CLASSPATH=...
AIX
Add the following line to the file setDomainEnv.sh file:

JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.xml .namespace.QName.useCompatibleSerialVersionUID=1.0"
UNIX Edit the file startWebLogic.sh by inserting the following two lines immediately after the first occurrence of the line CLASSPATH=...
JDBC_PATH=jdbc_path/sqljdbc_1.0/enu/sqljdbc.jar CLASSPATH=$JDBC_PATH:$CLASSPATH
Oracle a. Check to see if the Oracle JDBC Driver file is already on your WebLogic machine by searching for ojdbc##.jar in the wls_install_path/server/lib directory, where wls_install_path is the WebLogic Server installation path, such as C:\bea\weblogic92. b. If no Oracle JDBC Driver file is present, download the file (the one that matches the version of the JDK on your WebLogic Server machine) from the http://www.oracle.com/technology/software/ tech/java/sqlj_jdbc/index.html Web site to a directory on the WebLogic machine.
208
If you intend to install Add Ons (extensions toIBM FileNet P8 core components), and your Content Engine database will be Oracle, your Oracle JDBC Driver file requirements may be more restrictive. For the required version and patch number, see the IBM FileNet P8 Hardware and Software Requirements. c. From the Oracle web site, apply the patch Oracle Patch Ojdbc##.jar. d. Edit the file startWebLogic.cmd or startWebLogic.sh for the WebLogic Server domain you created. Add the following line immediately after the first line that starts with set CLASSPATH: Windows
set JDBC_PATH=<jdbc_path>\ojdbc##.jar set CLASSPATH=%JDBC_PATH%;%CLASSPATH%;
UNIX
JDBC_PATH=<jdbc_path>/ojdbc##.jar CLASSPATH=$JDBC_PATH:$CLASSPATH;
5. If your application server uses the IBM JVM, edit the JAVA_OPTIONS variable (to improve performance). UNIX Immediately before the following line in startWebLogic.sh:
SAVE_JAVA_OPTIONS=$JAVA_OPTIONS
insert this line (without a carriage return):

JAVA_OPTIONS="$JAVA_OPTIONS -Dprogram.name=$PROGNAME -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5"
Windows Immediately before the following line in startWebLogic.cmd:

set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
insert this line (without a carriage return):

set JAVA_OPTIONS=%JAVA_OPTIONS% -Dprogram.name=%PROGNAME% -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5
6. Stop and then start WebLogic Server. 7. Give the Configuration Manager user the following permissions: a. Read, write, and execute permission on the domain directory ../users_projects/domains/your_domain. b. Read and execute permission on the ../common/bin directory. Configuring JBoss Application Server for Content Engine: This task assumes you have already installed JBoss Application Server on the machine where you are going to deploy Content Engine. To configure a JBoss Application Server for Content Engine: 1. Navigate to the JBoss Application Server JBOSS_DIST/server directory, which contains configuration file sets. If you are installing into a JBoss Application Server cluster, use the JBoss Application Server JBOSS_DIST/all directory. 2. Create a new configuration file set by copying the default configuration file set to a new directory (called server1 in this procedure) within the server or all directory. 3. Edit the run.conf configuration file, located at JBOSS_DIST/bin, as follows:
209
a. Add a line to specify the path to the JDK on the machine where JBoss Application Server is installed, as shown in the following example:
JAVA_HOME="<path_to_Java_JDK>"
b. In the JAVA_OPTS line, change the -Xms and -Xmx values from:
-Xms128m -Xmx512m
to:
-Xms512m -Xmx1024m
c. Save your edits. 4. Open the file login-config.xml for editing. This file is typically located at .../server/myserver/conf, where myserver is the name of the JBoss Application Server server instance. a. In the <!DOCTYPE declaration, change:
"http://www.jboss.org/j2ee/dtd/security_config.dtd"
to:
"jboss_install_dir/docs/dtd/security_config.dtd"
where jboss_install_dir is the directory where JBoss Application Server is installed. b. Save your edit. 5. If your application server uses the IBM JVM, open the startup script file run.sh (UNIX) or run.bat (Windows) to edit the JAVA_OPTS variable (to improve performance). This file is typically located at JBOSS_HOME/bin. a. Edit the file as follows: UNIX Find the following line in run.sh:
JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME"
and change it to this (without a carriage return):

JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5"
Windows Find the following line in run.bat:

set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME%
and change it to this (without a carriage return):

set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME% -Dfilenet.pe.peorb.pool.min=2 -Dfilenet.pe.peorb.pool.max=5
b. Save your edit. 6. Refer to the IBM FileNet P8 Hardware and Software Requirements for information on the JDBC driver file for the database type that you need for the GCD or for an object store you will be creating later. 7. Install JDBC drivers on the JBoss Application Server machine, as follows: a. Obtain the JDBC drivers, depending on your database type. DB2 Find the latest version of the Redistributable DB2 JDBC Driver Type 4 driver from http://www.ibm.com by searching for JDBC Type 4.
Microsoft SQL Server Find the Microsoft SQL Server Driver 2005 JDBC Driver, sqljdbc.jar, at Microsoft Support.
210
Oracle Access the http://www.oracle.com/technology/software/tech/ java/sqlj_jdbc/index.html web site and find the JDBC driver file that matches the version of the JDK on the JBoss machine. b. Place the file JDBC driver file in CLASSPATH by copying it to the JBOSS_DIST/server/server_name/lib directory. If you are installing into a JBoss Application Server cluster, use the JBoss Application Server JBOSS_DIST/all/ server_name /lib directory. 8. Increase the database transaction timeout. Edit the jboss-service.xml file, and set TransactionTimeout to at least 600, as in this example:
<mbean code="org.jboss.tm.TransactionManagerService" name="jboss:service =TransactionManager" xmbean -dd="resource:xmdesc/TransactionManagerService-xmbean.xml"> <attributename="TransactionTimeout">600</attribute>
9. If you are deploying multiple instances of Content Engine of the same server, do the following for each additional instance: a. Copy the configuration file set that you just created and modified from the /server/server1 directory to a new directory. Use a separate directory for each instance. b. Assign unique port numbers to each instance. Refer to your JBoss Application Server documentation for details. 10. If it isnt already running, start JBoss Application Server as follows, and leave the command window open: UNIX
./run.sh -c server1
Windows
run.bat -c server1
Assigning directory permissions Give the Configuration Manager user read and write permission on the server directory where the Content Engine instance will be installed. Configuring JBoss Application Server clusters JBoss Application Server instances can be grouped together into a cluster for performance or to provide high availability. This guide provides on minimal instructions for setting up a JBoss Application Server cluster. Strengthening Content Engine server security under JBoss Application Server on page 212 In IBM FileNet P8 4.x environments the Content Engine server assumes that a users short name passed to it by means of an IIOP request from Application Engine, Workplace XT, or an associated custom application has been properly authenticated and can be trusted. Assigning directory permissions: Give the Configuration Manager user read and write permission on the server directory where the Content Engine instance will be installed. Configuring JBoss Application Server clusters: JBoss Application Server instances can be grouped together into a cluster for performance or to provide high availability. This guide provides on minimal instructions for setting up a JBoss Application Server cluster.
211
Refer to the IBM FileNet P8 Platform High Availability Technical Notice for details on how to set up your IBM FileNet P8 system using clusters, farms, and other high availability software and hardware. Because JBoss Application Server clusters do not have an administrative server, you will choose a single JBoss Application Server on which to install and configure the first instance of Content Engine, then copy the necessary files to the rest of the nodes in the cluster. Strengthening Content Engine server security under JBoss Application Server: In IBM FileNet P8 4.x environments the Content Engine server assumes that a users short name passed to it by means of an IIOP request from Application Engine, Workplace XT, or an associated custom application has been properly authenticated and can be trusted. WebSphere Application Server and Oracle WebLogic Suite have mechanisms such as Lightweight Third-Party Authentication (LTPA) keys to secure IIOP communications, which establishes this sort of trust relationship between Java Virtual Machines (JVMs). However, because JBoss Application Server has no such feature to prevent unauthenticated access, a security risk is exposed between the Content Engine JVM and the calling applications JVM. To mitigate the risk of passing unauthenticated user short names to Content Engine server under JBoss Application Server, place a firewall on the Content Engine server to allow only trusted JVMs associated with Application Engine, Workplace XT, or custom applications to connect to the Content Engine JVM IIOP port.
Configuring the application server for Content Engine (upgrades from 4.0)
You can deploy Content Engine only on certain versions of application servers. Therefore, you must determine if and when to upgrade the application server where version 4.0.1 of Content Engine is deployed before upgrading to version 4.5.1. To determine the order of upgrading Content Engine and the application server on which it is deployed: 1. 1. Consult the Hardware and Software Requirements documentation and determine what versions of your application server support both Content Engine 4.0.1 and Content Engine 4.5.1. 2. You will upgrade your application server and Content Engine according to the criteria in the following table:
Option Description
If you deployed Content Engine 4.0.1 on an 1. Upgrade to version 4.5.1 of Content application server version that supports Engine. It is not necessary to upgrade Content Engine 4.5.1 (for example, your application server. WebSphere 6.1, WebLogic 9.2, or JBoss 4.0.5) 2. (optional) Upgrade the application server to a newer version that supports version 4.5.1 of Content Engine
212
Option If you deployed Content Engine 4.0.1 on an application server version that does not support Content Engine 4.5.1 (for example, WebSphere 5.1 or WebLogic Server 8.1)
Description 1. Upgrade to an application server version that Content Engine 4.0.1 and 4.5.1 both support. 2. Upgrade Content Engine from version 4.0.1 to version 4.5.1. 3. (optional) Upgrade the application server to a newer version (for example, WebSphere 7 or JBoss Application Server 4.2.3) that supports Content Engine 4.5.1.
IBM FileNet P8 administrator upgrade tasks

The FileNet P8 Administrator must carry out several tasks to prepare your environment for your IBM FileNet P8 Platform upgrade. v Review all rows assigned to the FileNet P8 Administrator (P8A) in the Installation and Upgrade Worksheet. While you complete the following preparation tasks, provide values for the rows that are appropriate to your installation. Tip: With the Data Filter AutoFilter command enabled, as it is by default in the shipping worksheet file (p8_worksheet.xls), perform the following actions to quickly see only the properties assigned to a particular role: Click the AutoFilter drop-down arrow in the Role column header and select P8A. Further filter the result set by clicking the AutoFilter drop-down arrow in any of the other columns and selecting a value or clear a filter by selecting All. v Review all entries in the Appendix C, New Content Engine classes and properties, on page 237. This appendix lists the new classes and properties that have been added to Content Engine in the 4.0 and 4.5 release. If you have defined any classes or properties in a 3.5 or 4.0 object store with names that are the same as any of the class or property names listed in the appendix, you must change that object store name before upgrading the object store to 4.5. The upgrade tool will check for naming conflicts and require you to change the names before proceeding. Updating Process Engine 3.5 customer applications Verify that no customer application is using the Process Engine F_AEXmitStat system field.
Updating Process Engine 3.5 customer applications

Verify that no customer application is using the Process Engine F_AEXmitStat system field. The F_AEXmitStat field is dropped from the Process Engine database during the upgrade to version 4.5.1. Before upgrading, verify that no customer index has been defined to use this field. Drop or modify any indexes using this field and update any customer applications according. To update Process Engine 3.5 customer applications: 1. Check the customer-defined indexes on the system to determine if the F_AEXmitStat field has been used in any index. Refer to the following help topics for information on how to do this:
213
User help > Integrating Workflow > Workflow Applications > Process Configuration Console > Getting Started > Manage properties of queues, rosters, and event logs > Manage index properties User help > Integrating Workflow > Workflow Applications > Process Configuration Console > Getting Started > Manage properties of queues, rosters, and event logs > Manage index
2. If any index uses this field, drop the index, as in the case of a simple index, or remove the field, such as in the case of composite indexes. 3. Modify any customer applications that use the affected indexes accordingly.
214
Appendix A. Installing IBM FileNet P8 Platform in a non-English environment

To run IBM FileNet P8 components in a non-English environment, certain conditions must be met. Review the following considerations and tasks, organized by administrator role, if you plan to run IBM FileNet P8 in a non-English environment. Application Server administrator To support Unicode UTF-8 characters, all FileNet P8 domain application servers must be properly configured and must have all fix packs installed. Security administrator on page 216 The IBM FileNet P8 security administrator installation role includes configuring and maintaining directory servers. Database administrator on page 216 The IBM FileNet P8 database administrator installation role includes configuring database installations and tablespaces, and creating database accounts. IT administrator on page 222 Depending on the operating system, the IT administrator installs either a localized version of the operating system, or the operating system language pack. IBM FileNet P8 administrator on page 224 The FileNet P8 administrator starts Process Engine services and configures Process Task Manager for Application Engine and Workplace XT. Limitations on page 224 IBM FileNet P8 installations on non-English environments have limitations.
Application Server administrator

To support Unicode UTF-8 characters, all FileNet P8 domain application servers must be properly configured and must have all fix packs installed. Configuring character encoding on WebSphere Application Server IBM FileNet P8 requires the following character encoding settings. Configuring character encoding (WebLogic Server) on page 216 Set the appropriate codesets to UTF-8. WebLogic Server on page 216 (WebLogic Server 9.x) To fix the BEA CR298435 character corruption problem in FileNet P8, apply WebLogic Server 9.2 MP1 on WebLogic Server 9.x.
Configuring character encoding on WebSphere Application Server

IBM FileNet P8 requires the following character encoding settings. 1. Set the com.ibm.CORBA.ORBCharEncoding property to 0x05010001. 2. Set the com.ibm.websphere.security.BasicAuthEncoding property to UTF8.
215
Configuring character encoding (WebLogic Server)

Set the appropriate codesets to UTF-8. To configure the correct character encoding: Set the following Interop-Orb-Protocol (IIOP) attributes: v Default Char Codeset to UTF-8 v Default Wide Char Codeset to UTF-8
WebLogic Server
(WebLogic Server 9.x) To fix the BEA CR298435 character corruption problem in FileNet P8, apply WebLogic Server 9.2 MP1 on WebLogic Server 9.x.
The IBM FileNet P8 security administrator installation role includes configuring and maintaining directory servers. Extended characters and user names Note the following considerations for localized IBM FileNet P8 accounts.
Extended characters and user names

Note the following considerations for localized IBM FileNet P8 accounts. v With Microsoft Active Directory, Process Engine supports: Extended characters in user names and passwords for all Latin1, Latin2, and Arabic languages Extended characters in passwords for double-byte languages (Users names are not supported due to Microsoft limitations.) v Process Engine does not support extended characters in LDAP attributes for authentication purposes. These attributes include, but are not limited to, such items as cn (common name), ou (organizational unit), or dc (domain component). ASCII characters are required for these attributes. v Process Engine does not support non-ASCII user names. Therefore, do not use non-ASCII user names when starting the Process Task Manager. v WebDAV and the SSO environment also do not support Non-ASCII user names. v The Content Engine locale must match directory server locale to manage non-ASCII user names correctly. v UNIX systems can support Latin1, Latin2, Arabic, and double-byte user names simultaneously. Support for a Windows non-ACSII user name is limited to the Process Engine database code page. For example, if the Process Engine database code page is Japanese, Process Engine can support only Japanese and English user names. If the Process Engine database code page is Latin1, Process Engine can support all Latin1 user names, such as English, French, German, Spanish, and so forth.
The IBM FileNet P8 database administrator installation role includes configuring database installations and tablespaces, and creating database accounts. Installing Microsoft SQL Server on page 217 During installation, the Microsoft SQL Server installer program detects the Windows regional setting and sets the Microsoft SQL Server language setting
216
accordingly. Use the regional setting selected by the installation program throughout the entire Microsoft SQL Server installation. Installing Oracle server Before installing Oracle, verify that the operating system locale is set appropriately. Installing the DB2 server on page 221 Single instances of Content Engine and Process Engine on a DB2 server can support multiple languages.
Installing Microsoft SQL Server

During installation, the Microsoft SQL Server installer program detects the Windows regional setting and sets the Microsoft SQL Server language setting accordingly. Use the regional setting selected by the installation program throughout the entire Microsoft SQL Server installation. Microsoft does not recommend changing the selected regional setting unless you have to match the regional setting to the collation of another instance of Microsoft SQL Server or to the Windows regional setting of another computer. Localized versions of Microsoft SQL Server are available in French, German, Spanish, Italian, Japanese, Korean, and Simplified and Traditional Chinese. Restriction: Process Engine does not support Unicode UTF-8 encoded characters when using Microsoft SQL Server. Process Engine stores characters according to the Process Engine Windows regional setting. Using a binary sort for Process Engine is faster when configuring Microsoft SQL Server. However, IBM does support other collation settings. (A specific list of supported sort orders is not available. The collation setting depends on which sort order you need to use in your production environment.) Queried information returns in the selected sort order. The sort order can be either binary or based on a combination of sort options, such as language, case-insensitive (ci), case-sensitive (cs), accent-insensitive (ai), and accent-sensitive (as). The collation designator is a collation name that is based on a Windows regional setting. When you specify a collation designator, you should specify a sort order as well. For example: French - Latin 1 SQL Collations: Dictionary order, case-sensitive, for use with 1252 Character Set (or any case-sensitive MS-SQL collation).
Installing Oracle server

Before installing Oracle, verify that the operating system locale is set appropriately. For more information, see http://www.lc.leidenuniv.nl/awcourse/oracle/ server.920/a96529/ch3.htm#49757.
217
Content Engine
A single instance of Content Engine on an Oracle server in a Windows environment can support multiple languages by: v Selecting the Unicode AL32UTF8 database character set when configuring the Oracle database. v Installing the appropriate Windows language packs.
Process Engine
A single instance of Process Engine on an Oracle server in a UNIX environment can support multiple languages by selecting the Unicode AL32UTF8 database character set when configuring the Oracle database. If support for more than one language is not required, select the appropriate language database character set instead. Some examples of Process Engine supported database character sets are: AL32UTF8 Supports all languages that Process Engine currently supports. JA16SJIS Supports only Japanese and English. WE8ISO8859P15 Supports West European with Euro currency support, but not Japanese. Restriction: Process Engine does not support the National Character Set AL32UTF16 (NCHAR, NVARCHAR2, and NCLOB columns). Installing Oracle client Consider the following language information when installing Oracle Client software. UNIX on page 220 For all Process Engine deployments using a remote Oracle database, confirm the following two environment variables in the fnsw user profile are set to the proper locale for Process Engine.
Installing Oracle client

Consider the following language information when installing Oracle Client software. NLS_LANG environment variable - charset When data is exported from an Oracle database, it is converted from the database character set to the character set specified in the NLS_LANG environment variable on the Oracle client. Setting the NLS_LANG variable on Windows on page 219 To set the NLS_LANG variable, open the Registry Editor and update HKEY_LOCAL_MACHINE SOFTWARE ORACLE_HOME NLS_LANG= language_territory.charset. NLS_LANG environment variable - charset: When data is exported from an Oracle database, it is converted from the database character set to the character set specified in the NLS_LANG environment variable on the Oracle client.
218
When data is imported to an Oracle database, it is assumed imported data is already in the character set specified in the NLS_LANG environment variable. If the database character set matches the operating system locale, you do not need to set the NLS_LANG environment variable. However, if the database character set does not match the operating system locale and the NLS_LANG environment variable is not set, data could become garbled because the database will incorrectly map the import/export data between the database and operating system. Requirement: The NLS_LANG environment variable setting must match the UNIX locale or the Windows code page of the Process Engine server if the Oracle database is remote. The format of the NLS_LANG environment variable is:
NLS_LANG = language_territory.charset
The following table provides a brief explanation about the environment variable arguments. For more information, see the Oracle documentation.
Arguments Language Description Specifies the language used for Oracle messages, day names, and month names. Each supported language has a unique name, for example, American, French, or Japanese. The language argument has default values for the territory and character set arguments, so either (or both) of the territory or the character set arguments can be omitted. If a language is not specified, the value defaults to American. Specifies the default date format and decimal character used for numbers. Each supported territory has a unique name, for example, America, France and Japan. Because each language provides a default territory, a value is not required. Charset Specifies the character set used by the client application (normally that of the users terminal). Each supported character set has a unique acronym, for example, US7ASCII, WE8ISO8859P1, or JA16EUC. Because each language provides a default character set, a value is not required.
Territory
Setting the NLS_LANG variable on Windows: To set the NLS_LANG variable, open the Registry Editor and update HKEY_LOCAL_MACHINE SOFTWARE ORACLE_HOME NLS_LANG= language_territory.charset. 1. Determine the Oracle database character set that best matches the Process Engine Windows server code page. 2. Open the Registry Editor by typing regedit at the command prompt. 3. Navigate to and update HKEY_LOCAL_MACHINE SOFTWARE ORACLE_HOME NLS_LANG= language_territory.charset. 4. Verify the character set matches the Process Engine Windows operating system code page. 5. Click OK to close the window and exit the Registry Editor.
219
For more information, see http://www.microsoft.com/globaldev/reference/ WinCP.mspx.
UNIX
For all Process Engine deployments using a remote Oracle database, confirm the following two environment variables in the fnsw user profile are set to the proper locale for Process Engine. The LANG environment variable specifies internationalization information that allows users to work with different national conventions in UNIX. For more information, see the UNIX documentation. Setting the NLS_LANG environment variables The task of setting the NLS_LANG environment variables consists of configuring the language, territory and character set that correspond to the locale of your Process Engine server. Setting the NLS_LANG environment variables: The task of setting the NLS_LANG environment variables consists of configuring the language, territory and character set that correspond to the locale of your Process Engine server. Modify the fnsw user.profile file in /home/fnsw:
export NLS_LANG=language_territory.charset
where: language_territory.charset is the language, territory, and charset that best match your Process Engine server locale. Example of Process Engine LANG, Oracle character sets, and NLS_LANG configurations: The following table includes some sample NLS_LANG settings for different Process Engine configurations. Most important is to match your NLS_LANG to a Process Engine locale, not the Oracle database character set. For multilingual Process Engine configurations, the database character set must be AL32UTF8, and the server must use an UTF-8 locale. For example, LANG=JA_JP.UTF-8, or NLS_LANG=Japanese_Japan.UTF8 or NLS_LANG=French_France.UTF8@euro.
Locale/Windows Remote Oracle Code Page Character Set LANG= JA_JP.UTF-8 AL32UTF8 NLS_LANG for PE Server fnsw User NLS_LANG= Japanese_Japan. UTF8
OS AIX
Comments Because the AIX locale is Unicode, use the UTF-8 character set. Because Solaris data will be in eucJP, the Oracle JA16EUC character set is the best match.
Sun Solaris
LANG= ja_JP.eucJP
JA16SJIS
NLS_LANG= Japanese_Japan. JA16EUC
220
OS HP-UX
Locale/Windows Remote Oracle Code Page Character Set LANG= ja_JP.eucJP AL32UTF8
NLS_LANG for PE Server fnsw User NLS_LANG= Japanese_Japan. JA16EUC
Comments Because HP-UX data will be in eucJP, the Oracle JA16EUC character set is the best match. Because Shift-JIS is the code page for Windows, the Oracle JA16SJIS character set is the best match.
Windows
Japanese (Shift-JIS)
AL32UTF8
NLS_LANG= Japanese_Japan. JA16SJIS
Windows
JA16SJIS
Because Shift-JIS NLS_LANG= Japanese_Japan. J is the code page A16SJIS for Windows, The Oracle JA16SJIS character set is the best match. NLS_LANG= Japanese_Japan. JA16SJIS Although the database character set is JA16EUC, the Oracle character set in NLS_LANG is JA16SJIS since Shift-JIS is the code page for Windows.
Windows
JA16EUC
Installing the DB2 server

Single instances of Content Engine and Process Engine on a DB2 server can support multiple languages.
Content Engine
A single instance of Content Engine on a DB2 server can support multiple languages using Windows language packs.
Process Engine (UNIX)

To make a single instance of Process Engine in a UNIX environment support multiple languages, select the UTF-8 database character set when configuring the DB2 database. If support for more than one language is not required, select the appropriate language database character set instead. The following example shows a script line that could be used when creating a Process Engine database on AIX for multilingual support. The example illustrates a Unicode database code set with Japanese territory and collation support.
db2 create db VWDB using codeset UTF-8 territory JA_JP collate using system;
221
For more information, see the planning section in the DB2 administration guide.
IT administrator
Depending on the operating system, the IT administrator installs either a localized version of the operating system, or the operating system language pack. Operating system considerations In addition to any operating system platforms, the IT administrator must consider the FileNet P8 Platform components that will be installed in a non-English environment. Microsoft Windows on page 223 Use the localized Windows version when available. If the localized version is not available, use the English version with the appropriate regional setting. UNIX on page 223 Install the operating system language packs. For more information, see the operating system installation documentation.
Operating system considerations

In addition to any operating system platforms, the IT administrator must consider the FileNet P8 Platform components that will be installed in a non-English environment.
Application Engine or Workplace XT

Application Engine and Workplace XT can be installed: v In any locale on any of the supported UNIX platforms v On any localized version of Windows or in any region on the English version of Windows Remember: The Application Engine and Workplace XT setting must match the Process Engine setting when the Process Task Manager is started. Otherwise, workflows can experience unexpected problems such as errors related to the way characters display.
Content Engine
Content Engine can be installed: v In any locale on any of the supported UNIX platforms v On any localized version of Windows or in any region on the English version of Windows
Process Engine
Process Engine must be installed on: v A UTF-8 locale and a UTF-8 database character set when used with Oracle or DB2 v On any localized version of Windows for the supported language or in any region on the English version of Windows Process Engine has limited language support on Windows. Process Engine supports only those languages that are supported by the Windows code page and a corresponding database character set. For example, if the active Windows code page and the corresponding database character set support Latin 1 languages,
222
Process Engine will support such languages as English, French, Spanish, and Italian (and other Latin 1 languages) because these languages share a common character code page. However, Japanese cannot be supported in this scenario because the Japanese language uses a different character code page. Conversely, if the active Windows code page and the corresponding database character set support Japanese (and English) will be the only languages supported by Process Engine. v All Windows character code pages support English in addition to their primary languages. v In UNIX environments, Process Engine language support is determined by a combination of the operating system locale and the database character set. v The Java Runtime Environment version must be 1.5.0 or higher for the language capability to function correctly.
Microsoft Windows
Use the localized Windows version when available. If the localized version is not available, use the English version with the appropriate regional setting. Use the Regional Options Control Panel to change the regional setting. For more information, see the Windows help system.
UNIX
Install the operating system language packs. For more information, see the operating system installation documentation. Configuring support for other languages in X Windows UNIX system Add language fonts for your UNIX operating system if necessary to display an X-Windows desktop in a specific-language user interface. Follow your UNIX operating system administration guide to install other language fonts. Setting the LANG, LC_TIME, and LC_MESSAGES environment variables When the IT administrator sets the LANG, LC_TIME, and LC_MESSAGES environment variables, the locale must be the same as the UNIX locale and the Process Engine locale.
Configuring support for other languages in X Windows UNIX system

Add language fonts for your UNIX operating system if necessary to display an X-Windows desktop in a specific-language user interface. Follow your UNIX operating system administration guide to install other language fonts. Configure your X-session manager application to use UNIX operating system fonts. Refer to your X-session manager application administration guide for details on adding fonts or accessing them on the UNIX server.
Setting the LANG, LC_TIME, and LC_MESSAGES environment variables

When the IT administrator sets the LANG, LC_TIME, and LC_MESSAGES environment variables, the locale must be the same as the UNIX locale and the Process Engine locale. Set the LANG, LC_TIME, and LC_MESSAGES environment variables: For example:
LANG=locale export LANG
223
Where locale is the same as the UNIX locale and the Process Engine locale. v Use UTF-8 if Process Engine needs to support multiple languages that are not in the same language code page. v Use the UNIX locale -a command to determine the available locales. v Setting the LANG variable might reset the LC_TIME and LC_MESSAGES variables to the locale set in LANG. If this happens, you must change the settings of LC_TIME and LC_MESSAGES back to C or equivalent ISO-8859 locales. For example:
export LC_TIME="C" export LC_MESSAGES="C"

The FileNet P8 administrator starts Process Engine services and configures Process Task Manager for Application Engine and Workplace XT. Process Engine services All Process Engine services must start in a Unicode locale to support multiple languages on a UNIX platform. Regions initialized in a specific locale must restart in the same locale. Configuring Process Task Manager for Application Engine and Workplace XT In UNIX environments, verify the operating system locale is same as the Process Engine locale, and verify the LC_TIME and LC_MESSAGES are set to C or an equivalent ISO-8859 locale before running Process Task Manager in Application Engine or Workplace XT. Failing to do so can result in character corruption and application failure.
Process Engine services

All Process Engine services must start in a Unicode locale to support multiple languages on a UNIX platform. Regions initialized in a specific locale must restart in the same locale. Attention: Starting Process Engine services in a different locale can corrupt transferred workflow and region queue names in the isolated region. If an isolated regions non-English queue names are corrupted due to starting Process Engine services in the wrong locale, the only recovery option available is to re-initialize the region to clean up the Process Engine database. Transferred workflows and region queues will be lost.
Configuring Process Task Manager for Application Engine and Workplace XT

In UNIX environments, verify the operating system locale is same as the Process Engine locale, and verify the LC_TIME and LC_MESSAGES are set to C or an equivalent ISO-8859 locale before running Process Task Manager in Application Engine or Workplace XT. Failing to do so can result in character corruption and application failure. Restriction: Application Engine or Workplace XT locales must match the Process Engine UNIX locale when starting Process Task Manager.
Limitations
IBM FileNet P8 installations on non-English environments have limitations.
224
Oracle WebLogic Server

WebLogic Server 8.1 is not supported on a Turkish operating system.
GB18030 support for Windows Process Engine

Process Engine installed on Windows does not support GB18030 Simplified Chinese characters.
Application Engine, Workplace XT, or Process Engine Task Manager for UNIX
If Application Engine, Workplace XT, or Process Engine is installed on a UNIX platform, Process Task Manager (vwtaskman), takes too long to launch when run under a UTF-8 locale using remote CDE shells such as xWindows (exceed, xManager, etc). Verify that the xWindows application can handle Unicode fonts to fix this problem. The command-line interface functionality is not affected.
Publishing
When the watermark is checked in the Publishing Style Template Manager on the Content Engine server, double-byte documents cannot be published. This is a known independent software vendor issue.
Process Engine Modeler

To import a user defined XSD file containing non-English characters in Process Designer, run the following command to convert characters to the Unicode encoding format to match a UNIX Process Engine in a UTF-8 locale, then import the XSD file into Process Designer.
Java -cp pe.jar filenet.vw.toolkit.utils.FileConverter /in filename /out outfilename
225
226

The tables below list the port numbers used by IBM FileNet P8 components.
Content Engine ports

Port name LDAP Default number 389 Notes This port is on the directory server, specified on the Content Engine server for authentication. This port is on the directory server, specified on the Content Engine for authentication through SSL.
SSL
636
LDAP Global Catalog WebSphere EJB
3268 2809 This port is on the WebSphere Application Server for Content Engine, for communication with Content Engine by clients through EJB. This port is on the WebSphere Application Server for Content Engine, for communication with Content Engine by clients through WSI. This port is on the WebLogic Server for Content Engine for communication with Content Engine by clients. This port is on the JBoss Application Server for Content Engine for communication with Content Engine by clients through EJB. This port is on the JBoss Application Server for Content Engine for communication with Content Engine by clients through WSI. This port is on the JBoss Application Server for Content Engine for communication with Content Engine by clients through IIOP.
WebSphere WSI
9080
WebLogic
7001
JBoss EJB
1099
JBoss WSI
8080
JBoss IIOP
3528
227
Port name DB2
Default number 50000
Notes This port is on the DB2 database server, for communication with the database by Content Engine. This port is on the Microsoft SQL Server database server, for communication with the database by Content Engine. This port is on the Oracle database server, for communication with the database by Content Engine.
Microsoft SQL Server
1433
Oracle
1521
Process Engine ports

Port name SMTP (E-mail Notification) DB2 Default number 25 50000 Notes This port is on the SMTP server. This port is on the database server, for connection between Process Engine and DB2. This port is on the database server, for connection between Process Engine and Microsoft SQL Server. This port is on the database server, for connection between Process Engine and Oracle. This port is on the Oracle (Windows) database server. Task Manager service. TM_daemon listens for requests from initfnsw running on the same or a different system analogous to COR_Listen listening for RPCs. Courier service. COR_Listen listens on this port for incoming RPC requests. nch is the NCH deamon. NCH_daemon listens on this port. Pre-4.1.2 listened for broadcasts, etc. Post 4.1.2, only listens for old print servers to verify NCH is up.
1433
Oracle
1521
Oracle Services for Microsoft 2030 Transaction Server (Windows) TMS 32768 (TCP)
COR
32769 (TCP)
NCH
32770 (UDP)
228
Port name fn_snmpd
Default number 161 (UDP)
Notes IBM FileNet Image Services Simple Network Management Protocol Daemon. It listens for SNMP requests from the native OS snmp daemon. The native snmp daemon listens on this port and communicates with fn_snmpd through other local port. fn_snmpd does not listen on this port. fn_trapd is the IBM FileNet Image Services trap daemon, which listens for notifications of the end of Image Services background processes running on the server and sys_logs information. This port is on the Process Engine server. This port is on the Process Engine server. This port is on the Process Engine server. This port is on the Process Engine server. This port is on the Process Engine server and is used by the Component Manager. This port is on the Process Engine server.
fn_trapd
35225 (UDP)
SNMPD SMUX (AIX only) Rules Listener Process Engine Communication Port (IOR port) BPM Web Services Reliable messaging client port Registry Port
199 (TCP) 32774 (TCP/IP) 32776
32767 (TCP) 32767 (UDP) 32771
Event Port
32773
Application Engine ports

Port name WebSphere Default number 9080 Notes This port is on the WebSphere Application Server for clients to connect to Application Engine. This port is on the WebSphere Application Server for clients to connect to Application Engine through SSL. This port is on the WebLogic Server for clients to connect to Application Engine. This port is on the WebLogic Server for clients to connect to Application Engine through SSL.
WebSphere SSL
443
WebLogic
7001
WebLogic SSL
7002
229
Port name JBoss
Default number 8080
Notes This port is on the JBoss Application Server for clients to connect to Application Engine. This port is on the JBoss Application Server for clients to connect to Application Engine through SSL. This port is on the Windows Process Engine server for Process Task Manager to communicate with the Windows Process Engine Services Manager. This port is on the Application Engine server for Process Task Manager to communicate with the Component Managers and the Windows Process Application Engine (or Workplace XT) Services Manager.
JBoss SSL
8443
Process Engine (RMI)
32771
Component Manager (Event Port)
32773
This port is on the Application Engine server, and is used when the Component Manager (running on the Application Engine Server) is configured to be triggered by events, instead of polling. This port is on the Process Engine server, and is for the vworbbroker process handling RPCs from the PE API clients. This port (or a number of ports, one per Component Manager instance) is on the Application Engine server to respond to the WS-Reliable Messaging requests.
Process Engine Broker Port
32777
Web Services Reliable Messaging Client Port
xxxx - assigned by the client on the Application Engine Server, for a particular Component Manager instance.
Autonomy K2 search engine ports

Port name K2 Master Administration Server Default number 9950 (default) Notes This port is located on the machine that hosts the K2 Master Administration Server machine. It is the software port for K2 Master Administration Server.
230
Port name K2 Dashboard
Default number 9990 (default)
Notes This port is located on the machine that hosts the K2 Master Administration Server. It is used specifically for the URL access for the K2 Dashboard. This port is located on the machine where you created the K2 Index Server service. It is for communication between the K2 Index Server and P8 Content Engine. This port is located on the machine where you created the K2 Broker Server service. It is for communication between the K2 Broker Server and P8 Content Engine. This port is located on the machine where you created the K2 Server (Search Server) service. It is for communication between the K2 Server (Search Server) and Content Engine. This port is located on the machine where you created the K2 Ticker Server service. It is for communication between the K2 Ticket Server and Content Engine.
K2 Index Server
9960 - 9979 (recommended range)
K2 Broker Server
K2 Server (Search Server)
K2 Ticket Server
Rendition Engine and Content Engine ports for Liquent

Port name Liquent input port Default number 2867 (COM Repository only) Notes This port allows for distributed processing of jobs on the Rendition Engine servers when there are more than one Rendition Engine server. A Rendition Engine server or Rendition Engine client (Content Engine Publishing server) on which a job is submitted makes the load balancing decision on where to run the job. If the job is sent to another Rendition Engine server for execution then it uses the other Rendition Engine servers input port to do so.
231
Port name Liquent notify port
Default number 2868
Notes This port is also related to the distributed processing of jobs on the Rendition Engine servers. When a job is sent to another Rendition Engine server then the originating Rendition Engine server or Rendition Engine client (Content Engine Publishing server) is notified on this port by the other Rendition Engine Rendition Engine server when the other Rendition Engine Rendition Engine server has finished processing the job. One case of this is when the Rendition Engine Rendition Engine server is notifying the Rendition Engine client (Content Engine Publishing server) that a conversion job has completed. This port is used by each Rendition Engine server to send or receive events. These events are used by the Rendition Engine servers to keep each other informed of current activities. The Rendition Engine or Liquent Domain Manager uses these events for the job status display. This port is used by each Rendition Engine server for internal administrative functions. Its primary use is for each Rendition Engineserver to publish its current activity statistics (for example, how busy the business services are) for use by other Rendition Engine servers to make load balancing decisions. This port is used for transferring source, temporary, and result files between Rendition Engine servers as well as between Rendition Engine servers and Rendition Engine clients (Content Engine Publishing servers).
Liquent event port
2869
Liquent admin port
2870
Liquent file transfer port
2871
232
Port name Liquent job queue port
Default number 2872
Notes This port is for job queuing by the render business service on all Rendition Engine servers. When the selected Rendition Engine database is Microsoft SQL Server, then this port is used by the Rendition Engine servers and the Rendition Engine clients (Content Engine Publishing server) to access the Rendition Engine database. When the selected Rendition Engine database is Oracle, then this port is used by the Rendition Engine servers and the Rendition Engine clients (Content Engine Publishing server) to access the Rendition Engine database.
1433
Oracle
1521
Tip: If the Liquent port number assigned to the Rendition Engine/Liquent software conflicts with the port number required by another application or service that runs on the Rendition Engine server or the Content Engine Publishing server, then the default values can be changed in the Rendition Engine/Liquent Domain Manager. The above port numbers are the default values set by the Rendition Engine installer for the COM Repository in the Rendition Engine/Liquent domain, which represents the Rendition Engine server itself. When a Content Engine Publishing server is configured to point to the Rendition Engine server, one must create a Java Repository in the Rendition Engine/Liquent domain that represents the Content Engine Publishing server as a Java client to the Rendition Engine server, and this repository will also have the same default port number values. The database port number is not specified directly by the Rendition Engine servers Liquent software, but it is specified in the Rendition Engine client/Content Engine Publishing servers Rendition Engine Connection (for the JDBC connection from the Content Engine Publishing code to the Rendition Engine database server).
233
Process Analyzer ports

Port name Registry port Default number 32771 Notes This is the default RMI port on the Process Analyzer server. The Process Task Manager application on the Process Analyzer server communicates with the Process Analyzer server process on this port. The Process Simulator also communicates with the Process Analyzer server on this port. The Process Simulator can be installed on the Process Analyzer server or be remote. This port is on the Process Analyzer database server. The Process Analyzer server communicates with the Process Analyzer database on this port. The Process Simulator also communicates with the Process Analyzer database on this port. This port is on the Process Engine database server. The Process Analyzer server communicates with the Process Engine database on this port.
PA database port
DB2: 50000 Microsoft SQL Server: 1433 Oracle: 1521
PA database port
DB2: 50000 Microsoft SQL Server: 1433 Oracle: 1521
Process Simulator ports

Port name Process AnalyzerProcess Analyzer Default number 32771 Notes This port is on the Process Analyzer server (Registry Port). Process Simulator communicates with Process Analyzer on this port. This port is on the Process Simulator server. The Process Task Manager application on the Process Simulator server communicates with the Process Simulator server process on this port. The Application Engine also communicates with the Process Simulator server process on this port.
Registry port
32771
234
Port name PA database port
Default number 1433
Notes This port is on the Process Analyzer database server and is used by the Process Simulator to communicate with the Process Analyzer database. This port is on the Process Simulator server and is used to communicate with the Application Engine server. By default an anonymous port number is used. However, if the Process Simulator server resides behind a firewall it will be necessary to specify an explicit port by entering a value other than 0.
Return
0 (anonymous)
System manager ports

Port name Listener (first) Default number 32775 Notes This is the primary pilot port for connection to the System Manager server. This port also registers the other secondary allocated ports and communicates those numbers to the Dashboard. If needed, an administrator can use the PchConfig.properties file to override the OS-defined property and define a specific range of ports to use. If the first listener port is allocated, the OS will allocate additional ports for managers to connect to listeners on the System Manager server. If needed, an administrator can use the PchConfig.properties file to override the OS-defined property and define a specific range of ports to use.
Listener (subsequent)
OS defined
IBM FileNet Content Services for Image Services ports

Port name tms Default number 32768 (TCP) Notes tms is the Task Manager service. TM_daemon listens for requests from initfnsw running on the same or a different system analogous to COR_Listen listening for RPCs.
235
Port name cor
Default number 32769 (TCP)
Notes cor is the Courier service. COR_Listen listens on this port for incoming RPC requests. nch is the NCH deamon. NCH_daemon listens on this port. Pre-4.1.2 listened for broadcasts, etc. Post 4.1.2, only listens for old print servers to verify NCH is up. fn_snmpd is the Image Services Simple Network Management Protocol Daemon. It listens for SNMP requests from the native OS snmp daemon. The native snmp daemon listens on this port and communicates with fn_snmpd through other local port. fn_snmpd does not listen on this port. This is a well-known OS trap daemon port for listening to trap messages. All Image Services trap messages received by fn_trapd daemon are eventually routed to this port. fn_trapd is the Image Services trap daemon, which listens for notifications of the end of Image Services background processes running on the server and sys_logs information. All non-Image Services based SNMP requests are routed to this port for native SNMP processing. All Image Services based SNMP requests are routed to this port for fn_snmpd daemon processing. ds_notify and pri_notify processes send TPI notifications to signal completion of a task.
nch
32770 (UDP)
fn_snmpd
161 (UDP)
snmp trap
162 (UDP)
fn_trapd
35225 (UDP)
Native default SNMP port (HP only)
8000 (UDP)
IBM FileNet P8 specific SNMP port (HP and Solaris only) Migration notify
8001 (UDP)
anonymous
Important: On UNIX platforms, Image Services port assignments are made in the /etc/services file.
236
Appendix C. New Content Engine classes and properties

Content Engine classes and properties have been added to Content Engine in the 4.0 and 4.5 release. The classes and properties that have been added to the 4.5.1 release have been prefixed with the reserved value Cm to prevent conflict with user-defined classes and properties. Upgrading from version 3.5 to 4.5.1 If you have previously defined any classes or properties in a version 3.5 object store with symbolic names that are the same as any of the class or property symbolic names listed here, the upgrade tool will detect the naming conflicts and require you to change your class or property names before it will upgrade the object store to version 4.5.1. Therefore, you must resolve conflicts between your version 3.5 symbolic names and the version 4.0 and 4.5 symbolic names. Upgrading from version 4.0 to 4.5.1 Upgrades from version 4.0 use the automatic upgrade facility, which automatically renames any conflicting class or property symbolic name that it detects during the upgrade. The upgrade facility writes warning messages for each renamed class or property symbolic name to a log file p8_server_error.log on the application server where Content Engine is deployed. It also writes these messages to the automatic upgrade status web page. If you know of naming conflicts with 4.5 classes or properties, it is a best practice to resolve these conflicts before you upgrade to version 4.5.1 of Content Engine. Upgrading from version 4.5 to 4.5.1 Upgrades from 4.5 use the automatic upgrade facility, which will not encounter any conflicting class or property symbolic names. New in Content Engine 4.0.0 (for upgrades from 3.5 only) When you upgrade to Content Engine 4.0 from Content Engine 3.5, you need to consider new classes and properties. New in Content Engine 4.5.0 (for upgrades from 3.5 and from 4.0) on page 246 When you upgrade to Content Engine 4.5 from Content Engine version 3.5 or version 4.0, you need to consider new classes and properties.
New in Content Engine 4.0.0 (for upgrades from 3.5 only)

When you upgrade to Content Engine 4.0 from Content Engine 3.5, you need to consider new classes and properties. New Content Engine classes in 4.0.0 on page 238 The following table displays the new class names in Content Engine 4.0.0. To ensure successful upgrade, resolve any conflicts between your 3.x object store class names and the new names. New Content Engine properties in 4.0.0 on page 239 The following table displays the new property names in Content Engine 4.0.0. To ensure successful upgrade, resolve any conflicts between your 3.x object store property names and the new names.
237
New Content Engine classes in 4.0.0

The following table displays the new class names in Content Engine 4.0.0. To ensure successful upgrade, resolve any conflicts between your 3.x object store class names and the new names.
Class Symbolic Name AddOnInstallationRecord AsyncProcessingConfiguration CenteraSiteSettings CodeModule ComponentRelationship ContentCacheArea ContentCacheConfiguration ContentConfiguration DatabaseStorageArea DirectoryConfiguration DirectoryConfigurationAD DirectoryConfigurationADAM DirectoryConfigurationIBM DirectoryConfigurationNovell DirectoryConfigurationSunOne Domain EntireNetwork FileStorageArea FixedStorageArea Group ImageServicesClassDescription ImageServicesImportAgentConfiguration ImageServicesPropertyDescription ImageServicesSiteSettings IndexArea IndexJob IndexJobClassItem IndexJobCollectionItem IndexJobItem IndexJobSingleItem IsolatedRegion PEConnectionPoint PublishCompleteEvent PublishRequest PublishRequestEvent PublishingConfiguration Realm Class ID Add On Installation Record Async Processing Configuration Centera Site Settings Code Module Component Relationship Content Cache Area Content Cache Configuration Content Configuration Database Storage Area Directory Configuration Directory Configuration AD Directory Configuration ADAM Directory Configuration IBM Directory Configuration Novell Directory Configuration SunOne Domain EntireNetwork File Storage Area Fixed Storage Area Group Image Services Class Description Image Services Import Agent Configuration Image Services Property Description Image Services Site Settings Index Area Index Job Index Job Class Item Index Job Collection Item Index Job Item Index Job Single Item Isolated Region PE Connection Point Publish Complete Event Publish Request Publish Request Event Publishing Configuration Realm
238
Class Symbolic Name RenditionEngineConnection SecurityPrincipal ServerCacheConfiguration ServerInstance Site SiteSettings StorageArea StoragePolicy SubsystemConfiguration TakeFederatedOwnershipEvent TraceLoggingConfiguration UpgradeAddOn User VerityCollection VerityDomainConfiguration VerityIndexArea VerityServerConfiguration VirtualServer
Class ID Rendition Engine Connection Security Principal Server Cache Configuration Server Instance Site Site Settings Storage Area Storage Policy Subsystem Configuration Take Federated Ownership Event Trace Logging Configuration Upgrade Add On User Verity Collection Verity Domain Configuration Verity Index Area Verity Server Configuration Virtual Server
New Content Engine properties in 4.0.0

The following table displays the new property names in Content Engine 4.0.0. To ensure successful upgrade, resolve any conflicts between your 3.x object store property names and the new names.
Property Symbolic Name AbandonedContentCleanupInterval AbandonedDBContentCleanupInterval ActiveDirectorySiteDNS AddOn AddOnInstallationRecords AddOns AddOnName AllRealms AllowFederatedDeletes AllowsContentToBeCached AllowsDelete APITraceFlags AppenderNames ApplyDefinition AsynchronousProcessingTraceFlags AuditedDeletePrefix Property Name Abandoned Content Cleanup Interval Abandoned Database Content Cleanup Interval Active Directory Site DNS Add On Add On Installation Records Add Ons Add On Name All Realms Allow Federated Deletes Allows Content To Be Cached Allows Delete API Trace Flags Appender Names Apply Definition Asynchronous Processing Trace Flags Audited Delete Prefix
239
Property Symbolic Name BaseClassIDs BatchDelay BlobReadAheadSize BlobWriteCollisionsAvoidanceFlag BrokerPort FPPoolBufferSize CacheStatus CanAcceptForwardedRequests CanForwardRequests CBRLocale CBRTraceFlags CFSDaemonTraceFlags ChildComponent ChildDocuments ChildRelationships ChildVersionSeries ClassDefinition ClosureDate FPPoolClusterNonAvailTime CodeModule CodeModuleCacheEntryTTL CodeModuleCacheMaxFileSpace CodeModuleCacheMaxMemory CodeModuleTraceFlags CollectionName ComponentCascadeDelete ComponentPreventDelete ComponentRelationshipType ComponentSortOrder CompoundDocumentState ConcurrentReaders ConnectionState ConnectionTimeout ContentCacheArea ContentCacheAreas ContentCacheTraceFlags ContentElementCount ContentElementKBytes ContentElementsCreated ContentElementsDeleted ContentQueueMaxWorkerThreads
Property Name Base Class IDs Batch Delay Blob Read Ahead Size Blob Write Collisions Avoidance Flag Broker Port Buffer Size Cache Status Can Accept Forwarded Requests Can Forward Requests CBR Locale CBR Trace Flags CFS Daemon Trace Flags Child Component Child Documents Child Relationships Child Version Series Class Definition Closure Date Cluster Nonavailable Time Code Module Code Module Cache Entry TTL Code Module Cache Maximum File Space Code Module Cache Maximum Memory Code Module Trace Flags CollectionName Component Cascade Delete Component Prevent Delete Component Relationship Type Component Sort Order Compound Document State Concurrent Readers Connection State Connection Timeout Content Cache Area Content Cache Areas Content Cache Trace Flags Content Element Count Content Element Kbytes Content Elements Created Content Elements Deleted Content Queue Max Worker Threads
240
Property Symbolic Name ContentStorageTraceFlags ContentTempDirectoryRoot CSMCache CurrentUser DatabaseContentUploadBufferSize DatabaseServerPort DatabaseTraceFlags DatabaseType FPPoolDefaultCollisionAvoidance DefaultISDocumentClass DefaultRetentionDays DefaultRetentionPassThrough DefaultSite DeleteMethod DeviceAddress DeviceRootDirectory DirectoryConfigurations DirectoryServerHost DirectoryServerPassword DirectoryServerPort DirectoryServerProviderClass DirectoryServerType DirectoryServerUserName DirectoryStructure DispatcherEnabled DispatcherWaitInterval DistinguishedName DNSName DocumentsPerBatch Domain DomainID EJBForwardingEndpoint EJBTraceFlags Email EmbeddedDataThreshold FPPoolEnableMulticlusterFailover EncryptionAlgorithm EngineTraceFlags ErrorCode ErrorDescription EventsTraceFlags
Property Name Content Storage Trace Flags Content Temp Directory Root CSM Cache Current User Database Content Upload Buffer Size Database Server Port Database Trace Flags Database Type Default Collision Avoidance Default IS Document Class Default Retention Days Default Retention Pass Through Default Site Delete Method Device Address Device Root Directory Directory Configurations Directory Server Host Directory Server Password Directory Server Port Directory Server Provider Class Directory Server Type Directory Server User Name Directory Structure Dispatcher Enabled Dispatcher Wait Interval Distinguished Name DNS Name Documents Per Batch Domain Domain ID EJB Forwarding Endpoint EJB Trace Flags Email Address Embedded Data Threshold Enable Multicluster Failover Encryption Algorithm Engine Trace Flags Error Code Error Description Events Trace Flags
241
Property Symbolic Name ExpiredBatchSelectionSize FixedContentDevice FixedContentDevices FixedContentProviderTraceFlags FolderCacheMaxAgeDelta FolderCacheMaxEntries FolderCacheReapFrequency FromVersions FullTextRowDefault FullTextRowMax GCDCacheTTL GCDTraceFlags GroupBaseDN GroupDisplayNameAttribute GroupMembershipSearchFilter GroupNameAttribute GroupSearchFilter Groups ImageServicesClassDescriptions ImageServicesClassName ImageServicesDataType ImageServicesPropertyDescriptions ImageServicesPropertyName ImplementationClass ImportAgentRetryCount InboundFileNameCacheMaxEntries IndexArea IndexAreas IndexItems IndexationID InitiatingUser InlineContentRetrievalLimit InputDocument InstallationDate InstallationReport Installer IsCBREnabled ISDomainName IsFederatedOnly ISOrganization ISPassword
Property Name Expired Batch Selection Size Fixed Content Device Fixed Content Devices Fixed Content Provider Trace Flags Folder Cache Maximum Age Delta Folder Cache Maximum Entries Folder Cache Reap Frequency From Versions Full Text Row Default Full Text Row Max GCD Cache TTL GCD Trace Flags Group Base DN Group Display Name Attribute Group Membership Search Filter Group Name Attribute Group Search Filter Groups Image Services Class Descriptions Image Services Class Name Image Services Data Type Image Services Property Descriptions Image Services Property Name Implementation Class Import Agent Retry Count Inbound File Name Cache Maximum Entries Index Area Index Areas Index Items Indexation ID Initiating User Inline Content Retrieval Limit Input Document Installation Date Installation Report Installer Is CBR Enabled IS Domain Name Is Federated Only IS Organization IS Password
242
Property Symbolic Name IsSSLEnabled ISTempDir ISUserName IsolatedRegion IsolatedRegions JNDIDataSource JNDIXADataSource JobAbortRequested JobStatus LabelBindValue LeaseDuration LocalDomain MarkingSetCacheEntryTTL MarkingSetCacheMaxEntries MarkingSets MarkingUseGranted MaxBatchSize MaxCollections MaxInMemoryElementState MaxInMemoryQueueItems MaxObjectsPerCollection MaxReaderSemaphoreWaitTime FPPoolMaxConnections MaximumContentElements MaxResolutionBatchSize MaximumRetentionDays MaximumSizeKBytes MaximumTimeToLive MemberOfGroups MetadataTraceFlags MinimumRetentionDays FPPoolMulticlusterDeleteStrategy FPPoolMulticlusterExistsStrategy FPPoolMulticlusterQueryStrategy FPPoolMulticlusterReadStrategy FPPoolMulticlusterWriteStrategy MyRealm NeverDeleteClipsOrContent NoWorkDelay NumImportAgents ObjectSecurityCacheEntryTTL
Property Name Is SSL Enabled IS Temporary Directory IS User Name Isolated Region Isolated Regions JNDI DataSource JNDI XA DataSource Job AbortRequested Job Status Label Bind Value Lease Duration Local Domain Marking Set Cache Entry TTL Marking Set Cache Maximum Entries Marking Sets Marking Use Granted Max Batch Size Max Collections Max In Memory Element State Max In Memory Queue Items Max Objects Per Collection Max Reader Semaphore Wait Time Maximum Connections Maximum Content Elements Maximum Resolution Batch Size Maximum Retention Days Maximum Size Kbytes Maximum Time To Live Member Of Groups Metadata Trace Flags Minimum Retention Days Multicluster Delete Strategy Multicluster Exists Strategy Multicluster Query Strategy Multicluster Read Strategy Multicluster Write Strategy My Realm Never Delete Clips Or Content No Work Delay Num Import Agents Object Security Cache Entry TTL
243
Property Symbolic Name ObjectSecurityCacheMaxEntries ObjectStores FPOpenStrategy OptimizationInterval OriginalObject OriginalOrdinal OutputFolder OutputLocation ParentComponent ParentDocuments ParentRelationships PartialResolutionChunkSize PEConnectionPoints PersistenceType PoolAddress FPPoolPrefetchSize PreloadOnCreate Prerequisites PrivilegedSettability PruneAmount PruneThresholdContentElements PruneThresholdSizeKBytes PublicKey PublicationDocument PublishRequestType PublishStyleTemplate PublishTemplate PublishTraceFlags PublishingStatus QueueItemDatabaseTimeout QueueItemMaxDispatchers QueueItemRetryCount ReferencingActions RegionPassword RenameFileRetryAttempts RenditionEngineConnection RenditionEngineConnections RenditionEnginePassword ResourceStatus ResourceString RetentionPeriod
Property Name Object Security Cache Maximum Entries Object Stores Open Strategy Optimization Interval Original Object Original Ordinal Output Folder Output Location Parent Component Parent Documents Parent Relationships PartialResolutionChunkSize PE Connection Points Persistence Type Pool Address Prefetch Size Preload On Create Prerequisites Privileged Settability Prune Amount Prune Threshold Content Elements Prune Threshold Size KBytes Public Key Publication Document Publish Request Type Publish Style Template Publish Template Publish Trace Flags Publishing Status Queue Item Database Timeout Queue Item Max Dispatchers Queue Item Retry Count Referencing Actions Region Password Rename File Retry Attempts Rendition Engine Connection Rendition Engine Connections Rendition Engine Password Resource Status Resource String Retention Period
244
Property Symbolic Name RetrievalRetryAttempts FPPoolRetryCount FPPoolRetrySleep ReturnNameAsDN RollFwdBatchRetryAttempts RootDirectoryPath SearchCrossForestGroupMembership SearchServersToAttach SearchTraceFlags SecurityDescCacheMaxEntries SecurityTraceFlags ServerInstances ShortName SingleItem Site SiteSettings Sites SnapLockPassword SnapLockUserName SSITraceFlags StagingAreaPath Status StatusDescription StorageArea StorageAreas SubjectCacheEntryTTL SubjectCacheMaxEntries SubmittedCount SubsystemConfigurations TemplateType TempDBContentLifetime TempDirectoryPath TempFileLifetime ThreadCount TimeAllSubmitted TimeLastProcessed FPPoolTimeout TimeOutSeconds ToVersions TraceLoggingEnabled URIValue
Property Name Retrieval Retry Attempts Retry Count Retry Sleep Return Name As DN Roll Forward Batch Retry Attempts Root Directory Path Search Cross Forest Group Membership Search Servers To Attach Search Trace Flags Security Descriptor Cache Maximum Entries Security Trace Flags Server Instances Short Name Single Item Site Site Settings Sites SnapLock Password SnapLock User Name SSI Trace Flags Staging Area Path Status Status Description Storage Area Storage Areas Subject Cache Entry TTL Subject Cache Maximum Entries Submitted Count Subsystem Configurations Template Type Temporary Database Content Lifetime Temp Directory Path Temporary File Lifetime Thread Count Time All Submitted Time Last Processed Timeout Timeout Seconds To Versions Trace Logging Enabled URI Value
245
Property Symbolic Name UserBaseDN UserDisplayNameAttribute UserDomain UserGroup UserName UserNameAttribute UserPassword UserSearchFilter UserTokenCacheEntryTTL UserTokenCacheMaxEntries Users VerityAdminServerHostname VerityAdminServerPort VerityBrokerName VerityBrokers VerityCollections VerityDomainConfiguration VerityIndexServers VerityMasterAdminServerHostname VerityMasterAdminServerPort VeritySearchServers VersionBindType VirtualServer VirtualServers WSITraceFlags
Property Name User Base DN User Display Name Attribute User Domain User Group User Name User Name Attribute User Password User Search Filter User Token Cache Entry TTL User Token Cache Maximum Entries Users Verity Admin Server Hostname Verity Admin Server Port Verity Broker Name Verity Brokers Verity Collections Verity Domain Configuration Verity Index Servers Verity Master Admin Server Hostname Verity Master Admin Server Port Verity Search Servers Version Bind Type Virtual Server Virtual Servers WSI Trace Flags
New in Content Engine 4.5.0 (for upgrades from 3.5 and from 4.0)
When you upgrade to Content Engine 4.5 from Content Engine version 3.5 or version 4.0, you need to consider new classes and properties. New Content Engine classes in 4.5.0 The following table displays the new class names in Content Engine 4.5.0. To ensure successful upgrade, resolve any conflicts between your 3.5 or 4.0 object store class names and the new names. New Content Engine properties in 4.5.0 on page 247 The following table displays the new property names in Content Engine 4.5. To ensure successful upgrade, resolve any conflicts between your 3.5 or 4.0 object store property names and the new names.
New Content Engine classes in 4.5.0

The following table displays the new class names in Content Engine 4.5.0. To ensure successful upgrade, resolve any conflicts between your 3.5 or 4.0 object store class names and the new names.
246
Class Symbolic Name ReplicationGroup CMODApplicationGroup CMODFixedContentDevice CMODRepository ContentFederatingRepository DirectoryConfigurationCA DITARenditionEngineConnection ExternalAlias ExternalClassAlias ExternalClassDescription ExternalIdentity ExternalParticipant ExternalPropertyAlias ExternalPropertyDescription ExternalRepository ImageServicesRepository ObjectStoreParticipant Replicable ReplicableClassDefinition ReplicationConfiguration ReplicationJournalEntry ReplicationParticipant Repository
Class ID Replication Group CMOD Application Group CMOD Fixed Content Device CMOD Repository Content Federating Repository Directory Configuration CA DITA Rendition Engine Connection External Alias External Class Alias External Class Description External Identity External Participant External Property Alias External Property Description External Repository Image Services Repository Object Store Participant Replicable Replicable Class Definition Replication Configuration Replication Journal Entry Replication Participant Repository
New Content Engine properties in 4.5.0

The following table displays the new property names in Content Engine 4.5. To ensure successful upgrade, resolve any conflicts between your 3.5 or 4.0 object store property names and the new names.
Property Symbolic Name AliasDirection ApplicationGroupNumber ClassFamily ClassIdentity CMODApplicationGroups CMODLanguage CMODPassword CMODPort CMODServerName CMODTraceLevel CMODUserName Property Name Alias Direction Application Group Number Class Family Class Identity CMOD Application Groups CMOD Language CMOD Password CMOD Port CMOD Server Name CMOD Trace Level CMOD User Name
247
Property Symbolic Name DatabaseIndexStorageLocation DatabaseLOBStorageLocation DatabaseTableStorageLocation DateCheckedIn DestinationRepository DITADatabaseTimeout DITAHome DITAJVMArguments DITARenditionEngineConnection DITARenditionEngineConnections DITAWorkingDirectory DuplicateSuppressionEnabled DynamicGroupMemberAttribute DynamicGroupObjectClass DynamicGroupQueryAttribute ExternalAliases ExternalClassDescriptions ExternalObjectIdentity ExternalPropertyDescriptions ExternalReplicaIdentities ExternalRepositories ExternalRepository FcpPoolIdleTimeoutSeconds FcpPoolMaxInUse FcpPoolMaxWaitSeconds FcpPoolPreferredSize FederateInboundContent GroupUniqueIDAttribute GroupUniqueIDAttributeIsBinary HeldUntilDate IICEConfigurationServerURL InboundBatchSize InboundBusyWaitInterval InboundDispatcherEnabled InboundIdleWaitInterval LastFailureReason MappableDirection MaxInboundWorkers MaxOutboundWorkers ObjectStateRecordingLevel ObjectStoreSchemaDB2
Property Name Database Index Storage Location Database LOB Storage Location Database Table Storage Location Date Checked In Destination Repository DITA Database Timeout DITA Home DITA JVM Arguments DITA Rendition Engine Connection DITA Rendition Engine Connections DITA Working Directory Duplicate Suppression Enabled Dynamic Group Member Attribute Dynamic Group Object Class Dynamic Group Query Attribute External Aliases External Class Descriptions External Object Identity External Property Descriptions External Replica Identities External Repositories External Repository FCP Pool Idle Timout Seconds FCP Pool Max In Use FCP Pool Max Wait Seconds FCP Pool Preferred Size Federate Inbound Content Group Unique ID Attribute Group Unique ID Attribute Is Binary Held Until Date Content Integrator URL Inbound Batch Size Inbound Busy Wait tInterval Inbound Dispatcher Enabled Inbound Idle Wait tInterval Last Failure Reason Mappable Direction Max Inbound Workers Max Outbound Workers Object State Recording Level Object Store Schema DB2
248
Property Symbolic Name ObjectStoreSchemaMSSQL ObjectStoreSchemaOracle OutboundBatchSize OutboundBusyWaitInterval OutboundDispatcherEnabled OutboundIdleWaitInterval PartnerObjectStore PropertyIdentity RegionKey ReplicableDirection ReplicationData ReplicationGroup ReplicationGroups ReplicationMode ReplicationOperation ReplicationParticipants ReplicationStatus ReplicationTraceFlags RestrictMembershipToConfiguredRealms SearchDynamicGroup SuperclassIdentity SupersededAddOnIds TargetObjectStore UserUniqueIDAttribute UserUniqueIDAttributeIsBinary
Property Name Object Store Schema MSSQL Object Store Schema Oracle Outbound Batch Size Outbound Busy Wait tInterval Outbound Dispatcher Enabled Outbound Idle Wait tInterval Partner Object Store Property Identity Region Key Replicable Direction Replication Data Replication Group Replication Groups Replication Mode Replication Operation Replication Participants Replication Status Replication Trace Flags Restrict Membership To Configured Realms Search Dynamic Group Superclass Identity Superseded AddOn Ids Target Object Store User Unique ID Attribute User Unique ID Attribute Is Binary
249
250
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 3-2-12, Roppongi, Minato-ku, Tokyo 106-8711 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
251
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBMs suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating
252
platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided AS IS, without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml (www.ibm.com/legal/ copytrade.shtml). Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others.
Notices
253
254
Index A
accounts 192 Application Engine 61 Content Engine 56 Content Engine application server 110 Content Engine upgrade 184 Content Search Engine 62 Process Engine 61 specify upgrade accounts 183 specifying 55 accounts on upgrade Configuration Manager user on JBoss 211 Application Engine configure HP-UX 36 configuring Linux 36, 173 configuring Solaris 36 ASA installation tasks 108 upgrade tasks 197 authentication IBM Tivoli Directory Server 55 Novell eDirectory 53 Oracle Internet Directory 54 Sun Java System Directory Server Windows Active Directory 51 Windows AD LDS 52 Content Search Engine (continued) preparing storage areas to support 47 DB2 client instances creating 105 DB2 for z/OS dedicated database 96 install for Content Engine 96 install for FileNet P8 platform 98 install for Process Engine 96 installing license 106 shared database 96 DBA installation tasks 64 upgrade tasks 189 Decru 41 default time mask Solaris Process Engine 32, 170 deployment planning 3 planning application server 4 planning Content Engine 3 planning Content Engine multi-server on JBoss 6 planning Content Engine multi-server on WebSphere and WebLogic 5 directory servers IBM Tivoli Directory Server 55 Novell eDirectory 53 Oracle Internet Directory 54 Sun Java System Directory Server 52 Windows Active Directory 51 Windows AD LDS 52 DNS forwarder 51 documentation server installing 121 domain 119
D
data sources ODBC for Process Engine 80 database configuring automatic transaction processing (Oracle) 89 creating 86, 98 creating (DB2) 101 dedicated (DB2 for z/OS) 96 dedicated (DB2) 99 dedicated (Oracle) 82 dedicated (SQLServer) 72 environment variables (Oracle) 89 GCD (DB2) 104 GCD (Oracle) 86, 194 GCD (SQL Server) 75, 194 Global Configuration Data (GCD) DB2 193 installing (Oracle) 82 installing and configuring (SQL Server) 74 object store (Oracle) 87 object store (SQL Server) 75 Process Engine 102 Process Engine (SQL Server) 75 Process Engine tablespaces (Oracle) 87 shared (DB2 for z/OS) 96 shared (DB2) 99 shared (Oracle) 82 shared (SQL Server) 72 storage area 41 verifying connection 106 database accounts creating 66 database connection verifying connection for Oracle 106 verifying for DB2 107 verifying for SQL Server 108 DB2 cataloging Process Engine node 105 client 105 creating Process Engine database alias 106 dedicated database 99 install for FileNet P8 platform 100 installing 101 JDBC drivers 110, 114, 116 JDBC drivers, WebLogic 206 JDBC drivers, WebSphere 209 page size 98, 101 shared database 99 WebLogic 114 WebSphere 116 DB2 client installing 105
52
C
Configuration Manager setting permissions for user 113, 206 configurations Baseline with options 2 demo 3 developer 3 sample 1 Configure Windows servers 37 Content Engine 98 classes and properties 237 configure WebSphere 203 configuring JDBC datasource before upgrades 194 configuring remote access protocol 46 configuring UNIX 160 configuring Windows 38, 175 deployment on multiple servers 113, 206 primary administrative user name 113, 206 remote file access protocols 43 WebSphere 111, 203 WebSphere environment variables 111, 204 Content Search Engine configuring HP-UX 162 configuring UNIX 161 configuring Windows 177 Copyright IBM Corp. 2001, 2009
E
encrypted NTFS devices 41 Encryption products for storage 41 Enterprise Manager configuring Windows 37, 175 extensible authentication ports 227
F
file storage area configuring 43 defined 41 Fix Packs and Test Fixes minimum level required fixed storage area 41
151
G
GCD creating for upgrades from 3.5 GCD (SQL Server) database creating 75 193
255
H
host file 163, 176 hostname 26, 39, 163, 176 hosts file 26, 39
N
network configuring for FileNet P8 components 178 network name 26, 39, 163, 176 Novell eDirectory 53
I
IBM Encryption expert 41 IBM Tivoli Directory Server 55 installation ASA tasks 108 DBA tasks 64 ITA tasks 11 planning 1, 123 planning and preparing 1 SA tasks 47 installation and upgrade worksheet 8, 155 iPlanet, see Sun Java System Directory Server 52 IPv4 26, 39 IPv6 26, 39 ITA installation tasks 11 upgrade tasks 158
O
Object Request Broker (ORB) Windows-based PE Clients 176 Windows-based Process Engine clients 39 Object Request Broker(ORB) application server-based PE clients 121 object store DB2 database 104 object store (SQL Server ) database creating 75 ODBC data source for Process Engine 195 operating system accounts creating 15 Oracle character sets 85 client install 95 dedicated database 82 install for Content Engine 82 install for FileNet P8 platform 83 install for Process Engine 82 installing for FileNet P8 components 84 JDBC drivers WebLogic 114 JDBC drivers, WebLogic 206 preparing for FileNet P8 component upgrades 191 shared database 82 Oracle client installing 95 Oracle Internet Directory 54
Process Engine (continued) time zone settings 30, 168 Process Engine (AIX) configuring 27, 164 kernel limits 27, 165 Process Engine (HP-UX) collecting kernel parameters 168 configuring 29, 166 configuring kernel parameters 167 kernel limits 30 performing symbolic links 166 symbolic links 29 Process Engine (Solaris 10) configuring kernel parameters 171 kernel limits 33 Process Engine (Solaris 9) configuring kernel parameters 170 kernel limits 33 Process Engine (Solaris) configuring 169 Process Engine database tempdb (SQL Server) 75 Process Engine tablespaces DB2 database 102 profile 111, 203
J
JBoss configure for Content Engine 116, 209 configuring clusters 119 JBoss Application Server configuring for Application Engine 120 configuring for Workplace XT 120 JDBC distributed transaction components configuring 76 JDBC drivers 110, 116, 204, 209 install for DB2 114, 116 install for SQL Server 114 WebLogic 114 install for Oracle 114 WebLogic, install for DB2 206 WebLogic, install for Oracle 206 WebLogic, install for SQL Server 206 WebSphere 116 install for DB2 110 WebSphere, install for DB2 209
R
realm 47 Content Engine AllRealms property 239 Content Engine MyRealm property 239 Content Engine Realm class roles definition of installation 6 definition of upgrade 154
238
S
SA installation tasks 47 upgrade tasks 181 security install considerations 47, 181 specify accounts 55 Single Sign-On 47 SQL scripts running manually 77 SQL scripts (Oracle) changes made by 93, 94 changing default passwords 94 overview 92 running 90 running manually 91, 94, 95 SQL scripts (SQL Server) editing 78 modifying user names and passwords 79 overview 78 running 76 running manually 79 SQL Server client for Process Engine 80 dedicated database 72 install for Content Engine 72
P
P8A upgrade tasks 213 password complexity (Oracle) 90 ports 227 Process Engine 98 configuring AIX 27 configuring HP-UX 28 configuring Solaris 31 configuring UNIX 25, 162 configuring UNIX servers 25 configuring Windows 38, 175 database accounts, creating 66 enable port 32771 169 enable port 32777 32 installing SQL Server client software for upgrades 196 operating system accounts, creating 15 preparing for upgrades 180 preparing SQL Server for upgrades 195
K
Kerberos 47
L
LANG settings Solaris Process Engine 32 Solaris Process Engine install load balancer 163 load balancer name 176 170
256
SQL Server (continued) install for FileNet P8 platform 73 install for Process Engine 72, 73 installing patches before upgrades 197 JDBC drivers 114 JDBC drivers, WebLogic 206 shared database 72 WebLogic 114 SQL Server client installing 81 SSO Kerberos 47 planning considerations 47 requirements 47 Storage areas 41 Sun Java System Directory Server 52 setting resource limits for directory server 53 setting resource limits for users 53 Sun ONE, see Sun Java System Directory Server 52 synchronizing time and date 179
upgrade scenario upgrading Application Engine first 125 upgrading Content Engine first 134 upgrading Process Engine first 143 upgrading Workplace XT first 125 upgrade tasks P8A 213 upgrading automatic Content Engine upgrade 150
V
verify TCP/IP settings Vormetrics 41 38, 175
W
WebLogic configure for Content Engine 114 WebLogic Server configuring for Application Engine 119 configuring for Workplace XT 119 WebSphere configure for Content Engine 110, 203 configuring for Application Engine 119 configuring for Workplace XT 119 primary administrative user name 113, 206 WebSphere profile for Content Engine 111, 203 Windows configuring for FileNet P8 components 173, 174 Windows 2008 inbound rules 38, 176 Windows Active Directory 51 Windows AD LDS 52 Workplace avoid logon failures in multi-forest domains 114, 206 Workplace XT configuring Linux 173 worksheet autofiltering and sorting 10, 157 running the customize macro 9, 156 using the installation and upgrade worksheet 8, 155
T
time mask Solaris Process Engine 32, 170
U
UNIX configuring for FileNet P8 components 23, 160 update PE 3.5 applications 213 upgrade ASA tasks 197 DBA tasks 189 from 3.5 or 4 124 ITA tasks 158 overview 123 planning and preparing 123 planning considerations 150 SA tasks 181 staged from 4.0 124 Upgrade Content Engine resolve classes and properties 237 upgrade application server all platforms 198 Content Engine multi-server on JBoss 199 Content Engine multi-server on WebSphere and WebLogic 199 from 3.5 198 from 3.5 for Content Engine 203 JBoss clusters 212 JVM considerations 199 strengthening Content Engine for JBoss security 212 upgrade expansion products 152 Content Federation Services 153 FileNet P8 eForms 153 Records Manager 153 upgrade independent software vendor products 153
X
XA transactions enabling 75
Index
257
258
Program Number: 5724-R76 5724-R81
GC19-2801-00

Plan and Prepare

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Plan and Prepare

Enviado por

Direitos autorais:

Formatos disponíveis

IBM FileNet P8

Plan and Prepare Your Environment for IBM FileNet P8

Plan and Prepare Your Environment for IBM FileNet P8

Planning and preparing for IBM FileNet P8 installation . . . . . . . . . . . . 1

Copyright IBM Corp. 2001, 2009

Planning and preparing for IBM FileNet P8 Platform upgrade . . . . . 123

Planning for IBM FileNet P8

175 175 177 178 178 178

Updating Process Engine 3.5 customer applications . . . . . . . . . .

Appendix A. Installing IBM FileNet P8 Platform in a non-English environment . . . . . . . . . . . . 215

Appendix B. IBM FileNet P8 ports

Appendix C. New Content Engine classes and properties . . . . . . . 237

Planning for IBM FileNet P8

ibm.com and related resources

Support and assistance

Product Documentation for FileNet http://www.ibm.com/support/docview.wss?rs=3278 P8 Platform &uid=swg27010422

How to send your comments

Copyright IBM Corp. 2001, 2009

Planning for IBM FileNet P8

Planning and preparing for IBM FileNet P8 installation

Planning the installation

FileNet P8 Platform sample architecture

Baseline configuration with expansion components

External client workstation

Process Engine server

Documentation server Content Engine server

Enterprise Manager workstation Client workstation

Application Engine or Workplace XT servers

File storage server

Content Search Engine server Database server

Figure 1. Baseline configuration with expansion components

Sample development architecture

Planning for IBM FileNet P8

Sample demonstration architecture

Planning your deployment

Planning Content Engine deployment

Multi-instance single-server deployment

Planning and preparing for IBM FileNet P8 installation

Application server planning considerations

Planning for IBM FileNet P8

Definition of installation roles

Information technology administrator

Planning for IBM FileNet P8

Application server administrator

IBM FileNet P8 administrator

Planning and preparing for IBM FileNet P8 installation

Using the installation and upgrade worksheet

Planning for IBM FileNet P8

Running the Customize Worksheet macro

Autofiltering and sorting the Worksheet

Planning and preparing for IBM FileNet P8 installation

Performing the required installation preparation tasks

Planning for IBM FileNet P8

IT administrator installation tasks

Creating Content Engine operating system accounts

Create the following users and groups:

Planning for IBM FileNet P8

User or group name Content Engine Installer (Windows): ce_install_user

Content Engine Installer: (UNIX): ce_install_user

Planning and preparing for IBM FileNet P8 installation

Planning for IBM FileNet P8

User or group name Content Engine Operating System user: ce_os_user

Creating Process Engine operating system accounts