In addition to the settings accessible from the administrative console, you can set the following system property by command-line scripting.
This property is applicable to CMP 1.1 beans only. By default, the EJB Container creates the entity bean representation in the database only after the method ejbPostCreate(...) is called.
Some applications may rely on method ejbCreate(...) to have created the entity bean in the database. For such a requirement, setting the JVM property com.ibm.websphere.ejbcontainer.allowEarlyInsert to true overrides the default behavior.
This property enables you to indicate whether exceptions that are declared on the throws clause of an EJB method should are treated as application exceptions or as system runtime exceptions. When this property is set to true, these exceptions are treated like system runtime exceptions, and causes an EJBException to be issued on the client side.
If this property is not specified, or if this property is set to false, exceptions that are declared on the throws clause of an EJB method are treated as application exceptions.
The default value for this property is false.
This property allows the user to specify application names in which they want to have the EJBs in their EJB 3.0 modules demonstrate the pre-EJB 3.0 setRollbackOnly behavior.
The pre-EJB 3.0 setRollbackOnly behavior is described in Changing applications to WebSphere "version specific" setRollbackOnly behavior.
This property allows the user to specify application names in which they want to have the EJBs in their EJB 3.0 modules demonstrate the EJB 3.0 setRollbackOnly behavior.
The EJB 3.0 setRollbackOnly behavior is described in Changing applications to WebSphere "version specific" setRollbackOnly behavior.
Specifies the size of the pool for the specified bean type. This property applies to stateless, message-driven and entity beans. If you do not specify a default value, the container defaults of 50 and 500 are used.
beantype= [H] min,[H] max [:beantype= [H]min, [H]max...]
beantype is the J2EE name of the bean, formed by concatenating the application name without the file extension, the # character, the module name without the file extension, the # character, and the name of the bean (that is, the string assigned to the <ejb-name> field in the bean's deployment descriptor). For example, if you have an application called SMApp.ear that includes module PerfModule.jar, and module PerfModule.jar uses a bean named TunerBean, the J2EE name of the bean is specified as SMApp#PerfModule#TunerBean
min and max are the minimum and maximum pool sizes, respectively, for that bean type. Do not specify the square brackets shown in the previous prototype; they denote optional additional bean types that you can specify after the first. Each bean-type specification is delimited by a colon (:).
*=30,100
SMApp#PerfModule#TunerBean=54, :SMApp#SMModule#TypeBean=100,200
You can specify the bean types in any order within the string.
You can designate the maximum configured EJB pool size as a hard limit by inserting the character H directly in front of the max value. Without the H, the maximum value indicates how many EJB instances can be pooled, and does not limit the number of EJB instances that can be created or in use. Inserting the H before the max value indicates that it is a hard limit, and the EJB Container blocks creation of more instances when that limit is reached. Further threads must wait until an instance becomes available or until the transaction times out.
You can designate the minimum configured EJB pool size as a hard limit by inserting the character H directly in front of the min value. Without the H, the minimum value indicates how many EJB instances are maintained in the pool when the EJB type is not actively in use, but does not pre-load the pool when the application is started. Normally, the minimum pool size is not reached until the minimum number of EJB instances has been accessed concurrently by the application. Inserting the H before the min value indicates that it is a hard limit, and the EJB Container pre-loads the pool with the minimum number of EJB instances when the application is started.
SMApp#SMModule#TypeBean=100,H200If you want to indicate that the EJB Container pre-load the pool with a minimum of 100 EJB instances when the application is started, you enter:
SMApp#SMModule#TypeBean=H100,200