Configuring for Displaying and Processing Data in Views - OBIEE 11G

Manually Configuring Cube Settings for Pivot Tables and Graphs :

To manually edit the Cube settings:

1. Open the instanceconfig.xml file for editing
2. Locate the Cube section, in which you must add the following elements:
   
   • CubeMaxRecords — Specifies the maximum number of records that are returned by an analysis for the view to process. This roughly governs the maximum number of cells that can be populated in a view; unpopulated cells in a sparse view do not count. The default is 40000.
   • CubeMaxPopulatedCells — Specifies the maximum number of cells in a view that can be populated with data from the Oracle BI Server. The default is 120000.
3. Include the elements and their ancestor elements as appropriate, as shown in the following example:
   

   <ServerInstance>
     <Views>
       <Cube>
         <CubeMaxRecords>30000</CubeMaxRecords>
         <CubeMaxPopulatedCells>120000</CubeMaxPopulatedCells>
       </Cube>
     </Views>
   </ServerInstance>
   

4. Save your changes and close the file.
5. Restart Oracle Business Intelligence.
   
   
   Manually Configuring Settings for Data in Views:
   
   
   
   1. Open the instanceconfig.xml file for editing
   2. Locate the Table, Pivot, and Charts parent sections, in which you must add the elements.
   3. Include the elements and their ancestor elements as appropriate, as shown in the following example.
      

      <ServerInstance>
        <Views>
            <Table>
              <MaxVisiblePages>1000</MaxVisiblePages>
              <MaxVisibleRows>500</MaxVisibleRows>
              <MaxVisibleSections>25</MaxVisibleSections>
              <DefaultRowsDisplayed>30</DefaultRowsDisplayed>
            </Table>
            <Pivot>
              <MaxVisibleColumns>300</MaxVisibleColumns>
              <MaxVisiblePages>1000</MaxVisiblePages>
              <MaxVisibleRows>500</MaxVisibleRows>
              <MaxVisibleSections>25</MaxVisibleSections>
              <DefaultRowsDisplayed>30</DefaultRowsDisplayed>
            </Pivot>
            <Charts>
              <MaxVisibleColumns>2000</MaxVisibleColumns>
              <MaxVisiblePages>1000</MaxVisiblePages>
              <MaxVisibleRows>2000</MaxVisibleRows>
              <MaxVisibleSections>25</MaxVisibleSections>
              <JavaHostReadLimitInKB>4096</JavaHostReadLimitInKB>
            </Charts>
        </Views>
      </ServerInstance>
      

      Note that this example does not include parameters that might exist in the file, but that are centrally managed by Fusion Middleware Control and cannot be changed manually.
   4. Save your changes and close the file.
   5. Restart Oracle Business Intelligence.
      
      
      

      Manually Configuring for Graphs and Gauges:

      
      
      1. Open the instanceconfig.xml file for editing
      2. Search for the Charts sections, in which you must add the elements.
      3. Include the elements and their ancestor elements as appropriate, as shown in the following example:
         

         <ServerInstance>
           <Views>
             <Charts>
              <EmbedFonts>True</EmbedFonts>
              <SectionSliderDefault>5</SectionSliderDefault>
              <SectionSliderLimit>10</SectionSliderLimit>
              <DefaultImageType>png</DefaultImageType>
              <FlashCodeBase>\\CORPORATE\Download\Flash</FlashCodeBase>
              <FlashCLSID>E38CDB6E-BA6D-21CF-96B8-432553540000</FlashCLSID>
             </Charts>
           </Views>
         </ServerInstance>
         

      4. Save your changes and close the file.
      5. Restart Oracle Business Intelligence.
         
         

         where

         
         

         FlashCodeBase	Specifies the name of the source for downloading the Flash plug-in. The default download source for the Flash plug-in is the vendor's Web site. In some organizations, users are instructed to download the latest Flash software from a corporate location instead of the vendor's Web site. You can modify the setting to point to another location that holds the Flash code base. Then, when users view a graph and a newer version of the Flash software is available on the corporate server, they can be prompted to download the newer version.	vendor's Web site
         FlashCLSID	Specifies a custom global identifier (clsid) property for downloading Flash. After modifying the Flash download directory using the FlashCodeBase element, you can enable a download prompt by creating a new classID for the Flash ActiveX control to add a custom global identifier property. You can obtain the current global identifier property from any computer where Oracle BI Presentation Services graphing is being used. (The global identifier property used by Oracle Business Intelligence is D27CDB6E-AE6D-11CF-96B8-444553540000.) The custom global identifier property must contain the same number of characters and dashes as the global identifier used in the default Flash ActiveX control. You should test flash graphs independent of Oracle Business Intelligence to ensure that they function with the custom global identifier property.	NA

         
         Reference : http://download.oracle.com/docs/cd/E14571_01/bi.1111/e10541/answersconfigset.htm