Installing MCS for Oracle users

The second stage in the process of installing the Multi-Channel Server (MCS) software on WebSphere® Portal for use with Oracle is to install the MCS software.

1. Make sure that the database server and the database listener are running.

   If you are using a remote Oracle database, you must copy the JAR file that provides support for the JDK (for example, ojdbc6.jar) from the remote Oracle server to the WebSphere Portal server. The typical location of this file is the db_root/jdbc/lib directory.

   Note: Later in this installation, you add the JAR file to theCLASSPATH environment variable and to the JDBC_DRIVER parameter in the ImportPolicies.sh shell script. Specify the location of the file that you copied onto the WebSphere Portal server.
2. Log in to the WebSphere Portal server as the user who installed WebSphere Portal.
3. Add the JDBC driver to the Java™ Virtual Machine (JVM) classpath of the WebSphere Portal server as follows.
   1. Log in to the WebSphere Application Server Integrated Solutions Console.
   2. Click Servers > WebSphere application servers.
   3. Click the WebSphere_Portal server link.
   4. In Server Infrastructure, click Java & Process Management > Process Definition.
   5. Click the Java Virtual Machine link.
   6. In the Classpath field, add entries for your JDBC driver.
      An example entry follows.

      db_root/jdbc/lib/ojdbc6.jar

      where db_root is the value you assigned to the ORACLE_HOME environment variable when you configured the database for MCS.
   7. Click Apply.
   8. Save the configuration changes.
4. 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

5. Add the JDBC driver to your current CLASSPATH environment variable, as illustrated in the following examples:

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

6. 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
7. Change your working directory to:wp_profile_root/ConfigEngine
8. Run the following command.
   

   ./ConfigEngine.sh init mcs-deploy-mcs -DMcsRepositoryType=odbc -DMcsDbVendor=oracle -DMcsDbHost=hostname -DMcsDbPort=port -DMcsDbSource=SID -DMcsDbUser=mcs_dbuser -DMcsDbPassword=mcs_user_password -DMcsProject=mobile-portal

   

   ConfigEngine init mcs-deploy-mcs -DMcsRepositoryType=odbc -DMcsDbVendor=oracle -DMcsDbHost=hostname -DMcsDbPort=port -DMcsDbSource=SID -DMcsDbUser=mcs_dbuser -DMcsDbPassword=mcs_user_password -DMcsProject=mobile-portal

   Note: The previous code phrase is one command; enter the entire command on the same command line.
   You must specify mobile-portal as the project name. Definitions for the variable parameters follow.

   • hostname, the fully qualified host name of the database server.
   • port, the port number used for the MCS database on the database server. By default, the port is 1521. The port is defined when Oracle is installed.
   • SID, the Oracle SID used for the MCS database
   • mcs_dbuser, the MCS database user name
   • mcs_user_password, the MCS database user password
9. Edit the repository batch files.
   1. Go to wp_root/wp.mobile/wp.mobile/wp.mobile.mcs/repository/bin
   2. After installation of MCS, modify the drManager tool with the appropriate database-related information.
   3. Add the JBDC class path to thedrManager batch file or shell script.
   4. Add the JDBC driver class path to the ImportPolicies script to add JDBC driver class path

      For example:

      For ImportPolicies.bat, use:

      For ImportPolicies.sh, use:

      JDBC_DRIVER=

      For drManager.bat use:

      For drManager.sh use:

      jdbc-driver-path

      Use the following example in the Solaris or Oracle environment:

      java ${JAVA_OPTS} -cp ${CLASS_PATH}:${CLASSPATH} ${DEBUG_ARGS} com.volantis.devices.repository.manager.cli.DeviceRepositoryManager ${DEFAULT_ARGS} ${1+"$@"} --jdbc-driver-path /opt/IBM/oraclejar/ojdbc6.jar --jdbc-project mobile-portal --jdbc-vendor oracle--jdbc-host 9.126.143.110 --jdbc-port 1521 --jdbc-source orcl--jdbc-user mcs--jdbc-password

   5. Add the JDBC driver class path to the mcsImport script.
      For example:

      JDBC_DRIVER=/opt/IBM/oraclejar/ojdbc.jar

10. To import default device policies, run the following command:
    

    ./ConfigEngine.sh init mcs-import-devices -DMcsProject=mobile-portal

    

    ConfigEngine init mcs-import-devices -DMcsProject=mobile-portal

    Note: You must specify mobile-portal as the project name.

    The results of the import operation are displayed by the task and also written to the wp_profile_root/ConfigEngine/log/ConfigTrace.log file. Verify that the import was successful before continuing.