3
Post Installation Tasks

This chapter describes tasks that you need to complete following the Oracle Message Broker installation. Some of these tasks are optional, since different installations can use different drivers.

Update Path for the JRE

Assure that the proper version of the JRE is installed on your system, and that your PATH is set appropriately. If you have several versions of the JRE on your system, make sure that first one found in your path is the version that corresponds to the version installed with the Oracle Message Broker (see Table 1-2 for details on the supported JRE versions).

The Oracle Message Broker Installer installs the JRE in the directory, %OMB_HOME%\jdk for Windows NT, and it sets the path in the ombenv environment scripts in the directory %OMB_HOME%\bin to use the supplied JRE.

Directory Installation and Configuration

Oracle Message Broker requires an LDAP Directory to handle administrative functions. Oracle Message Broker supports two LDAP Directory products:

Oracle Internet Directory (OID) Release 2.0.6
Netscape Directory Server (running on a Windows NT system)

The LDAP Directory needs to be installed on a system available to Oracle Message Broker and configured for use with Oracle Message Broker. This section covers directory installation and configuration.

You can install the LDAP Directory on the same system as Oracle Message Broker, or on a separate system.

Oracle Internet Directory Installation and Configuration

Oracle Internet Directory is available from Oracle. Refer to the following web page for information on Oracle Internet Directory,

http://www.oracle.com/database/oid

Refer to the following documents for more information on installing Oracle Internet Directory:

Oracle8i Installation Guide Release 2.0 (8.1.7)
Oracle Internet Directory Release Notes

Supplying the Directory Bind DN

All of the Oracle Message Broker commands that access the LDAP Directory, including those used during the installation process require that a bind DN and a password be supplied.

For Oracle Internet Directory, the default bind DN is: "cn=orcladmin" and the default password is: "welcome". The bind DN, "cn=orcladmin" is the default super user bind DN, and therefore has super user privileges.

It is recommended that users create user and group entries in the directory and use the bind DN and password corresponding to those non-super users entries. Setting up user and group entries requires knowledge of LDAP and the LDAP server specific tools such as oidadmin.

Only the LDAPSchema command and possibly the InitDir command, depending on the directory setup, require super user privileges (see "Directory Configuration" for details on these commands). For details on the types of users that one might need to create when working with Oracle Message Broker, see the section, "Security Roles" in the Security Chapter in the Oracle Message Broker Administration Guide.

Using Oracle Message Broker commands, there are three ways to supply the bind DN and the password:

At the prompt, when running a command, such as InitDir.
Using the command-line options: -D and -w.
By directly setting JNDI properties. If you set JNDI properties, then to use the values you set when running an Oracle Message Broker command, either use the command-line option -noauth or supply no values in the supplied authentication prompt, and press the continue button.

The JNDI Java properties for setting security options are:

java.naming.security.principal
java.naming.security.credentials
java.naming.security.authentication=simple

Netscape Directory Server Installation

Netscape Directory Server is available from Netscape. Refer to the following web page for information on obtaining Netscape Directory Server,

http://www.iplanet.com/products

After you purchase the Netscape Directory Server, install it on a Windows NT system. The following instructions outline the installation procedures. For detailed instructions on installing and running the Netscape Directory Server, refer to the product documentation.

To install Netscape Directory Server, perform the following steps (these steps are for release 4.0; the steps may be different for newer releases):

After downloading the Netscape Directory Server, double click on the .zip file and extract it into a folder on your system.
Close all running programs and the run the installer, setup.exe.
On the installer dialogs, select all the defaults until you reach the dialog, "Directory Server 4.0 Server Settings". In this dialog, enter your desired suffix information. For example, the suffix could be o=us.oracle.com. The suffix needs to match the suffix you supply on the Suffix dialog when you install. On the next dialog, "Directory Server 4.0 Netscape Configuration Directory Server Administration", select a password to access the directory client tool. Remember the password you select; you will not be able to use the Netscape administration client if you forget the password.
On the dialog, "Directory Server 4.0 Manager Settings", select a password which has at least eight characters. This password allows you to set permissions to gain access to the directory.
Continue with the installation, selecting the defaults on the remaining dialogs.
Reboot the system to finish the installation. After rebooting, the Netscape Directory Server should be running. You can check this by viewing the status of the Netscape Directory Server in the Services screen. The status should indicate "started". To check this, from the Start Menu, select Settings>Control Panel>Services.

