A lifecycle module performs tasks when it is triggered by one or more events in the server lifecycle. These server events are:
Initialization
Startup
Ready to service requests
Shutdown
Lifecycle modules are not part of the Java specification, but are an enhancement to the Application Server.
If you do not specify the classpath, you must unpack the classes in domain-dir/applications/lifecycle-module/module-name. If you specify a classpath, nothing else is required.
The integer determines the order in which lifecycle modules are loaded when the server starts up. Modules with smaller integers are loaded sooner.
By default, if a load fails, the server continues the startup operation. To prevent the server from starting up when a load fails, select the On Load Failure checkbox.
Because a lifecycle module is invoked at server startup, a disabled lifecycle module will not cease to have an effect until the server instance is restarted.
From the list of available targets, choose the target or targets and click Add. Targets can be clusters or stand-alone server instances. If you do not select a target, the module is deployed to the default server instance server.