Configuration files of JMS logical names (destinations.json) are stored according to the following path convention:
| Info | ||
|---|---|---|
| ||
estar/tpe/dynamic/mc2/eaglejms/destinations/*.json |
This is a common configuration format for the destinations.json file.
| 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" }
]
} |
...
- 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 be are applied for all of them together.
- Destination names (physical names) must not be empty, otherwise they are skipped.
...