DB2: Database transfer

Your portal is installed with an Apache Derby database. The database that is immediately available for use is good for demonstration and portlet and theme development environments. Otherwise, you must configure portal to use a production-level database. Use the Configuration Wizard to transfer the data and configure a new database server.

Configuration Wizard

The primary Configuration Wizard options are based on your target configuration topology, such as a stand-alone server or a cluster. The database transfer option is included with both Set Up a Stand-alone Server and Set Up a Cluster. For the stand-alone server topology, run the database transfer option before you run the federated security option. For the cluster option, run the database transfer before you create your deployment manager profile.

Validation

Prevent a possible database transfer failure by validating your entries in the wizard. When you chose to validate settings for the Database Transfer option, field syntax and database connection validations are performed to prevent a possible failure before you run the configuration.

Syntax validation checks that you:

  • Enter a valid port number in the range of 1 - 65535.
  • Use the correct format for your host name.

The database connection validation checks that a connection can be made to your database server. The wizard can connect to your database server to validate the host name and port number values that you enter.

On the Database Settings panel, you can choose to turn validation on or off by selecting Yes or No to the Connect to database server to validate settings option. Select No, if you know that your parameters are correct and your database server is unavailable at the time of creating your instructions.

Transferring data to a different database server

Depending on your environment, the wizard generates a configuration process. The following steps reflect all possible steps in the configuration process. The steps do not represent a literal configuration. The steps are provided as a reference.

If you click View Step Command, you can see the task and properties associated with each step in the wizard.

  1. Back up the properties files that the wizard uses during the configuration.
    Condition
    None
    ConfigEngine task
    backup-property-files-for-dbxfer
  2. Manual Step: Create the database users and groups.
    Condition
    None
    ConfigEngine task
    None
  3. Create your databases.
    Condition
    None
    ConfigEngine task
    create-database
  4. Manual Step: Download the script and run it on the database server to create your database.
    Condition
    Select to manually create your database.
    ConfigEngine task
    None
  5. Set up your database.
    Condition
    None
    ConfigEngine task
    setup-database
  6. Manual Step: Download the script and run it on the database server to set up your database.
    Condition
    Select to manually assign users permissions.
    ConfigEngine task
    None
  7. Manual Step: Set up JCR collation for correct language locale order.
    Condition
    Select to have advanced database collation support.
    ConfigEngine task
    None
  8. Manual Step: Restart the DB2® server.
    Condition
    None
    ConfigEngine task
    None
  9. Validate the database connection and environment.
    Condition
    None
    ConfigEngine task
    validate-database validate-database-environment
  10. Stop the portal server.
    Condition
    collation support
    ConfigEngine task
    stop-portal-server
  11. Transfer the database.
    Condition
    None
    ConfigEngine task
    database-transfer enable-profiles-check-managed package-profiles
  12. Grant privileges to the database runtime users.
    Condition
    None
    ConfigEngine task
    grant-runtime-db-user-privileges
  13. Manual Step: Download the script and run it on the database server to grant privileges to the runtime user.
    Condition
    Select to manually create users and assign them permissions.
    ConfigEngine task
    None
  14. Configure the JCR domain to support large files.
    Condition
    None
    ConfigEngine task
    datasource-enable-fully-materialize-lob-data
  15. Start the portal server.
    Condition
    None
    ConfigEngine task
    start-portal-server

What to do next

You transferred your data from Apache Derby to your preferred database.

One quick way to test your database configuration is to log in and explore the site to validate the site is working as you expected.

Go to http://host_name:port/context_root/default_portal_home. For example, go to http://host_name:10039/wps/portal.

Next, you can use other options to configure your environment more.

If you are setting up a stand-alone server environment, you can use the Enable Federated Security option to add an LDAP user registry.

If you are setting up a cluster environment, you can use the Create a Deployment Manager option to create a deployment manager profile that is augmented with WebSphere® Portal resources.