obiBuild

Builds a deployment artifact that contains WebCatalog objects.

All WebCatalog objects are supported for both full and partial deployments. If partial deployment is used, each of the WebCatalog files will be placed into one of the following types.

  • Folder
  • Analysis
  • Dashboard
  • DashboardPrompt
  • DataModel
  • Filter
  • KPI
  • MetaData
  • Report
  • StyleTemplate
  • Other

In the case of the Datamodel, property replacement on variables and connection pool information is supported via a configuration file that should reside in an SCM repository. For more information on Property Replacement for OBIEE, see OBI WebCataloag - DataModel Configuration File.

Source Control

  • Full deployment mode - objects are downloaded from a source OBI server.
  • Partial deployment mode - objects can be sourced from either a source OBI server or SCM instance.

Environment/Instance Properties

Property Name

Property Code

Required

Description

OBIEE Server Port

FDOBIEE_SERVER_PORTYesThe managed server port number for OBIEE.(e.g. 9502 or 9704)
OBIEE Server HostFDOBIEE_SERVER_HOSTYesThe managed server host name for OBIEE.
OBIEE Server UserFDOBIEE_USERYesThe user to log into OBIEE. Should have sufficient privileges to move and upload data.
OBIEE Server PasswordFDOBIEE_PASSWORDYesThe password for the user to login to OBIEE.
Oracle Middleware Home (MW_HOME)FD_ORACLE_MW_HOMEYesThe oracle middleware home (which has subfolders such as oracle_common, wlserver, coherence*, etc.) (e.g. /u01/oracle/products/fmw)

Project Properties

Property Name

Property Code

Required

Description

OBIEE WebCat Object PathFDOBIEE_OBJECT_PATHYes

The WebCatalog path to be recursively exported. Separate folders with a forward slash (/).

The value must be the same during the build and deploy, so after changing the value, please do not deploy any old builds.

You probably want to set it to "/shared" or "/system" if you are populating the web catalog.

Inputs

Input Name

Input Code

Required

Description

Copy Object Permissions

FDOBIEE_INP_COPY_PERMISSIONSYesCopy object with current permissions. If false, parent folder permissions in deploy environment will be used.
Recursive WebCat Object BuildFDOBIEE_INP_RECURSIVE_CAT_BUILDYes

Boolean to indicate if a recursive build should be performed for web catalog objects.  If false, no objects under the catalog path will be exported. This will only be set to false in rare circumstances. Even if you only wish to export a single WebCatalog object, chances are that object has other data underneath it, that are required for the object to run, that would justify a recursive export.

BI plugin was updated in release 5.0.0.1 significantly where recursive option was used for full deployment projects by default and for partial deployment projects as each individual objects in archived, recursive option is defaulted to false. This input was not used and is removed with 5.1.0.3 for clarity.

Outputs

Output Name

Required

Description




Artifacts

This operation produces an archive file of the object specified in the OBIEE WebCatalog Object Path if the project is configured for full deployments.  If the project is configured for partial deployments, then the artifact will be a zipped directory containing the archive files for each built object. The zip/archive files are suitable for the deploy operation.

Endpoint Selection

This operation delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the environment instance. Selecting a specific resource will result in selection of endpoints associated to the environment instance which have that resource defined.

Endpoint Execution

This operation delegates endpoint execution to the workflow developer. The workflow editor will default to "Any", which will execute on any one of the selected endpoints, which will be randomly picked from selected endpoints or a specific endpoint where previous step may have executed. Changing this value to "All" to will result in execution on all selected endpoints.

The following macros are not currently supported in the footer:
  • style