FMQ Topics Test

This test reports general statistics pertaining to the topics on a FioranoMQ server.

Target of the test : A FioranoMQ Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every topic on a FioranoMQ server.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The IP address of the host for which this test is to be configured.

Port

The port at which the specified host listens.

HomeDir

The location of the directory in which the FioranoMQ server has been installed. For example, the HomeDir for a Windows installation of the FioranoMQ server will be of the following format: C:\PROGRA~1\Fiorano\FIORAN~1.0. The format for a Unix installation will be: /user/egurkha/Fiorano/FioranoMQ7.0.

SvrBinDir

The full path to the bin directory of the FioranoMQ server installation that contains the file ConnectionManager.xmlin FioranoMQ server 6.0, or the FMQListeners.xmlin the FioranoMQ7.0. These files, which are required for starting the respective FioranoMQ servers, also help the test in determining the version number of the FioranoMQ server (whether 6 or 7). For example, the svrbindir for a Windows installation of the server will be of the format: C:\PROGRA~1\Fiorano\FIORAN~1.0\bin. The format for Unix installations will be: /user/egurkha/Fiorano/FioranoMQ7.0/bin.

ServerMode

The mode in which the FioranoMQ server is running. This parameter can take any of the following values:

  • tcp: In this mode, the FioranoMQ server accepts non-secure TCP connections. This is the default value for ServerMode parameter.
  • ssljsse: In this mode, the FioranoMQ server accepts secure connections which are serviced using Sun's JSSE implementation.
  • sslphaos: In this mode, the FioranoMQ server accepts secure TCP connections and secure connections using Phaos.
  • http: In this mode, the FioranoMQ server accepts non-secure HTTP connections.
  • httpjsse: In this mode, the FioranoMQ server accepts secure HTTPS connections which are serviced using Sun's JSSE implementation.
  • httpphaos: In this mode, the FioranoMQ server accepts secure HTTPS connections using Phaos.

AdminID

The user name of the FioranoMQ server's administrator. The default is "admin".

Admin Password

The password corresponding to the specified admin user.

Confirm Password

Confirm the password by retyping it here.

ACF

ACF stands for Admin Connection Factory object. Specify the name of an existing ACF object in this text box. This object is used to obtain a handle to an Admin connection.

TCF

TCF stands for Topic Connection Factory object. Specify the name of an existing TCF object in this text box.  This object is used to set up a connection with the provider.

TrustStore

The truststore or keystore database which the JVM uses to verify certificates. For example, this parameter can take the value c:\FioranoMQ\bin\jssecacerts on Windows (on Unix, the path would be expressed as: /user/egurkha/Fiorano/FioranoMQ7.0/bin/jssecacerts), where jssecacerts is the truststore database which the JVM uses.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Note:

Refer to How to find the ServerMode, ACF and TCF parameters for a FioranoMQ server? section to know the values of the ServerMode, ACF and TCF test parameters.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Total durable subscribers

The total durable subscribers for this topic. Messages meant for a durable subscriber are stored in the persistent cache even when the subscriber is inactive.  These messages are delivered for durable subscribers when they connect to the FioranoMQ server.

Number

If the total number of durable subscribers is high, then we can expect the total durable messages to be stored on the FioranoMQ also to be relatively on the higher side.

Total deliverable messages

The number of messages deliverable (undelivered+redeliverable) to the durable subscribers of this topic

Number

If the value of this measure is consistently high, it indicates that the receivers are not receiving the messages stored in the topic. The reason is that the client may not be active to receive messages or the client may be unable to connect to the server. The detailed diagnosis of this measure, if enabled, provides the details of the messages still to be delivered to a particular topic.

The detailed diagnosis of this measure, if enabled, reveals information pertaining to the messages still to be delivered to a particular topic. The details displayed include the subscriber to which the message(s) is addressed to, the client from which the message(s) originated, and the number of undelivered messages.

How to find the ServerMode, ACF and TCF parameters for a FioranoMQ server?

To know the values for ServerMode, ACF and TCF parameters for a FioranoMQ server 6.0, first, open the ConnectionManager.xml file in the <FIORANO_INSTALL_DIR>/bin directory. You will find the following section within:

<FMQConnectionFactories>

<ClientConnectionFactories>

<ConnectionFactoryInfo type="HTTPS_SUN">

<URL>http://localhost:1856</URL>

<SSLVendor>Sun</SSLVendor>

<SecurityManager>fiorano.jms.ex.sm.def.DefaultJSSESecurityManager</SecurityManager>

