Configure WebSphere Portal to use 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, wkplc_comp.properties, and wkplc_dbtype.properties files. 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:
- ConfigEngine.bat task_name -Dpassword_property_key=password_value
- ./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 Express on Windows
- Configure WebSphere Portal Express to use DB2
This section provides information on how to manually transfer data to the DB2 database you have installed and set up. Follow these steps to transfer WebSphere Portal Express, and DB2 Content Manager databases to DB2.
- Configure WebSphere Portal Express to use Oracle
This section provides information on how to manually transfer data to the Oracle database you have installed and set up. Follow these steps to transfer WebSphere Portal Express, Member Manager, and DB2 Content Manager databases to Oracle.
- Configure WebSphere Portal Express to use Oracle RAC
This section provides information on how to manually transfer data to the Oracle RAC database you have installed and set up. Follow these steps to transfer WebSphere Portal Express, Member Manager, and DB2 Content Manager databases to Oracle.
- Configure WebSphere Portal Express to use SQL Server 2005
This section provides information on how to manually transfer data to the SQL Server 2005 database you have installed and set up. Follow these steps to transfer WebSphere Portal Express, and DB2 Content Manager databases to SQL Server 2005.
- Verifying database connections
After WebSphere Portal Express is configured to work with your database, test the database connection to ensure that it operates correctly.
Parent topic: Preparing the primary node on Windows
Previous topic: Installing WebSphere Portal Express on Windows
Next topic: Configuring WebSphere Portal Express to use a user registry on Windows
|
|
|
Portal, Express Beta Version 6.1