JMS activation specification custom properties

These custom properties are in addition to properties displayed on the JMS activation specification settings panel. To display or change these custom properties, you use the J2C activation specification custom properties panel.

To view this pane in the console, click the following path:

Resources > Resource adapters > SIB JMS Resource Adapter > J2C activation specifications > jms_activationspec > J2C activation specification custom properties .

Where jms_activationspec is the name of the JMS activation specification; for example as shown on the Resources > JMS > JMS providers > [Content Pane] default_messaging provider > [Additional Properties] Activation specifications panel

Use this panel to browse or change the custom properties of the selected JMS activation specification for use with the default messaging JMS provider. These J2C activation specification custom properties add to the properties set on the JMS activation specification settings panel.

readAhead

Read ahead is an optimization that preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.

Messages that are assigned to a consumer are locked on the server and cannot be consumed by any other consumers for that destination. Messages that are assigned to a consumer, but not consumed before that consumer is closed, are subsequently unlocked on the server and then available for receipt by other consumers.

You can override this property for individual JMS destinations by setting the Read ahead property on the JMS destination.

Required No
Data type Text
Default Default
Range
Default
The message provider preemptively assigns messages to consumers on nondurable subscriptions and unshared durable subscriptions. That is, read ahead optimization is turned on only when there can only be a single consumer.
Enabled
The messaging provider preemptively assigns messages to consumers. This improves the time taken to satisfy consumer requests.
Disabled
The messaging provider does not preemptively assign messages to consumers.

shareDataSourceWithCMP

Allow sharing of connections between JMS and container-managed persistence (CMP) entity beans.

This option enables container-managed persistence (CMP) entity beans to share the database connections used by the data store of a messaging engine. This has been estimated as a potential performance improvement of 15% for overall message throughput, but can only be used for entity beans connected to the application server that contains the messaging engine.

Required No
Data type Text
Default false
Range
false
CMP entity beans cannot share the database connections used by the data store of a messaging engine.
true
CMP entity beans can share the database connections used by the data store of a messaging engine.

targetTransportChain

The name of the inbound transport chain that the application should target when connecting to a messaging engine in a separate process to the application. If a messaging engine in another process is chosen, a connection can be made only if the messaging engine is in a server that runs the specified inbound transport chain. Refer to the InfoCenter for more information.

Type the name of the transport chain that the application should use when connecting to a messaging engine in separate process to the application. If a messaging engine in another process is chosen, a connection can be made only if the messaging engine is in a server that runs the specified transport chain.

If the selected messaging engine is in the same server as the application, a direct in-process connection is made and this transport chain property is ignored.

The transport chains represent network protocol stacks operating within a server. The name you specify must be one of the transport chains available in the server that hosts the messaging engine, as listed on the Servers > Application servers > [Content Pane] server_name > Messaging engine inbound transports panel. The following transport chains are provided, but you can define your own transport chains on that panel.

InboundBasicMessaging
This is a connection-oriented protocol, using a standard TCP/IP connection (JFAP-TCP/IP). It includes support for two-phase transactional (remote XA) flows, so that a message producer or consumer, running on a client or server system, can participate in a global transaction managed on that client or server system. The specific use for the XA flows is to support access from an application running in one server to a messaging engine on second server, perhaps because the first server does not have a suitable messaging engine. If the remote XA flows are used, a transaction coordinator must be available local to the application.
InboundSecureMessaging
This is the InboundBasicMessaging protocol wrapped in SSL.
Required No
Data type Text
Default Null



Related information
Default messaging provider, JMS resources
Administrative console buttons
Administrative console preference settings
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 8:25:23 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=SIBJMSActivationSpec_Custom
File name: SIBJMSActivationSpec_Custom.html