A manifest spec for BBDW OLAP extensions contains a list of extensions specs for the deployment utility to process. The extensions are grouped by six types (DSVTables, FactExtends, etc.) . The deployment utility processes the extensions specs referenced in the manifest spec. Because of dependencies, the processing logic is such that some specs are processed before others. The manifest spec is the simplest of the seven revisions specs. To create or modify a manifest spec, follow the pattern in the example, replacing the filenames with those of your specs. You only need one node for each type and you can add multiple nodes for children of the types (DSVTable, FactExtend, etc.)
A manifest spec looks like this:
<UDMExtendManifest> <DSVTables> <DSVTable>Event_Ext.DSVTable.xml</DSVTable> </DSVTables> <FactExtends> <FactExtend>FACT_INTERACTION.FactExtend.xml</FactExtend> </FactExtends> <Dimensions> <Dimension>Event_Ext.Dimension.xml</Dimension> <Dimension>Installment_Ext.Dimension.xml</Dimension> </Dimensions> <MeasureGroups> <MeasureGroup>ConstituencyPivot.MeasureGroup.xml</MeasureGroup> </MeasureGroups> <DimensionalUsages> <DimensionalUsage>Event_Ext.DimensionalUsage.xml</DimensionalUsage> <DimensionalUsage>Installment_Ext.DimensionalUsage.xml</DimensionalUsage> <DimensionalUsage>Constituent.DimensionalUsage.xml</DimensionalUsage> <DimensionalUsage>ConstituencyPivot.DimensionalUsage.xml</DimensionalUsage> <DimensionalUsage>FundraiserAddress.DimensionalUsage.xml</DimensionalUsage> <DimensionalUsage>FundraiserAge.DimensionalUsage.xml</DimensionalUsage> <DimensionalUsage>FundraiserDemographic.DimensionalUsage.xml</DimensionalUsage> <DimensionalUsage>FundraiserPersonalInformation.DimensionalUsage.xml</DimensionalUsage> </DimensionalUsages> <MDXScripts> <MDXScript>OLAP.MDXScript.xml</MDXScript> </MDXScripts> </UDMExtendManifest>