Chapter 3: Managing Applications and Packages in EAServer Manager
In EAServer Manager, a package contains a group of related components. Typically, components in a package work together to provide a coherent service or function.
Refresh when you modify a package, component, or method When you modify an existing package, component, or method, you must refresh the server, package, or component for the changes to take effect. To refresh, highlight the icon for the server, package, or component and select File | Refresh. If you modify a component’s supported interfaces, you must regenerate stubs and skeletons for the component and clients that access the component.
You must install your components in packages before applications can access the components. Packages serve the following purposes:
They allow you to control which users can access components Packages form one level in the EAServer authorization hierarchy. A package is not available on a server unless it is installed in the server’s Installed Packages folder. To further restrict access for non-EJB components, you can edit the package’s required Role Memberships to restrict which users can access components in the package. You can also control access on the individual component level. Chapter 2, “Securing Component Access,” in the EAServer Security Administration and Programming Guide describes options for configuring user authorization for package and component access. EJB components use a different security mechanism described in “Configuring role references and method permissions”.
In a cluster, they allow you to partition the load By installing different subsets of packages to the servers in a cluster, you can control which components execute on which servers within the cluster. See Chapter 7, “Load Balancing, Failover, and Component Availability,” in the EAServer System Administration Guide for more information.
Use EAServer Manager to create, modify, and delete packages, as described in the sections below:
You can also export and import package archives in the standard EJB-JAR format or in the Jaguar JAR format. For details, see Chapter 9, “Importing and Exporting Application Components,” in the EAServer System Administration Guide.
Creating a new package
Start EAServer Manager if it is not running, and connect to your server.
Expand the EAServer Manager icon.
Highlight the Packages icon.
Select File | New Package.
Enter the name of the new package. The name must not match any existing package defined in the EAServer repository. To avoid name collisions, you can use the Java reverse domain naming style; for example, “com.foo.finance.”
Supply the package information. The properties are described in “Configuring package properties”.
The new package appears on the right side of the screen when you highlight the package icon.
Names are not case sensitive. Your packages must have unique names that differ in ways other than letter case. For example, you cannot define two packages named MyPack and mypack in the same EAServer installation. You cannot have two packages with the same name, even if one is installed in an application and the other is not.
Copying package definitions
Use the Copy item in the package Edit menu to create a copy of a package. EAServer Manager creates a copy of the package definition and the definitions of the components it contains. You can modify the new package and component properties without affecting the original. However, the copied and original definitions refer to the same IDL interfaces and implementation files.
You cannot copy packages that are installed in an application. Packages that appear in the top-level Packages folder can be copied as follows:
In the top-level Packages folder, highlight the icon for the package to be copied.
Choose File | Copy.
Enter a unique name for the new package and click Ok.
EAServer Manager creates a copy with the specified name.
The Paste command in the package Edit menu pastes copied component definitions. See “Copying and pasting components”.
Except for packages used internally by EAServer, packages to be run on a server must be installed in that server, using one of two methods:
Add the package to the server’s Installed Packages folder.
Add the package to an application’s Installed Packages folder, then install the application to the server. See Chapter 3, “Managing Applications and Packages in EAServer Manager” describes this method.
Packages that you create must be installed in a server before that server’s clients can access components in the 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.
Default packages EAServer includes a set of default packages that include components used internally by EAServer. These packages are available whether or not they are installed to a server’s Packages folder. These include the packages: CosConcurrencyControl, CosNaming, CosTransactions, CtsComponents, CtsSecurity, DataWindow, EncinaInternal, EncinaOTS, JTS, Jaguar, JaguarOTS, JaguarProxy, JaguarServlet, OtsAdmin, PBDebugger, Proxy, TranLog. The list of default packages is subject to change without notice.
Double-click the Servers folder to expand it.
Double-click the server (listed on the left side of the screen) to which you want to install a package.
Highlight the Installed Packages icon. A list of installed packages appears on the right.
Select File |Install Package. Then select one of the following options from the Package Wizard:
Create and install a new package Enter the name of the new package you want to install. Supply the package information, and click Ok. The properties are described in “Configuring package properties”.
Modifying an existing package
Highlight the package you want to modify. You can highlight the package icon displayed in a server’s package folder or in the main Packages folder (both icons represent the same package as long as the package names are identical).
From the File menu, select one of the following options:
Package Properties Displays the Package Properties window described in “Configuring package properties”. Make any modifications required, and click Ok.
Delete Package Deletes the package from the system. You can choose between simple and full deletion. Simple deleletion removes only the package properties file. Full deletion removes all files that have been generated by the deployment of the package, including component stubs and skeletons and IDL interface and datatype definitions. By default, EAServer performs a full deletion.
Default packages cannot be modified or deleted EAServer’s default packages cannot be modified or deleted, and you cannot modify or delete components installed in default packages. These components are run internally by EAServer. See “Default packages” for more information.
The Package Properties window has two tabs, General and Advanced.
The following table describes the properties on the General tab.
A description of the package. The description can be up to 255 characters.
View or change the description of an existing component or set the description of a new one.
This tab allows you to define a custom class list shared by all components that are installed in the package. See “Custom class lists for packages, applications, or servers” for more information.
which specifies additional files that are to be archived when the
package is exported or replicated to another server with the synchronize
feature. By default, the file set includes the files associated
with components in the package.
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.
These settings map role names used in EJB components to role names that exist in EAServer Manager.
Mapping a J2EE role to an EAServer role
If necessary, define a new EAServer role as described in “Configuring EAServer roles” in the EAServer Security Administration and Programming Guide for instructions.
Select the Role Mapping tab from the Web application properties window.
Click Add. Double-click the J2EE role and enter a name. You can also enter a description for the role in the provided field.
Select an EAServer role from the drop-down list. This is the role from which the J2EE role inherits its permissions and members.
Configures the default JAXP, DOM, and XSLT parser implementations used by EJB components in the package. See Chapter 36, “Configuring Java XML Parser Support,”for more information on these properties.
The Advanced tab allows you to edit package property settings as they are stored in the EAServer configuration repository. You can only delete properties that you have added—you cannot delete default properties, such as the com.sybase.jaguar.package.name property.
For information on repository properties, see Appendix B, “Repository Properties Reference,” in the EAServer System Administration Guide.
Look for the property name in the list of properties. If it is displayed, highlight the property and click Modify. Otherwise, click Add.
If adding the property, fill in the Add Property fields as follows:
Enter the property name in the Name field
Enter the value in the Value field.
If modifying a property, edit the displayed value in the Modify Property window.
When to use the Advanced tab Though you can use the Advanced tab to set any property prefixed with com.sybase.jaguar.package, Sybase recommends that you use this tab to set properties only as specified by the EAServer documentation or by Sybase Technical Support. Most properties can be configured graphically elsewhere in the EAServer Manager user interface.
|Copyright © 2005. Sybase Inc. All rights reserved.|