Netscape Directory Server Schema Version Update

After the LDAP directory is installed, perform the following steps:

Start the Netscape LDAP directory (refer to the Netscape Directory Server documentation for information on starting the directory server).
Start the Netscape Console and double click on the entry for your LDAP host on the Console tab.
Expand "Server Group" and then double click on "Directory Server".
In the new, "Netscape Directory Server" window, click on the "Configuration" tab.
Click on the Database entry and then click the Settings tab. This lists all the available naming contexts.
Click on the "Add" button and type in the suffix "cn=OracleSchemaVersion".
Save the changes and exit the Netscape Console.

Directory Configuration

After the LDAP Directory and Oracle Message Broker are both installed, you need to perform several configuration tasks on the directory. The following tasks use tools installed with Oracle Message Broker. These tools modify the directory and require an active directory server. The directory modifications support the Oracle Message Broker administrative functions.

After the LDAP Directory and Oracle Message Broker are both installed, perform the following steps:

Start the LDAP Directory. If you are using the Netscape Directory Server, refer to the Netscape Directory Server documentation for information on starting the directory server.
Assure that the proper version of the JDK is installed on your system. If you have several versions of the JDK on your system, make sure that first one found in your path is the version that the Oracle Message Broker requires (see Table 1-2 for details on the required JDK version).
Perform the following steps to modify the directory schema to support the Oracle Message Broker:
1. Set the environment for your system:
  
  On Windows NT run the shell command:
```
> C:%ORACLE_HOME%\omb\2.0\bin\ombenv.bat
```
  The Oracle Message Broker installation creates the startup script ombenv.bat.
1. Update the directory schema using the LDAPSchema command. This command is found in %ORACLE_HOME\omb\2.0\bin. Use LDAPSchema as follows:
```
> LDAPSchema [options]
```
  where Table 3-1 shows the available options.
  
  For example, to modify the LDAP schema for the LDAP Directory running on the host named system1, and the default port number, 389, use the command:
```
> LDAPSchema -h "system1" 
```
  If LDAPSchema prints the following message, you need to run catalog.sh, as described in step 4, :
```
### ATTENTION: The attribute "orcloasentrytype" is not searchable. 
Please run "catalog.sh" on OiD to make this attribute searchable
```

Table 3-1 LDAPSchema Command Line Options

Option	Description
-D auth_dn	The auth_dn supplies the DN to use for user name authentication. The default Authentication DN for the Netscape Directory Server is: cn=Directory Manager The directory administrator should be able to supply the Authentication DN if the default value has been changed.
-errorlevel level	Set the error reporting level. The parameter level is set to an integer value in the range 1-4: 1 - print error message for the top exception 2 - print error messages for all linked exceptions 3 - print stack trace for the top exception 4 - print stack trace for all linked exceptions The default value for errorlevel is 2.
-h host-name	The host-name is the host where the directory is installed. Default value: localhost
-noauth	Specifies that LDAP authentication is not required on the LDAP server.
-p port	The port is the port used to access the directory on the specified host. Default value: 389
-P wallet_password	Specifies the wallet password. This is ignored if the value of -U is 0 or 1.
-ldapv2	Use this option when the LDAP Directory only supports LDAP version 2. Default value: `LDAPSchema` defaults to support for LDAP version 3.
-U value	Specifies if SSL is used, and the authentication level. Valid values are: 0, 1, 2, and 3. `0` - no SSL. This is the default if -U is not specified. `1` - SSL with no authentication. `2` - SSL with server-side authentication. `3` - SSL with server-side and client-side authentication.
-version	Provides version information. Use -fullVersion for detailed version information.
-w auth_passwd	Supplies a password, auth_passwd, for authentication on the LDAP server. The directory administrator should be able to supply the password if you do not know the password value for your directory.
-W wallet_path	Specifies the path to an exported wallet file. This is ignored if the value of -U is 0 or 1.

