Tuesday, April 30, 2013

[OBIEE 11g] How To Access The Files From Other Drive Or Network





How to access the files from other drive or network in OBIEE?



To call any file/videos in OBIEE11g we will follow below steps:


Step1: Copy all files /videos in the below paths. Here Videos is my folder name which stores all my files/videos.


C:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\Videos

C:\OBIEE11G\Oracle_BI1\bifoundation\web\app\res\Videos



Step2: Once we are done with the above step, need to restart the services and access the files/videos using

http://localhost:9704/analytics/res/Videos/filename.


Filename: Name of the files/videos which is stored in Videos folder which we created.


The above steps are well known to us, but there is one disadvantage on using the above method.



Disadvantage :-  All the files/video need to store in the OBIEE server, where if we have thousands of files then it will be the problem. Because on storing thousands of files will make server down, as these files may take more memory.


To achieve the above disadvantage we need to store all the files in other drive/network other than OBIEE server.




How to access the files from other drive or network in OBIEE?



Step1 :   Navigate to C:\OBIEE11G\Oracle_BI1\bifoundation\jee  path and open analytics.ear file.


Step2 :  On opening ear file we can see analytics.war file, open this war file.


Step3 : Now click on  WEB-INF folder and open weblogic.xml file.


Place the below code before </weblogic-web-app> tag.

<virtual-directory-mapping>

<local-path>N:/</local-path>                                <url-pattern>/Videos/*</url-pattern>

<url-pattern>*.jpeg</url-pattern>

</virtual-directory-mapping>



Step4 : Restart the services, now we can access the jpeg images which were stored N drive with folder name Videos using the below url





Tuesday, April 9, 2013

[OBIEE 11g] Task Performed By Oracle Fusion Middleware (EM)






Task Performed by Oracle Fusion Middleware (EM) in OBIEE 11g




 

Fusion Middleware Control:

The version 11g permits now to change some configuration with FMW control > Farm_Bi_Foundation > Business Intelligence > Coreapplication.


The Fusion Middleware Control console is used to monitor and start/stop various OBI components. It is located on the application server at http://localhost:7001/em. Much of the configuration of OBI that used to be done in the NQSConfig.ini files can now be done using this front end console, which in turns updates the NQSConfig.ini file. Things in the NQSConfig.ini file that are set by EM are noted in the file with '# This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager'. However some sections still need to be setup manually in the NQSConfig.ini file are:




 UsageTracking
 DynamicLibraries

 QueryOptimizationFlags
 MDXMemberNameCacheSection(SAPBW)

 More specific General Settings where EM doesn't contain the level of detail required



The Fusion Middleware Control EM console has five tabs to manage the application. From the domain tree, expand Business Intelligence and click coreapplication as shown below.



Overview:
This view shows system status, and allows you to start/stop/restart BI Components. The other tabs allow you to further configure the application.






CapacityManagement:


Thisviewhasfourtabs:


-Metrics: This gives metrics on request response time, load and query errors. You once might have looked at Usage Tracking for this information.

-Availability: Shows current availability of all components, allowing you to start/stop them. Also includes 'Point of Failure' analysis which shows areas in the infrastructure likely to fail when a hardware/software failure occurs.








-Scalability: This tab lets you enable Vertical Clustering, increasing the amount of instances of OBI on a server.

-Performance: Used for cache management, including settings that would have been set in NQSConfig.ini in 10g. It manages user query response time and max rows returned settings that were set in InstanceConfig.xml.



Diagnostics:
This view has 2 tabs. One for server log messages and the other for log file settings. These used to be kept in the RPD and the NQSServer.log.









Security:
This view allows you to enable SSO. Also links to Weblogic Admin Console Security realm to manage Weblogic security.








Deployment:

This section is for managing the deployment of various aspects of OBI 11G.

-Presentation: Contains a few settings for Dashboard and Analysis defaults. These used to be managed on a less global scale through Manage Privileges.

-Repository: This is where the RPD and Presentation Services are managed, and shared between servers for horizontal clustering. 





-Scheduler: Schema connection information for the scheduler tables

-Marketing: For Siebel Marketing connection

-Mail: Scheduler mail server connection information