Differences between revisions 1 and 6 (spanning 5 versions)
Revision 1 as of 2008-07-27 17:50:00
Size: 2550
Editor: KaiJaeger
Comment:
Revision 6 as of 2008-12-15 18:51:44
Size: 2675
Editor: KaiJaeger
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
[[TableOfContents]] <<TableOfContents>>
Line 6: Line 6:

'''currently under construction'''
Line 17: Line 15:
[[ImageLink(windowseventlog.jpg)]] [[attachment:windowseventlog.jpg|{{attachment:windowseventlog.jpg}}]]
Line 47: Line 45:
For a full version history: [:WindowsEventLog/History: History] For a full version history: [[WindowsEventLog/History| History]]
Line 57: Line 55:
Goto the [:WindowsEventLog/DownloadPage:DownloadPage]
[[http://aplteam2.com/aplwiki/WindowsEventLog?action=AttachFile&do=view&target=WindowsEventLog.ZIP | Download right now]]

[[attachment:WindowsEventLog.ZIP | Manage the attachment]]
Line 60: Line 61:
CategoryOpenSourceApl CategoryAplAplDyalog CategoryOpenSourceApl CategoryAplApl

Managing the Windows Event Log

Overview

This class offers methods useful to read from and write to the Windows Event Log.

The Windows Event Log is important to many large organisation due to the fact that servers situated in a special room cannot be accessed easily, not even by an administrator, and that monitoring them has to be done remotely as a conseqence. The Windows Event Log can be easily monitored remotely and is therefore the ideal place to report "Start", "Stop", "Fatal Error", Security problems and more.

Windows Event Log Classes

There are a number of so-called classes available in the Windows Event Log:

attachment:windowseventlog.jpg

There might be others as well. It is possible to create your own class, although this is not recommended.

An APL application programmer is likely to want to write into the "Application" class. Therefore, the WindowsEventLog class defaults to that Window Event Log class.

Source

Note that within a class you must specify a source, normally your application name. Note further that the name of the source must be unqiue across all classes, not only the class you try to write to!

Example: there is a source "Server" in the "Application" class on my machine. Although I can create a new class "MyAppl", I cannot use "Server" as a source name as a consequence!

.NET

The WindowsEventLog class uses .NET but tries to hide everything not needed for an APL application programmer, or to use appropriate defaults.

Security

Using this class without Admin rights, for example when your application runs as a service, needs "EventLogPermission" rigths. On a server you cannot control this might be a problem. Microsoft explicitly points out that granting this right is a security risc and should therefore only be given to code that is fully managed (trusted).

Example

 my←⎕NEW #.WindowsEventLog(,⊂'MyApp')
 my.WriteInfo 'Server started'
 my.WriteWarning 'Low on memory'
 my.WriteError 'Fatal error, server stopped'
 my.WriteInfo 'Server started'

History

For a full version history: History

Version Information

Original author:

KaiJaeger

Responsible:

KaiJaeger

Email:

kai@aplteam.com

Current state:

1.0

Download

Download right now

Manage the attachment


CategoryOpenSourceApl CategoryAplApl

WindowsEventLog (last edited 2018-03-03 11:36:54 by KaiJaeger)