Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

Transcription

1 Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss Version 5.3 SP5 May, 2007

2 Copyright EMC Corporation. All rights reserved.

3 Table of Contents Preface... 5 Chapter 1 Creating the Database... 7 System Requirements... 7 Creating the Microsoft SQL Server Database... 8 Creating the Oracle Database Creating the DB2 Database Creating the Sybase Database Chapter 2 Installing the BPA/BAM Server Business Process Analyzer Server System Requirements Business Activity Monitor Server System Requirements Additional Requirements For Oracle For Sybase Installing the BPA/BAM Server Chapter 3 Installing the BPA/BAM Client BPA/BAM Client System Requirements Installing the BPA/BAM Client Logging in to the BPA/BAM Client Technical Support Contact Information Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 3

4 Table of Contents List of Tables Table 1 1. Business Process Analyzer and Business Activity Monitor System Requirements... 7 Table 1 2. Additional System Requirements for BAM... 8 Table 1 3. Microsoft SQL Server Parameters... 8 Table 1 4. Oracle Parameters Table 1 5. DB2 Parameters Table 2 1. Business Process Analyzer Server System Requirements Table 2 2. Business Activity Monitoring Server System Requirements Table 3 1. BPA/BAM Client System Requirements Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

5 Preface Purpose of the manual This manual contains information and instructions you need to install the Documentum Business Process Analyzer (BPA) and Business Activity Monitor (BAM) database, Server, and Client applications. It describes decisions you must make and requirements that must be met before you install the products. Intended audience This manual is intended for the person installing the BPA/BAM software. Typically, a system administrator installs the software. Revision history This section contains a description of this document s revision history. Revision history Revision Date May 2007 Description Release 5.3 SP5 Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 5

6 Preface 6 Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

7 Chapter 1 Creating the Database This chapter discusses preparing the database so that you can install the Business Process Analyzer and the Business Activity Monitor. The following databases are supported: Oracle (BPA and BAM) Microsoft SQL Server (BPA and BAM) DB2 (BPA and BAM) Sybase (BPA Only) System Requirements Table 1-1. Business Process Analyzer and Business Activity Monitor System Requirements Database Versions MS SQL Server 2000 Professional and Standard Editions and Enterprise Edition Oracle 9i Enterprise Edition Oracle 10g Enterprise Edition DB2 8.2 Enterprise Edition DB2 9.0 Enterprise Edition Platform Memory Network Sybase SQL Anywhere (BPA Only) Any platform supported by Microsoft SQL Server, Oracle, DB2, and Sybase. At least 512 MB of memory required, although 1 GB or more recommended Network card that supports TCP/IP Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 7

8 Creating the Database Disk Space Operating System 1 GB of hard disk space required Any operating system supported by the selected database. Table 1-2. Additional System Requirements for BAM Database Sizing Connectivity Bandwidth and Firewall The size of the Business Activity Monitoring database depends on the number of processes to be monitored, their frequency of execution, the amount of business data being tracked, and the period of time to retain the data (before it is purged). Database access uses JDBC over TCP/IP The default BAM connection to the BPM Audit Trail database does not run across firewalls. The preferred way to connect to this database is a LAN. For remote connections, a T1 link may be used. Performance will depend on the amount of data to be monitored. Creating the Microsoft SQL Server Database This section guides you in creating the required MS SQL schema. To ensure best performance, use the following initialization parameters for the BPA/BAM schema. Table 1-3. Microsoft SQL Server Parameters Parameter name Value Security Connections SQL Server And Windows Authentication Query Time-Out = 0 (unlimited) Maximum Concurrent User connections = 0 (unlimited) Attributes Close cursor on Commit = V (enable) ANSI Warning = V (enable) ANSI padding = V (enable) ANSI nulls = V (enable) 8 Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

