WAS Eperience Sharing.ppt

* * * * * * * * * * * * * * * * * * * * * * * * 当工作 流向下游时，排队网络中的队列逐渐变小。当 200 个客户机请求到达 Web 服务器时，125 个请求在网络中保持排队，这是因为将 Web 服务器设置为处理 75 个并发客户机。当将 75 个请求从 Web 服务器传递到 Web 容器时，25 个请求在 Web 服务器中保持排队，而其余 50 个请求由 Web 容器处理。此过程在数据源进行，直到 25 个用户请求到达最终目标 － 数据库服务器。由于有工作正在等待进入每个上游的点上的组件，所以此系统中没有组件必须等待工作到达。成批的请求等待在网络中，WebSphere Application Server 外。此配置类型会增加稳定性，因为没有组件超负荷。 然后您可以使用 Edge Server 将等待用户导向到 WebSphere Application Server 集群 中的其他服务器。 * Tivoli Performance Viewer has gone under several different names throughout the life of the WebSphere product. In WebSphere 3.5.x-4.x it was known as Resource Analyzer. In WebSphere v5.x it was rebranded as Tivoli Performance Viewer. Resource Analyzer only works with WebSphere 3.5.x-4.x. Tivoli Performance Viewer only works with WebSphere 5.x and higher. Tivoli Performance Viewer is capable of connecting directly to a base application server or to the Deployment Manager in a Network Deployment configuration. The Performance Advisors will be discussed at length later in the presentation. Tivoli Performance Viewer is accessed through the Administrative Console. In order to receive information in the Summary Reports you need to enable the following PMI monitoring levels. Monitoring levels must be set to HIGH in order to receive information in the Servlets, EJBs, Web Container Pools, ORB Pools, and Connection Pools table. To receive information in the EJB Methods table, set the monitoring level to MAXIMUM for the EJB(s) that you want to collect method-level metrics from. When viewing data in the table and graphs in Tivoli Performance Viewer, you are able to select which performance metrics that you want displayed. This is useful when you want to correlate several different PMI metrics. Recording logs can be useful in the following situations: You need to forward your application server’s performance data on to someone in your team or to support for them to evaluate. You need to have historical data for comparing different performance tests. Keep