Configure WebSphere Portal to use SQL Server 2005

View information on manually transferring data to the SQL Server 2005 database you have installed and set up. Follow these steps to transfer WebSphere Portal, and Java Content Repository databases to SQL Server 2005. As an alternative to the manual database transfer procedure described here, you can use the configuration wizard to complete the database transfer task.

Before you begin:

Ensure that the following prerequisites are met:


Prerequisites

Installing SQL Server

Modifying database properties

Set up databases
Tips:

Steps for transferring data to another supported database

  1. Open a command prompt and change to the directory profile_root/ConfigEngine.

  2. Enter the following commands to validate configuration properties.

    ConfigEngine.bat validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DWasPassword=password
    

    ConfigEngine.bat validate-database-connection -DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DWasPassword=password
    

  3. From the same command prompt as the previous steps, change to the directory profile_root\bin.

  4. Stop both WAS and the WebSphere Portal server:

    Option Description
    WAS stopServer.bat server1-username admin_userid -password admin_password
    WebSphere Portal stopServer.bat WebSphere_Portal-username admin_userid -password admin_password

  5. Transfer the database:

    1. cd profile_root/ConfigEngine.

    2. Enter the following command:

      ConfigEngine.bat database-transfer -DTransferDomainList=release,customization,community,jcr, feedback,likeminds 
      

    3. After running this task, a message is added to the log files to verify that this task was successful. Check the log files. If the configuration fails, verify the values in the wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties files and then repeat this step.

  6. Change to the directory profile_root\bin.

  7. Enter the following command to start the WebSphere Portal server: startServer.bat WebSphere_Portal

  8. Update the SQL Server 2005 statistics for Portal, and JCR databases by opening SQL Server Management Studio, selecting New Query, and running the following query: use db_name exec sp_updatestats @resample='resample';

If you have performed database transfer in a clustered environment, explicitly copy the profile_root\PortalServer\jcr\lib\com\ibm\icm\icm.properties file from the primary node on which the database-transfer task was processed to all secondary nodes. This ensures that the secondary nodes have the new JCR database values specified in the icm.properties file.

  1. Stop the portal server on the secondary node.

  2. Copy the profile_root\PortalServer\jcr\lib\com\ibm\icm\icm.properties file from the primary node and replace the icm.properties file on the secondary node with the new file from the primary node.

  3. Start the portal server on the secondary node.


Parent topic:

Configure WebSphere Portal to use SQL Server


Previous topic:

Assigning custom table spaces