9 Creating the Database Parameter name Value Autostart policies when the operating system starts Network Server Collation Autostart SQL Server (enable) Autostart SQL Server Agent (enable) Autostart MSDTC (enable) Named Pipes TCP/IP Note: If the Server is running on Windows 2003 operating system, use TCP/IP. Case sensitive Before running the database installation script you must complete the following steps: 1. Create a new database. a. Use PROACT (recommended) as the database name. b. Set the data file size to 500 MB. c. Set the transaction log size to 100 MB. 2. Create a new Login. a. Create a new login for the server. b. Use PROACT as the login name. c. Use Microsoft SQL Server authentication and set password to be the same as the login name. 3. Create a new user of the database with a user name of PROACT. 4. Associate the role db owner with the PROACT user in the new database. 5. After completing these steps, run the database creation script provided with the installation files. 6. Create the BPA/BAM schema by following the instructions in ReadMe_MS.txt. The ReadMe is located within DB\MS SQL\Create Database Scripts. Note: When you install the MS SQL Server database for BPA/BAM, you must select a case sensitive Collation name. BPA/BAM will not function with a database using case insensitive collation. This is because the Documentum Docbase Repository database uses case-sensitive collation. Note: When you create the schema, you must be connected with a User that has the System Administrator role to the database. The owner of all entities must be dbo. Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 9

10 Creating the Database Creating the Oracle Database This section guides you in creating the required Oracle schema. Before running the database installation script, you must perform the following steps: 1. Verify that the Oracle server is installed and is running. 2. Create the new Oracle schema, using PROACT as the schema name and set the following parameters: DB_BLOCK_SIZE to 8,192 User table space to 500 MB System table space to 100 MB Rollback table space to 200 MB Temp table space to 50 MB Index table space to 50 MB 3. Initialize schema parameters using the Oracle Settings table found at the end of this section. 4. Create a new Oracle user and password pair with the same value. For example, use PROACT/PROACT. 5. Grant the following access to the new user: For Oracle 9i databases: Grant CONNECT Grant RESOURCE For Oracle 10g databases: Grant CONNECT Grant RESOURCE Grant CREATE VIEW 6. After completing these steps, run the database creation script provided with the installation files. Instructions for running the database scripts are available in ReadMe_Or.txt located in DB\Oracle\Create Database Scripts. Table 1-4. Oracle Parameters Parameter Name Value when server s RAM < 512 MB Value when server s RAM > 512 MB Comment DB_BLOCK_SIZE 8,192 8,192 Must be set during schema creation DB_BLOCK_BUFFERS , Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

11 Creating the Database Parameter Name Value when server s RAM < 512 MB Value when server s RAM > 512 MB OPTIMIZER_MODE CHOOSE CHOOSE SHARED_POOL_SIZE 20,000,000 50,000,000 LOG_CHECKPOINT_ INTERVAL 0 0 DML_LOCKS 1,000 1,000 PROCESSES LOG_BUFFER 327, ,360 ROW_CACHE_ CURSORS OPEN_CURSORS 1,000 2,000 SORT_AREA_SIZE 2,000,000 5,000,000 MAX_DUMP_FILE_SIZE 10,240 10,240 Comment Tip: This setting is crucial. DB_FILES Operating system dependent DB_WRITERS 4 10 CHECKPOINT_ PROCESS TRUE TRUE Can ALTER SYSTEM: FALSE TIMED_STATISTICS TRUE TRUE Obsoleted: FALSE Note: It is recommended that the database administrator periodically monitor the database and modify the parameters based on size changes. Creating the DB2 Database Prior to running the database installation script you must do the following: Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 11

