Changing 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. If the value of this property is set to true, then all beans within the server are initialized at each application's start time.

Overview

However, by default, the WebSphere Application Server's Enterprise JavaBeans (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.

Procedure

1. Open the administrative console.

2. Select Servers.

3. Select Application Servers.

4. Select the server you want to configure.

5. In the Server Infrastructure area, select Java and Process Management.

6. In the Server Infrastructure area, select Process Definition.

7. In the Additional Properties area, select Java Virtual Machine.

8. In the Additional Properties area, select Custom Properties.

9. Select the New box.

10. In the Name entry field, type com.ibm.websphere.ejbcontainer.initializeEJBsAtStartup.

11. In the Value entry field, type true. Entering true causes all Enterprise JavaBeans to initialize when your application starts. Entering false causes initialization of all beans to be delayed.

    Note: Setting com.ibm.websphere.ejbcontainer.initializeEJBsAtStartup to either true or false takes precedence over any Start EJB at Application Start settings made on individual EJB types (see Changing enterprise bean types to initialize at application start time using the Application Server Toolkit).

12. Select OK.