Configuring Oracle 8i Release 3 (8.1.7) for use with WebSphere Application Server

This article describes how to create the Oracle users required by WebSphere Application Server. The procedures in this article assume that you have installed Oracle 8i.

Perform the following steps to configure Oracle 8i for use with WebSphere Application Server:

  1. Ensure that you are logged in as the user oracle.
  2. Edit the initialization file $ORACLE_HOME/dbs/inityour_SID.ora as follows:
    • Ensure that the line open_cursors = 220 appears in the file. (The value for this parameter must be 220.)
    • Ensure that the value for the processes parameter is sufficient for your database by reading the information within the inityour_SID.ora file. To increase the value of this parameter, add comment markers to or remove comment markers from the specific lines related to processes within the file.
  3. Restart your Oracle database by entering the following commands:
    $ svrmgrl
    SVRMGR> connect internal
    SVRMGR> startup

    Note: You might need to stop the database before you are able to restart it. To stop the database, enter the following commands:

    $ svrmgrl
    SVRMGR> connect internal
    SVRMGR> shutdown
  4. Ensure that the Oracle listener is started or start it by entering the following commands:
    $ lsnrctl
    LSNRCTL> start
  5. You must create the Oracle users EJSADMIN and EJB required by WebSphere Application Server. You might or might not want to grant user EJSADMIN dba authority. Create the users EJSADMIN and EJB with the proper authorities by entering the following commands using these values: SYSTEM is a user account created by the Oracle Database Configuration Assistant; manager is the password for the SYSTEM account created by the Oracle Database Configuration Assistant; EJSADMIN_password is the password you assign to the user EJSADMIN.

    If you do want to grant dba authority to the user EJSADMIN, enter the following commands:

    $ sqlplus SYSTEM/manager
    SQL> create user EJSADMIN identified by EJSADMIN_password;
    SQL> grant connect, resource, dba to EJSADMIN;
    SQL> create user EJB identified by EJB;
    SQL> grant connect, resource to EJB;
    SQL> quit

    If you do not want to grant dba authority to the user EJSADMIN, enter the following commands:

    $ sqlplus SYSTEM/manager
    SQL> create user EJSADMIN identified by EJSADMIN_password quota 100M \
    on SYSTEM;
    SQL> create user EJB identified by EJB quota 100M on USERS;
    SQL> grant connect, resource to EJSADMIN;
    SQL> grant connect, resource to EJB;
    SQL> quit
  6. If any of your applications use JTA datasources, enter the following commands using these values: SYS is a user account created by the Oracle Database Configuration Assistant; change_on_install is the password for the SYS account created by the Oracle Database Configuration Assistant.
    $ sqlplus SYS/change_on_install
    SQL> grant select on dba_pending_transactions to EJB;
    SQL> quit
  7. Test access to the new database with the user ID EJSADMIN by doing the following:
    1. Enter the following command:
      $ sqlplus ejsadmin/EJSADMIN_password

      A message is displayed indicating a successful connection.

    2. Enter the following command to log out as the user EJSADMIN:
      $ exit