AutoCommand 20036 Guía de instalación descargar pdf (Pagina 85)

logging capability. It is possible to set SalesEZ's verbosity to zero, and still get a verbosity 5 log based on an

expression, for certain salespoints or certain operators or even certain function calls. Additionally, a new

streamlined log type can be enabled to capture statistics for length of time spent on calls, waiting for SQL Server

and logging. Instructions for using this will be provided in a separate document

4058Logging_options_in_SalesEZ and 4101Logging_options_in_Middleware.

When killing an instance of an EZ from the service monitor doing so will no longer kill the SQL connection for the

other live instances.

All log filenames for middleware components now start with the middleware component name and will always be

found in the ProgramData Pool\EZ folder.

Examples:

SalesEZ_Log.txt, SalesEZ_LongCallsAndErrors.txt, SalesEZ_MemoryDump.txt,

SalesEZ_Transact_Dump.txt and SalesEZ_Performance_20110309_Log.txt -

LongCallsAndErrors log files will now contain entries for all logged errors. Formerly log entries with an 'E'

value would only appear in the LongCallsAndErrors log if the developer made a separate (addition) call to a

different log routine. This is now automatic, so we should see more information in this log.

The ability for Sales to get a verbosity 5 log from SalesEZ was added using the tag set

<ReturnLog>Yes</ReturnLog>. If this is present in the call, SalesEZ will append the verbosity 5 log for that

call to the regular return value inside the <SalesEZLog></SalesEZLog> tags. This is for a future

enhancement to allow Sales to capture SalesEZ logs from the salespoint.

Logging options in Middleware(EZ)*

We have several logging options available to us now in the EZ’s. Below is a description of each. The first two,

Verbosity Level and Log Invoke, have been available in the software since nearly its inception. The newest form of

logging, added in January 2011, is Performance and Filtered logging. Here are outlines of each type:

VerbosityLevel

This is the standard we use everywhere in our applications. You can set the verbosity in the Sales32c.INI file,

and that will be the default level of logging when the application starts. In most applications, this is the only place

you can set this value. With our middleware components (SalesEZ, BookEZ, TallyEZ, RentEZ applications), you

can also adjust the verbosity “live” by using the PoolManager application in 4.0 or the Service monitor in 4.1. The

other special thing about the middleware applications is that even if you start with a verbosity 5 in the EZ.INI file,

Pool will still set it back to 0 in 6 hours. Pool will do this when you alter the verbosity level during operation as

well.

1 2 ... 80 81 82 83 84 85 86 87 88 89 90 ... 182 183

Sin comentarios

AutoCommand 20036 Guía de instalación Pagina 85