Skip Headers
Oracle® Application Server Integration InterConnect Adapter for WebSphere MQ Installation and User's Guide
10g Release 2 (10.1.2)
Part No. B14072-01
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents		 Go To Index
Index
Previous
Previous 		Next
Next 		 

2 Installation and Configuration

This chapter describes how to install and configure the WebSphere MQ adapter. It contains the following topics:

2.1 Installing the WebSphere MQ Adapter

The WebSphere MQ adapter must be installed in an existing Oracle home Middle Tier for OracleAS Integration InterConnect 10g Release 2 (10.1.2).

This section describes the following topics:

2.1.1 Preinstallation Tasks

Before installation, ensure that the WebSphere MQ server is installed. If the WebSphere MQ server is running on a remote host, then ensure that the WebSphere MQ client is installed.

For IBM installation guides, refer to the following:

Verify that the WebSphere MQ system is functional before commencing the installation of the WebSphere MQ adapter.

Consult the following guides before installing the WebSphere MQ adapter:

  • Oracle Application Server Installation Guide for information about Oracle Universal Installer startup.

  • Oracle Application Server Integration InterConnect Installation Guide for information on mounting CD-ROMs, software, hardware, and system requirements for OracleAS Integration InterConnect.


Note:

OracleAS Integration InterConnect Hub is installable through the OracleAS Integration InterConnect Hub installation type. You must install the OracleAS Integration InterConnect Hub before proceeding with the WebSphere MQ adapter installation.

2.1.2 Installation Tasks

To install the WebSphere MQ adapter:

  1. In the Available Product Components page of the OracleAS Integration InterConnect installation, select WebSphere MQ adapter, and click Next.

  2. The Set Oracle Wallet Password screen is displayed. Enter and confirm the password on the screen, which will be used to administer OracleAS Integration InterConnect installation. Click Next.

    • Go to step 3, if installing the WebSphere MQ adapter in an OracleAS Middle Tier Oracle home that does not have an InterConnect component already installed. Ensure that the OracleAS Integration InterConnect hub has been installed.

    • Go to step 4, if installing the WebSphere MQ adapter in an OracleAS Middle Tier Oracle home that has an existing InterConnect component. Ensure that it is a home directory to an OracleAS Integration InterConnect component.

  3. The Specify Hub Database Connection page is displayed. Enter information in the following fields:

    • Host Name: The host name of the computer where the hub database is installed.

    • Port Number: The TNS listener port for the hub database.

    • Database SID: The SID for the hub database.

    • Password: The password for the hub database user.

  4. Click Next. The Specify MQSeries Adapter Name page is displayed.

  5. Enter the application to be defined. Blank spaces are not permitted. The default value is myMQSeriesApp.

  6. Click Next. The Specify MQSeries Adapter Usage page is displayed.

  7. Select one of the options and go to the step specified.

    If You Select... Then Click Next and Go to Step...
    Configure for both sending and receiving messages 8
    Configure for sending messages ONLY 8
    Configure for receiving messages ONLY 10


    Note:

    You can change the values for these selections later by editing the parameter settings in the adapter.ini file.

  8. Enter the following information in the Configure Sending Endpoint Information page:

    • WebSphere MQ inbound queue: The URI of the WebSphere MQ queue to which messages are sent.

    • WebSphere MQ inbound log queue: The URI of the WebSphere MQ queue that temporarily stores log records during sending transactions.

    • WebSphere MQ inbound id queue: The URI of the WebSphere MQ queue that is used to store and generate unique (sequential) transaction identifiers for the inbound or sending transactions.


      Note:

      The preceding URIs can only denote queues, not topics.

    The logical WebSphere MQ inbound log queue and the logical WebSphere MQ inbound id queue can refer to the same physical WebSphere MQ queue.

  9. Click Next. The installation screen that appears is based on the selection made in Step 7.

    If You Selected... Then Go to Step...
    Configure for both sending and receiving messages 10
    Configure for sending messages ONLY 11

  10. Enter the WebSphere MQ outbound queue/topic information in the Configure Receiving Endpoint Information page. This is a URI for the WebSphere MQ queue or topic from which messages are received. It is used to listen to incoming messages from WebSphere MQ or as JMS ReplyTo addresses while sending request messages to WebSphere MQ.

  11. Enter the following information on the Define MQSeries Connection Information page:

    • WebSphere MQ Java installation Path: This path specifies the root directory of the WebSphere MQ Java (client) installation, which typically is /opt/mqm/java. During startup, the WebSphere MQ Adapter will try to locate the JAR files (jms.jar, com.ibm.mqjms.jar, com.ibm.mq.jar, and connector.jar) in the lib subdirectory in this path..

    • WebSphere MQ Queue Manager: The name of the WebSphere MQ queue manager to which to connect.

    • WebSphere MQ Client Connection Type: From the list, select the type of connection to make to the WebSphere MQ queue manager. Select Remote to use a client connection (through an WebSphere MQ channel), or select Local to bind to a queue manager running on the same computer as the adapter.

  12. Click Next. The installation page that appears next is based on the selection you made in Step 11.

    If You Selected... Then Go to Step...
    Remote 13
    Local 14

  13. Enter the following information on the Specify MQSeries Client Connect Parameters page:

    • Host Name: The DNS name of the host where the WebSphere MQ queue manager resides.

    • Port Number: The port number to connect to on the MQ Server host. The default port number is 1414. This port is defined when starting the WebSphere MQ listener by the command runmqlsr (for example, runmqlsr -m qmqr -t tcp -p 1415).

    • MQ Series Channel Name: The name of the WebSphere MQ channel to use for the client connection.

  14. Click Next. The Summary page is displayed.

  15. Click Install to install the WebSphere MQ adapter. The adapter is installed in the following directory:

    Platform Directory
    UNIX ORACLE_HOME/integration/interconnect/adapters/Application
    Windows ORACLE_HOME\integration\interconnect\adapters\Application

    You defined the value of Application in Step 4.

  16. Click Exit on the Installation page to exit the WebSphere MQ adapter installation.

