Deploys the RPD to a target environment and replaces connection pool and password information as needed.
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 RPD Configuration File.
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.|
|OBIEE RPD Name|
|Yes||The RPD name on the OBIEE server. (e.g. |
|OBIEE RPD Password|
|Yes||The RPD password on the OBIEE server.|
|Oracle Middleware Home (MW_HOME)|
|Yes||The oracle middleware home (which has subfolders such as oracle_common, wlserver, coherence*, etc.) (e.g. |
|Oracle BI Home|
Required for OBI 11G. Not used in 12C.
The oracle BI home. (e.g.
|Weblogic Domain Directory|
|11G||Weblogic Domain Directory.(e.g. |
|Weblogic Admin Listen Port|
|11G||The admin server port, (e.g. |
7001) Not used in 12C.
|11G||The admin server host address, (e.g. |
localhost) Not used in 12C.
|11G||Check if the WLST connection to the admin server should be made using t3s. otherwise it will be made using t3|
Config file name for RPD 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 RPD Configuration File for details.
This operation consumes an archive file of the RPD artifact. This artifact can be created by the rpdBuild 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.