Import shadowed metatdata objects such as cubes and dimensions; non-shadowed metatdata objects such as worksheets and named queries; scenarios and scenario-specific information into Integrated Operational Planning.
import datasource|rowsource|dimension|stagemap|cube|constraint| reporttemplate|modelgroup|dbconnection|worksheet|workbook| analysistype|style|scope|rule} {definition|definitions} from file xml_file_name
Arguments
xml_file_name—XML file containing the object definitions
import scenario from directory file_name {replace using batch}
Arguments
file_name—Name of the directory containing the scenario definitions. The scenario from the specified directory is imported.
import {named queries|acls|security filters} from file xml_file_name
Arguments
xml_file_name—XML file containing the object definitions. Imports the respective named queries, acls and security filters from the xml file specified.
import cubemaps
Creates cube maps.
import {user preferences|filters}
Imports user preferences from export/preferences directory and filters from export/filters directory.
The object definitions are in the XML file referred to in the command, and the XML file conforms to the grammar specified by the Integrated Operational Planning XSD. See XML Files and Search Path for information on how to locate the XML file.
On a clean system, the first action is to import these objects. If an object is already in the system and you run import again, Integrated Operational Planning compares the imported object with the existing object to see if anything has changed.
The following Imports the data source, row source, dimension, stagemap, cube, constraint, and reporttemplate definitions:
import datasource definition from file "${interlace_home}/custom/model/datasource_IN_TRANSITTIME_DS.xml"
import rowsource definition from file ""${interlace_home}/custom/model/rowsource_IN_SCRAPPERCENT_RS.xml"
import dimension definition from file ""${interlace_home}/custom/model/dim_Fiscal.xml"
import stagemap definition from file ""${interlace_home}/custom/model/stagemap_IN_TRANSITTIME_SM.xml"
import cube definition from file ""${interlace_home}/custom/model/cube_DriveDemand.xml"
import constraint definition from file ""${interlace_home}/custom/model/constr_HDAExcess.xml"
import reporttemplate definition from file ""${interlace_home}/custom/reportlibrary/report_Simple Report(Fixedheader).xml"
Imports database definition:
import all dbconnection definition [from file file name]
Imports all database connection information: The command imports database connection object details to an XML file in install-root/custom/datasource. The default file name is dbconnections.xml.
The XML file is generated by the corresponding export command
The XML file contains all the parameters that defines the connection to the Essbase instance
To verify the parameters, click Administrative Workbench, then Administration, and then Essbase connections.