Message-driven Bean attribute file

Acquiring the attribute file

Execute the following command to acquire a Message-driven Bean attribute file:

Execution format

cjgetappprop [server-name] [-nameserver provider-URL] -name J2EE application-name -type ejb -resname EJB-JAR-display-name/Message-driven-Bean-display-name -c path-of-the-Message-driven-Bean-attribute-file

Example of execution

cjgetappprop MyServer -name message -type ejb -resname message/MyMessageBean -c C: \home\MyMessageBean.xml
 

Setting the attributes

Execute the following command to apply the values of the Message-driven Bean attribute file:

Execution format

cjsetappprop [server-name] [-nameserver provider-URL] -name J2EE application-name -type ejb -resname EJB-JAR-display-name/Message-driven-Bean-display-name -c path-of-the-Message-driven-Bean-attribute-file

Example of execution

cjsetappprop MyServer -name message -type ejb -resname message/MyMessageBean -c C: \home\MyMessageBean.xml
 

The following table describes the property settings for the runtime attributes of Message-driven Bean (<runtime>):

Item	Mandatory	Corresponding tag
Maximum number of instances in the pool#	Y	<pooled-instance> - <maximum>

Legend:

Y: Mandatory

#

During the initialization of the Server Session pool, the number of Beans up to the specified value are generated. You can specify a value from 1 to 2147483647 (maximum value of int type). The default value is 1. In order to generate the specified number of JMS sessions, define the JMS sessions as per the number of JMS sessions that can be generated in the JMS provider.

For details on the property settings, see 3.6.1 Contents of the MessageDrivenBean property file in the uCosminexus Application Server Application and Resource Definition Reference Guide.