Contents
Icon

To perform certain operations, administrator permissions are required.

Overview

Landing page and Tabular data

After logging into WMT, the landing page is the MonitorUsers view.

All the tables present in all the views can be sorted in both ascending and descending order by clicking the corresponding column header.


Figure 1: WMT landing page - MonitorUsers View

Filtering

The Filter by option present on the upper-right part of the screen is used to filter the tabular data based on the filtering column selected in the menu and the following text entered in the filter text box.


Figure 2: Filter Options

Refreshing of data

All data present in the 'Monitor' views are refreshed automatically. The 'Configure' views, on the other hand, need to be refreshed manually. For refreshing the 'Configure' view, click on any Configure view and click again on the old configure view. Only the ConfigureFMQServer view present in JMX will be refreshed automatically.

To stop refreshing the current view, click on the Stop Refresh  image. Click on the same image again to resume refreshing.


Figure 3: Stop Refresh button

Server Shutdown Warning

During interaction with the Server, if the Server shuts down due to unknown reasons, the WMT will display a warning displaying 'Disconnected from Server'. When this warning is displayed, the logout prompt will be replaced with login prompt.


Figure 3: Server Disconnected status

If the FioranoMQ server is running, click login to go directly to the previously viewed page. If the FioranoMQ server is not running, the page gets redirected to the login page.

If the server is restarted and the WMT did not interact with the server, then clicking on any operation reconnects to the server. To avoid/override this, click the same operation manually.

Common Configurations

Four links at the upper-right side of the page may be viewed:

SaveConfigurations

Saves all the modified properties to the FioranoMQ Server.

Shutdown

Closes the Server that is running. Do not connect any other application to FioranoMQ server before 'shutdown'.

Restart

Closes and restarts the Server. Do not connect any other application to FioranoMQ server before 'shutdown'. After the Server restarts, login from the browser window.

Logout

Logs out the currently logged in user from the WMT application and redirects to the homepage.

Status Information

The upper-right part of the screen displays 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 4: Status information

Using Operations

In most of the views in the left navigation panel tabs, there will be various operations available under the Select Action drop-down menu.

To use any one of these operations, select the required operation and click the Go button.


Figure 6: Select Action drop-down

WMT Views

Details of each tab in the left navigation panel of the WMT dashboard is explained in detail in the following sections.

1. Users

MonitorUsers

This view contains all existing users and their respective connection status. Users are set as connected if a JMX connection is made or if a JMS 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 7: MonitorUsers view

ConfigureUsers

This view helps to modify users. In the Select Action drop-down menu, there are actions such as Add User, Delete Selected Users, Change Password for User, set Maximum Connections per user, Import Users, and Export Users. To use any one of the actions, select the action from the Select Action drop-down menu and click the Go button.

Icon

Only the users from 'Administrators' group will have the permissions to do any of the operations mentioned above.

The Import Users and Export Users operations help copying users to another FioranoMQ Server. Export operation allows exporting of all data to a standard file present on any machine (mapping needs to be done if the file is present on a different machine). The data can be imported to any other server that starts with FioranoMQ. 


Figure 8: ConfigureUsers view 

2. Groups

ConfigureGroups

This view contains information about all groups and its members. Groups can be added using Add Group and deleted using Delete Selected Groups. For modifying members of an existing group, use Edit Members in Group after selecting the required group. The above actions are available in the Select Action drop-down menu. Select the required action and click the Go button.


Figure 9: ConfigureGroups view

Upon clicking the Go button, a dialog box pops up with certain options if the selected action is Edit Members in Group. Click the Add Members option to see the members that could be added to the group. Select the users to be removed and click the Remove Members option to remove the selected users from the group.


Figure 10: Editing Group Members

3. Topics

MonitorTopics

This view contains the information about existing topics with a summary displayed on the top of the table. The 'Active Topics' mentioned in the summary refers to a topic that contains either a publisher or a subscriber. The Select Action drop-down lists the operations that can be executed on each Topic destination selected. The SendMessage action will send persistent text messages to the Topic(s) selected. The Corrupted Topics check box, present next to the Select Action drop-down, if selected, will display 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.


