Preventive Service Planning
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:
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;
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
- Copy the exportPolicies.bat script on the DB2 box which contains Sametime System Console database for 8.5.2 Sametime System Console
- Run the exportPolicies.bat script in command line as follows :
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
- On the DB2 server, log in to the system as the DB2 administrator created during DB2 installation.
- 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.
- 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.
- 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.