![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| ||||
Chapter 3Developing an External Java ManagerFor information about how to develop an external Java manager, see the following sections: Configuring an External Java Manager Using HTTPTo use the HTTP protocol adaptor, edit the following NMA properties in the nma.properties file:
These properties are by default true and 8081 respectively. Connecting to the NMAThe procedure for connecting to the NMA, or reconnecting to the NMA in case of a change of mastership, depends on your addressing scheme. Using the Floating AddressIf you are using the floating address to connect to the NMA running on the master node, perform the following steps to manage a failover or switchover:
Using a Physical Node AddressIf you are connecting to the NMA on each node using the node's IP address no connections will fail after failover or switchover. Using Proxy MBeansThe statistics providers in the NMA are implemented as MBeans. A set of generated proxy classes for the statistics MBeans is supplied with the NMA. A remote manager can access these statistics through the exposed MBean interfaces. The Java DMK enables predefined proxy classes of these MBeans to be instantiated in an external Java manager, and the objects to be manipulated as if they were present locally. Communication with the proxied MBeans is handled automatically. For more information about using proxy MBeans, see "MBean Proxies" in the Java Dynamic Management Kit 5.0 Tutorial. To use the supplied proxy classes, the Java DMK Remote Manager's class path must contain the path to proxies_42.jar or proxies_50.jar, depending on the version of the Java DMK runtime that you are using. The Java DMK toolkit can be used to regenerate the proxy classes. See Appendix A, MBean Naming Conventions for more information. | ||||
| ||||
![]() |