Reverse-engineer an Essbase Model

20-6 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator The KM choice for an interface determines the abilities and performance of this interface. The recommendations in this section help in the selection of the KM for different situations concerning Hyperion Essbase. This section contains the following topics: ■ Loading Metadata ■ Loading Data ■ Extracting Data

20.5.1 Loading Metadata

Oracle Data Integrator provides the IKM SQL to Hyperion Essbase METADATA for loading metadata into an Essbase application. Metadata consists of dimension members. You must load members, or metadata, before you load data values for the members. You can load members only to dimensions that exist in Essbase. You must use a separate interface for each dimension that you load. You can chain interfaces to load metadata into several dimensions at once. Table 20–3 lists the options of the IKM SQL to Hyperion Essbase METADATA. These options define how the adapter loads metadata into an Essbase application. Note: The metadata datastore can also be modified by adding or delete columns to match the dimension build rule that will be used to perform the metadata load. For example, the default datastore would have columns for ParentName and ChildName, if the rule is a generational dimension build rule, you can modify the metadata datastore to match the columns within your generational dimension build rule. The loadMarkets interface within the samples is an example of performing a metadata load using a generational dimension build rule. Table 20–3 IKM SQL to Hyperion Essbase METADATA Options Option Values Description RULES_FILE Blank Default Specify the rules file for loading or building metadata. If the rules file is present on the Essbase server, then, only specify the file name, otherwise, specify the fully qualified file name with respect to the Oracle Data Integrator Agent. RULE_SEPARATOR , Default Optional Specify a rule separator in the rules file. These are the valid values: ■ Comma ■ Tab ■ Space ■ Custom character; for example, , , Oracle Hyperion Essbase 20-7 RESTRUCTURE_ DATABASE ■ KEEP_ALL_ DATA Default ■ KEEP_ INPUT_ DATA ■ KEEP_ LEVEL0_ DATA ■ DISCARD_ ALL_DATA Restructure database after loading metadata in the Essbasecube. These are the valid values: ■ KEEP_ALL_DATA- Keep all the data ■ KEEP_INPUT_DATA Keep only ■ input data ■ KEEP_LEVEL0_DATA-Keep only ■ level 0 data ■ DISCARD_ALL_DATA-Discard all ■ data Note: This option is applicable for the Essbase Release 9.3 and later. For the Essbase releases prior to 9.3, this option is ignored. PRE_LOAD_MAXL_ SCRIPT Blank Default Enable this option to execute a MAXL script before loading metadata to the Essbase cube. Specify a fully qualified path name without blank spaces for the MAXL script file. Note: To successfully execute this option, the Essbase client must be installed and configured on the machine where the Oracle Data Integrator Agent is running. POST_LOAD_MAXL_ SCRIPT Blank Default Enable this option to execute a MAXL script after loading metadata to the Essbase cube. Specify a fully qualified path name without blank spaces for the MAXL script file. Note: To successfully execute this option, the Essbase client must be installed and configured on the machine where the Oracle Data Integrator Agent is running. ABORT_ON_PRE_ MAXL_ERROR ■ No Default ■ Yes This option is only applicable if you are enabling the PRE_LOAD_MAXL_SCRIPT option. If you set the ABORT_ON_PRE_MAXL_ERROR option to Yes, then the load process is aborted on encountering any error while executing the pre-MAXL script. LOG_ENABLED ■ No Default ■ Yes If this option is set to Yes, during the IKM process, logging is done to the file specified in the LOG_ FILE_NAME option. LOG_FILE_NAME ?=java.lang.Syst em.getProperty “java.io.tmpdir” ?Extract_ =snpRef.getFrom .log Default Specify a file name to log events of the IKM process. Table 20–3 Cont. IKM SQL to Hyperion Essbase METADATA Options Option Values Description