<ConnectionManager>

                              <ClassName>fiorano.jms.cm.def.SocketReadHandlerDefImpl</ClassName>

                        </ConnectionManager>

<ConnectionFactoryName fmq_type='TOPIC'>primaryTCF</ConnectionFactoryName>

                        <ConnectionFactoryName fmq_type='TOPIC'>secondaryTCF</ConnectionFactoryName>

                        <ConnectionFactoryName fmq_type='QUEUE'>primaryQCF</ConnectionFactoryName>

                        <ConnectionFactoryName fmq_type='QUEUE'>secondaryQCF</ConnectionFactoryName>

<ConnectionFactoryName fmq_type='UNIFIED'>primaryCF</ConnectionFactoryName>                 </ConnectionFactoryInfo>

        </ClientConnectionFactories>

<AdminConnectionFactories>

<ConnectionFactoryInfo type="HTTPS_SUN">

          <URL>http://localhost:1857</URL>

   <SSLVendor>Sun</SSLVendor>

<SecurityManager>fiorano.jms.ex.sm.def.DefaultJSSESecurityManager</SecurityManager>

                   <ConnectionManager>

                       <ClassName> fiorano.jms.cm.def.SocketReadHandlerDefImpl</ClassName>

                   </ConnectionManager>

<ConnectionFactoryName fmq_type='ADMIN'>primaryACF</ConnectionFactoryName>

</ConnectionFactoryInfo>

</AdminConnectionFactories>

</FMQConnectionFactories>

Note the lines marked in Bold. The first of these lines reads as follows: <ConnectionFactoryInfo type="HTTPS_SUN">. If the ConnectionFactoryInfo type is HTTPS_SUN, then the ServerMode will be httpjsse. For the other ServerModes, the corresponding ConnectionFactoryInfo type will be:

ConnectionFactoryInfo Type ServerMode
HTTP http
HTTPS_PHAOS Httpphaos
SUN_SSL Ssljsse
PHAOS_SSL Sslphaos

The next line marked in Bold, reads as follows: <ConnectionFactoryName fmq_type='TOPIC'>primaryTCF</ConnectionFactoryName>. Here, the term primaryTCF indicates the name of the TCF object, and the same has to be provided as the TCF parameter.

The last line marked in Bold, reads as follows: <ConnectionFactoryName fmq_type='ADMIN'>primaryACF</ConnectionFactoryName>. Here, the term primaryACF indicates the name of the ACF object, and the same has to be provided as the ACF parameter.

To know the values for ServerMode, ACF and TCF for a FioranoMQ server 7.0, open the AdminTool.xml file in the <FIORANO_INSTALL_DIR>/bin directory. You will find the following section within:

<AdminToolCfg>

<Param Name="LOG_MANAGER">fiorano.jms.log.def.LogManagerImpl</Param>

        <Param Name="REPEATER_ENABLED">yes</Param>

<Param Name="REPEATER_TOPIC">REPEATER_QUERY_TOPIC</Param>

<Param Name="REPEATER_REQUEST_TIMEOUT">10000</Param>

<Param Name="ConfigurationTab">true</Param>

<Param Name="showalltracecomponents">true</Param>

<Param Name="TransportProtocol">HTTP</Param>

<Param Name="SYSTEM_MESSAGESNOOPER_TOPIC">SYSTEM_MESSAGESNOOPER_TOPIC</Param>

 

<Param Name="SYSTEM_MESSAGESNOOPER_QUEUE">SYSTEM_MESSAGESNOOPER_QUEUE</Param>

<FioranoMQServer  URL="http://localhost:1856">

<AdminCF Name="primaryACF"></AdminCF>

<TopicCF Name="primarytcf"></TopicCF>

<QueueCF Name="primaryqcf"></QueueCF>

</FioranoMQServer>

</AdminToolCfg>

Note the lines marked in Bold. The first of these lines reads as follows: <Param Name="TransportProtocol">HTTP</Param>. If the TransportProtocol is HTTP then the ServerMode will be http. For the other ServerModes, the corresponding TransportProtocol will be:

Transportprotocol ServerMode
HTTPS_SUN httpjsse
HTTPS_PHAOS httpphaos
SUN_SSL ssljsse
PHAOS_SSL sslphaos

The next line marked in Bold, reads as follows: <AdminCF Name="primaryACF"></AdminCF>. Here, the term primaryACF indicates the name of the ACF object, and the same has to be provided as the ACF parameter.

The last line marked in Bold, reads as follows: <TopicCF Name =”primaryTCF”></TopicCF>. Here, the term primaryTCF indicates the name of the TCF object, and the same has to be provided as the TCF parameter.