Sun Java System Portal Server 7.1 Configuration Guide

ProcedureTo Prepare the Database

  1. Prepare the Database.

    1. Install RDBMS or identify the RDBMS that already exists on the system.

    2. Create a database instance (tablespace in case of Oracle) to be used for collaboration.

    3. Create the database user account or accounts.

  2. Establish appropriate privileges for the user accounts.

    1. Locate the JDBC driver.

    2. Add JDBC driver to the web container's JVM classpath.

    3. Add JVM option:


      -Djdbc.drivers=<JDBC_DRIVER_CLASS>
  3. Configure Community Membership and Configuration.

    1. Configure communitymc database configuration file by running the following scripts:


      portal-data-dir/portals/portal-id/config/portal.dbadmin
    2. Remove the Java DB specific property in the communitymc.properties file.


      portal-data-dir/portals/portal-id/config/communitymc.properties
  4. Load the schema onto the database.

  5. Edit the jdbc/communitymc JDBC resource to point to the new database.


    Note –

    On some of the web containers, you might need to edit the corresponding JDBC connection pool instead of the JDBC resource.


  6. Configure and install portlet applications.

    1. Locate the portlet applications.


      portal-data-dir/portals/portal-id/portletapps
    2. Configure portlet applications to use the new database by editing tokens_xxx.properties.

    3. Using the administration console or command-line tool provided by the web container, create a JDBC resource for the application using the values from the tokens_xxx.properties.

      Resource JNDI Name

      jdbc/DB_JNDI_NAME

      Resource Type

      javax.sql.DataSource

      Datasource Classname

      DB_DATASOURCEA

      User

      DB_USERU

      Password

      DB_PASSWORDS

      URL

      DB_URL


      Note –

      Some of the web containers might require you to set up a connection pool prior to setting up the JDBC resource.


    4. Undeploy existing portlets that use the Java DB Database as a datastore.

    5. Deploy the newly configured portlet applications.