Performance Testing of Documentum

Before starting details of how to do performance testing on Documentum I will try share a basic of Documentum so you can get an idea why we need a different approach while doing performance testing on it.

What is Documentum?

Documentum is content management software that provides management of document content and attributes. Documentum product is a three-tier, client-server system built on top of a relational database.

Documentum components comprise the following:

·         Content Server - Manage access to the metadata stored in the relational database and the  Content files, usually stored in the file system

·         Webtop/Wdk Server - J2EE-based web application framework

Behavior behind the scene:

An applet is invoked at the client side when a file within the docbase is accessed and while files are imported into a docbase.

Applet/UCF client being client side Java application requires a JVM for each user and it cannot be run in Web/Http virtual user of Load Runner.

Performance Testing of Documentum:

I have performed load testing of Documentum using LoadRunner as well as RPT.

But approach in both is different. EMC has done well work while giving support for performance testing.

Correlation for Documentum:

As we know in performance testing Correlation is the main activity. It is always good practice to perform manual correlation.

But while doing performance testing of documentum, it is recommended to perform Auto Correlation.

To perform auto correlation a file called “Documentum.cor” or “EMC_docuementum.cor” (which defines basic correlation rules) needs to be imported. During auto correlation all the Request IDs, Reload IDs, Serial Numbers & UCF Request Keys get correlated. This common approach in both tools. Now I will share steps for LoadRunner tool and in next post related to RPT.

Performance Testing of Documentum using LoadRunner:

Documentum is a web based application but scripting in LoadRunner cannot be done the conventional way of using Web (HTTP/HTML) protocol. Invocation of applets and JVM startup for each user requirement makes scripting difficult in LoadRunner.

The solution for this problem was brought about by LoadRunner and EMC and they introduced WebTop Development kit which contain various dll, correlation suits, invoker.bat  and files which can be used which creating and executing the script.

Important Points before starting the testing:

1.      Ask your Documentum admin to provide you the winsuite installation: set up content server repository on the loadgenerator

2.      Get details of docbroker port and hostname

3.      Get Eclispe  on same system : this will help us verify compilation errors

4.      Include JARs which developer would include in his code

5.      server monitoring aspects - same old same old - get rstat daemons running on the Content\DB server

6.      Need to use The Java Vuser protocol

After this we can record our scripts and using auto correlation file, script will be modified. We can still correlate session id and UID variable manually.

Executing Scripts in Load runner:

For executing the recorded scripts for multiple users first we need to setup Load generator system in following manner:

1.       Ensure at least one manual content transfer has been done to the load generator machine. It will download the UCF client binaries such as UCFWin32JNI.dll, ucf-client-impl.jar, ucf-client-api.jar into the folder

C:\Documents and Settings\<windowsusername>\Documentum\ucf\<hostname>\shared\bin

2.       The “PATH” Environment Variable needs to be set to UCF binary folder. UCF Client invoker will fail if path is not set properly and also check for java installation& its path settings.

3.       UCFInvokerTool.zip has to extract and all “.renamed” extensions from filenames must be removed.

4.       All the paths in the startInvoker.bat file has to be updated to match the working environment

5.       The path settings in ucf.client.config.xml file have to be checked.

6.       The path to the DLL has to be updated in the vuser_init section of the sample scripts.

7.       The invoker can be started using “startInvoker.bat”.

We require also more modification at Script level:

1.       getUID function: Created by EMC which need to use in LR script

2.      Replace hardcoded UID with correlation.

EMC also provides support documents for script modification which is very useful if you are aware of Documentum structure and behavior.

Please note that WebTop Development kit has provided by EMC support. They have done well done job for support in performance testing.

Happy Testing!!!!!