A locker is used for compartmentalizing the configuration in a way that allows access to that configuration to be controlled. Like a folder, a locker can be used to organize and group components, but a locker also has attributes to restrict access (through the Access Control in Rhapsody) so that only certain users can see and edit the configuration of a given locker, and only certain users can view the messages that are processed by the components in the locker.
Locker Usage
Like a folder, a locker can contain communication points and routes. Message definitions are also stored in the locker, as are message tracking schemes, X12 projects, Intelligent Mapper mapping projects and REST clients, so that when coupled with appropriate application of access rights, there can be no chance that users that do not have access to your configuration can edit anything that will interfere with your message processing. This means that routes and communication points can only use message definitions and tracking schemes that are in the same locker as them. The following Rhapsody objects are stored globally: security objects, web services, lookup tables, Rhapsody variables, shared JavaScript libraries.
| Rhapsody Object | Locker-based | Global |
|---|---|---|
| Folders |  |
|
| Routes | |
|
| Communication points | |
|
| Message definitions | |
|
| Message tracking schemes | |
|
| REST clients | |
|
| X12 projects | |
|
| Intelligent Mapper mapping projects | |
|
| Security objects | |
|
| Web services | |
|
| Lookup tables | |
|
| Rhapsody variables | |
|
| Shared JavaScript libraries | |
|
| Templates | |
Usage of lockers in a configuration conforms to the following general rules:
- Lockers cannot contain lockers.
- Lockers and global objects can only have unique names, whereas locker-based objects are only required to have unique names within the same locker.
- Folders, communication points, and routes can only be created in a folder or locker.
- A communication point and its receiving routes are required to be in the same locker.
Locker-based objects can only use other locker-based objects (message definitions, message tracking schemes, REST clients, X12 projects, Intelligent Mapper mapping projects) in the same locker.
- Cross route connectors are required to be within the same locker.
When copying a communication point or route to a different locker, Rhapsody detects the message definitions and tracking schemes that the component uses, and give you the option to also copy them to the destination locker. Refer to Copying or Moving Components for details.
Locker Access Rights
Rhapsody provides a way to view which access groups have access to the locker, allowing you to quickly check what permissions users have for the locker. Refer to Locker View for details.