aspose file tools
The moose likes Portals and Portlets and the fly likes Changing the log file name and location in RAD6 Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of The Mikado Method this week in the Agile and other Processes forum!
JavaRanch » Java Forums » Java » Portals and Portlets
Reply Bookmark "Changing the log file name and location in RAD6" Watch "Changing the log file name and location in RAD6" New topic
Author

Changing the log file name and location in RAD6

Bharat Chatla
Greenhorn

Joined: May 19, 2005
Posts: 14
I want to change the log file location and the name of the log file which is set by default in portalserver. Default location is wp_root/log/wps_date.log

But when I change the file in location wp_root/shared/app/config/log.properties with logFileName = wp_root/log/bharat/wps_date.log the new log file is not getting generated on path wp_root/log/bharat/

What could be the possible reason. How to solve this issue.

Below is the file for reference.

# The name of the WebSphere Portal Server's log file.
# This setting is ignored if the WebSphere Application Server's log files are
# used.
#
# The following tokens are replaced by the corresponding values:
# $APPSERVER_NAME The name of the WAS node, this should be used for vertical
# clusters to enforce that the different nodes write into
# different files or directories
# $CREATE_TIME The time a file was created
#
# Default: log/wps_$CREATE_TIME.log
#
logFileName=log/bharat/wps_$CREATE_TIME.log

#
# Uncomment the 'traceString' line to activate tracing in the Portal.
# The value of 'traceString' has to conform to the following grammar:
# TraceString := <ClassString>(:<ClassString> *
# ClassString := <ClassName>=<type>=<state>(,<type>=<state> *
# ClassName := a java String
# state := [enabled|disabled]
# type := [all|low|medium|high]
#
# The ClassName is used to identify the class (or set of classes) to
# apply the specified change to. This ClassName may either be an exact
# name which uniquely identifies a single class, or it may identify a
# point in the class hierarchy class by using the "*" wild card
# character.
# For example, if classes a.b.c.d and a.b.c.e are registered, then the name
# a.b.c.d applies to just one class and the name a.b.c.* applies to both.
#
# Following are some samples of valid trace Strings.
# a.b.c.d=all=enabled
# a.b.c.d=low=enabled,medium=disabled
# a.b.*=low=enabled:a.b.c.d=low=enabled,medium=enabled:a.b.c.e=low=disabled
#
# In case the traces are turned on for the complete portal environment (e.g.
# com.ibm.wps.*=all=enabled) the portlet debug traces will be enabled as well.
# To disable the portlet debug traces the follwing traceString should be added:
# com.ibm.wps.pe.PortletRenderTimeLoggingHelper=all=disabled
#
#traceString=*=all=disabled
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Changing the log file name and location in RAD6
 
Similar Threads
WPS Answers needed
IBM 399 Question challenge
Tomcat error when running startup.sh
Websphere Portal - Test 399
Test 399: IBM WebSphere Portal V5.1, Application Development