If enabled, WEB-INF\classes\META-INF\persistence.xml needs to be
Prev   Next

If enabled, WEB-INF\classes\META-INF\persistence.xml needs to be

properly configured.

outline.relational.cache.enabled=false

  1. Above and below the "outline.relational.cache.enabled" property, modify the set of properties matching the "cache." and "relational.cache." naming conventions. The only property that must be modified in addition to "outline.relational.cache.enabled" is the "outline.info.*" property, which must be added for each Essbase connection to be cached in the following form:

      ## This is a list of CACHED_OUTLINE_INFOS to add into the database on startup
  ## (if they don't already exist)
  ## The format is:
  ## outline.info.#=ID|APPLICATION|CUBE|SERVER|URL|USERNAME|PASSWORD
  ## (The number '#' should increase from 0)
  ## Example:
  ## outline.info.0=example.sample.basic|Sample|Basic|essbase11121|embedded|
     admin|password
outline.info.0=sample.basic|Sample|Basic|essprod01|embedded|admin|password
outline.info.1=demo.basic|Demo|Basic|essprod01|embedded|admin|password
  1. Navigate to the \WEB-INF\classes\META-INF directory and rename the file "persistence.xml_disabled" to "persistence.xml".
  2. Open the renamed \WEB-INF\classes\META-INF\persistence.xml file in a text editor and modify the "hibernate.connection.*" properties so that they match the properties used in the earlier-modified "hibernate.properties" file, located in the \staging\WEB-INF\classes subdirectory of your Dodeca Framework Installation. The instructions for determining the correct hibernate property values can be found at step 2. b. in the earlier section "Step-by-Step Instructions to Create the WAR File".
  3. If you have configured a database other than SQL Server, you must copy the relevant JDBC driver jars to the \WEB-INF\lib directory of the "dodeca-essbse.war" file.

Dodeca-Essbase WAR File Deployment

Next, you will need to deploy the Dodeca-Essbase servlet (dodeca-essbase.war) which you just modified. It should be deployed in the same manner as the dodeca.war file was earlier, according to the instructions provided for your application server.

For example, to deploy the WAR file in Apache Tomcat, simply copy the appropriate version of dodeca-essbase.war file to the \webapps directory of your Apache Tomcat deployment and start the application server. The dodeca-essbase WAR file will be unpacked and deployed into the webapps\dodeca-essbase directory.

Note

If you wish to deploy multiple versions of the Dodeca-Essbase servlet in order to allow Dodeca to connect to multiple versions of Essbase, you will need to give each servlet a unique filename, such as "dodeca-essbase-9.3.1.war" or "dodeca-essbase-11.1.2.war". This allows the application server to distinguish between servlets when a request is made by Dodeca. If you need any additional information, please contact Applied OLAP for support.

Prev   Next
Should only be used to increase performance at the cost of building the Home Completing the Setup - The Application Setup Utility