1.1.1

• ManagerMBean with Scope=ALL, which allows various distributed system-wide operations.
• Proxy to MBeans on managed nodes.
• Built-in platform MBeans.
Starting a JMX Manager
JMX Manager nodes are members that manage other SQLFire members (as well as themselves). A JMX Manager
node can manage all other members in the distributed system.
To convert a managed node to a JMX Manager you configure the SQLFire properties jmx-manager=true
and jmx-manager-start=true in the sqlfire.properties file or on the command line when you
start the member.
To start a locator as a JMX Manager:
sqlf locator start -jmx-manager=true -jmx-manager-start=true
A server can also become a JMX Manager when started. However, you should only have one JMX Manager per
distributed system.
After the member becomes a JMX Manager, all other jmx-manager-* configuration properties listed in
Configuring a JMX Manager are applied.
Configuring a JMX Manager
JMX manager properties are configured as follows.
DefaultDescriptionProperty
false
If true then this member can become a JMX Manager. All other
jmx-manager-* properties are used when it does become a JMX
jmx-manager
Manager. If this property is false then all other jmx-manager-* properties
are ignored.
not set
By default the JMX Manager allows full access to all MBeans by any client. If
this property is set to the name of a file, then it can restrict clients to only reading
jmx-manager-access-file
MBeans; they cannot modify MBeans. The access level can be configured
differently in this file for each user name defined in the password file. For more
information about the format of this file see Oracle's documentation of the
com.sun.management.jmxremote.access.file
system property. Ignored if jmx-manager is false or if
jmx-manager-port is zero. See Setting Up JMX Manager
Authentication on page 297.
not setBy default, the JMX Manager when configured with a port listens on all the
local host's addresses. You can use this property to configure which particular
jmx-manager-bind-address
IP address or host name the JMX Manager will listen on. This property is ignored
if jmx-manager is false or jmx-manager-port is zero.
not setHostname given to clients that ask the locator for the location of a JMX Manager.
By default the IP address of the JMX Manager is used. However, for clients on
jmx-manager-hostname-for-clients
a different network, you can configure a different hostname to be given to clients.
Ignored if jmx-manager is false or if jmx-manager-port is
zero.
8080 (not used)Not used. If you require HTTP access for JMX management, use a standalone
JMX Agent instead of a manager node. See Using a vFabric SQLFire JMX
Agent on page 298.
jmx-manager-http-port
not setBy default the JMX Manager allows clients without credentials to connect. If
this property is set to the name of a file, only clients that connect with credentials
jmx-manager-password-file
that match an entry in this file will be allowed. Most JVMs require that the file
vFabric SQLFire User's Guide296
Managing and Monitoring vFabric SQLFire