Configure WebSphere Portal for Oracle

After installing and setting up databases, configure WebSphere Portal to populate and use these databases. Before configuring databases, ensure that the following prerequisites are met:

• The database software is installed.
• Databases are created and the procedure for setting up the databases has been completed.
• WebSphere Portal V5.0 Test Environment is installed on Portal Toolkit.

Notes:

• If you intend to configure WebSphere Portal to use database software other than Cloudscape, it is recommended that you perform the database transfer before you use WebSphere Portal extensively. Large amounts of data in the databases can cause the database transfer to fail if your Java heap size is not large enough. Because information is added to the databases as you use WebSphere Portal, perform the database transfer as soon as it is practical to avoid problems due to the amount of data that you are transferring.

Follow the appropriate procedures:

• Configure for databases
• Verifying configuration
• Grant database privileges
• Next steps

Configure for databases

Follow these steps to configure WebSphere Portal to use the Oracle databases.

Note:A configuration template might exist to support these instructions. Refer to the <WS_Installdir>\runtimes\portal_v50\config\helpers (WS_Installdir is the directory where WebSphere Studio is installed.) directory for available configuration templates. Use the configuration template to update the wpconfig.properties file, as described in "Using configuration templates" in the InfoCenter of WebSphere Portal, according to the property descriptions and recommended values provided here. If you do not want to use a configuration template, simply follow these instructions as written.

Password considerations: For security reasons, if you elect to not store passwords in the wpconfig.properties file, you may specify passwords on the portal server command line. For example:

• WPSconfig.sh task_name [-Dpassword_property_key=password_value]
• WPSconfig.sh validate-ldap -DPortalAdminPwd=password -DLDAPAdminPwd=password -DLDAPBindPassword=password -DWasPassword=password -DLTPAPassword=password

1. In the command prompt, change to the directory WS_Installdir\runtimes\portal_v50\config (WS_Installdir is the directory where WebSphere Studio is installed.).
2. Enter the following.
   • Linux: ./WPSconfig.sh database-transfer-export-linux
   • Windows: WPSconfig.bat wpcpconfigure

   Note: If you installed the WebSphere Portal V5.0 Test Environment on WebSphere Application Server Enterprise (WAS Enterprise) V5.0.2, this command is not required.

3. Export the current database data by entering the following command:
   
   • Linux: ./WPSconfig.sh database-transfer-export-linux
   • Windows: WPSconfig.bat database-transfer-export
   Note: After running this task, a message indicating success should result. Check the log files to verify that this task was successful.