2.2 Configuring the WebSphere MQ Adapter

After an WebSphere MQ adapter installation, you can configure it for your needs. The following tables describe the location and details of the configuration files.

Table 2-1 describes the location where the adapter is installed.

Table 2-1 WebSphere MQ Adapter Directory

Platform Directory
UNIX ORACLE_HOME/integration/interconnect/adapters/Application
Windows ORACLE_HOME\integration\interconnect\adapters\Application

Table 2-2 describes the executable files of the WebSphere MQ adapter.

Table 2-2 Executable Files

File Description
start (UNIX) Does not use parameters, starts the adapter.
start.bat (Windows) Does not use parameters, starts the adapter.
stop (UNIX) Does not use parameters, stops the adapter.
stop.bat (Windows) Does not use parameters, stops the adapter.

Table 2-3 describes the WebSphere MQ adapter configuration files.

Table 2-3 Configuration Files

File Description
adapter.ini (UNIX) Consists of all the initialization parameters that the adapter reads at startup.
adapter.ini (Windows) Consists of all the initialization parameters that the adapter reads at startup.
d3l-file.xml One or more D3L XML files that describe the mappings between WebSphere MQ native/binary fixed-structure messages and OracleAS Integration InterConnect Application View messages.

Table 2-4 describes the directories used by the WebSphere MQ adapter.

Table 2-4 Directories

File Description
logs The adapter activity is logged in subdirectories of the logs directory. Subdirectory names take the following form:

timestamp_in_milliseconds

Each time the adapter is run, a new subdirectory is created for the oailog.txt log file.

persistence The messages are made available in this directory. Do not edit this directory or its files.

2.2.1 Using the Application Parameter