Note 1:
If the security options -D, -noauth, or -w are not used, LDAPSchema prompts for an authentication DN and a password.

Note 2:
If the LDAP Directory has authentication enabled, then to use the LDAPSchema command, you need to enter the directory administrator's entry DN and password.

Note 3:
The LDAPSchema command creates an LDAP Directory entry, cn=OracleSchemaVersion at the root. This entry contains the attribute, orclProductVersion, defining the version number of the Oracle Message Broker LDAP schema. LDAPSchema updates the LDAP schema only if the entry cn=OracleSchemaVersion does not exist, or, if the value for orclProductVersion is lower than the current version for the LDAPSchema command.

Note 4::
Options that do not list a default value have no default value.

Modify the directory for the Oracle Message Broker suffix with the InitDir command. This command is found in %ORACLE_HOME\omb\2.0\bin. Use InitDir as follows:

> InitDir [options]

where Table 3-2 shows the available options.

For example, to initialize the LDAP Directory running on the host named system1, and the default port number, 389, use the command:

> InitDir -h "system1" -b "o=us.oracle.com" -ou "sales"

This assumes that the directory is being initialized for Oracle Message Broker from the root specified with the -band -ou options.

Table 3-2 InitDir Command Line Options

Option	Description
-b base_dn	Create all entries under the specified base_dn. The DN specified for the base_dn must exist in the directory.
-c country	Specifies the country to use for the root naming context
-D auth_dn	The auth_dn supplies the DN to use for user name authentication. The default Authentication DN for the Netscape Directory Server is: cn=Directory Manager The administrator should be able to supply the value if the default value has been changed.
-errorlevel level	Set the error reporting level. The parameter level is set to an integer value in the range 1-4: 1 - print error message for the top exception 2 - print error messages for all linked exceptions 3 - print stack trace for the top exception 4 - print stack trace for all linked exceptions The default value for errorlevel is 2.
-h host-name	The host-name is the host where the directory is installed. Default value: localhost
-noauth	Specifies that LDAP authentication is not required on the LDAP server.
-o org	Specifies the organization to use for the root naming context.
-ou org-unit	Specifies the organizational unit to use for the root naming context.
-p port	The port is the port used to access the directory on the specified host. Default value: 389
-P wallet_password	Specifies the wallet password. This is ignored if the value of -U is 0 or 1.
-U value	Specifies if SSL is used, and the authentication level. Valid values are: 0, 1, 2, and 3. `0` - no SSL. This is the default if -U is not specified. `1` - SSL with no authentication. `2` - SSL with server-side authentication. `3` - SSL with server-side and client-side authentication.
-ldapv2	Use this option when the LDAP Directory only supports LDAP version 2. The default, without this option is support for LDAP version 3.
-version	Provides version information. Use -fullVersion for detailed version information.
-w auth_passwd	Supplies a password, auth_passwd, for authentication on the LDAP server.
-W wallet_path	Specifies the path to an exported wallet file. This is ignored if the value of -U is 0 or 1.

Note 1:
The values you select for the -c, -o, and -ou options to InitDir should match the LDAP base naming context information that you supplied on the Suffix Information screen while running the Oracle Message Broker installer.

Note 2:
If the security options -D, -noauth, or -w are not used, InitDir prompts for an authentication DN and a password.

Note 3:
If the LDAP Directory has authentication enabled, then you need to enter the directory administrator's entry DN and password to use the InitDir command.

Note 4::
Options that do not list a default value have no default value.

Make the Oracle Internet Directory attributes searchable.

Note:
Only perform this step when the LDAPschema command described in step 2 prints the following message:
ATTENTION: The attribute "orcloasentrytype" is not searchable. Please run "catalog.sh" on OiD to make this attribute searchable.

