Manage EJB containers
Each appserver can have a single Enterprise Java Beans (EJB) container; one is created automatically for you when the appserver is created.
The following steps are to be performed only as needed to improve performance after the EJB application has been deployed.
If adjustments do not improve performance, consider adjusting access intent policies for entity beans, reassembling the module, and redeploying the module in the application.
Related concepts
EJB containers
EJB container settings
EJB container system properties
Change enterprise bean types to initialize at application start time
Stateful session bean failover for the EJB container
Enable session bean failover with the EJB container panel
Enable session bean failover with the enterprise apps panel
Enable session bean failover with the EJB modules panel
Tuning the EJB cache using the trace service
EJB cache settings
Container interoperability
EJB 2.1 container tuning
Related tasks
Applying access intent policies to methods