Java CAPS 5.
1 Field Notes
Note 1: Runtime logging management
December 2007
Table of Contents
Introduction....................................................................................................................1
Determining logging configuration................................................................................1
Changing log levels for specific logging categories ......................................................4
More examples...............................................................................................................5
Introduction
In Java CAPS 5.1 the Sun SeeBeyond Integration Server is a modified version of the
Sun Application Server 8.0 Platform Edition. As such a number of things that can be
done with that application server can be done with the Sun SeeBeyond Integration
Server. Most notably, it can be managed at runtime using the isadmin tool much the
same way as the Sun Application Server 8.0 PE can be managed using the asadmin
tool.
In as much as the isadmin tool is barely mentioned in Java CAPS documentation
the material presented here is gathered through empirical study rather then gleaned
from documentation.
Additional material on the Sun Application Server 8.0 Platform Edition can be found
on Sun’s documentation site and elsewhere:
[Link]
[Link]
This note discusses how the isadmin tool can be used to manage runtime logging of
the Sun SeeBeyond Integration Server. This note applies to the Sun SeeBeyond
Integration Server included in Java CAPS 5.1.
Determining logging configuration
This command will list all log-service configuration properties, for the Integration
Server running on port 20000, and their values.
isadmin get -p 20000 [Link]-service.*
[Link] = false
[Link] =
C:/JCAPS513/logicalhost/is/domains/wssec/logs/[Link]
[Link]-filter = <null>
[Link]-handler = <null>
[Link]-rotation-limit-in-bytes = 10000000
[Link]-to-console = false
[Link]-msg-per-second = 0
[Link]-in-millis = 500
[Link]-in-millis = 250
[Link]-dup-stack-trace = false
[Link]-sysout-warning = false
[Link]-size = 10
[Link]-system-logging = false
For explanation of the properties see [Link]
6093/[Link]#wp1006045
In a Unix-like environment, or in a Windows environment with the grep command
available, one can issue the following isadmin command to obtain a list of all
configuration properties pertaining to the log-service hierarchy and their current
values.
C:\JCAPS513\logicalhost\is\bin>isadmin get -p 20000 server*.* | grep
log-service
[Link] = false
[Link] =
C:/JCAPS513/logicalhost/is/domains/wssec/logs/[Link]
[Link]-filter = <null>
[Link]-handler = <null>
[Link]-rotation-limit-in-bytes = 10000000
[Link]-to-console = false
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link]-container = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link]-container = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link]-container = INFO
[Link] = INFO
[Link] = FINEST
[Link]-adapter = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link] = INFO
[Link]-container = INFO
[Link]-msg-per-second = 0
[Link]-in-millis = 500
[Link]-in-millis = 250
[Link]-dup-stack-trace = true
[Link]-sysout-warning = false
[Link]-size = 10
[Link]-system-logging = false
Note that [Link]-log-levels component lists all
module log levels but not the log levels for specific logging categories. Given a
[Link] with the following content fragment:
<log-service
alarms="false"
file="C:/JCAPS513/logicalhost/is/domains/wssec/logs/[Link]"
log-rotation-limit-in-bytes="10000000"
log-to-console="false"
use-system-logging="false"
>
<module-log-levels
admin="INFO"
classloader="INFO"
cmp="INFO"
.
.
.
verifier="INFO"
web-container="INFO"
>
<property name="[Link]" value="INFO"/>
<property name="[Link]" value="INFO"/>
<property name="[Link]" value="INFO"/>
<property name="[Link]" value="INFO"/>
<property name="[Link]" value="FINEST"/>
<property name="[Link]" value="INFO"/>
<property name="[Link]" value="FINEST"/>
.
.
.
one can readily relate specific elements to the [Link]-service
components:
[Link] = false
[Link] =
C:/JCAPS513/logicalhost/is/domains/wssec/logs/[Link]
[Link]-filter = <null>
[Link]-handler = <null>
[Link]-rotation-limit-in-bytes = 10000000
[Link]-to-console = false
[Link] = INFO
[Link] = INFO
[Link] = INFO
.
.
.
[Link] = INFO
[Link]-container = INFO
however none of the property elements below module-log-levels, present in the
[Link], are listed using the isadmin get command. I have not found a way to
list these elements using the asadmin or the isadmin tools.
Changing log levels for specific logging categories
Inspection of the [Link] for a Java CAPS domain may reveal a series of
properties with names of logging categories under the module-log-levels element, for
example:
<module-log-levels
admin="INFO"
classloader="INFO"
cmp="INFO"
.
.
.
verifier="INFO"
web-container="INFO"
>
<property name="[Link]" value="INFO"/>
<property name="[Link]" value="INFO"/>
<property name="[Link]" value="INFO"/>
<property name="[Link]" value="INFO"/>
<property name="[Link]" value="FINEST"/>
<property name="[Link]" value="INFO"/>
.
.
.
These properties would have typically been set through the Integration Server
Administration console, logging Tab, log-levels sub-tab.
To display the values of a specific property, [Link],
using the isadmin tool one would enter a command like similar to the following:
C:\JCAPS513\logicalhost\is\bin>isadmin get -p 20000 [Link]-log-
[Link]\.eWay\.framework\.management
[Link] = INFO
Note that all dots “.” in the logging category [Link] have
been escaped with the backslash “\”.
To change the value of the logging category one would issue the following command,
where log level to set is one of OFF, SEVER, WARNING, INFO, CONFIG, FINE,
FINER, FINEST:
C:\JCAPS513\logicalhost\is\bin>isadmin set -p 20000 [Link]-log-
[Link]\.eWay\.framework\.management=F
INE
[Link] = FINE
The command executes and displays the current logging level for the category.
Note that specifying partial category name for the get command does not return a
partial category but results in an error, for example:
C:\JCAPS513\logicalhost\is\bin>isadmin get -p 20000 [Link]-log-
[Link]\.eWay\.framework
[Link]
CLI137 Command get failed.
Issuing a set command with a category name not already in the [Link] causes
that category property element to be created and set in the [Link]:
C:\JCAPS513\logicalhost\is\bin>isadmin set -p 20000 [Link]-log-
[Link]\.eWay\.framework=CONFIG
[Link] = CONFIG
C:\JCAPS513\logicalhost\is\bin>isadmin get -p 20000 [Link]-log-
[Link]\.eWay\.framework
[Link] = CONFIG
Successful command execution sets the ERRORLEVEL to 0 on Windows.
Unsuccessful command execution sets the ERRORLEVEL to 1 in Windows.
In Unix-like environments command execution status is set at the shell level.
Command execution status can be used in scripts/batch files to control script/batch
file execution.
More examples
Get the value of the log level for the logging category [Link]
isadmin get -p 20000 ^
[Link]\.xml\.messaging\.saaj
Note that the category [Link], being already a dotted
name, is escaped as javax\.xml\.messaging\.saaj
This command produces the following:
[Link] = FINEST
To change this logging category logging level to INFO one would use the set
command:
isadmin set -p 20000 ^
[Link]\.xml\.messaging\.saaj=INFO
which would result in the following output:
[Link] = INFO
