+

Search Tips   |   Advanced Search

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.

  1. Adjust EJB container settings.

  2. 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


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