Configuration entries are necessary to protect by replication in data groups that have not enabled journal-centric configuration for object types that are capable of being journaled to a user journal.
Data groups that have enabled journal-centric configuration for specific object types do not need configuration entries to include and protect those object types in replication. However, configuration entries may still be needed to identify exceptions to exclude from replication for those object types. Configuration entries are still required for object types that cannot be journaled to a user journal, for identifying objects with differences to ignore during auditing, and for objects that you do not want to replicate from the user journal for performance reasons.
Replication processes evaluate an object against the set of configuration entries for that category of object (library, directory, folder). The rule from the set that is the “best” or most specific match to an object determines if and how the object is replicated. However, this does not mean that you should create specific rules for every object!
It is more efficient to create a few broad configuration entries capable of identifying multiple objects to include in replication, and then create specific rules to handle exceptions.
The Include and Exclude options from reports do not support creating rules that specify generic names. However, you can manually create data object entries, IFS entries, or DLO entries with generic names. Once rules with generic names exist, the next time reports run they will be used in determining protection levels.
You can also manually create rules for directories that use wildcard characters embedded within generic names to exclude content. These “advanced generic” exclude rules act as a filter for directories that are already identified by include configuration entries which specify basic generic names. When directory rules with advanced generic names exist, they affect the overall protection status of directories listed in the data protection report.