Specifying a Burst Configuration File
By default, Arbortext Editor expects the document-type-specific burst configuration file to be named doctypename.bcf where doctypename is the same name as that of the document type file. For example, if the document type name is axdocbook.dtd, the name of the associated burst configuration file is expected to be axdocbook.bcf.
If you want to use a different name for your document-type-specific burst configuration file, you can specify that name in the document type's .dcf file.
To specify a burst configuration file:
1. Open Arbortext Architect.
2. Choose > .
3. Locate the directory in which the document type whose .dcf file you want to modify is saved, and click Select.
4. Once the document type is loaded, choose > . If the document type has a .dcf file, it displays in the Arbortext ArchitectDCF Editor window. If there is no .dcf file associated with this document type, Arbortext Architect automatically creates one.
5. Locate the Options element in the DCF Editor. If the file doesn't include an Options element, add one.
|
|
Open the Document Type Viewer ( > ) to view the element hierarchy for the .dcf file. This will help you determine the valid location for the Options element.
|
6. Click next to the Options element to open the Modify Attributes dialog box.
|
|
You must have the Force Required Attributes EntryEdit preference selected for this dialog box to open automatically. |
7. In the burstConfigFileOverride field, enter the repository adapter prefix and the name of the burst configuration file using the following format:
x-dm://newbasename
x-dm is the prefix for the repository adapter. For the PTC Server connection, use x-wc. newbasename is the new base name for the document-type-specific burst configuration file with the required prefix .bcf. For example, if the attribute burstConfigFileOverride="x-wc://ax40" is found in axdocbook.dcf, then a burst file named ax40.bcf is searched for instead of axdocbook.bcf.
If you need to specify files for more than one repository adapter, you can add others entries separated by a semicolon. For example:
x-dm://newbasename;x-dm2://newbasename2
8. Click OK.
9. Choose > to save the changes you have made to the .dcf file.
Note that if you have the deprecated ATI-DOCBURST entry in the catalog file for your document type, that entry overrides the burstConfigFileOverride setting in the .dcf file.
