This page lists the predefined data sources that are available with Performance Explorer and outlines specific installation and configuration requirements for each server type that Performance Explorer can monitor.
System | Installation and Configuration Requirements |
---|---|
.NET | .NET CLR and ASP.NET using PerfMon |
Active Server Pages |
Performance Explorer can monitor Active Server Pages without custom configuration. Varying counters can be displayed, depending on which Internet
Information Server version is installed.
|
Apache | The monitoring of Apache Web Servers is supported for the following operating systems (using rexec): HP-UX, Linux, Solaris,
and OSF1.
With Apache Web servers, you have the option of using the built-in status report functionality. This option requires that the mod_status module be built in, which is done by default. To obtain more detailed information, select the compile option ExtendedStatus On. To enable status reports only for browsers from the foo.com domain, add code to your access.conf configuration file. The Apache configuration is maintained in a set of files, usually located in /usr/local/apache/etc or /usr/local/apache/conf (Solaris) or /etc/httpd/conf (Linux). By default, the following code is commented out in one of the configuration files. <Location /server-status> SetHandler server-status order deny, allow deny from all allow from.foo.com </Location> If it is not, add it to the main Apache configuration file, httpd.conf. Ensure that the Allow statements are correct. Restart your server. To verify the server's performance module, type the following URL into your browser: http://hostname/server-status?auto Monitoring is enabled if you receive a response like the following: Total Accesses: 210 Total kBytes: 94 CPULoad: .000278279 Uptime: 366539 ReqPerSec: .000572927 BytesPerSec: .262608 BytesPerReq: 458.362 BusyServers: 1 IdleServers: 6 Scoreboard: ______W................................................................................. Note: The default Apache monitor works only if Telnet is enabled. To monitor an Apache server with Telnet disabled, use the
WGet command instead of the default Rexec commands, as follows:
wget -q -O - http://hostname/server-status | grep "requests/sec" | cut -c5- | cut -d\ -f1 |
Application In-Depth |
AppDynamics Diagnostics: Built in dynaTrace Diagnostics: Built in |
ASP .NET | Using PerfMon |
BEA WebLogic 8.x, 9.x, 10.x, 11.x |
Performance Explorer can monitor WebLogic 8.x, 9.x, 10.x, and 11.x servers. For monitoring BEA WebLogic 8.x and 9.0 - 9.1, the JNDI protocol is used to connect by way of the Management EJB (MEJB) to the MBean Server. For versions 9.2 and higher, JSR-160 over IIOP is used. Default connection parameters are preconfigured in Performance Explorer. Support for WebLogic Server 11.x includes the following:
Performance Explorer needs to know the application server installation directory or have access to a copy of it to build the correct classpath. A JMX browser allows the selection of the MBean attributes to monitor. An Easy JMX profile can be used to preselect interesting MBeans. Also using SNMP. |
Borland Application Server 6.6 |
Performance Explorer can monitor Borland Application Server 6.6 by way of JSR-160 standard by using the Corbaloc protocol over IIOP. The application
server must be configured to allow access to the MBean Server by way of IIOP.
Performance Explorer needs to know the application server installation directory or have access to a copy of it to build the correct classpath. A JMX browser allows the selection of the MBean attributes to monitor. An Easy JMX profile can be used to preselect interesting MBeans. Certain MBeans do not function properly without applying patch 7697 to Borland Application Server. |
Custom data |
|
F5 Labs 3DNS | Using SNMP |
Helix Server | Using PerMon |
IBM Universal Database DB2 | Using Snapshot |
IBM UniversalDatabase DB2 7.1 | Using PerfMon |
IBM WebSphere Application Server 6.1 |
Performance Explorer can monitor WebSphere Server without custom configuration of the application server.
JNDI protocol is used to connect by way of the Management EJB (MEJB) to the MBean Server. Default connection parameters are preconfigured in Performance Explorer. Performance Explorer needs to know the application server installation directory or have access to a copy of it to build the correct classpath. Performance Explorer needs to use the same IBM JVM version for monitoring. A JMX browser allows the selection of the MBean attributes to monitor. JMX monitoring of WebSphere requires that you specify an IBM JDK. |
IBM WebSphere Application Server 7.0, 8.0, 8.5 | Performance Explorer can monitor WebSphere Servers without custom configuration of the application server. This does not apply to WebSphere Server
7.0 with enabled administrative security and inbound CSIv2 transport layer. In such a case SSL is required. For details, see
the table below.
The JSR-160/Plain IIOP protocol is used to connect by way of the Management EJB (MEJB) to the MBean Server. Default connection parameters are preconfigured in Performance Explorer. Performance Explorer needs to know the application server installation directory or needs to have access to a copy of it to build the correct classpath and to set additional JVM parameters correctly. JMX monitoring of WebSphere requires that you specify an IBM JDK with the same version. If your WebSphere server has disabled administrative security or enabled administrative security and the inbound CSIv2 transport layer is TCP/IP, you can specify a SUN JDK. A JMX browser allows for the selection of MBean attributes for monitoring. |
Internet Information Server 5.1, 6.0, 7.0, 7.5 |
Performance Explorer can monitor IIS Web servers without custom configuration.
SNMP is supported only with a custom monitoring configuration. Windows NT SNMP Service must be installed before the IIS Web server is installed. |
JBoss 4, 5, 6, 7 |
Performance Explorer can monitor JBoss 4, 5, 6, and 7 Server without custom configuration of the application server. JNDI protocol is used to
connect by way of the Management EJB (MEJB) to the MBean Server. Default connection parameters are preconfigured in
Performance Explorer.
Performance Explorer needs to know the application server installation directory or have access to a copy of it to build the correct classpath.
A JMX browser allows the selection of the MBean attributes to monitor. Two Easy JMX profiles can be used to preselect interesting
MBeans.
To access your JBoss 5, 6 or 7 server remotely, JBoss must not point to the default location
127.0.0.1, it must point to your server's external IP address. To point JBoss to the external IP address, proceed as follows:
|
Micro Focus Enterprise Server |
Performance Explorer can monitor
Micro Focus Enterprise Server without custom configuration of the application server.
Note: Monitoring support is available for Windows platforms only.
When setting up your Micro Focus Enterprise Server monitoring project, from the Data Source Wizard, select . On the Connection Parameters dialog, click Attributes Configuration to open the Attributes Configuration dialog.
|
Microsoft Proxy Server 2.0 | Microsoft Proxy Servers are monitored by the Performance Monitor.
No special configuration is required. |
Operating System Data | Operating system data can be monitored for the following platforms:
If available on the host, information such as processor utilization, disc usage, swap file utilization, and network packets can be monitored. On Microsoft systems, operating system data is monitored by the Performance Monitor. For UNIX systems, a remote execution daemon must be running. Such daemons run on UNIX systems by default. Note:
When fetching values using Rexec:vmstat, there can be cases in which Performance Explorer reflects the values of other measures. This can be caused by VMSTAT on a particular server returning values to an unexpected column. The columns in which Performance Explorer expects to receive values from VMSTAT are defined in realtime.ini (C:\Program Files\Silk\Silk Performer 19.5\Include). You may edit the column values in this file to properly capture the values of desired measures. For example, your server might return values for System\CPU Usage System in column 13, while Operating System Data\Linux\System (rexec:vmstat) uses column 14 for System\CPU Usage System. To correct this behavior, you must edit realtime.ini. |
Oracle | Using SNMP and v$sysstat |
Oracle 9, 10, 11, 12 | Using PerfMon
Performance Explorer can monitor Oracle 9, 10, 11, and 12 servers without custom configuration. However, Oracle counters for Windows Performance Monitor are not installed with the default Oracle installation options and need to be made available in the custom installation options. Refer to the Oracle Performance Monitoring section in the Performance Explorer Help for detailed information on monitoring Oracle servers. |
Oracle Application Server 10.1.3 |
Performance Explorer can monitor Oracle Application Server 10.1.3 without custom configuration of the application server.
JNDI protocol is used to connect by way of the Management EJB (MEJB) to the MBean Server. Default connection parameters are preconfigured in Performance Explorer. Performance Explorer needs to know the application server installation directory or have access to a copy of it to build the correct classpath. A JMX browser allows the selection of the MBean attributes to monitor. An Easy JMX profile can be used to preselect interesting MBeans. |
Oracle Forms Application Server | |
PeopleSoft |
|
SAP and SAP V7 | SAPGUI Monitoring, SAPGUI OS-Monitoring |
Secure Shell | |
Silk Central 2008, 2008 R2, 2009, 2009 R2, 2010, 2010 R2, 2011 | Application server and front-end server |
Silk Performer 19.5 controller | The performance metrics in this section are related to the currently running load test, in particular the health values such as memory, CPU or responsiveness, represent the worse values over all agents |
Silk Performer 19.5 agent | The performance metrics in this section are related to the currently running load test from the perspective of the selected agent |
SQL Server 7.0, 2000, 2005, 2008, 2008 R2 | Using PerfMon
The most significant versions of SQL Server can be monitored with the Performance Monitor. No special configuration is required, but make sure that all Performance Monitor counters are enabled on the server that hosts your SQL Server. |
SUN JVM 1.5, 1.6, and 1.7 | Using EJMX and JMX MBeanServer
Performance Explorer can monitor SUN JVM 1.5, 1.6, and 1.7 by way of JSR-160 standard using the RMI protocol. Any application or application server using the platform MBean Server can be monitored in this way. No custom configuration is necessary. A JMX browser allows the selection of the MBean attributes to monitor. An Easy JMX profile can be used to preselect interesting MBeans. |
Terminal Services | Using PerfMon |
VMware ESX Server preconfigured | Using SNMP |
Windows Media Services | Using PerfmMon |
Security settings WebSphere Version |
Disabled administrative security | Enabled administrative security. Inbound CSIv2 Transport Layer = TCP/IP | Enabled administrative security. Inbound CSIv2 Transport Layer = SSL-supported | Enabled administrative security. Inbound CSIv2 Transport Layer = SSL-required |
---|---|---|---|---|
7.0.0.27 | + | + | + | - * |
8.0.0.5 | + | + | + | + |
8.5.0.1 | + | + | + | + |