Set up a database

Before transferring default data to the production database server, prepare the database server. Database preparation includes creating user IDs and databases. For this installation path, stand-alone production server, remote databases servers are used. Select the database server that are using.

• Configure a local database

  The database can be installed on the same server as WebSphere Portal. Having the database on the same server has advantages and disadvantages. This is a common scenario for a proof-of-concept installation where you want to test out the capabilities and features. Another scenario that may use this configuration is a stand-alone server installation. Installing the database on another server has the advantage of distributing the processing and workload.

• Set up a remote DB2 database

  You can install DB2 on the same server as WebSphere Portal, also referred to as local, or on a different server, referred to as remote. If you plan to use a local DB2 database, scripts are provided to simplify the database creation and transfer. More information about the local database is provide in the single server installation instructions. For a remote database complete the transfer manually.

• Set up a remote Oracle database on Windows for a stand-alone production server

  Setting up the Oracle database includes creating user IDs and databases on a remote server. A task is provided to assist with creating the users. Before you can use the task, modify properties files.

• Set up a remote Oracle RAC database on Windows for a stand alone production server

  Setting up the Oracle RAC database includes creating user IDs and databases on a remote server. A task is provided to assist with creating the users. Before you can use the task, modify properties files.

• Set up a remote SQL Server database on Windows for a stand-alone production server

  To setup a remote Microsoft SQL Server Enterprise Edition database, create user IDs and databases on a remote server. Tasks are provided to assist with creating the user IDs and the databases. Before you can use the tasks, modify properties files.

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

Set up a stand-alone server on Windows

Previous topic:

Installing WebSphere Portal on Windows

Next topic:

Prepare a remote Web server when portal is installed on Windows

---