Deploying Web applications  Deploying application clients

Chapter 9: Importing and Exporting Application Components

Deploying J2EE applications

You can export applications from EAServer Manager to deploy them on another server. EAServer supports two archive formats for applications:

NoteConsider synchronization instead of archives If you are deploying between EAServer installations, you may find synchronization easier than exporting and importing archives. Synchronization replicates an application directly between servers. See Chapter 6, “Clusters and Synchronization”for more information.

StepsExporting an application

  1. Expand the top-level Applications folder.

  2. Highlight the application to export. If you are exporting an EAR file, choose File | Export | J2EE EAR. If you are exporting an EAServer JAR, choose File | Export | EAServer JAR.

  3. In the Export wizard:

    1. Enter the name of the EAR or JAR file to create including the full directory path and the .ear or .jar extension.

    2. If exporting in EAR format, optionally deselect the Export with EAServer XML Configuration File option if you do not want the archive to include an EAServer XML configuration file.

  4. Click Next. EAServer Manager creates the EAR or JAR file, displaying status messages in the Export wizard.

StepsImporting an application

  1. Highlight the top-level Applications folder. If you are importing an EAR file, choose File | Deploy | J2EE EAR. Otherwise, choose File | Deploy | EAServer JAR.

  2. Enter the path to the EAR or JAR file.

  3. If importing an EAR file, choose a deployment strategy. Table 9-1 describes the deployment strategy options.

  4. If importing an EAR file, configure the deployment options:

    NoteWhen you are deploying an EAR or EJB-JAR file containing a sybase-easerver-config.xml file, which was previously exported from EAServer, do not use the JAR File Naming option. When exporting packages to a J2EE archive file, EAServer optionally creates a sybase-easerver-config.xml file that includes configuration information based on the package names. If you deploy a package or an application that contains packages with the JAR File Naming option, EAServer renames the packages. When the package names do not match the names in the sybase-easerver-config.xml file, deployment fails.

  5. Click Next. The Deploy wizard reads the EAR or JAR file and creates a new application. Any errors display in the status window. Review the status information, then click Close.


What is created during import

When you import an EAServer JAR, the Deploy wizard creates an application identical to the original.

When you import an EAR, the Deploy wizard creates:

If the EAR file did not contain EAServer XML configuration files, you may need to configure the following settings in the Component or Web Application Properties dialog boxes before running EJBs, servlets, or JSPs:

Other settings have been configured by the Deploy wizard.

NoteUse the status dialog as a to-do list In the deployment status dialog box, EAServer Manager displays warnings for each setting that requires further attention before you run the application. You can copy and paste this text to a text editor to use as a to-do list.





Copyright © 2005. Sybase Inc. All rights reserved. Deploying application clients