Configuration properties in the ejb-jar.xml

The following properties have to be set in the deployment descriptor (ejb-jar.xml) of the OLTP message-driven bean:

• The messaging-type property specifies the message listener interface used by the OLTP message-driven bean.

• The activation-config properties refer to the specified message listener interface. Each of the properties are specified in a separate activation-config-property element within the activation-config element of the file ejb-jar.xml.

  The following activation-config properties are available:

  encoding
  encodingActive
  messageEndpoint
  redeliveryThreshold
  

The properties for the file ejb-jar.xml are described in detail below.

messaging-type

The messaging-type property specifies the message listener interface used by the OLTP message-driven bean.

Definition:	Message listener interface used by the OLTP message-driven bean
Default:	-
Example:	<messaging-type> net.fsc.jca.communication.AsyncOltpMessageListener </messaging-type>

messageEndpoint

The messageEndpoint activation-config property specifies the name of the message endpoint. Note that the message endpoint name specified here must be identical to the name of the inbound message endpoint specified when configuring the proxy using the Management Console (see Configuring inbound message endpoints ).

Definition:	Name of the message endpoint.
Default:	-
Example:	<activation-config-property> <activation-config-property-name>messageEndpoint </activation-config-property-name> <activation-config-property-value>SampleAsynOltpMdb </activation-config-property-value> </activation-config-property>

encoding

The encoding activation-config property defines a code table for converting EIS-specific byte code (for example EBCDIC) to Unicode.

The property specified here is overwritten if the message-driven bean is called by an inbound service to which a Partner Encoding was assigned in the Management Console during the configuration of the proxy.

Definition:	[<builtin_encoding_table> | builtin:<builtin_encoding_table> | jdk:<jdk_encoding_table> | custom:<encoding_table>]
Explanation:	Name of a code table to be used for code conversion. If no prefix is specified or if the prefix builtin: is specified, you must specify the name of a built-in code table provided by BeanConnect. The following code tables are provided: OSD_EBCDIC_DF03_IRV, OSD_EBCDIC_DF04_1, OSD_EBCDIC_DF04_15, OSD_EBCDIC_DF04_DRV Use the prefix jdk: to specify a code table contained in the JDK. Use the prefix custom: to assign your own code table. Here you must specify the fully qualified class name of the code table. For further details on using your own code tables, refer to the JavaDoc for BeanConnect
Default:	OSD_EBCDIC_DF04_DRV
Example:	for UTM partners: <activation-config-property> <activation-config-property-name>encoding </activation-config-property-name> <activation-config-property-value>OSD_EBCDIC_DF04_15 </activation-config-property-value> </activation-config-property> for CICS partners: <activation-config-property> <activation-config-property-name>encoding </activation-config-property-name> <activation-config-property-value>jdk:Cp1047 </activation-config-property-value> </activation-config-property>

encodingActive

The encodingActive activation-config property specifies whether code conversion is to be activated.

encodingActive is set to true irrespective of the value specified here if the message-driven bean is called by an inbound service to which a Partner Encoding was assigned in the Management Console during the configuration of the proxy

Definition:	[true | false]
Explanation:	Flag specifying whether code conversion is to be activated.
	true:	Code conversion according to the settings of the encoding activation-config property is activated.
	false:	The default code table of the JDK is used to convert byte streams to strings.
Default:	false
Example:	<activation-config-property> <activation-config-property-name>encodingActive </activation-config-property-name> <activation-config-property-value>true </activation-config-property-value> </activation-config-property>

redeliveryThreshold

The redeliveryThreshold activation-config property defines the number of additional attempts to deliver the message if the transaction is rolled back. This property can only be set for asynchronous OLTP message-driven beans, i.e. for OLTP message-driven beans which implement the message listener interface net.fsc.jca.communication.AsyncOltpMessageListener. The message listener interface is specified in the messaging-type property.

The property only takes effect if the OLTP message-driven bean has been deployed with the transaction attribute Required. In this case, the onMessage method is called inside a transaction which has been started by the proxy (never by the EIS). If this transaction is reset, the message is delivered again, unless the generated threshold has been exceeded.

Definition:	Number of additional redelivery attempts if an error occurs. Minimum value = 0 Maximum value = 254
Default:	0, i.e. the message is not delivered again.
Example:	<activation-config-property> <activation-config-property-name>redeliveryThreshold </activation-config-property-name> <activation-config-property-value>1 </activation-config-property-value> </activation-config-property>