9.10.2 Setting the runtime properties for Stateless Session Beans
You set the application runtime properties for the individual Stateless Session Beans that form an application.
- Organization of this subsection
(1) Attribute file to be edited
Session Bean attribute file
(2) Acquiring the attribute file to be edited and setting the attributes
-
Acquiring the attribute file
Execute the following command to acquire a Session Bean attribute file:
- Execution format
cjgetappprop [server-name] [-nameserver provider-URL] -name J2EE application-name -type ejb -resname EJB-JAR-display-name/Stateless-Session-Bean-display-name -c path-of-the-Session-Bean-attribute-file
- Example of execution
cjgetappprop MyServer -name adder -type ejb -resname adder/MyAdder -c C:\home\MyAdder.xml
-
Setting the attributes
Execute the following command to apply the values of the Session Bean attribute file:
- Execution format
cjsetappprop [server-name] [-nameserver provider-URL] -name J2EE application-name -type ejb -resname EJB-JAR-display-name/Stateless-Session-Bean-display-name -c <path-of-the-Session-Bean-attribute-file
- Example of execution
cjsetappprop MyServer -name adder -type ejb -resname adder/MyAdder -c C:\home\MyAdder.xml
(3) Attribute settings to be edited
The runtime properties of the Stateless Session Bean are classified into the following three types:
-
Runtime attributes common to the Session Beans
-
Attributes specific to the Stateless Session Bean
-
Runtime attributes of CTM integration
The respective settings are described below:
(a) Runtime attributes common to the Session Beans
The following table describes the property settings for the runtime attributes common to the Session Beans (<runtime>):
|
Items |
Mandatory |
Corresponding tags |
|---|---|---|
|
Look up name of the Enterprise Bean#1 |
Y |
<lookup-name> |
|
Optional name of the Enterprise Bean name having a remote interface#1 |
O |
<optional-name> |
|
Optional name of the Enterprise Bean name having a local interface#1 |
O |
<local-optional-name> |
|
Maximum number of sessions#2 |
O |
<maximum-sessions> |
|
Settings for scheduling#3 |
O |
<enable-scheduling> |
|
Pass by reference settings#4 |
O |
<pass-by-reference> |
- Legend:
-
Y: Mandatory
O: Optional
- #1
-
For referencing and changing the name registered in the JNDI namespace, see 9.13.2 Referencing and changing the Enterprise Bean name.
- #2
-
The maximum number of sessions specified in the Stateless Session Bean is the number of Stateless Session Bean instances that a client can use. This specified value, however, is not enabled.
- #3
-
For details on CTM scheduling, see 9.14 CTM scheduling.
- #4
-
Pass by reference settings can also be specified in the usrconf.properties file. If the settings are specified in either the properties or in the usrconf.properties file, pass by reference settings become valid.
For details on the property settings, see 3.4.1 Specifications of the HITACHI Session Bean Property file in the uCosminexus Application Server Application and Resource Definition Reference Guide.
(b) Attributes specific to Stateless Session Bean
The following table describes the property settings for the runtime attributes specific to Stateless Session Beans (<runtime> - <stateless>):
|
Items |
Mandatory |
Corresponding tags |
|---|---|---|
|
Minimum number of the instances in the pool |
Y |
<pooled-instance> - <minimum> |
|
Maximum number of the instances in the pool |
Y |
<pooled-instance> - <maximum> |
- Legend:
-
Y: Mandatory
For details on the property settings, see 3.4.1 Specifications of the HITACHI Session Bean Property file in the uCosminexus Application Server Application and Resource Definition Reference Guide.
The property settings and operations are explained below:
- Minimum number of instances in the pool
-
The number of Stateless Session Beans specified here are generated and pooled when the J2EE application starts. The number of pooled Stateless Session Beans lies between the maximum and the minimum count, depending on the volume of access from the EJB client applications. If '0' is specified in the minimum number of instances in the pool, the Stateless Session Bean is not generated when the J2EE application starts.
The minimum number also specifies the number of Stateless Session Bean instances created when the application is started.
- Maximum number of instances in the pool
-
The generated Stateless Session Beans are pooled in the method-ready state. The pooled Stateless Session Beans are already executable when accessed from the EJB client applications. Specify the maximum number of pooled Stateless Session Beans in the maximum number of instances in the pool. The maximum number is the maximum number of the Stateless Session Beans that can be executed immediately when accessed from multiple EJB client applications. If '0' is specified in the maximum number of instances in the pool, the pooled Stateless Session Beans becomes infinite.
(c) Runtime attributes of CTM integration
The following table describes the property settings for the runtime attributes of CTM integration (<runtime> - <scheduling>).
|
Items |
Mandatory |
Corresponding tags |
|---|---|---|
|
Queue name |
Y |
<queue-name> |
|
Thread name |
Y |
<parallel-count> |
- Legend:
-
Y: Mandatory
For details on the property settings, see 3.4.1 Specifications of the HITACHI Session Bean Property file in the uCosminexus Application Server Application and Resource Definition Reference Guide.
For details on CTM scheduling, see 9.14 CTM scheduling.
(4) Notes
-
The function for checking the upper limit of the Stateless Session Beans accessible from a client does not work. Instead set the value in maximum number of instances in the pool.
-
Specify the minimum number of pooled Stateless Session Beans and the maximum number of pooled Stateless Session Beans such that the following condition is fulfilled:
Minimum number of pooled Stateless Session Beans ≤ Maximum number of pooled Stateless Session Beans
When you specify the maximum number of pooled Stateless Session Beans, you also need to specify the minimum number of pooled Stateless Session Beans.