WebLogic Server 11g with java based node manager stdout/stderr log path configuration

rhel5weblogic

How I can configure the path where the stdout logs are written by the WebLogic server?

I've read about -Dweblogic.log.RedirectStdoutToServerLogEnabled=true, but this redirects only part of the output. For example if I will run a thread dump, the output will remain in the original log file.

I think it should be an option in nodemanager/startup.properties file.

WebLogic version is 10.3.2.0 and I am using a java based node manager. OS is RHEL 5.

Thank you,
Mircea

Best Answer

Most of the logs can be redirected to standard WebLogic logging with -Dweblogic.log.RedirectStdoutToServerLogEnabled=true See: http://download.oracle.com/docs/cd/E15051_01/wls/docs103/logging/config_logs.html#wp1022848 and http://download.oracle.com/docs/cd/E15051_01/wls/docs103/ConsoleHelp/taskhelp/logging/RedirectJVMOutput.html this can also be configured from the WL Admin Console by ticking the Environment/Servers/<server_name>/Logging/Advanced/Redirect stdout logging enabled checkbox.

Other application logs can be managed by WebLogic logging system or by log4j.

The native java output (like thread dumps) goes to the log configured at the domain creation and set by the NodeManager at the startup time of the ManagedServer. The location is $DOMAIN_HOME/servers/<server_name>/logs/<server_name>.out See: http://download.oracle.com/docs/cd/E14571_01/web.1111/e13740/overview.htm#i1079068
This log is not rotated by WebLogic and should be rotated by something like logrotate.

Related Solutions

Oracle: Can Weblogic 11G run PL/SQL code like App Server 10G

The PL/SQL runs in the database, and so any changes on the application server won't affect the actual execution of PL/SQL code. However, it may still impact on the final result, eg. how the application presents itself to the user, depending on how the application is built.

As for PL/SQL compatibility between Oracle Datababase 11G and 10G you will likely have to do minor modifications in the code. I believe Oracle is claiming backwards compatibility, but in my experience with previous releases there are always a few things that needs tweaking.

Ssl – Custom Trust and Custom Identity Keystore in WebLogic 10.3

Create the boot.properties file:

${DOMAIN_HOME}/servers/AdminServer/security/boot.properties

edit the content to add the following:

username=weblogicAdminUsername
password=weblogicAdminUnencryptedPassword
TrustKeyStore=CustomTrust
CustomTrustKeyStoreFileName=/path/to/custom/keystore
CustomTrustKeyStorePassPhrase=keystoreUnencryptedPassword

Start the WebLogic server.

After startup, note the contents of the boot.properties file are now encrypted.

An alternative way to do it is as follows:

JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.TrustKeyStore=CustomTrust "
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.CustomTrustKeyStorePassPhrase=customKeystorePassword "
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.security.CustomTrustKeyStoreFileName=/my/custom/keystore.jks "

Append the above lines to the domain's bin/setDomainEnv.sh file. Customize the last two.

Best Answer

Related Solutions

Oracle: Can Weblogic 11G run PL/SQL code like App Server 10G

Ssl – Custom Trust and Custom Identity Keystore in WebLogic 10.3

Related Topic