Manage EJB containers
Each application server can have a single Enterprise JavaBeans (EJB) container; one is created automatically for you when the application server is created. The following steps are to be performed only as needed to improve performance after the EJB application has been deployed.
- Adjust EJB container settings.
- Adjust EJB cache settings.
What to do next
If adjustments do not improve performance, consider adjusting access intent policies for entity beans, reassembling the module, and redeploying the module in the application.
Subtopics
- EJB containers
An EJB container provides a run-time environment for enterprise beans within the application server. The container handles all aspects of an enterprise bean's operation within the application server and acts as an intermediary between the user-written business logic within the bean and the rest of the application server environment.
- EJB container settings
Use this page to configure and manage the EJB container of this application server.
- EJB container system properties
In addition to the settings that are accessible from the administrative console, we can set EJB system properties using command-line scripting.
- Change enterprise bean types to initialize at application start time using the administrative console
All EJB types within a server can be forced to initialize at application start time by setting a system property within the administrative console.
- Change applications to WebSphere version specific setRollbackOnly behavior
Use this task to allow post-EJB 3.0 applications to exhibit the pre-EJB 3.0 behavior and to allow pre-EJB 3.0 applications to exhibit post-EJB 3.0 behavior. The steps in this task that provide this processing behavior are based on a very specific processing scenario, which is explained in the About this task section.
- EJB cache settings
Use this page to configure and manage the cache for a specific EJB container. To avoid errors from attempting to overload the cache, determine the cache absolute limit. Multiply the number of enterprise beans active in any given transaction by the total number of concurrent transactions expected. Then, add the number of active session bean instances. This value is the limit that the cache will hold.
- Container interoperability
Container interoperability describes the ability of the product clients and servers at different versions to successfully negotiate differences in native EJB finder methods support and Java EE compliance.
Related concepts
EJB containers Stateful session bean failover for the EJB container
Related tasks
Apply access intent policies to methods Enable or disable stateful session bean failover with the EJB container panel Enable or disable stateful session bean failover with the enterprise applications panel Enable or disable stateful session bean failover at the EJB module level using the administrative console Tune EJB cache with trace service
(zos) Enable failover of servants in an unmanaged z/OS server
EJB container tuning