Supported Platforms

EPM Automate can be installed on virtual machines and Oracle Integration Cloud (OIC) machines that can access external hosts over a secure HTTP connection.


  • EPM Automate may be used only on 64-bit operating systems that are currently supported by the operating system vendor.
  • EPM Automate does not work with SOCKS proxy; it works only with HTTP/HTTPS proxy.
  • EPM Automate supports Basic, Digest, Kerberos, Negotiate, and NTLM authentication mechanisms to connect to the proxy server.
  • EPM Automate can connect to Oracle Enterprise Performance Management Cloud through API Gateways, such as Google APIGEE, IBM Data Power, and other reverse proxy servers.

    For this to work, configure the gateway or reverse proxy by setting the target as the URL of your EPM Cloud environment without any context such as /epmcloud. Example: Then, use the reverse proxy URL instead of the EPM Cloud URL in the login command. For configuration information, see the documentation of your gateway or proxy server.

    While configuring the proxy settings, be sure to pass the response code from EPM Cloud to EPM Automate without modifying it in any manner to allow EPM Automate to correctly process response codes such as 200,206, 400, 404, 500, 501, and so on. For example, for IBM Datapower, set proxy HTTP Response to ON. Additionally, the API gateway should allow HTTP methods (GET, POST, PUT, PATCH, and DELETE).

On Linux and UNIX computers, EPM Automate looks for the following environment variables to determine HTTP or HTTPS proxy settings:

  • proxyHost
  • proxyPort

Examples of http proxy settings:


export proxyPort=8000

Examples of https proxy settings:


export proxyPort=8080


EPM Automate can use the OAuth 2.0 authentication protocol to access OCI (Gen 2) EPM Cloud environments (if configured for OAuth) to execute commands, especially for automating the running of commands.

In Classic environments and those OCI (Gen 2) environments that use basic authentication, EPM Automate does not work with corporate SSO (identity provider) credentials. Because users cannot sign in using corporate credentials, the user accounts for accessing EPM Automate must be maintained in the identity domain. If your subscription is configured for SSO, you must also enable EPM Automate users to sign-in with their identity domain credentials. See Enabling Sign In With Identity Domain Credentials in Administering Oracle Cloud Identity Management.

Download Instructions: Downloading and Installing Clients in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators.