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, configure portal to use a production-level database. 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.
For the Do to transfer to one database or multiple databases or schemas option, select Single database to configure one database with a single database user and a single data source. Select Multiple databases or schemas to configure multiple databases with different data sources and different users per schema. We can also use the multiple database option to configure a single database with different data sources and different users.
Validation
Prevent a possible database transfer failure by validating the 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 running the configuration.
Syntax validation checks that you:
- Enter a valid port number in the range of 1 - 65535.
- Use the correct format for the host name.
- Enter a valid context root value
The database connection validation checks that a connection can be made to the database server. The wizard can connect to the database server to validate the host name and port number values that you enter.
On the Database Settings panel, we 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 the parameters are correct and the database server is unavailable at the time of creating the instructions.
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 you click View Step Command, we can see the task and properties associated with each step in the wizard.
- Back up the properties files that the wizard uses during the configuration.
Condition None ConfigEngine task backup-property-files-for-dbxfer
- Manual Step: Create the database users and groups.
Condition None ConfigEngine task None
- Manual Step: Create the database user profile on IBM DB2 for i.
Condition None ConfigEngine task None
- Manual Step: Create the database runtime users and groups.
Condition None ConfigEngine task None
- Manual Step: Create the database configuration users on DB2 for z/OS .
Condition None ConfigEngine task None
- Manual Step: Download the script and view instructions to delete existing databases.
Condition None ConfigEngine task None
- Create the databases.
Condition None ConfigEngine task create-database
- Manual Step: Download the script and run it on the database server to create the database.
Condition Select to manually create your database. ConfigEngine task None
- Manual Step: Download the script and run it on the database server to create the database.
Condition Select to manually create your database. ConfigEngine task None
- Manual Step: Create the Oracle database.
Condition None ConfigEngine task None
- Manual Step: Download the script and view instructions to create the databases.
Condition None ConfigEngine task None
- Manual Step: Create the data directory, data, and the index directory, index, on the database server.
Condition Select to manually create users and assign them permissions. ConfigEngine task None
- Set up the database.
(Automatic Storage Management Users only): If we have configured your database with Automatic Storage Management, perform additional manual instructions after you perform this step. Run the setup database script to create database schemas and users and grant privileges to database users . Then, go to Oracle: Create JCR table spaces (Automatic Storage Management) to perform additional manual instructions.
Condition None ConfigEngine task setup-database
- 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
- Manual Step: Download the script and run it on the database server to set up the database.
(Automatic Storage Management Users only): If we have configured your database with Automatic Storage Management, we must edit the script that you download for your environment before running it on the database server.
Condition Select to manually create users and assign them permissions. ConfigEngine task None
- Manual Step: Download the script and run it on the database server to set up the database.
Condition Select to manually create users and assign them permissions. ConfigEngine task None
- Manual Step: Set up JCR collation for correct language locale order.
Condition Select to have advanced database collation support. ConfigEngine task None
- Manual Step: Restart the DB2 server.
Condition None ConfigEngine task None
- Validate the database connection and environment.
Condition None ConfigEngine task validate-database validate-database-environment
- Stop the portal server.
Condition collation support ConfigEngine task stop-portal-server
- Transfer the database.
Condition None ConfigEngine task database-transfer enable-profiles-check-managed package-profiles
- Grant privileges to the database runtime users.
Condition None ConfigEngine task grant-runtime-db-user-privileges
- 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
- Manual Step: Download the script and run it to grant the database runtime user the appropriate privileges to work with database tables.
Condition Select to manually create users and assign them permissions. ConfigEngine task None
- Manual Step: Download the script and run it on the database server to grant privileges to database runtime users.
Condition Select to manually create users and assign them permissions. ConfigEngine task None
- Connect to the databases.
Condition None ConfigEngine task None
- Manual Step: Download the script and view instructions to reset the check pending status on portal table spaces.
Condition None ConfigEngine task None
- Reset the web content manager event log.
Condition None ConfigEngine task None
- Configure the JCR domain to support large files.
Condition None ConfigEngine task datasource-enable-fully-materialize-lob-data
- Manual Step: Improve database response time for the database containing the JCR domain.
Condition None ConfigEngine task None
- Start the portal server.
Condition None ConfigEngine task start-portal-server
What to do next
You transferred the data from Apache Derby to the preferred database.
One quick way to test the database configuration is to log in and explore the site to validate the site is working as you expected.
Go to...
http://host:port/context_root/default_portal_home
For example, go to...
http://host:10039/wps/portal
Next, we can use other options to configure our environment more.
If we are setting up a stand-alone server environment, we can use the Enable Federated Security option to add an LDAP user registry.
If we are setting up a cluster environment, we can use the Create a dmgr option to create a deployment manager profile that is augmented with WebSphere Portal resources.
Related tasks:
Access the Configuration Wizard
Update DB2 self-tuning memory manager (STMM) settings