Update 2.5 SQL Server databases manually 

Manually update IBM Lotus Connections 2.5 databases to version 3.0.1 in an existing IBM WAS and Microsoft™ SQL Server database environment.


Before starting


Before applying updates, back up your databases. For more information, see the Backing up IBM Connections topic.

Ensure that you have installed and configured all supporting software for version 3.0.1.


About this task


This topic describes how to manually update Lotus Connections version 2.5 databases to version 3.0.1. Use this procedure if you want an alternative to using the database wizard to update your databases.

Notes:

To update databases manually...


Procedure

  1. Log in to the WAS admin console on your dmgr.

  2. Go to Applications -> Application types -> WebSphere enterprise Applications.

  3. Stop all Lotus Connections applications.

  4. Log in as the database administrator and change to the directory containing the scripts. The relative path is shown in the step for each application.

  5. For each application, run the appropriate scripts by entering the commands 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 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.

  6. Activities: Wizards\connections.sql\activities\sqlserver

    1. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30.sql

        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.

    2. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql

    3. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

  7. Blogs: Wizards\connections.sql\blogs\sqlserver

    1. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30.sql

    2. From a command prompt, change to the Wizards directory and enter the following text as a single command:

        jvm\win\jre\bin\java -classpath

        <jdbc_library_location>\sqljdbc.jar;

        lib\lc.dbmigration.default.jar;

        lib\blogs.migrate.jar;

        lib\commons-lang-2.0.jar;

        lib\commons-logging-1.0.4.jar

        com.ibm.lconn.blogs.migration.MigrationFrom25To30

        -dburl jdbc:sqlserver://<dbHost>:<dbPort>;databaseName=BLOGS

        -dbuser <dbUser> -dbpassword <dbPassword>

        where

        • <jdbc_library_location> is the location of your JDBC driver

        • <dbHost> is the name of the system hosting your database

        • <dbPort> is the communications port for the database

        • <dbUser> is the database user ID

        • <dbPassword> is the administrator password

    3. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

    4. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql

    5. From a command prompt, change to the Wizards directory and enter the following text as a single command:

        From a command prompt, change to the Wizards directory and enter the following text as a single command:

        jvm\win\jre\bin\java -classpath

        <jdbc_library_location>\sqljdbc.jar;

        lib\lc.dbmigration.default.jar;

        lib\blogs.migrate.jar;

        lib\commons-lang-2.0.jar;

        lib\commons-logging-1.0.4.jar

        com.ibm.lconn.blogs.migration.MigrationFrom30To301

        -dburl jdbc:sqlserver://<dbHost>:<dbPort>;databaseName=BLOGS

        -dbuser <dbUser> -dbpassword <dbPassword>

        where

        • <jdbc_library_location> is the location of your JDBC driver

        • <dbHost> is the name of the system hosting your database

        • <dbPort> is the communications port for the database

        • <dbUser> is the database user ID

        • <dbPassword> is the administrator password

    6. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

  8. Communities: Wizards\connections.sql\forum\sqlserver

      These commands create a Forums database and then update the Communities database.

      1. sqlcmd -U <dbUser> -P <dbPassword> -i createDb.sql -v filepath=<path_to_db> password=<dbPassword>

          where <path_to_db> is the full file path to the new database.

      2. sqlcmd -U <dbUser> -P <dbPassword> appGrants.sql

      3. sqlcmd -U <dbUser> -P <dbPassword> uninteg.sql

      4. From a command prompt, change to the Wizards directory and enter the following text as a single command:

          jvm\win\jre\bin\java -classpath

          <jdbc_library_location>\sqljdbc.jar;

          lib\lc.dbmigration.default.jar;

          lib\forum.migrate.jar;

          lib\commons-lang-2.0.jar;

          lib\commons-logging-1.0.4.jar

          com.ibm.lconn.forum.migration.MigrationFrom25To30

          -dburl "jdbc:sqlserver://<dbHost>:<dbPort>;databaseName=FORUM"

          -dbuser <3.0.1_dbAdmin> -dbpassword <3.0.1_dbPassword>

          -srcdburl "jdbc:sqlserver://<dbHost>:<dbPort>;databaseName=SNCOMM"

          -srcdbuser <2.5_dbAdmin> -srcdbpassword <2.5_dbPassword>

          where

          • <3.0.1_dbAdmin> is the name of the 3.0.1 database administrator account

          • <3.0.1_dbPassword> is the account password

          • <2.5_dbAdmin> is the name of the 2.5 database administrator account

          • <2.5_dbPassword> is the account password

      5. sqlcmd -U <dbUser> -P <dbPassword> integ.sql

      6. Change to the Wizards\connections.sql\communties\sqlserver directory and run the scripts in the following steps.

      7. sqlcmd -U <dbUser> -P <dbPassword> -i drop_lc25_forum_tables.sql

      8. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30a.sql

      9. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30b.sql

      10. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

      11. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql

      12. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

  9. Dogear: Wizards\connections.sql\dogear\sqlserver

    1. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30.sql

    2. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

    3. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql

    4. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

  10. Files: Wizards\connections.sql\files\sqlserver

    1. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30.sql

    2. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

    3. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql

    4. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

  11. Home page: Wizards\connections.sql\homepage\sqlserver

    1. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30a.sql

    2. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30b.sql

    3. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

    4. From a command prompt, change to the Wizards directory and enter the following text as a single command:

        jvm\win\jre\bin\java -classpath

        <jdbc_library_location>\sqljdbc.jar;

        lib\news.migrate.jar;

        lib\news.core.data.jar;

        lib\news.core.service.jar;

        lib\news.common.jar;

        lib\lc.admin.userlifecycle.spi.jar;

        lib\lc.events.newsEjbConsumer.jar;

        lib\lc.dbmigration.default.jar;

        lib\ibatis-2.3.0.677.jar;

        lib\spring.jar;

        lib\commons-logging-1.0.4.jar;

        lib\commons-dbcp-1.2.1.jar;

        lib\commons-collections-3.2.1.jar;

        lib\commons-pool-1.2.jar;

        lib\commons-lang-2.4.jar

        com.ibm.lconn.news.migration.EmailDigestMigrationFrom25To30
        Note: If you receive an Out Of Memory exception when running this command, you need to increase the memory allocation. Run the command again but with the -Xmx parameter. For example: -Xmx512 com.ibm.lconn.news.migration.EmailDigestMigrationFrom25To30

        -dburl jdbc:sqlserver://<dbHost>:<dbPort>

        -dbuser <dbUser> -dbpassword <dbPassword>

    5. From a command prompt, change to the Wizards directory and enter the following text as a single command:

        jvm\win\jre\bin\java -classpath

        <jdbc_library_location>\sqljdbc.jar;

        lib\news.migrate.jar;

        lib\news.core.data.jar;

        lib\news.core.service.jar;

        lib\news.common.jar;

        lib\lc.admin.userlifecycle.spi.jar;

        lib\lc.events.newsEjbConsumer.jar;

        lib\lc.dbmigration.default.jar;

        lib\ibatis-2.3.0.677.jar;

        lib\spring.jar;

        lib\commons-logging-1.0.4.jar;

        lib\commons-dbcp-1.2.1.jar;

        lib\commons-collections-3.2.1.jar;

        lib\commons-pool-1.2.jar;

        lib\commons-lang-2.4.jar

        com.ibm.lconn.news.migration.NewsMigrationFrom25To30

        -dburl jdbc:sqlserver://<dbHost>:<dbPort>

        -dbuser <dbUser> -dbpassword <dbPassword>

    6. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql

    7. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

  12. Profiles: Wizards\connections.sql\profiles\sqlserver

    1. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30.sql

        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.

    2. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

    3. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql

    4. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

  13. Wikis: Wizards\connections.sql\wikis\sqlserver

    1. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-25-30.sql

    2. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

    3. sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql

    4. sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql

  14. Migrate your 2.5 themes: From a command prompt, change to the Wizards directory and enter the following text as a single command:

      jvm\win\jre\bin\java -classpath

      <jdbc_library_location>\sqljdbc.jar;

      lib\lc.dbmigration.default.jar;

      lib\sncomm.migrate.jar;

      lib\commons-lang-2.0.jar;

      lib\commons-logging-1.0.4.jar

      com.ibm.tango.migrate.MigrateCommunityTheme_2_5_To_3_0

      -source sqlserver SNCOMM <2.5_dbHost> <2.5_dbPort> <2.5_dbUser> <2.5_dbPassword>

      -target sqlserver <3.0.1_database> <3.0.1_dbHost> <3.0.1_dbPort> <3.0.1_dbAdmin> <3.0.1_dbPassword>

      where

      • <2.5_dbHost> is the name of the system hosting your Lotus Connections 2.5 database,

      • <2.5_dbPort> is the communications port for the database

      • <2.5_dbAdmin> is the 2.5 database administrator ID

      • <2.5_dbPassword> is the administrator password

      • <3.0.1_database> is the database for the Activities, Blogs, and Wikis applications

      • <3.0.1_dbHost> is the name of the system hosting your IBM Connections 3.0.1 database

      • <3.0.1_dbPort> is the communications port for the database

      • <3.0.1_dbAdmin> is the 3.0.1 database administrator ID

      • <3.0.1_dbPassword> is the administrator password


What to do next


Check that all the databases are working correctly.


Parent topic

Update 2.5 databases manually

+

Search Tips   |   Advanced Search