Adapters do not have integration logic. The WebSphere MQ adapter has a generic transformation engine that uses metadata from the repository as runtime instructions to perform transformations. The application parameter defines the capabilities of an adapter, such as the messages to be published and subscribed, and the transformations to be performed. The application parameter allows the adapter to retrieve only the relevant metadata from the repository. The application parameter must match the corresponding application name that will be defined in iStudio under the Applications folder.

If you use prepackaged metadata, then import it into the repository and start iStudio to find the corresponding application under the Applications folder. You can use this as the application name for the adapter you are installing.

2.2.2 Ini File Settings

The following are the .ini files used to configure the WebSphere MQ adapter:

2.2.2.1 hub.ini Parameters

The WebSphere MQ adapter connects to the hub database using parameters in the hub.ini file located in the hub directory. Table 2-5 lists the parameter names, descriptions for each parameter, and an example.

Table 2-5 hub.ini Parameters

Parameter Description Example
hub_host The name of the computer hosting the hub database. There is no default value. The value is set during installation. hub_host=mpscottpc
hub_instance The SID of the hub database. There is no default value. The value is set during installation. hub_instance=orcl
hub_port The TNS listener port number for the hub database instance. There is no default value. The value is set during installation. hub_port=1521
hub_username The name of the hub database schema (or user name). The default value is ichub. hub_username=ichub
repository_name The name of the repository that communicates with the adapter. The default value is InterConnectRepository. repository_name=InterConnectRepository

Oracle Real Application Clusters hub.ini Parameters

When a hub is installed on a Oracle Real Application Clusters database, the parameters listed in Table 2-6 represent information on additional nodes used for connection and configuration. These parameters are in addition to the default parameters for the primary node. In Table 2-6, x represents the node number. The number is between 2 and the number of nodes. For example, if the cluster contains 4 nodes, then x can be a value between 2 and 4.

Table 2-6 Real Application Clusters Hub.ini Parameters

Parameter Description Example
hub_hostx The host where the Real Application Clusters database is installed. hub_host2=dscott13
hub_instancex The instance on the respective node. hub_instance2=orcl2
hub_num_nodes The number of nodes in a cluster. hub_num_nodes=4
hub_portx The port where the TNS listener is listening. hub_port2=1521

2.2.2.2 adapter.ini Parameters

The agent component of the WebSphere MQ adapter reads the adapter.ini file at runtime to access WebSphere MQ adapter parameter configuration information. Table 2-7 lists the parameter names, descriptions for each parameter, and examples.

Table 2-7 adapter.ini Parameters

Parameter Description Example
agent_admin_port Specifies the port through which the adapter can be accessed through firewalls.

Possible Value: A valid port number.

Default Value: None.

agent_admin_port=1059
agent_delete_file_cache_at_startup Specifies whether to delete the cached metadata during startup. If any agent caching method is enabled, then metadata from the repository is cached locally on the file system. Set the parameter to true to delete all cached metadata on startup.

Possible Values: true or false.

Default Value: false.

Note: After changing metadata or DVM tables for the adapter in iStudio, you must delete the cache to guarantee access to new metadata or table information.

agent_delete_file_cache_at_startup=false
agent_dvm_table_caching Specifies the Domain Value Mapping (DVM) table caching algorithm.

Possible values:

  • startup: Cache all DVM tables at startup. This may be time-consuming if there are many tables in the repository.

  • demand: Cache tables as they are used.

  • none: No caching. This slows down performance.

Default Value: demand.

agent_dvm_table_caching=demand
agent_log_level Specifies the amount of logging necessary.

Possible values:

0=errors only

1=status and errors

2=trace, status, and errors

Default Value: 1.

agent_log_level=2
agent_lookup_table_caching Specifies the lookup table caching algorithm.

Possible values:

  • startup: Cache all lookup tables at startup. This may be time-consuming if there are many tables in the repository.

  • demand: Cache tables as they are used.

  • none: No caching. This slows down performance.

