Rainer Brandl

Sametime 8.5.2.x Migration to Sametime 9


http://www-01.ibm.com/support/docview.wss?uid=swg21646498

Preventive Service Planning

Abstract

Because of changes to Websphere Application Server architecture, it is not possible to perform a straight migration from Sametime 8.5.x (based on Websphere 7.0.0) to Sametime 9 (based on Websphere 8.5.5). Instead, you must deploy Sametime 9 separately from your 8.5.x deployment and then reproduce any custom configuration items the Sametime 9 deployment. A key area of concern is the migration of user based data stored in DB2 such as your Sametime Meeting Rooms, Chat Rooms and Broadcast communities. This article describes you can migrate that data.

Content

Because of changes to Websphere Application Server architecture, it is not possible to perform a straight migration from Sametime 8.5.x (based on Websphere 7.0.0) to Sametime 9 (based on Websphere 8.5.5). Instead, you must deploy Sametime 9 separately from your 8.5.x deployment and then reproduce any custom configuration items to the Sametime 9 deployment. A key area of concern is the migration of user-based data stored in DB2 such as your Sametime Meeting Rooms, Chat Rooms and Broadcast communities. This article describes how to migrate that data.
There are two options for migration:
  • Option 1 – Keep using your existing Sametime 8.5.2 databases running on DB2 9.5 or 9.7* or on DB2 for IBM i
  • Option 2 – Migrate the databases from DB2 9.5 – 9.7 to DB2 10.1


*Option 1 is the only option for IBM i platforms.
Option 1 – Keep using the existing Sametime 8.5.2 databases that are running on DB2 9.5 or 9.7 or on DB2 for IBM i
A. Sametime System Console
Deploy the new Sametime System Console database for the Sametime 9 environment to the existing server. Use the following steps to migrate policies from the Sametime System Console for Sametime 8.5.2 to the Sametime System Console for Sametime 9:

Step 1 : Directly export the TEMPLATE table and ASSIGNMENT table from Sametime System Console DB (with V 8.5.2) using DB2CC -> export (on IBM i, use iNavigator-> export), or by using the commands that follow.
CONNECT TO S_SC12;EXPORT TO “c:\backup_Pol_template.txt” OF DEL MESSAGES “c:\2.txt” SELECT * FROM POLICY.TEMPLATE;CONNECT RESET;
CONNECT TO S_SC12;EXPORT TO “c:\backup_Pol_assignment.txt” OF DEL MESSAGES “c:\2.txt” SELECT * FROM POLICY.ASSIGNMENT;CONNECT RESET;
On IBM i, use the following commands to export the policy data to stream file:
CPYTOIMPF FROMFILE(POLICY/ASSIGNMENT) TOSTMF(‘/HOME/852TEST/ASSIGNMENT.CSV’) RCDDLM(*LFCR)
CPYTOIMPF FROMFILE(POLICY/TEMPLATE) TOSTMF(‘/HOME/852TEST/TEMPLATE.CSV’) RCDDLM(*LFCR)
Step 2 :  Import the same file in S9 Sametime System Console DB. “TEMPLATE” table in delimited format and by selecting import mode as “INSERT_UPDATE” and “ASSIGNMENT” table in REPLACE mode OR using the commands that follow:
CONNECT TO S_SC14;IMPORT FROM “C:\backup_Pol_template.txt” OF DEL METHOD P (1, 2, 3, 4, 5, 6) MESSAGES “c:\2.txt” INSERT_UPDATE INTO POLICY.TEMPLATE (POLICY_ID, POLICY_LABEL, POLICY_WEIGHT, POLICY_PRODUCT, POLICY_TYPE, POLICY_XML);CONNECT RESET;

CONNECT TO S_SC14; IMPORT FROM “c:\backup_Pol_assignment.txt” OF DEL METHOD P (1, 2, 3, 4) MESSAGES “c:\2.txt” REPLACE INTO POLICY.ASSIGNMENT (POLICY_ID, POLICY_PRODUCT, USER_ID, IS_GROUP); CONNECT RESET;
PolicyCleaner.class
On IBM i, copied the export file ASSIGNMENT.CSV,TEMPLATE.CSV and PolicyCleaner.class to the directory under the target IBM i system. For example, copy the csv file to the /home/9test and copy the class file to the /test (these two folders could be the same). Then run the following commands:

JAVA CLASS(‘PolicyCleaner’) PARM(‘/HOME/9TEST/TEMPLATE.CSV’) CLASSPATH(‘/TEST’)
CPYFRMIMPF FROMSTMF(‘/HOME/9TEST/ASSIGNMENT.CSV’) TOFILE(POLICY/ASSIGNMENT) MBROPT(*REPLACE) RCDDLM(*LFCR)
CPYFRMIMPF FROMSTMF(‘/HOME/9TEST/TEMPLATE.CSV’) TOFILE(POLICY/TEMPLATE) MBROPT(*UPDADD) RCDDLM(*LFCR)

Step 3:  Log out from Sametime System Console and log back in. Go to Sametime System Console -> Manage Policies -> Edit Policy Settings -> Update Policies -> Apply/Done.
Note that the policies are updated from Sametime 8.5.2 to 9 without any side effects on settings. There are new fields added and templates added but the existing settings are not changed.
Using automated scripts
Attached are automated batch scripts that you can use to export the TEMPLATE table and ASSIGNMENT table from Sametime System Console DB in Sametime 8.5.2.
exportPolicies.batexportPolicies.batimportPolicies.batimportPolicies.bat
Windows
  1. Copy the exportPolicies.bat script on the DB2 box which contains Sametime System Console database for 8.5.2 Sametime System Console
  2. Run the exportPolicies.bat script in command line as follows : 


 exportPolicies.bat

