Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.

How to stress/load test your GroupWise system with messages

How to stress/load test your GroupWise system with messages

Sometimes an admin may want to stress test their GroupWise system, underlying filesystem performance and message flow by load testing it with hundreds or thousands of messages.

With the correct tools, this is actually quite easy to do.  The tool I chose was Apache JMeter  which allows you to create automation scripts, and thankfully includes an easily usable SMTP module for building what we want by pushing the messages through your GWIA(s).

  1. Download and extract Apache JMeter, and be sure you have support java JVM installed.

  2. To start jmeter, go into the bin directory and run the appropriate jmeter.bat/sh script

  3. In jmeter gui, right click Test Plan and choose Add>Threads(users)>Thread Group

  4. Choose how many messages you want to push at a time, and how many in total by filling in the Number of threads, and Loop count.  A decent start is 10 threads and 100 loops, which will generate 1,000 messages, or 10 threads of 100 messages each.  Keep in mind this will be per SMTP thread you add in the following step.



  5. Right click Thread Group and choose Add>Sampler>SMTP Sampler.  Configure this SMTP to authenticate against your GWIA.  If you wish to test multiple GWIAs at once, simply add more SMTP Samplers to the thread group, just keep in mind that this will multiply your total messages generated.

    A good idea is to use a common nonexistant email from for all, a per smtp subject so you can easier see in mailbox which messages came through to assist in troubleshooting.

    There is also an option to include timestamp in subject which can assist in tracking message delivery delays.

    You can also attach files to each message if you want the test messages to be larger than just simple basic test.  Be wary of mailbox size growth.



  6. Don't forget to save your test plan so you can reload it later.

  7. Hit Run.  Monitor your various GroupWise agents using their agent web consoles, and of course GW Monitor.  Keep in mind GWIA mailbomb protection may block, so you may have to disable it temporarily on your GWIAs.

  8. Once done, I recommend using a User Activated rule to clean up your test messages.

    If you have separate post offices, you can further stress the system by using rules to move the generated messages to shared folders belonging to user/resource on separate PO.  This will further load your underlying filesystem mtp connunication between agents.


 

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2018-01-22 20:26
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.