Set up a remote database
For high availability, using a remote database is preferred. For improved performance databases can be distributed across multiple database servers. Databases should also be configured for failover. Configuring the database for failover is beyond the scope of this documentation. Refer to the database product documentation for the most authoritative guidance about setting up databases for fail over.
Password considerations when transferring data manually
For security reasons, you should not store passwords in the wkplc.properties and wkplc_comp.properties. Edit each of the properties files prior to running a configuration task, inserting the passwords needed for that task. After the task has run, delete all passwords from each file. For more information, see Deleting passwords from configuration scripts.
To specify the password on the command line....
./ConfigEngine.sh task_name -Dpassword_property_key=password_value
As with other properties, each password property must have the -D prefix and be set equal to (=) a value. If you have multiple properties in a single command, use a space character between each -Dproperty=value setting.
Prerequisites
- Install WebSphere Portal on Windows on the primary node
- Technotes for database connectivity issues
See
- Configure portal to use DB2
- Configure portal to use DB2 for z/OS
- Configure portal to use Oracle
- Configure portal to use Oracle RAC
- Configure portal to use SQL Server
- Verify databases
Parent topic:
Prepare the primary node on Windows
Previous topic:
Install WebSphere Portal on Windows on the primary node
Next topic:
Configure the primary node to communicate with the deployment manager on Windows
Related information
Troubleshoote WebSphere Portal V6.1 databases