LDAPSchema prints this message when there is data in the directory which uses the attribute `orcloasentrytype' and `orcloasentrytype' was not cataloged. In this case, LDAPSchema cannot catalog the attribute and catalog.sh must be run manually.

On the system where Oracle Internet Directory is installed and running, issue the commands:

> cd %ORACLE_HOME%\ldap\bin
> catalog.sh -connect "connect_string" -add -attr "orcloasentrytype"

where:

connect_string

Specifies the Net8 connect descriptor for connecting to the Database Server.

Enter the password when the catalog.sh command prompts you. The default password is ods, which is the default OID Database Server password. If you change the password using oidpasswd before running catalog.sh, use the new password, rather than the default password.

Directory Configuration Notes

It is possible that the Oracle Internet Directory may need to be restarted after running catalog.sh (see step 4 for information on running catlog.sh). It is also possible for step 4 to not fully complete its actions. If step 4 does not fully complete its actions, directory operations, including use of AdminUtil or ombadmin may report the following error message:

DSA unwilling to perform: operation not supported

The following steps provide a workaround for this problem:

Run the following commands:

catalog.sh -connect connect-string -delete -attr orcloasentrytype
catalog.sh -connect connect-string -add -attr orcloasentrytype

where: connect-string specifies the Net8 connect descriptor for connecting to the Database Server.

Shutdown the oidldapd instance(s) using oidctl.
Shutdown oidmon.
```
oidmon connect=connect-string stop
```
Shutdown the Database Server.
Start the Database Server.
Start oidmon using the command:
```
oidmon connect=connect-string start
```
Start the oidldapd instance(s) using oidctl.

Oracle Advanced Queuing Configuration (Optional)

This section covers the configuration steps for using the Oracle 8i Advanced Queuing feature with the Oracle Message Broker. Perform the steps in this section if you are using Oracle Message Broker and the Oracle AQ Driver.

Note:
If you are not using the Oracle Message Broker's Oracle AQ Driver, skip this section.

Prior to configuring the Oracle 8i Database Server for the Oracle Message Broker AQ Driver, you need to purchase and install the Oracle 8i Database Server. Refer to the following site for information on obtaining the Oracle 8i Database Server,

www.oracle.com/products

For information on installing Oracle 8i Database Server, refer to the documentation supplied with the product.

Stop Oracle Internet Directory

If you are running Oracle AQ using the same Oracle 8i Database Server as Oracle Internet Directory, then you need to shutdown both Oracle Internet Directory and the Oracle 8i Database Server. This section covers shutting down Oracle Internet Directory.

Use the OID command oidctl to stop the OID instance. See the Oracle Internet Directory Administrator's Guide for information on oidctl. For example,
```
% oidctl connect=connect_string server=oidldapd instance=1 stop
```
where: connect_string specifies the Net8 connect descriptor for connecting to the Database Server.

Use the OID command oidmon to stop the OID monitor. See the Oracle Internet Directory Administrator's Guide for information on oidmon. For example,

% oidmon connect=connect_string stop

where: connect_string specifies the Net8 connect descriptor for connecting to the 
Database Server.

Stop the Database Server and the Listeners

On the system running the Oracle8i Database Server, perform the following steps:

Stop the Net8 Listeners. To stop Net8 Listeners, use the listener control program:
```
lsnrctl 
lsnrctl> stop
lsnrctl> quit
```
See the Net8 Administrator's Guide for more information on stopping listeners.
Stop the database. To stop the Oracle8i Database Server, navigate to the Oracle8i Database Server home directory and then Start SQL*Plus at the command prompt by typing:
```
> sqlplus
```
Log on as INTERNAL.

At the SQL*Plus prompt, type:

SQL> SHUTDOWN [MODE]

where, MODE is one of the following:

Normal

The Database Server waits for all currently connected users to disconnect and disallows any new connections before shutting down. This is the default mode.

Immediate

The Database Server terminates and rolls back active transactions, disconnects clients, and shuts down.

