Deployment Target:
A deployment target is a server or a clustered group of servers
where in the J2EE application is to be deployed and configured.
The J2EE application needs to be stored on the server and this
could be a directory or a database repository depending on the
type of application server and the storage system it has. The
configuration of the server is the responsibility of the J2EE
product provider. The provider also has the responsibility of
making sure the target is capable of deploying J2EE applications
by the deployer. The deployer or the tool provider need not
bother about the configuration. The J2EE provider needs to
provide at least one target per J2EE product and has to make the
information about the target available to the deployment
manager. The deployer will deploy and distribute the J2EE
application to all targets as dictated in the deployment
descriptor.
TargetModuleID:
When a J2EE application is deployed on a target the target
server generates a TargetModuleId object for each module in the
application. The TargetModuleID object contains a unique target
ID identifier which identifies each module in the application
server. The ID is unique across the application server and
remains with the module all through its lifetime on the server.
The object also contains information on the target on which the
module is deployed. The target module ID information is
accessible to the deployment manager. This way the deployer can
access information on modules through the deployment manager and
do operations like starting a module, stopping a module or
undeploying a module.
The TargetModuleID also maintains references to its parent
modules and its child modules. In case the module happens to be
the root of the deployed application its parent TargetModuleID
is null. Other API methods of the TargetModuleID class can help
retrieve the module ID, parent module object, child module
objects, targets, etc.
ProgressObject:
A ProgressObject class is provider to the tool provider to poll
the status and provide callback information on deployment
operations. It tracks and reports the progress of deployment
operations like start, stop, deploy undeploy etc. It also
provides methods to stop or start a deployment operation midway.
If a request for stop is issued to the target it finishes the
currently running target module but halts the processing of
subsequent modules. A J2EE provider may provide an optional
cancel method which will cancel the requested operation. The
cancel operation will cancel all operations and return the
system to the same state it was before it started the operation.
A ClientConfiguration object is returned by the progress object
for every application client distributed on the J2EE product.
This object helps in installing, configuring and running an
application client.
New on the Java Boutique:
New Review:
Time Management Made Easy with the Quartz Enterprise Job Scheduler
Why not just use the Java timer API? This open source scheduling
API boasts simplicity, ease-of-integration, a well-rounded feature
set, and it's free!
New Applet:
Reverse Complement
Reverse Complement is a simple applet that converts DNA or RNA
sequences into three useful formats.
Elsewhere on internet.com:
WebDeveloper Java
Lots of Java information on webdeveloper.com
WDVL Java
Thorough Java resource at the Web Developer's Virtual Library.
ScriptSearch Java
Hundreds of free Java code files to download.
jGuru: Your View of the Java Universe
Customizable portal with online training, FAQs, regular news updates, and tutorials.