Default Value: demand.

agent_lookup_table_caching=demand
agent_max_ao_cache_size Specifies the maximum number of application object metadata to cache.

Possible Value: An integer greater than or equal to 1.

Default Value: 200.

agent_max_ao_cache_size=200
agent_max_co_cache_size Specifies the maximum number of common object metadata to cache.

Possible Value: An integer greater than or equal to 1.

Default Value: 100.

agent_max_co_cache_size=100
agent_max_dvm_table_cache_size Specifies the maximum number of DVM tables to cache.

Possible Value: An integer greater than or equal to 1.

Default Value: 200.

agent_max_dvm_table_cache_size=200
agent_max_lookup_table_cache_size Specifies the maximum number of lookup tables to cache.

Possible Value: Any integer greater than or equal to 1.

Default Value: 200.

agent_max_lookup_table_cache_size=200
agent_max_message_metadata_cache_size Specifies the maximum number of message metadata (publish/subscribe and invoke/implement) to cache.

Possible Value: An integer greater than or equal to 1.

Default Value: 200.

agent_max_message_metadata_cache_size=200
agent_max_queue_size Specifies the maximum size internal OracleAS Integration InterConnect message queues can grow.

Possible Value: An integer greater than or equal to 1.

Default Value: 1000.

agent_max_queue_size=1000
agent_message_selector Specifies conditions for message selection when the adapter registers its subscription with the hub.

Possible Value: A valid Oracle Advanced Queue message selector string (like '%,aqapp,%').

Default Value: None.

agent_message_selector=%,aqapp,%
agent_metadata_caching Specifies the metadata caching algorithm.

Possible values:

  • startup: Cache everything at startup. This may be time-consuming if there are many tables in the repository.

  • demand: Cache metadata as it is used.

  • none: No caching. This slows down performance.

Default Value: demand.

agent_metadata_caching=demand
agent_persistence_cleanup_interval Specifies how often to run the persistence cleaner thread in milliseconds.

Possible Value: An integer greater than or equal to 30000 milliseconds.

Default Value: 60000.

agent_persistence_cleanup_interval=60000
agent_persistence_queue_size Specifies the maximum size of internal OracleAS Integration InterConnect persistence queues.

Possible Value: An integer greater than or equal to 1.

Default Value: 1000.

agent_persistence_queue_size=1000
agent_persistence_retry_interval Specifies how often the persistence thread retries when it fails to send an OracleAS Integration InterConnect message.

Possible Value: An integer greater than or equal to 5000 milliseconds.

Default Value: 60000.

agent_persistence_retry_interval=60000
agent_pipeline_from_hub Specifies whether to turn on the pipeline for messages from the hub to the bridge. If you set the pipeline to false, then the file persistence is not used in that direction.

Possible Value: true, false

Default Value: false.

agent_pipeline_from_hub=false
agent_pipeline_to_hub Specifies whether to turn on the pipeline for messages from the bridge to the hub. If you set the pipeline to false, then the file persistence is not used in that direction.

Possible Value: true, false.

Default Value: false.

agent_pipeline_to_hub=false
agent_reply_message_selector Specifies the application instance to which the reply must be sent. This parameter is used if multiple adapter instances exist for the given application and given partition.

Possible Value: A string built using the application name (parameter:application) concatenated with the instance number (parameter:instance_number).

Default Value: None.

If application=aqapp, instance_number=2, then agent_reply_message_selector=recipient_list like '%,aqapp2,%'
agent_reply_subscriber_name Specifies the subscriber name used when multiple adapter instances are used for the given application and given partition. This parameter is optional if only one instance is running.

Possible Value: The application name (parameter:application) concatenated with the instance number (parameter:instance_number).

Default Value: None.

If application=mpapp and instance_number=2, then agent_reply_subscriber_name=mqapp2
agent_subscriber_name Specifies the subscriber name used when this adapter registers its subscription.

