Chapter 3: Managing Applications and Packages in EAServer Manager  Defining packages

Chapter 3: Managing Applications and Packages in EAServer Manager

Defining applications

In EAServer 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:

You can import and export applications that have been archived in the standard J2EE Enterprise Archive (EAR) file format or the EAServer Jaguar JAR format. For details, see Chapter 9, “Importing and Exporting Application Components,” in the EAServer System Administration Guide.


Creating and installing applications

You can create applications manually or by importing an EAR file as described in Chapter 9, “Importing and Exporting Application Components,” in the EAServer System Administration Guide. An application must be installed into a server before the application’s EJBs, servlets, or JSPs can run on that server.

StepsCreating 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.

StepsInstalling 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.

StepsInstalling 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.

StepsInstalling 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.


Deleting and removing applications

To delete an application, highlight the application icon in EAServer Manager and choose File | Delete. You can choose between simple and full deletion. Simple deleletion removes only the application properties file and the properties files for components and Web applications installed in the application. Full deletion removes all files that have been generated by the deployment of the application, including component stubs and skeletons and IDL interface and datatype definitions. By default, EAServer performs a full deletion.

If you have installed an application in a server, you can remove it by highlighting the application icon in the server’s Installed Applications folder and choosing File | Remove. This operation does not delete any files associated with the application.


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 EAServer Manager.

StepsMapping a J2EE role to an EAServer 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 an EAServer role from the drop-down list. This is the role from which the J2EE role inherits its permissions and members.

    Refer to “Configuring EAServer roles” in the EAServer Security Administration and Programming Guide for more information about EAServer roles.


Application properties: Java Classes

This tab allows you to define a custom class list shared by all components and Web applications that are installed in the J2EE Application. See “Custom class lists for packages, applications, or servers” for more information.


Application properties: Additional Files

Configures the com.sybase.jaguar.application.files property, which specifies additional files that are to be archived when the application is exported or replicated to another server with the synchronize feature. By default, the file set includes the files associated with Web applications, application clients, and packages installed in the application.

The rules for setting this property are the same as for the com.sybase.jaguar.component.files component property. See “Component properties: Additional Files” for more information.


Application properties: JAXP Support

Configures the default JAXP, DOM, and XSLT parser implementations used by EJB components and Web applications in the application. See Chapter 36, “Configuring Java XML Parser Support,” for more information on these properties.


Application properties: Security

Security properties include:

Property

Description

Trusted Identities

Trusted identities must be configured for EJB 2.0 caller propagation from another server to the server where this application is deployed.Trusted identities can “vouch” for the client identity specified in the intercomponent call. For outgoing calls from this application to another server, configure the Security Identity property..

Security Identity

Specifies the identity used for outgoing component invocations when propagating client credentials to another server.

Run-as Identity

Specifies the identity used for intercomponent calls issued from EJBs or servlets. The identity specified here can be overridden in the package, Web application, or component properties.

For more information on these settings, see “Intercomponent authentication for EJBs and servlets” in the EAServer Security Administration and Programming Guide.


Application properties: Advanced

For advanced users only. The Advanced tab allows you to hand edit property settings in the EAServer configuration repository.

For information on repository properties, see Appendix B, “Repository Properties Reference,” in the EAServer System Administration Guide





Copyright © 2005. Sybase Inc. All rights reserved. Defining packages