A lifecycle module performs tasks when it is triggered by one or more events in the server lifecycle. These server events are:
Lifecycle modules are not part of the J2EE specification, but are an enhancement to the Sun Java System Application Server.
To create a lifecycle module:
If you don’t specify the classpath, you must unpack the classes in application_server_home/domains/domain/applications/lifecycle-module/module_name. If you specify a classpath, nothing else is required.
MAXINT
value.The integer determines the order in which lifecycle modules are loaded when the server starts up. Modules with smaller integers are loaded sooner.
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
.
If you are redeploying, don’t select targets. Anything you select here is ignored. Any target clustered or stand-alone server instance that references the deployed module automatically references the new, redeployed module if dynamic reconfiguration is enabled for the cluster or stand-alone instance. For more information about how to redeploy modules without interruption of service, see "About Rolling Upgrades".
Equivalent asadmin
command: create-lifecycle-module