Network Deployment (Distributed operating systems), v8.0 > Set up intermediary services > Set up the proxy server > Troubleshoot the proxy server

Troubleshoot request routing and workload management through the proxy server

This section provides information for how to troubleshoot request traffic that flows through the proxy server. 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. We 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.

New feature: Beginning in WAS v8.0 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 or 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.New feature:

Procedure

1. Obtain the Dynamic Route MBean for the proxy server and invoke the operation to generate routing information for the URI. Start wsadmin.sh and get all of the Dynamic Route MBeans as follows:

    $AdminControl queryNames
    type=DynamicRoute,*
   
   set routembean
   <cut and paste the MBean Identifier from the previous command output>
    $AdminControl invoke $routembean debugRouting {http://*/urlpattern all}
   
   

   Use an asterisk (*) to match all of the virtual hosts, or explicitly specify a virtual host. For example, http://proxy_name:80/urlpattern. The set routembean command should correspond to the MBean from the output of the previous command.

   The proxy server will start generating routing-related information for all subsequent HTTP requests that match the specified virtual host and URL pattern to the SystemOut.log file.

2. Send representative workload traffic through the proxy server.
3. Analyze the routing information in the proxy server SystemOut.log file.

4. Make required changes to application routing to enable or disable routing through the proxy server, using the administrative console, by clicking Applications > Enteprise Applications.
5. Repeat steps two through four until the routing of all requests are satisfied.
6. Disable gathering routing information using wsadmin.sh as follows:

   $AdminControl invoke $routembean
   stopDebugRouting
   

Results

The proxy server and the applications are correctly configured for external access.
Troubleshoot the proxy server
Set up the proxy server

+

Search Tips   |   Advanced Search