This section includes information on setting up Oracle databases to work with WebSphere Portal.
When creating Oracle databases for use with WebSphere Portal, you should consider the following information:
You must create the databases that you are planning to use, create users, and grant privileges before you can configure WebSphere Portal to use the database. After you finish setting up the databases, continue to the Configuring WebSphere Portal for Oracle topic.
For additional information on the databases that you are creating, refer to the Oracle product documentation. For more information on the recommended database architecture, see the Planning for Oracle topic for information on the databases that you need to create.
Be sure that all databases to be used with WebSphere Portal are created as UTF-8 character set databases.
Note: If you are using remote Oracle databases, you must also copy the classes12.zip file from the remote Oracle server to the WebSphere Portal machine. The typical location is the <oracle_home>/jdbc/lib directory. Record the copy location on your local machine for future reference.
Ensure that you create users and grant the appropriate privileges in Oracle before configuring WebSphere Portal to work with Oracle.
Follow these steps to create the users in the WebSphere Portal databases:
SQL> create user <username> identified by <password> default tablespace <user_tablespace> temporary tablespace <temp_tablespace>;
where <user_tablespace> is the default tablespace that is identified by the database administrator to store user objects and <temp_tablespace> is identified to store temporary objects.
For example, to create the wpsdbusr in the wps50 database, log in to the wps50 database and type:
SQL> create user WPSDBUSR identified by ABC123 default tablespace USERS temporary tablespace TEMP;
To implement the architecture based on the recommendations in the planning section, follow these steps:
$ sqlplus
Press Enter
Enter user-name:
username/password@<dbname>
where username is an existing administrative user in the database. For example:
system/manager@wps50 will log the administrative user system with a password of manager into the wps50 database.
SQL> create user WPSDBUSR identified by PASSWORD default tablespace USERS temporary tablespace TEMP; SQL> create user WMMDBUSR identified by PASSWORD default tablespace USERS temporary tablespace TEMP;
SQL> connect
Press Enter
Enter user-name:
username/password@<dbname>
where username is an existing administrative user in the database. For example:
system/manager@wpcp50 will log the administrative user system with a password of manager into the wpcp50 database.
SQL> create user PZNADMIN identified by PASSWORD default tablespace USERS temporary tablespace TEMP; SQL> create user EJB identified by PASSWORD default tablespace USERS temporary tablespace TEMP; SQL> create user WCMDBADM identified by PASSWORD default tablespace USERS temporary tablespace TEMP;
Connect to the Feedback database
SQL> connect
Press Enter
Enter user-name:
username/password@<dbname>
where username is an existing administrative user in the database. For example:
system/manager@fdbk50 will log the administrative user system with a password of manager into the fdbk50 database.
SQL> create user FEEDBACK identified by PASSWORD default tablespace USERS temporary tablespace TEMP;
SQL> exit
Grant these two default roles and their corresponding default privileges to each of the users that you created:
To grant WebSphere Portal users the appropriate privileges, perform the following steps:
SQL> grant connect, resource to <username>;where <username> represents the database user.
For example, to grant privileges for users in the wps50 database:
SQL> grant connect, resource to wpsdbusr;
To implement the architecture based on the recommendations in the planning section, follow these steps:
Connect to the WebSphere Portal database
SQL> connect
Press Enter
Enter user-name:
username/password@<dbname>
where username is an existing administrative user in the database. For example:
system/manager@wps50 will log you in to the wps50 database.
Grant WebSphere Portal users the required privileges by typing
SQL> grant connect, resource to WPSDBUSR; SQL> grant connect, resource to WMMDBUSR;
Connect to the content publishing database
SQL> connect
Press Enter
Enter user-name:
username/password@<dbname>
where username is an existing administrative user in the database. For example:
system/manager@wpcp50 will log you into the wpcp50 database.
Grant content publishing users the required privileges by typing
SQL> grant connect, resource to PZNADMIN; SQL> grant connect, resource to EJB; SQL> grant connect, resource to WCMDBADM; SQL> grant insert any table to WCMDBADM;
Note: The insert privilege is required only to import the database during WebSphere Portal configuration. After configuring WebSphere Portal, this privilege can be revoked, if desired.
Connect to the content publishing Feedback database
SQL> connect
Press Enter
Enter user-name:
username/password@<dbname>
where username is an existing administrative user in the database. For example:
system/manager@fdbk50 will log you in to the fdbk50 database.
Grant the content publishing feedback user the required privileges by typing
SQL> grant connect, resource to FEEDBACK;
SQL> exit
You have completed this step. Continue to the next step by choosing one of the following topics:
Related information |
---|