Configure Database Parameters

The Oracle8i Database Server needs to be configured to support the resource requirements for Oracle Message Broker. Active Oracle Message Brokers consume transactions, sessions, cursors, and processes. Other applications may also use the Database Server and have their own resource needs.

Table 3-3 shows equations that determine the Database Server requirements for Oracle Message Broker. These requirements are in addition to the requirements for any other applications that will use the Database Server. Table 3-3 outlines the parameters needed to support Oracle Message Broker.

Keep the following points in mind when configuring an Oracle8i Database Server:

The DBMS must be restarted when initSID.ora is edited
It is better to be too generous than too conservative when setting limits. The errors that occur when some of these limits are exceeded can be confusing.

The OS kernel may need to be configured to support some of these parameters and the OS may need to be rebooted. Consult the platform specific Oracle8i install guide for details.

Table 3-3 Oracle8i Database Server Parameters Required for Oracle Message Broker

Parameter	Description
AQ_TM_PROCESSES = num_aq	The value of num_aq must .
LICENSE_MAX_ SESSIONS = num_license	The value of num_license must be greater than the following: num_license > num_processes See PROCESSES below for information on the value of num_processes.
OPEN_CURSORS = num_open	The num_open must be, at a minimum: num_open = Max( (2*maxConsumers), numQueues ) * 1.2 Where: maxConsumers is the maximum number of consumers. A consumer is a QueueReceiver or a TopicSubscriber within a JMS session. numQueues is the number of AQ queues configured for the Oracle Message Broker. This equation should determine the maximum number of cursors used by any Oracle Message Broker managed Database Server connection. If other uses require more cursors, then OPEN_CURSORS should be set to the value required.
PROCESSES= num_processes	The num_processes must be, at a minimum: num_processes = (maxPrivate + maxShared + aq_tm_processes) * 1.2 maxPrivate is the sum of the maxPrivateSessions attribute values for all Oracle Message Broker that concurrently use the Database Server. maxShared is the sum of the maxSharedSessions attribute values for all Oracle Message Brokers that concurrently use the Database Server. aq_tm_processes is the value of AQ_TM_PROCESSES from the init.ora file. See chapter 4, "Managing Oracle Processes," in the Oracle 8i Administrator's Guide for more information on managing processes. This assumes use of dedicated Database Servers. If other applications use the same Database Server, their resource needs also must be included.
SESSIONS = num_sessions	The value of num_sessions should be,
TRANSACTIONS = num_trans	The num_trans must be, at a minimum: num_trans = (2 * maxPrivate + maxShared) * 1.2 maxPrivate is the sum of the maxPrivateSessions attribute values for all Oracle Message Broker that concurrently use the Database Server. maxShared is the sum of the maxSharedSessions attribute values for all Oracle Message Broker that concurrently use the Database Server.

Restart the Database Server and the Listeners

On the system running the Oracle8i Database Server supporting AQ, perform the following steps:

Restart the database. To start an Oracle8i Database Server, navigate to the Oracle8i Database Server home directory.
Start SQL*Plus at the command prompt by typing:
```
> sqlplus
```
Log on as INTERNAL.
At the SQL*Plus prompt, type:
```
SQL> STARTUP
```
At the SQL*Plus prompt, type:
```
SQL> EXIT
```
Restart the Net8 Listeners. To stop Net8 Listeners. At the command program type:
```
lsnrctl
lsnrctl> start
lsnrctl> quit
```
See the Net8 Administrator's Guide for more information on starting listeners.

Start Oracle Internet Directory

If you are running Oracle AQ using the same Oracle 8i Database Server as Oracle Internet Directory, then you need to startup both the OID and the Oracle 8i Database Server. This section covers starting OID after the Database Server is up and running.

Use the OID command oidmon to start the OID monitor. See the Oracle Internet Directory Administrator's Guide for information on oidmon. For example,
```
% oidmon connect=connect_string start
```
where:

connect_string

