Configuring Security 6-7
b.
Select Configuration, then Keystores.
c.
Define the keystore. See the online help for information about each field.
2.
Import the certificate used by Oracle WebLogic Server into the Oracle HTTP Server wallet as a trusted certificate. You can use any available utility such as
WLST or Fusion Middleware Control for this task.
3.
Edit the Oracle HTTP Server configuration file ORACLE_ INSTANCE
configOHSohs1ssl.conf and add the following line to the SSL configuration under mod_weblogic:
WlSSLWallet ORACLE_INSTANCE}configCOMPONENT_TYPECOMPONENT_NAMEdefault
In the line, default is the name of the Oracle HTTP Server wallet in Step 2. Here is an example of the configuration:
IfModule mod_weblogic.c WebLogicHost myhost.example.com
WebLogicPort 7002 Debug ALL
WLLogFile tmpweblogic.log MatchExpression .jsp
SecureProxy On WlSSLWallet ORACLE_INSTANCEconfigOHSohs1keystoresdefault
IfModule
Save the file and exit.
4.
Restart Oracle HTTP Server to activate the changes.
5.
Ensure that your Oracle WebLogic Server instance is configured to use the custom keystore generated in Step 1, and that the alias points to the alias value used in
generating the certificate. Restart the Oracle WebLogic Server instance.
6.5 Learn More
For more information about the topics covered in this chapter and other security topics, see:
■
Oracle Fusion Middleware Administrators Guide for information about the following topics:
– Secure Sockets Layer SSL, which is an industry standard for securing
communications. See Configuring SSL.
– Keystores, wallets, and certificates. See Managing Keystores, Wallets, and
Certificates.
■
Oracle Fusion Middleware Application Security Guide for information about the following topics:
– Oracle Platform Security, which is a security framework that runs on Oracle
WebLogic Server. It provides application developers, system integrators, security administrators, and independent software vendors with a portable,
integrated, and comprehensive security platform framework for Java SE and Java EE applications.
– Common Audit Framework, which provides a uniform system for
administering audits across a range of components, flexible audit policies, and prebuilt compliance-reporting features.
6-8 Oracle Fusion Middleware 2 Day Administration Guide
– Identity, Policy, and Credential stores, which provide secure storage and
management of user and role information, policies, and credentials.
7
Managing Log Files 7-1
7
Managing Log Files
Oracle Fusion Middleware components generate log files containing messages that record all types of events, including startup and shutdown information, errors,
warning messages, access information on HTTP requests, and additional information. This chapter describes how to view and manage log files to assist in monitoring
system activity and in diagnosing system problems.
This chapter contains the following topics:
■
Overview of Logging in Oracle Fusion Middleware
■
Viewing Log Messages and Summaries
■
Viewing Log Files
■
Searching Log Files
■
Downloading Log Files
■
Configuring Log Settings
■
Learn More
7.1 Overview of Logging in Oracle Fusion Middleware
Most Oracle Fusion Middleware components write diagnostic log files in the Oracle Diagnostic Logging ODL format. Log file naming and the format of the contents of
log files conforms to an Oracle standard. By default, the diagnostic messages are written in text format.
ODL provides the following benefits:
■
The capability to limit the total amount of diagnostic information saved.
■
Older segment files are removed and newer segment files are saved in chronological fashion.
■
Components can remain active, and do not need to be shutdown, when older diagnostic logging files are deleted.
Note: Oracle WebLogic Server does not use the ODL format. For
information about the Oracle WebLogic Server log format, see Oracle Fusion Middleware Configuring Log Files and Filtering Log Messages for
Oracle WebLogic Server.
7-2 Oracle Fusion Middleware 2 Day Administration Guide
7.2 Viewing Log Messages and Summaries
