About Packaged Archive Projects
See Also
If you have a Java EE application that you need to deploy to a server
different from the server for which the application was developed, you might need to make
some adjustments to that application.
The IDE provides the Packaged Archive project type to simplify this redeployment
process. A packaged archive project is based on an existing binary archive file, such as a JAR file,
a WAR file, an EAR file, an RAR file or a CAR file. Assuming the application and server are both Java EE-compliant,
you do not need to change any Java source code before redeploying the application.
Packaged archive projects have the following advantages:
- You do not have to have the original sources for the project.
- The application on which you base the archive project does not have to
have been developed in IDE.
- When you build a packaged archive project, a new archive is generated.
The copy of the archive on which you base the project is not affected.
When you create a packaged archive project, the IDE creates a new project that
contains the following files:
- New copies of important configuration files, such as
deployment descriptors and archive manifests.
You can view these file's
in the Projects window by expanding the project's Config Files node.
If the
configuration files belong to an archive file that is packaged within
the archive file that the project is based on, you can find them
by expanding the Config node for that archive file. (For example, if your
packaged archive project is based on an EAR file, you would have two
or more sub-archive files, such as WAR files or EJB JAR files.)
- A setup folder (represented by the Server Resources node in the Projects window)
that can contain items such as JDBC connection pools, JMS resources, and so on.
After you have created the packaged archive project, you can do the following things:
- Delete or modify the existing configuration files and resource files as necessary.
- Add new configuration and resource files as required by the server to which
you are deploying.
- Repackage the archive by right-clicking the packaged archive project's
node and choosing Build.
- Verify the Java EE-compliance of the project by right-clicking the
project's node and choosing Verify.
- Deploy the repackaged application to the new server by right-clicking
the project's node and choosing Deploy.
- Change the application server to which you want to deploy by opening
the Project Properties dialog box and changing the Server property.
- See Also
- Redeploying a Project to a Different Server
- About Deployment Descriptors
- About Standard Projects
- About Free-Form Projects
Legal Notices