Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Granting privileges

This section provides information on granting privileges on Oracle.

Grant these two default roles and their corresponding default privileges to each of the users that you created:

• CONNECT
• RESOURCE

To grant WebSphere Portal Express users the appropriate privileges, perform the following steps:

1. Log in to the database in which you want to grant privileges to users.
2. Log in to SQLPlus as system/manager or another administrative user.
3. When granting privileges on dba_pending_transactions, be logged in as sysdba.
4. From the prompt, type the following command, where username represents the database user, to grant privileges: SQL> grant connect, resource to username;

1. Start SQL*Plus, the Oracle SQL command line tool, and enter the following commands to log in:

   $ sqlplus
   user-name: username/password@dbname

   where username is an existing administrative user in the database. For example, system/manager@release will log the administrative user system with a password of manager into the release database.

2. Connect to the WebSphere Portal Express database by entering the following command:

   SQL> connect
   user-name: username/password@dbname

   where username is an existing administrative user in the database. For example, system/manager@wpsdb will log you in to the wpsdb database.

3. Grant WebSphere Portal Express users for each dbdomain the required privileges:

   SQL> grant select on dba_pending_transactions to dbdomain.dbusr;
   SQL> grant connect, resource to dbdomain.dbusr;

4. Connect to the content database by entering the following commands:

   SQL> connect
   user-name: username/password@dbname

   where username is an existing administrative user in the database. For example, system/manager@jcrdb will log you into the Oracle database.

5. Grant the Oracle user with the necessary authority on the database, where icmadmin is replaced with your user name:

   SQL> GRANT create session, alter session, create table, 
   create view, create procedure, create trigger, create library, 
   create tablespace, alter tablespace, drop tablespace, 
   execute any procedure, unlimited tablespace, create public synonym, 
   drop public synonym, create sequence to icmadmin;  

6. Grant Oracle user the required privileges, where icmadmin is replaced with your user name:

   SQL> grant select on dba_pending_transactions to icmadmin;
   SQL> grant connect, resource to icmadmin;
   SQL> grant insert any table to icmadmin;

   Note: The insert privilege is required only to import the database during WebSphere Portal Express configuration. After configuring WebSphere Portal Express, this privilege can be revoked, if required.
7. Connect to the Feedback database:

   SQL> connect
   user-name: username/password@dbname

   where username is an existing administrative user in the database. For example, system/manager@fdbkdb will log you in to the fdbkdb database.

8. Grant the Feedback user the required privileges:

   SQL> grant select on dba_pending_transactions to feedback;
   SQL> grant connect, resource, create session to feedback;

9. Connect to the LikeMinds database:

   SQL> connect
   user-name: username/password@dbname

   where username is an existing administrative user in the database. For example, system/manager@lmdb will log you into the lmdb database.

10. Grant LikeMinds user the required privileges:

    SQL> grant select on dba_pending_transactions to lmdbusr;
    SQL> grant connect, resource, create session to lmdbusr;
    SQL> grant insert any table to lmdbusr;

    Note: The insert privilege is required only to import the database during WebSphere Portal Express configuration. After configuring WebSphere Portal Express, this privilege can be revoked, if desired.
11. If you are using Oracle 10g with WebSphere Application Server Version 6.0 or higher, refer to the following technote for additional information on Oracle database configuration: http://www-1.ibm.com/support/docview.wss?uid=swg21196663.
12. Log out of the SQL command line tool by entering SQL> exit.