• It is recommended that you put a master version of the siteprefs.xml configuration file on a shared network drive and edit the XInclude tag in the userprefs.xml configuration file to specify the full path to the master file. This enables you to specify global site parameters for all users that reference the master file. Any changes to the master file are processed by the PTC サーバー接続 the next time a user invokes the connection.

• If you decide to enable object reuse by setting objectreuse=on in the atidefaults.bcf burst configuration file, then reusable document and graphic objects must be accessible to all users that might need to reference the objects. Be sure to set the access control policies on your products and libraries so that users can access reusable objects.

• Consider whether you want to enable users to determine where document objects are stored when they are saved to the PTC Server. If you set useroverride=on in the atidefaults.bcf burst configuration file, then any location rules you set in the burst configuration files are ignored if the user changes the location.

• While 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.