Checks for objects imported into the system and publish the objects so that they are available to everyone.
publish {datasource|rowsource|dimension|stagemap|cube|constraint} definitions
or
publish {datasource|rowsource|dimension|stagemap|cube constraint|dbconnection worksheet|workbook|reporttemplate|keymetric|analysistype} definition object_name
object_name—Name of the object to publish.
When publishing, Integrated Operational Planning checks to ensure that the object model is valid.
Publish commands refer to the following schemas supported by Integrated Operational Planning.
Model schema—Schema into which XML objects are imported and maintained. XML objects are created through actions in the Administration Workbench and by isadmin import commands.
XML files that do not conform to XSD are rejected. Integrated Operational Planning does additional syntax and semantic checking not expressible in XSD to ensure a consistent and valid object model.
Model objects include shadowed objects (cubes, dimensions) and nonshadowed objects (workbooks and worksheets used for presentations). When publishing, shadowed objects go first to the Edit schema and then to the Base schema. Nonshadowed objects go directly to the Base schema.
Base schema—Schema into which XML objects that are converted to proprietary backend versions of objects are maintained. This is the published schema available to everyone. All loading, calculations, and data manipulation occur in this schema.
Edit schema—Similar to the Base schema for storing backend versions of objects. Integrated Operational Planning creates the backend versions of XML objects in the Edit schema, does more error checking not possible in the Model schema, and then gets ready to push the changes to the Base schema.
The following example publishes row source, data source, dimension, and stagemap definitions.
# Set the model schema to edit mode. alter model schema set current edit # Set the schema to shadow in backend and clear any previous information. set schema shadow clear schema shadow # Publish row source and dimension defintions to shadow schema. # These "macro" commands publish the imported data sources, row sources, dimensions, and stagemaps. # This way you don't need to remember to publish one object at a time. publish rowsource definitions publish datasource definitions publish dimension definitions publish stagemap definitions # Push object definitions from shadow schema to base schema. alter system restructure
The following example publishes cube and constraint objects. Publish cubes after you publish and restructure dimensions.
# Set the model schema to edit mode. alter model schema set current edit # Set the schema to shadow in backend and clear any previous information. set schema shadow clear schema shadow # Publish cube and constraint defintions to shadow schema. # These "macro" commands publish the imported cube and constraint definitions. # This way you don't need to remember to publish one object at a time. publish cube definitions publish constraint definitions # Push object definitions from shadow schema to base schema. alter system restructure