Possible Value: A valid Oracle Advanced Queue subscriber name.

Default Value: None.

agent_subscriber_name=mqapp
agent_throughput_measurement_enabled Specifies if the throughput measurement is enabled. Set this parameter to true to turn on throughput measurements.

Default Value: true.

agent_throughput_measurement_enabled=true
agent_tracking_enabled Specifies if message tracking is enabled. Set this parameter to false to turn off tracking of messages. Set this parameter to true to track messages with tracking fields set in iStudio.

Default Value: true.

agent_tracking_enabled=true
agent_use_custom_hub_dtd Specifies whether to use a custom DTD for the common view message when handing it to the hub. By default, adapters use a specific OracleAS Integration InterConnect DTD for all messages sent to the hub.

Set this parameter to true to have the adapter use the DTD imported for the message of the common view instead of the OracleAS Integration InterConnect DTD.

Default Value: None.

agent_use_custom_hub_dtd=false
application Specifies the name of the application to which this adapter connects. This must match the name specified in iStudio while creating metadata.

Possible Value: An alphanumeric string.

Default Value: None.

application=mqapp
encoding Specifies the character encoding for published messages. The adapter uses this parameter to generate encoding information for the encoding tag of transformed OracleAS Integration InterConnect messages. OracleAS Integration InterConnect represents messages internally as XML documents.

Possible Value: A valid character encoding.

Default Value: UTF-8.

When there is no existing encoding in the subscribed message, this parameter will be used to explicitly specify the encoding of the published message. This parameter will be ignored when the encoding already exists in the subscribed message.

encoding=Shift_JIS
external_dtd_base_url Specify the base URL for loading external enitites and DTDs.This specifies to the XML parser to resolve the external entities in the instance document using the given URL.Possible Value: A URL.Default Value: The URL of the current user directory. external_dtd_base_url=file://C:\InterConnect10_1_2\adapters\AQApp\
instance_number Specifies the instance number to which this adapter corresponds. Specify a value only if you have multiple adapter instances for the given application with the given partition.

Possible Value: An integer greater than or equal to 1.

Default Value: None.

instance_number=1
nls_country Specifies the ISO country code. The codes are defined by ISO-3166.

Possible Value: A valid code. A full list of the codes is available at http://www.chemie.fu-berlin.de/diverse/doc/ISO_3166.html

Default Value: US.

Note: This parameter specifies date format and is applicable for the date format only.

nls_country=US
nls_date_format Specifies the format for a date field expressed as a string.

Possible Value: A valid date format pattern as shown in Table 2-8 for the definitions of the format characters.

Default Value: EEE MMM dd HHmmss zzz yyyy.

Date format pattern dd/MMM/yyyy can represent 01/01/2003.

nls_date_format=dd-MMM-yy

Multiple date formats can be specified as num_nls_formats=2

nls_date_format1=dd-MMM-yy

nls_date_format2=dd/MMM/yy

nls_language Specifies the ISO language code. The codes are defined by ISO-639.

Possible Value: A valid code. A full list of these codes is available at http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt

Default Value: en.

Note: This parameter specifies date format and is applicable for the date format only.

nls_language=en
partition Specifies the partition this adapter handles as specified in iStudio.

Possible Value: An alphanumeric string.

Default Value: None.

partition=germany
service_class Specifies the entry class for the Windows service.

Possible Value: oracle/oai/agent/service/AgentService.

Default Value: None.

service_class=oracle/oai/agent/service/AgentService
service_classpath Specifies the class path used by the adapter JVM. If a custom adapter is developed and the adapter is to pick up any additional jar files, then add the files to the existing set of jar files.

Possible Value: A valid PATH setting.

Default Value: None.

This parameter is for Microsoft Windows only.

service_classpath=D:\oracle\oraic\integration\interconnect\lib\oai.jar; D:\oracle\oraic\jdbc\classes12.zip
service_jdk_dll Specifies the Dynamic Link Library(DLL) that the adapter JVM should use.

