Thursday, February 10, 2011

Give your OBI EE Request the Stephen Few Treatment...

Stephen Few has a couple of great books on visual display of quantitative information. Use these principles when you're building your requests.

1. Take this...
From DR. OBI
2. Then turn it into this...
From DR. OBI

DB Functions 'Evaluate' and 'Evaluate Aggr' Bypass Cache

If super-fast performance using cache is your goal, the DB functions 'Evaluate' and 'Evaluate Aggr' will cause a request to bypass any OBI Server Cache. Look for an alternative that will populate your cache instead.

DR. OBI Open Letter Content Reminder

Dear Readers,

just a reminder of the ONLY content you'll find this blog:
  • useful tips for getting the most from OBI EE front-end components
  • descriptions are brief (you'll find a lot of wordy solutions out there!)
  • a working knowledge of OBI EE is anticipated or
  • at heart a desire to get more from your implementation
  • references to fellow bloggers and colleagues highlight (in my opinion) good quality technical solutions or approaches
If you find the solutions helpful, I'm glad. To the best of my knowledge, blog posts do not repeat content found on other blogs!

All the best,
DR. OBI

    Tuesday, February 8, 2011

    Theory: Single Dashboard Prompt, Multiple Subject Areas

    Frequently the requirment pops up to provide results from more than one subject area, using a single dashboard prompt.
    From DR. OBI
    OBI EE doesn't handle this situation directly, so the 'mid-request' concept can be used.
    From DR. OBI
    The steps briefly are...
    1. Create dashboard prompt using subject area 1, including required columns.
    2. Create a 2nd (mid) request listing columns and data returned from the prompt in Step 1.
    3. Filter columns using 'Is Prompted' option. 
    4. Create the 3rd and 4th requests, from subject areas 1 and 2 respectively, then make sure these requests are based on the results of the request in Step 2.
     A worked example in a future post...

    Thursday, December 16, 2010

    Wednesday, December 15, 2010

    OBI EE Usage Tracking - Part 4

    In a later post we'll extend the request used in Parts 1-3, to highlight performance for individual users. Continuing the license review theme, let's clarify overall exposure.

    Set this up from the beginning and a business can witness the growing number of licenses used.

    1. A saved filter for the definition of 'Active Users' can be changed without affecting dependent requests, so using the Part 2 definition:

        (TIMESTAMPDIFF(SQL_TSI_DAY, MAX("Query Time"."Date"), Current_TimeStamp)) 
     
    a filter will look similar to this...
    From DR. OBI
    2. So, we can count active users now at any time, but inform your Usage data a little more making the report more informative with:
    • Total Available Licenses
    • Remaining Available Licenses (Total Available - # Active Users)
      3. Add these to your request and always know your license exposure, similar to the one here...
      From DR. OBI
      4. Alternate text is added for context using HTML markup for the column:

          <HTML TITLE="# of Active Users"># of Named Users</HTML>

      Add your total number of licenses using a repository variable, database table updated via writeback or other convenient method of your choosing.

      Keen-eyed readers will see I'm using the SampleApp available from Oracle. Usage Tracking is available in the RPD supplied in this bundle, just follow the other steps to setup the required tables.

      Wednesday, November 24, 2010

      OBI EE Usage Tracking - Part 3

      Part 2 explored active users at quarterly license reviews. Tightening up the request a bit more, are individual users normally active on an annualized basis? Is the average days between visits <=90?

      1. Normally Active: 365/COUNT(DISTINCT "Query Time"."Date")
      2. Again, add some conditional formatting:
      • <=90 - Green Tick
      • >90 - Red Cross
      3. Thinking about your user activity, what you want to know when might be important. Column order improves readability of the information here...
      • Active Now
      • Normally Active
      • Active @ License Review Date
      4. The request from Parts 1 and 2 could look a bit like this...
      From DR. OBI