As promised, this is the next iteration of a blog discussing performance testing in BI 4.1 with Apache JMeter.  You can find the first installment, which covered logon and the refresh of a Web Intelligence report here.

The next BI client in the queue is Explorer.  This test plan allows you to invoke a previously created Exploration View set, built against a HANA calc view, to generate some load against both the application server and Explorer processes.  The part of the test plan dealing with Explorer looks like this:

explorer test plan.png

You can see that most of the activity comes from a file called polestar_xml.jsp and that there is a single regular expression extractor attached to the config.jsp file.  Explorer leverages both a serialized session and a session token to grant access to the application, a similar mechanism to that used with Dashboards (Xcelsius) and other components that leverage the dswsbobje web service.  A serialized session might look something like this:


This contains all sorts of useful information such as the authentication type, user name, Favorites Folder, and Personal Category.

A session token is a shorter string that looks like this:


The string represents the CMS that generated the session, as well as the logon token used to access the platform.

First, it is necessary to extract the user’s serialized session from the Logon transaction controller and the request.  The regular expression extractor should contain the following properties:

Serialized Session.png

For reference (and ease of copying) the regular expression to use for this is:

serializedSession: ‘(.+?)’,

This value is going to be URL encoded since there are a massive number of URL unfriendly characters such as &, { }, etc.  Once we have the infoviewses variable, it will be attached to the index.jsp request to gain initial access to Explorer.  The URL parameters of index.jsp should be configured as such:

Pass Session with Encoding.png

Note that we need to check the Encode? box to ensure the value is passed correctly.  With this option enabled for the serialized session above we see the following URL encoded value:


Fun isn’t it?  This request grants us access to Explorer.  From here it is simply a matter of adjusting the XML Parameter required in each of the polestar_xml.jsp calls.  Note that each of these requests has a parameter attached to it called xmlParameter as below:


This value actually has the session token embedded within it!  In order to correctly invoke Explorer functionality we need to adjust each response body as follows:


This is where JMeter really shows what an awesome product it is.  We are able to transform the contents of the sestoken variable by invoking a JavaScript method called encodeURIComponent.  This translates the session token above into this format:


Now use the text replacement process I discussed in the previous blog post to update the JMX file so that each occurrence of xmlParameter contains the JMeter function:


as the contents of the session token string.  Hopefully this example helps illustrate just how powerful JMeter can be in terms of executing scripts as part of your performance testing process.

Once you have correctly updated each of the polestar_xml.jsp requests you are ready to execute the Explorer section of your performance test.  By looking at the View Results Tree component for the polestar_xml.jsp calls we can see Explorer feeding us customized XML:

xmlOutput.pngYou can see the name of the connection, the measures in the view set, and numerous other properties associated with the Exploration.  This covers Explorer performance testing … next week I am at SBOUC but expect a final supplement to this blog the following week when I’ll cover Analysis Edition for OLAP.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply