Analytic Workspace Manager for Oracle OLAP 11.2.0.3.0
Installation Notes
Analytic Workspace Manager Version 11.2.0.3.0
System Requirements
This installation contains the client-side files required to run Analytic Workspace Manager 11.2.0.3.0. This release is intended for Windows Vista, XP, 2000, Server 2003, and Linux. It requires, at a minimum, a connection to Oracle OLAP 11.1.0.6.0 production software or later. In addition, the Oracle Database must be in 11.1 compatibility mode or later. To take advantage of all the new features found in Analytic Workspace Manager 11.2.0.3.0, the Oracle Database 11.2.0.3.0 server release must be installed and the Oracle Database must be in 11.2 compatibility mode.
Major New Features
Analytic Workspace Manager in Release 11.2.0.3.0 provides the following new features:
- Ability to select multiple objects (Dimensions, Levels, Attributes, Hierarchies, Cubes, Measures, Calculated Measures) in the Navigation tree and delete them in one transaction.
- Ability to create a Data Security Policy using an OLAP DML Expression
Please refer to the Oracle OLAP User's Guide 11g Release 2 (E10627-01) and Analytic Workspace Manager Help for further details.
Release Components
The following files are contained in this download:
- readme_112030.html
- awm11.2.0.3.0.jar
- awm.bat
- awmd.bat
- awmrun.sh
- awm.properties
- awm.ico
- datavplugin.jar
- obieeplugin.jar
- E18648_01 - OBIEE Plug-in for Analytic Workspace Manager Users's Guide for OBIEE 10g.pdf
- E20237_01 - OBIEE Plug-in for Analytic Workspace Manager Users's Guide for OBIEE 11g.pdf
- E18663_01 - Data Validation Plug-in for Analytic Workspace Manager Users's Guide.pdf
- Create_sample_tables.sql
- Reset_tables.sql
- Dim_validation.xml
- Review Guide for Data Validation Plug-in.pdf
Analytic Workspace Manager application Plug-ins
This release of Analytic Workspace Manager includes two application plug-ins:
- The Oracle Business Intelligence Enterprise Edition (OBIEE) Plug-in for Analytic Workspace Manager (obieeplugin.jar) lets you quickly create an OBIEE 10g or 11g repository that enables the
OBIEE Server (and therefore any OBIEE client, including Dashboards, Answers, Delivers, and the MS Office Plug-in) to query Oracle Database 11g OLAP cubes.
- The Data Validation Plug-in for Analytic Workspace Manager (datavplugin.jar) provides tests to quickly find conditions in dimension table data that might cause errors when
maintaining an OLAP dimension or cause problems when querying a cube using business intelligence tools. The data validation plug-in also includes methods that can quickly fix many
different types of data errors in dimension tables. Please refer to the Review Guide for Data Validation Plug-in.pdf for a tutorial on the use of the Data Validation Plug-in.
Please refer to the documentation of each application plug-in for a description of each tool and the Oracle support policy for these plug-ins.
How To Install
Windows Environment Install Options:
To install the Analytic Workspace Manager 11.2.0.3.0 release as a standalone executable jar file, extract the contents of the PRODUCTION-11.2.0.3.0-AWM.zip file and then follow
the instructions for a either a new installation of Analytic Workspace Manager or the instructions for upgrading Analytic Workspace Manager from a previous release.
New installation of Analytic Workspace Manager 11.2.0.3.0
- If you are installing Analytic Workspace Manager for the first time, copy the extracted files into a new directory.
- Make sure your environment has at least JRE version 1.5 (Java Runtime Environment) installed. JRE version 1.6 is also supported. This is required to be able to run Analytic Workspace Manager as a single jar file.
- Update the awm.bat file included in the kit with the directory path of the version of the Java Runtime Environment installed in your environment and then execute this file to start Analytic Workspace Manager.
Additionally, you may start the awm11.2.0.3.0.jar file by executing the jar file or by running the jar file from a command line as follows:
start javaw mx1024m -jar awm11.2.0.3.0.jar
Upgrading to Analytic Workspace Manager 11.2.0.3.0 from a previous release
- If you are upgrading to Analytic Workspace Manager from a prior release, choose one of the following two options for handling the upgrade:
Option 1: First, create a backup copy of the installation directory for your previous release of AwM. Copy the location of the directory and all subdirectories of the installed version of AWM to a backup directory. Second, delete the prior version of AWM by removing the awm11.x.x.x.x.jar file (where x.x.x.x. is the release, e.g. 11.2.0.2) from the existing installation directory. Lastly, install the new version of AWM, by copying the awm11.2.0.3.0.jar file, extracted from the PRODUCTION-11.2.0.3.0-AWM.zip, to this installation directory.
Option 2: First, follow the instructions for a new installation of Analytic Workspace Manager 11.2.0.3.0, as documented above. Secondly, you will need to copy any user-written plugins or XML templates from the previous version of AWM to the new directories where you have installed the new version of AWM. Third, you should copy from the previous version of AWM, the awm.properties file which stores the AWM preferences settings and the awmdb.properties file which stores database connection settings, to the directories where you have installed the new version of AWM. This will ensure that any previous configuration settings will be migrated to the new installation of AWM.
- Make sure your environment has at least JRE version 1.5 (Java Runtime Environment) installed. JRE version 1.6 is also supported. This is required to be able to run Analytic Workspace Manager as a single jar file.
- Update the awm.bat file included in the kit with the directory path of the version of the Java Runtime Environment installed in your environment and then execute this file to start Analytic Workspace Manager.
Additionally, you may start the awm11.2.0.3.0.jar file by executing the jar file or by running the jar file from a command line as follows:
start javaw mx1024m -jar awm11.2.0.3.0.jar
- After starting AWM for the first time, you should verify that the preference settings for directories in the AWM configuration are set properly for the new version of AWM. Select the Configuration option item from the Tools menu in AWM to adjust these settings. The preference settings to check are:
General Template directory
Logging Session Logging Directory Location
Plugin Plugin directory
Linux Environment Install Options:
To install the Analytic Workspace Manager 11.2.0.3.0 release as a standalone executable jar file, extract the contents of the PRODUCTION-11.2.0.3.0-AWM.zip file and then follow
the instructions for a either a new installation of Analytic Workspace Manager or the instructions for upgrading Analytic Workspace Manager from a previous release.
New installation of Analytic Workspace Manager 11.2.0.3.0
- If you are installing Analytic Workspace Manager for the first time, copy the extracted files into a new directory.
- Make sure your environment has at least JRE version 1.5 (Java Runtime Environment) installed. JRE version 1.6 is also supported. This is required to be able to run Analytic Workspace Manager as a single jar file.
- Update the awmrun.sh file included in the kit with the directory path of the version of the Java Runtime Environment installed in your environment and then execute this file to start Analytic Workspace Manager.
Additionally, you may start the awm11.2.0.3.0.jar file by running the jar file from a command line as follows:
java mx1024m -jar awm11.2.0.3.0.jar
Upgrading to Analytic Workspace Manager 11.2.0.3.0 from a previous release
- If you are upgrading to Analytic Workspace Manager from a prior release, choose one of the following two options for handling the upgrade:
Option 1: First, create a backup copy of the installation directory for your previous release of AwM. Copy the location of the directory and all subdirectories of the installed version of AWM to a backup directory. Second, delete the prior version of AWM by removing the awm11.x.x.x.x.jar file (where x.x.x.x. is the release, e.g. 11.2.0.2) from the existing installation directory. Lastly, install the new version of AWM, by copying the awm11.2.0.3.0.jar file, extracted from the PRODUCTION-11.2.0.3.0-AWM.zip, to this installation directory.
Option 2: First, follow the instructions for a new installation of Analytic Workspace Manager 11.2.0.3.0, as documented above. Secondly, you will need to copy any user-written plugins or XML templates from the previous version of AWM to the new directories where you have installed the new version of AWM. Third, you should copy from the previous version of AWM, the awm.properties file which stores the AWM preferences settings and the awmdb.properties file which stores database connection settings, to the directories where you have installed the new version of AWM. This will ensure that any previous configuration settings will be migrated to the new installation of AWM.
- Make sure your environment has at least JRE version 1.5 (Java Runtime Environment) installed. JRE version 1.6 is also supported. This is required to be able to run Analytic Workspace Manager as a single jar file.
- Update the awmrun.sh file included in the kit with the directory path of the version of the Java Runtime Environment installed in your environment and then execute this file to start Analytic Workspace Manager.
Additionally, you may start the awm11.2.0.3.0.jar file by running the jar file from a command line as follows:
java mx1024m -jar awm11.2.0.3.0.jar
- After starting AWM for the first time, you should verify that the preference settings for directories in the AWM configuration are set properly for the new version of AWM. Select the Configuration option item from the Tools menu in AWM to adjust these settings. The preference settings to check are:
General Template directory
Logging Session Logging Directory Location
Plugin Plugin directory
Copyright © Oracle Corporation 2011. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.