+

Search Tips   |   Advanced Search

DB2: Database transfer

The 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, configure portal to use a production-level database. We can use the Configuration Wizard to transfer the data and configure a new database server.

Before doing portal database transfer, increase DB transaction log size.


Configuration Wizard

The primary Configuration Wizard options are based on the 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 running the federated security option. For the cluster option, run the database transfer before creating the deployment manager profile.
DB2 worksheets...


Transfer data to a different database server

Depending on the 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 we click View Step Command, we can see the task and properties associated with each step in the wizard.

  1. Back up the properties files 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 the databases.

      Condition None
      ConfigEngine task create-database

  4. Manual Step: Download the script and run it on the database server to create the database.

      Condition Select to manually create the database.
      ConfigEngine task None

  5. Set up the database.

  6. Manual Step: Download the script and run it on the database server to set up the 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


    Parent Database Management Systems