Install the MPF Foundation fix pack in a new cluster

You must create a new cluster, in which you install the MPF Foundation fix pack. Here, the procedure targets an installation in a WebSphere Application Server Network Deployment environment, in a single cell, with IBM HTTP Server and web server plug-ins for IBM WebSphere Application Server.

1. Create a cluster in IBM WebSphere Application Server. In the rest of this document, this cluster is called cluster_WL61FP1.

2. Create servers in this cluster.

3. For each server, set a weight of 0.

4. Install the MPF Foundation fix pack in this cluster. We can install this fix pack with the MPF Foundation Ant tasks, or manually.

   • To install this fix pack with the MPF Foundation Ant tasks, follow the steps 5 - 9.

   • To install this fix pack manually, follow the steps 10 - 14.

Install the fix pack with the MPF Foundation Ant tasks:

5. With IBM Installation Manager, install the MPF Foundation fix pack on the computer where the WebSphere Application Server Deployment Manager is installed.

   Do not install the Application Center.

6. Verify that WebSphere Application Server is not set to automatically generate and propagate the web plug-in. To be sure that the installation of the product fix-pack does not generate and propagate a new web plug-in that you did not review, perform the following steps.

   1. Open the WebSphere Application Server administration console.

   2. Go to Servers > Server Types > Web Servers.

   3. In the table, click the web server.

   4. Under Additional Properties, click Plug-in properties.

   5. Make sure that the check box for Automatically generate the plug-in configuration file is not selected.

   6. Make sure that the check box for Automatically propagate plug-in configuration file is not selected.

7. Copy the Ant file that we used to install IBM MobileFirst Platform Foundation in the cluster cluster_WL61.

   1. Modify the cluster name, for example ${was.nd.cluster.name} in the code example in step 8.

   2. Modify the environment ID.

      You use this environment ID to distinguish the Administration Services and MobileFirst runtime environment from the two clusters. The new ID also generates different application names to avoid name conflicts in the WebSphere Application Server cell.

   3. You must make these modifications for the following Ant tasks. Use the same environment ID in all the tasks.

      • configureapplicationserver

      • updateapplicationserver

      • unconfigureapplicationserver

      • installworklightadmin

      • updateworklightadmin

      • uninstallworklightadmin

      Important: The environment ID determines which instance of Administration Services manages the deployed runtime environments. All runtime environments must have the same environment ID as the MobileFirst Server administration components.

8. Run the adminstall target of the Ant file.

9. Run the install target of the Ant file that installs the MobileFirst runtime environment. If we have more than one MobileFirst runtime environment, repeat this operation for all of them:

   Do not change the database settings, the context roots, or the other parameters of the installation.

   <!-- Start of the install target Generated by Worklight -->
     <target name="install">
       <configureapplicationserver environmentId="${worklight.environment.id}" contextroot="${worklight.contextroot}" id="${worklight.deployment.id}">
         <project warfile="${worklight.project.war.file}"/>
         <applicationserver>
           <websphereapplicationserver installdir="${appserver.was.installdir}"
                                       profile="${appserver.was.profile}"
                                       user="${appserver.was.admin.name}"
                                       password="${appserver.was.admin.password}">
             <cluster name="${appserver.was.nd.cluster}"/>
           </websphereapplicationserver>
         </applicationserver>

Install the fix pack manually:

10. Install the data sources that point to the administration and MobileFirst runtime databases in the cluster.

    • For instructions about the administration database, see the following documentation:

      • Configure WebSphere Application Server for DB2 manually for MobileFirst Server administration

      • Configure WebSphere Application Server for Oracle manually for the MobileFirst Server administration

    • For instructions about the runtime database, see the following documentation:

      • Configure WebSphere Application Server for DB2 manually

      • Configure WebSphere Application Server for Oracle manually

11. Select a name for an environment ID used for all the web applications that you installed in step 12.

    For example, FP1.

    You must not have any other installation of IBM MobileFirst Platform Foundation in the WebSphere Application Server cell that is using the same environment ID.

12. Install the Administration Services as documented in Configure WebSphere Application Server for MobileFirst Server administration manually, with the following change:

    In Environment entries for Web modules for the Administration Services, set the value of ibm.worklight.admin.environmentid to the environment ID selected in step 11.

13. Install the MobileFirst runtime environment as documented in Configure WebSphere Application Server for MobileFirst Server administration manually, with the following change:

    In Environment entries for Web modules for the MobileFirst runtime environment, set the value of ibm.worklight.admin.environmentid to the environment ID selected in step 11.

14. Use a different name for the WebSphere applications than the one that we used in the first cluster.

Parent topic: Performing a rolling upgrade to install a fix pack