JMS Logical names configuration (Aliases)

Configuration files of JMS logical names (destinations.json) are stored by this path: 

This is common configuration format of destinations.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 being applied for aliases:

• all logical names for all Queues & Topics sections must be unique (if you have a set of json-files of aliases - it will be applied for all of them together)
• destination names (physical names) should not be empty, otherwise it will be 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.