The Sametime® workloads
The Domino® Administrator client contains three IBM® Sametime® workloads.
About this task
- Sametime® Initialization workload
- Sametime® 7.0 Instant Messaging workload
- Sametime® 7.5 Instant Messaging workload
The information in this topic applies to all three Sametime® workloads. Review this section and complete the necessary steps prior to running any of the three Sametime® workloads.
Sametime® Workload Setup
Procedure
- Install the Domino® Administrator client. Select the Server.Load option from the Client Install Options list.
- Install Server.Load or NotesBench into the Notes® client program directory as needed.
- Add the required NOTES.INI settings to the test driver's NOTES.INI file and replace the values in the table with the values for your test setup.
NOTES.INI variables required by all Sametime® workloads
About this task
In the examples, RND(XdY) indicates that a random number is generated by rolling a "Y" sided die "X" times. For example, RND(5d10) indicates that five 10-sided dice are rolled and the results are summarized to form a random number.
NOTES.INI variables required by all Sametime® workloads |
Description |
---|---|
NB_EnableSTAwareness=1 |
Enables Sametime® Awareness |
JavaMaxHeapSize=700M |
JNI/java maximum heap size |
JavaUserClasses=CstClientTest.jar;stjavatk.jar, ibmjceprovider.jar |
Required jar files |
ST.server=<servername> |
Sametime® server name |
ST.user=<username prefix> |
Prefix for users; for example, "mail" |
ST.password=<user password> |
Password used to authenticate a user |
ST.login.type=[MUX|JAVA] |
MUX simulates a mux, JAVA simulates a direct client connection |
ST.logout.pause.wait=RND(100d6) |
Time to wait before logging in again |
ST.bl.size.quan=RND(4d100) |
The number of users to add to each buddy list |
ST.bl.beginuser.number= 1 |
Starting user number for buddy list operations |
ST.bl.enduser.number=1000 |
Ending user number for buddy list operations |
ST.test.maxusers=10000 |
Maximum number of users in the test |
ST.debug.filename=c:\\results\\debugout.txt |
The name of the file to which errors are written, requires STdebug > 0 |
STDebugOn=<value> |
Specify one of these debug settings:
|
NB_Include_ST_Stats=1 |
Enables per-minute statistics to be sent to the console window. To capture the stats, set DEBUG_OUTFILE=<filename> |
NOTES.INI variables for the Sametime® 7.0 and 7.5 Instant Messaging workloads |
Description |
---|---|
ST.converse.pause.wait=RND(10d6) |
Think time between exchanged messages |
ST.converse.nummessages.quan=RND(1d10) |
Number of messages per chat |
ST.converse.messagelength.quan=RND(8d128) |
Size in bytes of each message sent |
ContextIteration1=3 |
Run a command every third iteration (once every 45 minutes) |
ContextIteration2=24 |
Run a command every twenty-fourth iteration (once every 6 hours) |
ContextIteration3=12 |
Run a command every twelfth iteration (once every 3 hours) |
NOTES.INI variables for the Sametime® 7.5 Instant Messaging workload |
Description |
---|---|
NB_ENABLELOCATIONWATCH=1 |
Choose one:
|
ContextIteration4=12 |
Run a command every twelfth iteration (once every 3 hours) |
ST.converse.htmltext.percent=90 |
Percent of all rich text messages sent with STchat that should be HTML |
ST.converse.img.percent=10 |
Percent of all rich text messages sent with STchat that should be images |
ST.converse.img.filename=c:\\lotus\\notes\\data\\image.gif |
The image file that users should send. The maximum image size is 100K. |
NB_DISABLEFILETRANS=1 Note: In
tests, file transfers have been shown to be resource-heavy operations.
To save resources, IBM® recommends
setting NB_DISABLEFILETRANS=1. If file transfers are required, set
NB_DISABLEFILETRANS=0. |
To run the workload with File Transfer enabled, set this variable to 0. |
NB_STFTransSizeInBytes=1000000 |
Size (in bytes) of the file to transfer. Server policies can restrict this on the server side |
NB_STFTransFileTypeBinary=1 |
Set to 1 for binary format, otherwise it is set to text |
ST.ft.send.file=<filepath/name |
Specify a particular file for file transfer |
ContextIteration5=24 |
Associated with File Transfer in the workload. In this example, the 24 indicates that file transfer will occur once every 24th iteration. |
ST.ft.receive.location=<path> |
Where to place the received file on file transfer. Currently the file is deleted after it is received, but a valid location is necessary |