Specifies the Net8 connect descriptor for connecting to the Database Server.
Use the OID command oidctl to start the OID instance. See the Oracle Internet Directory Administrator's Guide for information on oidctl. For example,
```
% oidctl connect=connect_string server=oidldapd instance=1 start
```
where:

connect_string

Specifies the Net8 connect descriptor for connecting to the Database Server.

Initialize AQ

After installing the Oracle Message Broker and installing the Oracle 8i Database Server, perform the following steps. The Oracle 8i Database Server needs to be running to use these scripts. These scripts initialize AQ for use with Oracle Message Broker and provide support to allow the AQ Driver to work with AQ queues and topics.

Navigate to the directory containing Oracle Message Broker AQ administration scripts:
```
> cd %OMB_HOME%\admin\plsql
```

Run the three AQ setup scripts:

> sqlplus system/system_password[@service_name] @step1
> sqlplus system/system_password[@service_name] @step2
> sqlplus aq/aq[@service_name] @step3

where:

system_password

The password for the system administrative user.

service_name

The database service name.

Note1:
The step1.sql script sets the default AQ administrative password to "aq".
If you change the default password in step1.sql, note the changed value.The administrative sample script SetupAQ requires that you supply the password values for AQ.
After installation, the AQ password can be changed using the Database Server Enterprise Manager, or using the Database Server ALTER USER SQL command.

Note 2:
One or more of the following errors messages are expected while running the script step3.sql. You can ignore these error messages.
ORA-00942: table or view does not exist
ORA-04043: xx does not exist
ORA-04043: object xx does not exist

Running the pl/sql script step1.sql is only required if this is the first time that Oracle Message Broker pl/sql support is installed. It creates the user aq with the password aq.

Running the pl/sql script step2 is required. This script does the following:

It grants privileges to user aq
Creates the role ombadmin
Grants privileges to role ombadmin
Creates role ombuser
Grants privileges to role ombuser

Running the pl/sql script step3 is required. This script does the following:

Installs package ombaq in the aq schema
Installs package ombaqadm in the aq schema
Grants execute on ombaq to ombuser, ombadmin
Grants execute on ombaqadm to ombadmin

Removing AQ Queue Tables

The Oracle Message Broker also provides a script to remove the tables and users that are created for AQ. If you need to remove these tables, use the following command to remove the AQ Driver support from the Database Server:

% sqlplus  @uninstall

where:

system_password

The password for the system administrative user.

service_name

The database service name.

Note:
The step1.sql script sets the default AQ administrative password to "aq".
If you change the default password assigned in step1.sql, note the changed value.The administrative sample script SetupAQ requires that you supply the password values for AQ.
After installation, the AQ password can be changed using the Database Server Enterprise Manager, or using the Database Server ALTER USER SQL command.

One or more of the following types of errors are expected while running this script:

ORA-00942: table or view does not exist
ORA-04043: xx does not exist

This uninstall script does the following:

Drops the ombadmin and ombuser roles
Drops the aq user (using the cascade option)

Removes all of the queues and queue tables that exist in the AQ schema

Note:
The unistall script performs these functions only if no queue tables outside of the schema `aq' use the Oracle Message Broker object types. If queue tables outside of the schema `aq' use the Oracle Message Broker object types, executing the uninstall script lists those queue tables, prints an error message, and quits.

MQSeries Installation Tasks (Optional)

This version of the Oracle Message Broker only supports IBM MQSeries V5.1. For details on installing MQSeries, refer to the MQSeries documentation available from IBM and supplied with the MQSeries product.

TIBCO Installation Tasks (Optional)

To use the Oracle Message Broker with the TIBCO Driver you need to install and start up TIB/Rendezvous Release 5.x or TIB/Rendezvous Pro Release 5.x (when using the JDK 1.2 version of Oracle Message Broker, TIB/Rendezvous Pro Release 5.x is required). For information on TIB/Rendezvous installation and administration, refer to the TIB/Rendezvous Administrator's Guide. For more information on TIB/Rendezvous, see the following web site,

