Hi To follow up on Dale's mail
The standard FME log file is excellent for development, and debugging, but in a production environment we just want to log the key parameters (MACROS and statistics) to check that everything is working OK. In a project i am working on I have implemented a logging system based on the FME_BEGIN_TCL / FME_END_TCL using tclodbc to log the data to a Access database, I have attached the mapping file fragment I use and the tcl scripts 1. The FME_TCL_LOG.FMI file is Included in the main mapping file 2. The BeginEnd.tcl dos the actual logging (and zipping of the data set) 3. Kmsodbc.tcl is an attempt to write a general script to use with fme/tcl and odbc 4. Xldslog.def is using fme's syntax to describe the database, allowing the system to run a auto setup, note, the name of this file is the name of the DSN, allowing you to have more than one connection 5. Zipdata.tcl is the function i use to zip the resulting data set, it use the zip.exe that comes with SpatilDirect This is still a beta but working quit well. But there is still some issues around how to handle errors, and in some cases it not logging in batch mode. Peter Laulund National Survey and Cadastre, Denmark >From: "Dale Lutz" <[EMAIL PROTECTED]> >Reply-To: [email protected] >To: <[email protected]> >Subject: RE: [fme] change log generation >Date: Sun, 3 Apr 2005 23:31:35 -0700 > > >Hello Julien, > >This type of thing has been asked a few times, and so we came up with a >general mechanism for FME 2005 which flexibly addresses this. > >We posted a note about it recently -- its at: > > http://www.mail-archive.com/[email protected]/msg00255.html > >(among other places), and will be part of our documentation when FME 2005 >is >finalized. > >It will tell you how you can use a post-process to write out only what you >want, if you carefully look through the examples, you will see how you can >do >this. > >I hope this is useful. If you'd like to engage our professional services >folks to give you a few hours of help on setting this up for your >particular >needs, we are able to do this -- contact [EMAIL PROTECTED] > >Dale > >---------------------------------------------------------------------- >Dale Lutz Safe Software Inc. [EMAIL PROTECTED] >VP Development Surrey, BC, CANADA phone: (604) 501-9985 > http://www.safe.com fax: (604) 501-9965 >---------------------------------------------------------------------- > > > > > > -----Original Message----- > > From: julien_jacquier [mailto:[EMAIL PROTECTED] > > Sent: Thursday, March 31, 2005 6:58 AM > > To: [email protected] > > Subject: [fme] change log generation > > > > > > > > > > hello, > > I'm french developper. I begin with fme and i'd like to change log's > > format. > > For exemple i just want "STATS" (no INFORM, WARN...) when fme is in > > production (with number of features written). What's the option(s) to > > add at the end of my command line? > > > > thanks for your help. > > Julien. > > > > > > > > > > > > > > > > > > Get the maximum benefit from your FME, FME Objects, or SpatialDirect via > > our Professional Services team. Visit www.safe.com/services for >details. > > Yahoo! Groups Links > > > > > > > > > > > > > > >Get the maximum benefit from your FME, FME Objects, or SpatialDirect via >our Professional Services team. Visit www.safe.com/services for details. >Yahoo! Groups Links > > > > > > > _________________________________________________________________ F� alle de nye og sjove ikoner med MSN Messenger http://messenger.msn.dk/ Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
BeginEnd.tcl
Description: Binary data
XLDSLOG.DEF
Description: Binary data
kmsodbc.tcl
Description: Binary data
zipdata.tcl
Description: Binary data
Navn : Peter Laulund, KMS
Oprettet dato : 11 januar 2005 - 13:19
Beskrivelse :
ToDo : Kopiering af logfilen til dataRoot skal ske via denne
rutine da jeg kender navnet p� den aktuelle logfil
det sker bl.a. hensyn til jar/so-ajour
============================================================================*/
# =============================================================================
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FME_BEGIN_TCL source {$(Dir2mf)\TCL\BeginEnd.tcl} ; beginTcl ; \
array set lds {dataset {$(Dataset)} \
format $(Format) \
proj $(DestCoordSys) \
plusminus $(plusminus) \
Dim $(Dim) \
BBOX $(BBOX) \
Y1 $(Y1) \
X1 $(X1) \
Y2 $(Y2) \
X2 $(X2) \
noproj $(noproj) \
cut $(cut) \
udtrType $(udtrType) \
name $(name)} ; \
catch { set lds(admkode) "$(AdmKode)" } ;
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FME_END_TCL endTcl
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# =============================================================================