12 Creating the Database Table 1-5. DB2 Parameters Step 1. Verify that the DB2 Server is installed 2. Create a new database by using the Control Center. By default, three tablespaces will be created system, user, and temporary each with a page size equal to 4 KB. In addition, a default pool will be created with a page size of 4 KB. 3. Add two buffer pools. The first buffer pool must support page size 16 KB. Comments Verify you have DB2 server installed, up and running. Example: CREATE DATABASE BPA61 ON 'C:' USING CODESET UTF-8 TERRITORY US COLLATE USING SYSTEM CATALOG TABLESPACE MANAGED BY SYSTEM USING ( 'C:\DB2\BPA61\catalog_tables' ) EXTENTSIZE 16 PREFETCHSIZE 16 OVERHEAD TRANSFERRATE 0.14 USER TABLESPACE MANAGED BY SYSTEM USING ( 'C:\DB2\BPA61\user_tbs_4kb' ) EXTENTSIZE 16 PREFETCHSIZE 16 OVERHEAD TRANSFERRATE 0.14 TEMPORARY TABLESPACE MANAGED BY SYSTEM USING ( 'C:\DB2\BPA61\temp_tbs_4kb' ) EXTENTSIZE 16 PREFETCHSIZE 16 OVERHEAD TRANSFERRATE 0.14@ Example: CREATE BUFFERPOOL POOL16 IMMEDIATE SIZE 250 PAGESIZE 16 name=pool16 (this can be changed) SIZE = 250 (this can be changed) page size = 16K (this cannot be changed) The second buffer pool must support 32 KB. name=pool32 (this can be changed) SIZE = 250 (this can be changed) page size = 32K (this cannot be changed) 12 Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

13 Creating the Database 4. Create 2 new User Tablespaces with page size 16 KB and 32 KB. 5. Create a new User Temporary Tablespace with page size 4 KB. 6. Create a new System Temporary Tablespace with page size 32 KB. CREATE REGULAR TABLESPACE USER_TBS_16 PAGESIZE 16 K MANAGED BY SYSTEM USING ('C:\DB2\BPA61\user_tbs_16kb' ) EXTENTSIZE 4 OVERHEAD 10.5 PREFETCHSIZE 4 TRANSFERRATE 0.14 BUFFERPOOL CREATE REGULAR TABLESPACE USER_TBS_32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('C:\DB2\BPA61\user_tbs_32kb' ) EXTENTSIZE 4 OVERHEAD 10.5 PREFETCHSIZE 4 TRANSFERRATE 0.14 BUFFERPOOL CREATE USER TEMPORARY TABLESPACE USER_TMP_4 PAGESIZE 4 K MANAGED BY SYSTEM USING ('C:\DB2\BPA61\user_temp_tbs_4kb' ) EXTENTSIZE 4 OVERHEAD 10.5 PREFETCHSIZE 4 TRANSFERRATE 0.14 BUFFERPOOL CREATE SYSTEM TEMPORARY TABLESPACE TEMPSPACE_32 PAGESIZE 32 K MANAGED BY SYSTEM USING ('C:\DB2\BPA61\temp_ tbs_32kb' ) EXTENTSIZE 4 OVERHEAD 10.5 PREFETCHSIZE 4 TRANSFERRATE 0.14 BUFFERPOOL 7. Create a new user in the operating system. Then add this user to the list of Database Users. 8. Grant the following authorization to the new user: - connect to database - create tables - create schemas implicitly - create external routines - register routines to execute in database manager s process In addition, grant the use of the User Tablespaces with the 4 KB and 16 KB page sizes and User Temporary Tablespace with page size 4 KB. Example: GRANT CREATETAB,CONNECT, CREATE_NOT_FENCED_ROUTINE,IMPLICIT_ SCHEMA, CREATE_EXTERNAL_ROUTINE ON DATABASE TO USER ALEX@ GRANT USE OF TABLESPACE USERSPACE1 TO USER Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 13

14 Creating the Database 9. Define the JDK_PATH for the instance. 10. Update SQL statement heap (STMTHEAP) to be equal to at least In Control Center right-click the instance you are working with and select Configure Parameters. Example: db2 update db cfg using STMTHEAP Note: After completing these steps, run the database creation script provided with the installation files. Instructions for running the database scripts are available in ReadMe_DB2.txt located in DB\DB2\Create Database Scripts. Creating the Sybase Database This section guides you in installing an empty Sybase database. 1. Create a Databases folder at the C:\ root directory. This folder will hold the database file. This folder can actually exist anywhere on the hard drive. 2. Browse the installation files to the following folder: DB\Sybase\Databases \Empty. 3. From within the Empty folder copy the proact.db file to the Databases folder you created in Step Run the database using Adaptive Server Anywhere dbserv8.exe. 14 Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

