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 and 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:

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.


Installing WebSphere Portal on Solaris on the primary node

Technotes for database connectivity issues

Parent topic:

Prepare the primary node on Solaris

Previous topic:

Installing WebSphere Portal on Solaris on the primary node

Next topic:

Configure the primary node to communicate with the deployment manager on Solaris

Related information

Troubleshooting WebSphere Portal v6.1 databases