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. Alternatively, you can specify the password on the command line using the following syntax:
- Windows:ConfigEngine.bat task_name -Dpassword_property_key=password_value
- UNIX: ./ConfigEngine.sh task_name -Dpassword_property_key=password_value
- i5/OS: 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
- Installing WebSphere Portal on AIX on the primary node
- Technotes for database connectivity issues
- Configure WebSphere Portal to use DB2
View information on installing and setting up DB2 to work with WebSphere Portal.
- Configure WebSphere Portal to use DB2 for z/OS
View information on installing and setting up DB2 for z/OS to work with WebSphere Portal.
- Configure WebSphere Portal to use Oracle
View information on installing and setting up Oracle to work with WebSphere Portal.
- Configure WebSphere Portal to use Oracle RAC
View information on installing and setting up Oracle RAC to work with WebSphere Portal.
- Configure WebSphere Portal to use SQL Server
View information on installing and setting up SQL Server to work with WebSphere Portal.
- Verify databases
After you configure WebSphere Portal to work with your database, test the database connection to ensure that it operates correctly. Then verify that all database transactions work properly within the WebSphere Portal environment.
For example, all portal pages should display without HTTP 404 errors, and there should be no database layer-related exceptions in the SystemOut.log and SystemErr.log files.
Parent topic:
Prepare the primary node on AIX
Previous topic:
Installing WebSphere Portal on AIX on the primary node
Next topic:
Configure the primary node to communicate with the deployment manager on AIX
Related information
Troubleshooting WebSphere Portal v6.1 databases