Configuration files of JMS logical names (destinations.json) are stored according to the following path convention:
Info | |
---|---|
title | Path to aliasesestar/tpe/dynamic/mc2/eaglejms/destinations/*.json |
This is a common configuration format of for 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 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
will beare applied
forall
of themtogether.
Destination names (physical names) must not be empty, otherwise they are skipped.
Warningnote |
---|
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 Queue destination although you may have intended it to have a Topic subscriptiondestination. |