Chapter 3 Managing Applications and Packages in Jaguar Manager
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:
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 10, "Importing and Exporting Application Components" in the EAServer System Administration Guide.
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 EAServer as a J2EE application. See the PowerJ documentation for
more information on using PowerJ with EAServer.
You can applications manually or by importing an EAR file. An application must be installed into a server in Jaguar Manager before the application's EJBs, servlets, or JSPs can run on that server.
Creating an application manually
Installing 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:
Installing 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:
Installing 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:
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.
You can enter optional text in the Description field to document your application.
These settings map role names used in the application's packages and Web applications to role names that exist in Jaguar Manager.
Mapping a J2EE role to an EAServer role
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 Chapter 28, "Configuring Custom Java Class Lists" for more information.
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.
Configures the default JAXP, DOM, and XSLT parser implementations used by EJB components and Web applications in the application. See Chapter 27, "Configuring Java XML Parser Support" for more information on these properties.
For advanced users only. The All Properties tab allows you to hand edit property settings in the EAServer configuration repository.
For information on repository properties, see the chapter, "Repository Properties Reference," in the EAServer System Administration Guide
Copyright © 2002 Sybase, Inc. All rights reserved. |
![]() |