Install an edition

Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Installing an edition

Installing an application edition is similar to installing an application. The only difference is that during the process, you specify edition and edition description information.

Before you begin

Before you install your application edition, create a deployment target for your application.
If you are a user with either a monitor or an operator role, then you can view the application edition manager information only. If you have the role of configurator or administrator, then you have all the configuration privileges for the application edition manager.

About this task

Multiple versions of the same shared library are installed if you give them 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 is 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 or Applications > Install new middleware application . Enter the following information in the wizard panels:

Specify the application type.
Specify the EAR, WAR, JAR, or SAR module to upload and install.

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 ~!@#$%.-.
Session Initiation Protocol (SIP), Java™ Enterprise Edition 5 (Java EE) applications: The edition identifier becomes part of a directory name under which the application is installed. Any character that you use in a file name on your system can also be used in the edition identifier.
PHP Hypertext Preprocessor (PHP), WebSphere^® Application Server Community Edition, unmanaged Web applications: The edition identifier becomes a configuration attribute in the repository and accepts any characters.
Specify the installation options. 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, Session Intiation Protocol (SIP) applications: If you are installing an enterprise application, then you can use split deployment. 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 enterprise archive (EAR) file that contains a Web application module and the enterprise beans module is installed in the WebSphere Virtual Enterprise environment. As a result, the Web application module is installed on a server and the enterprise beans module is deployed on a cluster.
Unmanaged Web applications: Define the deployment properties of the application. Specify module, context root, and virtual host information for the application. Choose the servers and clusters on which the application is deployed by selecting deployment targets.
PHP, WebSphere Application Server Community Edition applications: Choose the servers and clusters on which the application runs by selecting the deployment targets. Choose PHP servers or PHP dynamic clusters for PHP applications. Choose WebSphere Application Server Community Edition servers or dynamic clusters for WebSphere Application Server Community Edition applications.

Optional: If you are installing an enterprise application: 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, then 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, then the defaults are created.
Specify the location of the virtual host for the Web modules, and edit the context root that is defined in the deployment descriptor file.
Click Save to synchronize your nodes.
Start the application.

Enterprise applications: In the administrative console, click Applications > Enterprise applications. Select the application, and click Start.
PHP applications: In the administrative console, click All applications. Select the PHP application that you want to start. Choose the Start action, and click Submit. This action starts all of the PHP servers that are associated with this application. To start the servers individually, click Servers > Other middleware servers > PHP servers.
Unmanaged Web applications: The application is displayed as started when the server on which the application is deployed starts.
WebSphere Application Server Community Edition applications: Start application editions individually. In the administrative console, click Applications > Edition control center > application_name > Activate.

What to do next

Now that your edition is installed, you can perform a rollout, backout, concurrent activation, or validation.

Related tasks

Rollout an edition
Deploying unmanaged Web applications
Deploying PHP applications
Deploying WebSphere Application Server Community Edition applications
Deploying enterprise applications

Related reference

Administrative roles and privileges
Related information

Application edition management administrative tasks