CA Single Sign On Secure Proxy Server (SiteMinder)CA Single Sign On SOA Security Manager (SiteMinder)CA Single Sign-OnSITEMINDER
Issue/Introduction
This is a demonstration of using smtest tool for stress testing the policy server.
Environment
Release: Component: SMPLC
Resolution
Run smtest tool. You can only run smtest tool on Windows. There are two type of smtest tool, stand-alone or bundled with a policy server package. The stand-alone one can be obtained from a corresponding Siteminder SDK package.
Enter details and options as below. Please note: the SmHost.conf must be the one from a Windows web server
Enter the Output Script Selection: e.g: D:\input.txt (There should be no existing file as it will APPEND)
Select Connect -> IsProtected -> IsAuthenticated -> IsAuthorized. This will generate content in the input file, D:/input.txt, to run smtest command.
Close the smtest tool
Create a D:\controlfile.txt file with a content similar to this.
.output .brief D:\input.txt, 1, 1 .disconnect
The meaning of "D:\input.txt, 1, 1" is at this format: <script file name>, <number of script repetitions>, <number of threads> You can increase those numbers accordingly.
Save the file.
So, now you have input.txt and controlfile.txt, it is ready to run the smtest.
From a DOS command, navigate to Siteminder bin directory, where smtest.exe resides and run the commands as below:
For example, D:\<Siteminder_root_path>\bin>smtest d:\controlfile.txt /c Here are the list of smtest options:
SmTest --> opens the SmTest Windows UI without initial settings
SmTest <Init_file> --> opens the SmTest Windows UI with initial settings
SmTest <Input_file> <Output_file> --> runs Basic Playback mode without opening the Windows UI
SmTest <Input_file> /F --> runs Basic Playback mode with default output file at DOS
SmTest <Control_file> /C --> runs Advanced Playback mode without opening the Windows
After the test finishes, there is a stats file generated under the same directory of the input.txt file with the file name as <the input filename>_stats, e.g input.txt_stats. It contains some useful information of the test.