1.1

Table Of Contents
Note: If you require only RMI conenctor access for JMX clients, then it is simpler to use the built-in
SQLFire JMX manager process. Use the standalone standalone Agent if you need to provide HTTP access
for JMX clients using MX4J.
Example Configuration
This gure shows a sample conguration in which the JMX agent connects applications to a vFabric SQLFire
distributed system. The architecture includes the following components.
Client applications that connect to the JMX Agent via HTTP or RMI.
A set of connectors and adapters that allow clients to contact and interact with the MBeans in the JMX Agent s
MBean server. See Conguring JMX Connectors and Adapters on page 299.
A set of SQLFire JMX MBeans that are used to manage the admin distributed system. See vFabric SQLFire
MBeans on page 303.
Starting the JMX Agent
To start the SQLFire JMX Agent, use the sqlf agent command to invoke the Agent script.
The general syntax for using sqlf agent to start an Agent is:
sqlf agent start [-Jvmarg]* [-dir=dir] [prop=value]*
295
Using Java Management Extensions (JMX)