Installing the Mobile Portal Accelerator extensions silently

You can install the Mobile Portal Accelerator extensions silently, using a response file. This silent installation applies only in a stand-alone configuration.

1. Start the database server and the database listener, if they are not already running.
2. Run the following command to ensure that the WebSphere environment is set up correctly:
   

   . wp_profile_root/bin/setupCmdLine.sh

   Note: There is a space between the period (.) and the rest of the command.
   

   wp_profile_root\bin\setupCmdLine

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. Check the file wp_profile_root/ConfigEngine/properties/wkplc.properties to ensure that the correct values are specified.
5. Change your working directory to wp_root/PortalServer/wp.mobile/wp.mobile.mwp/setup.
6. Open InstallResponse.properties in a text editor and supply values for the following properties.

   licenseAccepted

   Must be true.

   MWPInstallType

   Specify which features to install:

   full

   Install and configure all of the Mobile Portal Accelerator extensions

   base

   Install and configure all of the Mobile Portal Accelerator extensions except the sample XDIME portlets and sample XDIME pages

   empty

   Use when an empty portal was installed ( -W installPortletsSequence.active="false" was set on the install command for WebSphere Portal)

   McsRepositoryType

   The interface for accessing the MCS database, for example odbc

   McsDbVendor

   The database vendor for MCS:

   • db2-type4 for DB2 version 9.1 (with fix pack 5) and DB2 version 9.7
   • DB2 for DB2 version 9.5 (with fix pack 3)
   • oracle for Oracle Database
   • MS SQL: mssql-jsql for Microsoft SQL Server 2005 Enterprise Edition SP2 or SQL Server 2008, with the NetDirect driver
   • MS SQL: mssql-2005 for Microsoft SQL Server 2005 Enterprise Edition SP2 or SQL Server 2008, with the Microsoft driver

   McsDbHost

   The fully qualified host name of the MCS database server

   McsDbPort

   The port number used for the MCS database on the database server, typically one of the following:

   • 50000
   • 1521
   • MS SQL: 1433

   McsDbSource

   The MCS database user name

   McsDbPassword

   The MCS database user password

   McsProject

   The MCS project name

   JDBCDriverPath

   The path to the JDBC driver, for example:

   • db_root/db2instance/sqllib/java/db2jcc4.jar:db_root/db2instance/sqllib/java/db2jcc_licen se_cu.jar

   dependency.useValidation

   Whether to enable prerequisite checking and input validation during the installation:

   true

   Perform the checks. This is the default value, and it is recommended.

   false

   Do not perform the checks.

   dependency.rulesDirectory

   The directory where custom rules files are located, if you are using custom dependency and validation rules (ignored when dependency.useValidation=false)

7. Save your changes.
8. Change your working directory to wp_root/PortalServer/wp.mobile/wp.mobile.mwp/setup/install.
9. Run the following commands to launch the installation script:
   • # export USER_INSTALL_ROOT
   • # install.sh wp_root/PortalServer/wp.mobile/wp.mobile.mwp/setup/install/installresponse.properties
   • install.bat wp_root\PortalServer\wp.mobile\wp.mobile.mwp\setup\install\installresponse.properties
10. 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).