4. Locate the WS_Installdir\runtimes\portal_v50\config\wpconfig.properties (WS_Installdir is the directory where WebSphere Studio is installed.) file and create a backup copy before changing any values.
5. Edit the WS_Installdir\runtimes\portal_v50\config\wpconfig.properties (WS_Installdir is the directory where WebSphere Studio is installed.) file and enter the values that are appropriate for your environment.
   Note the following information:
   • Do not change any settings other than those that are specified in these steps. For instructions on working with these files, see "Configuration properties reference" in the InfoCenter of WebSphere Portal for a complete properties reference, including default values.
   • If you are using a remote database, be sure to enter the values for the remote server.
   • Use / instead of \ for all platforms.
   • Some values, shown here in italics below, might need to be modified to your specific environment.
   • There might be additional database properties other than those listed here. Only change the properties within this table; skip all other properties.
   • If you are following the recommended architecture in Planning for Oracle, the Value listed for each property in the following table represents the Oracle-specific information that is required to configure WebSphere Portal to Oracle.

   Section	Property	Value
   Database properties	DbSafeMode	Description: This only applies to database-specific tasks. If this property is set to true no database-specific updates will be performed, such as create/modify/drop database. The property should be used if a preconfigured database (from a previous installation) already exists. If the property is set to false the database will be updated, and the pre-existing database configuration is overwritten. Recommended value: false Default Value: false
   	DbType	Description: The type of database that is used to store information for WebSphere Portal. This value indicates the type of database you are using. You must change this value to oracle. Recommended value: oracle Default value: cloudscape
   	WpsDbName	Description: This value represents the database name where you want the WebSphere Portal objects to be created. In the planning section, this database is referred to as wps50. Note: This value is also the database element in the DbUrl property. Important note for Oracle: WebSphere Portal and Member Manager must share the same database. Therefore, this value must be the same for WmmDbName also. Recommended value: wps50 Default value: wps50
   	DbDriver	Description: This is the name of the JDBC provider that is used to import SQL files. Recommended value: oracle.jdbc.driver.OracleDriver Default value: com.ibm.db2j.jdbc.DB2jDriver (Cloudscape)
   	DbDriverDs	Description: The data source for the JDBC provider that WebSphere Portal uses to communicate with its databases. Recommended value: oracle.jdbc.xa.client.OracleXADataSource Default value: com.ibm.db2j.jdbc.DB2jXADataSource (Cloudscape)
   	DbUrl	Description: The database URL that is used to access the WebSphere Portal database with JDBC, where <hostname> is the name of the remote server and <port> is the port where the appropriate database instance is listening. The value must conform to standard JDBC URL syntax. Note: The database element of this value should match the value of WpsDbName. Recommended value: jdbc:oracle:thin:@<hostname>:<port>:wps50 Default value: jdbc:db2j:wps50;create=true (Cloudscape)
   	DbUser	Description: Database user ID needed to connect to WpsDbName database. In the planning section, this user is referred to as wpsdbusr. Recommended value: wpsdbusr Default value: db2admin
   	DbPassword	Description: This password must match the password for the database user ID that is indicated in DbUser. Recommended value: No recommended value for this property Default value: password
   	DbLibrary	Description: DbLibrary is machine specific. You must locate the classes12.zip file on your machine, and enter the fully-qualified path name, including the file name. Recommended value: C:/Program Files/oracle/jdbc/lib/classes12.zip Default value: WS_Installdir/runtimes/portal_v50/shared/app/cloudscape/db2j.jar, where WS_Installdir is the WebSphere Studio installation directory. (Cloudscape)
   	WpsDsName	Description: This value is the name of the data source to be used for the WebSphere Portal database. Recommended value: wps50DS Default value: wps50DS
   WebSphere Portal content publishing Database properties	WpcpDbName	Description: This value indicates the database name of the database that you created for content publishing. Note: This value is also the database element in the WpcpDbUrl property. In the planning section, this database is referred to as wpcp50. Recommended value: wpcp50 Default value: wps50
   	WpcpDbUser	Description: This value should be a user in the database. In the planning section, this user is referred to as wcmdbadm. If you choose to use one database to store all WebSphere Portal, Member Manager, and content publishing information, this user must be different from DbUser. Recommended value: wcmdbadm Default value: wcmdbadm
   	WpcpDbPassword	Description: This password must match the password for the database user ID that is indicated in WpcpDbUser. Recommended value: No recommended value for this property Default value: password
   	WpcpDbUrl	Description: The database URL that is used to access the content publishing database with JDBC, where <hostname> is the name of the remote server and <port> is the port where the appropriate database instance is listening. The value must conform to standard JDBC URL syntax. Note: The database element of this value should match the value of WpcpDbName. Recommended value: jdbc:oracle:thin:@<hostname>:<port>:wpcp50 Default value: jdbc:db2j:wps50;create=true (Cloudscape)
   	WpcpDbEjbPassword	Description: The password for Enterprise Java Bean (EJB) user. Only needed for MS SQL Server and Oracle. Recommended value: No recommended value for this property Default value: ejb
   	WpcpDbPznadminPassword	Description: The password for PZNADMIN user. Only needed for MS SQL Server and Oracle. Recommended value: No recommended value for this property Default value: pznadmin
   	FeedbackDbName	Description: This value represents the database name where you want the Feedback objects to be created. In the planning section, this database is referred to as fdbk50. Note: This value is also the database element in the FeedbackDbUrl property. Recommended value: fdbk50 Default value: wps50
   	FeedbackDbUser	Description: Database user ID needed to connect to the FeedbackDbName database. In the planning section, this user is referred to as feedback. This property must be changed to the uppercase value FEEDBACK. Recommended value: FEEDBACK Default value: wcmdbadm
   	FeedbackDbPassword	Description: This password must match the password for the database user ID that is indicated in FeedbackDbUser. Recommended value: No recommended value for this property Default value: password
   	FeedbackDbUrl	Description: The database URL that is used to access the feedback database with JDBC, where <hostname> is the name of the remote server and <port> is the port where the appropriate Oracle instance is listening. The value must conform to standard JDBC URL syntax. Note: The database element of this value should match the value of FeedbackDbName. Recommended value: jdbc:oracle:thin:@<hostname>:<port>:fdbk50 Default value: jdbc:db2j:wps50;create=true (Cloudscape)
   Member Manager properties	WmmDsName	Description: This value is the name of the data source to be used for the Member Manager database. Recommended value: wmmDS Default value: wmmDS
   	WmmDbName	Description: This value represents the database name where you want the Member Manager objects to be created. In the planning section, this database is shared and referred to as wps50. If Member Manager will share the WebSphere Portal database, this value will be the same as the value for WpsDbName. Note: This value is also the database element in the WmmDbUrl property. Important note for Oracle: WebSphere Portal and Member Manager must share the same database. Therefore, this value must be the same for WpsDbName also. Recommended value: wps50 Default value: wps50
   	WmmDbUser	Description: Database user ID needed to connect to the WmmDbName database. In the planning section, this user is referred to as wmmdbusr. Recommended value: wmmdbusr Default value: db2admin
   	WmmDbPassword	Description: This password must match the password for the database user ID that is indicated in WmmDbUser. Recommended value: No recommended value for this property. Default value: password
   	WmmDbUrl	Description: The database URL that is used to access the Member Manager database with JDBC. The value must conform to standard JDBC URL syntax. If WebSphere Portal and Member Manager are sharing a database, you will use the same database value entered for WpsDbName. Note: The database element of this value should match the value of WmmDbName. Recommended value: jdbc:oracle:thin:@<hostname>:<port>:wps50 Default value:jdbc:db2j:wps50;create=true (Cloudscape)

