19 Getting Started with Oracle Messaging Gateway

Loading Database Objects into the Database

Using SQL*Plus, run ORACLE_HOME/mgw/admin/catmgw.sql as user SYS as SYSDBA. This script loads the database objects necessary for Messaging Gateway, including roles, tables, views, object types, and PL/SQL packages. It creates public synonyms for Messaging Gateway PL/SQL packages. It creates two roles, MGW_ADMINISTRATOR_ROLE and MGW_AGENT_ROLE, with certain privileges granted. All objects are owned by SYS.

Modifying listener.ora for the External Procedure (Solaris Operating System 32-Bit Only)

Static service information for the listener is not necessary on the Windows operating system.

You must modify listener.ora so that the Messaging Gateway PL/SQL packages can call the external procedure.

1. Verify that the default Inter-process Communication (IPC) protocol address for the external procedures is set.

   LISTENER = (ADDRESS_LIST=
   (ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))
         .
         .
         .
   
   

2. Add static service information for the listener in step 1. This involves setting a SID_DESC for the listener. Within the SID_DESC, the parameters described in Table 19-1 are important to Messaging Gateway and must be specified according to your own situation.

JRE_HOME/lib/PLATFORM_TYPE/server
ORACLE_HOME/lib

Example 19-1 adds SID_NAME mgwextproc to a listener.ora file.

