Application Gateway Administration GuideChapter 11 Logging and Monitoring Application Gateway OperationsConfiguring and Working with System Logs133f. The archiving frequency, which should be based on the expected levelof AG activity and how you wish to track activity.If the FTP server is unavailable when the Application Gatewayattempts to contact it, the Application Gateway tries every hour fromthat point on to send the log. Once the server is contacted and the logis sent, the Application Gateway returns to the usual archive schedule.6 Click Submit.To view the system log:• In the Administration Tool, go to the Logging > System Log page.The Application Gateway displays the most recent activity when the entirelog is too large to display. For more information, see “Interpreting theSystem Log,” page 133.Interpreting the System LogSystem log entries have the form (date time) thread: message, where“thread” is used to identify the component source of the message. Forexample:(Jan 30 13:07:04 2006) license: Checking available bcs licenses 110 of 1000(Jan 26 15:00:07 2006) directory: no license found, will not initialize module(Jan 26 15:00:09 2006) server: No more licenses available for 00:04:0D:4C:29:2B(Jan 30 13:07:05 2006) ldap: ldap: unbind successfulMuch of the information in the log is informational and can be ignored.Errors at the beginning of the log do not necessarily indicate problemswith the Application Gateway. However, a log of only a few lines uponstartup of the Application Gateway indicates a possible problem with thelogging service. If the initial log does not include at least 50 or so entries,restart the server. If that does not correct the problem, contact yoursupport representative.Some log entries help with troubleshooting issues, as described in thefollowing topics:Broadcast Server, page 134Call Server synchronization for IP/DN mapping, page 134CSV synchronization for IP/DN mapping, page 136
