Configuring and using the Oracle JDBC driver

After you have fully installed IBM® Mobile Portal Accelerator and performed any migration tasks, you can configure WebSphere® Portal and Multi-Channel Server (MCS) to use the appropriate Oracle JDBC driver so that it can communicate with your Oracle database. (Refer to the topic Software requirements for a list of supported versions.)

1. Download the Oracle JDBC driver from the Oracle JDBC Drivers Downloads web page.
   • The JDBC driver for Oracle Release 11.2.0.2 is ojdbc6.jar.
2. Place the JAR file in a directory on your WebSphere Portal server.
   Note: If you are configuring within a cluster, place the JAR file on every node in the cluster. Add the JAR file to the CLASSPATH on each node.
3. Add the Oracle JDBC driver to the Java™ Virtual Machine (JVM) classpath of the WebSphere Portal server and remove the previous Oracle driver from the JVM classpath. Update the JVM classpath as follows:
   1. Log in to the WebSphere Application Server Integrated Solutions Console.
   2. Click Servers > Application Servers.
   3. Click the name of your WebSphere Portal server.
   4. Under Server Infrastructure, click Java and Process Management, and then click the Process Definition link.
   5. Under Additional Properties, click the Java Virtual Machine link.
   6. In the Classpath field, delete the entry for your previous Oracle JDBC driver and add an entry for the new Oracle JDBC driver using the following command:

      oracle_driver_path/oracle_JDBC_driver_name

      where:

      • oracle_driver_path is the directory path for the Oracle JDBC driver on the WebSphere Portal server
      • oracle_JDBC_driver_name is the JDBC driver filename
   7. Click Apply.
   8. Save the configuration changes.
4. Edit wp_root/wp.mobile/wp.mobile.mcs/repository/bin/ImportPolicies.sh as follows:
   1. Add the path to the Oracle JDBC driver to the end of the CLASSPATH= line.

      :oracle_driver_path/oracle_JDBC_driver_name

   2. Remove the path to the previous Oracle JDBC driver file.
5. If you have a profile or script that sets the JDBC_DRIVER environment variable, modify it to specify the path to the new Oracle JDBC driver in place of the previous Oracle JDBC driver.
6. 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).