1.1

Table Of Contents
2. Create a password le that contains entries for the user names and passwords you want to grant access to the
SQLFire management and monitoring system. For example:
#the sqlfiremonitor user has password Abc!@#
#the sqlfiremanager user has password 123Gh2!
sqlfiremonitor Abc!@#
sqlfiremanager 123Gh2!
3.
On each of your JMX Manager-enabled nodes, set the property jmx-manager-password-file to the
name of the le you created in step 2. This will require clients to authenticate when connecting to a JMX
Manager node in SQLFire.
4. If you wish to further restrict access to system operations, you can also set up an access le for the JMX
Manager. The access le indicates whether the users listed in the password le have the ability to read system
MBeans (monitor the system) or whether they can additionally modify MBeans (perform operations). For
example, you can dene the following:
#the sqlfiremonitor user has readonly access
#the sqlfiremanager user has readwrite access
sqlfiremonitor readonly
sqlfiremanager readwrite
5.
On each of your JMX Manager-enabled nodes, set the SQLFire property jmx-manager-access-file
to the name of the le you created in step 4. This will associate MBean permissions to the users who
authenticate to the JMX Manager node in SQLFire.
6. If desired, enable SSL for your JMX Manager connections. To enable SSL, make sure the
jmx-manager-port property is set to a non-zero value and set the jmx-manager-ssl property to
true. Then congure all other SSL-related SQLFire properties as described in Conguring SSL Communication
between the JMX Agent and Clients on page 301.
Note: The SQLFire property ssl-enabled does not apply to the JMX Manager. Use the
jmx-manager-ssl property instead.
For more information about the format of the password and access le, see
http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html.
Using a vFabric SQLFire JMX Agent
The standalone SQLFire JMX Agent provides administrative and operational monitoring along with additional
functionality such as health monitoring. You can use the JMX Agent to perform the following management
tasks.
View the distributed system and its settings.
View distributed system members.
View and modify conguration attributes.
View runtime system and application statistics.
View query and application statistics.
Monitor the health of a vFabric SQLFire system and its components.
The JMX Agent runs as a separate distributed system member, and can manage only a single distributed system.
The JMX Agent uses connectors that are specied by JMX Remote v1.0. For information about JMX, see
http://www.oracle.com/technetwork/java/javase/tech/javamanagement-140525.html.
vFabric SQLFire User's Guide294
Managing and Monitoring vFabric SQLFire