Tag Archives: OBIEE 11g

The Importance of BI Documentation

Why Is BI Documentation Important?

Business intelligence systems come with a lot of extra information. Even beautifully constructed analyses have piles of background information and histories. Administrators might often have memos and updates that they’d like share with analysts. Sales figures might have anomalies that need further explanation. But OBIEE does not currently have any options for BI Documentation inside the dashboard.

Let’s say a BI user for a cell phone distribution company is viewing a report comparing the yearly sales figures for several different cell phones. If the analyst notices that one specific cell phone is outperforming the others, but doesn’t know what makes that specific model unique, then they have to go searching for that information.


But what if the individual phone model specifications and advertising and marketing histories were already included as reports inside the dashboard? What if the analyst, with only a couple of clicks, discovered that the reason one cell phone was outperforming the others was due to its next-gen screen, camera, and chip upgrades, which proved popular with consumers? Or what if the analyst discovered that the popular phone, while containing outdated peripherals, was selling so well because a Q3 advertising push for that model only? All of this information might not be contained in the dashboard’s visuals, but greatly affects the analysts’ understanding of the reports.

Current Options for OBIEE Documentation

Some information can be displayed as visuals, but many times this isn’t a practical solution. Besides making dashboards too cluttered, memos, product descriptions, company directories, etc., are not practical as charts and graphs. As of right now, important documentation can be stored in a wide range of places outside of the BI dashboard, but the operating reality at most organizations means that important information is spread across several locations and not always accessible to the people who need it.


Workarounds are inefficient, cost time, cause BI users to leave the BI environment (potentially reducing usage), and increase frustration. If an analyst has to email several different people to locate the information she wants, that complicates her workflow and produces extraneous communications (who likes answering emails?). Before now, there wasn’t an easy solution to these problems.

ChitChat’s BI Documentation Features

With ChitChat, it’s now possible to store critical documentation where it belongs—at the source of the conversation. Keep phone directories, memos from administrators (or requests from analysts to administrators), product descriptions, analytical histories—really, the possibilities are endless—inside the dashboard where they are accessible to the people who need them. Shorten workflows and make life easier for your BI users.

ChitChat’s easy-to-use functionality allows BI users to copy and paste or write (ChitChat has a built-in WYSIWYG text editor) important information inside the BI dashboard, creating a quicker path to insightful and actionable analytics. And isn’t that the goal in the end?

To learn more about ChitChat’s many commentary features, or to request a demo, click here.

The post The Importance of BI Documentation appeared first on Rittman Mead Consulting.

Deploy the OBIEE AnalyticsRes Folder on a WebLogic Server

Since Oracle BI 11g was released it has sought as to use the /analyticsRes folder of the default OBIEE 11g implementation to store media and programmatic scripting files as a best practice. Although you could create a different folder named arbitrarily, containing a WEB-INF folder with web.xml file to denote it is a JEE deployable […]

The post Deploy the OBIEE AnalyticsRes Folder on a WebLogic Server appeared first on Art of Business Intelligence Blog.

OBIEE en JDev in the same FWM home

Don't do it, it screws up your OBIEE weblogic instance.........

(especially when you are preparing for the Brighton 2012 BI congress.......)

8-(

Till Next Time

OBIEE install avoid RTD license problems

If you are not going to use RTD (Real Time Decisions) uncheck the box during installation:

image

This avoids extremely difficult discussions with Oracle over the license fee.

Till Next Time

OBIEE 11116 repository on MS-SQL I

We had to do a POC on some MS-SQL data. Instead of bringing an extra Oracle DB we used an existing MS-SQL instance.

1. Create a repository database:

We called ours “Repositories” Winking smile

image

2. Enable case-sensitive collation

ALTER DATABASE Repositories COLLATE Latin1_General_CS_AS

3. Enable Row versioning

ALTER DATABASE Repositories SET READ_COMMITTED_SNAPSHOT ON

 

4. Allow TCP/IP access to the database:

image

(Bounce the service if you changed it!)

4b. If you have a firewall running check if the ms-sql port is open (1433 for a default instance)

5. Create a user (fi: REP_OWN)

image

6. make  the default database repositories:

image

7. Set the public and sysadmin role:

image

Now we can start with the actual repository:

8. Download and unzip de RCU.

9. Start the RCU.bat (..\rcuHome\BIN)

10. On the database connection details page:

image

11. Select the BI components:

image

12. Enter the passwords

image

13. Succes:

image

image

14. You can disable the REP_OWN account, the RCU has create dedicated logins:

image

Till Next Time