Application Startup Modes
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.
Integration
There are no additional requirements for the always and manual startup modes.
Each application consists of one or more modules. Each container handles different types of modules. In order to implement lazystartup, a container must be able to start an application when the first request to it is made.
Prerequisites
One application can use lazy startup mode, if 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 lazystartup mode.
Features
Each application can be in one of the next startup modes:
· always – application is started each time the J2EE Engine is restarted.
· lazy – if a lazy enabled application has not been started when the J2EE Engine was stopped, containers are responsible for starting this application at the first request.
· manual - application cannot be started automatically, and calls to startApplication() throw the applicationDisabled exception.
Manual mode is not supported completely due to possible implications for other parties. Applications with manual mode are not started initially, but can be started manually later on.
Activities
In order to specify the startup mode, you need to modify the application-j2ee-engine.xml to contain the element <start-up mode =”<startup_mode>”>, where “<startup_mode>” stands for one of the possible startup modes.
If no value is specified, the default value is lazy.