As an alternative to the silent installation, you can install
the Mobile Portal Accelerator extensions by
following these steps.
Before you begin
- A supported version of WebSphere® Portal for
use with IBM® Mobile Portal Accelerator version 8.0 must
be installed on the system where you install MCS.
(For supported versions of WebSphere Portal,
see the topic Software requirements.)
Note: For instructions
about installing WebSphere Portal and
required fixes, see the topic Performing required steps before Mobile Portal Accelerator.
Also, see the WebSphere Portal product documentation for
detailed planning and installation information.
- Make sure that you have unpacked wp.mobile.zip and
created the install images as described in the Performing required
steps before Mobile Portal Accelerator topic.
- Multi-Channel Server (MCS)
must also be installed before installing the Mobile Portal Accelerator extensions.
Note: See
the Planning section of this information center for detailed
planning information for Mobile Portal Accelerator and MCS,
and the appropriate topic Installing Multi-Channel Server for
your environment for detailed installation instructions.
Procedure
- 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 SQLCLASSPATH=mssql_driver_path\sqljdbc4.jar:$CLASSPATH
export CLASSPATH
- 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:
- 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:
- Use one of the following options to install and configure
the Mobile Portal Accelerator extensions:
- 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.
- If you performed the mwp-config-all task
earlier in this procedure, 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.
- 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:
where server_name is the
name of the WebSphere Application Server instance
(for example, WebSphere_Portal).
Results
The
Mobile Portal Accelerator extensions
are installed and ready for use.