APL Wiki|
Size: 3145
Comment: New version: minor fix
|
← Revision 28 as of 2018-03-03 11:36:54 ⇥
Size: 135
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| {{{WindowsEventLog}}} is part of the CategoryAplApl project. <<TableOfContents>> == 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|{{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: [[WindowsEventLog/History| History]] == Version Information == ||Original author:||KaiJaeger|| ||Responsible:||KaiJaeger|| ||Email:||kai@aplteam.com|| ||Current state:||1.0.2|| == Download == You have two options: you can either download the script for usage: [[http://aplwiki.com/WindowsEventLog?action=AttachFile&do=get&target=WindowsEventLog.ZIP | Download WindowsEventLog script right now]] or get the whole thing from the AplWikiRepository, including the development workspace and the script and maybe more for any development or for running the test cases: {{{ svn list svn://aplteam.com/os/dyalog/WindowsEventLog/tags }}} If you plan to contribute please note that all stuff published as part of the APLAPL project must follow certain [[AplAplStandards|APLAPL-specific standards]]. ---- CategoryAplApl |
The project has been relocated to [[https://github.com/aplteam/WindowsEventLog]] on 2018-03-03. |
Managing the Windows Event Log
The project has been relocated to https://github.com/aplteam/WindowsEventLog on 2018-03-03.