Planning for databases

This section provides information to give the database administrator an overall picture of WebSphere Portal database requirements.

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.

Planning for DB2 on Windows
When planning to transfer data to IBM DB2 Universal Database Enterprise Server Edition, you should consider the databases and user information, such as database names, what data is stored, and the database space needed. Some fix packs require steps prior to the transfer task to complete successfully.
Planning for DB2 on Linux
When planning to transfer data to IBM DB2 Universal Database Enterprise Server Edition, you should consider the databases and user information, such as database names, what data is stored, and the database space needed. Some fix packs require steps prior to the transfer task to complete successfully.
Planning for DB2 for i5/OS
When planning to transfer data to DB2 for i5/OS, you should consider the database names, what data is stored, and the database space needed.
Planning for DB2 for z/OS
When planning to transfer data to DB2 for z/OS, you should consider the databases and user information, such as database names, what data is stored, and the database space needed. Some fix packs require steps prior to the transfer task to complete successfully.
Planning for Oracle
When planning to transfer data to Oracle, you should consider the databases and user information, such as database names, what data is stored, and the database space needed.
Planning for Oracle RAC
When planning to transfer data to Oracle RAC, you should consider the databases and user information, such as database names, what data is stored, and the database space needed.
Planning for SQL Server 2005
When planning to transfer data to SQL Server 2005, you should consider the databases and user information, such as database names, what data is stored, and the database space needed.

Parent topic: Database considerations