The Rhapsody datastore is a file-based system used to store the engine configuration and state information as well as the message archive.
The default location for the datastore files is <RhapsodyInstallDirectory>\rhapsody\data
.
Sub-directory | Description |
---|---|
|
Contains the backups schedule. |
\charactermap |
Stores the global mapping file, characterMapping.xml . Refer to Global Mapping File for details. |
\cleanup |
Holds configuration details that control when cleanup is performed. |
|
Contains the cleanup trace log files used by the Management Console. |
|
Contains indexes for certain communication points. |
|
Contains the Rhapsody configuration. |
|
Used by the Duplicate Message Detection filter to store the data structure for tracking duplicate messages. |
|
Stores persistent information about the current state of each ID generator. |
|
Contains indexes created to access properties on messages. |
|
Contains external libraries that are common between many communication points. For example, you can add third-party JDBC drivers here instead of attaching them to each individual communication point. However, if you attach a library to a communication point it will override any library that is in this directory. |
|
Contains the following log folders used by the Management Console:
These files are not text logs, and should not be attached to support tickets. The text logs can be found in the |
\lookuptable |
Contains the following databases:
|
|
Contains data about events that occur to messages, which is used to display the message path in the Management Console. |
\messagemodifier |
Not currently used for any purpose. |
Holds both the message body, and all the metadata and properties of messages. |
|
|
Contains indexes for the Hold Queue and Error Queue. |
|
Contains all the uploaded modules, such as custom communication points and filters. |
|
Contains a settings file used by the Management Console. |
\notifications |
Contains notifications history and respective indexes etc. |
|
Used by communication points to store values that must be persisted, for example, a database key value. |
|
Stores index files that point into the message store. These indexes control how messages are queued inside the engine. The
|
|
Stores the startup state information for a communication point or route. The storage location of the startup metadata can be changed by adding the |
|
Stores statistical information used to plot graphs in the Management Console, and also the total message counts for components. |
|
Used as a general storage location. |
|
Used to store files temporarily as they are being processed by Rhapsody. |
|
Used to store information about messages currently being tracked. |
|
Contains a transaction system that operates in a similar way to a database. |
|
Contains all the user data. This data is protected with encryption and a one-way hash system so that it is impossible to recover a password. If the contents of this directory are deleted the administration account is automatically recreated. |
|
Contains the current data validation status, which is used to ensure that data is validated correctly after an unclean shutdown. |