Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Extensible Storage Engine wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Relational model wikipedia , lookup
Microsoft SQL Server wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Database model wikipedia , lookup
Clusterpoint wikipedia , lookup
IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle 9i-based installations Contents Section 1. Content Management Overview Section 2. Content Management Component Needs 2.1 ECM V8.3 Library Server Database Needs Document By Burt Vialpando Edited by Steven Soria, Raghuram Tadipatri With Contributions By: Nick Puz, Francisco Bermudez and Hari Sanghvi IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 2.2 ECM V8.3 Resource Manager Database & Application Needs 2.3 ECM V8.3 System Administration Client Needs 2.4 Optional Install Items Section 3. Content Management Setup Needs 3.1 Installation Steps 3.2 ECM V8.3 Library Server Database Setup Issues 3.3 ECM V8.3 Resource Manager Database Setup Issues 3.4 ECM V8.3 Resource Manager Application Server Setup Issues 3.5 ECM V8.3 System Administration Client Setup Issues 3.6 ECM V8.3 Information Integrator for Content System Administration Database 3.7 ECM V8.3 Information Integrator for Content System Administration Client Section 4. Content Management Install Needs – Oracle Specific 4.1 Windows – ECM Install Issues 4.2 Windows – Information Integrator for Content Install Issues 4.3 AIX – ECM Install Issues (similar to Solaris, and Linux) Section 5. Oracle Install Suggestions 5.1 For All Operating Systems 5.2 Windows Specific Suggestions – Oracle Install 5.3 AIX Specific Suggestions – Oracle Install (similar to Solaris and Linux) Section 6. Content Management Administration Issues 6.1 Remote Connections 6.2 Text Search Options 6.3 Resource Manager Utilities & Services – Environment Setup File 6.4 Optimizing Databases 6.5 Oracle Features Support 6.6 Customizing Table Spaces 6.7 Useful Links _____________________________________________________________________________________________________________ January 18, 2007 Page 2 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ Contents - continued Section 7. Appendix 7.1 Library Server Database init.ora Detailed Usage 7.2 Library Server Database Creation Particulars 7.3 Resource Manager Database init.ora Detailed Usage 7.4 Resource Manager Database Creation Particulars 7.5 References _____________________________________________________________________________________________________________ January 18, 2007 Page 3 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 1. IBM DB2 Content Manager product overview 1.1. Purpose of this document This document is a supplement to Planning and Installing Your Content Management System. It is intended to pull together Oracle® information from the installation guide and provide common tips to assist with the installation and configuration of DB2® Content Manager with Oracle 9i Database Release 2 Enterprise Edition. You should be familiar with DB2 Content Manager concepts and terminology as described in the installation guide. Additionally, you must be familiar with all of the Oracle 9i database concepts discussed in this document including, but not limited to, the following concepts: • Oracle 9i database setup and configuration on operating systems supported by DB2 Content Manager • Oracle Client and Oracle database server concepts and configurations • The Oracle Listener, Oracle Net, and TNSNAMES • Oracle external routines and configuration See your Oracle 9i database documentation for information about these topics. _____________________________________________________________________________________________________________ January 18, 2007 Page 4 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 1.2. DB2 Content Manager product support for Oracle database The following table lists recent DB2 Content Manager products and whether they include support for Oracle. Product Oracle support? IBM DB2 Content Manager Enterprise Edition V8.3 Yes IBM DB2 Content Manager iSeries™ V5.3 No IBM DB2 Content Manager for z/OS® V8.3 No IBM DB2 Content Manager OnDemand V8.3 Yes IBM DB2 Content Manager OnDemand for iSeries No IBM DB2 Content Manager OnDemand for z/OS IBM DB2 CommonStore for SAP V8.3 No Integrated with Enterprise Content Management (ECM) V8.3 Integrated with Enterprise Content Management V8.3 IBM DB2 CommonStore for Lotus Domino V8.3 Integrated with Enterprise Content Management V8.3 IBM DB2 Document Manager V8.3 Integrated with Enterprise Content Management V8.3 IBM DB2 CommonStore for Exchange Server V8.3 IBM Content Manager ImagePlus® for z/OS V8.2 No IBM DB2 Records Manager V4.1.1 Yes IBM Content Management for Message Monitoring and Retention n/a _____________________________________________________________________________________________________________ January 18, 2007 Page 5 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 2. IBM DB2 Content Manager component requirements 2.1. Enterprise Content Management (ECM) V8.3 library server database requirements The following table lists the requirements for the library server. Required: Component Database Operating system Optional: Text search C compiler (for user exit development only) DB2 DB2 Universal Database Enterprise Server Edition V8.1 or V8.2 with FixPak 7A special Windows®2, AIX®, Solaris, or Linux® DB2 Net Search Extender V8.2 Oracle Oracle Database Enterprise Edition V9.2.0.61 or V9.2.0.7 See Planning and Installing Your Content Management System for operating systemspecific support See Planning and Installing Your Content Management System for operating systemspecific support Windows2, AIX or Solaris Oracle Text Notes: 1. On Windows, Oracle V9.2.0.6 patchset 4 or later. On AIX or Solaris, Oracle V9.2.0.6 with Oracle patch 4168725. Oracle 10g is not supported. 2. In this instance, Windows refers to a “server” based Windows versions, not Windows XP, for example. 2.2. ECM V8.3 resource manager database and application server requirements The following table lists the requirements for the resource manager. Required: Component Database server (for resource manager database) Application Server Operating system Optional: Database client (If resource manager application & database on different machines) Long-term storage management HTTP Server DB2 DB2 Universal Database Enterprise Server Edition V8.1 or V8.2 with FixPak 7A special WebSphere® Application Server V5.1.1 Windows2, AIX, Solaris or Linux DB2 Run-Time Client V8.1 or V8.2 with FixPak 7a special Oracle Oracle Database Enterprise Edition V9.2.0.61 or V9.2.0.7 Tivoli® Storage Manager V5.2.2 IBM HTTP Server Tivoli Storage Manager V5.2.2 IBM HTTP Server WebSphere Application Server V5.1.1 Windows2, AIX or Solaris Oracle Client V9.2.0.6* or V9.2.0.7 (if using HTTP Secure Sockets Layer) _____________________________________________________________________________________________________________ January 18, 2007 Page 6 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ Notes: 1. On Windows, Oracle V9.2.0.6 patchset 4 or later. On AIX and Solaris, Oracle V9.2.0.6 with Oracle patch 4168725. Oracle 10g is not supported. 2. In this instance, Windows refers to a “server” based Windows versions, not Windows XP, for example. 2.3. ECM V8.3 system administration client requirements The following table lists the requirements for the system administration client. Component Required: Either Client for Windows1 Or eClient DB2 Windows 2003, Windows Server, Windows XP Oracle Windows 2003, Windows Server, Windows XP Microsoft® Internet Explorer, Netscape Navigator, Mozilla Microsoft Internet Explorer, Netscape Navigator, Mozilla 1 (On Windows , AIX or Solaris) e-Client Server DB2 Content Manager client Client property file Optional: Custom client LDAP DB2 Run-Time Client V8.1 or V8.2 with FixPak 7A special DB2 Content Manager client property file DB2 Content Manager client APIs LDAP (many supported versions) 1 (On Windows , AIX or Solaris) e-Client Server Oracle Client V9.2.0.62 or V9.2.0.7 DB2 Content Manager Client property file DB2 Content Manager client APIs LDAP (many supported versions) Notes: 1. Windows refers to any version of Windows. 2. On Windows, Oracle V9.2.0.6 patchset 4 or later. On AIX or Solaris, Oracle V9.2.0.6 with Oracle patch 4168725. Oracle 10g is not supported. 2.4. Optional installation items: • IBM DB2 Information Integrator for Content V8.3 • DB2 Content Management V8.3 Information Center (usually installed on a development server rather than a production server). _____________________________________________________________________________________________________________ January 18, 2007 Page 7 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 3. IBM DB2 Content Manager setup requirements 3.1. Basic steps in a DB2 Content Manager installation 1. Installation Assistant Tool for generating worksheets for you that help with your installation. Highly recommended, especially for Oracle users. 2. Installation Main installation process using the launchpad. Oracle users must click the Custom installation option. The Typical option only installs DB2. 3. Installation verification Utility to verify that DB2 Content Manager is installed successfully. 4. First Steps Component that allows you to load and experiment with sample data. _____________________________________________________________________________________________________________ January 18, 2007 Page 8 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 3.2. Install the DB2 Content Manager V8.3 library server When you complete the installation windows for installing the library server on Oracle, provide the values indicated in this table. Input Value Database type Administration user group Setting Oracle user Oracle home directory The default value is oracle. Change the value if different. Oracle The default value is dba. Change the value if different. The default value is: Windows: c:\program files\oracle\ora92 AIX: /usr/oraprod/product/9.2.0 Solaris: /opt/oracle/920server Change the value if different. Important: This value is case-sensitive on all operating systems. On Windows, it must match the exact value of ORACLE_HOME as it appears in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE] Oracle domain The installation supplies the fully qualified host name of the machine as the default. Change the value if different. Oracle database path The default value is: Windows: c:\oradata\<db name> AIX or Solaris: /oradata/<db name> Change the value if different. Oracle system password Provide the value. It is assigned to Oracle SYS and SYSTEM users and must be a valid Oracle password. Oracle listener name The default value is <db name>_LISTENER. Change the value if different. The listener that you specify must already exist and be active. Oracle table space names If DB2 Content Manager creates the database for you, you do not see this prompt. If using an existing schema, the installation prompts for table space names. These names must match default values as documented in the Customize Oracle table space parameters section of the installation guide. Specifying non-default values causes unknown behavior and is not supported at this time. Oracle port Mirror database directory The default value is 1521. Change the value if different. The default value is: Windows: c:\oradata\mirror AIX or Solaris: /oradata/mirror Change the value if different. _____________________________________________________________________________________________________________ January 18, 2007 Page 9 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 3.3. Install the DB2 Content Manager V8.3 resource manager database When you complete installing the resource manager on Oracle, provide the values indicated in this table. Input Value Database type Administration user group Setting Oracle user The default value is oracle. Change the value if different. Oracle home directory The default value is: Windows: c:\program files\oracle\ora92 AIX: /usr/oraprod/product/9.2.0 Solaris: /opt/oracle/920server Change the value if different. Oracle domain The installation supplies the fully qualified host name of the machine as the default value. Change the value if different. Oracle database path The default value is: Windows: c:\oradata\<db name> AIX or Solaris: /oradata/<db name> Change the value if different. Oracle system password Provide the value. It is assigned to Oracle SYS and SYSTEM users and must be a valid Oracle password. Oracle listener name The default value is <db name>_LISTENER. Change the value if different. The listener that you specify must already exist and be running. Oracle table space names If DB2 Content Manager creates the database for you, you do not see this prompt. If using an existing schema, the installation prompts for table space names. These names must match default values as documented in the Customize Oracle table space parameters section of the installation guide. Specifying non-default values cause unknown behavior and is not supported at this time. The default value is 1521. Change the value if different. Oracle port Mirror database directory Oracle The default value is dba. Change the value if different. The default value is Windows: c:\oradata\mirror UNIX: /oradata/mirror Change the value if different. _____________________________________________________________________________________________________________ January 18, 2007 Page 10 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 3.4. Install the DB2 Content Manager resource manager application The resource manager application server setup might require the following special input values for Oracle if installed on a different server than the resource manager database. Additionally, installation input values for the resource manager staging location should reflect the resource manager application machine. Staging is done on the application side, not the on the resource manager database server. For more information, consult the Configure resource manager options section of the installation guide. Input Value Setting Oracle home directory The default value is: Windows: c:\program files\oracle\ora92 AIX: /usr/oraprod/product/9.2.0 Solaris: /opt/oracle/920server Change the value if different. Resource manager database port The port on which the Oracle listener is listening for your resource manager database. The default value is 1521. Change the value if different. Resource manager database type Oracle 3.5. Install the DB2 Content Manager system administration client When you install the system administration client, provide these values for Oracle. Input Value Database type Oracle database port Setting Oracle The default value is 1521. Change the value if different. _____________________________________________________________________________________________________________ January 18, 2007 Page 11 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 3.6. Install the DB2 Information Integrator for Content system administration database When you install the DB2 Information Integrator for Content system administration database, provide these values for Oracle: Input Value Database type Administration user group Setting Oracle user The default value is oracle. Change the value if different. The default value is: Windows: c:\program files\oracle\ora92 AIX: /usr/oraprod/product/9.2.0 Solaris: /opt/oracle/920server Change the value if different. Important: This value is case-sensitive on all operating systems. On Windows, it must be the exact value of ORACLE_HOME as it appears in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE]. Oracle home directory Oracle The default value is dba. Change the value if different. Oracle domain The installation program supplies the fully-qualified host name of the machine as the default. Change the value if different. Oracle database path The default value is: Windows: c:\oradata\icmnlsdb UNIX®: /oradata/icmnlsdb Change the value if different. Oracle system password Provide the value that is assigned to Oracle SYS and SYSTEM users and must be a valid Oracle password] Oracle listener name The default value is <db name>_LISTENER Change the value if different. Oracle table space names [If DB2 Content Manager creates the database for you, you do not see this prompt. If using an existing schema, the installation prompts for table space names. These names must match default values as documented in the Customize Oracle table space parameters section of the installation guide. Specifying non-default values will cause unknown behavior and is not supported at this time. Oracle port The default value is 1521. Change the value if different. Mirror database directory The default value is: Windows: c:\oradata\mirror UNIX: /oradata/mirror Change the value if different. _____________________________________________________________________________________________________________ January 18, 2007 Page 12 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 3.7. Install the DB2 Information Integrator for Content system administration client When you complete the installation windows for installing the DB2 Information Integrator for Content system administration client, enter these values for Oracle: Input Value Database type Oracle database port Setting Oracle The default value is 1521. Change the value if different. _____________________________________________________________________________________________________________ January 18, 2007 Page 13 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 4. IBM DB2 Content Manager installation requirements: Oraclespecific Issues 4.1. Windows: ECM installation issues 4.1.1. Follow Oracle installation instructions to install the Oracle database server and Oracle client Check the Oracle compatibility matrix to ensure that the Oracle client level you are using is compatible with the version of Oracle server you are using for the library server and resource manager databases. 4.1.2. Verify that the Oracle software is configured correctly Your Oracle sqlnet.ora file (client and server) must include TNSNAMES in your NAMES.DIRECTORY_PATH. For successful database creation through the DB2 Content Manager installation, SQLNET.AUTHENTICATION_SERVICES must include NTS. This is because DB2 Content Manager does not require the use of an Oracle password file and uses connect / as SYSDBA to create the Oracle database. Use of NTS on Windows operating systems instructs Oracle to authenticate the currently logged on operating system user, verifying that the user is a member of the Oracle DBA operating system group (ORA_DBA). The following example shows a correctly configured sqlnet.ora file. Your actual file contents may be different. SQLNET.AUTHENTICATION_SERVICES=(NTS) NAMES.DIRECTORY_PATH=(TNSNAMES,ONAMES,HOSTNAME) If you do not normally use NTS authentication, you can remove the NTS setting only after your DB2 Content Manager databases have been successfully created and configured. For example, enter: SQLNET.AUTHENTICATION_SERVICES=(NONE) Additionally, ensure that your Oracle server tnsnames.ora and listener.ora files are configured for use with Oracle external routines (“extproc”). See your Oracle documentation for details. If there is an Oracle configuration error in this area, your library server configuration fails and DB2 Content Manager is not operational. _____________________________________________________________________________________________________________ January 18, 2007 Page 14 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ You want to configure tnsnames.ora with an entry to allow your Oracle library server database to be able to create stored procedures: EXTPROC_CONNECTION_DATA= (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0)) ) (CONNECT_DATA = (SID = PLSExtProc)(PRESENTATION = RO) ) ) 4.1.3. Verify Windows system environment variables Ensure that information similar to that in the following examples exists under System variables: Ensure that your ORACLE_HOME is set to the proper location, and: CLASSPATH=<ORACLE_HOME>\jdbc\lib\ojdbc14.jar;%CLASSPATH% PATH=<ORACLE_HOME>\bin;%PATH% LIB=<ORACLE_HOME>\lib;%LIB% 4.1.4. Verify that the users have the proper privileges DB2 Content Manager creates external operating system users (icmadmin, rmadmin, icmconct) for you if they don’t already exist. If you have created the users yourself, prior to DB2 Content Manager installation, you should verify that icmadmin and rmadmin have the proper rights (Control Panel > Administrative Tools > Local Security Policy). You should perform this check after installing DB2 Content Manager but before the runtime operation of DB2 Content Manager servers: • • • • • • 4.1.5. Be a part of the Oracle database administrators group “Act as part of the operating system” “Create a token object” “Increase or adjust quotas” “Replace process level token” "Log on as a Service" should be added for the library server and resource manager user IDs if created before running the installer. (The post-installation validation program fails if this is not done.) Remote communication If any of your DB2 Content Manager components are remotely communicating to the library server, ensure that the Oracle client (or server) and the Oracle JDBC® drivers are installed on the machine that communicates with the library server. Important: The tnsnames.ora file must be correctly configured for the remote library server before the DB2 Content Manager component products are installed. _____________________________________________________________________________________________________________ January 18, 2007 Page 15 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ For example, if your resource manager application is not on the same machine as either the library server or resource manager database, then the Oracle client must be installed on that machine and tnsnames.ora should have entries for both the library server and resource manager database. Additionally, all of the client DB2 Content Manager components, such as eClient, Client for Windows, and DB2 Information Integrator for Content, that do not reside with the library server or resource manager databases, require the Oracle client and the tnsnames.ora configuration for both databases. For example, your Oracle tnsnames.ora file might look similar to the following: # TNSNAMES.ORA Network Configuration File # Generated by Oracle configuration tools. ICMNLSDB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS=(PROTOCOL=TCP)(HOST=ls_host.ls_domain.com)(PORT=1521)) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = icmnlsdb.ls_domain.com) ) ) RMDB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS=(PROTOCOL=TCP)(HOST=rm_host.rm_domain.com)(PORT=1521)) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = rmdb.rm_domain.com) ) ) Note that the DB2 Content Manager installation and configuration tools use the Oracle JDBC thin driver to communicate with the library server and resource manager databases. DB2 Content Manager client applications, DB2 Information Integrator for Content connector API’s, and the resource manager application use the Oracle JDBC-OCI driver to communicate with the library server. The result is that during DB2 Content Manager installation and configuration, the database name you choose is mapped to the Oracle service name registered with the listener. If you are using an existing database, the database name you provide must match the service name for that database registered with the listener. This is because the Oracle thin driver bypasses TNSNAMES and communicates directly with the listener on the Oracle server. If you specify a TNSNAMES alias, or a database name other than the actual service name reported by the listener, the connection fails. _____________________________________________________________________________________________________________ January 18, 2007 Page 16 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ After DB2 Content Manager installation and configuration, if you decide to define a TNSNAMES alias on one of your client boxes, this alias must be used as the database name when configuring the DB2 Content Manager client to communicate with a remote library server. This is because the Oracle Call Interface (OCI)-JDBC driver uses TNSNAMES to look up database connection and listener information. If it cannot find the TNSNAMES alias you used, the connection fails. 4.1.6. Test your library server and resource manager connectivity Perform a basic “sanity check” of proper Oracle configuration by testing connectivity to your library server and resource manager database. From a command prompt window, type the following command: <ORACLE_HOME>\bin\sqlplus.exe <icmadmin>/<password>@<ls_dbname> where icmadmin = your library server administrator user ID password = your library server administrator password ls_dbname = the TNS alias you have defined for your library server database Do not set ORACLE_SID to test connectivity. Using the method above ensures your Oracle listener and TNSNAMES are communicating properly with one another. Setting ORACLE_SID bypasses TNSNAMES. Important: Do not rely on TNSPING to verify connectivity, because that only verifies that the instance is registered with the listener. You should perform this check from all machines that connect to the library server database such as clients, mid-tiers, and the resource manager application machine. If the resource manager application is on a different machine than your resource manager database, you should also perform this check against your resource manager database. 4.1.7. JDBC driver registration for the resource manager application Usually, the DB2 Content Manager installation performs this task. Follow the steps below as validation or troubleshooting steps only. 1) 2) 3) 4) 5) 6) Log on to WebSphere administrative console. Go to Resources > JDBC provider > new. Select Oracle JDBC Driver. Click OK. Set name: CM_Oracle_jdbc_driver. Set CLASSPATH to your Oracle JDBC driver path (ojdbc14.jar). For example, set it to: ORACLE_HOME\jdbc\lib\ojdbc14.jar. _____________________________________________________________________________________________________________ January 18, 2007 Page 17 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 7) Verify that the Implementation Classname is set to the following value (change it if it is not): oracle.jdbc.OracleDriver 8) When the Content Manager installer creates the CM_Oracle_jdbc_driver, it does so with this setting: ${ORACLE_JDBC_DRIVER_PATH}/ojdbc14.jar So, check the default ORACLE_JDBC_DRIVER_PATH in the WebSphere environment variable to make sure this is set appropriately. 4.2. Windows: DB2 Information Integrator for Content installation issues 4.2.1. DB2 Content Manager library server connector window Make sure you select Oracle as the database type for the library server. Doing this updates these files: cmbicmsrvs.ini & cmbicmenv.ini in your <IBMCMROOT>\cmgmt\connectors directory for Windows, or your <CM Admin Home Dir>/cmgmt/connectors directory for AIX or Solaris. 4.2.2. Federated connector or system administration client window Ensure that you select Oracle as database type for the library server. Doing this updates the cmbds.ini file in your <IBMCMROOT>\cmgmt\connectors directory for Windows, or your <CM Admin Home Dir>/cmgmt/connectors directory for AIX or Solaris. _____________________________________________________________________________________________________________ January 18, 2007 Page 18 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 4.3. AIX/Solaris: ECM installation issues Use Oracle installation instructions to install the Oracle database server and client. Check the Oracle compatibility matrix to ensure that the Oracle client level you are using is compatible with the version of Oracle Server you are using for the library server and resource manager databases. 4.3.1 Verify that the Oracle software is configured correctly Your Oracle sqlnet.ora file (client and server) must include TNSNAMES in your NAMES.DIRECTORY_PATH. The following is an example of a correctly configured sqlnet.ora file. Your actual file contents might be different. NAMES.DIRECTORY_PATH=(TNSNAMES,ONAMES,HOSTNAME) Additionally, ensure that your Oracle server tnsnames.ora and listener.ora files are configured for use with Oracle external routines (“extproc”). See your Oracle documentation for details. If there is an Oracle configuration error in this area, your library server configuration fails and DB2 Content Manager is not operational. You will want to configure tnsnames.ora with an entry to allow your Oracle library server database to be able to create stored procedures: EXTPROC_CONNECTION_DATA= (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0)) ) (CONNECT_DATA = (SID = PLSExtProc)(PRESENTATION = RO) ) ) 4.3.3. Create groups and user IDs Attention: The installation program can create these user IDs for you during the installation. 1. Create the DB2 Content Manager administration group. This group should have write access to all of the DB2 Content Manager installation directories. _____________________________________________________________________________________________________________ January 18, 2007 Page 19 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 2. Create the DB2 Content Manager administration ID, library server administration ID, resource manager administration ID, and DB2 Content Manager connection user ID. The DB2 Content Manager administration IDs (for example, icmadmin and rmadmin) should all be members of the DB2 Content Manager administration group. 3. Update all .profiles for user IDs created here, including the Oracle operating system user (default value is oracle): ORACLE_HOME=<path to your Oracle Home> LIBPATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LIBPATH CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc14.jar:$CLASSPATHIBMCM ROOT=/opt/IBM/db2cmv8 export ORACLE_HOME LIBPATH IBMCMROOT CLASSPATH Note: Solaris users replace LIBPATH with LD_LIBRARY_PATH: LD_LIBARY_PATH=$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$LD_LIBARY_PATH export LD_LIBRARY_PATH instead of LIBPATH 4.3.4. Oracle 64-bit considerations on AIX and Solaris The reference to lib32 in section 4.3.3 applies only for customers who are running the 64-bit installation of Oracle on AIX and Solaris operating systems. If you are running a 32-bit-only version of Oracle, the lib32 path reference is not needed because you only have a single lib directory under your ORACLE_HOME. Important: If you are running the 64-bit version, lib32 must come before the lib directory. Additionally, in a 64-bit environment, the Oracle listener must be configured to run the 32-bit version of the Oracle extproc process for external routines. The default Oracle configuration in a 64-bit installation is to spawn 64-bit extproc processes. The library server external routines are a 32-bit shared library and are not compatible with the 64-bit extproc. To ensure your listener is properly configured: 1. Stop the listener under which your extproc is configured. For example, enter: lsnrctl stop [LISTENER] _____________________________________________________________________________________________________________ January 18, 2007 Page 20 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 2. Edit <ORACLE_HOME>/network/admin/listener.ora. Look for an entry similar to the example below and make sure that PROGRAM=extproc32. Note that your specific listener.ora file might be different than the example. SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = /opt/oracle/920server) (PROGRAM = extproc32) ) … 3. Restart your listener. For example, enter: lsnrctl start [LISTENER] 4.3.5. Verify that the ojdbc14.jar file exists for the installation The ojdbc14.jar file must exist and be in the correct path before you begin the installation. Check that it exists in the following path: $ORACLE_HOME/jdbc/lib. If it does not, you need to install the Oracle JDBC drivers before proceeding with the DB2 Content Manager installation. 4.3.6. Ensure that the Oracle listener is started on the Oracle server where the DB2 Content Manager databases are located prior to launching the installation: su - oracle lsnrctl start 4.3.7. Remote communication If any of your DB2 Content Manager components are remotely communicating to the library server, you must ensure that the Oracle client (or server) is installed on each machine as well as the Oracle JDBC drivers. Important: The tnsnames.ora file must be correctly configured for the remote library server before DB2 Content Manager component products are installed. For example, if your resource manager database is not on the same machine as the library server database, then make sure the resource manager database tnsnames.ora file has your library server database entry. If your resource manager application is not on the same machine as either the library server or resource manager database, then the Oracle client must be installed on that machine and tnsnames.ora should have entries for both the library server and resource manager database. _____________________________________________________________________________________________________________ January 18, 2007 Page 21 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ Additionally, all of the client DB2 Content Manager components, such as eClient, Client for Windows, and DB2 Information Integrator for Content, that do not reside with the library server or resource manager databases require Oracle client and tnsnames.ora configuration for both databases. For example, your Oracle tnsnames.ora file might look similar to this example: # TNSNAMES.ORA Network Configuration File # Generated by Oracle configuration tools. ICMNLSDB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS=(PROTOCOL=TCP)(HOST=ls_host.ls_domain.com)(PORT=1521)) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = icmnlsdb.ls_domain.com) ) ) RMDB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS=(PROTOCOL=TCP)(HOST=rm_host.rm_domain.com)(PORT=1521)) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = rmdb.rm_domain.com) ) ) Note that the DB2 Content Manager installation and configuration tools use the Oracle JDBC thin driver to communicate with the library server and resource manager databases. DB2 Content Manager client applications, DB2 Information Integrator for Content connector API’s, and the resource manager application use the Oracle JDBC-OCI driver to communicate with the library server. 4.3.8. Test your library server and resource manager connectivity Perform a basic “sanity check” of proper Oracle configuration by testing connectivity to your library server and resource manager database. From a command prompt window, type the following command: <ORACLE_HOME>/bin/sqlplus <icmadmin>/<password>@<ls_dbname> where icmadmin = your library server administrator ID password = your library server administrator password ls_dbname = the TNS alias that you have defined for your library server database _____________________________________________________________________________________________________________ January 18, 2007 Page 22 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ Important: Do not set ORACLE_SID to test connectivity. Using the method above ensures that your Oracle listener and tnsnames are communicating properly with one another. Setting ORACLE_SID bypasses TNSNAMES. Do not rely on TNSPING to verify connectivity because that only verifies that the instance is registered with the listener. You should perform this check from all of the machines that connect to the library server database such as clients, mid-tier machines, and the resource manager application machine. If the resource manager application is on a different machine than your resource manager database, you should also perform this check against your resource manager database. 4.3.9. JDBC driver registration Usually, this step is performed the DB2 Content Manager installation. You should follow these steps for validation or troubleshooting only. 1) 2) 3) 4) 5) 6) Log on to WebSphere administrative console. Go to Resources > JDBC provider > new. Select Oracle JDBC Driver. Click OK. Set name: CM_Oracle_jdbc_driver. Set CLASSPATH to your Oracle JDBC driver path (ojdbc14.jar). For example: ORACLE_HOME/jdbc/lib/ojdbc14.jar. 7) Set the implementation classname to oracle.jdbc.OracleDriver. _____________________________________________________________________________________________________________ January 18, 2007 Page 23 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 5. Oracle installation suggestions to support IBM DB2 Content Manager 5.1. For all operating systems Oracle V9.2.0.6 and V9.2.0.7 are the only versions that DB2 Content Manager products support on any operating system. Oracle must be installed before to installing DB2 Content Manager. Depending on your needs, you might not need to install all aspects of Oracle Database Enterprise Edition. The following are guidelines that might or might not be appropriate for your environment. Consult with the Oracle database administrator or Information Technology (IT) department when choosing which aspects of Oracle to install. When installing your Oracle software for Content Manager usage, selecting a custom installation might allow you to save disk space. ¾ Enterprise Edition options not required by DB2 Content Manager: • Advanced security • Partitioning • Spatial • OLAP • Label security • Data mining • Oracle Development Kit • Transparent gateway • Change Management Pack ¾ Enterprise Edition options you might find useful but are not required by DB2 Content Manager: • Oracle Enterprise Manager (OEM) • Oracle HTTP Server (required for OEM) • Oracle Intelligent Agent (required for OEM) • Diagnostics Pack (for use with OEM) • Tuning Pack (for use with OEM) • Oracle Management Server (OMS) • iSQLPlus • Windows interfaces _____________________________________________________________________________________________________________ January 18, 2007 Page 24 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 5.2. Oracle product installation - Suggestions 9 During Oracle product installation, it is recommended that you allow Oracle to create a sample database. Although you don’t have to create a sample database for proper DB2 Content Manager installation, consider the following: • DB2 Content Manager requires a specific Oracle sqlnet.ora configuration (see elsewhere in this document for details), but does not create the file if it does not exist. • DB2 Content Manager requires a properly configured Oracle listener that is up and running (the library server and DB2 Information Integrator for Content administration database also require a configured extproc as part of the listener), but does not create the listener.ora file if it does not exist. • The DB2 Content Manager installer requires an existing tnsnames.ora file (the library server and DB2 Information Integrator for Content administration database also require an extproc entry that corresponds to the listener), but does not create the file if it doesn’t exist. • All three of these files are required to exist before a DB2 Content Manager installation. • Creating a sample database in Oracle creates these files for you. 9 If you are creating a sample database during the installation, perform a typical configuration when Net Configuration Assistant is launched. 9 After successful completion of all of the Oracle installation steps, including sample database creation and Net Configuration Assistant, verify connectivity to your sample database through Oracle SQL*Plus both from the local machine and from any remote clients that will be used with DB2 Content Manager. This helps to ensure that the Oracle client and server are properly configured and able to communicate with one another prior to attempting to do a DB2 Content Manager installation. Use the fully qualified logon string with SQL*Plus for more thorough validation. For example: sqlplus <dbuser>/<dbpasswd>@<dbname> _____________________________________________________________________________________________________________ January 18, 2007 Page 25 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 6. IBM DB2 Content Manager Oracle-specific administration issues 6.1. Remote connections If you are running a client application that communicates with a remote library server, the Oracle Client tnsnames.ora file needs to be updated to include remote database connection information. The connection information also needs to be added to the DB2 Content Manager server parameter file, cmbicmsrvs.ini. Verify remote connectivity by using Oracle SQL*Plus to connect to the remote library server. See section 4.1.6 (Windows) or 4.3.8 (AIX and Solaris) for details. Attention: The Server Configuration Utility tool allows you to update the cmbicmsrvs.ini file. This file might also be updated during installation of certain ECM products. 6.2. Text search options DB2 Content Manager can be configured to use Oracle Text to make attributes, resource content, and document content text-searchable. To enable this functionality, you must select the check box on the library server configuration panels in the DB2 Content Manager installation to enable text search. Alternately, Planning and Installing Your Content Management System documents a procedure for enabling text search functionality after the DB2 Content Manager installation. Through the DB2 Content Manager system administration utility, a DB2 Content Manager administrator can define various text search options when creating an item type (if DB2 Content Manager is enabled for text search). Client applications that support text search functionality can then be used to perform textbased searches on items stored in text-searchable item types. The system administration client supports the following Oracle-based text search options when defining an item type: 6.2.1. In the New Item Type Definition window, select the Text Searchable check box to enable text search for the item type. Then click Options. 6.2.2 If you want to use default values for all of the text search options, select DEFAULT SYSTEM in the Copy settings from field, and click Load. Alternatively, select another entry from the list and click Load to copy that entry’s values in the Text Search Options window. 6.2.3 Choose your index preferences: Datastore Specifies how your text is stored. Filter Specifies how documents are filtered for indexing. Your selection is based on your documents’ formatting, character sets, and type. For example, HTML and plain text document do not need filtering, so they can use the null filter option. _____________________________________________________________________________________________________________ January 18, 2007 Page 26 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ Lexer Specifies the language of the text you are indexing. Wordlist Specifies the linguistic options (stemming, fuzzy and wildcard). This setting affects the docs that are returned for text search queries. Storage Specifies how the index table should be stored. Stop List Specifies words not to index. The lists can include one language or multiple languages. You can create your own list or you can modify the default list that comes with your database language. Section Group Specifies the area to index within a document. 6.2.4 Specify how the index will update: Update every Specifies the length of time between synchronizing changes to the index. Parallel degree Specifies the degree to run parallel synchronization. Maximum memory Specifies the maximum runtime memory to use for synchronization. The more memory you allocate, the better the indexing performance. 6.2.5 Specify how the index will be optimized: Update every Specifies the length of time between optimizations, which will remove old information and can improve query time. Parallel degree Specifies the degree as a number for parallel optimization. Maximum time Specifies the maximum amount of time to spend on optimizing the index. 6.2.6 To specify additional options, enter the information in the Option Name field and corresponding Option Value field. Click Add to add the new option to the list. For example, to set the runtime memory to use for indexing to 32 megabytes, add memory to the Option Name field and 32M to the Option Value field. See your Oracle documentation for a complete list of options available. 6.2.7 Click OK to save the information. Important: The default setting specifies that the text index will not be updated automatically if an update frequency is not set. This can be changed later, programmatically, through the DB2 Information Integrator for Content Connector API method, DKDatastoreDefICM.updateTextIndexes(). The sample which demonstrates the use of this method is STextIndexUpdateICM. _____________________________________________________________________________________________________________ January 18, 2007 Page 27 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 6.3. Resource manager utilities and services environment setup file Windows: IBMCMROOT\config\setprocenv.bat AIX and Solaris: IBMCMROOT/config/setprocenv.sh Make sure the following values are completed: Input Value dbtype orahome Setting oracle Oracle home installation directory: Windows: c:\program files\oracle\ora92 AIX: /usr/oraprod/product/9.2.0 Solaris: /opt/oracle/920server ora_jdbc_abspath Fully qualified path of the Oracle JDBC driver location (JDBC 9.0.x or later required) 6.4. Optimize databases Oracle DBAs must use traditional tools and utilities for such things as reorgs, index rebuilds, and analyzes. DB2 Content Manager does not prevent Oracle database administrators from using whatever methodologies they are used to in order to manage the database. 6.5. Oracle features support Currently, the following Oracle features have not been tested with DB2 Content Manager and are therefore not supported at this time: • • • • Oracle high availability: Real application clusters and related technologies Oracle storage: RAW partitions, Oracle cluster file system Oracle replication: Data guard Oracle table spaces: Oracle partitioned tables Important: Oracle 10g is not currently supported. _____________________________________________________________________________________________________________ January 18, 2007 Page 28 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 6.6. Customize table spaces • • Library server table space setup options DB2 Information Integrator for Content system administration database table space setup options Customers can create their own table spaces for use with DB2 Content Manager, but are currently required to use the table space names specified below for both the library server and the resource manager. Table Space Type Description Default name Frequently queried large objects Table space holds tables for which updates, inserts, and deletes are very common. ICMVFQ04 Moderately queried large objects Table space holds large, persistent, frequently used tables, such as the item type tables. ICMLFQ32 Rarely queried large objects Table space holds large but infrequently used tables, such as event logs. ICMLNF32 Frequently queried small objects Table space holds small, frequently used but seldom updated tables. ICMSFQ04 Table indexes Table space holds library server indexes. ICMLSNDX • Resource manager table space setup options Table Space Type Description Default name Frequently queried large objects Tables that can become very large because they have information about all of the objects stored on the resource manager. OBJECTS Collections Holds small, but frequently read administrative information. SMS Large objects Holds binary large objects (BLOBS). BLOBS Tracking system transactions Holds volatile tables related to transactions. TRACKING Item validation Holds volatile tables with information about objects that are being validated for data consistency between the library server and the resource manager. VALIDATEITEM Table indexes Holds resource manager indexes. OBJINDX _____________________________________________________________________________________________________________ January 18, 2007 Page 29 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 6.7. Useful links DB2 Content Management main site: Sales site with product offerings and overviews: http://www-306.ibm.com/software/data/cm/ DB2 Content Manager Support: Searchable APARs, technotes, white papers and more: http://www-306.ibm.com/software/data/cm/cmgr/mp/support.html DB2 Content Manager Information Roadmap: Documentation site: http://publib.boulder.ibm.com/infocenter/cmgmt/v8r3m0/index.jsp?topic=/com.ibm.cmgmt.hl p/cmiroadmap.htm _____________________________________________________________________________________________________________ January 18, 2007 Page 30 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 7. Appendix 7.1. Detailed usage of library server database init.ora file Parameter Db_name Db_domain Global_names Remote_login_passwordfile Undo_management Control_files Db_block_size Db_cache_size Shared_pool_size Java_pool_size Pre_page_sga Pga_aggregate_target Db_files Open_cursors Processes Cursor_sharing Cursor_space_for_time Background_dump_dest User_dump_dest Core_dump_dest Max_dump_file_size Job_queue_processes Compatible Set To Input name given during installation. Input name given during installation. True None Auto Input directory names given during installation. 4096 Windows, 8192 UNIX 175M 0 0 True 200M 1024 500 150 Similar True Input directory name given during installation. Input directory name given during installation. Input directory name given during installation. 10240 1 9.2.0 7.2. Library server database creation particulars Log file groups Database path and mirror path (directories input during installation) and multiplexed in three groups of 50M size each. Autoextend on 50M, max at 500M. Undo table space Called UNDO01, 50M size, autoextend unlimited. Table space defaults Set at initial 64K, next 64K, minextents 1, maxextents unlimited, pctincrease 0. Minimum extent 64K. Temporary table space TEMP 100M size, extent management local, autoextend unlimited. Default for sys and system users. _____________________________________________________________________________________________________________ January 18, 2007 Page 31 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 7.3. Detailed usage of resource manager database init.ora file Parameter Db_name Db_domain Global_names Remote_login_passwordfile Undo_management Control_files Db_block_size Db_cache_size Shared_pool_size Large_pool_size Java_pool_size Pre_page_sga Pga_aggregate_target Db_files Open_cursors Processes Cursor_sharing Cursor_space_for_time Optimizer_mode Background_dump_dest User_dump_dest Core_dump_dest Max_dump_file_size Job_queue_processes Compatible Set To Input name given during installation. Input name given during installation. True None Auto Input directory names given during installation. 4096 Windows, 8192 UNIX 50M 50M 50M 0 True 100M 1024 500 150 Similar True First_rows Input directory name given during installation. Input directory name given during installation. Input directory name given during installation. 10240 1 9.2.0 7.4. Resource manager database creation particulars Log file groups Database path and mirror path (directories input during install) and multiplexed in 3 groups of 50M size each. Autoextend on 50M, max at 500M. Character set UTF8 Undo table space Called UNDO01, 50M size, autoextend unlimited. Table space defaults Set at initial 64K, next 64K, minextents 1, maxextents unlimited, pctincrease 0. Minimum extent 64K. Temporary table space TEMP 100M size, extent management local, autoextend unlimited. Default table space for sys and system users. _____________________________________________________________________________________________________________ January 18, 2007 Page 32 of 33 IBM DB2 Content Manager Enterprise Edition setup and usage For Oracle-based installations ____________________________________________________________________________________________________________ 7.5. References The following publications, Web sites, and documents were useful in helping to compile this document. They can provide further information on the topics presented in this document. DB2 Content Manager publication library and info center (Contains links to the information center and to V8.3 manuals such Planning and Installing Your Content Management System and System Administration Guide). http://www-306.ibm.com/software/data/cm/cmgr/mp/ http://publib.boulder.ibm.com/infocenter/cmgmt/v8r3m0/index.jsp Managing your digital content effectively http://www-306.ibm.com/software/data/cm/attach/cmtechwp.pdf ECM Solution Guide http://w3103.ibm.com/software/xl/portal/!ut/p/_s.7_0_A/7_0_IP?type=doc&srcID=DM&docID=Q391526P32296V72 ECM Install viewlets http://w3103.ibm.com/software/xl/portal/!ut/p/_s.7_0_A/7_0_IP?type=doc&srcID=DM&docID=D850982N63863I42 © Copyright IBM Corporation 2006 IBM Corporation IBM Software GroupRoute 100 Somers, NY 10589 Printed in the United States of America All Rights Reserved May 2006 IBM, the IBM logo, DB2 and WebSphere are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries or both. Microsoft, Windows, and Windows XP, 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 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. All statements regarding IBM future direction or intent are subject to change or withdrawal without notice and represent goals and objectives only. ALL INFORMATION IS PROVIDED ON AN “AS-IS” BASIS, WITHOUT ANY WARRANTY OF ANY KIND. References in this publication to IBM products or services do not imply that IBM intends to make them available in all countries in which IBM operates. This material was developed in conjunction with specific hardware and software products and levels specified herein. Your environment might contain hardware and software components not present during IBM testing that significantly alter the performance or operability of any test scenario. Any performance data contained in this document was determined in a controlled environment, and therefore, the results that may be obtained in other operating environments might vary significantly. Users of the material should verify the applicable data for their specific environment. Further, the information contained in this material has not been submitted to comprehensive testing and is distributed AS IS. No warranties or guarantees are given, other than those accompanying the sale or license of the IBM products. The use of this information or the implementation of any of these techniques is your responsibility and depends on your ability to evaluate and integrate them into your operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. IBM assumes no responsibility for its accuracy or completeness of information herein related to non-IBM products. The IBM home page on the Internet can be found at ibm.com _____________________________________________________________________________________________________________ January 18, 2007 Page 33 of 33