all bits considered data to information to knowledge

27Dec/117

Getting started with Oracle BI: a virtual experience – Part VI

(continued from Part V)

Step 10

You are ready to access OBIEE web interface. Launch Firefox browser either from desktop icon, or from the top toolbar; its home page is set  to the Oracle Business Intelligence login page (http://localhost:7001/analytics/saw.dll?bieehome&startPage=1)

Note that several bookmarks are set up (see Fig. 1):

  • OBIEE  (http://localhost:7001/analytics)
  • WLS Console (http://localhost:7001/console)
  • Enterprise Manager (EM) (http://localhost:7001/em)
  • BI Composer (http://localhost:7001/analytics/bicomposer/faces/answersWizard.jspx)

NB: I was unable to launch BI Composer, ether due to configuration problems and/or Essbase services not running

Log into OBIEE (case sensitive)

User ID: Prodney        Password: Admin123

This will sign you in as “Paulo Rodney”; other user ID(s) and passwords are set up within the system; the document seems to imply that  BISAMPLE/BISAMPLE credentials pair is set up on the system - it does not work

OBIEE opens on General Index page which is packed with links to all the capabilities built into the application.

The following users are set up in the system:

 

Here is an example of a BI dashboard demo - one of the few supplied in this SampleApp_107 virtual machine

To log onto WebLogic Server console (WLS), click WLS console bookmark in the browser.

User Name: weblogic
Password: Admin123

Note: the same user id and password are used to log in onto Enterprise Management (EM) console

Here is an example of the WLS administrative console

You can access Oracle Enterprise Manager (EM) in the same way; with the same user ID and password.

User Name: weblogic
Password: Admin123

 

And here's a sample of the EM administrative console

 

That's all. Hope this will spare you a few moments of aggrawation 🙂 Comments and suggestions are always welcome.

Feel free to explore the applications on your own; you can also shut down system by killing off the VM environment - or you could do it in an orderly fashion using Oracle's provided scripts (see comments below)