SQL Server: 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.
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.
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 we 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.
See
- SQL Server: SQL Server worksheet: Transfer to a single database
- SQL Server: SQL Server worksheet: Transfer to multiple databases
Parent topic: Database Management Systems
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
- 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
- Set up the database.
- 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 create users and assign them permissions.
- 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 database runtime users.
- Condition
- Select to manually create users and assign them permissions.
- 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.