http://www.rv.tibco.com/

Asynchronous Component Invocation Installation Tasks (Optional)

If you are using the Oracle Message Broker Asynchronous Component Invocation (ACI), you need to load Oracle Message Broker's client classes in the Oracle Database Server, and grant permissions to the schema in which the EJB executes using the following two commands (replace SCOTT/TIGER with your schema and password):

# grant permissions to SCOTT
sqlplus sys/sys_password @$OMB_HOME/admin/plsql/setupaci.sql SCOTT
# Loading OMB client classes
loadjava -r -g SYS -u SCOTT/TIGER ${OMB_HOME}/classes/ombclt.jar

or on Windows NT systems:

sqlplus sys/sys_password @%OMB_HOME%\admin\plsql\setupaci.sql SCOTT
loadjava -r -g SYS -u SCOTT/TIGER %OMB_HOME%\classes\ombclt.jar

where:

sys_password is the administrative user sys's password.

Note:
Run these commands only once for each schema, prior to deploying EJBs in the schema.

AQ Lite Installation Tasks (Optional)

The Oracle Message Broker AQ Lite Driver requires that Oracle 8i Lite, and the AQ Lite component be installed on the same system as the Oracle Message Broker. This section covers requirements for installing both Oracle 8i Lite and AQ Lite.

Note:
Only Install Oracle 8i Lite and Oracle AQ Lite if you are using the AQ Lite Driver with Oracle Message Broker.

Keep the following in mind when installing AQ Lite:

It is not possible to install Oracle 8i Lite and Oracle Message Broker in the same %ORACLE_HOME% (they use different versions of the Oracle Installer). Make sure that the default %ORACLE_HOME% points the location where Oracle 8i is installed whenever the Oracle Message Broker AQ Lite Driver is used (before staring the Oracle Message Broker or a JMS client).
Set the Oracle Home using the Oracle Home Selector utility, which is shipped as a part of Oracle 8i Lite. The Oracle Home Selector utility allows you to change the default Oracle Home to the one on which Oracle 8i Lite is installed, in the event that it points to a different location (for example, to the location where the Oracle Message Broker is installed).

Install AQ Lite

Oracle 8i Lite's installation only supports an older version of the Oracle Installer, and it is strongly recommended that Oracle 8i Lite be installed before the Oracle Message Broker. The typical option for the Oracle 8i Lite installation does not install the AQ Lite component. Installation of the AQ Lite component is accomplished by performing a custom install of Oracle 8i Lite.

Follow the steps outlined in the Oracle 8i Lite release notes to fully install Oracle 8i Lite, especially the notes in Section 1.1.9, "Oracle Lite JDK Setup", under the subsection, "Setting Variables for JDK 1.2". Maker sure that the %CLASSPATH% includes the AQ Lite jar files: aqcommon.jar, aqoracle.jar, aqlite.jar.

AQ Lite Default Database and User Names

The Oracle 8i Lite Installer installs a default Oracle 8i database, %ORACLE_HOME\oldb40\polite.odb, and creates a default user ('Scott'). You can use the default database and the default user, or create a new database or a new user. the Oracle 8i Lite Users Guide describes creating new users and databases.

Install Oracle Message Broker

Oracle Message Broker should be installed after Oracle 8i Lite and AQ Lite. Install Oracle Message Broker on the same system, but on a different %ORACLE_HOME%.

