...
This view contains all existing Users and their respective connection status. Users are set as connected to an 'admin' Connection or JMX Connection if a JMX connection is made or if the a JMS Application client is started. This view also gives information about the maximum connection limit that is set for each user and the current number of connections created by the user.
Figure 5: Monitor Users View
...
This section contains the information about existing topics with the sum of each displayed on the top of the page. An Active Topic refers to a topic that contains either a publisher or a subscriber. The Select Operation drop down lists the operations that can be executed on each Topic destination selected. The Send Message operation will send persistent text messages to the topic(s) selected. The Corrupted Topics check box, if selected, displays all the corrupted topics in the MonitorTopics view; by default, the view displays all the Topics (Corrupted and Non-Corrupted Topics). The corrupted topics can be recovered and replayed using the Recover Selected Topics and Replay Messages from Topics operations respectively. More information on this feature can be found under the Handling data base corruption section.
Figure 10: MonitorTopics View
...
| Note |
|---|
As JMSProducer is a light weight object for which just a single message producer instance is created for it. So, even though multiple JMSProducers are created from the same JMSContext, it is considered as a single message producer object and while monitoring, the producer count of that context is shown as 1 (irrespective of the number of producers created). |
5. ConnectionFactories
...
MonitorConnectionFactory
...
This view lists all the connection factories along with their important properties (such as ConnectUrl, AutoUpdate, Description, and Type, Description), with a sum of each displayed at the top of the table.The ConfigureConnectionFactory operation
Figure 15: MonitorConnectionFactory View
ConfigureConnectionFactory
This view allows various operations to be performed such as Create CF, Delete Selected CF, Edit CF Properties on Connection Factories. The Edit CF Properties can be used to edit all the properties related to the selected connection factory. The Create CF option present under the Select ActionOperation drop-down list can be used to create new Connection Factories and the Delete Selected CF can be used to delete existing Connection Factories.
Figure 16: ConfigureConnectionFactory View
Export and Import CF can be used to save Connection Factories to a standard file and to create all of them in a FioranoMQ Server that is running. Import and Export CF can be used only by the 'admin' User.
...
Policies allow users to change permissions on a specific destination for a specific principal. By default, the view will show No restrictions on policies if the user had not modified any permission. If a user wants to modify any particular permission, then the user needs to use the Add Permissions option present in the Select Operations drop-down menu. A dialog box will appear with properties such as User Name, Destination Name, Positive Permissions, and Negative Permissions. After all required values are provided, click on Add button. The modified permissions will be updated in the table.
Figure 1517: Editing policies of a destination
...
The IP Access List view lists down the IP addresses which are allowed to connect to the the FioranoMQ server. By default, all the IP addresses are accepted by FioranoMQ Server, which is denoted by *.*.*.* representation. The Select Operation drop-down has two operations - Add IPAddress, for adding a new IP Address set/range to the allowed list and Remove IPAddress, for removing the IP Address entry from the list already available. While adding a new IP Address set/range, it can be added as IPV4 or IPV6 address(es).
Figure 1618: Adding IP address
7. Routes
...
If there are any routes present on the Server, those details will be displayed in the table. If no routes are present, a message "No routes available in the Server" is displayed in the table.
Figure 1719: Route
To Add or Delete a route from the Server, choose the appropriate operation from the Select Operation drop-down menu.
Figure 1820: Adding Route
Select any of the routes present in the table to display the properties of the corresponding routes in the table.
Figure 1921: Route Added
8. DashBoard
DashBoard gives a graphical representation of Time vs Threads/Connections/Memory in the x axis and y axis respectively. The entries in the y axis may be selected based on the requirement; selecting more than one of these options displays graphs one below the other.
Figure 2022: Displaying a graph of Time Vs Memory
...
A summary is present at the top of this window, denoting the total number of Durable Subscriptions for this instance of FioranoMQ Server. The Active Topics counter is updated based on the number of Topics having Active Durable Subscribers running. The Passive Topics counter is updated for Topics having Passive Durable Subscriptions.
Figure 2123: Monitor durable subscriptions
The Select Operation drop down has a single operation - 'Browse Messages' on a Durable Subscriber.
Figure 2224: Browse messages for durable subscription
...
This view lists all types of connections along with their relevant properties, such as the 'ClientID' of the connection, the 'ClientAddress' indicates the IP address from which this connection is created, 'Type' of connection whether it belongs to PTP or PUBSUB model or an MQTT Connection type, the 'Destinations' column gives the list of destinations that this connection is using in the form either creating Producers or Consumers, the 'CreationTime', the 'User' credentials used for creating this connection, and the 'Protocol' used, the 'Total PSQSize' and the 'Max PSQSize'. It has three tabs, namely "Connections", "LPC" and "API keys".
A summary is present at the top of this window denoting the total number of connections and the under each category, PTP/PUBSUB/Admin connections.
Figure 2325: Monitor connections
Connections
...
- Build Number: The build number of the client connection
- CSPBaseDir: The CSP base directory used for this connection
- ClientID: The ClientID used by this connection
- ConnectionStarted: Boolean which indicates whether or not this connection has been started
- Destination List: The list of destinations that this connection is using
- Number of Browsers: The number of Browsers created under this connection
- Number of Consumers: The number of Consumers created under this connection
- Number of Producers: The number of Producers created under this Connection
- Runtime Connection Type: The type of client runtime used to create this connection
- Server Port: The server port to which this Connection is created.
- Session Count: The number of Sessions created under this Connection
- Version Number: The FioranoMQ Version number used by the Client Connection.
- SocketInfoList: The list of sockets used by this connection
Figure 2426: Monitor connections - connection information
...
This tab lists all connections which use the LPC protocol.
Figure 2527: Monitor connections - LPC
...
This tab lists all the API keys which are used for the purpose of invoking resource methods on the server side, from the application. Some additional information such as the last-use timestamp of the API key, the IP address and the user involved in the creation of the API key are shown. Note that the API key which is being used by this instance of the WMT Angular application is highlighted in green.
Figure 2628: Monitor connections - API keys
...
MonitorSockets view contains information about all the sockets currently open within the Server. The sockets are created for each of the connections made to the server by the clients. The table gives information on Server ports, information about the client, the transport type, IP address of the Server, and whether SSL is enabled.
Figure 2729: Monitor Sockets
12. Logs
...
Lists all the loggers used in the FioranoMQ Server. Selecting any particular logger changes its level.
Figure 2830: Changing the log level of a particular logger
...
The Attributes tab lists all the attributes of the Mbean along with their values, parameter types and whether a restart of the Server is required for changes to take effect.
Figure 2931: Attribute View of JMX
Operations
This tab lists the operations present in that Mbean enabling the User to invoke these operations.
Figure 3032: Operations View of JMX
14. AdvancedProperties
This view contains frequently used properties and their values. For example, the PORT_PRPERTIES tab contains the properties RMIBasedJMXServerPort and JettyServer port. These two ports and the JMS Server listening port (which is represented by the property "SocketAcceptorPort" under the category called ConnectionManager properties, under the tab called ConnectionManager__1) need to be unique for running multiple instances of the server on the same IPAddress. All of these values can be modified.
Figure 3133: PORT_PRPERTIES tab in the AdvancedProperties View
...
MonitorLicense displays information of about all the licenses available. The License Filename list-box lists the available licenses. Selecting a license displays its corresponding license information in the table:
Figure 3234: Licenses
16. SystemProperties
SystemProperties view lists all the relevant properties of the system on which the FioranoMQ Server is hosted. These values cannot be modified through the WMT Angular.
Figure 3335: System Properties
Status Information
...
Click the information button present at the upper-right part of the SystemProperties page to view information such as the name of the logged in user, the access mode, time and date of FioranoMQ Server startup, FioranoMQ product version number, build number, and the JVM version indicates whether the server JVM is 32 or 64 bits.
Figure 3436: Status information
17. Audit Manager
...
In this view, the audit events that are recorded in the System can be monitored. To enable this, the 'Audit Filter' set for the current view needs to be changed. The figure below shows how to modify the view:
Figure 3537: Modify Audit Search Filter
...
In the Configuring Audit Policies view, the various kinds of Storage Policies which are responsible for generating Audit events are configured. In order to do this, the Modify Audit Storage Policy operation needs to be invoked after selecting one of the Storage Policies listed in the table inside the view. The storage policy will then need to be configured.
Figure 3638: ConfigureAuditPolicies > Modify Audit Storage Policy
...