ShowTable of Contents
As part of our regular Quality Assurance control, the IBM® Sametime® United Telephony (SUT) Systems Verification Test (SVT) team executes reliability tests on SUT environments. This article describes the process used internally within IBM to generate test users for reliability test cases.
We describe how to provision 15,000 users for a SUT workload. These users need to be created in the LDAP after which the IBM Tivoli® Directory Integrator (TDI) process is used to generate importFiles which are used in the SUT Common Management Portal (CMP) console.
Adding users in LDAP
Generate users DN
For this example we are using Tivoli Directory Server 6.2 as our LDAP server.
1. First, we need to create the base DN (domain name) where users' data will be stored; in this case, the ldif file 852_819OC_DN.ldif was created (see figure 1).
Figure 1. ldif file with users' DN
2. Use the following command to generate a DN:
ldifde -a cn=myLDAPUser myLDAPpassword -s ldapFQDN -i -f "852_819OC_DN.ldif"
3. Look for the following log messages to confirm that the import operation completed successfully:
Importing directory from file "852_819OC_DN.ldif"
Lazy commit support not available on the server, lazy commit will be disabled.
5 entries modified successfully.
The command has completed successfully
The LDAP GUI reflects that new records were created (see figure 2).
Figure 2. Users' DN in LDAP GUI
Generating ldif file with users' details
1. Using your preferred tool/script, create an ldif file similar to the one illustrated below (with 15,000 users); entries should be of the format:
dn: uid=testUser8190000,cn=testUsers 819,l=Dublin,c=IE,ou=SUT,o=My Test Org,dc=ibm,dc=com
dn: uid=testUser8190001,cn=testUsers 819,l=Dublin,c=IE,ou=SUT,o=My Test Org,dc=ibm,dc=com
2. When the file is ready, execute the following command to begin the import:
ldifde -a cn=myLDAPUser myLDAPpassword -s ldapFQDN -i -f "852_819OC_users.ldif"
The following messages confirm that the import was successful:
10000 entries modified successfully.
The command has completed successfully
This can also be confirmed in the LDAP GUI (see figure 3).
Figure 3. LDAP users created
Create a group
The next step is to create a group in the LDAP:
1. First prepare the ldif file as shown in the example in figure 4.
Figure 4. Sample ldif for group creation
2. When the file is ready, execute the following command for the import:
ldifde -a cn=myLDAPUser myLDAPpassword -s ldapFQDN -i -f "groupFile.ldif"
Figure 5 shows the group created in the LDAP GUI.
Figure 5. Group in LDAP GUI
Confirm users in the IBM Sametime Connect client
We should now be able to log in to the IBM Sametime Connect client using one of the imported users, as shown in figure 6.
Figure 6. User logged in to Lotus Sametime Connect
We are ready now to provision SUT subscribers.
Adding subscribers with the TDI
First, we need to install TDI and the provisioning project. If the Telephony Application Server (TAS) has been installed using the ./install.sh all command, then all required files are already installed since the All option includes the TDI and the provisioning project assembly lines.
If TDI is not installed in the TAS server then use the following command:
Update the setting.xml file, located in cd /opt/IBM/tivoli/tdi/solutions/SUT/, renaming the first template file:
cp settings.xml.template settings.xml
Figure 7 shows and example of a setting.xml file configured to provision TAS users using previously created LDAP records.
Figure 7. Sample setting.xml file
In the above file, we use addCFWD_2.js. It's a simple script:
$ cat scripts/addCFWD_2.js
var deskPhone = retrieveAttribute("homePhone");
return "900" + deskPhone;
Initial provisioning process
Now we are ready to run the initial provisioning process, which will create an output CSV file of subscriber data:
/opt/IBM/tivoli/tdi/solutions/SUT # ./initial.sh
Executing Initial User Provisioning ...
Total users found: 10000
Total users added: 10000
Total users skipped: 0
As a result, the file output/GrouptestUsers819.csv is generated, to be used in the CMP.
Before starting the user provisioning process, the setting.xml file must be prepared, which can be a time-consuming task that you may wish to run in batches. Each execution of the provisioning process retrieves user information from a data source.
The number of retrieved users can be changed in the config/SUTParameters.properties file by changing the value of the UserFetchLimit
parameter. It's strongly recommended to set this param to some small number while testing settings in the setting.xml file.
For more details on this process, refer to the product documentation topic, “Adding subscribers with the Tivoli Directory Integrator
Changing CMP before importing
Before we start importing the CSV file, we need to make some changes in the CMP.
Add local office code
To do this:
Figure 8. Add Office Code window
Define new Destination Code
- Log in to CMP as Administrator.
- Navigate to Telephony Control Server --- Global Translation and Routing --- Directory Numbers --- Office Codes.
- Add a new Local Office Code, as shown in figure 8.
To do this:
Figure 9. Add destination code
- In the CMP navigate to Telephony Control Server --- Business Group --- Translation --- Destination Codes.
- Add the Destination Code as shown in figure 9.
CSV file generated in previous step can be imported in CMP:
1. In CMP, navigate to Operation & Maintenance --- Recovery --- Import & Export --- Import (see figure 10).
Figure 10. Import function in CMP
2. Select a file to import; click Next (see figure 11).
Figure 11. Import – Step 1 window
3. The next window displays a warning message; this is the default message when provisioning more than 1000 users into the system.
Figure 12. Warning window when importing over 1000 users
The Latest Job Status window confirms the import was successful (see figure 13).
Figure 13. Latest Job Status window
4. Per the warning message, after import is completed, restart the system.