You can perform the Oracle Message Broker related installation steps at this point, including setting up the environment (using ombenv.bat') and setting up LDAP Directory entries for Oracle Message Broker.

Oracle 8i client side is installed along with the Oracle Message Broker. It is recommended that the TNS listener that is started as part of the Oracle 8i client side be turned off after the Oracle Message Broker installation is complete.

Deploy the AQ Lite Database

A one time deployment operation has to be performed against the database. This is performed using the DeployAQLite command provided in the %ORACLE_HOME%\omb\2.0\bin directory (where %ORACLE_HOME% is the location where Oracle Message Broker 2.0.0.1 was installed).

Use the following option to run DeployAQLite:

DeployAQLite dbname

Where dbname is the name of the database.

For example,

DeployAQLite d:\oralite\oldb40\polite.odb

The DeployAQLite command performs a standalone deployment of the AQ Lite queues created in the database. Messages from AQ Lite queues created in the deployed database cannot be propagated with AQ Lite propagation. If the user needs to deploy AQ Lite in a mode other than standalone, then it is expected that the user will provide a customized script in place of DeployAQLite. For more information refer to the AQ Lite Developers Guide, Section 2, "AQ Lite Deployment".

Add LDAP Entries for the AQ Lite Driver and Queues

Create LDAP entries for the AQ Lite Driver and for AQ Lite queues by editing the sample configuration script,

%ORACLE_HOME\omb\samples\admin\SetupAQLite

where %ORACLE_HOME% is the location where Oracle Message Broker is installed.

Escape the '\' in the path name for the Oracle Lite database with backslahes. For example,

 set AQLITESVR_DB_NAME d:\\orant\\oldb40\\polite.odb;

Escape the '\' in the path name for the empty passwords, in case the Oracle Lite databases is not encrypted. For example,

 set AQLITESVR_DB_PASSWORD \"\";

Reinstallation Limitation

If you need to reinstall Oracle 8i Lite for any reason after Oracle Message Broker has been installed, Oracle 8i Lite installer might end up in an inconsistent state during the reinstallation phase. This can occur when the Oracle 8i installer does not perform a clean deinstall due to more than one %ORACLE_HOME% being available. Overcome this problem by deinstalling Oracle Message Broker and then cleaning up the registry entries associated with the Oracle 8i Lite installer (using the Windows NT regedit tool) and reinstalling Oracle 8i Lite and the Oracle Message Broker.

Migrating Directory Data Between Versions

The Oracle Message Broker provides the utility Migrate10to20 to migrate directory data between versions. Refer to the Oracle Message Broker Administration Guide for information on using Migrate10To20.

Creating an OMB Instance and Using Oracle Message Broker

At this point, the installation for the Oracle Message Broker, the LDAP Directory, and the required providers is complete. The next step is to configure the Oracle Message Broker and to start using the Oracle Message Broker. Refer to Chapter 2, "QuickStart", in the Oracle Message Broker Administration Guide for information on creating an OMB Instance, working with the administrative utilities and the sample administrative scripts, and starting the Oracle Message Broker.

	Normal	The Database Server waits for all currently connected users to disconnect and disallows any new connections before shutting down. This is the default mode.
	Immediate	The Database Server terminates and rolls back active transactions, disconnects clients, and shuts down.

	system_password	The password for the system administrative user.
	service_name	The database service name.

3 Post Installation Tasks

Contents

Update Path for the JRE

Directory Installation and Configuration

Oracle Internet Directory Installation and Configuration

Supplying the Directory Bind DN

Netscape Directory Server Installation

Netscape Directory Server Schema Version Update

Directory Configuration

Table 3-1 LDAPSchema Command Line Options

Table 3-2 InitDir Command Line Options

Directory Configuration Notes

Oracle Advanced Queuing Configuration (Optional)

Stop Oracle Internet Directory

Stop the Database Server and the Listeners

Configure Database Parameters

Table 3-3 Oracle8i Database Server Parameters Required for Oracle Message Broker

Restart the Database Server and the Listeners

Start Oracle Internet Directory

Initialize AQ

Removing AQ Queue Tables

MQSeries Installation Tasks (Optional)

TIBCO Installation Tasks (Optional)

Asynchronous Component Invocation Installation Tasks (Optional)

AQ Lite Installation Tasks (Optional)

Install AQ Lite

AQ Lite Default Database and User Names

Install Oracle Message Broker

Deploy the AQ Lite Database

Add LDAP Entries for the AQ Lite Driver and Queues

Reinstallation Limitation

Migrating Directory Data Between Versions

Creating an OMB Instance and Using Oracle Message Broker

3
Post Installation Tasks