Novell Access Manager 3.1 SP 2, Руководство пользователя, Страница: 124 / 126

124 Novell Access Manager 3.1 SP2 J2EE Agent Guide
n
ov
do
cx (e
n)
16
Ap
ril 20
10
9.10 JBoss and SSL
If you want to restrict access to SSL on JBoss, you need to either disable the HTTP port in JBoss and
enable only the SSL port or configure SSL in the
web.xml
file. It is not enough to select Require
SSL on the Protected Web Resource page. In the Administration Console, click Devices > J2EE
Agents > Edit > Manage authorization policies > [Name of Web Module] > [Name of Protected
Resource] .
9.11 Viewing Log Files
The J2EE agent logs messages to the J2EE server log files. For verbose messages, including policy
evaluation messages, you need to enable tracing. In the Administration Console, click
Devices >
J2EE Agents > Edit > Enable tracing .
The location of the log files for each J2EE server is implementation-specific:
Š
JBoss Server: For a JBoss server, the log messages are logged to the
$JBOSS_HOME/log/
jboss.log
file if you launched the JBoss server by using the
run.sh
script found in the
bin
folder. Messages are also sent to the console, so you should check the console or the
$JBOSS_HOME/server/default/log/server.log
file.
Š
WebSphere Server: For a WebSphere server, the log messages are logged to files in the
$WAS_BaseDir/profiles/$ProfileName/logs
directory. Check the
SystemOut.log
and
SystemErr.log
files.
Š
WebLogic Server: For a WebLogic server, the log messages are sent to standard out. If you
launch the server in a console window, the messages appear in this window. If you want the
messages logged to the server log file, you need to configure the server to send standard out to
this file. This can be done from the WebLogic Administration Server console application in the
Logging tab under Servers .
9.12 Troubleshooting Access Control
When a user requests access to a resource protected by the J2EE Agent, the request flows through
the policy enforcement points illustrated in
Figure 9-1 .