Moteurs de recherche
JavaTM 2 Platform Std. Ed. v1.5.0
Package javax.management.remoteInterfaces for remote access to JMX MBean servers.
Package javax.management.remote Description
Interfaces for remote access to JMX MBean servers. This package defines the essential interfaces for making a JMX MBean server manageable remotely. The companion document JMX Remote API completes the specification of this interface. It should be available as a PDF document in the same place as this Javadoc specification.
The JMX specification defines the notion of connectors.
A connector is attached to a JMX API MBean server and makes it
accessible to remote Java clients. The client end of a
connector exports essentially the same interface as the MBean
server, specifically the
A connector makes an MBean server remotely accessible through
a given protocol.
Typically, a connector has an address, represented by the
An address for the RMI Connector can take several forms,
as detailed in the documentation for the package
Creating a connector server
Typically, a connector server is associated with an MBean server either by registering it in that MBean server, or by supplying the MBean server as a parameter when creating the connector server.
Creating a connector client
A connector client is usually created by supplying a
Additional client or server parameters
When creating a connector client or server, it is possible to
supply an object of type
Every connection opened by a connector server has a string
identifier, called its connection id. This identifier
appears in the
Conventionally, a connection ID looks something like this:
jmxmp://clienthost:6789 clientname xxxyyyzzz
The formal grammar for connection ids that follow this convention is as follows (using the grammar notation from The Java Language Specification, Second Edition):
ConnectionId: Protocol : ClientAddressopt Space ClientIdopt Space ArbitraryText ClientAddress: // HostAddress ClientPortopt ClientPort : HostPort
Copyright 2003 Sun Microsystems, Inc. All rights reserved