WAS v8.5 > Administer applications and their environment > Welcome to administering EJB applications > Manage EJB containersInitialize EJBs at application start time
All EJB types within a server can be forced to initialize at application start time by setting a system property within the dmgr console. If the value of this property is set to true, then all beans within the server are initialized at each application's start time.
However, by default, the product's EJB container delays the initialization (loading of classes and processing of deployment descriptor metadata) of most EJB types until they are needed during run time. This delay helps to speed up the application start time.
Go to...
Servers | Application servers | appserver | Server Infrastructure | Java and Process Management | Process Definition | Additional Properties | Java Virtual Machine | Additional Properties | Custom Properties | New
..and in the Name set...
com.ibm.websphere.ejbcontainer.initializeEJBsAtStartup = true
This causes all EJBs initialize when the application starts. Setting false causes initialization of all beans to be delayed.
This takes precedence over any "Start EJB at Application Start" settings made on individual EJB types.
This task can also be done using an assembly tool.