Posts Tagged ‘testing’

BMC Remedy Performance Testing Tools

December 10th, 2009
BMC Remedy ARSystem

BMC Remedy ARSystem

Performance is the most important aspect of any application or service regarding User/Customer satisfaction. Great UI and Highly sophisticated applications or services can fall short if the performance is poor. This will be same in any application development environment even including Remedy apps.

I have heard a lot about performance testing tools but never used one, though I have done performance tuning before never tried tools to test them except Developer Plus. Remedy Developer Plus is an excellent tool which analyzes and let developers know about Structural, performance and Security based analysis and solutions.

I mainly use Developer plus to find fields which are larger than 255 characters, not indexed and used in queries, Active Link/Filter multiple execute on conditions and inefficient queries. I also love the Execution flow graphical view. What Remedy developer tool can do is limited in terms of performance testing, there are several tools available for this particular task to do load, performance and stress testing.

Recently when I was going through “BMC Remedy AR System 7.x: Performance Tuning and Troubleshooting” book from BMC, I was struck with by a note which says performance generators like Mercury, LoadRunner and Seque Silk performer are not advisable to perform tests on Remedy.

The reasons as stated in the book are:

  • You should not run tests using performance generators like Mercury, LoadRunner, or Segue Silk Performer. They use the wrong layer to perform their load generation.
  • It is important to test at the RPC, or even better, the BMC Remedy API layer.
  • It is not recommended that you run tests using performance generators like Mercury, LoadRunner, or Seque Silk performer. Although these applications can produce a lot of work on a server for testing, they tap into the wrong layer in order to perform their load generation. The server can become “confused
  • It is much better to replay BMC Remedy work at the RPC Layer, or even higher, the API layer. It is recommended to use BMC Remedy ‘driver’ using BMC Remedy API executables (Java or C) or a higher level tool that emulates the clicking of buttons and the entering of data using GUI.

It is well known that BMC uses Scapa TPP internally to test ITSM applications and it is validated software from BMC.

Scapa TPP for BMC Remedy
Scapa TPP for BMC Remedy

Unlike other testing tools, Scapa integrates BMC Remedy at the HTTP and API level to record system performance with more accuracy.

Note: Remedy Developer Plus 6.3 doesn’t work with Remedy 7.x server (Just found it will not work that way) and it is integrated with BMC Remedy 7.5 IDE :)

Njoy, Venkat

%d bloggers like this: