SDX 6.4.x Application Library Guide > Activating Services Through SOAP > Monitoring Dynamic Service Activator

Monitoring Dynamic Service Activator

SDX owners can use Manageable JavaBeans (MBeans) to monitor Dynamic Service Activator. MBeans are a feature of the Java Management Extension (JMX) software.

If you want to monitor the MBeans, your Web application server must include a JMX agent. Dynamic Service Activator creates MBeans and makes the information available to the JMX agent. The way you view the MBeans depends on the particular Web application server and the interfaces that its JMX agent provides.

Monitoring the Performance of Dynamic Service Activator

Dynamic Service Activator creates one instance of an MBean called GalMgmt to provide information about their performance. Table 8 shows the information that this MBean provides.

You can reset the values of many GalMgmt MBean properties to zero. To do so, execute the reset counters operation through the mechanism that the JMX agent for your Web application server provides. Table 8 shows which counters the reset operation affects.

 Table 8:  Information That the GalMgmt MBean Provides 

 Name of Property
 Description
 Ability to Reset to Zero

 webServiceName

 Name of the Web application (for example, ScriptInvoker)

 No


 upTime

 Number of milliseconds since the Web application server initialized the Web application

 No


 numSaeCallsAttempted

 Number of times the Web application has attempted to contact an SAE through CORBA

 Yes


 numSaeCallsInProgress

 Total number of CORBA calls that are currently in progress to SAEs

 Yes


 numSaeCallsSucceeded

 Total number of successful CORBA calls to SAEs

 Yes


 numSaeCallsFailed

 Total number of failed CORBA calls to SAEs

 Yes


 saeCallTimeAvg

 For the 100 most recent (successful and failed) CORBA calls to SAEs, the average time (in milliseconds) of the CORBA call

 Yes


 saeCallTimeMin

 For the 100 most recent (successful and failed) CORBA calls to SAEs, the minimum time (in milliseconds) of the CORBA call

 Yes


 saeCallTimeMax

 For the 100 most recent (successful and failed) CORBA calls to SAEs, the maximum time (in milliseconds) of the CORBA call

 Yes



 

Monitoring the SOAP Operations

You can monitor SOAP operations through the GalOpMgmt MBeans. Dynamic Service Activator creates one instance of an MBean called GalOpMgmt for each operation that is publicly available in its SOAP interface. For information about available SOAP operations, see API for Dynamic Service Activator. Table 9 shows the information that this MBean provides.

You can reset the values of many GalOpMgmt MBean properties to zero. To do so, execute the reset counters operation through the mechanism that the JMX agent for your Web application server provides. Table 9 shows which counters the reset operation affects.

 Table 9:  Information That the GalOpMgmt MBean Provides 

 Name of MBean
 Description
 Ability to Reset to Zero

 webServiceName

 Name of the Web application (for example, ScriptInvoker)

 No


 operationName

 Name of the operation provided by the Web application (for example, invokeScript)

 No


 numReqs

 Total number of SOAP requests for this operation

 Yes


 numReqsInProgress

 Number of current SOAP requests for this operation

 Yes


 numReqsDenied

 Number of SOAP requests for this operation that the Web application rejected because of access controls

 Yes


 numReqsSucceeded

 Number of SOAP requests for this operation that the Web application accepted and completed

 Yes


 numReqsFailed

 Number of SOAP requests for this operation that the Web application accepted but could not process because of errors or misconfigurations

 Yes


 reqTimeAvg

 For the 100 most recent (successful, failed, and denied) SOAP requests to this operation, the average time (in milliseconds) that the Web application took to respond to the request

 Yes


 reqTimeMin

 For the 100 most recent (successful, failed, and denied) SOAP requests to this operation, the minimum time (in milliseconds) that the Web application took to respond to the request

 Yes


 reqTimeMax

 For the 100 most recent (successful, failed, and denied) SOAP requests to this operation, the maximum time (in milliseconds) that the Web application took to respond to the request

 Yes



 

Monitoring the NIC Proxies

All NIC proxies create one instance of an MBean called NicProxyMgmt to provide information to a JMX agent. For information, see SDX Network Guide: SAE, Juniper Networks Routers, and NIC, Chapter 5, Locating Subscriber Information.