Possible Value: A valid jvm.dll.

Default Value: jvm.dll.

This parameter is for Microsoft Windows only.

service_jdk_dll=jvm.dll
service_jdk_version Specifies the JDK version that the adapter JVM should use.

Possible Value: A valid JDK version number.

Default Value: 1.4

This parameter is for Microsoft Windows only.

service_jdk_version=1.4
service_max_heap_size Specifies the maximum heap size for the adapter JVM.

Possible Value: A valid JVM heap size.

Default Value: 536870912.

This parameter is for Microsoft Windows only.

service_max_heap_size=536870912
service_max_java_stack_size Specifies the maximum size the JVM stack can grow.

Possible Value: A valid JVM maximum stack size.

Default Value: Default value for the JVM.

This parameter is for Microsoft Windows only.

service_max_java_stack_size=409600
service_max_native_stack_size Specifies the maximum size the JVM native stack can grow.

Possible Value: A valid JVM maximum native stack size.

Default Value: Default value for the JVM.

This parameter is for Microsoft Windows only.

service_max_native_size=131072
service_min_heap_size Specifies the minimum heap size for the adapter JVM.

Possible Value: A valid JVM heap size.

Default Value: 536870912.

This parameter is for Microsoft Windows only.

service_min_heap_size=536870912
service_num_vm_args Specifies the number of service_vm_argnumber parameters specified in JVM.

Possible Value: The number of service_vm_argnumber parameters.

Default Value: None.

This parameter is for Microsoft Windows only.

service_num_vm_args=1
service_path Specifies the environment variable PATH. The PATH variable is set before starting the Java Virtual Machine (JVM). Typically, list all directories that contain necessary DLLs.

Possible Value: A valid PATH environment variable setting.

Default Value: None.

This parameter is for Microsoft Windows only.

service_path=%JREHOME%\bin;D:\oracle\oraic\bin
service_vm_argnumber Specifies any additional arguments to the JVM. For example, to retrieve line numbers in any stack traces, set service_vm_arg1=java.compiler=NONE. If a list of arguments exists, then use multiple parameters as shown in the example, by incrementing the last digit by 1.

Possible Value: A valid JVM arguments.

Default Value: None.

This parameter is for Microsoft Windows only.

service_vm_arg1=java.compiler= NONE

service_vm_arg2=oai.adapter=.aq


Table 2-8 shows the reserved characters used to specify the value of the nls_date_format parameter. Use these characters to define date formats.

Table 2-8 Reserved Characters for the Value of the nls_date_format Parameter

Letter Description Example
G Era designator AD
y Year 1996 or 96
M Month in year July or Jul or 07
w Week in year 27
W Week in month 2
D Day in year 189
d Day in month 10
F Day of week in month Number 2
E Day in week Tuesday or Tue
a a.m./p.m. marker P.M.
H Hour in day (0-23) 0
k Hour in day (1-24) 24
K Hour in a.m./p.m. (0-11) 0
h Hour in a.m./p.m. (1-12) 12
m Minute in hour 30
s Second in minute 55
S Millisecond 978

2.2.2.3 WebSphere MQ Adapter-specific Parameters

Table 2-9 lists the parameters specific to the WebSphere MQ adapter.

Table 2-9 WebSphere MQ Adapter-specific Parameters

Parameter Description Example
bridge_class Specifies the entry class for the WebSphere MQ adapter. A value must be specified and cannot be modified later.

Possible Value: oracle.oai.agent.adapter.technology.TechBridge.

Default Value: None.

bridge_class=oracle.oai.agent.adapter.mq.MQBridge
Encrypted_mq.default. password Specifies the WebSphere MQ (encrypted) password when connecting to the queue manager. Equivalent to the WebSphere MQ environment variable MQ_PASSWORD. The value may be used to verify the identity of the WebSphere MQ adapter.