For example: exportPolicies.bat s_sc14 c:\exports
3. Copy the importPolicies.bat script and the policies exported folder on the box where Sametime System Console DB for Version 9 is present 
4. Run importPolicies.bat script in command line as follows : 
importPolicies.bat
For example: importPolicies.bat s_sc12 c:\exports
5.  Logout from Sametime System Console and log back in. Go to the Sametime System Console and click Manage Policies -> Edit Policy Settings -> Update Policies -> Apply/Done.
 exportPolicies.shimportPolicies.sh
Linux
1. Copy the exportPolicies.sh script on the DB2 box which contains Sametime System Console database for 8.5.2 Sametime System Console
2. Make sure you are logged in as db2 administrator, else use “su – ” to switch as db2 administrator. 
3. Run the exportPolicies.sh script in terminal as follows : 
sh exportPolicies.sh
For example: sh exportPolicies.sh s_sc14 /opt/IBM/DatabaseScripts/PolicyExports/
4. Copy the importPolicies.sh script and the policies exported folder on the box where Sametime System Console DB for Version 9 is present 
5. Log in as the db2 administrator, else use “su – ” to switch as db2 administrator. Run the importPolicies.sh script in command line as follows : 
sh importPolicies.sh
For example: sh importPolicies.sh s_sc12 /opt/IBM/DatabaseScripts/PolicyExports/
6.  Logout from Sametime System Console and login back. From the Sametime System Console, click Manage Policies -> Edit Policy Settings -> Update Policies -> Apply/Done
 exportPolicies_i.shexportPolicies_i.shimportPolicies_i.shimportPolicies_i.sh
IBM i
1. Copy the exportPolicies_i.sh script to the IBM i system where System Console Server 8.5.* is installed. for example: copy to the folder /test
2. From the IBM i command line, run the following command to start the QShell interpreter : QSH
3. Navigator to the script directory,for example: cd /test
4. Run the exportPolicies_i.sh script to export the data as follows:
exportPolicies_i.sh
For example: exportPolicies_i.sh /policyexports
5. Copy the importPolicies_i.sh script and PolicyCleaner.class to the IBM i System where System Console Server 9 is installed. for example: copy the script to the folder /test and copy the class to another folder or the same folder as the import scripts.
6. Repeat step 2 and 3. then run the importPolicies_i.sh script to import the data as follows:
importPolicies_i.sh
if don’t specify , it will be the same as
For example: importPolicies_i.sh /test
7. Logout from Sametime System Console and login back. From the Sametime System Console, click Manage Policies -> Edit Policy Settings -> Update Policies -> Apply/Done

B. Sametime Meetings
Update the schema of the Sametime Meetings Database. This does not impact existing meetings, only adding new tables for new features. In the database scripts folder – execute applyDDLUpdate.bat/sh
  1. On the DB2 server, log in to the system as the DB2 administrator created during DB2 installation.
  2. If you are logging in for the first time, create a DB2 profile if you are prompted to do so, then close the Welcome to First Steps window.
  3. Open a command prompt and navigate to the folder where you extracted the Sametime Meeting Server installation package.  Scripts are located under DatabaseScripts – Meeting Server.
  4. Create the database by entering one of the following commands from the SametimeDB2 folder. Wait until you see confirmation that the database has been created and the command has finished.


AIX, Linux, or Solaris: ./applyDDLUpdate.sh STMS dbadmin
Windows: applyDDLUpdate.bat STMS dbadmin
IBM i: ./appDDLUpdate.sh
Replace STMS in the command if you chose a different database name during installation. Replace dbadmin with the DB2 Application User ID you created when you installed DB2. This user has database administration authority.

  • When creating the deployment plan(s) for your new S9 environment, point it to your existing STMS database
  • If you want to isolate your S9 meetings during intial deployment (for testing), you still need to update the schema of the existing database as well as create a new database for the testing.
  • After deployment, you can manually update the datasource reference manually to point to the existing database (see procedure that follows).

C. Sametime Advanced

  • There are no schema updates required. There are 3 inserts that need to be manually run for new default configuration items.
  • When creating the deployment plan(s) for your new S9 environment, point it to your existing STADV database
  • If you want to isolate your S9 meetings during intial deployment (for testing) you still need to insert the records into the existing database as well as create a new database for the testing.
  • After deployment, you can manually update the datasource reference manually to point to the old database (see procedure that follows).

D. Sametime Proxy

  • There are no Schema updates required.
  • Based on the usage of the STProxy database (transient data only) there is no reason to have a seperate database for staging.
  • When creating the deployment plan(s) for your new S9 environment, point it to your existing STPRoxy database

E. Sametime Community
There are no updates required to VPUserinfo.nsf – follow standard procedures for moving the database to the new servers.

Changing the datasource references 1. In the Sametime System Console, go to Data sources.

2. Click the link for the resource you want to update. For example, for Sametime Meetings, you want to update both the MeetingServerDataSource and the MeetingServerAdminDataSource.



3. Update the pdate the settings as appropriate at the bottom of the page.

Option 2 – Migrate the databases from DB2 9.5/9.7 to DB2 10..1
Instructions for upgrading to DB2 Version 10.1 http://pic.dhe.ibm.com/infocenter/db2luw/v10r1/index.jsp?topic=%2Fcom.ibm.db2.luw.qb.upgrade.doc%2Fdoc%2Fc0023662.html
See also this technote – Upgrading to DB2 Version 10.1 roadmap http://www-01.ibm.com/support/docview.wss?uid=swg21573228
Please note that none of the deprecated or discontinued features in 10.1 have a direct impact on Sametime deployments.
After the Upgrade is complete – The steps in Option 1 apply for the individual products to bring the database schemas to the new version or to migrate policies.
–

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s