Steps to update Portal database connection information after completing database-transfer

You may need to update the connection information some time after you configure WebSphere Portal to use an external database (such as DB2, Oracle or SQLServer)   This document desacribes the procedure to take to update the database configuration information for various scenarios.

The connect database configuration script

WebSphere Portal provides a WPSconfig/ConfigEngine script to automatically make these changes for you.  This script is the 'connect-database' task.  

connect-database
 
 
This script does all of the following:

• Drop the existing datasources and JDBC provider in the WAS configuration
• Creates a new JDBC provider and datasources in the WAS configuration using your updated information
• Creates new environment variables if needed for database drivers
• Updates several portal applications (such as wps.ear, wcm.ear and icmjcr.ear) to use the new datasources

Steps to update Portal with the new hostname or port of the databases

Portal v6.0.x
 
1. In the PortalServer/config directory, edit the wpconfig_dbdomain.properties file
2. Change the following values as needed to reflect the new hostname and/or port for the database server:

3. Save the file
4. Cluster only.  Ensure the DMGR is started.
5. From the PortalServer/config directory, execute the following WPSconfig scripts to validate the properties:

6. Execute the following WPSconfig script to update the Portal datasources:

7. Restart the WebSphere_Portal server.


Portal v6.1.x

1. In the wp_profile/ConfigEngine/properties directory, edit the wkplc_comp.properties file
2. Change the following values as needed to reflect the new hostname and/or port for the database server:

3. Save the file
4. Cluster only.  Ensure the DMGR is started.
5. From the wp_profile/ConfigEngine directory, execute the following ConfigEngine scripts to validate the properties:
6. Execute the following ConfigEngine script to update the Portal datasources:
7. Restart the WebSphere_Portal server.

Steps to update Portal with the new names of the databases

Portal v6.0.x
 
1. In the PortalServer/config directory, edit the wpconfig_dbdomain.properties file
2. Change the following values as needed to reflect the new hostname and/or port for the database server:

3. Save the file
4. Cluster only.  Ensure the DMGR is started.
5. From the PortalServer/config directory, execute the following WPSconfig scripts to validate the properties:

Windows:   WPSconfig.bat validate-database-connection-wps
           WPSconfig.bat validate-database-connection-jcr
           WPSconfig.bat validate-database-connection-likeminds
           WPSconfig.bat validate-database-connection-wmm

UNIX:     ./WPSconfig.sh validate-database-connection-wps
          ./WPSconfig.sh validate-database-connection-jcr
          ./WPSconfig.sh validate-database-connection-likeminds
          ./WPSconfig.sh validate-database-connection-wmm

6. Execute the following WPSconfig script to update the Portal datasources:

Windows:  WPSconfig.bat connect-database -DWasPassword=password
UNIX:   ./WPSconfig.sh connect-database -DWasPassword=password

7. Restart the WebSphere_Portal server.

Portal v6.1.x

1. In the wp_profile/ConfigEngine/properties directory, edit the wkplc_comp.properties file
2. Change the following values as needed to reflect the new hostname and/or port for the database server:

3. Save the file
4. Cluster only.  Ensure the DMGR is started.
5. From the wp_profile/ConfigEngine directory, execute the following ConfigEngine scripts to validate the properties:

Windows:  ConfigEngine.bat validate-database-connection
    
UNIX:   ./ConfigEngine.sh validate-database-connection

6. Execute the following ConfigEngine script to update the Portal datasources:

Windows:  ConfigEngine.bat connect-database -DWasPassword=password
UNIX:    ./ConfigEngine.sh connect-database -DWasPassword=password

7. Restart the WebSphere_Portal server.

Steps to Update Database User IDs and Passwords in the Portal and WebSphere Configuration

Portal v6.0.x

1. In the PortalServer/config directory, edit the wpconfig_dbdomain.properties file
2. Change the following values as needed to reflect the new user ID and/or password for the database server:

3. Save the file
4. Cluster only.  Ensure the DMGR is started.
5. From the PortalServer/config directory, execute the following WPSconfig scripts to validate the properties:

6. Execute the following WPSconfig script to update the Portal datasources:
7. Restart the WebSphere_Portal server.

Portal v6.1.x

1. In the wp_profile/ConfigEngine/properties directory, edit the wkplc_comp.properties file
2. Change the following values as needed to reflect the new user ID and/or password for the database server:

3. Save the file
4. Cluster only.  Ensure the DMGR is started.
5. From the wp_profile/ConfigEngine directory, execute the following ConfigEngine scripts to validate the properties:
6. Execute the following ConfigEngine script to update the datasources:

7. Restart the WebSphere_Portal server.

Steps to point Portal to a backup database

Portal v6.0.x

1. In the PortalServer/config directory, edit the wpconfig_dbdomain.properties file
2. Change the following values as needed to reflect the values for the backup database server:

3. Save the file
4. Cluster only.  Ensure the DMGR is started.
5. From the PortalServer/config directory, execute the following WPSconfig scripts to validate the properties:
6. Execute the following WPSconfig script to update the Portal datasources:

7. Restart the WebSphere_Portal server.


Portal v6.1.x

1. In the wp_profile/ConfigEngine/properties directory, edit the wkplc_comp.properties file
2. Change the following values as needed to reflect the values for the backup database server:

NOTE:  domain in this case refers to release, community, customization, jcr, likeminds, and wmm.  Update the following properties for all domains that apply to your situation.

3. Save the file
4. Cluster only.  Ensure the DMGR is started.
5. From the wp_profile/ConfigEngine directory, execute the following ConfigEngine scripts to validate the properties:
6. Execute the following ConfigEngine script to update the datasources:

7. Restart the WebSphere_Portal server.

Limitations

 
1. To only update the datasource information for specific domains, you can add the following flags to the 'connect-database' script:2. 'connect-database' does not validate any of the properties you have entered into wpconfig_dbdomain.properties or wkplc_comp.properties.  It is very important that you run the validation scripts prior to running connect-database.
3. 'connect-database' drops the Portal JDBC provider.  If you have created any custom datasources in this JDBC provider, they will be lost.  It is recommended that you create custom datasources in their own JDBC provider.
4. If you customized any of the Portal datasources, these changes will be lost.  You will need to redo any customizations you may have made to the Portal datasources.