This section provides information for how to troubleshoot
request traffic that flows through the proxy server.
Before you begin
You will need to know the machines and nodes that will belong
to the proxy server cluster, because the product needs to be installed
on those machines. You will also need to know the URL for the applications,
application deployment, and cluster definition details. The proxy
server should be started.
About this task
You can use the proxy server MBean to determine how requests
are routed to applications, and subsequently, to a particular application
server. If the request is being routed incorrectly, you can disable
routing to specific applications or reconfigure the routing rules.
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.