Versions Compared

Old Version 2

changes.mady.by.user Karl Henselin

Saved on

compared with

New Version Current

changes.mady.by.user Rajashekar.Gaddi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Oracle Business Intelligence plugin provides operations to manage the Web Catalog objects and RPD repository files within Oracle Business Intelligence Enterprise Edition (OBIEE) or Oracle Analytics Server (OAS).

Supported Versions

  • 11.1.1+ on Linux

  • 12c on Linux

Key Features

  • Supports both OBIEE and Oracle Analytics Server (OAS)

  • Source RPD and WebCatalog from SCM or Development environment.

  • Supports FlexDeploy Full as well as Partial Deployments for WebCatalog objects.

    • Package-Based deployment option allows users to select various objects for deployment. Change detection and reporting is done for each individual object.

  • Property replacement via configuration files for RPD and Datamodel.

  • Operations to support synching WebCatalog objects to a source code repository.

Info

Oracle BI Project Types

This plugin supports two models of management for Web Catalog objects, derived by the selected project type.

Oracle BI

This project type is equivalent to the pre-5.5.0.1 model and was previously named Oracle Business Intelligence.  The web catalog project files are populated into various object types, making it easier to filter by those types.

Oracle BI 2.0

This project type is new for 5.5.0.1 and matches the model introduced by the Oracle Transactional Business Intelligence (OTBI) support in 5.5.0.0.  The web catalog project files are populated into a single object type, called WebCatalog, making it easier to locate a set of files matching a file path or naming convention.  To identify the type of each file, the object name is artificially decorated with an extension matching the OBIEE object type.  For example, /shared/Sample Lite.Folder or /shared/Sample Lite/DailyReview.Report.

Both models are supported, with the only caveat being that you cannot change the project type of an existing project once the project files have been populated. Instead, you must create a new project.  While nothing will prevent you from changing the type on the project you will encounter unexpected behavior, and this is not a supported function.   

Plugin Operations Operations 

Child pages (Children Display)
first8

...

All files for the Oracle BI 2.0 project type are categorized into a single type:

  1. WebCatalog

Special Considerations

Child pages (Children Display)
pageAppendix-OBIEE

Working with Scorecard and Dashboard Sub-items

  • By default, we won't discover subitems for Dashboard and Scorecard Object types.but conditionally we can discover subitem only for OBIEE V2 Model projects only.

  • It is always recommended to build parent-level files for both dashboard and Scorecard Object types because these objects can contain dependent files that are in hidden mode. and they are necessary.

    • We have identified two types of hidden files within the Scorecard folder/Dashboad folder:

      • Some of them represent versions of the actual files (e.g., _Perspectives). these files are auto-generated when the scorecard is created.

      • Some of them are random numbers (e.g., 9817c0100ba6100085670ae4eb540000). Actually, these are SHORTCUT files created by the system when we use particular files in the scorecard.

      • These 2 file types are essential. Without them, archiving and unarchiving processes will succeed, but when you attempt to open the file, it will result in an error. And sometimes unarchive also fails.

      • in Dashboard we can see hidden files with name dashboard layout and these files are necessary.

  • if you want to work with subitems for these two types of Objects, use the project property(FDOBIEE_DISCOVER_SUB_ITEMS) to Discover sub-items. which enables the sub-items for the scorecard and Dashboard based on the selection and we can see them in the File catalog.

  • while working with subitems for the Scorecard and dashboard make sure to build a file along with dependent files

  • When you create a package with Scorecard or Dashboard, keep the parent file (root file) sequence as one, as shown below. When you are creating it for the first time in another environment, it is mandatory to create the parent folder first, followed by the subitems; therefore, a sequence is needed.

     

    Image Added

     

  • when you build files without a timestamp and deploy them we only see the Last Accessed Attribute only gets updated. If the Object has write permission and there is a change in the object then only the Last modified attribute gets updated. permission will play crucial role please check the following document