Sun Java System Portal Server 7.1 Deployment Planning Guide

ProcedureTo Point All Portal Server Instances To The Common Derby Network Server Instance

Portal clients of the Derby network server instance access it through a JDBC data source that is configured in the web container. Configuring a Portal instance to use a non-default Derby network server instance means reconfiguring these data sources to point to a different host. The method depends on the brand of web container. This procedure uses Sun Java Webserver 7.0 as an example.

Perform the following procedure for each Portal Server instance that you want to use a common Derby network server instance.

  1. Access the Sun Java System Web Server.

    For example, http://sesta.iplanet.com:8800

  2. Under the Common Tasks Tab, click Edit Java Settings under Configuration Tasks.

  3. Click the Resources tab.

    A list of the JDBC resources in the web container is displayed.

    This figure depicts the Resources tab in the Sun Java
System Web Server console.
  4. Perform the following steps for each of the following resources:

    • jdbc/communitymc

    • jdbc/FileSharingDB

    • jdbc/SurveyDB

    • jdbc/WikiDB

    1. Click the resource.

      A new window opens.

    2. Click the Properties link at the top of the window to scroll to the resource properties.

      This figure shows a screen shot of the Properties page.
    3. Change the serverName property to the host name of the common Derby server instance.

    4. Click Ok.

  5. Deploy the configuration by performing the following steps:

    1. Select the Configurations Tab.

    2. Identify the configuration by selecting the configuration checkbox.

    3. Select Deploy Configuration from the configuration action list.

  6. Restart the Web Container.