Fixed Portion RFH Version 2 RFH2 Header

Oracle JCA Adapter for MQ Series 10-9 The usr folder This is used to transport any application-defined properties associated with the message. This folder is only present if the application has set some application-defined properties. The psc folder This is used to convey publishsubscribe command messages to the broker. Only one psc folder is allowed in the NameValueData field. The pscr folder This is used to contain information from the broker, in response to publishsubscribe command messages. Only one pscr folder is present in a response message. Table 10–4 shows a full list of property names. The syntax used to express the properties in the variable portion is as follows: NameValueLength MQLONG Length, in bytes, of the NameValueData string that immediately follows this length field. It does not include its own length. The value set into NameValueLength is always a multiple of 4. The NameValueData field is padded with space characters to achieve this. NameValueData MQCHARn A single character string, whose length in bytes is given by the preceding NameValueLength field. It contains a folder holding a sequence of properties. Each Table 10–4 MQRFH2 Folders and Properties Used by JMS JMS Field Name Java Type MQRFH2 Folder name Property Name Typevalues JMSDestination Destination jms Dst string JMSExpiration long jms Exp i8 JMSPriority int jms Pri i4 JMSDeliveryMode int jms Dlv i4 JMSCorrelationID String jms Cid string JMSReplyTo Destination jms Rto string JMSTimestamp long jms Tms i8 JMSType String mcd Type, Set, Fmt string JMSXGroupID String jms Gid string JMSXGroupSeq int jms Seq i4 xxx User Defined Any usr xxx any mcd Msd jms_none jms_text jms_bytes jms_map jms_stream jms_object 10-10 Oracle Fusion Middleware Users Guide for Technology Adapters property is a nametypevalue triplet, contained within an XML element whose name is the folder name, as follows: foldername triplet1 triplet2 ..... tripletn foldername

10.3.2 SSL Enabling

Secure Sockets Layer SSL is a protocol for transmitting encrypted data over the Internet or an internal network. SSL works by using public and private keys to encrypt data that is transferred over the SSL connection. Data that has been encrypted with a public key can be decrypted only with the corresponding private key. Conversely, data that has been encrypted with a private key can be decrypted only with the corresponding public key. MQ Series supports secure communication, with MQ Series clients using SSL. As a part of this functionality, the adapter would provide support to put a message on queue using SSL. To enable Oracle MQ Series Adapter for SSL, the following properties must be provided: ■ SSLEnable : The truefalse value for this property means that the Oracle MQ Series Adapter is SSL enableddisabled. ■ KeyStoreLocation : This is the keystore where Oracle MQ Series Adapter will have its private keys. This is required when an adapter needs to authenticate itself to the MQ Series server. ■ KeyStorePassword : This password is required to access keystore. ■ TrustStoreLocation : This is the location where the adapter keeps its trusted certificates information. This information is required when an adapter needs to authenticate to the MQ Series server. ■ Protocol : Key Management Algorithm. ■ KeyStoreProviderName : The name of the keystore provider. ■ KeyStoreType : Type of the key store. ■ KeyStoreAlgorithm : Algorithm used by the key store. ■ CipherSuite : Set CipherSuite to the name matching the CipherSpec set on the SVRCONN channel. If set to null default, then no SSL encryption is performed. ■ SSLPeerName : A distinguished name pattern. If CipherSuite is set, then this variable can be used to ensure that the correct queue manager is used. If set to null default, then the DN of the queue manager is not checked. This variable is ignored if sslCipherSuite is null.

10.3.3 XA Transactions

Oracle MQ Series Adapter enables transaction support, which along with the inherent data processing, ensures that each modification has a clearly defined outcome, resulting in either success or failure, thus preventing potential corruption of data, executes independently from other changes, and, once completed, leaves underlying data in the same state until another transaction takes place. The Oracle MQ Series Adapter supports both inbound and outbound XA transaction. You must set the XATransaction property in the Oracle WebLogic Server Administration Console to enable the XA transaction. To enable XA transaction, perform the following steps: