Exporting J2EE applications

You can export an enterprise application to a location of your choice.

Overview

To export applications, use the Export button on the Enterprise Applications page. Using Export produces an enhanced enterprise archive (EAR) file that contains the application as well as the deployment configuration. The deployment configuration consists of the deployment.xml and other configuration files that control the application behavior on a deployment target.

Procedure

1. Click ApplicationsEnterprise Applications in the console navigation tree to access the Enterprise Applications page.

2. Select the check box beside the application and click Export.

3. On the Export Application EAR Files page, click on the link to download the exported EAR file.

4. Use the browser dialogue to specify a location at which to save the exported EAR file.

   User profile QEJBSVR must have *WX authority to the directory and at least *X authority to all directories in the path specified for the location.

5. Click Back to return to the Enterprise Applications page.

Results

Using the Export button to export applications does not export any manual changes that were made to applications in the installedApps directory. To export those changes, copy and move the application files manually.

What to do next

To reinstall the enhanced EAR file, do either of the following:

• Use the Update operation available from the Enterprise Applications page to upgrade the existing application installation.

  The Update operation adds the application files to the app_server_root/profiles/installedApps/cell_name directory, where cell_name is the current cell name or the name of the cell that you specified for Directory to install application when you first installed the application on a deployment target. The Directory to install application setting is on the Select installation options panel of the application installation wizard. If you specified the $(CELL) variable for Directory to install application when you first installed the application, the cell_name directory is the current cell name.

• Use the Install New Application operation to install the exported EAR file.

  If you specified the $(CELL) variable for Directory to install application when you first installed the application, the cell_name directory is the current cell name. That is, if the file is originally installed on Cell1 with $(CELL) variable in the destination directory and you reinstall the enhanced EAR file on Cell2, the cell_name directory is Cell2, the current cell name.

  If the $(CELL) variable was not specified for the first installation, using Install New Application to reinstall an enhanced EAR file installs the application in the cell_name directory of the exported application. That is, if the application is originally installed on and exported from Cell1 and you reinstall the enhanced EAR file on Cell2, the cell_name directory is Cell1. The enhanced EAR file expands in the Cell1 directory even though the current cell name is Cell2. By default, the application destination directory contains Cell1 in its path because the deployment.xml file in the exported application has Cell1 in it.

  If you exported the application from Cell1 and did not specify the $(CELL) variable when first installing the application, and you want to install the enhanced EAR file on a different cell, deselect Process embedded configuration on the Select installation options panel of the application installation wizard to expand the enhanced EAR file in the current cell name directory, which is not Cell1.

Related Reference