6. Save the file.
7. Open a command prompt, and change to directory WS_Installdir\runtimes\portal_v50\config (WS_Installdir is the directory where WebSphere Studio is installed.).
8. Enter the following commands to validate configuration properties.
   • Linux:
     • ./WPSconfig.sh validate-database-connection-wps -DDbPassword=password
     • ./WPSconfig.sh validate-database-connection-wmm -DWmmDbPassword=password
     • ./WPSconfig.sh validate-database-connection-wpcp -DWpcpDbPassword=password -DFeedbackDbPassword=password
     • ./WPSconfig.sh validate-database-driver
   • Windows:
     • WPSconfig.bat validate-database-connection-wps -DDbPassword=password
     • WPSconfig.bat validate-database-connection-wmm -DWmmDbPassword=password
     • WPSconfig.bat validate-database-connection-wpcp -DWpcpDbPassword=password -DFeedbackDbPassword=password
     • WPSconfig.bat validate-database-driver
9. Enter the following commands to run the configuration task.
   • Linux: ./WPSconfig.sh database-transfer-import
   • Windows: WPSconfig.bat database-transfer-import

   Note: After running this task, a message indicating success should result. Check the log files to verify that this task was successful. If the configuration fails, verify the values in the wpconfig.properties file, and then repeat this step.

10. Linux only: Enter the following commands:
    • cd WS_Installdir\PortalToolkit (where WS_Installdir is the directory that you installed WebSphere Studio.)
    • ./ModifyResourcesXml.sh
11. Verify that the WebSphere Portal V5.0 Test Environment can start successfully by carrying out the following steps.
    1. Launch the WebSphere Studio.
       Linux:
       1. If you want to use the double-byte character set on Red Hat 8.0, you will need to upgrade GTK 2.0 to GTK 2.2.2 or later. However, support for Korean, Simplified Chinese, Japanese, and Traditional Chinese languages is not fully functional. To avoid these limitations, use the product in English. To upgrade GTK, refer to "(Optional) Upgrading to GTK 2.2.2 or later" in the Installation Guide of WebSphere Studio Version 5.1.2.
       2. Log out and log in as a user that is used for the development.
       3. In a command prompt, type either of the following command:/usr/bin/wssitedev51 or /usr/bin/wsappdevie51
       Windows:
       1. Select Start > Programs > IBM WebSphere Studio > Site Developer 5.1.2, Enterprise Developer 5.1.2, or Application Developer Integration Edition 5.1.1 to start the application.
    2. From the menu, select File > New > Other > Server > Server and Server Configuration.
    3. Select WebSphere Portal version 5.0 > Test Environment and click Finish.
    4. In the Servers view, right-click the server and select Start.

Verifying configuration

1. Verify that the WebSphere Portal server is running by opening the following URL in a browser:

   http://localhost:9081/wps/portal/!ut/p/.cmd/LoginUserNoAuth?userid=wpsadmin&password=wpsadmin

   9081 is default port number of WebSphere Portal server in the Test Environment.

Grant database privileges

Grant content publishing users the required privileges by typing the following commands:

SQL> grant ALTER on  EJB.BRBeans_Rule to PZNADMIN;
SQL> grant DELETE on  EJB.BRBeans_Rule to PZNADMIN;
SQL> grant INSERT on  EJB.BRBeans_Rule to PZNADMIN;
SQL> grant SELECT on  EJB.BRBeans_Rule to PZNADMIN;
SQL> grant UPDATE on  EJB.BRBeans_Rule to PZNADMIN;

SQL> grant ALTER on  EJB.BRBeans_RuleFolder to PZNADMIN;
SQL> grant DELETE on  EJB.BRBeans_RuleFolder to PZNADMIN;
SQL> grant INSERT on  EJB.BRBeans_RuleFolder to PZNADMIN;
SQL> grant SELECT on  EJB.BRBeans_RuleFolder to PZNADMIN;
SQL> grant UPDATE on  EJB.BRBeans_RuleFolder to PZNADMIN;

Next steps

You have completed this step. Continue to the next step by choosing one of the following options: