...
| Tip |
|---|
More information on Destination Level Configurations is available in the Support for Destination Level Configuration section. |
By using the Edit Queue Subsystem Properties operation present under the Select Operation drop-down menu, it is possible to view all queue subsystem properties and their corresponding values. When properties highlighted in Bold are modified, the changes need to be saved and the server must also be restarted for them to apply the changes. If the changes are done at the destination level by using the Edit Queue Properties operation, restart of that particular queue alone would be enough to apply the changes. The mouse can be hovered over the text box to view the description of any property. The Export Queues and Import Queues operations can be used to save queues to a standard file as well as to create all of them in the FioranoMQ server that is running.
...
Figure 19: Adding IP address
7. Audit Manager
Using the Audit Manager view it is possible to configure the Audit Storage Policies as well as monitor the audit events recorded in the Server.
MonitorAuditEvents
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 20: Modify Audit Search Filter
ConfigureAuditPolicies
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 21: A ModifyAuditEvent policy
The recording of Audit events can be stopped by configuring the same storage policy that is used for enabling Audit Events. In order to do this, the action 'De-activate Storage Policy' needs to be invoked after selecting the Storage Policy which is to be de-activated.
| Tip |
|---|
For more information on Audit Management, please refer to the Audit Management section. |
8. Routes
A Route enables the transport of messages between destinations. A message arriving at one destination can be made available to another if a route exists between the two destinations.
...
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 2022: Route added in the list
To Add or Delete a route from the Server, choose the appropriate operation from the Select Operation drop-down menu.
Figure 2123: Adding Route
Select any of the routes present in the table to display the properties of the corresponding routes in the table.
Figure 2224: Route properties
...
9. Dashboard
MonitorPerformanceGraphs
The MonitorPerformanceGraphs view under 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 2325: Displaying a graph of Time Vs Memory
...
10. DurableSubscribers
MonitorDurableSubscriber
This view contains all existing durable subscribers listed along with other relevant information such as Subscription state, the Topic destination it is subscribing to, the deliverable number of messages for each durable Subscriber, the ClientId of the connection, and if it is a Shared Subscriber or not, and the number of active consumers under each Shared Subscriber.
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 2426: Monitor durable subscriptions
The Select Operation drop down has a single operation - 'Browse Messages' on a Durable Subscriber.
Figure 2527: Browse Messages operation for durable subscription
...
| Tip | ||
|---|---|---|
| ||
Pressing CTRL key while selecting a table entry in either the MonitorDurableSubscription or ConfigureDurableSubscription component instantly navigates to the same table entry in the other component. |
...
11. Connections
MonitorConnections
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 2628: MonitorConnections view
...
- 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 2729: Connection information
LPC
This tab lists all connections which use the LPC protocol.
Figure 2830: MonitorConnections - LPC tab view
...
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 2931: MonitorConnections - API keys tab view
...
| Tip | ||
|---|---|---|
| ||
Pressing CTRL key while selecting a table entry in either the MonitorConnections or ConfigureConnections component instantly navigates to the same table entry in the other component. This can be done through both the Connections tab and the API keys tab. |
...
12. Sockets
MonitorSockets
The 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 3032: MonitorSockets view
...
13. Logs
MonitorLog
This view allows the user to fetch details of logs, view log details, and clear log details.
...
This view lists all the loggers used in the FioranoMQ Server. Selecting any particular logger changes its level.
Figure 3133: Changing the log level of a particular logger
...
14. JMX
ConfigureFMQServer
The ConfigureFMQServer view under JMX lists all the Mbeans along with their attributes and operations. Navigate to the specific Mbean and click on it to display its Attributes and Operations. Click the Invoke button to invoke the particular attribute/operation.
...
The Attributes tab lists all the attributes present in the Mbean along with their details such as AttributeName, Type, DefaultValue and isRestatRequired (whether a restart of the Server is required for changes to take effect) and an option to invoke these attributes.
Figure 3234: Attribute View of JMX
Operations
This tab lists all the operations present in the Mbean along with their details such as OperationName, Impact, ReturnType, and isRestatRequired (whether a restart of the Server is required for changes to take effect) and an option to invoke these operations.
Figure 3335: Operations view of JMX
...
15. AdvancedProperties
The ConfigureAdvancedProperties view under AdvancedProperties 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" listed in the ConnectionManager__1 tab under the CONNECTIONMANAGER PROPERTIES category) need to be unique for running multiple instances of the server on the same IPAddress. All of these values can be modified.
Figure 3436: PORT_PROPERTIES tab in the AdvancedProperties view
...
16. Licenses
MonitorLicense
The MonitorLicense view displays information of about all the licenses available. Selecting a license lists its corresponding license information below
Figure 3537: License information
...
17. SystemProperties
The SystemProperties view lists all the relevant properties and the corresponding values of the system on which the FioranoMQ Server is hosted. These values cannot be modified through the WMT Angular.
Figure 3638: System Properties
17. Audit Manager
Using the Audit Manager view it is possible to configure the Audit Storage Policies as well as monitor the audit events recorded in the Server.
MonitorAuditEvents
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 37: Modify Audit Search Filter
ConfigureAuditPolicies
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 38: A ModifyAuditEvent policy
The recording of Audit events can be stopped by configuring the same storage policy that is used for enabling Audit Events. In order to do this, the action 'De-activate Storage Policy' needs to be invoked after selecting the Storage Policy which is to be de-activated.
| Tip |
|---|
For more information on Audit Management, please refer to the Audit Management section. |