In addition to the settings accessible from the administrative console, you can set the following system property by command-line scripting.
beantype = min,max[:beantype=min , max...]
beantype is the J2EE name of the bean, formed by concatenating the application name, the # character, the module name, the # character, and the name of the bean (that is, the string assigned to the <ejb-name> field in the bean's deployment descriptor). 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 (:). Use an asterisk (*) as the value of beantype to indicate that all bean types are to use those values unless overridden by an exact bean-type specification somewhere else in the string, as follows:
*=30,100To specify that a default value be used, omit either min or max but retain the comma (,) between the two values, as follows (split for publication):
SMApp#PerfModule#TunerBean=54, :SMApp#SMModule#TypeBean=100,200
You can specify the bean types in any order within the string.
Note: 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. However, 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.
Related concepts
EJB
containers
Related tasks
Managing EJB containers
Related reference
EJB container settings