| |
JSR88 Client Example
The OC4J 10g (10.0.3) Developer Preview on
OTN provides an implementation of JSR88, the J2EE Deployment API. This
API is now a part of J2EE 1.4 and provides a standard way for tools to
perform deployment oriented operations on a J2EE container.
admin_gui.jar -- the prototype
We provide a prototype of a Swing based JSR88 deployment tool with the
OC4J 10g (10.0.3) Developer Preview. The prototype is actually a
melding of JSR88 and JSR77 since it also shows up the set of JSR77
defined objects that are available in the connected OC4J
instance. But mostly it's targetted at the JSR88 Deployment API.
To run the prototype, first start OC4J in the usual manner.
Then start the GUI with >java -jar admin_gui.jar
This will fire up the tool and prompt you to enter the connection
details. We only support connection to an OC4J standalone
environment today, so select OC4J from the select list. The host
and portname are the same as for a standard ORMI connection (localhost,
23791). The username/password should be administrator enabled --
the default admin/.... entry will do if you have not changed
them.
Once you connect to to the OC4J instance, you will see two tabs -- one for management and one for deployment.
The Management tab exposes the JSR77 objects in the navigator.
You can click around here and see all the various configured elements
of the OC4J instance. In the prototype, you can't actively make
any alterations, it's a read-only view.
The interesting thing you can do with the tool is to perfom deployments (hey, it's mostly JSR88 oriented after all!).
To perform a deployment, you can then select the File > Open Archive menu item.
That will load the application archive and then let you adjust the
various settings the application should have when it is deployed.
This all boils down to something that is called a deployment plan,
which basically describes all the settings at the J2EE and vendor
specific container level that the application should have when it is
deployed.
Once the application has been configured, it can then be deployed to the connected OC4J instance by selecting the Deployment > Deploy menu item.
A progress dialog will show the progression of the deployment as it occurs.
Once the application is deployed, you can then cruise over to the Management tab and see it listed as a deployed application.
The tool lets you view the deployment plans, the OC4J specific XML
files, etc. It's worth having a click around and see what it can
do.
© Copyright 2004 buttso.
Last update: 2/27/2004; 12:07:27 PM.
|
|
