Deploys any combination of WebCatalog objects to the target OTBI environment. Objects will be deployed at the same path they were built from, e.g. if a report was built from /shared/Custom/Sample Lite/Reports, it will also be deployed to the same location on the target server.
Tip |
---|
Endpoint TipThis operation uses HTTP operations to communicate remotely to the OTBI server, and therefore, can be executed on any endpoint (including LOCALHOST). |
...
. |
...
Target Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
OTBI Server Host |
| Yes | The server host name for Oracle Transactional Business Intelligence. |
OTBI Server Port |
| Yes | The HTTP port number for Oracle Transactional Business Intelligence. Default is 443. |
OTBI Server User |
| Yes | The user to log into Oracle Transactional Business Intelligence. User must have BI Service Administrator role to archive catalog. |
OTBI Server Password |
| Yes | The password for the user to login to Oracle Transactional Business Intelligence. |
OTBI Server SSL Connection |
| Yes | Indicates whether to connect to OTBI server using SSL. Default is true. |
Project Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
OTBI WebCat Object Path |
| No | The WebCatalog path to import the objects of the build artifact into. The property is shared with the build operation and must not be changed between build and deployment execution. Note: In case of package deployments, the import path is considered from the package file path. |
Analytics WSDL Path |
| No | The path to the analytics WSDL. We don’t recommend changing this option unless the OTBI instance you are using has a different path to the analytics WSDL. |
...
Input Name | Input Code | Required | Description |
---|---|---|---|
Copy Object Permissions |
| Yes | Upload object with exported permissions. If false, parent folder permissions in deploy environment will be used. |
Overwrite Object |
| Yes | If object already exists in deployment environment, should it be overwritten with this one. |
Deploy Objects In Async Mode |
| Yes | For large sized objects deployment, it should be enabled to avoid timeout exception from OTBI. (Boolean) Default Value: checked Note: Unchecking this option will initiate deployment in synchronous mode, which might cause timeout for objects of size more than 4 MB.@since 6.0.0.8 When Default Value: true |
Async API Timeout |
| Yes | The maximum number of seconds to wait for unarchive process. Defaults to 1200 seconds (20 minutes). (Integer) Note: This option is only considered when the |
...