Install an application edition

Installing an application edition is similar to installing an application. When installing a new edition of an application, the edition must be specified.

• Before installing the application edition, create a deployment target for the application.

• If we are a user with either a monitor or an operator role, then we can view the application edition manager information only. If we have the role of configurator or administrator, then we have all the configuration privileges for the application edition manager.

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. We can also clone an existing edition.

Install an application edition

1. Install the application...
   Applications > Install new application or Applications > Install new middleware application

   In the wizard panels.

   1. Specify the application type.

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

   3. For enterprise applications, to clone work classes from another edition of the application, select..
      Show me all installation options and parameters

2. 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 ~!@#$%.-.

   SIP, Java EE applications: The edition identifier becomes part of a directory name under which the application is installed. Any character used in a file name on the system can also be used in the edition identifier.

   For PHP Hypertext Preprocessor (PHP), WebSphere Application Server Community Edition and unmanaged web applications, the edition identifier becomes a configuration attribute in the repository and accepts any characters.

   Ensure you enter a value for the edition; otherwise, a new edition of an application cannot be created.

3. Specify the installation options. In the Application description field, specify the type of edition we are installing. For example, type First edition.

4. Specify the deployment targets for the application.
   • If we are installing an enterprise application, we can use split deployment. With split deployment, we deploy a module in a single Java EE application archive and divide the module across multiple deployment targets. For example, we might deploy an EAR file containing a web application module and the enterprise beans module is installed in the Intelligent Management environment. As a result, the web application module is installed on a server and the enterprise beans module is deployed on a cluster.

   • For 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.

   • For PHP and WAS 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 WAS Community Edition servers or dynamic clusters for WAS Community Edition applications.

5. Optional: If we are installing an enterprise application: To save time and reuse work classes, we can choose an existing edition of the application to clone. On the first administrative console panel of the application installation, select the Show me all installation options and parameters option to see the clone work classes option. 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 we select an existing application edition, all of its work classes are cloned with the defaults appropriately renamed with the new application edition name. If we do not select an application edition, the defaults are created.

6. Specify the location of the virtual host for the web modules, and edit the context root defined in the deployment descriptor file.

7. Save and synchronize the nodes.

8. Start the application.
   • Enterprise applications: In the administrative console, select...
     Applications > Enterprise applications > application_name > Start

   • For PHP applications, in the administrative console, select...
     All applications PHP application > Start > Submit

     This action starts all of the PHP servers associated with this application. To start the servers individually, select...

     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.

   • WAS Community Edition applications: Start application editions individually. In the administrative console, select..
     Applications > Edition control center > application_name > Activate

What to do next

Now that the application edition is installed, we can perform a rollout, backout, concurrent activation, or validation.

Perform a rollout on an edition

Deploy enterprise applications

Deploy unmanaged Web applications

Deploy PHP applications

Deploy WAS Community Edition applications (deprecated)

Intelligent Management: administrative roles and privileges

Intelligent Management: application edition management administrative tasks