rpdUploadAndConfigure
- Chandresh Patel
Uploads the RPD to a target environment, then updates connection pool information using provided JSON file, which is done by invoking updateconnectionpool command. Property replacement is done on JSON file, which will allow you to update environment specific information in JSON file at update time. This operation is slightly different than rpdDeploy, as it uploads RPD file first as is and then performs connection pool update and is only supported for OBIEE 12c.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
| Oracle Middleware Home (MW_HOME) | FD_ORACLE_MW_HOME | Yes | The oracle middleware home (which has sub folders such as oracle_common, wlserver, coherence*, etc.) (e.g. /u01/oracle/products/fmw) |
| Oracle BI Home | FD_ORACLE_BI_HOME | No | The oracle BI home. (e.g. |
| OBIEE Server Host | FDOBIEE_SERVER_HOST | Yes | The managed server host name for OBIEE. |
OBIEE Server Port | FDOBIEE_SERVER_PORT | Yes | The managed server port number for OBIEE.(e.g. 9502 or 9704) |
| 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. |
| OBIEE RPD Name | FDOBIEE_RPD_NAME | Yes | The RPD name on the OBIEE server. (e.g. liverpd). Do not put .rpd extension on this value. |
| OBIEE RPD Password | FDOBIEE_RPD_PASSWORD | Yes | The RPD password on the OBIEE server. |
| OBIEE RPD Source Password | FDOBIEE_SOURCE_RPD_PASSWORD | No | The RPD password from the Source Environment. Used if the RPD password changes between environments. If source password is different than rpd password then password will be updated on rpd prior to upload. |
| WebLogic Domain Directory | FDWLS_DOMAIN_DIRECTORY | No | WebLogic Domain Directory.(e.g. /u01/oracle/config/domains/soa_domain) |
| WebLogic Admin Domain Directory | FDWLS_ADMIN_DOMAIN_DIRECTORY | No |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
| Connection Pool JSON File | FDOBIEE_INP_CONN_POOL_JSON_FILE | No | You can create connection pool JSON file using link, use Example for listconnectionpool cd /oracle/Middleware/Oracle_Home/user_projects/domains/bi01/bitools/bin ./datamodel.sh listConnectionpool -SI ssi -U weblogic -P welcome1 -V true -O /var/tmp/connectionpool.json FlexDeploy will perform property replacement on this file, so you can use ${{...}} notation to replace environment specific values. JSON 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
{
"Title": "List Connection Pools",
"Conn-Pool-Info": [
{
"uid": "215297b0-0c83-1000-8029-0a0a0b690000",
"connPool":"BSC",
"parentName":"\"BSC\"",
"user": "BSC",
"password": "${{FDBI_BSC_PASSWORD}}",
"dataSource":"VALUEOF(BSC_DSN)",
"appServerName":"''"
},
{
"uid": "80d01383-0bd5-0000-714b-e31d00000000",
"connPool":"HR",
"parentName":"\"HR\"",
"user": "HR",
"password": "${{FDBI_HR_PASSWORD}}",
"dataSource":"VALUEOF(FDBI_HR_DSN)",
"appServerName":"''"
}
],
"Variables-In-Conn-Pool": [
{
"uid": "23829710-0c83-1000-8029-0a0a0b690000",
"variable": "BI_EE_HOME",
"value": "'${{FD_ORACLE_BI_HOME}}'"
},
{
"uid": "80d01384-0bd5-0000-714b-e31d00000000",
"variable": "BSC_DSN",
"value": "'${{FDBI_BSC_DSN}}'"
},
{
"uid": "fc3b8480-0c61-1000-8421-0af052d90000",
"variable": "HR_DSN",
"value": "'${{FDBI_HR_DSN}}'"
}
]
}
|
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation consumes an archive file of the RPD artifact. This artifact can be created by the rpdBuild 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.
Related content
- style