Log Server Properties

server.port

<port> - DEPRECATED – replaced by server.listenurls

The log server collects log information from all the servers in the installation. The log server uses the log4j configuration.
<PP_HOME>/webapps/scl/WEB-INF/classes/log4jserver.properties

This configuration contains:

log4j.appender.FileLog.File=./logs/server/ppServer.log

which shows where the logservers collected log is stored.

Example:
21236
In this example the log server listens for log client connections on port 21236

server.listenurls

<URL list> - defaults to tcp://{server.port} where {server.port} is the value of the server.port property.

List of URLs to listen for connections from log clients – The URLs have the following format:

tcp://[hostname:]port – TCP/IP blocking sockets – requires 2 java threads per connection.
nio://[hostname:]port – TCP/IP nonblocking (java nio) sockets – does not require any extra threads.
local://port – Local queue-based connection, requires 1 thread per connection, only works in the same JVM, but much faster than using sockets.
nios://[hostname]:port[?params] – Like NIO, but with SSL encryption

For nios connections, the following parameters can be specified;
keystore – Filename of keystore – default is /ptskeystore
keystorepassword - Password for keystore
keystoretype – Type of keystore, default is JKS
enabledciphersuites – List of enabled cipher suites, if not specified, the Java default ones are used.

Note that this list of URLs replaces the older server.port and server.address properties – this provides a more flexible way to support multiple communication protocols, and listen on multiple interfaces simultaneously.
If this property is not specified, it will default to tcp:// protocol and the port number from the server.port setting to remain backward compatible.

Examples:
server.listenurls=tcp://21233 – Listens on port 21236, using TCP blocking sockets
server.listenurls=nio://10.0.0.1:21236;local://21236 – Listen on the specified IP address and port, using nonblocking sockets, and also listens for local connections from components in the same JVM on port 21236.

logbackConfigName
logPropertiesName

<name of logback xml file in classpath> - default logback_server.xml
<name of log4j properties file in classpath> - default log4j_server.properties

PortalProtect Server will first attempt to load the logback configuration from the specified file, defaulting to logback_server.xml – if that file is not found in the classpath, it will attempt to load the log4j configuration, by default from log4j_server.properties and initialize logging using log4j.

All log entries that the server receives from agents, no matter if it is log4j events or logback events will be converted to the specified logging methods (logback or log4j) and logged on the server using the configured appenders in the appropriate configuration.

memoryCacheSize

<Integer>

Sets the number of log entries that are kept in memory on the log server. The entries kept in memory can be viewed from the administration client – older entries are only available in the logfile.

Example:
memoryCacheSize=1000

categoryfilter

<Pattern> - default empty.

If non-empty, all log categories matching the pattern will not be kept in memory on the web server, and will not be visible in the admin interface.

The pattern can include * and ? characters to match any or 1 character, and the pipe character | can be used to divide multiple entries. If the pattern starts with ^ then the match is reversed, e.g. "{_}^dk.*|com.{_}" means that anything not matching dk. or com.* will not be displayed, where "dk.*|com." means that anything matching dk. or com.* will not be included in memory.

Example:
categoryfilter=accesslog|historylog