Specifying the Application Startup Mode 

Use

To decrease the initial load on the J2EE Engine and to minimize its startup time at each restart, you should use the most appropriate startup modes for your applications. Startup modes determine how your application is started on the J2EE Engine. More information about the DTD is available in application-j2ee-engine.dtd.

Prerequisites

·        You have opened the application-j2ee-engine.xml multipage editor. See Editing application-j2ee-engine.xml.

·        If you want to use lazy startup mode, you have made sure it consists exclusively of modules that are handled by containers supporting lazy startup mode. Such an application is called a lazy enabled application.

Currently, only the Web Dynpro container supports the lazy startup mode.

This requirement does not apply to the always and manual startup modes.

Procedure

...

       1.      Choose the General tab.

       2.      In the Startup mode field, choose the appropriate entry from the drop-down list:

¡        manual – The application will be stopped initially after installation on the J2EE Engine, and will require manual start on each J2EE Engine restart.

¡        lazy – If a lazy application has not been started when the J2EE Engine was stopped, the application will be stopped upon restart of the J2EE Engine. When another application requests a resource from the application, the responsible containers will start the it.

This is the default value.

Applications that are not lazy enabled, but have the startup option set to lazy, are treated automatically as if they have the always startup option.

¡        always – The application is started each time the J2EE Engine is restarted.

       3.      Save the changes.

Result

The corresponding XML source is added to the application-j2ee-engine.xml. You can see the changes in the Source tab.