Testing Burst Configurations
Test your burst configuration thoroughly before deploying it. When testing your burst configuration, keep the following issues in mind:
• Always use an area of the PTC Server for testing. Ideally, you should be working in a PTC Server area in that you can delete from at any time without losing any valuable data.
• When you test your burst configuration, make sure to use as many different types of documents as possible. Ideally, you should include documents that define the outermost boundaries of your authors' work. While testing, make sure to balance how well the burst configuration handles a given document against how common that kind of document is for your authors.
• Use the bursting log file to your advantage. Saving your burst logs from one version of your burst configuration to another will give you valuable data on how the PTC Server connection is traversing your document and creating document objects.
Suggested Iteration
You may find it useful to repeat the following process: Enable bursting for your document type, test your documents, and then examine the results. If you want to make a change, perform the following steps:
1. Disable the current burst configuration by renaming the doctypename.bcf burst configuration file.
2. Make the desired edits to the renamed doctypename.bcf burst configuration file.
3. Remove the entities and objects that have been added to the PTC Server during import.
4. Enable the revised burst configuration by renaming the doctypename.bcf burst configuration file back to its original name.
5. Start Arbortext Editor or Arbortext Publishing Engine and connect to a PTC Server. If there are any parsing errors in the atidefaults.bcf file, an error message will display. You must fix any parsing errors before you can proceed.
6. Load a test document (either from inside or outside the PTC Server) that matches the doctypename.bcf document type. If there are any parsing errors in the doctypename.bcf file, an error message will display. You must fix any parsing errors before you can proceed.
7. Perform the desired bursting on your suite of test documents.
8. View the same test document as generated by the two different burst configurations and verify that your changes had the desired effect.