Transferring to an Oracle database  |
Use the configuration wizard to transfer the Lotus® Quickr™ database domains to an Oracle database. |
Use the configuration wizard to transfer the Lotus® Quickr™ database domains to an Oracle database.
Before transferring the Lotus Quickr database domains to an Oracle database, you must complete Preparing an Oracle database for Lotus Quickr.
A database domain is a concept from WebSphere® Portal, which refers to a complete set of tables, indices, and constraints contained in one single database schema. There are 9 database domains in Lotus Quickr 8.5: release, customization, feedback, likeminds, community, jcr (inherited from WebSphere Portal), placecntr, searchcntr, and qkradmin (Lotus Quickr specific database domains). During installation, all 9 database domains reside in the same database, specified during the installation. After installation, the 9 domains can be transferred to remote databases. Each domain can be transferred to a different database, for example for performance reasons. IMPORTANT: If you are transferring to Oracle RAC, the URL used during database-transfer must point to a single RAC node, for example:
jdbc:oracle:thin:@PRIMARY_NODE_HOSTNAME:1521:PRIMARY_NODE_INSTANCENAME
The Oracle RAC URL will be set manually after database-transfer completes.
- On the Lotus Quickr machine, run the ConfigWizard for performing the database transfer. If you are in a cluster environment, perform this step on the primary node.
- Enter the appropriate ConfigWizard command.
- UNIX®: quickr_install_root/wp_profile/wizard/configwizard.sh
- Windows®: quickr_install_root\\wp_profile\\wizard\\configwizard.bat
Note: After installation, open a new command prompt to start the configuration wizard with the updated environment variables.
- Windows 64 bit: quickr_install_root\\wp_profile\\wizard\\configwizard64.bat
Note: After installation, open a new command prompt to start the configuration wizard with the updated environment variables.
- Click Configure the database
- Enter your Lotus Quickr Account
- Click Transfer data to another database -> Transfer data with all domains
- Select IBM DB2 Universal Database as the source database.
- Select Oracle Enterprise Edition as the target database
- Specify the source DB2® database information:
* DbDriver: com.ibm.db2.jcc.DB2Driver (predefined)
* DbLibrary: C:/IBM/Quickr/db2/java/db2jcc.jar;C:/IBM/Quickr/db2/java/db2jcc_license_cu.jar (predefined)
* JdbcProviderName: wpdbJDBC_db2 (predefined)
* DbHostName: hostname (or IP) of the Lotus Quickr install machine
* DbPort: DB2 port (e.g. 50000)
* DbName: name of the Lotus Quickr database (out of box: WPSDB)
* DbUser: db user (same as your Lotus Quickr user out of installation)
* DbPassword: db password (same as your Lotus Quickr password out of installation)
- Click Next. The configuration wizard will make a JDBC connection to the specified database. If the connection fails, verify the information and try again.
- Specify the target Oracle database information:
* DbDriver: oracle.jdbc.OracleDriver (predefined)
* DbLibrary: C:\\ojdbc14.jar (IMPORTANT: you should copy this JDBC driver file to your Quickr machine)
* JdbcProviderName: wpdbJDBC_oracle (predefined)
* DbHostName: hostname (or IP) of the Oracle machine
* DbPort: Oracle database port (e.g. 1521)
* DbName: name of the Oracle database (e.g. QKRDB as shown in the above DDL scripts)
* DbUser: DBA user on the Oracle database (if you use "SYSTEM" as the user, be sure you grant "sysdba" role to it, since "SYSTEM" is only granted "SYSOPER" out of box; or you can use the following command to create a DBA user for Lotus Quickr:
connect sys/PASSWORD/@QKRDB as sysdba;
create user QKRDBA identified by MYPASSWORD;
grant sysdba to QKRDBA;
then you can use QKRDBA as your DB user and MYPASSWORD as your DBA account.
* DbPassword: DBA user password
- Click Next. The configuration wizard will make a JDBC connection to the specified database. If the connection fails, verify the information and try again.
- Verify both databases. Verify all the information on the next preview panel.
- Click Next to initiate the database transfer.
- If you are in a cluster environment, perform this step on the secondary node.
- Copy the ojdbc14.jar file to your secondary node. For example: C:\\lib\\ojdbc14.jar
- Open the DM WebSphere Application Server administration console, and create the following WebSphere Application Server variable:
- scope: your secondary node
- name: WP_ORACLE_JDBC_DRIVER_CLASSPATH_1
- value: C:\lib\ojdbc14.jar
- Copy the wp_profile/PortalServer/jcr/lib/com/ibm/icm/icm.properties file from the primary node to the secondary node. Change all values that are different between the two machines, for example the location of the index directory.
- Restart the secondary node.
- Oracle RAC only. Update the database URL in the WebSphere datasource to connect to the cluster:
- Login to the WebSphere Application Server Administrator Console
- Navigate to Resources > JDBC Providers
- If there is a value in the Node field, remove it and click Apply.
- For each Oracle JDBC provider, repeat the following steps:
- Click the provider name.
- Select Data Sources.
- Click the name of the data source.
- Under the Oracle data source properties, modify the URL attribute according to Oracle RAC configuration:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=PRIMARY_NODE_HOSTNAME)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=SECONDARY_NODE_HOSTNAME)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=DATABASE_SERVICENAME))) - Save your changes.
Parent topic: Installing: qp85
|
|
|
|
| Version 2 |
November 21, 2011 |
8:58:33 AM |
by Hunter T Tweed  |
|
|