Figure 11: MonitorTopics View

ConfigureTopics

This view allows all actions to be performed on topics such as Create Topic and Delete Selected Topics. The Restart Topics operation restarts a specific Topic destination to apply the changes made to its parameter values. The Shutdown Topics operation shuts down the unwanted Topic destinations.

The Edit Topic Subsystem Properties operation can be used to edit all properties related to a topic destination, whereas, the Edit Topic Subsystem Properties operation can be used to modify similar properties at the global level for all Topics.

Icon

More information on Destination Level Configurations is available in the Support for Destination Level Configuration section.


Figure 12: ConfigureTopics View

By selecting the EditTopicProperties options from the Select Action drop-down menu and clicking the Go button, it is possible to view all properties and their corresponding values. Values with a different background color need to be saved. Once saved, the server needs to be restarted to make them take effect. If the changes are done at the destination level by using the Edit Topic Properties operation, restart of that particular topic alone is enough to apply the changes. A description of the property that is selected is provided at the bottom of the overlay panel. Hover the mouse over the property text box to view the description of the property as a tool-tip. Export Topics and Import Topics can be used to save topics to a standard file as well as to create all of them in a FioranoMQ server that is running. Import Topics and Export Topics can be used only by the 'admin' User.


Figure 13: Editing Topic Properties

4. Queues

MonitorQueues

This view contains the information about existing queues with a summary displayed on the top of the table. The 'Active Queues' mentioned in the summary refers to the queues which contain either a sender or receiver. DeliverableMessages and UndeletedMessages are not updated at regular intervals. To update these values, select all the required queues and invoke 'Update Selected' or 'invoke Update All Queues' operation present in the Select Action drop-down menu. Deliverable Messages count is the number of messages yet to be delivered from the Queue, and Undeleted Messages count denotes the number of messages yet to be acknowledged by the Consumer and deleted from the data base. 

The SendMessage action will send persistent text messages to the Queue(s) selected. The Corrupted Queues check box (present next to the Select Action checkbox), if selected, will display all the corrupted queues in the MonitorQueues view; by default, the view displays all the Queues (Corrupted and Non-Corrupted Queues). The corrupted queues can be recovered and replayed using the Recover Selected Queues and the Replay Messages from Queues operations. The Purge Messages operation deletes all the messages in a selected Queue.


Figure 14: MonitorQueues View

The Browse Messages operation can be handy in browsing messages on a selected Queue and viewing its properties. When 'Browse Messages' operation is invoked, a new dialogue box is popped up to view the Messages and its properties. 


Figure 15: Browse Messages operation 

ConfigureQueues

This view allows all operations to be performed on queues such as Create Queue and Delete Selected Queues. The Restart Queues operation restarts a specific Queue destination to apply the changes made to its parameter values. The Shutdown Queues operation shuts down the unwanted Queue destinations

The Edit Queue Properties operation can be used to edit all properties related to a queue destination, whereas, the Edit Queue Subsystem Properties operation can be used to modify similar properties at the global level for all Queues. 

Icon

More information on Destination Level Configurations is available in the Support for Destination Level Configuration section.

By using Edit Queue Properties option present under the Select Action drop-down menu it is possible to view all properties and their corresponding values. Values with different background colour need to be saved. Once saved the Server needs to be restarted to make them take effect. If the changes are done at the destination level by using the Edit Queue Properties operation, restart of that particular queue alone is enough to apply the changes. Description of each property that is selected is provided at the bottom of the overlay panel. The mouse may be moved over the textbox to view the description of the property. Export Queues and Import Queues can be used to save queues to a standard file as well as to create all of them in a FioranoMQ Server that is running. Import Queues and Export Queues can be used only by the 'admin' User.

Icon

As JMSProducer is a light weight object,we create a single message producer instance 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, Type, Description). A summary is present at the top of the table.


Figure 16: 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 operation can be used to edit all the properties related to the selected connection factory. The Create CF option present under the Select Action 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 17: ConfigureConnectionFactory View

