Set the Logging Level field to one of the following settings: Severe, Warning,

Diagnosing Problems 16-21 Viewing Message Logs You can view the message log files for an ADF and WebCenter Web service endpoint from the Log Messages page. To view message logs for a Web service endpoint: Navigate to the Web Service Endpoint page, as described in Viewing the Details for a Web Service Endpoint on page 6-7, and in the Quick Links section of the Web Services Endpoint page top right, click Message Logs. The Log Messages page is displayed, similar to Figure 16–7 . For more details about the contents of the Log Messages page, see Viewing Diagnostic Logs on page 16-18. Filtering Message Logs By default, the Log Messages page displays a summary of SOAP messages logged over the last hour. You can filter the messages that are displayed by updating the search criteria. The process is the same as for diagnostic logs; for more information, see Filtering Diagnostic Logs on page 16-19. By default, the Component and Module message fields are included as part of the Search criteria for message logs. The Component field is set to the WebLogic Server name; the Module field is set to oracle.wsm.msg.logging, which is the name of the message logging component. Reviewing Sample Logs The following sections provide excerpts from sample logs, demonstrating how to diagnose specific problems using the log entries. ■ Sample Log: Oracle WSM Policy Manager Not Available ■ Sample Log: Security Keystore Not Configured ■ Sample Log: Certificate Not Available Sample Log: Oracle WSM Policy Manager Not Available The following sample log excerpt indicates that the Oracle WSM Policy Manager is down. To resolve this issue, restart the wsm-pm application, as described in Starting and Stopping Applications Using in Oracle Fusion Middleware Administrators Guide. 2009-02-16 16:21:28,029 [[ACTIVE] ExecuteThread: 4 for queue: weblogic.kernel.Default self-tuning] ERROR policymgr.PolicyManagerModelBean logp.251 - Service lookup failed with URL:t3:stadk13.us.oracle.com:7001wsm-pm oracle.wsm.policymanager.PolicyManagerException: WSM-02118 : The query service cannot be created. ... Sample Log: Security Keystore Not Configured The following sample log excerpt indicates that an Oracle WSM security policy with message protection was applied, but the keystore was not configured. To resolve this security fault, configure the keystore, as described in Configuring Keystores for Message Protection on page 10-8. Feb 16, 2009 5:29:56 PM oracle.wsm.common.logging.WsmMessageLogger logSevere SEVERE: The specified Keystore file scratchsbollapastage131user_ projectsdomainssai131_domainconfigfmwconfigdefault-keystore.jks 16-22 Oracle Fusion Middleware Security and Administrators Guide for Web Services cannot be found; it either does not exist or its path is not included in the application classpath. Feb 16, 2009 5:29:56 PM oracle.wsm.common.logging.WsmMessageLogger logSevere SEVERE: Keystore is not properly configured in jps config. Feb 16, 2009 5:29:56 PM oracle.wsm.common.logging.WsmLogUtil log SEVERE: failure in OWSM Agent processRequest, category=security, function=agent.function.client, application=default, composite=pe3test3, modelObj=Service1, + policy=null, policyVersion=null, assertionName=null oracle.wsm.common.sdk.WSMException: WSM-00101 : The specified Keystore file scratchsbollapastage131user_projectsdomainssai131_ domainconfigfmwconfigdefault-keystore.jks cannot be found; it either does not exist or its path is not included in the application classpath. ... Sample Log: Certificate Not Available The following sample log excerpt indicates that an Oracle WSM security policy with message protection was applied that required a security certificate that was not available in the keystore. To resolve this security fault, configure the keystore with a certificate, as described in Obtaining a Trusted Certificate and Importing it into the Keystore on page 10-15. [2009-04-15T04:07:02.821-07:00] [jrfServer] [ERROR] [WSM-000062] [oracle.wsm.resources.security] [tid: [ACTIVE].ExecuteThread: 0 for queue: weblogic.kernel.Default self-tuning] [userId: anonymous] [ecid: 0000I2dTFG7DScT6uBe9UH19tRyv000000,0:1] [WEBSERVICE_PORT.name: NonCAAsCAMessageProtectionPolicyPort] [APP: jaxwsservices] [J2EE_MODULE.name: NonCAAsCAMessageProtectionPolicy] [WEBSERVICE.name: NonCAAsCAMessageProtectionPolicyService] [J2EE_APP.name: jaxwsservices] [arg: oracle.wsm.security.SecurityException: WSM-00062 : The path to the certificate used for the signature is invalid.] [2009-04-15T04:07:02.810-07:00] [jrfServer] [NOTIFICATION] [] [oracle.wsm.security.policy.scenario.processor.Wss11X509TokenProcessor] [tid: [ACTIVE].ExecuteThread: 0 for queue: weblogic.kernel.Default self-tuning] [userId: anonymous] [ecid: 0000I2dTFG7DScT6uBe9UH19tRyv000000,0:1] [WEBSERVICE_PORT.name: NonCAAsCAMessageProtectionPolicyPort] [APP: jaxwsservices] [J2EE_MODULE.name: NonCAAsCAMessageProtectionPolicy] [WEBSERVICE.name: NonCAAsCAMessageProtectionPolicyService] [J2EE_APP.name: jaxwsservices] Certificate path validation failed for signing certificate [2009-04-15T04:07:02.821-07:00] [jrfServer] [ERROR] [WSM-00006] [oracle.wsm.resources.security] [tid: [ACTIVE].ExecuteThread: 0 for queue: weblogic.kernel.Default self-tuning] [userId: anonymous] [ecid: 0000I2dTFG7DScT6uBe9UH19tRyv000000,0:1] [WEBSERVICE_PORT.name: NonCAAsCAMessageProtectionPolicyPort] [APP: jaxwsservices] [J2EE_MODULE.name: NonCAAsCAMessageProtectionPolicy] [WEBSERVICE.name: NonCAAsCAMessageProtectionPolicyService] [J2EE_APP.name: jaxwsservices] [arg: oracle.wsm.security.SecurityException: WSM-00062 : The path to the certificate used for the signature is invalid.] Error in receiving the request: oracle.wsm.security.SecurityException: WSM-00062 : The path to the certificate used for the signature is invalid.