Chapter 4 Managing Applications and Packages in Jaguar Manager

Defining applications

In Jaguar Manager, Applications allow you to group related packages and Web applications into a single entity. In this way, you can deploy related business logic components, Web application components, and Web pages as a single unit between servers. For information on Packages and Web applications, see:

• "Defining packages"
• Chapter 22, "Creating Web Applications"

Jaguar Manager allows you to import applications that have been archived in the standard J2EE Enterprise Archive (EAR) file format. You can also export an application from Jaguar Manager in this format.

A future Jaguar version will allow you to define and configure standalone Java clients within an application, as specified by Sun's J2EE Specification.

   J2EE application deployment from PowerJ PowerJ provides an integrated environment for developing EJB 1.1 components, Java Servlets, JSPs, and Web applications and deploying them to Jaguar as a J2EE application. See the EAServer Feature Guide for more information on using PowerJ with Jaguar.

Creating and installing applications

You can applications manually or by importing an EAR file. An application must be installed in a Jaguar server before its EJBs, servlets, or JSPs can run on that server.

To create an application manually

1. Highlight the top level Applications folder and choose File | New Application.
   
   
2. Enter a unique name for the application and click Ok.
   
   

To install a package

You can only install a package in one application. Once a package is installed in an application, it cannot be installed directly in a server. Install a package in your application as follows:

1. If necessary, expand the top level Applications folder.
   
   
2. If necessary, expand the icon for your application.
   
   
3. Highlight the Installed Packages folder beneath the application and choose File | Install Package.
   
   
4. Select the name of the package to install and click OK.
   
   

To install a Web application

You can only install a Web application in one application. Once a Web application is installed an application, it cannot be installed directly in a server. Install a Web application in your application as follows:

1. If necessary, expand the top level Applications folder.
   
   
2. If necessary, expand the icon for your application.
   
   
3. Highlight the Installed Web Applications folder beneath the application and choose File | Install Web Application.
   
   
4. Select the name of the Web application to install and click OK.
   
   

To install an application in a server

You must install your application in a server before the server's clients can call the application's components, servlets, and JSPs. Install your application as follows:

1. If necessary, expand the server's icon by double clicking on it.
   
   
2. Highlight the Installed Applications folder beneath the server icon and choose File | Install Application.
   
   
3. Choose the application to be installed from the list and click Ok.
   
   

Configuring application properties

To display an application's properties, highlight the application's icon, then choose File | Application Properties. You can configure the settings described below in the Application Properties dialog box that displays.

Application properties: General

You can enter optional text in the Description field to document your application.

Application properties: Role Mapping

These settings map role names used in the application's packages and Web applications to role names that exist in Jaguar Manager.

To map a J2EE role to a Jaguar role:

1. Select the Role Mapping tab from the Web application properties window.
   
   
2. Click Add. Double-click the J2EE role and enter a name. You can also enter a description for the role in the provided field.
   
   
3. Select a Jaguar role from the drop-down list. This is the role from which the J2EE role inherits its permissions and members.
   
   Refer to the Jaguar System Administration Guide for more information about Jaguar roles.
   
   

Application properties: All Properties

For advanced users only. The All Properties tab allows you to hand edit property settings in the Jaguar configuration repository. Properties are listed in the documentation for the Jaguar::Repository IDL interface, in the description of the define method. Any property prefixed with "com.sybase.jaguar.application" can be set on this tab.

Importing and exporting applications

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

• J2EE enterprise archive (EAR) The EAR format is the standard for servers that support J2EE. This format allows portability to other vendor's J2EE servers, but does not support component types other than EJB or container-specific information such as:
  • Role mappings
  • Resource references
  • EJB references (to components that are not installed with the EAR file)
  • Environment properties
  
  These items must be configured manually after importing an EAR file.
  
• Jaguar JAR For exporting between Jaguar 3.6 or later servers. This format, while proprietary, preserves all information in the application and supports component types other than EJB. When importing, EJB references, resource references, and role mappings are preserved. You must ensure that the referenced items are in place before running the imported application.

   Consider synchronization instead of archives If you are deploying between Jaguar servers, you may find synchronization easier than exporting and importing archives. Synchronization replicates an application directly between servers. See Chapter 3, "Jaguar Clusters and Synchronization" in the Jaguar CTS System Administration Guide for more information.

To export an application:

1. Expand the top level Applications folder.
   
   
2. Highlight the application to export. If exporting an EAR file, choose File | Export | J2EE EAR. If exporting a Jaguar JAR, choose File | Export | Jaguar JAR.
   
   
3. In the Export Wizard, enter the name of the EAR or JAR file to create including the full directory path and the .ear or .jar extension.
   
   
4. Click Next. Jaguar Manager creates the EAR or JAR file, displaying status messages in the Export Wizard.
   
   

To import an application:

1. Highlight the top level Applications folder. If importing an EAR file, choose File | Deploy | J2EE EAR. Otherwise choose File | Deploy | Jaguar JAR.
   
   
2. Enter the path to the EAR or JAR file and click Next.
   
   
3. The Deploy Wizard will read the EAR or JAR file and create a new application. Any errors are displayed in the status window. Review the status information, then click Close.
   
   

What is created during import

When importing a Jaguar JAR, the Deploy wizard creates an application identical to the original.

When importing an EAR, the Deploy wizard creates the following:

• An application with the same name as the display name in the EAR file's XML descriptor. If there is no display name, the new application has the same name as the EAR file.
• For each EJB-JAR file in the EAR, a package with the same name as the EJB-JAR display name, or the name of the EJB-JAR file if there is no display name.
• For each Bean in an EJB-JAR file, an EJB component with the same name as the ejb-name element in the EJB-JAR deployment descriptor.

     Home names for imported EJB components When importing from EAR or EJB-JAR files, Jaguar sets an imported Bean's home name to the Jaguar default, package/component, where package is the Jaguar Manager package name, and component is the Jaguar Manager component name.

• For each WAR file in the EAR, a Web application with the same name as the display name in the WAR file's XML descriptor. If there is no display name, the new Web application has the same name as the WAR file.
• For each servlet defined in a WAR file, a Web application component with the same name as the servlet-name element in the Web application deployment descriptor.

You may need to configure the following settings in the Component or Web Application Properties dialog boxes before running EJBs, servlets, or JSPs:

• Role mappings
• Resource references
• EJB references (to components that are not installed with the EAR file)
• Environment properties

Other settings have been configured by the Deploy Wizard.

   Use the status dialog as a to-do list In the deployment status dialog box, Jaguar Manager display warnings for each setting that requires further attention before running the application. You can copy and paste this text to a text editor to use as a to-do list.

Copyright © 2000 Sybase, Inc. All rights reserved.