# Add a SID_DESC
SID_LIST_LISTENER= (SID_LIST=
(SID_DESC =
   (SID_NAME= mgwextproc)
   (ENVS="LD_LIBRARY_PATH=JRE_HOME/lib/sparc/server:ORACLE_HOME/lib")
   (ORACLE_HOME=ORACLE_HOME)
   (PROGRAM = extproc))
      .
      .
      .

Modifying tnsnames.ora for the External Procedure (Solaris Operating System 32-Bit Only)

For the external procedure, configure a net service name MGW_AGENT in tnsnames.ora whose connect descriptor matches the information configured in listener.ora, as shown in Example 19-2. The net service name must be MGW_AGENT (this value is fixed). The KEY value must match the KEY value specified for the IPC protocol in listener.ora. The SID value must match the value specified for SID_NAME of the SID_DESC entry in listener.ora.

MGW_AGENT = 
(DESCRIPTION= 
   (ADDRESS_LIST= (ADDRESS= (PROTOCOL=IPC)(KEY=EXTPROC))) 
   (CONNECT_DATA= (SID=mgwextproc) (PRESENTATION=RO)))

Setting Up a mgw.ora Initialization File

The Messaging Gateway initialization file ORACLE_HOME/mgw/admin/mgw.ora is a text file. The Messaging Gateway external procedure uses it to get initialization parameters to start the Messaging Gateway agent. Copy ORACLE_HOME/mgw/admin/sample_mgw.ora to mgw.ora and modify it according to your situation.

The following procedure sets environment variables and other parameters required for all applications of Messaging Gateway:

1. Windows Operating System Only: Set the MGW_PRE_PATH variable. Its value is the path to the jvm.dll library:

   set MGW_PRE_PATH = JRE_HOME\bin\client
   
   

   This variable is prepended to the path inherited by the Messaging Gateway agent process.

2. Set CLASSPATH to include at least the following:

   • Messaging Gateway classes:

     ORACLE_HOME/mgw/classes/mgw.jar
     
     

   • JRE runtime classes:

     JRE_HOME/lib/rt.jar
     
     

   • Oracle JDBC classes:

     ORACLE_HOME/jdbc/lib/ojdbc14.jar
     
     

   • Oracle internationalization classes:

     ORACLE_HOME/jlib/orai18n.jar
     
     

   • SQLJ runtime:

     ORACLE_HOME/sqlj/lib/runtime12.jar
     
     

   • Java Message Service (JMS) interface

     ORACLE_HOME/rdbms/jlib/jmscommon.jar
     
     

   • Oracle JMS implementation classes

     ORACLE_HOME/rdbms/jlib/aqapi13.jar
     
     

   • Java transaction API

     ORACLE_HOME/jlib/jta.jar
     
     

   • Any additional classes needed for Messaging Gateway to access non-Oracle messaging systems

     
     

     See Also: "Setting Up Non-Oracle Messaging Systems"

     
     
     
     

     Note: Replace ORACLE_HOME with the appropriate, spelled-out value. Using $ORACLE_HOME, for example, does not work. Users of the Windows operating system must set CLASSPATH using the Windows operating system path syntax.

     
     

Creating an Oracle Messaging Gateway Administration User

To perform Messaging Gateway administration work, a database user must be created with MGW_ADMINISTRATOR_ROLE privileges, as shown in Example 19-3.

CREATE USER admin_user IDENTIFIED BY admin_password;
GRANT CONNECT, RESOURCE to admin_user;
GRANT MGW_ADMINISTRATOR_ROLE to admin_user;

Creating an Oracle Messaging Gateway Agent User

To establish the Messaging Gateway agent connection back to the database, a database user with MGW_AGENT_ROLE privileges must be created, as shown in Example 19-4.

CREATE USER agent_user IDENTIFIED BY agent_password;
GRANT CONNECT, RESOURCE to agent_user;
GRANT MGW_AGENT_ROLE to agent_user;

Configuring Oracle Messaging Gateway Connection Information

After the Messaging Gateway agent user is created, the administration user uses DBMS_MGWADM.DB_CONNECT_INFO to configure Messaging Gateway with the username, password, and database connect string used by the Messaging Gateway agent to connect back to the database, as shown in Example 19-5. Use the Messaging Gateway username and password that you created in "Creating an Oracle Messaging Gateway Agent User". The database connect string parameter can be set to either a net service name in tnsnames.ora (with IPC protocol for better performance) or NULL. If NULL, then the oracle_sid parameter must be set in mgw.ora.

For Oracle Database release 10.1, always specify a not NULL value for the database connect string parameter when calling DBMS_MGWADM.DB_CONNECT_INFO.

connect admin_user/admin_password
exec dbms_mgwadm.db_connect_info('agent_user','agent_password', 'agent_database');

Configuring Oracle Messaging Gateway in a RAC Environment

The DBMS_MGWADM.STARTUP procedure submits a job queue job that starts the Messaging Gateway agent external process when the job is executed. You can use the instance and force parameters to control the job and instance affinity. By default the job is set up so that it can be run by any instance.

Setting Up for TIB/Rendezvous

Running as a TIB/Rendezvous Java client application, the Messaging Gateway agent requires TIB/Rendezvous software to be installed on the computer where the Messaging Gateway agent runs. In this section TIBRV_HOME refers to the installed TIB/Rendezvous software location.

On the Solaris operating system, LD_LIBRARY_PATH in the entry for Messaging Gateway must include TIBRV_HOME/lib for the agent to access TIB/Rendezvous shared library files.

On the Windows operating system, you are not required to modify listener.ora. But the system environment variable PATH must include TIBRV_HOME\bin.

MGW_PRE_PATH must include the directory that contains the TIB/Rendezvous license ticket file (tibrv.tkt), which usually is located in TIBRV_HOME/bin.

CLASSPATH must include the TIB/Rendezvous jar file TIBRV_HOME/lib/tibrvj.jar. If you use your own customized TIB/Rendezvous advisory message callback, then the location of the callback class must also be included.

You can set the following Java properties to change the default setting:

• oracle.mgw.tibrv.encoding

• oracle.mgw.tibrv.intraProcAdvSubjects

• oracle.mgw.tibrv.advMsgCallback

  
  

  See Also: "Understanding the mgw.ora Initialization File"

  
  

setJavaProp oracle.mgw.tibrv.encoding=ISO8859_1
setJavaProp oracle.mgw.tibrv.intraProcAdvSubjects=_RV.>
setJavaProp oracle.mgw.tibrv.advMsgCallback=MyadvCallback

Setting Up for WebSphere MQ Base Java or JMS

The WebSphere MQ client and WebSphere MQ classes for Java and JMS must be installed on the computer where the Messaging Gateway agent runs. In this section MQ_HOME refers to the location of the installed client. On the Solaris operating system, this location is always /opt/mqm. On the Windows operating system, the installed location can vary.

No extra modification of listener.ora is necessary for Messaging Gateway to access WebSphere MQ.

When using WebSphere MQ Base Java (non-JMS) interface, set CLASSPATH to include at least the following (in addition to those in "Setting Up a mgw.ora Initialization File"):

• MQ_HOME/java.101/lib/com.ibm.mq.jar

• MQ_HOME/java.101/lib/connector.jar

When using WebSphere MQ JMS interface, set CLASSPATH to include at least the following (in addition to those in "Setting Up a mgw.ora Initialization File"):

• MQ_HOME/java.101/lib/com.ibm.mqjms.jar

• MQ_HOME/java.101/lib/com.ibm.mq.jar

• MQ_HOME/java.101/lib/connector.jar

mgw.ora Initialization Parameters

The initialization parameters are typically specified by lines having a "name=value<NL>" format where name represents the parameter name, value represents its value and <NL> represents a new line.

Specifies the directory where the Messaging Gateway log/trace file is created.

log_directory = value

ORACLE_HOME/mgw/log

log_directory = /private/mgwlog

Specifies the level of logging detail recorded by the Messaging Gateway agent. The logging level can be dynamically changed by the dbms_mgwadm.set_log_level API while the Messaging Gateway agent is running. Oracle recommends that log level 0 (the default value) be used at all times.

log_level = value

0 for basic logging; equivalent to dbms_mgwadm.BASIC_LOGGING

1 for light tracing; equivalent to dbms_mgwadm.TRACE_LITE_LOGGING

2 for high tracing; equivalent to dbms_mgwadm.TRACE_HIGH_LOGGING

3 for debug tracing; equivalent to dbms_mgwadm.TRACE_DEBUG_LOGGING

log_level = 0

mgw.ora Environment Variables

Because the Messaging Gateway process environment is not under the direct control of the user, certain environment variables should be set using the initialization file. The environment variables currently used by the Messaging Gateway agent are CLASSPATH, MGW_PRE_PATH, and ORACLE_SID.

Environment variables such as CLASSPATH and MGW_PRE_PATH are set so the Messaging Gateway agent can find the required shared objects, Java classes, and so on. Environment variables are specified by lines having a "set env_var= value<NL>" or "setenv env_var=value<NL>" format where env_var represents the name of the environment variable to set, value represents the value of the environment variable, and <NL> represents a new line.

Used by the Java Virtual Machine to find Java classes needed by the Messaging Gateway agent for propagation between Oracle Streams AQ and non-Oracle messaging systems.

set CLASSPATH=value

set CLASSPATH=ORACLE_HOME/jdbc/lib/ojdbc14.jar:JRE_HOME/lib/rt.jar:
ORACLE_HOME/sqlj/lib/runtime12.jar:ORACLE_HOME/jlib/orai18n.jar:ORACLE_HOME/mgw
/classes/mgw.jar:ORACLE_HOME/rdbms/jlib/jmscommon.jar:ORACLE_HOME/rdbms/jlib/aq
api13.jar:ORACLE_HOME/jlib/jta.jar:/opt/mqm/java.101/lib/com.ibm.mq.jar:/opt/mqm/ja
va/lib/com.ibm.mqjms.jar:/opt/mqm/java.101/lib/connector.jar

Appended to the front of the path inherited by the Messaging Gateway process. For the Windows operating system, this variable must be set to indicate where the library jvm.dll is found.

set MGW_PRE_PATH=value

set MGW_PRE_PATH=JRE_HOME\bin\client

Can be used when a service name is not specified when configuring Messaging Gateway.

set ORACLE_SID=value

set ORACLE_SID=my_sid

mgw.ora Java Properties

You must specify Java system properties for the Messaging Gateway JVM when working with TIB/Rendezvous subjects. You can use the setJavaProp parameter of the Messaging Gateway initialization file for this. Java properties are specified by lines having a "setJavaProp prop_name=value<NL>" format, where prop_name represents the name of the Java property to set, value represents the value of the Java property, and <NL> represents a new line character.

This Java property represents the maximum number of messages propagated in one transaction. It serves as a default value if the Messaging Gateway subscriber option, MsgBatchSize, is not specified. If altered from the default, then consideration should be given to the expected message size and the Messaging Gateway agent memory (see max_memory parameter of DBMS_MGWADM.alter_agent). The minimum value of this Java property is 1, the maximum is 100, and the default is 30.

setJavaProp oracle.mgw.batch_size=value

setJavaProp oracle.mgw.batch_size=10

This parameter specifies the time (in milliseconds) that must elapse between polls for available messages of a propagation source queue. The default polling interval used by Messaging Gateway is 5000 milliseconds (5 seconds).

setJavaProp oracle.mgw.polling_interval=value 

setJavaProp oracle.mgw.polling_interval=1000 

This parameter specifies the character encoding to be used by the TIB/Rendezvous messaging system links. Only one character set for all configured TIB/Rendezvous links is allowed due to TIB/Rendezvous restrictions. The default is ISO 8859-1 or the character set specified by the Java system property file.encoding.

setJavaProp oracle.mgw.tibrv.encoding=value 

setJavaProp oracle.mgw.tibrv.encoding=ISO8859_1 

Used for all TIB/Rendezvous messaging system links, this parameter specifies the names of system advisory subjects that present on the intraprocess transport.

setJavaProp oracle.mgw.tibrv.intraProcAdvSubjects=
advisorySubjectName[:advisorySubjectName]

setJavaProp oracle.mgw.tibrv.intraProcAdvSubjects=_RV.>

Used for all TIB/Rendezvous messaging system links, this parameter specifies the name of the Java class that implements the TibrvMsgCallback interface to handle system advisory messages. If it is not specified, then the default system advisory message handler provided by Messaging Gateway is used, which writes system advisory messages into Messaging Gateway log files. If it is specified, then the directory where the class file is stored must be included in the CLASSPATH in mgw.ora.

setJavaProp oracle.mgw.tibrv.advMsgCallback=className

setJavaProp oracle.mgw.tibrv.advMsgCallback=MyAdvCallback

mgw.ora Comment Lines

Comment lines are designated with a # character as the first character of the line.