{"id":3608,"date":"2020-11-13T15:47:00","date_gmt":"2020-11-13T23:47:00","guid":{"rendered":"https:\/\/alt2.minisoft.com\/support\/?p=3608"},"modified":"2022-09-23T10:27:36","modified_gmt":"2022-09-23T17:27:36","slug":"logging","status":"publish","type":"post","link":"https:\/\/minisoft.com\/support\/logging\/","title":{"rendered":"eFORMz Logging"},"content":{"rendered":"

eFORMz has flexible logging options for the eFORMz Composer and the Director. How you configure your logs depends on your business requirements. The primary use of logs is to help troubleshoot problems or unusual conditions.<\/p>\n

Separate logs are kept for the eFORMz Composer and the Director, and each Director configuration file has an associated log file. The default location for all logs is C:\\Minisoft\\eFORMz_6\\log\\. All logs include the following options:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Logging option<\/strong><\/td>\nDescription<\/strong><\/td>\n<\/tr>\n
Log to File<\/td>\nWrites log data to a specified file.<\/td>\n<\/tr>\n
Append<\/td>\nAdds log data to the current log file until the File limit, Roll Count, or Reset time is reached.<\/td>\n<\/tr>\n
\u00a0Log File<\/td>\nNames the path and name of the log file when Log to File is checked. The current log file has no suffix. The most recently closed log has a suffix of _001, and older logs having larger numbers.<\/td>\n<\/tr>\n
\u00a0File limit<\/td>\nThe maximum size of a log file before a new log file is created.<\/td>\n<\/tr>\n
\u00a0Roll Count<\/td>\nThe maximum number of logs to keep. The oldest log file is deleted when a new log file is created. Zero means no limit exists on the number of logs to keep.<\/td>\n<\/tr>\n
\u00a0Reset time interval<\/td>\nThe time units that are associated with the Reset time value: Years, Months, Days or Hours<\/td>\n<\/tr>\n
\u00a0Reset time value<\/td>\nThe number of units associated with the value specified\u00a0in Reset time interval. A new log file is created (that is, the log is rolled) with the frequency specified in the two Reset fields. For example, if you specify two days,\u00a0a new log file is created every two days.<\/td>\n<\/tr>\n
\u00a0Message Priority Fence<\/td>\nLimits which types of messages are logged:\n

\u00a0<\/p>\n

    \n
  • 0 – 3: All messages<\/li>\n
  • 4 – 7: Not used<\/li>\n
  • 8 – 11: Status messages<\/li>\n
  • 12 – 15: Error and high-priority messages<\/li>\n<\/ul>\n

    Specifying a number below 8 can impact system\u00a0performance, but can be helpful during development and testing.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Logging eFORMz Composer activity<\/strong><\/p>\n

    Setting up eFORMz logging creates a logging profile for the eFORMz Composer. To specify eFORMz logging options:<\/p>\n

      \n
    1. Start the eFORMz Composer.<\/li>\n
    2. Click File > System Properties > Logging tab<\/li>\n<\/ol>\n

      Logging Director Toolkit activity<\/strong><\/p>\n

      You can have a unique log profile for each Director configuration file. To specify logging options for a Director configuration file:<\/p>\n

        \n
      1. Start the Director Toolkit and open the Director configuration file.<\/li>\n
      2. Right click the .cfg file name > Logging.<\/li>\n<\/ol>\n

        The log file should have the same name as the .cfg file to avoid confusion. The following image shows a typical logging configuration associated with invocies.cfg. A new log file is created every 7 days, and no more than 12 log files are kept. The oldest log file is deleted when a new one is created. Minisoft recommends a maximum log file limit of 10000000. Logs that exceed that size consume a great deal of storage and are not practical.\u00a0<\/p>\n

        \"Logging\"<\/p>\n\n\n

        <\/p>\n\n\n\n

        <\/p>\n\n\n\n

        <\/p>\n\n\n\n

        <\/p>\n\n\n\n

        Some configurations keep separate logs. For example, UNIX and Linux systems that use the eFORMz Printer Service (with eFORMzPrinter.jar) keep a log whose settings are in PrintServices.xml. Please contact Minisoft Support for questions with these logs.<\/p>\n","protected":false},"excerpt":{"rendered":"

        eFORMz has flexible logging options for the eFORMz Composer and the Director. How you configure your logs depends on your business requirements. The primary use of logs is to help troubleshoot problems or unusual conditions. Separate logs are kept for the eFORMz Composer and the Director, and each Director configuration file has an associated log […]<\/p>\n","protected":false},"author":12,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[85,105,1],"tags":[],"_links":{"self":[{"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/posts\/3608"}],"collection":[{"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/comments?post=3608"}],"version-history":[{"count":10,"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/posts\/3608\/revisions"}],"predecessor-version":[{"id":10451,"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/posts\/3608\/revisions\/10451"}],"wp:attachment":[{"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/media?parent=3608"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/categories?post=3608"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/minisoft.com\/support\/wp-json\/wp\/v2\/tags?post=3608"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}