Creating 50 users in advance
I noticed when a new user is created, he/she needs to login the first time to create the user account. Is there a batch process available to do that if I want to create 50 users account?
For each user created with TIMP there is a corresponding XML file in the following directory:
C:Documents and Settings-TW32JS_USER-Application Data-Tipic-spool-your_Jabber_server
Depending on the type of Authentication (integrated with NT or Standalone) the file will contain either a dummy password or the real password; the file also contains all the other info about the user and the offline messages received by the user.
IF you decide to change the XML file, you should be VERY careful about character encoding, and accepted XML, otherwise your JSM will stop working.
You can create the files for 50 users in advance, either by hand or by a simple batch program (off course changing the names of the files to reflect the use name).
If you pre-create these files, you can take the opportunity to pre-add contacts to users' rosters, if that is something interesting for your application.
--------------
If I create the 50 users in advance, does that mean they are automatically registered as new user and there is no need to relogin the first time to verify the account? (for integrated with NT)
YES
--------------
I presume I also need to create the similar account in Active Directory or Win2K users account if the type of authentication is integrated with NT.
YES. The request of creating a new account the first time you connect, is related to the creation of the XML file. There must be the Win2k user though (if you chose the integrated authentication) otherwise the client will not authenticate.
--------------
Does it mean that the user xml file is constantly updated, either when the user is online or offline (storing offline message)? What is updated in the xml file when user is online?
YES, it is constantly updated. It stores offline messages. It stores the password (which is dummy in the case of integrated authentication).
It also stores subscription information: for example a subscription information is the info related to the users with which the contact exchanges presence information; if that setting changes while the user is online (for example a new subscription) that information is stored in the XML file.