Installing an application edition is similar to installing an application. Both are Java 2 Platform, Enterprise Edition applications
and are installed following the WebSphere Application Server and WebSphere
Extended Deployment application installation processes. The only difference
is that during the process you specify edition and edition description information.
Before you begin
Before installing your application edition, you must create a deployment
target for your application.
A deployment target
is a server or cluster with all members on a WebSphere Application Server
Version 6 product. For more information, see Installable module versions.If you
are a user with either a monitor or an operator role, you can only view the
application edition manager information. If you have the role of configurator
or administrator, you have all the configuration privileges for the application
edition manager.
About this task
Multiple versions of the same shared library can be installed if
they are given different names during creation. Use a naming scheme that adds
a version number to the shared library name, for example, Production
Library 1.0 and Production Library 2.0. Each edition
of an application can be updated to use a distinct version of the shared
library by binding the edition to the appropriate library. You can also clone
an existing edition.
Procedure
- Begin the steps to install the application. In the administrative
console, click Applications > Install new application.
- In the Application edition field, specify your edition information.
For example, type 1.0. The edition identifier
does not have to be numeric, and can be any combination of letters, numbers,
and certain special characters, such as ~!@#$%.-.
The edition identifier
becomes part of a directory name under which the application is installed.
Any character that can be used in a file name on your system can also be used
in the edition identifier.
- In the Application Description field, specify the type of
edition you are installing. For example, type First
edition.
- Specify the deployment targets for the application.
- Enterprise applications: On the Map
modules to servers page, from the Clusters and Servers list, select
a deployment target. With split deployment,
you deploy a module in a single J2EE application archive and divide the module
across multiple deployment targets. For example, you might deploy an EAR file
that contains a Web application module and the enterprise beans module is
installed in the WebSphere Extended Deployment environment. Thus, the Web
application module is installed on a server and the enterprise beans module
is deployed on a cluster.
- Optional: To save time, and reuse work classes,
you can choose an existing edition of the application to clone. From
the Clone existing work classes from this application edition list,
select the work class, and click Next. The work class
establishes default routing rules for the application edition. The work classes
of an application constitute the routing policy of that application. If you
select an existing edition, all of its work classes are cloned with the defaults
appropriately renamed with the new application edition name. If you do not
select an edition, the defaults are created.
- Save and synchronize your nodes.
- Start the application.
- Enterprise applications: In the administrative console, click Applications
> Enterprise applications. Select the application, and click Start.
What to do next
Now, that your edition is installed, you can perform a rollout, backout,
concurrent activation, or validation.