Page Comparison

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 aliasesAliases:

• all All logical names for all Queues & and Topics sections must be unique across all *.json files! (if .
• If you have a set of json-files with aliases definitions - it , they will be applied for all of them together).
• destination Destination names (physical names) should must not be empty, otherwise it will be skippedBe aware! We will search for alias name in Queues section first and only then for Topics - it means if we will find they are skipped.

...

...