You can model data in these ways:
Create a model using the Model tab in the Administration Workbench
Import a model using XML meatadata definition files
Figure 10, How Modeling Data is Staged and Loaded into Integrated Operational Planning illustrates the relationship and flow between various modeling elements.
Data Sources—Relational tables in the Integrated Operational Planning database where copies of external modeling data are stored. By default, the Integrated Operational Planning application looks in not/install/config/data for files containing the data; for example, CSV text files. The data is then loaded into data sources in the Integrated Operational Planning database. The default directory for external modeling data is specified in ISServer.properties.
Data Source Definitions—XML files that specify which data source columns in a data source to use. Using all columns in a data source is not required. By default, data source definition files are in /install/custom/data source.
Stagemaps—XML files that map data sources to row sources or dimensions in the Integrated Operational Planning database. One data source can be mapped to multiple row sources. For example, each row source can contain some columns of the original data source. By default, stagemap files are in directory/install/custom/loader.
When data sources are mapped to dimensions, Integrated Operational Planning maps the names from the tabular data source to the elements of the dimension’s hierarchy. In addition to mapping Data source columns to dimension members at all levels, Integrated Operational Planning maps the attributes of dimension members and specifies the relationship (for example, parent-child).
Row Sources—Relational tables in the Integrated Operational Planning database containing data values. Row sources can be mapped to cubes.
Integrated Operational Planning supports one-to-one mapping of row source values to one value in a cube measure or aggregation of row source values to one value in cube measure. Row source columns are mapped to dimension member names in the cube, and the values are mapped to different measures.
Dimension Definitions—XML files that specify the namespace name, hierarchy names, and hierarchy level names for a dimension. By default, dimension definition files are in /install/custom/model.
Row Source Definitions—XML files that specify the columns in a row source and the parent-child relationships between row sources. By default, row source definition files are in /install/custom/row source.
Cube Definitions—XML files that specify the dimensions in a cube, the names of measures in the cube and measure formulas, the names of row sources mapped to the cube, and cube-to-cube mapping information. By default, cube definition files are in /install/custom/model.
The mapping among cubes allows data values in one cube to flow to data values in another cube. The cubes have different structures, and the mapping defines the data flow. The mapping is like a table join in the relational world—it defines the common dimensions and how to map or join them.