The Export CF operation and Import CF operation 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 CF and Export CF can be used only by the 'admin' User.

6. Policies

ConfigurePolicies

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 user had not modified any permission. To modify any particular permission, use the Add Permission option present in the Select Action drop-down menu. A pop-up window will appear with properties such as UserName, Destination Name, Positive Permissions, Negative Permissions, and Type of Permission. After all the required values are selected, click the OK button. The modified permissions will be shown in the table.


Figure 18: Editing policies of a destination

Click any row and view the permissions set on a specific destination.

ConfigureIPAccessList

This view lists down the IP addresses which are allowed to connect to the FioranoMQ Server. By default, all the IP addresses are accepted by FioranoMQ Server, denoted by *.*.*.* representation. The Select Action drop-down has two operations - The Add IPAddress operation, for adding a new IP Address set/range to the allowed list and the Remove IPAddress operation, for removing the IP Address entry from the list already available. While adding a new IP Address set/range, select the IP Type to add it as IPV4 or IPV6 address(es).


Figure 19: ConfigureIPAccessList view

7. AuditManager

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.  Use the Modify Audit Search Filter operation to perform the same.


Figure 20: Modify Audit Search Filter

ConfigureAuditPolicies

In this 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 action 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: The Modify Audit Storage Policy dialog box

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. The figure below shows how to deactivate the storage policy:.


Figure 22: De-activate Storage Policy message

For more information on Audit Management, please refer to the Audit Management section of this document.

8. Routes

A Route enables the transport of messages between destinations. A message arriving at one destination can be made available to another provided a route exists between the two destinations.

ConfigureRoutes

This view contains information about the properties of the route manager. These are the properties of the individual routes present on the server.

If there are any routes present on the Server, they will be displayed in the Route GUID box. If no routes are present, the message "No routes available in the Server" is displayed on the page.


Figure 23: Message saying there are no routes available in the server

To Add or Delete a route from the server, the appropriate action must be chosen from the Select Action drop-down menu.


Figure 24: Adding a route

Select a route name from the Route GUID drop-down to display the properties of that route in the table.


Figure 25: Route Added

9. DashBoard

MonitorPerformanceGraphs

The MonitorPerformanceGraphs view under Dashboard gives a graphical representation of Time vs Connections/Memory/Threads 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 after the other.


Figure 26: Displaying a graph of Time Vs Memory

10. DurableSubscriptions

MonitorDurableSubscription

This view contains all existing durable subscribers listed along with its 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 table, 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 27: MonitorDurableSubscription view

The Select Action drop down has a single operation, 'Browse Messages' on a Durable Subscriber. 


Figure 28: ConfigureDurableSubscription view

ConfigureDurableSubscription

This view contains all durable subscriber names in the form of subscriberID::clientID. Messages can be unsubscribed or purged for passive durable subscribers from this view. Any operations involving active durable subscribers throw a warning message.

11. Connections

MonitorConnections

This view lists all types of connections along with their relevant properties, such as the 'ClientID' of the connection, the 'ClientAddress' which 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 of either creating Producers or Consumers, the 'CreationTime', the 'User' credentials used for creating this connection, the 'Protocol' used, the 'Total PSQSize' and the 'Max PSQSize'. It has two tabs, namely "Connections" and "LPC".

A summary is present at the top of this table denoting the total number of connections and the under each category, PTP/PUBSUB/Admin connections.


Figure 29: MonitorConnections view

When clicked on each Connection, it displays the following additional Connection Information:

  • Build Number: The build number of the client connection
  • CSPBaseDir: The CSP base directory used for this connection
  • Client ID: The ClientID used by this connection
  • ConnectionStarted: Boolean which indicates whether or not this connection has been started
  • Destinations: 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 30: ConfigureConnections view

LPC

This tab lists all connections which use the LPC protocol.

ConfigureConnections

This view allows the disconnection of a connection based on the clientID.

12. Sockets

MonitorSockets

This 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 31: MonitorSockets view

