Deployment of Analytic Workspace

Question

Hi,
I have a query regarding the deployment of an AW in various environments like dev, test and live.
When we first create the AW in dev environment, we specify an AW name and the tablespace to be allocated for that particular AW. For deploying the AW in different environment, we use the XML template that is exported from the AW using 'Export Analytic Workspace to Template' option. But while creating the AW from template, there is no option to specify the tablespace for the new environment.
Could anyone please help me how tablespace can be specified while deploying AW in other environments.
Thanking in advance,
Mainak

Answer 1

This is a bit of a hack, but it will work
Towards the end of the XML template file you should see an entry something like this.
<AW
  Name="MY_AW"
  Version="11.2">
</AW>The name of the AW will obviously be different, and the version may be different as well. It doesn't matter because you will just delete the section from the XML document.
Now in AWM you first create an empty AW using the simple "Create Analytical Workspace..." option. This will allow you to specify a tablespace. Once you have done this you select "Create Analytical Workspace From Template..." and import your objects into the AW you just created. Note that you must create an AW with the same name as the original as it is embedded into the XML for the cubes and dimensions.
The more sophisticated version of this is to delete the AW section above and then add a header to the XML template
<!DOCTYPE Metadata [
  <!ENTITY % BIND_VALUES PUBLIC "OLAP BIND VALUES" "OLAP METADATA">
  %BIND_VALUES;
  ]>Finally you replace all occurrences of your AW name with the string
&AW_NAME;For example, instead of
<AWPrimaryDimensionOrganization
  MVOption="NONE"
  HierarchyConsistencyRule="STAR_CONSISTENT"
  AddUniqueKeyPrefix="False"
  AW="MY_AW">you would have
<AWPrimaryDimensionOrganization
  MVOption="NONE"
  HierarchyConsistencyRule="STAR_CONSISTENT"
  AddUniqueKeyPrefix="False"
  AW="&AW_NAME;">You can see this type of XML if you export a single cube or dimension to a template. I don't know why AWM doesn't let you do the same thing for the whole AW.