Configuration files of JMS logical names (destinations.json) are stored by this pathaccording to the following path convention:
Info |
---|
Path to aliasesestar/tpe/dynamic/mc2/eaglejms/destinations/*.json |
This is a common configuration format of destinationsfor the destinations.json file.
aliases.json
...
Code Block | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
{ "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 being applied for aliasesAliases:
- all
All logical names for all Queues
&and Topics sections must be unique
(ifacross all *.json files.
If you have a set of json-files
of aliases - it will be applied for all of them together)destinationwith aliases definitions, they are applied all together.
Destination names (physical names)
shouldmust not be empty, otherwise
it will bethey are skipped
Be aware! We will search for alias name in Queues section first and only then for Topics - it means if we will find alias name in Queues section first we will consider it as a queue destination in spite of you wanted topic subscription.
Note |
---|
The system searches for an alias name in the Queues section before the Topics section. This means that an alias name in the Queues section is considered as a Queue destination although you may have intended it to have a Topic destination. |