Cloud CM-IPMP Anleitung zur Fehlerbehebung Seite 79
- Seite / 201
- Inhaltsverzeichnis
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
Chapter 10
Log System Configuration
10.1 Introduction
The Rhino SLEE uses the Apache Log4J logging architecture (
http://logging.apache.org/
) to provide logging facilities to
the internet SLEE components and deployed services. This chapter explains how to set up the Log4J environment and examine
debugging messages.
SLEE application components can use the Trace facility provided by the SLEE for logging facilities. The Trace facility is
defined in the SLEE 1.0 specification, and Trace messages are converted to Log4J messages using the NotificationRecorder
MBean.
10.1.1 Log Keys
Subsystems within the Rhino SLEE send logger messages to various appropriate logger keys. An example logger key is
"rhino.facility.alarm", which periodically receives messages about which alarms are currently active within the Rhino SLEE.
Logger keys are hierarchical. Parent keys receive all messages that are sent to child keys. For example, the key "rhino.facility"
is a parent of "rhino.facility.alarms" and so it receives all messages destined to the "rhino.facility.alarms" key.
The root logger key is aptly called "root". To get a list of all logger keys, one could use the "listLogKeys" command in the
Command Console.
10.1.2 Log Levels
Log Levels determine how much information is sent to the logs from within the Rhino SLEE. A log level can be set for each
logger key.
If a logger does not have a log level assigned to it, then it inherits its log level from its parent. By default, the root logger is
configured to the
INFO
log level. In this way, all keys will output log messages at the
INFO
log level or above unless explicitly
configured otherwise.
Note that a lot of useful or crucial information is output at the
INFO
log level. Because of this, setting logger levels to
WARN
,
ERROR
or
FATAL
is not recommended.
Table 10.1 lists the logger levels that control logger cut-off filtering.
10.2 Appender Types
After being filtered by logger keys, logger messages are sent to Appenders. Appenders will append log messages to whatever
they’re configured to append to, such as files, sockets or the Unix syslogd daemon. Typically, an administrator is interested in
file appenders which output log messages to a set of rolling files.
The actual messages that each appender receives is determined by the loggers
AppenderRefs
.
70
- Open Cloud Rhino SLEE 1.4.3 1
- Administration Manual 1
- November 2, 2006 (1838) 2
- Contents 3
- Introduction 10
- The Rhino SLEE Platform 12
- 2.3 Integration 13
- 2.4 Service Development 14
- 2.5 Functional Testing 15
- 2.6 Performance Testing 15
- 2.7 Software Development Kit 16
- JAIN SLEE Overview 17
- 3.3 Event Driven Applications 18
- 3.4 Components 18
- 3.5 Provisioned Data 18
- 3.6 Facilities 18
- 3.7 Activities 19
- 4.2.3 Firewalls 22
- 4.2.4 Unpacking 22
- 4.2.5 Installation 22
- 4.2.6 Unattended Installation 23
- 4.2.7 Configuring a Cluster 23
- 4.2.9 Configuring the Cluster 25
- 4.3 Cluster Lifecycle 26
- 4.3.2 Starting a Node 27
- 4.3.3 Starting a Quorum Node 27
- 4.3.4 Automatic Node Restart 27
- 4.3.5 Starting the SLEE 27
- 4.4 Management Interface 28
- 4.5 Setting the system clock 29
- 4.6 Optional Configuration 30
- 4.7 Installed Files 31
- 4.8 Runtime Files 32
- 4.8.2 Logging output 33
- Management 35
- 5.2 Management Tutorials 36
- 5.3 Building the Examples 37
- 5.5 Installing a Service 40
- 5.6 Uninstalling a Service 43
- 5.8 Creating a Profile 46
- 5.9 SLEE Lifecycle 50
- 5.9.4 The Stopping State 51
- 5.9.2 The Starting State 51
- 5.9.3 The Running State 51
- Administrative Maintenance 52
- 6.2.2 Removing Activities 54
- 6.2.3 Inspecting SBBs 55
- 6.2.4 Removing SBB Entities 56
- 6.2.5 Removing All 56
- 6.3 Upgrading a Cluster 57
- 6.3.3 Deploying State 58
- 6.4 Backup and Restore 59
- Export and Import 60
- 7.2 Exporting State 61
- 7.3 Importing State 62
- 7.4 Partial Imports 63
- Statistics and Monitoring 65
- 8.2 Performance Implications 66
- 8.3 Console Mode 66
- 8.3.1 Useful output options 67
- 8.4 Graphical Mode 68
- Web Console 73
- 9.2.2 Managed Objects 74
- 9.2.3 Navigation Shortcuts 74
- 9.3 Deployment Architecture 75
- 9.3.2 Standalone Web Console 76
- 9.4 Configuration 77
- 9.5 Security 77
- 9.5.2 Declarative Security 78
- 9.5.3 JAAS 78
- Log System Configuration 79
- 10.3 Logging Configuration 80
- 10.3.2 Web Console Logging 81
- Chapter 11 84
- 11.2.2 Web Console 85
- Threshold Alarms 87
- 12.5 Types of Rule Conditions 88
- 12.6 Creating Rules 89
- 12.6.2 Command Console 90
- Chapter 13 92
- 13.3.1 Configuration 93
- Licensing 94
- 14.2 Alarms 95
- 14.2.4 Management Interface 96
- 14.2.5 Audit Logs 96
- Security Configuration 97
- 15.3 Network Connections 98
- 15.4 Signing Deployable Units 99
- 15.5 Key Stores 100
- 15.6 Transport Layer Security 100
- 15.7 JAAS Configuration 101
- Performance Tuning 103
- 16.2.3 Tuning Recommendations 104
- 16.2.1 Configuration 104
- 16.2.2 Stage Tuning 104
- 16.3 Object Pool Configuration 105
- 16.4 Fault Tolerance 106
- Clustering 109
- 17.3 Scenarios 110
- 17.4 Configuration Parameters 111
- Application Environment 113
- 18.2.2 Concurrency Control 114
- 18.3 Application Configuration 115
- 18.5.4 Example 119
- 18.6 Application Fail-Over 120
- 18.6.2 Management Interface 121
- Database Connectivity 122
- 19.3 Configuration Example 123
- 19.4 SBB use of JDBC 124
- 19.4.1 SQL Programming 125
- J2EE SLEE Integration 127
- PostgreSQL Configuration 131
- 21.4 TCP/IP Connections 132
- 21.5 Access Control 132
- SIP Example Applications 138
- 22.2 System Requirements 139
- 22.3 Directory Contents 139
- 22.4 Quick Start 139
- 22.4.2 Building and Deploying 140
- 22.5 Manual Installation 144
- 22.6 Using the Services 152
- 22.6.4 Enabling Debug Output 156
- JCC Example Application 157
- 23.2.1 Resource Adaptor 158
- 23.2.3 Service Logic 160
- 23.3 Directory Contents 163
- 23.4 Installation 163
- 23.6.1 Trace Components 170
- 23.6.3 Creating a Call 171
- 23.7 Call Duration Service 172
- Customising the SIP Registrar 178
- 24.4 Extending with Profiles 181
- Hardware and Systems Support 182
- A.2.4 Application Example 184
- Redundant Networking 186
- Entities 191
- C.3 Configuration Properties 192
- C.4 Entity Binding 193
- Transactions 194
- D.3.3 Summary 195
- D.4.3 Commit Protocols 196
- Audit Logs 197
- E.2 Example Audit Logfile 199
- Glossary 200
ProSoft Technology ProLinx S3964R Handbücher
Bedienungsanleitungen und Benutzerhandbücher für Gateways / Controller ProSoft Technology ProLinx S3964R.
Wir stellen 6 PDF-Handbücher ProSoft Technology ProLinx S3964R zum kostenlosen herunterladen nach Dokumenttypen zur Verfügung Bedienungsanleitung
Kommentare zu diesen Handbüchern