Appendix C. Probes 207Field ValuePort* 80Pathname* /server-statusUserAgent* NOCpulse-ApacheUptime/1.0UsernamePasswordTimeout* 15Table C-3. Apache::Uptime settingsC.3. BEA WebLogic 6.x and higherThe probes in this section (with the exception of JDBC Connection Pool) can be configuredto monitor the properties of any BEA WebLogic 6.x and higher server (Administration orManaged) running on a given host, even in a clustered environment. Monitoring of a clusteris achieved by sending all SNMP queries to the Administration Server of the domain andthen querying its Managed Servers for individual data.In order to obtain this higher level of granularity, the BEA Domain Admin Server pa-rameter must be used to differentiate between the Administration Server receiving SNMPqueries and the Managed Server undergoing the specified probe. If the host to be probedis the Administration Server, then the BEA Domain Admin Server parameter can be leftblank, and both the SNMP queries and the probe will be sent to it only.If the host to be probed is a Managed Server, then the IP address of the AdministrationServer should be provided in the BEA Domain Admin Server parameter, and the Man-aged Server name should be included in the BEA Server Name parameter and appendedto the end of the SNMP Community String field. This causes the SNMP queries to besent to the Administration Server host, as is required, but redirects the specific probe to theManaged Server host.It should also be noted that the community string needed forprobes run against Managed Server hosts should be in the form ofcommunity_prefix@managed_server_name in order for the SNMP query toreturn results for the desired Managed Server. Finally, SNMP must be enabled on eachmonitored system. SNMP support can be enabled and configured through the WebLogicConsole.Please see the documentation that came with your BEA server or information on the BEAwebsite for more details about BEA’s community string naming conventions: http://e-docs.bea.com/wls/docs70/snmpman/snmpagent.html
