Configuration files of JMS logical names (destinations.json) are stored according to the following path convention:
Path to aliases
estar/tpe/dynamic/mc2/eaglejms/destinations/*.json
This is a common configuration format for the destinations.json file.
aliases.json
{
"Region": "Oracle SID",/*Specific Oracle SID of region name to which this config belongs*/
"Queues": [
{ "alias": "logicalname_1", "destination": "real queue name A" },
{ "alias": "logicalname_2", "destination": "real queue name B" }
],
//=================================================================
"Topics": [
{ "alias": "logicalname_3", "destination": "real topic name A" },
{ "alias": "logicalname_4", "destination": "real topic name B" }
]
}
Rules for Aliases:
- All logical names for all Queues and Topics sections must be unique across all *.json files.
- If you have a set of json-files with aliases definitions, they are applied all together.
- Destination names (physical names) must not be empty, otherwise they are skipped.
The system searches for an alias name in the Queues section before the Topics section. This means that an alias name in Queues section is considered as a queue destination although you may have intended to have a Topic subscription.