IBM DB2 for i: 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.

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. Manual Step: Create the database user profile on IBM® DB2® for i.
    Condition
    None
    ConfigEngine task
    None
  4. Manual Step: Create the database runtime users and groups.
    Condition
    None
    ConfigEngine task
    None
  5. Create your databases.
    Condition
    None
    ConfigEngine task
    create-database
  6. Validate the database connection and environment.
    Condition
    None
    ConfigEngine task
    validate-database validate-database-environment
  7. Stop the portal server.
    Condition
    collation support
    ConfigEngine task
    stop-portal-server
  8. Transfer the database.
    Condition
    None
    ConfigEngine task
    database-transfer enable-profiles-check-managed package-profiles
  9. Grant privileges to the database runtime users.
    Condition
    None
    ConfigEngine task
    grant-runtime-db-user-privileges
  10. 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.