Browse Prior Art Database

Dependent Resources Discovery and Management of J2EE Applications Disclosure Number: IPCOM000172280D
Original Publication Date: 2008-Jul-08
Included in the Prior Art Database: 2008-Jul-08
Document File: 4 page(s) / 180K

Publishing Venue



Today one of the biggest challenges facing an administrator of J2EE deployment platform is to successfully provision the application to a new environment from scratch. Along with the application to be deployed, developers need to transfer the knowledge about the dependent resources for an application. For example, many applications assume that a JDBC data source has already been created. This means that you can not deploy the application until the data source has been provisioned. It is always a challenge for application deployer and system administrators to resolve such dependencies for an application themselves. In addition, after the application is successfully deployed, the dependency map between the resources and the application are not maintained by the J2EE container. Thus, the application transition or undeployment is not a trivial process and is often manual-intensive and error-prone.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 83% of the total text.

Page 1 of 4

Dependent Resources Discovery and Management of J2EE Applications

When a J2EE artifact (*.ear, *.

war, or *.

jar) is uploaded to server to be deployed, the server

will extract and then parse the configuration file (


portlet.xml or ejb-

jar.xml) from the compression package before the real

deployment. When parsing the XML formatted configuration file, some potential

dependent resources will be detected. And then,

with deployer's confirmation, the exact dependent resources will

be created (if does not exist before) and the

dependency relation will be saved.

When an application is supposed to be undeployed bythe administrator, the server will judge whether the dependent resources can be deleted. For example, if a JDBC data source is used by multiple applications, it can be deleted only when all the relative applications have been undeployed.

J2EE Application User Interactive Deployment Process

Firstly, the user uploaded the artifact to server.


Page 2 of 4

After the VendorServiceEAR.ear is uploaded successfully, server will extract VendorServiceEAR.ear/




web.xml and parse it.


[This page contains 1 picture or other non-text object]

Page 3 of 4


[This page contains 1 picture or other non-text object]

Page 4 of 4

Third, the server asks for deployer's confirmation of the potentially dependent resources to be cr...