Installing the Mobile Portal Accelerator instance WP02 (creating new cluster)—horizontal scalingAdded by IBM on October 1, 2012 | Version 1 (Original)
|After installing Mobile Portal Accelerator on WP01, the next step in this process is to install IBM® Mobile Portal Accelerator instance WP02.
You must have followed the instructions in the topic Installing the Mobile Portal Accelerator instance WP01 (creating new cluster)
before installing the WP02 instance.
WP02 is the second WebSphere
® Portal instance in the cell.
- Follow the instructions provided in the Performing required steps before installing Mobile Portal Accelerator.
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.
- 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:
- 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))
Portal are not installed on the same machine, specify the path to where the files are located on the WebSphere
- Change your working directory to: wp_profile_root/ConfigEngine
- Make sure that the correct values are specified for the following parameters in the file wp_profile_root/ConfigEngine/properties/wkplc.properties:
Application Server security is enabled, you must also specify values for the WasUserid
parameters in wp_profile_root/ConfigEngine/properties/wkplc.properties
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
All of this text, including parameters, is entered on the same command line.
- 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
- Install and configure the Mobile Portal Accelerator extensions using the following command for every instance on the secondary nodes:
- 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.
- Restart the portal server using the following commands:
[[Variable names used in the information center for user supplied informationmpa8|wp_profile_root]]/bin/stopServer.sh server_name -username WAS_admin -password WAS_admin_password_value
[[Variable names used in the information center for user supplied informationmpa8|wp_profile_root]]/bin/startServer.sh server_name
[[Variable names used in the information center for user supplied informationmpa8|wp_profile_root]]\bin\stopServer server_name -username WAS_admin -password WAS_admin_password_value
[[Variable names used in the information center for user supplied informationmpa8|wp_profile_root]]\bin\startServer server_name
is the name of the WebSphere
Application Server instance (for example, WebSphere_Portal
Parent topic: Installing Mobile Portal Accelerator on a WebSphere Portal node not managed by a deployment manager
Installing MCS for use with DB2
Installing MCS for use with Oracle
Performing required steps before installing Mobile Portal Accelerator
Installing Mobile Portal Accelerator extensions manually
Installing MCS for Microsoft SQL Server
WebSphere Portal product documentation
After Mobile Portal Accelerator is installed on WP02, continue with the procedure for WP02 documented in the WebSphere
Portal product documentation to configure WP02 data sources to point to the database being used by WP01. When you are done, continue to the next topic Configuring the cluster (creating new cluster)