HCL Sametime 12.0 – Converting from native Domino Directory to LDAP and Migrating contact list from older Sametime versions
0 likes1,159 views
This document provides a step-by-step guide for converting from a native Domino directory to LDAP and migrating contact lists to HCL Sametime 12.0. It outlines necessary preparations, such as blocking specific ports and using utilities for converting names and migrating contact data to MongoDB. The guide includes technical commands and procedures for different operating systems to ensure a successful migration process.
HCL Sametime 12.0 – Converting from native Domino Directory to LDAP and Migrating contact list from older Sametime versions
- 1. ALEŠ LICHTENBERG twitter: @a_lichtenberg blog: www.alichtenberg.cz HCL Sametime 12.0 (for Docker) Converting from native Domino Directory to LDAP and Migrating contact list from older Sametime versions Step by Step Ver. 1.0
- 2. About me 1 I am a technical consultant of HCL Digital Solutions software: Domino/Notes, Sametime, Nomad, Verse. I am a Member of Czech Lotus User Group = Sutol. I am a Bloger and a Speaker. I have been primarily engaged in the Lotus software family since 1994. I remember the era when these products were owned by Lotus, then IBM, and now I am looking forward to another successful years with HCL Software. Contacts: e-mail: ales@alichtenberg.cz twitter: a_lichtenberg blog: alichtenberg.cz
- 3. Agenda ▪ Step 1 - Converting from native Domino Directory to LDAP ▪ Step 2 - Migrating contact lists (VPUSERINFO.NSF) 2
- 4. Planning for migration to Sametime 12 3 • Sametime 12 does not support upgrades from an existing community or proxy server to Sametime 12. • Sametime 12 is now only containerized.You have to deploy the new images and then migrate your users. • If the new server is part of the same community as your existing servers, block port 1516 between the new server and existing server to prevent confusion while testing and validating new features. Prior to migrating, make sure port 1516 is open. • Running the notes-migration tool moves your contact list to MongoDB. • If the older Sametime deployment is not configured for LDAP, then the contact lists must be converted using the Stnamechange utility. Run the utility on Sametime 9, 10 or 11 before migrating.
- 5. 4 Step 1 Converting from native Domino directory to LDAP If you already have your existing Sametime configured for LDAP, you can skip this step
- 6. Sametime 12.0 - Converting from native Domino Directory to LDAP • Users create a contact list, a privacy list, and an alert-me-when list in the HCL Sametime Connect client by selecting user names or group names from the Domino or Domino LDAP directory that is used with the Community Server. These contact, privacy, alert-me-when lists are stored in the user information database (vpuserinfo.nsf) on Community Servers. When a user starts the Sametime Connect client, the lists are downloaded from the database to update the lists stored on the client's local computer. • If the older Sametime deployment is not configured for LDAP, the contact lists must be converted using the Stnamechange utility before migrating. • Running the name conversion utility updates Community Server user or group names with the latest directory changes. The name conversion utility uses a comma-separated value list that you compile to change names, delete names, or convert all names from Domino to Domino LDAP formatted names. • Run the task on the older Sametime Community server. • In our example, we will be migrating from Sametime 11.6 5
- 7. Sametime 12.0 - Converting from native Domino Directory to LDAP • Create a csv file (for example ldap.csv) in a text editor. • The text file should be saved in UTF-8 format • In our case, type in the file: LDAP • Save the file to your local disk for now • You can find details about creating a csc file in the documentation 6
- 8. Sametime 12.0 - Converting from native Domino Directory to LDAP • Using a Notes or Administrator client open the stnamechange.nsf database on the Sametime Community server (V11.x). 7
- 9. Sametime 12.0 - Converting from native Domino Directory to LDAP • From the Notes or Administrator Client menus, select Create > Name Change Task. • Provide a Name and optional Description. 8
- 10. Sametime 12.0 - Converting from native Domino Directory to LDAP • In the next window fill in the name of the document, the "Description” field is optional, In the “Location” field enter the DN of your Sametime Community Server (for example “CN=<server_name>/O=<organisation_name>”) • Paste the saved csv file (ldap.csv) into the "File" field • Save and Close this document. 9
- 11. Sametime 12.0 - Converting from native Domino Directory to LDAP • If the existing Community server runs on Linux OS: • To use the tool for Windows OS, use the documentation • Open a command line • Stop the HCL Sametime Community Server and the Domino server • You must run the program as „notes“ user • Sign in as notes user: su notes • Change to the Domino data directory: cd /domino/notesdata • Type the following command: /stnamechange.sh domino_bin_directory domino_data_directory • For example: ./stnamechange.sh /opt/hcl/domino/notes/11000100/linux /local/notesdata 10
- 12. Sametime 12.0 - Converting from native Domino Directory to LDAP • A successful transfer looks like this 11
- 13. Sametime 12.0 - Converting from native Domino Directory to LDAP • When the utility runs, it creates a log file that summarizes information or error found during the conversion. It stores the log file in the "trace" folder (/local/notesdata/trace) with a name that includes the time and date that the utility ran, such as name_change_summary_report_220906_2022.log. 12
- 14. DONE! You have now completed the conversion from the native Domino Directory to LDAP 13
- 15. Step 2 Migrating contact lists (VPUSERINFO.NSF) 14
- 16. • In Sametime 9.x, 10.x and 11.x, VPUserinfo.nsf stores all the contact list for users. To migrate your contact list from a previous release to Sametime 12, the contact list data must be migrated to MongoDB. • On the Sametime server you want to migrate from, copy and extract the notes- migration.zip to the server notesdata directory from the Sametime_12.0.zip or Sametime_Premium_12.0.zip file downloaded from the HCL Software Portal. 15 Sametime 12.0 - Migrating contact list from older Sametime versions
- 17. • Edit the notes-migration-user-input.txt file 16 Sametime 12.0 - Migrating contact list from older Sametime versions
- 18. • Enter the path to the vpuserinfo .nsf file NSF_PATH=/local/notesdata/vpuserinf.nsf • Enter Mongo connections URL • And enter „true“ in the USER_MIGRATION and PRIVACY_MIGRATION: USER_MIGRATION=true PRIVACY_MIGRATION=true • Save and close file 17 Sametime 12.0 - Migrating contact list from older Sametime versions
- 19. 18 Sametime 12.0 - Migrating contact list from older Sametime versions • If the existing Community server runs on Linux OS: • To use the tool for Windows OS, use the documentation • Open a command line • Stop the HCL Sametime Community Server and the Domino server • You must run the program as „notes“ user • Sign in as notes user: su notes • Change to the Domino data directory: cd /domino/notesdata • You must run this command from the Sametime server's program directory where sametime.ini and notes.ini exist • Run the following commands to setup the environment and run the migration task source ./setenv.sh ./notes-migration.sh
- 20. 19 Sametime 12.0 - Migrating contact list from older Sametime versions • You can also monitor the progress of the conversion of vpuserinfo.nsf to Mongo DB
- 21. 20 Sametime 12.0 - Migrating contact list from older Sametime versions • You can also monitor the progress of the conversion of vpuserinfo.nsf to Mongo DB • Once done, you can log in to the new Sametime 12.0 community server and you should see your original contact list
- 22. DONE! You have now completed the migrating contact list from older Sametime versions to Sametime 12.0 21