create-lifecycle-module.1


sun.com \| docs.sun.com		How To Buy \| My Sun \| Worldwide Sites

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
OPERANDS
EXAMPLES
EXIT STATUS
SEE ALSO

NAME

create-lifecycle-module - adds a lifecycle module for the named instance

SYNOPSIS

create-lifecycle-module --user admin_user[ --password admin_password ][ --host localhost ] [ --port 4848 ][ --passwordfile filename ][ --secure|-s ][ --instance instance_name ] --classname class_name[ --classpath classpath ][ --loadorder load_order ][ --failurefatal failure_fatal ] [ --enabled=true ][ --property (name=value)[ :name=value ]* ]module_name

DESCRIPTION

Creates the lifecycle module associated with the named server instance.

OPTIONS

--user: administrative user associated for the instance.
--password: administrative password corresponding to the administrative user.
--host: host name of the machine hosting the administrative instance.
--port: administrative port number associated with the administrative host.
--passwordfile: file containing passwords appropriate for the command (e.g., administrative instance).
--secure: if true, uses SSL/TLS to communicate with the administrative instance.
--instance: name of the instance.
--classname: fully qualified name of the startup class.
--classpath: indicates where this module is actually located if it is not under applications-root.
--loadorder: an integer value that can be used to force the order in which deployed lifecycle modules are loaded at server startup. Smaller numbered modules get loaded sooner. Order is unspecified if two or more lifecycle modules have the same load-order value.
--failurefatal: if true indicates abort server startup if this module does not load properly.
--enable: determines whether the resource is enabled at runtime or not.
--description: text description of the resource.
--property: optional attributes name/value pairs for configuring the resource.

OPERANDS

module_name: unique identifier for the deployed server lifecycle event listener module.

EXAMPLES

Example 1. using create-lifecycle-module

asadmin> create-lifecycle-module --user admin --password adminadmin
 --host fuyako --port 7070 --instance server1 --classname "com.acme.CustomSetup" 
--classpath "/export/customSetup" --loadorder 1 --failurefatal=true 
--description "this is a sample customSetup" 
--property rmi=Server="acme1\:7070" :timeout=30 customSetup
Created the Lifecycle module with module name = customSetup

Where: customSetup is the lifecycle module created. The escape character (\) is used in the property option to distinguish the colons (:).

EXIT STATUS

0: command executed successfully
1: error in executing the command