Menu Path: |
Toolbar: |
A Rhapsody Local Configuration (RLC) file contains the working details for all routes, communication points and filters, along with any associated message and mapper definition files, XML configuration files, custom modules, security certificates and third-party drivers.
An RLC file is likely to contain a configuration which is used to control the processing and flow of PHI (Protected Health Information). Therefore, untrusted RLC files should be reviewed before loading them into production environments to ensure the security of PHI, doing precisely what is intended (and no more). In particular, a review of an untrusted RLC file should include:
- All output-capable communication points to ensure that no PHI is being sent out an unexpected channel.
- JavaScript components and objects to ensure associate code functions as expected, including: shared JavaScript libraries; the JavaScript filter, JavaScript conditional connector, JavaScript TCP Client and Server communication points, JavaScript REST Client communication point; and any custom components built using the RDK.
- The use of the Execute Command communication point and filter.
| If you want to... | Refer to... |
|---|---|
| Load, save or move a Rhapsody configuration from one machine to another | |
| Reload the current configuration from the engine | |
| Edit a configuration or create a new one | |
| Compare changes in any two configuration versions | |
| Configure rules for commit comments | |
| Manage versioned configuration history | |
| Learn about migrating non-versioned configurations to versioned configurations |
You must have the appropriate access rights to manage Rhapsody configurations.