Versions Compared

Key

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

Builds a deployment object artifact that contains any combination of WebCatalog objects OR the OBI Repository file(RPD).

All WebCatalog objects and the RPD are supported for both full and partial package-based deployments. If partial package-based deployment is used, for Oracle BI project type (Oracle Business Intelligence project type in pre-5.5.0.1) each of the WebCatalog files will be placed into one of the following buckets:types.

  • Folder

  • Analysis

  • Dashboards

    Dashboard

  • DashboardPrompts

    DashboardPrompt

  • DataModels

    DataModel

  • Filters

    Filter

  • Folders

    KPI

  • KPIs

    MetaData

    MetaData
  • Report

  • Reports

    StyleTemplate

  • StyleTemplates
  • RPD
  • Other Files

    Other

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

  1. WebCatalog

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

title Controlling
Info

Source

It is recommended to source the OBI objects from a "build" OBI environment rather than using a source control system; however, both methods are supported.

Control

  • Full deployment mode - objects are downloaded from a source OBI server.

  • Package-based deployment mode - objects can be sourced from either a source OBI server or SCM instance.

...

Target Properties

Property Name

Property Code

Required

Description

OBIEE Server Port

FDOBIEE_SERVER_PORT

Yes

The managed server port number for OBIEE.(e.g. 9502

...

 or 9704)

OBIEE Server Host

FDOBIEE_SERVER_HOST

Yes

The managed server host name for OBIEE.

OBIEE Server Use SSL

FDOBIEE_SERVER_USE_SSL

Yes

Check if the connection to the managed server should be made using t3s. Otherwise, it will be made using t3. Defaults to false.

OBIEE Server User

FDOBIEE_USER

Yes

The user to log into OBIEE. Should have sufficient privileges to move and upload data.

OBIEE Server Password

FDOBIEE_PASSWORD

Yes

The password for the user to login to OBIEE.

...

Oracle

...

Middleware

...

Home

...

(

...

MW_HOME)

FD_ORACLE_MW_HOME

Yes

The 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 Path

FDOBIEE_OBJECT_PATH

Yes

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.

OBIEE Analytics WSDL Path

FDOBIEE_ANALYTICS_WSDL_PATH

No

@since 6.0.0.8

The path to the analytics WSDL. We don’t recommend changing this option unless the OBIEE instance you are using has a different path to the analytics WSDL. Use at your own risk.

Default value - /analytics-ws/saw.dll/wsdl/v7

Inputs

Input Name

Input Code

Required

Description

Copy Object Permissions

FDOBIEE_INP_COPY_PERMISSIONS

Yes

Copy object with current permissions. If false, parent folder permissions in deploy environment will be used.

...

Keep Timestamps

FDOBIEE_INP_

...

PRESERVE_

...

Outputs

...

Output Name

...

Required

...

TIMESTAMPS

...

No

Export object with timestamp details.

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

...

package-based 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

...

Target. Selecting a specific resource will result in selection of endpoints associated to the

...

Target 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.