WebSphere 8.5 JVM实例状态仪表盘实现咨询（支持IE访问）

Got it, let's break down the feasible solutions for your WebSphere 8.5 (Linux) monitoring dashboard that Windows users can access via Internet Explorer. These approaches are tailored to WAS 8.5's capabilities and IE's compatibility constraints:

1. Build a Web Dashboard Using WebSphere Admin API #

This is the most native approach since it leverages WAS's built-in administrative APIs to fetch server metrics directly. You'll package this as a WAR file and deploy it to your WAS instance for IE access.

Step-by-Step Implementation #

• Set up dependencies: Grab the required JARs from your WAS installation (WAS_HOME/runtimes/com.ibm.ws.admin.client_8.5.0.jar and WAS_HOME/plugins/com.ibm.ws.security.crypto.jar) and add them to your Java project.
• Write code to fetch metrics:
  Use AdminClient to connect to your WAS server and query MBeans for the data you need:

  import com.ibm.websphere.admin.client.AdminClient;
  import com.ibm.websphere.admin.client.AdminClientFactory;
  import java.util.Properties;
  import javax.management.ObjectName;
  
  public class WASMonitor {
      public static String getJVMStatus() throws Exception {
          // Configure connection properties
          Properties props = new Properties();
          props.setProperty(AdminClient.CONNECTOR_TYPE, AdminClient.CONNECTOR_TYPE_SOAP);
          props.setProperty(AdminClient.CONNECTOR_HOST, "your-linux-was-host");
          props.setProperty(AdminClient.CONNECTOR_PORT, "8880"); // Default SOAP port, adjust as needed
          props.setProperty(AdminClient.USERNAME, "was-admin-user");
          props.setProperty(AdminClient.PASSWORD, "was-admin-pass");
  
          // Create AdminClient connection
          AdminClient adminClient = AdminClientFactory.createAdminClient(props);
  
          // Fetch JVM (Server) status
          ObjectName serverRuntime = new ObjectName("WebSphere:type=ServerRuntime,process=server1,*");
          return (String) adminClient.getAttribute(serverRuntime, "state");
      }
  
      public static String getDeployDate() throws Exception {
          Properties props = new Properties();
          props.setProperty(AdminClient.CONNECTOR_TYPE, AdminClient.CONNECTOR_TYPE_SOAP);
          props.setProperty(AdminClient.CONNECTOR_HOST, "your-linux-was-host");
          props.setProperty(AdminClient.CONNECTOR_PORT, "8880");
          props.setProperty(AdminClient.USERNAME, "was-admin-user");
          props.setProperty(AdminClient.PASSWORD, "was-admin-pass");
  
          AdminClient adminClient = AdminClientFactory.createAdminClient(props);
  
          // Fetch EAR deployment date
          ObjectName appDeployment = new ObjectName("WebSphere:type=ApplicationDeployment,name=your-ear-name,*");
          return (String) adminClient.getAttribute(appDeployment, "deployedDate");
      }
  }
  

