Instructs the adapter to persistently store a path name to a Logical ID association. If a mapping already exists for the path name, it will be replaced with the new Logical ID. Use this method in conjunction with the getFileMappingEntry method to prevent creating multiple CMS objects based on a single file.

The getFileMappingEntry and setFileMappingEntry calls are not atomic. During bursting, a new CMS object is created between the getFileMappingEntry and setFileMappingEntry calls. If multiple processes are performing burst operations, the result might be multiple CMS objects for the same source file. For example, assume process A and process B both call the getFileMappingEntry method at the same time and find that an association does not currently exist. Both processes then create new CMS objects and call the setFileMappingEntry method to create the association. The last setFileMappingEntry call takes precedence, and its CMS object will be reused by subsequent burst operations. The other CMS object continues to exist and be referenced by its XML document.

There is no standard way to tell the adapter to remove a path name to Logical ID mapping.