WAS v8.5 > Administer applications and their environment > Welcome to administering EJB applicationsManage EJB containers
Each application server can have a single Enterprise JavaBeans 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.
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 container settings
- EJB container system properties
- Initialize EJBs at application start time
- Stateful session bean failover for the EJB container
- Enable stateful session bean failover with the EJB container panel
- Enable stateful session bean failover with the enterprise applications panel
- Enable stateful session bean failover at the EJB module level
- Tune EJB cache with trace service
- EJB cache settings
- Container interoperability
- EJB container tuning
- EJB containers
- Change applications to WebSphere version specific setRollbackOnly behavior
- EJB cache settings
- Container interoperability
Related concepts:
EJB containers
Related
Applying access intent policies to methods