• Create a web interface: Wrap this logic in a JSP that generates an IE-compatible HTML page. Use basic HTML tables and inline CSS (since older IE versions don't support modern CSS features well):

  <%@ page import="com.yourpackage.WASMonitor" %>
  <!DOCTYPE html>
  <html>
  <head>
      <title>WAS Server Dashboard</title>
      <style>
          table { border-collapse: collapse; width: 80%; margin: 20px auto; }
          th, td { border: 1px solid #ddd; padding: 8px; text-align: left; }
          th { background-color: #f2f2f2; }
      </style>
  </head>
  <body>
      <h2 style="text-align:center;">WebSphere Server Status Dashboard</h2>
      <table>
          <tr>
              <th>Metric</th>
              <th>Value</th>
          </tr>
          <tr>
              <td>JVM Runtime Status</td>
              <td><%= WASMonitor.getJVMStatus() %></td>
          </tr>
          <tr>
              <td>EAR Deployment Date</td>
              <td><%= WASMonitor.getDeployDate() %></td>
          </tr>
      </table>
  </body>
  </html>
  

• Deploy and test: Package your code into a WAR file, deploy it to WAS 8.5, and grant the necessary administrative permissions to the app's user. Then access the JSP URL from Windows IE.

2. Use JMX Remote Monitoring for Dashboard Data #

WebSphere 8.5 supports JMX remote access, which lets you fetch metrics via standard JMX APIs. This is a more flexible option if you want to separate the monitoring app from WAS itself.

Step-by-Step Implementation #

• Enable JMX remote in WAS:
  1. Log into the WAS Admin Console
  2. Navigate to Servers > Server Types > WebSphere Application Servers > [Your Server] > Administration Services
  3. Check Enable administrative JMX connector and set the port (e.g., 1099) and authentication credentials
  4. Restart the server
• Write JMX client code:
  Use JMXConnector to connect to the WAS JMX service and fetch metrics:

  import javax.management.MBeanServerConnection;
  import javax.management.ObjectName;
  import javax.management.remote.JMXConnector;
  import javax.management.remote.JMXConnectorFactory;
  import javax.management.remote.JMXServiceURL;
  import java.util.HashMap;
  
  public class WASJMXMonitor {
      public static String getJVMStatus() throws Exception {
          JMXServiceURL url = new JMXServiceURL("service:jmx:rmi:///jndi/rmi://your-linux-was-host:1099/jmxrmi");
          HashMap<String, Object> env = new HashMap<>();
          env.put(JMXConnector.CREDENTIALS, new String[] {"was-admin-user", "was-admin-pass"});
  
          JMXConnector connector = JMXConnectorFactory.connect(url, env);
          MBeanServerConnection connection = connector.getMBeanServerConnection();
  
          // Fetch JVM status
          ObjectName serverRuntime = new ObjectName("WebSphere:type=ServerRuntime,process=server1,*");
          String status = (String) connection.getAttribute(serverRuntime, "state");
          
          connector.close();
          return status;
      }
  
      public static String getDeployDate() throws Exception {
          JMXServiceURL url = new JMXServiceURL("service:jmx:rmi:///jndi/rmi://your-linux-was-host:1099/jmxrmi");
          HashMap<String, Object> env = new HashMap<>();
          env.put(JMXConnector.CREDENTIALS, new String[] {"was-admin-user", "was-admin-pass"});
  
          JMXConnector connector = JMXConnectorFactory.connect(url, env);
          MBeanServerConnection connection = connector.getMBeanServerConnection();
  
          // Fetch EAR deployment date
          ObjectName appDeployment = new ObjectName("WebSphere:type=ApplicationDeployment,name=your-ear-name,*");
          String date = (String) connection.getAttribute(appDeployment, "deployedDate");
          
          connector.close();
          return date;
      }
  }
  

• Build the web interface: Same as the first approach—wrap this logic in a Servlet/JSP with IE-compatible HTML, deploy to any web server (even a lightweight one like Tomcat if you don't want to use WAS), then access from IE.

3. Shell Script + Lightweight Web Service (No Java Required) #

If you prefer a simpler, script-based approach, you can use wsadmin (WAS's administrative script tool) to fetch metrics, then expose them via a basic web service for IE access.

Step-by-Step Implementation #

• Write a wsadmin Jython script (was_monitor.py):

  # Fetch JVM status
  server_runtime = AdminControl.completeObjectName('type=ServerRuntime,process=server1,*')
  jvm_status = AdminControl.getAttribute(server_runtime, 'state')
  
  # Fetch EAR deployment date
  app_deployments = AdminConfig.list('ApplicationDeployment').splitlines()
  deploy_date = ""
  for app in app_deployments:
      if AdminConfig.showAttribute(app, 'name') == 'your-ear-name':
          deploy_date = AdminConfig.showAttribute(app, 'deployedDate')
          break
  
  print("JVM Status: " + jvm_status)
  print("EAR Deployed Date: " + deploy_date)
  

• Create a wrapper script (generate_dashboard.sh) to convert the output to HTML:

  #!/bin/bash
  OUTPUT=$(wsadmin.sh -lang jython -f /path/to/was_monitor.py)
  cat <<EOF > /tmp/was_dashboard.html
  <!DOCTYPE html>
  <html>
  <head>
      <title>WAS Dashboard</title>
      <style>
          table { border-collapse: collapse; width: 80%; margin: 20px auto; }
          th, td { border: 1px solid #ddd; padding: 8px; }
      </style>
  </head>
  <body>
      <h2 style="text-align:center;">WAS Server Status</h2>
      <table>
          <tr><th>Metric</th><th>Value</th></tr>
          <tr><td>JVM Status</td><td>$(echo "$OUTPUT" | grep "JVM Status:" | cut -d' ' -f3-)</td></tr>
          <tr><td>EAR Deployment Date</td><td>$(echo "$OUTPUT" | grep "EAR Deployed Date:" | cut -d' ' -f4-)</td></tr>
      </table>
  </body>
  </html>
  EOF
  

• Expose the HTML via a web service:
  Use Python's built-in HTTP server to serve the generated HTML:

  # Run this in the directory where /tmp/was_dashboard.html is stored (or adjust paths)
  cd /tmp
  python -m SimpleHTTPServer 8080
  

  Alternatively, use Node.js if Python isn't available.
• Test from IE: On Windows, open IE and navigate to http://your-linux-was-host:8080/was_dashboard.html. Make sure Linux's firewall allows incoming traffic on port 8080.

Key Notes for IE Compatibility #

• Stick to HTML5 basic tags (<table>, <h2>, <style> with inline or simple selectors)
• Avoid modern CSS features like Flexbox/Grid—use table-based layouts for older IE versions
• Test on the specific IE version your users are using (IE 9/10/11 have different support levels)

内容的提问来源于stack exchange，提问作者Nithin S