Select the RKM Oracle OLAP (Jython) from the KM list.
Set the RKM options as follows:
MOLAP: Set to YES to reverse an Analytic Workspace. If this option is set to YES, the following options are mandatory:
AW_NAME: Indicate the name of the Analytical Workspace AW_URL: Specify the URL of the Analytical Workspace AW_OWNER: Indicate the name of the Analytical Workspace Owner AW_PASSWORD: Indicate the password of the Analytical Workspace Owner ROLAP: Set to YES to reverse tables from a ROLAP schema USE_LOG: Set to YES to write the log details of the reverse-engineering process into a log file. L O G _ F I L E _ N A M E : S p e c i f y t h e n a m e o f t h e l o g f i l e
Specify the reverse mask in the Mask field in order to select the tables to reverse. The Mask field, in the Reverse tab, filters reverse-engineered objects based on their name. The Mask field must not be empty and must contain at least the percentage symbol (%).
Click Apply, and then click Reverse.
You can follow the reverse-engineering process in the Execution Log.
Note: The reverse-engineering process may take several minutes or longer depending on the number of tables reverse-engineered.
At the end of the reverse-engineering process, the tables used by a cube are represented as datastores. You can then use these datastores as a source or a target of your interfaces.
Using Oracle OLAP as a Source in an Integration Interface
After performing a reverse-engineering using the RKM Oracle OLAP (Jython), you can use Oracle OLAP data tables as a source of an integration interface to extract data from the Oracle OLAP database and integrate them into another system (Data warehouse, other database...). Using Oracle OLAP as a source in these conditions is identical to using an Oracle datastore as a source in an integration interface. The Generic SQLand Oracle Database KMs can be used for this purpose.
Using Oracle ROLAP as a Target in an Integration Interface
After performing a reverse-engineering using the RKM Oracle OLAP (Jython), you can use Oracle ROLAP data tables as a target of an integration interface to load data from any system to the Oracle ROLAP database. Using Oracle ROLAP as a target in these conditions is identical to using an Oracle datastore as a target in an integration interface. The Generic SQLand Oracle Database KMs can be used for this purpose.
Using Oracle MOLAP as a Target in an Integration Interface
Using Oracle MOLAP as a Target in an integration interface is similar to using Oracle ROLAP as a target with the difference that, in addition to the standard features of the integration process, you can refresh the MOLAP cube at the execution of the integration interface by using the IKM Oracle AW Incremental Update.
Note: In order to avoid refreshing the cube at every integration interface step, use the IKM Oracle AW Incremental Update with the refresh cube options only in the last integration interface of the package. In the last integration interface set the options to refresh the cube as follows: Set the REFRESH_CUBE option to YES and specify the values for the AW_OWNER, AW_NAME, and CUBE_NAME option.
Knowledge Modules Reference Guide