Default Value: None.

Note: All passwords are stored in Oracle Wallet. Refer to "How do I secure my passwords?" for more details on how to modify and retrieve the password using Oracle Wallet.

Encrypted_mq.default.password=112411071071106510801094108410731070107110811069
mq.default. connection_type Specifies the type of connection to make to an WebSphere MQ queue manager.

Possible Values: bind (local) or client (remote).

Default Value: None.

mq.default.connection_type=client
mq.default. receiver.durable Defines whether or not a durable subscriber should be used to subscribe to the topic. This is used only if the receiver.destination.uri parameter specifies a JMS topic.

Possible Value: Y or N.

Default Value is N.

mq.default.receiver. durable=Y
mq.default. receiver.transacted Specifies whether or not the JMS sessions for the receive URI should be transacted. The JMS session for the sender URI is always transacted.

Possible Value: Y or N.

Default Value: N.

mq.default.receiver. transacted=Y
mq.default. sender.seq_queue.uri Specifies a URI for the WebSphere MQ transaction id (sequence generator) queue used during send transactions. It can refer to the same queue as mq.default.sender.log_queue.uri.

Possible Values: A JMS queue URI.

Default Value: None.

mq.default.sender.log_queue.uri=queue:///OIA.SEQ.QUEUE
mq.default.ccsid Specifies the coded-character-set-ID in use on connections instead of the default.

Possible Values: Refer to table 16 in the WebSphere MQ Using Java Guide.

Default Value: blank (~819).

mq.default.ccsid=1208
mq.default.channel Specifies the name of the WebSphere MQ channel to use for the client connection.

Possible Value: Any valid WebSphere MQ channel name.

Default Value: None.

mq.default.channel=SYSTEM.DEF.SVRCONN
mq.default.event.name Specifies the default event name. This parameter should be used if the bridge will only handle one single fixed event name for outbound messages (from WebSphere MQ) and none of the other options are feasible to use. This parameter requires only one D3L file defined, with an event name exactly matching this hardcoded event name.

Possible Value: A valid OracleAS Integration InterConnect event name.

Default Value: None.

mq.default.event.name= Price.update
mq.default.event.property Defines the default event property. If the sending external application is able to specify the event name as a message property value, then use this parameter to define the name of the message property that will carry the message event name.

Possible Value: A valid JMS message property name.

Default Value: None.

mq.default.event.property=MyApp_OAIEventProperty
mq.default.event.exit Allows a custom Java class to be defined to determine which event name the native WebSphere MQ message corresponds to. It is invoked by the bridge, which provides the received JMS message as input, expecting the event name in return (as a String). This Java class must implement the oracle.oai.agent.adapter.mqseries.MQEventExit interface.

Possible Value: The Java class name of a class that implements the oracle.oai.agent.adapter.mqseries.MQEventExit interface.

Default Value: None.

mq.default.event.exit= mypackage.myMqEventExit
mq.default.event.use_mq_fmt Specifies the usage of the IBM WebSphere MQ Message Format field. If this parameter value is Y, then the bridge uses the IBM WebSphere MQ Message Format field as the name of the OracleAS Integration InterConnect event. This message field or property is often referred to as:

  • (C)—MQMD Format field (MQFMT)

  • (Java)—com.ibm.mq.jms.JMSC.FORMAT_PROPERTY

Possible Values: Y or N.

Default Value: N.

mq.default.event.use_mq_fmt=Y
mq.default.hostname Specifies the DNS name of the host where the queue manager resides.

Possible Value: A valid hostname that can be reached over the network from the WebSphere MQ adapter.

Default Value: None.

mq.default.hostname= mqsvrhost1.acme.com
mq.default.polling_interval Specifies the number of milliseconds between attempts to receive a message.

Possible Value: 0-java.lang.Long.MAX_VALUE.

Default Value: 5000.

