IBM Sametime Migration and IBM Sametime Consulting Services
The IBM Sametime migration process in this documentation enables you to use most of the existing databases in both the existing Sametime 8.5.2x deployment and the new IBM Sametime 9 deployment at the same time; only the IBM Sametime 9 System Console and the IBM Sametime 9 Community Server receive new databases. Changes to database schemas and tables in Sametime 9 support new features that were not available in Sametime 8.5.2x, and will be ignored by the old deployment.
The Sametime databases in DB2 require the following updates for Sametime 9:
- Sametime System Console: Export the Policy database, update policies, and import them to a new Policy database using a new database name. Existing policy settings will be preserved.
- Sametime Meeting Server: Schema update required to support new features. The update does not impact existing meetings.
- Sametime Advanced Server: No changes to schema but you must add 3 items to the database for default configuration settings.
- Sametime Proxy Server: No changes.
- Sametime Gateway: No changes.
- Sametime Bandwidth Manager: No changes.
IBM Sametime upgradation steps
- Copy mail files in notes\data
- Copy mail files in notes\
- Verify ownership of directory
- Setting up Connect to LDAP Server, for user authancation for login
- Register the server Node, sametime server is working on Node, need to create the node
- utility registers the server. Utility link community or video conference need to registered
- SSCUserName and SSCPassword settings this setting working single sign on feature for sametime server
- Enabling the administrator to manage the Sametime Community
- Configuring Sametime Community for chat and live the user status
- "Verifying a Sametime Community Server
- Assigning users to a home Sametime Community Server
- Configuring the single login
- Turn on traffic to point to the new server
- Verification that server is running and functioning correctly
- Turn older server off
IBM Sametime upgradation requirement
- All Mail Files, usually in notes\data\mail directory
- All db's created by the original server
- notes.ini file
- b. Server ID file (Server.id, most company its saved as ServerName.Id)
- c. Administrator ID file (Administrator.Id)
- d. Certificate ID file (Cert.id)
- e. Domino Directory (Domino Address book) (NAMES.NSF)
- f. ADMIN4.NSF (Administration Requests Database)
- g. Evnet4.nsf (Monitoring Configuration database
- h. Admin4.nsf (Administration Process Database)
- i. DDM.nsf (Domino Domain Monitoring database, If exists)
- j. Log.nsf (Optional)
- k. Note: It is important to copy CERTLOG.NSF because it is used for security purposes and for user maintenance
- l. Move all user mail files. By default, the user mail files are stored in the Notes\Data\Mail directory.
- Move all other databases that were created on the original Domino server.