13. Logs

MonitorLogs

This view allows the user to fetch details of logs, view log details, and clear log details.


Figure 32: MonitorLogs view

ConfigureLogs

This view lists all the loggers used in the FioranoMQ Server; select any particular logger to change its level.


Figure 33: Changing log level of a particular logger

14. JMX

ConfigureFMQServer

This view lists all the Mbeans along with their attributes and operations. Mbeans are listed in this hierarchical view with a brown color bullet.

When a particular Mbean is selected, a overlay panel containing two tabs is displayed with an option to invoke these attributes. The Attributes tab lists all the attributes of the Mbeans along with their values, parameter types and whether a restart of the Server is required for changes to take effect.


Figure 34: Attribute View of JMX

The Operations tab lists all the operations present in the Mbean along with their details such as OperationName, Impact, ReturnType, and isRestartRequired (whether a restart of the Server is required for changes to take effect) and an option to invoke these operations.


Figure 35: Operations View of JMX

15. AdvancedProperties

ConfigureAdvancedProperties

The ConfigureAdvancedProperties view contains frequently used properties and their values. For example, the Port Properties tab contains the properties RMIBasedJMXServerPort and JettyServerPort. These two ports and the JMS Server listening port (which is represented by the property "SocketAcceptorPort" listed in the ConnectionManager__1 tab under the ConectionManager 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 36: AdvancedProperties View

16. Licenses

MonitorLicense

The MonitorLicense view displays information about all the licenses available. Selecting a license lists its corresponding license information below.


Figure 37: Licenses

17. SystemProperties

SystemProperties

This view lists the 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.


Figure 38: System Properties

18. Dispatcher

ConfigureDispatcher

This tab is available in the left navigation panel only when logged into the web console of a dispatcher-enabled server.

A Dispatcher distributes the messages received to different Servers that are connected to it. The Dispatcher performs the load balancing function of a network connected to FioranoMQ Servers.

This view contains information about the properties of the Dispatcher Manager and the properties of the Servers to which it dispatches messages. The Server URL drop-down contains the list of server URLs to which the Dispatcher can dispatch messages. On selecting a URL, its properties are displayed on the table.


Figure 39: Dispatcher

To Add or Delete or set a preferred dispatcher server, the appropriate action must be chosen from the Select Action drop-down menu.


Figure 40: AddDispatcher Server

19. HighAvailability

This view contains properties related to the HA Servers.

If the HA server is running this view displays all relevant properties for HA. Please note that the word 'remote server' means backup server, it can be either of HAPrimary or HASecondary Servers. 


Figure 41: HA view

20. StandAloneBridge

This tab is available only when logged into the web console of a Server running on the StandAloneBridge profile.

A Bridge transmits a message received on one queue (source queue) to another queue (target queue).

ConfigureBridge view lists all the Bridges currently available on the server. The Select Action drop-down menu contains various options , such as:

  • View Bridge Attributes
  • Add Link
  • Delete Links
  • View Link Configuration
  • Edit Link Configuration
  • Add Channel
  • Delete Channels
  • View Channel Configuration


Figure 42: StandAloneBridge

AddLink Attributes

To add a link select Action drop-down, choose the AddLink action and click the Go button. Following are the parameters present in AddLink window:

LinkName

The name of the link which is to be added.
Default Value:
SampleLink

SourceServerInitialContextFactory

The class name of the initial context factory which is used to open connection with the source server.
Default Value:
fiorano.jms.runtime.naming.FioranoInitialContextFactory

SourceServerName

The name of the source server.
Default Value:
SourceServer

SourceServerPassword

The password which the bridge uses to connect to the source server.
Default Value:
senna- The default password

SourceServerProtocol

The transport protocol used for establishing a connection with the source server.
Default Value:
TCP - The default transport protocol used for the connection.

SourceServerQCF

The connection factory with which the connection is to be established.
Default Value:
primaryQCF - The default connection factory used for the connection.

SourceServerSecurityCredentials

The SecurityCredentials (password) used for connecting to the source server.
Default Value:
Anonymous - The default password

SourceServerSecurityManager

ServerSecurityManager of the source server linked by the bridge.
Default Value:
null - No server Security Manager

SourceServerSecurityPrincipal

The SecurityPrincipal (username) used for connecting to the source server.
Default Value:
Anonymous- The default username

SourceServerType

Need to mention the type of the source server.
Default Value:
JMS - The default type of server

SourceServerURL

The URL of the source server should be given here.
Default Value:

http://localhost:1856

- The default provider URL of the server.

SourceServerUserName

The UserName which the bridge uses to connect to the source server.
Default Value:
ayrton- The default bridge user name

TargetServerInitialContextFactory

The class name of the initial context factory which is used to open connection with the target server.
Default Value:
fiorano.jms.runtime.naming.FioranoInitialContextFactory

TargetServerName

The name of the target server.
Default Value:
TargetServer

TargetServerPassword

The password which the bridge uses to connect to the target server.
Default Value:
senna- The default password

TargetServerProtocol

The transport protocol used for establishing a connection with the target server.
Default Value:
TCP - The default transport protocol used for the connection.

TargetServerQCF

The connection factory with which the connection is to be established.
Default Value:
primaryQCF - The default connection factory used for the connection.

TargetServerSecurityCredentials

The SecurityCredentials (password) used for connecting to the target server.
Default Value:
Anonymous - The default password

TargetServerSecurityManager

ServerSecurityManager of the target server linked by the bridge.
Default Value:
null - No server Security Manager

TargetServerSecurityPrincipal

The SecurityPrincipal (username) used for connecting to the target server.
Default Value:
Anonymous- The default username

TargetServerType

Need to mention the type of the target server.
Default Value:
JMS - The default type of server

TargetServerURL

The URL of the target server should be given here.
Default Value:

http://localhost:1856

- The default provider URL of the server.

TargetServerUserName

The UserName which the bridge uses to connect to the target server.
Default Value:
ayrton- The default bridge user name

To perform any of the actions listed in the Select Action drop-down, choose the appropriate action and click the Go button.


Figure 43: AddLink

AddChannel Attributes

To add a channel to a link, select a link and then click the Select Action drop-down, choose the Add Channel action and click the Go button. Following are the parameters present in AddChannel overlay panel:

AddSourceQueueParams

Specify the source queue parameters.
Default Value:undefined

AddTargetQueueParams

Specify the target queue parameters.
Default Value:undefined

ChannelName

The name of the channel which is to be added.
Default Value:
channel1

SourceQueueMessageSel

The message selector of the source queue. Allows the user to set message selectors for the
source queues which have been linked using bridges.
Default Value:
null - No message selector is used

SourceQueueName

The name of the queue present in source server which is to be linked by the bridge.
Default Value:
primaryQueue - The name of the queue which the bridge links.

TargetQueueMessageSel

The message selector of the target queue. Allows the user to set message selectors for the
target queues which have been linked using bridges.
Default Value:
null - No message selector is used

TargetQueueName

The name of the queue present in target server which is to be linked by the bridge.
Default Value:
secondaryQueue - The name of the queue which the bridge links.

21. StandAloneRepeater

This tab is available when logged into the web console of a Server running on the StandAloneRepeater profile.

A Repeater transmits a message received on one topic (source topic) to another topic (target topic).

ConfigureRepeater

This view lists all the Repeaters currently available on the server. The Select Action drop-down contains various options such as:

  • View Repeater Attributes
  • Show Repeater Info
  • Add Link
  • Delete Links
  • View Link Configuration
  • Edit Link Configuration
  • Add Link Topic
  • Show Link Topic Configuration
  • Remove Link Topic
  • Add Reply Topic
  • Show Reply Topic Configuration
  • Remove Reply Topic


Figure 44: StandAloneRepeater

To perform any of the actions listed in the Select Action drop-down, choose the appropriate action and click the Go button.


Figure 45: View Link Configuration

Adaptavist ThemeBuilder EngineAtlassian Confluence