Builds a deployment object artifact that contains any combination of WebCatalog objects or the OBI Repository file(RPD).In full deployment mode, the artifacts are downloaded from a source OBI server. In Partial mode, they can be sourced from either an OBI server or SCM instance.
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:
WebCatalog
In the case of the RPD and DataModelsDatamodel, 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, see RPD Configuration File Setup and Datamodel OBI WebCatalog - DataModel Configuration File Setup. Note that if you want to provide a config file for both the RPD and DataModels and deploy both at the same time using partial deploy, the two configurations should reside in one common file which is specified on the obiDeploy input Config File.
| Info | |
|---|---|
Source | ControllingSource Controlling of OBI Objects and the RPD is supported as of 4.0.3. Control
|
...
|
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
OBIEE Server Port |
| Yes | The managed server port number for OBIEE.(e.g. |
...
or | |||
OBIEE Server Host |
| Yes | The managed server host name for OBIEE. |
OBIEE 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 |
| Yes | The user to log into OBIEE. Should have sufficient privileges to move and upload data. |
OBIEE Server Password |
| Yes | The password for the user to login to |
...
OBIEE |
...
. |
...
...
Oracle |
...
Required for OBI 11G. Not used in 12C.
...
Middleware |
...
Home |
...
Required for OBI 11G. Not used in 12C.
...
( |
...
Required for OBI 11G. Not used in 12C.
The oracle BI instance home.(e.g. /oracle/Middleware/Oracle_Home/instances/FDBI01)
...
MW_HOME) |
|
...
Yes | The oracle middleware home (which has subfolders such as oracle_common, wlserver, coherence*, etc |
...
. |
...
) |
...
(e.g. |
...
) |
...
...
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
OBIEE WebCat 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 |
| 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 |
| Yes | Copy object with current permissions. If false, parent folder permissions in deploy environment will be used. |
...
Keep Timestamps |
|
...
|
...
Outputs
...
Output Name
...
Required
...
Description
|
...
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.