Detailed and Sanitized Logs

The Publisher for Rhapsody™ provides the user with the ability to have a detailed log of operations to support identification of failures.
This allows the ability to identify problematic areas of a model. They are useful for both developers and users.
Hence, two log files are generated, in the following folders:

• %USER%/.rhp2md/com.sodius.mdw.interop.rhp_md_sysml, when publishing from Rhapsody.
• %USER%/.md2rhp/com.sodius.interop.md_rhp, when publishing from MagicDraw.

Detailed logging

Several levels of logging are generated in the detailed logging:

• INFO: An information is given. Most of time, it concerns an activity/positive action.
• WARNING: An alert is used. Most of time, it warns the user that the input model is not correct. This will potentially damage the result.
• ERROR: An exception is launched. The publishing is cancelled.

Also, logging can concern different steps in the publishing:

• PROXY: The reading of the Rhapsody instances.
• TRANSFORMATION: The transformations of the Rhapsody instances to UML2 instances.
• DIAGRAM: The reading of the Rhapsody diagrams.
• SYSML_MAPPING: The mapping of the SysML profiles.
• CLEANING: The cleaning of the UML2 model.

Sanitized Logging

The Sanitized log matches the Detailed logging.
However, potential sensitive information have been removed, like the name of diagrams, or the full path of elements.
The Sanitized log is the log to share with the support team.