Specifying the Burst Configuration Location

Though you are not required to store the burst configuration files in a single location in the PTC Server, that is the recommended approach. The best practice is to create a PTC Server product or library that you use just to store burst configuration files. Since burst configuration files must be accessible by all users, you must change the access control policy on that product or library to make all Dynamic Document objects in the product or library readable by everybody.

Use Arbortext Editor to develop your burst configuration files, before saving them to the PTC Server. Once you have finished development, use File > Save As Server Object to store the files into the designated location in the PTC Server. You must name the object correctly, either atidefaults.bcf for the system-wide burst configuration settings or the name of the associated document type (for example, axdocbook.bcf) for a document-type-specific burst configuration. The system recognizes that you are storing a burst configuration file and will be able to locate the file in the PTC Server when needed. You must store the burst configuration files in a location accessible by all users.

You can also store burst configuration files outside of your PTC Server. You can use a directory on the file system referenced by the APTOBJCFG environment variable, an Arbortextcustom directory, or the document type directory to store the burst configuration files. If you use a custom directory, you can also use a zipped custom directory to store the document-type-specific burst configuration files.

When you use the PTC Server connection, Arbortext Editor and Arbortext Publishing Engine search for the system-wide burst configuration file using the following rules:

1. If the APTOBJCFG environment variable is defined, Arbortext Editor and Arbortext Publishing Engine search the specified directory. If Arbortext Editor or Arbortext Publishing Engine finds an atidefaults.bcf file in this directory, it becomes the system-wide burst configuration file for the current Arbortext Editor or Arbortext Publishing Engine session.

If atidefaults.bcf is not found, Arbortext Editor and Arbortext Publishing Engine also search this location for a file named atidefaults (the file name prior to the 6.0 release). If found, that file becomes the system-wide burst configuration file for the current session.

2. Arbortext Editor and Arbortext Publishing Engine search Arbortext-path\custom\lib for a atidefaults.bcf file.

3. Arbortext Editor and Arbortext Publishing Engine search for an object stored in the PTC Server that is flagged as a burst configuration file and named atidefaults.bcf. If atidefaults.bcf is not found, Arbortext Editor and Arbortext Publishing Engine also search for a file flagged as a burst configuration file and named atidefaults.

If no atidefaults.bcf file or atidefaults is located, then the system defaults are used for bursting. These defaults use no object naming or location rules, no metadata rules, and result in monolithic documents during bursting.

1. If the APTOBJCFG environment variable is defined, Arbortext Editor and Arbortext Publishing Engine search the specified directory. If Arbortext Editor or Arbortext Publishing Engine finds a doctype.bcf file in this directory (for example axdocbook.bcf), it becomes the document-type-specific burst configuration file for that document type in the current Arbortext Editor or Arbortext Publishing Engine session.

If doctype.bcf is not found, Arbortext Editor and Arbortext Publishing Engine also search this location for a file named doctype (the file name prior to the 6.0 release). If found, that file becomes the document-type-specific burst configuration file for the current session.

2. Arbortext Editor and Arbortext Publishing Engine search all known custom\doctype directories for a doctype.bcf file. The name of the folder should match the name of the burst configuration. For example, if a diag.bcf file is available in the diag folder, Arbortext Editor and Arbortext Publishing Engine find the diag.bcf file in the custom\doctypes\diag folder. This includes any zipped custom directories referenced through the APTCUSTOM environment variable. It also includes the location on the PTC Server indicated by the WindchillCustomizations Folder preference. The preference is located in the Preference Manager utility in the Arbortext group. Refer to the Windchill documentation for more information about PTC Server preferences.

3. Arbortext Editor and Arbortext Publishing Engine search the document type directory for a doctype.bcf file.

4. Arbortext Editor and Arbortext Publishing Engine search for an object stored in the PTC Server that is flagged as a burst configuration file and named doctype.bcf. If doctype.bcf is not found, Arbortext Editor and Arbortext Publishing Engine also search for a file flagged as a burst configuration file and named doctype.