WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Installing an edition

Installing an application edition is similar to installing an application. Both are Java™ 2 Platform, Enterprise Edition (J2EE) 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 you install your application edition, you must create a deployment target for your application. A deployment target is a server or cluster with all members on the latest version of WebSphere Application Server.

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

  1. Begin the steps to install the application. In the administrative console, click Applications > Install new application. Enter the following information in the wizard panels:
    1. Specify the application type.
    2. Specify the EAR, WAR, JAR, or SAR module to upload and install.
    3. Optional: For enterprise applications: If you want 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 ~!@#$%.-.

    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.

  3. Specify the installation options. In the Application description field, specify the type of edition you are installing. For example, type First edition.
  4. 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 enterprise archive (EAR) file that contains a Web application module and the enterprise beans module is installed in the WebSphere Extended Deployment environment. As a result, the Web application module is installed on a server and the enterprise beans module is deployed on a cluster.
  5. Optional: To save time and reuse work classes, you can choose an existing edition of the application to clone. On the first administrative console panel of the application installation, you must 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 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.
  6. Specify the location of the virtual host for the Web modules, and edit the context root that is defined in the deployment descriptor file.
  7. Click Save to synchronize your nodes.
  8. 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.




Related tasks
Performing a rollout on an edition
Deploying enterprise applications
Related reference
Administrative roles and privileges
Task topic    

Terms of Use | Feedback

Last updated: Oct 16, 2009 11:09:26 AM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/appedition/tappedinst.html