mq.default.polling_interval=5000
mq.default.port Specifies the port to connect to on the WebSphere MQ Server host (IBM's default is 1414).

Possible Value: A valid port number for the WebSphere MQ listener.

Default Value: None.

mq.default.port=1414
mq.default.queue_manager Specifies the name of the WebSphere MQ queue manager to connect to.

Possible Value: Any WebSphere MQ queue manager name.

Default Value: None.

mq.default.queue_manager=mars.queue.manager
mq.default.receive_exit Specifies the fully qualified class name of the receive exit being used.

Possible Value: The classname of a Java class that implements com.ibm.mq.MQReveiveExit.

Default Value: None.

mq.default.receive_exit=mypackage. myReceiveExit
mq.default.receiver. destination.uri Specifies a URI for the WebSphere MQ outbound queue or topic from which messages will be received. Used for listening to incoming messages or as a ReplyTo address when sending request messages to WebSphere MQ.

Possible Values: A JMS queue URI.

Default Value: None.

mq.default.receiver. destination.uri=topic: //SAP/Events/HR/ newEmployee
mq.default.receiver. selector Specifies the JMS selector expression applied while dequeueing from the receiver destination.

Possible Values: A JMS selector expression.

Default Value: None.

mq.default.receiver. selector=JMS_IBM_Format <> 'MQSTR' AND JMSXUserID = 'scott'
mq.default.receiver.exception.uri Specifies a URI for an WebSphere MQ queue where faulty native messages will be placed.

Default Value: None.

mq.default.receiver.exception.uri=queue:///EXCEPTION.QUEUE
mq.default.security_exit Specifies the fully qualified class name of the security exit being used.

Possible Value: The classname of a Java class that implements com.ibm.mq.MQSecurityExit.

Default Value: None.

mq.default.security_exit=mypackage.MySecurityExit
mq.default.send_exit Specifies the fully qualified class name of the send exit being used.

Possible Value: The classname of a Java class that implements com.ibm.mq.MQSendExit.

Default Value: None.

mq.default.send_exit=mypackage.mySendExit
mq.default.sender. destination.uri Specifies the URI for the WebSphere MQ inbound queue to which messages will be sent from OracleAS Integration InterConnect.

Possible Values: A JMS queue URI.

Default Value: None.

mq.default.sender. destination.uri=queue: ///INBOUND.QUEUE?priority=1
mq.default.sender.log_queue.uri Specifies a URI for the WebSphere MQ log queue used during send transactions.

Possible Values: A JMS queue URI.

Default Value: None.

mq.default.sender.log_queue.uri=queue:///OAI.LOG.QUEUE
mq.default.sender.mqfmt Supresses the JMS specific header information. The WebSphere MQ adapter will normally read and write JMS messages from and to WebSphere MQ queues, which include a JMS specific header section. To suppress this header when interacting with external non-JMS clients (C or non-JMS Java applications), define this property. It will also defines the message MQMD Format field of each message being sent by the adapter. If the value is set to MQFMT_STRING, then it will cause all messages to be sent as Text messages, even in D3L mode. Normally, D3L mode will cause the adapter to send only Bytes messages.

Default Value: None.

mq.default.sender.mqfmt=MQFMT_STRING
mq.default.trans_id_expiry Specifies the number of milliseconds before an idle transaction identifier will expire.

Possible Value: 0-java.lang.Long.MAX_VALUE.

Default Value: 60000.

mq.default.trans_id_expiry=360000
mq.default.user Specifies the WebSphere MQ user ID when connecting to the queue manager. Equivalent to the WebSphere MQ environment variable MQ_USER_ID. The value may be used to verify the identity of the WebSphere MQ adapter.

Possible Value: A valid WebSphere MQ user name.

Default Value: None.

mq.default.user=mqm
ota.type Defines the type of payload this adapter handles.

Possible values: XML and D3L.

Default Value: XML.

ota.type=D3L

  Previous
Previous 		Next
Next
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents		 Go To Index
Index