15 Installing the BPA/BAM Server Chapter 2 This chapter discusses the following topics: System requirements for installing the Business Process Analyzer Server System requirements for installing the Business Activity Monitor Server Installing the BPA/BAM Server Business Process Analyzer Server System Requirements Table 2-1. Business Process Analyzer Server System Requirements Platform IBM PC or compatible with Pentium 4, 2.4 GHz processor required, although Pentium 4, 3.0 GHz processor or higher recommended Memory Network Disk Space Operating Systems At least 1 GB of memory required. The following rules apply for the amount of memory required: 1-20 concurrent users: 1 GB 20 or more concurrent users: consult with technical support Network card that supports TCP/IP 1.5 GB of hard disk space required Windows 2000 Server, Windows 2003 Server, Windows 2000 Professional, Windows XP Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 15

16 Installing the BPA/BAM Server Business Activity Monitor Server System Requirements Table 2-2. Business Activity Monitoring Server System Requirements Platform Memory Network Disk Space Connection Operating Systems IBM PC or compatible with Pentium 4, 2.4 GHz processor required, although Pentium 4, 3.0 GHz processor or higher recommended At least 1 GB of memory required, although 2 GB or more recommended. The following rules apply for the amount of memory required: Up to 100 instances per hour: 1 GB 20 or more concurrent users: consult with technical support Network card that supports TCP/IP 80 GB of hard disk space required 1.5 GHz for application 2.4 GHz processor The connections between Documentum BPM and BAM requires use of a high-speed LAN Windows 2000 Server, Windows 2003 Server, Windows 2000 Professional, Windows XP Additional Requirements For Oracle 1. JAVA Run Time Environment (JRE) is installed as part of the Server installation. It does not need to be installed separately. 2. For the installation of the BPA/BAM Server, the Database Server Host name, SID, User Name, and Password are required. 3. The installation of the Server cannot be completed without the database installed and running. It is recommended that the BPA/BAM Server not be installed on the 16 Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

17 Installing the BPA/BAM Server database server; therefore there must be access from the installation machine to the database via TCP/IP connection. 4. The BPA/BAM Server does not require the Oracle Client for its operations. The Server uses Oracle s JDBC native driver for database operations. For more information, please refer to the Oracle documentation dealing with Oracle Client and Server installations. For Sybase 1. JAVA Run Time Environment (JRE) is installed as part of the Server installation. It does not need to be installed separately. 2. For the installation of the BPA Server, the Database Server Host Name, Sybase Engine Name, User Name, and Password are required. 3. The installation of the Server cannot be completed without the database installed and running. It is recommended that the BPA Server not be installed on the database server; therefore there must be access from the installation machine to the database via TCP/IP connection. 4. The BPA Server does not require the ASA Client for its operations. The Server uses ASA s JDBC native driver (JCONNECT) for database operations. For more information, please refer to the ASA documentation dealing with ASA Client and Server installations. Installing the BPA/BAM Server The BPA/BAM Server runs over the JBoss application server. It supports connections from many users at a time over a network. The Server runs on one computer (the server machine), while Client applications run on other computers (client machines). The installation of the Server cannot be completed without the database installed and running. It is recommended that the application server not be installed on the database server; therefore there must be access from the installation machine to the database server using TCP/IP connection. 1. From the installation files, open the Setup\suite\disk1 folder and select setupwin32.exe. It may take up to a minute for the first installation panel to appear. Note: For network installations make sure you use a mapped drive to start the installation. The installation program will NOT run if using network URL notation (e.g. use M:\ProcessAnalyzerInstall and not \\NETDOMAIN\PUBLIC\ProcessAnalyzerInstall). Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 17

