Installing the Mobile Portal Accelerator instance WP01 (existing WebSphere Portal cluster)

The first step in this process is to install IBM® Mobile Portal Accelerator on the primary node of the WebSphere® Portal cluster.

1. Follow the instructions in the topics Performing required steps before installing Mobile Portal Accelerator and Performing recommended steps before installing Mobile Portal Accelerator in this information center.
2. Follow the instructions in the topic Installing Multi-Channel Server for your database type (DB2®, Oracle, or Microsoft SQL Server).
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:
   • ./ConfigEngine.sh mwp-config-cluster-primary-node
   • ConfigEngine mwp-config-cluster-primary-node
7. Import Mobile Portal Accelerator policies into the MCS policy repository. Run the following command to import XDIME aggregator policies and generic portlet policies:
   • ./ConfigEngine.sh mwp-import-policies
   • ConfigEngine mwp-import-policies
   Note: The result of the import tasks are displayed on the screen and logged to the wp_profile_root/ConfigEngine/log/ConfigTrace.log file. If errors occur during any imports, correct the problems and rerun any import tasks that failed.
8. Import Mobile Welcome portlet policies using the following command:
   • ./ConfigEngine.sh mwp-import-portlet-policies
   • ConfigEngine mwp-import-portlet-policies
   Note: The results of the import tasks are displayed on the screen and logged to the wp_profile_root/ConfigEngine/log/ConfigTrace.log file. If errors occur during any imports, correct the problems and rerun any import tasks that failed.
9. 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.