Novell IFOLDER 3.7 - SECURITY ADMINISTRATION, Руководство администратора

Страница: 105 / 216

Managing an iFolder Enterprise Server 105
no
vd
ocx
(e
n)
13
Ma
y 20
09
In the Log4net terminology, each output destination is defined in an XML
appender
tag. If you do
not want to log events for the Simias Service or for file access, comment out (
!--
) the related
appender
tag and its child elements for that log file.
9.5 Backing Up the iFolder Server
1 Find and note down the Simias Data Store(s)
You can find the default location of the Simias store directory under Data Store section in
the Server Details page of the Web Admin console and additional data stores if configured. For
more information on this, see
Step 8 on page 136 and “Enable or Disable Data Store:” on
page 137 .
2 Open a terminal console, login as root or root equivalent user, and enter the following
command to stop the iFolder server.
/etc/init.d/apache2 stop
3 Stop the iFolder mono process if running.
pkill mono
4 Use your normal file system backup procedures to back up all the Data Stores.
Level of Simias Services
messages
<level value=” status ”
/>
(Use only for the
Simias.log
.)
The type of messages or level of
detail you want to capture for the
log. Valid levels include the
following:
OFF
FATAL
ERROR
WARN
INFO
DEBUG
ALL
<level value="ERROR" />
Fields to report for file access
events
<header value=” layout ”
/>
(Use only for the
Simias.access.log .)
Specify which fields to report and
the order you want them to appear
for each entry. Valid fields include
the following:
date
time
method
(program call or event)
status
(success or failure)
user
uri
(relative path of the file in an
iFolder)
id
(node key)
The fields are pattern delimited
(
**
) by default. Use this pattern to
add additional fields.
<header value="#version:
1.0&#xD;&#xA;#Fields:**dat
e**time**method**status**u
ser**uri**id**&#xD;&#xA;"
/>
Parameters Description Examples