How To Change Log Level for Oracle Web Services Manager (OWSM)

-
OWSM Gateway
1. Make sure that OracleAS / OC4J hosting OWSM is running.
2. Open $OC4J_HOME/owsm/config/gateway/logging.xml and replace all “INFO” with “FINEST”.
3. Go to $OC4J_HOME/owsm/bin directory, and run the following command
wsmadmin deploy gateway

4. The changed log level for the gateway application is in effect now. Look for the detailed logs in $OC4J_HOME/j2ee/OC4J_Instance/log/gateway.log

OWSM Control
1. Make sure that OracleAS / OC4J hosting OWSM is running.
2. Open $OC4J_HOME/owsm/config/ccore/logging.xml and replace all “INFO” with “FINEST”.
3. Go to $OC4J_HOME/owsm/bin directory, and run the following command
wsmadmin deploy control

4. The changed log level for the OWSM Control application is in effect now. Look for the detailed logs in $OC4J_HOME/j2ee/OC4J_Instance/log/ccore.log

OWSM Policy Manager
1. Make sure that OracleAS / OC4J hosting OWSM is running.
2. Open $OC4J_HOME/owsm/config/policymanager/logging.xml and replace all “INFO” with “FINEST”.
3. Go to $OC4J_HOME/owsm/bin directory, and run the following command
wsmadmin deploy policymanager

4. The changed log level for the Policy Manager is in effect now. Look for the detailed logs in $OC4J_HOME/j2ee/OC4J_Instance/log/policymanager.log

OWSM Monitor
1. Make sure that OracleAS / OC4J hosting OWSM is running.
2. Open $OC4J_HOME/owsm/config/coreman/logging.xml and replace all “INFO” with “FINEST”.
3. Go to $OC4J_HOME/owsm/bin directory, and run the following command
wsmadmin deploy monitor

4. The changed log level for the OWSM Monitor is in effect now. Look for the detailed logs in $OC4J_HOME/j2ee/OC4J_Instance/log/coreman.log

OWSM Client / Server Agents on OC4J
1. Make sure that OracleAS / OC4J hosting the OWSM is running.
2. Open $OC4J_HOME/owsm/config/interceptors/componentId/config/clientagent or serveragent/logging.xml and replace all “INFO” with “FINEST”.
3. Restart OWSM & your application.
4. The changed log level for the agent is in effect now. Look for the detailed logs in $OC4J_HOME/j2ee/OC4J_Instance/log/serveragent.log for Server Agent (and clientagent.log for Client Agents).

Comments

Post a Comment

Popular posts from this blog

jstatd error : Could not create remote object : access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write)

-
While running "./jstatd -J-Djava.security.policy=jstatd.all.policy &" command , below error is getting encountered Error :- Could not create remote object access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) java.security.AccessControlException: access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:536) at java.lang.System.setProperty(System.java:699) at sun.tools.jstatd.Jstatd.main(Jstatd.java:122) Cause :- The "access denied" error is expected, because "jstatd" requires a security policy file specified with the "java.security.policy" system property, if there is no security manager running on the machine. Solution :- 1) cd $ORACLE_HOME/jdk
Read more

Weblogic server is not starting up ; java.lang.AssertionError

-
  If the weblogic server is not starting up and giving the below error , please follow the below solution :- Error :- #Aug 18, 2014 12:34:29 AM PDT# #Notice# #WebLogicServer# #BEA-000365# #Server state changed to STARTING# #Aug 18, 2014 12:34:29 AM PDT# #Info# #WorkManager# #BEA-002900# #Initializing self-tuning thread pool# #Aug 18, 2014 12:34:29 AM PDT# #Notice# #Log Management# #BEA-170019# #The server log file /u01/app/oracle/config/domains/Vinay/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.# #Aug 18, 2014 12:34:29 AM PDT# #Critical# #WebLogicServer# #BEA-000386# #Server subsystem failed. Reason: java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine. java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.                 a
Read more

ORA-22990: LOB locators cannot span transactions

-
Below is the error reported in BPEL opmn logs :- ############ <2010-02-07 10:50:59,852> <:logerror>Error while invoking bean "cube engine": Cannot update lob column.The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid. sql statement: BEGIN INSERT INTO cube_scope( cikey, domain_ref, scope_bin ) VALUES ( ?, ?, '0' ) RETURNING scope_bin INTO ?; END; ORABPEL-04040 Cannot update lob column. The process domain was unable to update the lob column "3" in the datastore. The exception reported is: ORA-22990: LOB locators cannot span transactions Please check that the machine hosting the datasource is physically connected to the network. Oth
Read more