SeawaxLog User Manual
Contents
1. webapp process id useful when process pooling is enabled description if passed Everything is saved in the WxEvtLog data file DoLogAction can be called from anywhere in your application to log a specific action or status in your application Examples of this are Confirmation Order Email is send User Logged in Banner is clicked The description is again optional the action is a predefined action and will have to be added to the define enumeration list The following items will automatically be logged as well date time IP address visitor asp script page name webapp process id useful when process pooling is enabled description if passed Actions are saved in the WxAppLog data file DoLogError is to be used to add custom messages to your error log The normal way of doing this would be to call the Error command The downside of using the Error command is of course that it can display this error in the page You can call this to add extra info in the WxErrLog data file Class cWxWebAppError SeawaxLog User Manual Page 27 of 29 Private You should use the cWxLog class to communicate with the error handler This class allows you to have your webapp related errors to be redirected to a DataFlex error logging data file Doing so enables you to improve troubleshooting as you can log more related info and to automate handling the error This code is tested and written for Visual DataFlex 15 1 The cur2. You can also use the shortcut keys Ctrl Up Arrow and Ctrl Down Arrow to access these buttons SeawaxLog User Manual Page 15 of 29 Date Time Process ID User ID Description CustomDatal CustomD ata2 CustomD ata3 08 10 2010 Script Page 18 23 IP Address EE 2644 Action login asp 127 0 0 1 9 User Login Logged In Previous Close With the CustomDatan fields you can log up to three customizable data states to your log entry The description on how to do this is briefly discussed at the Adding User ID and login status to the logs example SeawaxLog User Manual Page 16 of 29 Page Event Date Time IP Page Request PID gt 28 25 2000 e 21 08 10 2010 18 23 127 0 0 1 invt asp POST 2644 08 10 2010 18 23 127 0 0 1 invt asp POST 2644 08 10 2010 18 23 127 0 0 1 invt asp POST 2644 08 10 2010 18 23 127 0 0 1 invt asp POST 2644 08 10 2010 18 23 127 0 0 1 invt asp POST 2644 08 10 2010 18 23 127 0 0 1 invt asp POST 2644 08 10 2010 18 23 127 0 0 1 invt asp GET 2644 08 10 2010 18 23 127 0 0 1 login asp POST 2644 08 10 2010 18 23 127 0 0 1 login asp GET 2644 08 10 2010 16 10 127 0 0 1 invt asp POST 3148 08 10 2010 16 09 127 0 0 1 invt asp POST 3148 08 10 2010 16 08 127 0 0 1 invt asp POST 3148 08 10 2010 16 08 127 0 0 1 invt asp POST 3148 08 10 2010 16 08 127 0 0 1 invt asp GET 3148 08 10 2010 16 08 127 0 0 1 invt asp POST 3148 08 10 2010 16 08 12
3. Down here we illustrate how to set User ID and logged in status only but the method for setting custom data is exactly the same In our order entry workspace example the user id and logged in status of the current user is stored in a cookie So down here we get this information from the cookie in your system it could come from a datafile or a property somewhere The method is still pretty much the same The file to look at is WxLog wo This webobject is in its default form completely empty see the SeawaxLogLib Web library for this version In the order entry example we have copied that file into the workspace and added the following code Use cWxLog pkg Object oWxLog is a cWxLog Function UserNameFromCookie Returns String String sUserName Move To sUserName Get Cookie User Name To sUserName Function_Return sUserName End_Function UserNameFromCookie Function LoggedInStatusFromCookie Returns Boolean Boolean bIsLoggedIn String sValue Move False To bIsLoggedIn Get Cookie Rights To sValue If sValue 1 Move True To bIsLoggedIn Function Return bIsLoggedIn End Function LoggedInStatusFromCookie You can use this method in your object instantiation of this class to have SeawaxLog User Manual Page 8 of 29 VA l Pr En End The it populate any of the following properties psCurrentUserID pbLoggedIn psCustomData1 psCustomData2 psCustomData3 If you fill these in
4. registered msg Calling nUndefinedMessageHere YDF Errortt 4375 in line 8660 Previous Next Close The details screen gives you more information about the error and the origination of the error Besides the fields also in the list view you can see here Error Line Number which is the normal error line number as in the default error object User ID If your webapp identifies user by ID number or name then you can set this field from within a CallBack method accordingly See WxLogs pkg Origin Object if the error was triggered from within a datadictionary then the origin object will show the name of the datadictionary that triggered the error Primary Key if a record is in memory then the PK form will contain the unique record ID field data of the main datadictionary Operation is the datadictionary operation when the error occurred Processed is a field that indicates if the error has been read by the process that generates the email Basically it tells you if an email has been send to the administrator Logged in this value can be set from within a CallBack method in WxLogs The Previous and Next buttons allow you to select previous or next lines in the underlying list view In other words you can use them to see the next or previous error SeawaxLog User Manual Page 11 of 29 You can also use the shortcut keys Ctrl Up Arrow and Ctrl Down Arrow to access these buttons ois oeat 3 Date 0
5. the quotes Next e Application Name SeawaxLog Click Finish You can now access the demo application from your browser at http localhost SeawaxLog SeawaxLog User Manual Page 5 of 29 Examples The standard Order Entry workspace has been renamed to SeawaxLog and has been extended with examples on how to use the SeawaxLog libraries Below we ve highlighted some of those examples to show the most important features Automatically adding page visits to the access log The method of automatically adding your page to the access log is very easy At the top of each asp page add the call DoLogPage as follows you can see this in each asp page in the example workspace If you already call a standard method from the top of your page then it is suggested that you add the call in there as that would mean you wouldn t have to change all of your asp pages The method will still be able to detect from which asp page the call is invoked So your asp page should look like this lt oWxLog call msg_DoLogPage gt lt html gt lt head gt Or if your first call on each page is called InitPage as in lt oSession call msg_InitPage gt lt html gt lt head gt Then augment your InitPage method in the oSession Web Object as Procedure InitPage Send DoLogPage Of ghowxLog the rest of your method End Procedure InitPage Adding login event to the action log In order to follow the status of what ha
6. 7 0 0 1 invt asp GET 3148 Logs access of end user visits to your pages This logs every page that you have added the DoLogPage logic to If you are tracing an error you might want to use this to backtrack what steps the user has exactly taken to trigger the problem You can do that by matching up date time process ID and if saved things like User ID logged in status The Previous and Next buttons allow you to select previous or next lines in the underlying list view In other words you can use them to see the next or previous error You can also use the shortcut keys Ctrl Up Arrow and Ctrl Down Arrow to access these buttons SeawaxLog User Manual Page 17 of 29 Script Page triggererrort asp Time IP Address 127 0 0 1 Process ID Request Method G User ID Logged In Description SeawaxLog User Manual Page 18 of 29 Application Actions _ Application Actions ActionlD Description 10 Login failed 11 New Page 12 Page Not Found 13 Helper Page 21 New Banner 22 Banner Clicked 30 Insufficient Rights 40 Time out 50 Redirect 70 Search Contractor 71 Search Retailer 80 Quiz Start 81 Quiz Success 82 Quiz Failed 83 Quiz Mail Confirmed 1100 New Product Saved 101 Product details updated SourceCodelD ACTION NEW PRODUCT Comment Send when new product gets saved into the database Application Actions are a dynamic feature to allow you to track if a certain event happene
7. 8 25 2010 Script Page triqgererrorl asp Time 21 52 Origin Object 0 Error Number 4375 Primary Key Line Number 8660 Operation Ww Process ID 2780 Processed User ID Logged In Description Method interface not registered Call Error Message not registered msg_Calling4nUndefinedMessa MSG ERROR REPORT 433 OW gt WEBAPPERROR 18 at address 14317 GET DOCALL 1284 OSALESP 174 at address 8660 MSG_ONDFFUNC 4880 OVDFINETSESSION 33 at address 7213 MSG_STARTWEBAPP 5240 OWEBAPP 31 at address 11395 start at address 17153 Previous Next Close Having the stack trace of when an error occurs can sometimes provide you with a direct clue of why the error happened In this example it tells you that the undefined method in the script page triggererrorl asp is not published in object oSalesp SeawaxLog User Manual Page 12 of 29 i Oo Date 08 10 2010 Script Page inyt asp Time 18 23 Origin Object 0 Error Number 28 Primary Key Line Number 3935 Operation wW Process ID l Processed User ID l Logged In Description Duplicate records not allowed in file 0 i SeawaxLog Datakinvt k1 Details Data Stack Trace Custom HTTP_ACCEPT image alf image sx xbitmap image peg image pjpeg application x shockwave flash application vnd ms excel application vnd ms powerpoint application msword application x ms
8. If you are using an SQL database backend my suggestion is to NOT migrate it to SQL as that way you ll be able to also log errors related to connectivity problems Add the SeawaxLib Web library to your workspace Your application needs just two lines of code to get the basics working Use AllWebAppClasses pkg Use cWxAllWebLogs pkg Object oApplication is a cApplication Object oWebApp is a cWebApp Use WxLog wo By putting the package before the cApplication object it ensures that the error handler is activated before any data files are opened You ll also need to add the following 5 files to your data folder just unzip the WxLogDatafiles zip datafiles into your data folder You do not need to add the files to the filelist cfg Filenumber FileName Function 3062 WxErrLog dat Error Log 3065 WxEvtLog dat Visiting pages Log 3066 WxAppAct dat Application Actions 3067 WxAppLog dat Application Log 3069 WxLogsSys dat Log System table After that the basics work and your errors will automatically be logged in the WxErrLog data file SeawaxLog User Manual Page 25 of 29 WebApp src X Ibwx Use AllWebAppClasses pkg A Use cWxAllWebLogs pkg a Object oApplication is a cApplication Set psCompany to Data Access Worldwide Set psProduct to Visual DataFlex Examples Set psVersion to 15 1 Set psProgram to Seawax Log Sample End Object Object oWebApp is a cWebApp Use WxLog wo Use Customer wo Use CustomerReport w
9. SeawaxLog User Manual Classes and applications to add pro active error monitoring and event logging to your webapp based applications and web services 1 Version 1 1 0 March 29 2011 2011 SeawaxLog is an Antwise Solutions product SeawaxLog User Manual Page 1 of 29 Index Ea RR RR EE 23 EE NE 24 Adding the code to your FORT il ap i dir 25 JEG RR 26 SeawaxLog User Manual Page 2 of 29 Introduction The SeawaxLog product is a set of classes and applications to automatically log and report runtime errors page access and application actions All of these events are logged to a database and can be easily inspected using the supplied support applications An application to automatically send email notifications when an error happens is included as well By using this product you have much better control to act upon problems in your product that are otherwise missed when users fail to report the problem they bumped into When they do report problems you now have an audit trail of events with status of your application and things like a stack trace and HTTP POST headers to better pinpoint why this problem has happened The product has been designed in a modular way and consists of the following main components Windows based support applications e WxLogs application With this application you can view the log details It has a view for errors triggered pages viewed and actions happened e WxEmailErrors applica
10. application application x ms xbap application ynd ms xpsdocument application xaml xml HTTP ACCEFT LANGUAGE en us HTTP CONNECTION Keep Alive HTTP HOST localhost HTTP REFERER http ocalhost SeawaxLog Invt asp HTTP_USER_AGENT Mozilla 4 0 compatible MSIE 7 0 Windows NT 5 1 NET CLR 2 0 50727 NET CLR 3 0 4506 2152 NET CLR 3 5 30723 NET CLR 1 1 4322 HTTP COOKIE ASPSESSIONIDASRRCORC LFBFHMKAMBKPFBMML HKIDALB Rights 1 User FullN ame John J 2E S mith amp Pass john amp Name john HTTP U CPU x86 HTTP CONTENT LENGTH 176 HTTP CONTENT TYPE application x www form urlencoded HTTP_ACCEPT_ENCODING azip deflate Previous Next Close For a GET operation it means that the parameters passed on the URL are saved For a POST operation it means that all of the HTTP headers send during POST are saved SeawaxLog User Manual Page 13 of 29 Action Log la a Application Action Log fo ms Date Time Page Action Description me gt New Product Saved JACE 4 127 0 0 1 08 10 2010 18 23 invtasp Product details updated 127 0 0 1 08 10 2010 18 23 login asp User Login JOHN 127 0 0 1 08 10 2010 16 08 login asp User Login JOHN 127 0 0 1 08 10 2010 15 49 login asp User Login JOHN 127 0 0 1 08 06 2010 02 47 login asp User Login JOHN 127 0 0 1 08 06 2010 02 47 login asp Login failed JOHN 127 0 0 1 08 06 2010 02 46 login asp Login failed TEST 127 0 0 1 The action log can be used to lo
11. asp 06 16 2010 13 An entry is required on this windoy invt asp 06 16 2010 4375 Method interface not registered C triggererrorl asp 06 16 2010 4375 Method interface not registered C triggererror asp 06 16 2010 4375 Method interface not registered C 06 16 2010 4375 Method interface not registered C 06 16 2010 4375 Method interface not registered C 05 25 2010 13 An entry is required on this windor 05 25 2010 13 An entry is required on this windor You get a quick overview of the errors that have happened by opening the Error Log View from the View menu This list shows you the date time DataFlex error number triggered the webapp asp page from where the error was triggered and the windows Process ID PID of the webapp process triggering the error Knowing the PID helps you tracking the error when process pooling is enabled After selecting an error you can see more details by either double clicking on the row or by clicking on the details button below SeawaxLog User Manual Page 10 of 29 a a Error Log Details i Date 08 25 2010 Script Page triggererrorl asp Time 21 52 Origin Object 0 Error Number 4375 Primary Key Line Number 8660 Operation W Process ID 2780 Processed I User ID Logged In Description Method interface not registered Call Error Message not registered msg Calling nUndefinedmessa Details Data Stack Trace Custom Method interface not registered Call Error Message not
12. d in your web application This comes with several actions preset but you can add as many actions as you want As you need to be able to identify the action in your source code in a clear and concise way we have come up with the following solution You can freely define your actions here in this file Use Action ID 1001 and up to leave room for adding standard actions Then define SourceCodelD as a string prefixed with ACTION just as in the example above We want to log whenever someone creates a new product and have defined a source code constant ACTION NEW PRODUCT That s the code you will use in your source SeawaxLog User Manual Page 19 of 29 The way that works is that you can generate a new ActionCodes h header file from the system settings Actions tab see system settings section in the manual SeawaxLog User Manual Page 20 of 29 System Settings a ss i A System Settings Version 1 00 Mark Errors as Processed Log Details Custom Actions Log Errors Verbose Errors Log Actions Verbose Actions Log Events SsSssisi8 8 Verbose Events Save With the system settings dialog you can change certain behavior of the logging in your webapp For starters you can mark all errors as read so that if you just have been testing a bit and have collected a lot of errors in your log file that you don t get spammed by a lot of email if you activate your error email notifica
13. ere are times when you would want to log these state changes if only for auditing purposes or to team up with the other logs when you are troubleshooting For the purpose of this example we added the states New Product saved and Product Details Updated You can easily add these states in the Application Actions screen in the WxLogs application After regenerating the ActionCodes h file you can then log these states as follows see invt wo Object Invt_DD is a Invt_DataDictionary Set DDO_Server to Vendor_DD Send DefineAllExtendedFields Augmented to track when a user saves a new product or updates an existing one Procedure Request_Save Boolean bHasRecord Boolean bNewRecord String sItemID Move False To bNewRecord Get HasRecord To bHasRecord If bHasRecord false Begin Move True To bNewRecord End SeawaxLog User Manual Page 7 of 29 Get Field_Current_Value Field Invt Item_Id To sItemID Forward Send Request_Save If Err false Begin If bNewRecord Send DoLogAction Of ghowxLog ACTION NEW PRODUCT sItemID Else Send DoLogAction Of ghowxLog ACTION PRODUCT UPDATED sItemID End End Procedure Request Save End Object Invt DD Adding User ID and login status to the logs As mentioned before you can add application specific data to your logs using a callback mechanism Standard information would be a user ID and logged in status In addition to that you have 3 more custom data fields you can fill and set
14. g specific state changes also called an action in your application This is very useful as it only logs the state changes that you are interested in The Actions can be defined by you A nice example for that is the following screenshot M Application Action Log Aa x Date Time Page ction l Description JR fa 03 23 2011 18 24 39 ordersuccess asp Order payment complete Order 71 77 167 9 I 03 23 2011 18 21 59 orderconfirm asp Start payment Order 71 77 167 980 03 23 2011 18 21 59 orderconfirm asp Start order process 77 167 38 50 03 23 2011 18 21 39 login asp User Login Anke 77 167 985 03 10 2011 22 46 13 login asp User Login Wil van Antwerpen 217 149 208 61 El Details SeawaxLog User Manual Page 14 of 29 In the above screenshot you see that it is fairly easy to follow an ordering process in the action logs Please also note that the checkbox to only show the actions for logged in users has been checked a amp Action Log Details Date 08 10 2010 Script Page invLasp Time 18 23 IP Address 127 0 0 1 Process ID 2644 Action 0 New Product Saved User ID F Logged In i Description ACE 4 Data Custom Previous Next Close The detail view of the action log The Previous and Next buttons allow you to select previous or next lines in the underlying list view In other words you can use them to see the next or previous error
15. ile Below is a screenshot from such a file WxEmailErrors Notepad File Edit Format View Help website R Host www example com Description Example mail RecipientName The Site Administrator RecipientAddress adminGexample com FromName WxEmailerrors Error ExcludeList 13 28 41 42 Website section The host field can be used to identify the website for which this is run The description field is used as a subject line along with the error message Mail section This section speaks a bit for itself you set the sender as FromName FromAddress and the recipient of the automatic email as RecipientName RecipientAddress SeawaxLog User Manual Page 23 of 29 Error section The excludelist is a comma separated list that allows you to filter which errors you do not want to see an email from Some errors trapped by the error handler are not critical take for example error 13 An entry is required error In pretty much all cases that is an error which is expected and doesn t need any action WxTestEmailConfig This little program can be run to test the email setup configuration file When you run this it will read the WxEmailErrors ini file and gives you an easy means to test if the automated email service WxEmailErrors should work SeawaxLog User Manual Page 24 of 29 Adding the code to your workspace You ll have to add the Wx data files to your datafolder
16. ins both connections and errors in the same log Finding error reports is difficult on a busy web site The event log view even becomes non responsive when you try to navigate it If you turn off the logging in the Web Application administrator tool uncheck Log all access to the Web Application it only logs the errors Problems with this event log are 1 Unfortunately it is still difficult to navigate when a user connects or a new error is triggered the cursor skips back to the top 2 There s no way you can get that info except by logging into the host In most cases the host is remote which complicates things a bit 3 It just has the error and line which quite often is not enough to troubleshoot the problem 4 There s no way to extend it no way to read the data outside of webapp administrator the solution is completely proprietary b Windows event logs The errors to look for here are spread over the application log problems with your webapp processes and the system log problems with the service Of course any other windows error is also in here so if you re not lucky you ll be searching like crazy The solution By logging errors directly to a data file you now have the ability to do anything you like with the error data Examples of what can be done are You can create a web page to browse recent errors Automatically email yesterday s errors in the morning Email critical errors happening on
17. ivity of your web application It also logs details such as page accessed IP number date time SeawaxLog User Manual Page 29 of 29
18. o Use Invt wo Use Login wo Use OrderDtlReport wo Use OrderReport wo Use SalesP wo Use Vendor wo mn Procedure OnAttachProcess Forward Send OnAttachProcess Will only log on session attach if session pooling is enabled Send DoLogPage Of oWxLog Attach session End Procedure DoAttach Procedure OnDetachProcess Forward Send OnDetachProcess Will only log on session detach if session pooling is enabled Send DoLogPage Of oWxLog Detach session End Procedure DoAttach Class cWxLog This class allows you to have your webapp log a variety of details to a set of DataFlex data file This enables you to create auditing troubleshooting and store visiting log data The web object contains handles to call the following methods DoLogPage DoLogAction SeawaxLog User Manual Page 26 of 29 DoLogError There s a global variable called ghoWxLog which holds the object ID of the oWxLog instance and which can be used without having to refer to the oWxLog web object DoLogPage can be used to track what is happening The webobject method is supposed to be called from the top of your page In its most bare form call it from asp If you already have an initialize method that you call then you can just call the method from within webapp directly You can pass it a description but that s optional It will automatically log things such as date time IP address visitor asp script page name post or get method
19. rent version of the webapp errorhandler errorlog data file has the following fields 1 standard line and extended error string 2 if it is a datadictionary error for a recnum table the value in the record identity RECNUM and fields and data that make up index 1 for anon recnum table the fields that make up primary index and the data in the primary index 3 the name of the originating object where the error was triggered 4 the datadictionary operation when the error was triggered save delete clear find 5 Of course date time when the error happened What has been added is 1 The ability to filter out don t report datadictionary required errors 2 Add the asp page name called when the error happened not for web services 3 Make vdf15 1 compatible which includes adding stack traces to the log for errors 4 Some of the content of the response header object querystring referer page UserAgent Remote Address Method type like GET or POST 5 If one identifies users by having them log in to your webapp Then there s a callback method so you can add the user name into the logs Class cWxWebApplicationLog Private Used to log events of your web application An event is for example a user logging in successfully a failed login starting a particular process In addition it also logs details such as page accessed IP number date time SeawaxLog User Manual Page 28 of 29 Class cWxWebEventLog Private Used to log act
20. s happened while you are trying to unravel a problem it can be very useful to log certain interesting state changes of your application For example your application is likely to have a different behavior when someone is logged in in comparison to not logged in Knowing which user has logged in can be useful too SeawaxLog User Manual Page 6 of 29 In general the way to do that is to augment your login method In the example workspace that is in the login wo web object Function Login_User String sUserId String sPass Returns Integer Integer bOk clear Login DD Move values to file buffer and attempt a find EQ Get ddClear Users To bOk Send setDDValue Users loginName Uppercase sUserid Send setDDValue Users password Uppercase sPass Get ddFind Users 2 Eq To bok If bok Send DoLogAction Of ghowxLog ACTION USER LOGIN Uppercase sUserid Else Send DoLogAction Of ghoWxLog ACTION LOGIN FAILED Uppercase sUserid Function Return bOK End Function The last parameter in the call to DoLogAction Uppercase sUserId is added as the description to your action log entry This is a free field you can put other info in there as well Adding application specific events to the action log The action logging has been designed to make it easy to customize it to your application In the Order Entry example we are maintaining a simple ordering system and it has a very basic inventory system where you can add or change products Th
21. then the data that is used is saved in any of the log fil s ocedure onUpdateLog String sCurrentUserId Boolean bLoggedIn Get UserNameFromCookie To sCurrentUserId Get LoggedInStatusFromCookie To bLoggedIn Set psCurrentUserID To sCurrentUserID Set pbLoggedIn To bLoggedIn d_Procedure onUpdateLog Object oWxLog onUpdateLog method is a so called callback method and is called from within each write action to the log It allows you to set the five properties psCurrentUserID pbLoggedIn psCustomData1 psCustomData2 and psCustomData3 SeawaxLog User Manual Page 9 of 29 SeawaxLog support applications WxLogs An easy way to inspect the SeawaxLog logfiles is to start the WxLogs application It has a variety of views that give you an easy insight into the collected data Error Log Every time an error is triggered by the webapp or webservice it gets written out into the Error Log Time Error ft Description 08 25 2010 ethod interface not registered Ceftri 08 10 2010 28 Duplicate records not allowed in fi invt asp 08 10 2010 28 Duplicate records not allowed in fi invt asp 08 10 2010 13 An entry is required on this windoy invt asp 08 10 2010 28 Duplicate records not allowed in fi invt asp 08 06 2010 4375 Method interface not registered C triggererrorl asp 06 16 2010 13 An entry is required on this windoy invt asp 06 16 2010 13 An entry is required on this windoy invt asp 06 16 2010 13 An entry is required on this windoy invt
22. tion This application can be setup to run as a scheduled task to automatically send any errors that happened by email e WxTestEmailConfig application A simple application to test your current email settings The SeawaxLog example workspace An example workspace which is based on the standard order entry application from Data Access Worldwide which has some small changes made to it to highlight how to use the techniques in question The SeawaxLogLib Web Library This library contains all of the code needed for your webapp projects and webservices It only has to be added to your project and can be included and activated with a few lines of code The SeawaxLogLib Win Library This library contains all of the code needed for the windows based support applications It only has to be added to your project after which you can compile the aforementioned support applications from above A set of DataFlex data files that you have to add to your application which are used to save the logging data It is suggested to keep these files as DataFlex files as that way you can also log any database connectivity kit related errors SeawaxLog User Manual Page 3 of 29 Background reasons for writing this product The reason this product is born is that it gives you a one stop place to check if problems occur Without this tool whenever there s problems you ll have to check the logs from a WebApp administrator By default the event log conta
23. tions Another thing you can tweak here is to actually enable disable any of the logs Setting the verbosity level to true checked has the effect that the HTTP headers are saved during a GET or POST action SeawaxLog User Manual Page 21 of 29 Log Details Data Column 1 Label Data Column 2 Label Data Column 3 Label You can set the labels that are shown in the WxLogs application for custom data that you want to be stored with your logs By setting the labels here you don t have to remember what CustomData1 actually stands for Version 100 Mark Errors as Processed Custom Actions Next Action ID Source File DA SSeawaxLogLib web AppSre Generate Action Header Source File SeawaxLog User Manual Page 22 of 29 WxEmailErrors The WxEmailErrors application can be used to automatically send the web site administrator an email with all the technical details whenever an error has been triggered In order to do this the application has its own embedded smtp send control which allows you to send the email directly via smtp The idea is to run this application on your web host automatically every 10 minutes or so using the standard windows tasks feature This way if a user triggers an error in your service or webapp you will get this information automatically by email and take direct action if needed As this application has no user interface at all it is configured via a standard windows INI f
24. your web site directly to the web site administrator this is part of the product host license or better SeawaxLog User Manual Page 4 of 29 SeawaxLog example Workspace Installing the SeawaxLog example workspace The example workspace SeawaxLog has to be registered in the Visual DataFlex Studio to properly use it The SeawaxLogLib Web library contains the code which takes care of the actual logging The SeawaxLogLib Win library contains the code for the windows support applications You ll need to register the SeawaxLog workspace in the Studio by going to the menu and choosing File gt Open Workspace and selecting the sws file After you have done that add the SeawaxLogLib Web and SeawaxLogLib Win libraries to the SeawaxLog workspace via menu option Tools gt Maintain Libraries r Library Maintenance Libraries used by this workspace ASeawaxLogLibywebiS eawaxLoaLib web sws SeawaxLogLib win S eawaxLogLib win sws Add Library Remove Library Cancel hem In order to run the webapp example you must register the webapp using webapp administrator using the following steps e File gt Configure New Web Application e Select Local Applicaton Configuration Click Next e Now browse to the webapp exe under the SeawaxLog workspace Click Next e Select Process Pooling if you want or leave it at the default Next e Change Virtual Directory Name into SeawaxLog Without
Download Pdf Manuals
Related Search