Skip to Content
Author's profile photo Ryan Lang

Tracking Peak and Historical Concurrency Using BusinessObjects BI4 Monitoring

This brief article will detail how to quickly view your concurrency metrics using monitoring in BI4.x. This article is designed as an accompaniment to James Rapp’s excellent blog post which details how to track concurrency using the SDK in BI 3.1.

To explain why we may need to understand your concurrency, I will leverage James’ excellent explanation:

“Some of you may already be familiar with the new licensing model available for SAP BusinessObjects BI, but for those who aren’t, let me take a couple of minutes to explain Concurrent Sessions (CS) licensing and how it works.

Historically the CPU license model has been used extensively and remains a popular way to bring BI to a large number of report consumers at a reasonable cost.  CPU licensing allows an unlimited number of users to access the system.  For minimally intensive usage such as viewing of previously scheduled reports, distribution of agnostic documents such as PDF/XLS, and Crystal Reports viewing and refreshing, it can enable a vast number of business users to run successfully on just a few CPU.

On the other hand, customers wishing to implement more interactive BI (and thus more CPU intensive!), in the form of Web Intelligence ad-hoc, Explorer, and Dashboards, could quickly find themselves needing dozens (or even hundreds) of CPU to service a smaller user population.  This could make the CPU license model become cost prohibitive very quickly.  Fortunately for us SAP has listened, and delivered a complimentary license model that allows us to purchase the necessary number of concurrent sessions and scale CPU as required without the corresponding license cost.  For those of you that don’t already know, a concurrent session represents a connected user, in terms of InfoView/BI Launch Pad, Web Intelligence, Mobile, or any other client of the Business Intelligence system.”

I have seen that there are a lot of customers out there who have CPU based deployments and they need to expand. They may have less license allotment that the modern minimum hardware specs, or maybe they want to set up a clustered deployment, set up a swath of test and dev environments, or leverage the power of a tool like Lumira 2.0. No matter the reason, when looking to convert to a concurrent licensing model, it’s important to understand your current usage so you can size it correctly.

Here is a quick way to identify your current concurrent usage:

  1. Log onto your CMC
  2. Under ‘manage’ you’ll see ‘monitoring’ – Click it
  3. Click metrics
  4. Expand servers and your CMS
  5. Note: if you have a multiple, clustered CMS, you will need to do this for every CMS to get a full picture of your concurrency
  6. Add the ‘number of sessions established by all users’ metric to the selection and expand it
  7. Click ‘go to history’
  8. You’ll then see two dates which you can change. These create the reporting range, set that to a reasonable range for your expected usage

With those eight easy steps, you should now know your historical concurrency rate.



Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Atul Divekar
      Atul Divekar

      Hello Ryan,


      It will still capture data if my cms get restarted?



      Atul Divekar

      Author's profile photo Ryan Lang
      Ryan Lang
      Blog Post Author

      It should, it writes this data to a trending database.