18 Installing the BPA/BAM Server For Windows 2000 and/or Citrix installations, use Add/Remove in the control panel. 2. Click Next on the Welcome screen. 3. Read the License Agreement and then click Next. The Next button will not activate unless you accept the terms of the license agreement. 4. Enter the path to the installation directory. Either accept the default or click Browse to choose (or create) a folder to hold the installation files. 5. Click Next. The Shortcut/Icon window appears. 6. Select the shortcuts or icons that you want to install on your computer. 7. Click Next. The Group Name window appears. 8. Select the Process Analyzer Server and the Process Analyzer Server Administration Utility checkboxes. 9. Click Next. The Product Installation window appears. 10. Enter the serial number and license key provided to you. Then, click Next Note: The serial number and license key combination is case sensitive. 11. Enter the database connection parameters. Note: You must obtain these parameters from your DBA. The Server uses these parameters to connect to the database. The installation verifies that the host name is valid and accessible, if not, a warning box appears requesting that you re-type the correct host name. 12. Examine the Confirmation window to ensure that your parameters are correct. 13. Click Next to begin copying the files. The status bar will show progress on each of the software components that you have selected to install. 18 Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

19 Installing the BPA/BAM Client Chapter 3 This chapter discusses the following topics: System requirements for installing the BPA/BAM Client Installing the BPA/BAM Client Logging in to the BPA/BAM Client BPA/BAM Client System Requirements Table 3-1. BPA/BAM Client System Requirements Platform IBM PC or compatible with Pentium III 500 processor, although Pentium III 800 or higher recommended Memory Network Disk Space Operating system For BPA: 256 MB of memory For BAM: 1 GB of memory Network card that supports TCP/IP and network access to the Server Account For BPA: 300 MB of space For BAM: 1 GB of space Windows XP, Windows 2000 Professional, Windows 2000 Server, or Windows 2003 The host name of the Server is also required. In addition, JAVA Run Time Environment (JRE) is installed as part of the Client installation. It should not be installed separately. Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 19

20 Installing the BPA/BAM Client Installing the BPA/BAM Client 1. From the installation files, open the Setup\suite\disk1 folder and select setupwin32.exe. It may take up to a minute for the first installation panel to appear. Note: For network installations make sure you use a mapped drive to start the installation. The installation program will NOT run if using network URL notation (e.g. use M:\Process AnalyzerInstall and not \\NETDOMAIN\PUBLIC\Process AnalyzerInstall). For Windows 2000 and/or Citrix installations, use Add/Remove in the control panel. 2. Click Next on the Welcome screen. 3. Read and accept the License Agreement and then click Next. The Next button will not activate unless you accept the terms of the license agreement. 4. After clicking Next the Destination Directory window appears. Either accept the default or click Browse to choose (or create) a folder to hold the installation files. 5. Click Next. 6. After selecting a destination directory, the Shortcut/Icon window appears. Either accept the default selection or make a change. Click Next to continue. 7. Accept the default group name or type a new one and click Next. 8. Select the Process Analyzer Client checkbox and click Next. 9. Enter the Client connection parameters, including the Server host and port. You can leave the user name and password field blank. 10. Click Next. A Confirmation window appears. 11. In the Confirmation window, click Back to make changes or click Next to start the installation. 12. Click Finish when the progress window finishes with the install. Logging in to the BPA/BAM Client To log into the Client, perform the steps below. These instructions assume that the database is not yet running 1. Start the Database. 2. Start the Server. 3. Click the Client icon located on your desktop. 20 Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss

21 Installing the BPA/BAM Client 4. Enter the following default log in parameters: Default log in name: SYS Default password: ADM Note: The login name and password are case sensitive. Technical Support Contact Information If you have questions or issues please access the following support as necessary: Call the toll free support hotline at (Please select Option #2 for Content Management including ProActivity). Send an to Documentum Business Process Analyzer and Business Activity Monitor Installation Guide for JBoss 21