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: 이 주제는 하나 이상의 애플리케이션 서버 로그 파일을
참조합니다. 권장되는 대안은 분배 및 IBM® i 시스템에서 SystemOut.log, SystemErr.log, trace.log 및 activity.log 파일을 사용하는 대신
HPEL(High Performance Extensible Logging) 로그를 사용하고
인프라를 추적하도록 서버를 구성하는 것입니다. 원시 z/OS® 로깅 기능과 연계하여 HPEL을 사용할 수도 있습니다. HPEL을 사용하는 경우
서버 프로파일 바이너리 디렉토리의 LogViewer 명령행 도구를 사용하여
모든 로그에 액세스하고 정보를 추적할 수 있습니다. HPEL 사용에 대한 자세한 정보는
HPEL을 사용한 애플리케이션 문제점 해결 정보를
참조하십시오.
Procedure
- Obtain the Dynamic Route MBean for the proxy server and
invoke the operation to generate routing information for the URI. Start wsadmin 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.
- Send representative workload traffic through the proxy
server.
- Analyze the routing information in the proxy server SystemOut.log file.
- Make required changes to application routing to enable
or disable routing through the proxy server, using the administrative
console, by clicking .
- Repeat steps two through four until the routing of all
requests are satisfied.
- Disable gathering routing information using wsadmin as
follows:
$AdminControl invoke $routembean
stopDebugRouting
Results
The proxy server and the applications are correctly configured
for external access.