Deploys any combination of WebCatalog objects to the target OBIEE environment. Objects will be deployed at the same path they were built from, e.g. if a report was built from /shared/Sample Lite/Reports, it will also be deployed to the same location on the target server.
In case of DataModel, property replacement on data sources will occur if the
Config File Input is specified. For more information on Property Replacement for OBIEE, see OBI WebCatalog - DataModel Configuration File.
When deploying to 12C, it may not be necessary to specify the replacement values as OBI 12c takes care of the replacement for you in the target environment. If deploying to a new environment, it would be helpful. If your changes don't seem to be working in 12C, verify that the override files contain the correct data. They will override the values that FlexDeploy uses.
OBIEE Server Port
|Yes||The managed server port number for OBIEE.(e.g. |
|OBIEE Server Host|
|Yes||The managed server host name for OBIEE.|
|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 Middleware Home (MW_HOME)|
|Yes||The Oracle Middleware Home (which has subfolders such as oracle_common, wlserver, coherence*, etc.) (e.g. |
|Weblogic Domain Directory|
|Yes||Weblogic Domain Directory.(e.g. |
|OBIEE WebCat Object Path|
The WebCatalog path to be exported. Separate folders with a forward slash (/).
The value must be the same during the build and deploy, so if it is desired to change the value, please perform a new build.
Copy Object Permissions
|Yes||Upload object with exported permissions. If false, parent folder permissions in deploy environment will be used.|
|Yes||If object already exists in deployment environment, should it be overwritten with this one.|
Config file name for DataModel property replacement. Config file can be absolute path or relative to artifacts folder. If you are using config file from temp folder, then use FD_TEMP_DIR variable to indicate absolute path (using groovy expression for input).
You can either
- Save config file during build operation as artifact, or
- Extract it from SCM during deploy workflow or
- Use absolute path to location on server. (not recommended as it requires manual setup on server)
See OBI WebCatalog - DataModel Configuration File for details.
This operation consumes the artifacts produced from the obiBuild operation.
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.
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.