Defining
packages

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 are a unit of deployment Using EAServer Manager, you can import and export archived
copies of the components in a package and related application files.

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:

Creating a new package

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

The new package appears on the right side of the screen when
you highlight the package icon.

Package names must begin with a letter, are not case
sensitive, and must be unique
Package names must be unique among other packages in the same
EAServer installation, and begin with a letter.

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.

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.

Installing packages

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:

Install an existing package A list of uninstalled packages appears in the dialog box.
Highlight the package you want to install, and click Ok.

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
packages

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

Remove Package If you have selected a package that is installed in a server
or application, this option removes the package from the server.

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.

Configuring package properties

The Package Properties window has two tabs, General and Advanced.

Package properties: General

The following table describes the properties on the General
tab.

Table 3-1: Package properties: General tab

Property

Description

Comments/example

Description

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.

Package properties: Java Classes

Package properties: Additional Files

Configures the com.sybase.jaguar.package.files property,
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.

Package properties: JAXP Support

Package Properties: Advanced

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.

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.