Manually migrate HCL
Connections™
5.0 or 5.5 databases to version 6.0 in an existing IBM®
WebSphere® Application Server and Microsoft™ SQL Server database environment.
Before you begin
Before you apply updates, back up your
databases. For more information, see Backing up IBM® Connections.
Ensure that you install and configure all
supporting software for version 6.0 CR1.
Ensure that the
name of the Home page database instance is not null. If it is null, rename it to HOMEPAGE.
Ensure
that Named Pipes is enabled in the SQL Server Network Configuration for all instances. For more
information, refer to your SQL Server documentation.
About this task
Update IBM® Connections version 5.0 or 5.5 databases to version 6.0 CR1 manually. Use this procedure
if you want an alternative to using the database wizard to update your databases.
Notes:
- Use the Java™
Runtime Environment (JRE) under the Wizards directory in the installation
media. Update your PATH variable to point to this JRE, by using the instructions for your operating
system. For example, the relative path to the JRE on Microsoft™
Windows™ might be Wizards\jvm\win\jre.
For AIX® or Linux™, the
relative path might be Wizards/jvm/aix/jre and
Wizards/jvm/linux/jre.
- IBM® Connections
does not support GNU Java™.
- You need to use a database administrator ID to
run the Java™ migration utilities that are described in this
task.
- After you run each command, examine the output of the command for error messages. If you find
errors, resolve them before you continue with the update process.
- To improve readability, some commands and file paths in are displayed on separate lines. Ignore
these formatting conventions when you enter the commands.
To update databases manually, complete the
following steps:
Procedure
-
Log in to the WebSphere® Application Server
Integrated Solutions Console on your Deployment Manager.
-
Go to .
-
Stop all IBM® Connections applications.
-
Log in as the database administrator and change to the directory that contains the scripts.
The relative path is shown in the step for each application.
-
For each application, run the appropriate scripts by entering the commands that are shown in
the following list. In these commands, dbPassword is the password for the SQL
Server user named sa. If your database server has multiple SQL Server
instances that are installed, add the following text as the first parameter to each command:
-S
sqlserver_server_name\sqlserver_server_instance_name
Where:
- sqlserver_server_name is the name of your SQL Server database server
- sqlserver_server_instance_name is the name of your current instance
Note: To capture the output of each
command to a log file, append the following parameter to each command:
>> \file_path\db_application.log
where file_path is
the full path to the log file and application is
the name of the log file.
For example:
sqlcmd >>
\home\admin_user\lc_logs\db_activities.log
where sqlcmd is
a command with parameters and admin_user is the
logged-in user. Ensure that you have write permissions for the directories
and log files.
Note: If your database version of Connections components are already at a given
schema version, then run scripts for that schema version level.
-
Perform the following steps for the Activities application:
-
Change to the Activities SQL scripts directory
Wizards/connections.sql/activities/sqlserver.
-
Enter sqlcmd -U dbUser -P dbPassword
. before each upgrade command.
Where:
- dbUser is the database user ID
- dbPassword is the administrator password
Note: This script generates a message that states
Changing any part of an object name could break scripts and stored procedures. You
can safely ignore the message.
-
Check for the database schema version as follows:
-i connect to OPNACT
-i select DBSCHEMAVER from ACTIVITIES.OA_SCHEMA
- If schema version is 69, then enter the following
commands:
-i upgrade-50-50CR1.sql
-i upgrade-50CR1-55.sql
-i upgrade-55-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 72, then enter the following
commands:
-i upgrade-50CR1-55.sql
-i upgrade-55-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 94, then enter the following
commands:
-i upgrade-55-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 98, then enter the following
commands:
-i upgrade-55CR2-60.sql
-i appGrants.sql
-
Perform the following steps for the Blogs application:
-
Change to the Blogs SQL scripts directory
Wizards\connections.sql\blogs\sqlserver.
-
Enter sqlcmd -U dbUser -P dbPassword
before you run each upgrade command.
-
Check the database schema version as follows:
-i connect to BLOGS
-i select value from BLOGS.roller_properties where name='database.schema.version'
- If schema version is 69 , then enter the following
commands:
-i upgrade-50-50CR1.sql
-i upgrade-50CR1-50CR2.sql
-i upgrade-50CR2-55.sql
-i upgrade-55-60.sql
-i appGrants.sql
- If schema version is 70, then enter the following
commands:
-i upgrade-50CR1-50CR2.sql
-i upgrade-50CR2-55.sql
-i upgrade-55-60.sql
-i appGrants.sql
- If schema version is 72, then enter the following
commands:
-i upgrade-50CR2-55.sql
-i upgrade-55-60.sql
-i appGrants.sql
- If schema version is 75, then enter the following
commands:
-i upgrade-55-60.sql
-i appGrants.sql
-
Perform the following steps for the Bookmarks application:
-
Change to the Bookmarks SQL scripts directory
Wizards\connections.sql\dogear\sqlserver.
-
Enter sqlcmd -U dbUser -P dbPassword
before each upgrade command.
-
Check for the database schema version as follows:
-i connect to DOGEAR
-i select DBSCHEMAVER from DOGEAR.DOGEAR_SCHEMA
-
Perform the following steps for the Communities application:
-
Change to the Communities SQL scripts directory
Wizards\connections.sql\communities\sqlserver.
-
Run sqlcmd -U dbUser -P dbPassword before
each upgrade command.
-
Check the database schema version as follows:
-i connect to SNCOMM
-i select DBSCHEMAVER from SNCOMM.SNCOMM_SCHEMA
- If schema version is 93, then enter the following
commands:
-i upgrade-50-50CR2.sql
-i upgrade-50CR2-55.sql
-i upgrade-55-60.sql
-i appGrants.sql
- If schema version is 98, then enter the following
commands:
-i upgrade-50CR2-55.sql
-i upgrade-55-60.sql
-i appGrants.sql
- If schema version is 104, then enter the following
commands:
-i upgrade-55-60.sql
-i appGrants.sql
-
Perform the following steps for the Calendar application:
-
Change to the Calendar SQL scripts directory
Wizards/connections.sql/communities/sqlserver.
-
Run sqlcmd -U dbUser -P dbPassword
before each upgrade command.
-
Check the database schema version as follows:
-i connect to SNCOMM
-i select DBSCHEMAVER from CALENDAR.CA_SCHEMA
- If schema version is 29, then enter the following
commands:
-i calendar-upgrade-50-50CR1.sql
-i calendar-upgrade-50CR1-55.sql
-i calendar-upgrade-55-60.sql
-i calendar-appGrants.sql
- If schema version is 30, then enter the following
commands:
-i calendar-upgrade-50CR1-55.sql
-i calendar-upgrade-55-60.sql
-i calendar-appGrants.sql
- If schema version is 34, then enter the following
commands:
-i calendar-upgrade-55-60.sql
-i calendar-appGrants.sql
-
Perform the following steps for the Files application:
-
Change to the Files SQL scripts directory
Wizards\connections.sql\files\sqlserver.
-
Enter sqlcmd -U dbUser -P
dbPassword before each upgrade command.
-
Check the database schema version as follows:
-i connect to FILES
-i select SCHEMA_VERSION from "FILES"."PRODUCT"
- If schema version is 107, then enter the following
commands:
-i upgrade-50-55.sql
-i upgrade-55-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 139, then enter the following
commands:
-i upgrade-55-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 140, then enter the following
commands:
-i upgrade-55CR2-60.sql
-i appGrants.sql
Note: Do not run the following scripts for the Files application:
- pns-createDb50.sql
- pns-dropDb.sql
-
Change to the Wizards/connections.sql/pushnotification/sqlserver
directory, and check the database schema version as follows:
-i connect to PUSHNOTIFICATION
-i select SCHEMA_VERSION from PUSHNOTIFICATION.PRODUCT
- If you cannot connect to PUSHNOTIFICATION, switch to
Wizards/connections.sql/files/sqlserver, and enter the following command:
-i pns-dropDb.sql
Then switch back to
Wizards/connections.sql/pushnotification/sqlserver, and enter the following
commands:
-i createDb.sql
-i appGrants.sql
- If schema version is 7, then enter the following
commands:
-i upgrade-55-60.sql
-i appGrants.sql
-
Perform the following steps for the Forums application:
-
Change to the Forums SQL scripts directory
Wizards\connections.sql\forum\sqlserver.
-
Enter sqlcmd -U dbUser -P
dbPassword before each upgrade command.
-
Check the database schema version as follows:
-i connect to FORUM
-i select DBSCHEMAVER from FORUM.DF_SCHEMA
- If schema version is 35, then enter the following
commands:
-i upgrade-50-50CR1.sql
-i upgrade-50CR1-55.sql
-i upgrade-55-60.sql
-i appGrants.sql
- If schema version is 36, then enter the following
commands:
-i upgrade-50CR1-55.sql
-i upgrade-55-60.sql
-i appGrants.sql
- If schema version is 38, then enter the following
commands:
-i upgrade-55-60.sql
-i appGrants.sql
-
Perform the following steps for the Home page application:
-
Change to the Home page SQL scripts directory
Wizards\connections.sql\homepage\sqlserver.
-
Run
sqlcmd -U dbUser -P dbPassword
before each upgrade command.
-
Check the database schema version as follows:
-i connect to HOMEPAGE
-i select DBSCHEMAVER from HOMEPAGE.HOMEPAGE_SCHEMA
- If schema version is 475 , then enter the following
commands:
-i upgrade-50-50CR1
-i upgrade-50CR1-50CR2.sql
-i upgrade-50CR2-50CR3.sql
-i upgrade-50CR3-50CR4.sql
-i upgrade-50CR4-55.sql
-i upgrade-55-55CR1.sql
-i upgrade-55CR1-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 477, then enter the following
commands:
-i upgrade-50CR1-50CR2.sql
-i upgrade-50CR2-50CR3.sql
-i upgrade-50CR3-50CR4.sql
-i upgrade-50CR4-55.sql
-i upgrade-55-55CR1.sql
-i upgrade-55CR1-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 478 , then enter the following
commands:
-i upgrade-50CR2-50CR3.sql
-i upgrade-50CR3-50CR4.sql
-i upgrade-50CR4-55.sql
-i upgrade-55-55CR1.sql
-i upgrade-55CR1-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 479, then enter the following
commands:
-i upgrade-50CR3-50CR4.sql
-i upgrade-50CR4-55.sql
-i upgrade-55-55CR1.sql
-i upgrade-55CR1-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 705, then enter the following
commands:
-i upgrade-55-55CR1.sql
-i upgrade-55CR1-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 706, then enter the following
commands:
-i upgrade-55CR1-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 707, then enter the following
commands:
-i upgrade-55CR2-60.sql
-i appGrants.sql
Next, you need to run a java migration from 5.0 to 5.5.
-
Perform the following steps for the Metrics application:
-
Change to the Metrics SQL scripts directory
Wizards\connections.sql\metrics\sqlserver.
-
Run sqlcmd -U dbUser -P dbPassword before each upgrade command.
-
Check the database schema as follows:
-i connect to METRICS
-i select SCHEMA_VERSION from "METRICS"."PRODUCT"
-
Perform the following steps for the Mobile application:
-
Change to the Mobile SQL scripts directory
Wizards/connections.sql/mobile/sqlserver.
-
Enter sqlcmd -U dbUser -P
dbPassword before each upgrade command.
-
Check the database schema version as follows:
-i connect to MOBILE
-i select VALUE from MOBILE.ROLLER_PROPERTIES where NAME='database.schema.version'
-
Perform the following steps for the Profiles application:
-
Change to the Profiles SQL scripts directory
Wizards\connections.sql\profiles\sqlserver
-
Enter sqlcmd -U dbUser -P dbPassword before
each upgrade command.
Note: This script generates a message that states
Changing any part of an object name could break scripts and stored procedures. You
can safely ignore the message.
-
Check the database schema version as follows:
-i connect to PEOPLEDB
-i DBSCHEMAVER from EMPINST.SNPROF_SCHEMA
-
Perform the following steps for the Wikis application:
-
Change to the Wikis SQL scripts directory
Wizards\connections.sql\wikis\sqlserver.
-
Enter sqlcmd -U dbUser -P dbPassword
before each upgrade command.
-
Check the database schema version as follows:
-i connect to WIKIS
-i select SCHEMA_VERSION from "WIKIS"."PRODUCT"
- If schema version is 107, then enter the following
commands:
-i upgrade-50-55.sql
-i upgrade-55-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 139, then enter the following
commands:
-i upgrade-55-55CR2.sql
-i upgrade-55CR2-60.sql
-i appGrants.sql
- If schema version is 140, then enter the following
commands:
-i upgrade-55CR2-60.sql
-i appGrants.sql
-
IBM® Connections Content Manager:
Wizards\connections.sql\libraries.gcd\sqlserver
- sqlcmd -U dbUser -P dbPassword -i "createDb.sql" -v filepath="path_to_db"
password="password_for_FNGCDUSER"
- sqlcmd -U dbUser -P dbPassword appGrants.sql
Wizards\connections.sql\libraries.os\sqlserver
- sqlcmd -U dbUser -P dbPassword -i "createDb.sql" -v filepath="path_to_db"
password="password_for_FNOSUSER"
- sqlcmd -U dbUser -P dbPassword appGrants.sql
-
Next, update databases to the CR1 level as explained in the IBM technote, Updating the IBM Connections 6.0 databases to the required schema versions for Cumulative Refresh 1
(CR1).
What to do next
Check that all the databases are working
correctly.