Configuring Oracle EPM Cloud Account
- Chandresh Patel
Before using EPM plugin operations, navigate to Topology → Integrations → Cloud, then create an account with provider OracleEPM for each one of your SaaS environments. This account will store the URL and credentials to make HTTPS requests to your SaaS environment. The account will be reusable by all Oracle EPM Plugin operations. All fields shown are required.
For non-basic authentication methods you can reference OIC OAuth Support for additional guidance as process will be almost identical except cloud account will be type OracleEPM.
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle EPM Auth Type |
| Yes | Authentication method for connecting to Oracle EPM. Additional properties may be required depending on basic authentication or OAuth. |
Oracle EPM URL |
| Yes | URL of the Oracle EPM environment. Typically, the URL of your Oracle Cloud service e.g. https://<SERVICE_NAME>-<TENANT_NAME>.<SERVICE_TYPE>.<dcX>.oraclecloud.com |
Oracle EPM Username |
| Yes |
|
Oracle EPM Password |
| Yes | The password for your Oracle environment. Required for basic authentication and OAuthResourceOwner. |
Oracle EPM Identity Base URI |
| No |
|
Oracle EPM Client Id |
| No | EPM Client Id when using. Required for OAuth. |
Oracle EPM Client Secret |
| No | EPM Client Secret Key. Required for OAuth. |
Oracle EPM Scope |
| No | EPM Client Scope. Required for OAuth. |
Oracle EPM Keystore Path |
| No | Java keystore path containing the private key to use for JWT User Assertion. |
Oracle EPM Keystore Password |
| No | Java keystore password for the FSM Keystore Path property. |
Oracle EPM Private Key Alias |
| No | Private Key alias. |
Oracle EPM Private Key Passphrase |
| No | Passphrase for the EPM Private Key Alias property. Leave blank if the private key passphrase matches the keystore password. |
Oracle EPM Certificate Algorithm |
| No | Algorithm used for the certificate. Defaults to RS256. |
Related content
- style