Moving Sametime EMS 8 to new machines

Now I have finished my Sametime Enterprise Meeting Server 8 (ST EMS 8) deployment I would like to share some tips with the Lotus community out there.

First of all, Sametime EMS is actually 3 Java applications (STAdmin, STCenter, STServer) running on top of WebSphere Application Server and connecting to Sametime servers in the background (data is stores in a DB2). ST EMS 8 will store the Meeting information in DB2, so don't try to go to stconf.nsf for old meetings information.

I won't go over the details of installing and deploying EMS, but I will cover what you need to do in order to move the old DB2 data to the new environment.

In case you are looking to move the entire DB2 database, you will need to backup and restore the DB in the new DB2 server. Also, if you are moving from ST 7.5 to ST 8, you will need to ask Lotus Support for a script which is suppose to upgrade the DB Schema.

I will suggest to remove the Sametime servers from the cluster before you backup the DB, then, after WebSphere is installed, running and talking to DB2, you can go ahead and restore the DB, deploy the EMS Java applications and add the Sametime Servers back to the cluster.

---------------------------------

Since my customer was actually moving from ST EMS 7.5 (Using ST 7.5 servers and Domino 7.0.2 server) to ST EMS 8, ST 8 and Domino 8.0.1, I decided to install everything from scratch and then just move (migrate) the meeting information (finished and scheduled) from the DB2 database

After I installed the new servers, deploy EMS, connect to DB2, add Sametime servers to the cluster I needed to move the Finished and Scheduled meetings information.

First, this is the list of tables you need from the SAMETIME Database:

SAMETIME.MEETING
SAMETIME.MEETING_ACCESS
SAMETIME.SCHEDULE
SAMETIME.TOOLS
SAMETIME.PARTICIPANT_ROLES
SAMETIME.MATERIAL_INFO
SAMETIME.MATERIAL
SAMETIME.RECORDED_MEETING

SAMETIME.LOG *
SAMETIME.LOG_MEETING_END *

Second, bring all the servers down (except for DB2) and using standard SQL, delete the records from those tables in the new DB2 database (* don't clean the Log databases).

Export and Import the tables from the old DB to the new one (including the log databases) and that's it. There are some special considerations when importing the DB2 data into the tables (identity columns, location, recorded meetings path, etc) I can share with you, but it is just to much information to post in one single blog entry.

Contact me at lguiriga at gmail dot com if you need it.

I don't have any image to post with this entry, but I will if I find something cool.