MEGA Administration : Administrator Guide : Managing Repositories : Managing Repositories : Configuring the logging for an inter repository consolidation
   
Configuring the logging for an inter repository consolidation
To improve performance you can define some MetaClasses or MetaAssociationEnds as non loggable.
*See "Modifying MetaClass loggability".
Logging
Logging of updates enables:
mainly to view the repository activity, i.e. actions performed on objects.
*See "Viewing the Repository Update Log".
In that case, an incomplete (Consolidate command) or truncated (Delete command) log is functionally satisfactory.
*See "Deleting a log or reducing the log size" step 7.
This is the default configuration.
to transfer the commands performed from a repository to another.
Example: you want to transfer all the commands performed during the day from a development repository to a production repository.
In that case a complete log, including all the actions performed by the users, is necessary so that the inter repository consolidation is performed correctly. You must modify the default log behavior.
*See "Modifying the log behavior".
Modifying the log behavior
To include in your log the MetaClasses and MetaAssociations defined as non loggable, you must modify the log behavior.
To modify the log behavior:
1. Access the options.
*See "Accessing Options", page 368.
2. In the Options tree, select Repository.
3. In the right pane, for the Log behavior option, select "Logging all updates" value.
All of the updates are included in the logs, including MetaClasses and MetaAssociations that are defined as non loggable.
*See "Modifying MetaClass loggability".