Message oriented middleware topology explorer
A method includes retrieving vendor specific data from one or more message oriented middleware servers of a message oriented middleware infrastructure, and inputting the vendor specific data from the one or more message oriented middleware servers into a back-end database. The vendor specific data is converted into commonly formatted data, and the commonly formatted data is inputted into a front-end database. The method also includes retrieving the commonly formatted data from the front-end database, and displaying the commonly formatted data on a user interface providing a visualization of a topology of the message oriented middleware infrastructure.
1. An apparatus comprising:
at least one processing platform comprising a plurality of processing devices;
said at least one processing platform being configured:
to retrieve vendor specific data from one or more message oriented middleware servers of a message oriented middleware infrastructure;
to input the vendor specific data from the one or more message oriented middleware servers into a back-end database;
to convert the vendor specific data into commonly formatted data;
to input the commonly formatted data into a front-end database;
to retrieve the commonly formatted data from the front-end database; and
to display the commonly formatted data on a user interface providing a visualization of a topology of the message oriented middleware infrastructure;
wherein, in converting the vendor specific data into the commonly formatted data, said at least one processing platform is configured:
to convert first terminology formatted in accordance with a convention of a first message oriented middleware server to terminology formatted in accordance with a convention of the commonly formatted data, wherein the first terminology represents message queue properties associated with transmission of a first plurality of messages via the first message oriented middleware server; and
to convert second terminology formatted in accordance with a convention of a second message oriented middleware server to the terminology formatted in accordance with the convention of the commonly formatted data, wherein the second terminology represents message queue properties associated with transmission of a second plurality of messages via the second message oriented middleware server;
wherein the conventions of the first and second message oriented middleware servers are different from each other;
wherein the message queue properties associated with the transmission of the first and second plurality of messages comprise at least two of: a depth of a given messaging queue of a plurality of messaging queues, a time period that one or more messages have been waiting in the given messaging queue, and a transmission time of a last message from the given messaging queue;
wherein the visualization of the topology of the message oriented middleware infrastructure comprises a pictorial depiction displaying the first and second message oriented middleware servers between one or more message producers and one or more message consumers, the pictorial depiction further displaying first and second ones of the message queue properties as corresponding to respective ones of the first and second message oriented middleware servers; and
wherein at least portions of the first and second ones of the message queue properties are displayed in the terminology formatted in accordance with the convention of the commonly formatted data.
2. The apparatus of claim 1 wherein, in retrieving the vendor specific data from the one or more message oriented middleware servers, said at least one processing platform is configured to execute one or more vendor specific software agents to connect to the one or more message oriented middleware servers.
3. The apparatus of claim 1 wherein the vendor specific data is in a native command format of the one or more message oriented middleware servers.
4. The apparatus of claim 1 wherein the commonly formatted data is in JavaScript Object Notation (JSON) format.
5. The apparatus of claim 1 wherein said at least one processing platform is further configured to store the vendor specific data in a shared network attached storage (NAS) mount prior to inputting the vendor specific data into the back-end database.
6. The apparatus of claim 1 wherein the visualization of the topology of the message oriented middleware infrastructure displays the plurality of messaging queues between the one or more message producers and the one or more message consumers.
7. The apparatus of claim 6 wherein at least two of the plurality of messaging queues respectively correspond to different message oriented middle ware servers.
8. The apparatus of claim 6 wherein the displayed commonly formatted data comprises an Internet Protocol address corresponding to at least one of the plurality of messaging queues, the one or more message producers and the one or more message consumers.
9. The apparatus of claim 6 wherein the visualization of the topology of the message oriented middleware infrastructure displays a plurality of connections between the plurality of messaging queues.
10. The apparatus of claim 6 wherein the visualization of the topology of the message oriented middleware infrastructure displays a plurality of connections between the plurality of messaging queues and at least one of the one or more message producers and the one or more message consumers.
11. The apparatus of claim 6 wherein the visualization of the topology of the message oriented middleware infrastructure displays a messaging pattern between one or more source queues and one or more target queues of the plurality of messaging queues.
12. The apparatus of claim 6 wherein the visualization of the topology of the message oriented middleware infrastructure displays a status of the first and second message oriented middleware servers respectively associated with one or more messaging queues of the plurality of messaging queues.
13. The apparatus of claim 6 wherein said at least one processing platform is configured to display the commonly formatted data associated with the given messaging queue in response to a user selecting the given messaging queue via the user interface.
14. A method comprising:
retrieving vendor specific data from one or more message oriented middleware servers of a message oriented middleware infrastructure;
inputting the vendor specific data from the one or more message oriented middleware servers into a back-end database;
converting the vendor specific data into commonly formatted data;
inputting the commonly formatted data into a front-end database;
retrieving the commonly formatted data from the front-end database; and
displaying the commonly formatted data on a user interface providing a visualization of a topology of the message oriented middleware infrastructure;
wherein converting the vendor specific data into the commonly formatted data comprises:
converting first terminology formatted in accordance with a convention of a first message oriented middleware server to terminology formatted in accordance with a convention of the commonly formatted data, wherein the first terminology represents message queue properties associated with transmission of a first plurality of messages via the first message oriented middleware server; and
converting second terminology formatted in accordance with a convention of a second message oriented middleware server to the terminology formatted in accordance with the convention of the commonly formatted data, wherein the second terminology represents message queue properties associated with transmission of a second plurality of messages via the second message oriented middleware server;
wherein the conventions of the first and second message oriented middleware servers are different from each other;
wherein the message queue properties associated with the transmission of the first and second plurality of messages comprise at least two of: a depth of a given messaging queue of a plurality of messaging queues, a time period that one or more messages have been waiting in the given messaging queue, and a transmission time of a last message from the given messaging queue;
wherein the visualization of the topology of the message oriented middleware infrastructure comprises a pictorial depiction displaying the first and second message oriented middleware servers between one or more message producers and one or more message consumers, the pictorial depiction further displaying first and second ones of the message queue properties as corresponding to respective ones of the first and second message oriented middleware servers;
wherein at least portions of the first and second ones of the message queue properties are displayed in the terminology formatted in accordance with the convention of the commonly formatted data; and
wherein the method is performed by at least one processing platform comprising at least one processing device comprising a processor coupled to a memory.
15. The method of claim 14 wherein retrieving the vendor specific data from the one or more message oriented middleware servers comprises executing one or more vendor specific software agents to connect to the one or more message oriented middleware servers.
16. The method of claim 14 wherein the visualization of the topology of the message oriented middleware infrastructure displays the plurality of messaging queues connected between the one or more message producers and the one or more message consumers, and a plurality of connections between the plurality of messaging queues.
17. The method of claim 16 wherein the visualization of the topology of the message oriented middleware infrastructure displays a status of the first and second message oriented middleware servers respectively associated with one or more messaging queues of the plurality of messaging queues.
18. A computer program product comprising a non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing platform causes said at least one processing platform:
to retrieve vendor specific data from one or more message oriented middleware servers of a message oriented middleware infrastructure;
to input the vendor specific data from the one or more message oriented middleware servers into a back-end database;
to convert the vendor specific data into commonly formatted data;
to input the commonly formatted data into a front-end database;
to retrieve the commonly formatted data from the front-end database; and
to display the commonly formatted data on a user interface providing a visualization of a topology of the message oriented middleware infrastructure;
wherein, in converting the vendor specific data into the commonly formatted data, the program code causes said at least one processing platform:
to convert first terminology formatted in accordance with a convention of a first message oriented middleware server to terminology formatted in accordance with a convention of the commonly formatted data, wherein the first terminology represents message queue properties associated with transmission of a first plurality of messages via the first message oriented middleware server; and
to convert second terminology formatted in accordance with a convention of a second message oriented middleware server to the terminology formatted in accordance with the convention of the commonly formatted data, wherein the second terminology represents message queue properties associated with transmission of a second plurality of messages via the second message oriented middleware server;
wherein the conventions of the first and second message oriented middleware servers are different from each other;
wherein the message queue properties associated with the transmission of the first and second plurality of messages comprise at least two of: a depth of a given messaging queue of a plurality of messaging queues, a time period that one or more messages have been waiting in the given messaging queue, and a transmission time of a last message from the given messaging queue;
wherein the visualization of the topology of the message oriented middleware infrastructure comprises a pictorial depiction displaying the first and second message oriented middleware servers between one or more message producers and one or more message consumers, the pictorial depiction further displaying first and second ones of the message queue properties as corresponding to respective ones of the first and second message oriented middleware servers; and
wherein at least portions of the first and second ones of the message queue properties are displayed in the terminology formatted in accordance with the convention of the commonly formatted data.
19. The computer program product according to claim 18 wherein the visualization of the topology of the message oriented middleware infrastructure displays the plurality of messaging queues connected between the one or more message producers and the one or more message consumers, and a plurality of connections between the plurality of messaging queues.
20. The computer program product according to claim 19 wherein the visualization of the topology of the message oriented middleware infrastructure displays a status of the first and second message oriented middleware servers respectively associated with one or more messaging queues of the plurality of messaging queues.