1. Installation and Configuration Guide
  2. Configuring EPM System Products in a New Deployment
  3. EPM System Configurator Task Reference
  4. Deploy to Application Server: Oracle WebLogic
  5. What Happens During Deployment: WebLogic Server

What Happens During Deployment: WebLogic Server

Deployment notes:

  • Essbase has its own WebLogic Administration Server and is deployed under a separate WebLogic Domain. The login credentials for WebLogic Administration are identical to those of the EPM WebLogic Administration Server.

  • EPM System Configurator deploys each application to the Oracle WebLogic Server domain you specified. For a new domain, the domain is created when the first application is deployed. Each application runs in a separate JVM, except for Oracle Hyperion Shared Services and Oracle Hyperion Enterprise Performance Management Workspace, which run together and are deployed to the same managed server, or if you deploy multiple Java web applications to a single managed server.

  • EPM System Configurator deploys the applications to MIDDLEWARE_HOME/user_projects/domains/domainName.

  • EPM System Configurator deploys Oracle Enterprise Manager automatically when it deploys the first Java web application.

  • Start and stop scripts are created in /bin/.

  • For each application, in /bin/deploymentScripts there is a setCustomParamsProduct.bat file (.sh extension for Linux), where you can change JAVA_OPTIONS when using start scripts.

  • EPM System Configurator creates a cluster for each managed server.