Skip Headers
Oracle Procedural Gateway® for WebSphere MQ Installation and User's Guide,
10g Release 2 (10.2) for Windows

Part Number B16216-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
Go to next page
Next
View PDF

2 Release Information

This chapter contains information that is specific to this release of the gateway. It contains the following sections:

Changes and Enhancements

The following changes and enhancements apply to all releases of the 10g Release 2 (10.2) gateway products.

Changes and Enhancements for 10g Release 2 (10.2)

The following sections describe the changes and enhancements included in this release.

Oracle Server Dependencies

This release of the Oracle Procedural Gateway and Tools for WebSphere MQ requires the latest released patch set for Oracle Database 10g Release 2 (10.2), or for the Oracle database release that you are using.

Changes and Enhancements for 10g Release 2 (10.2)

The following changes and enhancements are for the previous release of the Oracle10g gateway products.

Support for Large Data Buffers

The PL/SQL RAW data type limitation is 32 KB (32767 bytes). For large loads, you must use the TABLE OF RAWS data type. For more information about support for large data buffers, refer to Appendix A.

PGM_UTL Procedures

The following table provides information about PGM_UTL procedures.

Procedure V401 V804 V817 and V901 Oracle10g Release 2
TO_RAW NA PGM_UTL.TO_RAW PGM_UTL8.TO_RAW PGM.TO_RAW
RAW_TO_MQMD NA PGM_UTL.RAW_TO_MQMD PGM_UTL8.RAW_TO_MQMD PGM.RAW_TO_MQMD
RAW_TO_MQPMO NA PGM_UTL.RAW_TO_MQPMO PGM_UTL8.RAW_TO_MQPMO PGM.RAW_TO_MQPMO
RAW_TO_MQGMO NA PGM_UTL.RAW_TO_MQGMO PGM_UTL8.RAW_TO_MQGMO PGM.RAW_TO_MQGMO


Note:

For Oracle10g Release (10.2), the PGM.TO_RAW, PGM.RAW_TO_MQMD, PGM.RAW_TO_MQPMO, and PGM.RAW_TO_MQGMO procedures are added for backward compatibility.

PG4MQ API Prototype Changes

The following table provides information about PG4MQ application programming interface changes.

API V401 Arguments V804 Arguments V817 & V901 Arguments 10g Release 2 Arguments
MQOPEN (MQOD,INT,INT) (RAW,INT,INT) (RAW,INT,INT) (PGM.MQOD,INT,INT)
MQPUT (INT,MQMD,MQPMO,RAW) (INT,RAW,RAW,RAW) (INT,RAW,RAW,RAW) (INT,PGM.MQMD,PGM_MQPMO,RAW) or (INT, PGM.MQMD, PGM_MQPMO, PGM.MQPUT_BUFFER)
MQGET (INT,MQMD,MQGMO,RAW) (INT,RAW,RAW,RAW) (INT,RAW,RAW,RAW) (INT,PGM.MQMD,PGM_MQGMO,RAW) or (INT, PGM.MQMD, PGM.MQGMO, PGM_MQGET_BUFFER)
MQCLOSE (INT,INT) (INT,INT) (INT,INT) (INT,INT)

Refer to Appendix A for the details of APIs.

Heterogeneous Services Architecture

This release of Oracle Procedural Gateway for WebSphere MQ uses the Oracle Heterogeneous Services external procedure component within the Oracle10g server.


See Also:

Refer to Oracle Database Application Developer's Guide - Fundamentals for more information.

Performance Enhancements

Oracle Procedural Gateway for WebSphere MQ contains several internal performance enhancements. This product has shown major improvements in response time and CPU utilization for all relevant address spaces for a variety of workloads compared to version 4 gateways. The actual performance improvement at your site might vary, depending on your installation type and workload.

New PG4MQ Packages

PGM and PGM_UTL8 packages are new in this release. These packages provide new features as well as ensure backward compatibility. Refer toMigration Tips for details of upgrading your existing PL/SQL application programs to use Oracle10g PG4MQ features.

New PG4MQ Deployment Scripts

The following scripts are new in this release:

  • pgm.sql

  • pgmobj.sql

  • pgmdeploy.sql

  • pgmundeploy.sql

The gateway procedures in the PGM package are defined in pgm.sql and PGM_MQ* data type definitions used by the procedures are defined in pgmobj.sql. For complete information about PGM package, PG4MQ gateway procedures, and data type definitions, refer to Appendix A.

Large Payload Support

PG4MQ 10g Release 2 (10.2) supports large payloads or messages longer than 32767 bytes. For more information, refer to the putlongsample.sql and getlongsample.sql sample programs installed with the PG4MQ.

Database Link and Alias Library

A connection to the gateway is established through a database link. From PG4MQ 10g release 2 and later, this database link is no longer associated with each PG4MQ gateway procedural call (for example, PGM.MQPUT@dblink). From 10g release 2 and later, it needs to be defined only once in the MQOD data type used by MQOPEN, and this database link is registered in the object handle returned by the MQOPEN call. Refer to the sample programs installed with the gateway for details. By default, a public database link, pg4mqdepdblink, is created with your default SID when PG4MQ deployment scripts are executed.

Known Restrictions for 10g Release 2

The following restriction is known to exist for this release.

Customizing LOG_DESTINATION

There is a known issue when customizing the gateway initialization file for gateway tracing for MS windows platform. When customizing the path name of LOG_DESTINATION, the delimiter must be double backslashes. For example:

LOG_DESTINATION=C:\\oracle\\product\\10.2.0\\pg4mqs\\pg4mq\\log\\pg4mqs.log

Note:

If LOG_DESTINATION is not defined for MS windows platform, a default name is used and the log is created in ORACLE_HOME\pg4mq\trace directory

Customizing deployment script pgmobj.sql

There is a known issue when customizing the gateway deployment script pgmobj.sql for MS windows platform. When defining the path name of libpg4mq, the delimiter must be backslashes. For example create or replace library libpg4mq as:

CREATE OR REPLACE LIBRARY libpg4mq as 'C:\oracle\product\10.2.0\pg4mqs\bin\orapg4mqs.dll' transactional

or

CREATE OR REPLACE LIBRARY libpg4mq as '$ORACLE_HOME\bin\orapg4mqs.dll' transactional

Known Problems for 10g Release 2

The problems documented in this section are specific to the Oracle Procedural Gateway for WebSphere MQ and are known to exist in this release of the product. These problems will be fixed in a future release. If you have any questions or concerns about these problems, contact Oracle Support Services.

A current list of problems is available online. Contact your local Oracle office for information about accessing this online information.