Installing the Mobile Portal Accelerator instance WP02 (creating new cluster)—horizontal scaling

After installing Mobile Portal Accelerator on WP01, the next step in this process is to install IBM® Mobile Portal Accelerator instance WP02.

1. Follow the instructions provided in the Performing required steps before installing Mobile Portal Accelerator.
   Note: Because this is a secondary node, it is not necessary to migrate the WebSphere Portal database from Derby to DB2®, Oracle, or Microsoft SQL Server.
2. Follow the procedures in the topic Installing Multi-Channel Server for your database type (DB2, Oracle, or Microsoft SQL Server).
   Also, be advised of the following important items:

   • Do not create another MCS database, because you will use the same MCS database information created by the WP01 instance. Make sure to use the identical values for the following parameters in both WP01 and WP02:

     DMcsRepositoryType, 
     DMcsDbVendor, 
     DMcsDbHost, 
     DMcsDbPort, 
     DMcsDbSource, 
     DMcsDbUser, 
     DMcsDbPassword 

   • Do not run the following command, because the default device policies were imported when you installed MCS on WP01:
     • ./ConfigEngine.sh init mcs-import-devices -DMcsProject=mobile-portal
     • ConfigEngine init mcs-import-devices -DMcsProject=mobile-portal
3. Use the appropriate database-specific commands to add the JDBC driver to your current CLASSPATH environment variable, as illustrated in the following examples:
   (version 9.1 (with fix pack 5) or 9.5 (with fix pack 3))

   CLASSPATH=db_root/db2instance/sqllib/java/db2jcc.jar:
             db_root/db2instance/sqllib/java/db2jcc_license_cu.jar:$CLASSPATH
   export CLASSPATH   

   (version 9.7)

   CLASSPATH=db_root/db2instance/sqllib/java/db2jcc4.jar:
             db_root/db2instance/sqllib/java/db2jcc_license_cu.jar:$CLASSPATH
   export CLASSPATH   

   Note: If DB2 and WebSphere Portal are not installed on the same machine, specify the path to where the files are located on the WebSphere Portal server.
   

   CLASSPATH=oracle_driver_path/ojdbc6.jar:$CLASSPATH
   export CLASSPATH

   MS SQL

   CLASSPATH=mssql_driver_path\sqljdbc4.jar:$CLASSPATH
   export CLASSPATH

4. Change your working directory to:wp_profile_root/ConfigEngine
5. Make sure that the correct values are specified for the following parameters in the file wp_profile_root/ConfigEngine/properties/wkplc.properties:
   • WasHome
   • WpsInstallLocation
   • NodeName
   • ServerName
   • PortalAdminId
   • PortalAdminPwd
   • WpsHostPort
   • WpsContextRoot

   If WebSphere Application Server security is enabled, you must also specify values for the WasUserid and WasPassword parameters in wp_profile_root/ConfigEngine/properties/wkplc.properties.

   Note: For security reasons, if you do not want to store the WebSphere Portal admin password and WebSphere Application Server admin password in the wkplc.properties file, you can specify the passwords on the portal server command line. For example, when this topic directs you to enter the ConfigEngine script or batch file, you would add parameters to the command to specify the password values as shown here:

   

   ./ConfigEngine.sh init task_name -DPortalAdminPwd=WP_admin_password_value -DWasPassword=WAS_admin_password_value

   

   ConfigEngine init task_name -DPortalAdminPwd=WP_admin_password_value -DWasPassword=WAS_admin_password_value

   Note: All of this text, including parameters, is entered on the same command line.

   where:

   • task_name is the name of the configuration task being invoked (for example, mcs-deploy-mcs)
   • WP_admin_password_value is the value of the WebSphere Portal admin password
   • WAS_admin_password_value is the value of the WebSphere Application Server admin password if WebSphere Application Server security is enabled
6. Install and configure the Mobile Portal Accelerator extensions using the following command for every instance on the secondary nodes:
   

   ./ConfigEngine.sh mwp-config-cluster-secondary-node

   

   ConfigEngine.sh mwp-config-cluster-secondary-node

7. Run the Health Check Utility to check the status of the Mobile Portal Accelerator installation using the following command:
   • ./ConfigEngine.sh check-mobile-install -DMPAInstallZip=/tmp
   • ConfigEngine check-mobile-install -DMPAInstallZip=c:\mpa_temp
   The output displays the directory locations for files that are required by WebSphere Portal and Mobile Portal Accelerator.

   • If all of the files were installed successfully, the message BUILD SUCCESSFUL is displayed. Proceed to the next step.
   • If the utility detected a problem with the installation, the message BUILD FAILED is displayed. This indicates that files required by Mobile Portal Accelerator are not installed in the proper locations. Check the output for a description of the problem. Then, make sure that the image zip files are complete, or not corrupted due to a failed copy or lack of disk space; compare the file sizes against the original media. You can also verify that disk space or permissions are sufficient. Next, you will need to uninstall and re-install Mobile Portal Accelerator. After the re-install, run the Health Check Utility again.
8. Restart the portal server using the following commands:
   

   wp_profile_root/bin/stopServer.sh server_name -username WAS_admin -password WAS_admin_password_value

   wp_profile_root/bin/startServer.sh server_name

   

   wp_profile_root\bin\stopServer server_name -username WAS_admin -password WAS_admin_password_value

   wp_profile_root\bin\startServer server_name

   where server_name is the name of the WebSphere Application Server instance (for example, WebSphere_Portal).