SA XT for web access : System Architect XT : Customizing System Architect XT : Customizing the configuration file
  
Customizing the configuration file
As an example for working with components, the steps in the section below use the configuration file commercial.xml (you can also use defence.xml).
Note Backup the original files before you modify them.
Overview of customizing the configuration file
1 Make a copy of a configuration file and name it something like Mycommercial.xml or Mydefence.xml, respectively. Both files are in this folder:
C:\Program Files\UNICOM Systems\System Architect Suite\SAXT\Pagefiles
2 Save your custom Configuration Files to the same folder so your files appear as options that you can select from the Select page configuration file list.
3 Using your XML editor of choice, open your copy of the configuration file (for example, Mycommercial.xml).
4 Modify or create new components on the page.
5 Save the configuration file.
6 Login to the System Architect XT website, for example http://<computername>/saxt.
7 On the default Home page, click Encyclopedia Profile on the Site Management box. This takes you to the Configure Encyclopedia Profile page.
8 Select Mycommercial.xml from the Select page configuration file list.
9 Click OK.
Your customized Configuration File is now displayed as the Home page of System Architect XT.
Specifying that reports should be run across workspaces
Reports can be run across all workspaces or a subset. What happens is that the output from each workspace is combined.
To obtain the workspace IDs, execute this query in SAEM:
SELECT * FROM Workspaces
Where reports are specified in component blocks
<component name="..." ...>
<settings>
...
</settings>
<runAcrossWorkspaces workspaces="" restrictToRecsInWS="Y" /><!-- workspaces=anything to report on all workspaces or csv of workspace ids -->
<fields>
...
</fields>
<report>
...
</report>
</component>
Where reports are referenced through link elements
<component name="By Audit" type="Link" class="boxSmall" style="height:150px" header="By Audit" format="Table" scrolling="Y" newpage="Y">
<link target="ip/getpage.aspx?reportfile=HealthOfArchitecture&amp;reportname=Count of All Definitions Modified by Audit ID&amp;DDID=&amp;stylesheet=/stylesheets/Count of Groups (All).xsl" label="Which Audit ID has modified the most definitions?"/>
<link target="ip/getpage.aspx?reportfile=HealthOfArchitecture&amp;reportname=Count of All Definitions Created by Audit ID&amp;DDID=&amp;stylesheet=/stylesheets/Count of Groups (All).xsl&amp;RunAcrossWorkspaces=Y&amp;RestrictToRecsInWS=Y" label="Which Audit ID has created the most definitions?"/>
<!-- Workspaces=anything to report on all workspaces or csv of workspace ids -->
Use of attribute restrictToRecsInWS or parameter RestrictToRecsInWS
The attribute restrictToRecsInWS or parameter RestrictToRecsInWS causes output for each workspace to be restricted to those records that were stored in that workspace. This means creations and modifications made in this workspace, so excludes anything that was inherited from parent workspaces that was not changed.
Note The values returned by the WorkspaceName and WorkspacePath fields will be those of the workspace being reported on, when a report is run across workspaces, in order to understand records that might otherwise appear to be duplicates.