IBM i clustered server: 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.
Refer to the following password considerations when transferring data manually:
For security reasons, you should not store passwords in the wkplc.properties and wkplc_dbdomain.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.
You can specify the password on the command line using the following syntax:
Windows™:ConfigEngine.bat task_name -Dpassword_property_key=foo_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.UNIX™: ./ConfigEngine.sh task_name -Dpassword_property_key=foo_value
i: ConfigEngine.sh task_name -Dpassword_property_key=foo_value
Prerequisites
Install WebSphere PortalInstall the database drivers under the WP_PROFILE directory so the drivers will automatically be copied to the additional cluster node profiles.
Parent
Prepare the primary node on IBM i
Previous
Install WebSphere Portal
Next topic
Create the WebSphere Portal profile template on IBM i in a clustered environment