BusinessPhone Communication Platform 6.0
Dialogs

## Program Logs

The following program logs are created from the BMS server.

There are two types of program logs in the BMS:

- Alarm / Error:

- These logs are used to store the alarm and error messages from the programs.

- Trace / Debug:

- These logs are used to store status information, action logs, traces information and debugging messages.

### Log file naming convention

The name of the each log is created according to the following rules:

1. The first part indicates the type of log: ALARM for alarms and errors; TRACE for status information, actions, traces and debug messages.
2. The second part is the starting date of the logging. The date uses the format “DAY_MONTH_YEAR”.
3. The third part indicates the originator of the log: OAM for the BMS server and WEB for the web server.
4. The last part is the file extension “.LOG”.

Following are two examples of log names:

ALARM13_05_00_OAM.LOG

TRACE15_03_00_WEB.LOG

### Live time of the log files

The same log files are use during the complete live time of the programs. Therefore, if the servers are running for more than one day, the start date used in the name of a log file is the one of the first creation of the file.

In addition, if the servers are started and stopped several times on a day, the same log files will also be used.

### Log files entries

Each time the servers are started, log start messages are added to the logs. The log file open message consists of a date and the current time. The date could differ from the date stamp used for creating the log files because the servers could be started more than once a day.

The following entries are created during the live time of the servers. Each log message entry consists of several parts:

1. The first part is a time stamp.
2. The second part is a marker defining the type of entry:

   <I> |  | Information, used for status information, actions and traces |
   <D> |  | Debug information |
   <A> |  | Alarm |
   <E> |  | Error. |

3. The third part contains the information regarding the part of the servers responsible for the message creation:

- [ASB: asbname, module:class.function]
- If a part connected to a BusinessPhone is firing the message, the code “ASB:” with the name of the BusinessPhone is shown.
- The module could be a text or a numeric value describing the internal module range in the server.
- The class is the java class, which builds the message; the function is the method of the class.
- Some of these parts could be missing!

1. The next part exists only if the type of the log message entry is an alarm or an error. In this case, a numeric code – decimal and hexadecimal notation – is shown.
2. The next part describes the severity of the state and is present only if the type of log message entry is an alarm.
3. The last part is a message text with one or more lines beginning with “>>”.

Following are two examples of log message entries:

    15:16:06 <I> [OAMCore:ConfigSrv.init()]
    >> Register MIB classes...OK. Elapsed time:
    2174
    18:16:05 <E> [ASB:jürgen,
    BPMIB:AttListEntry.AttListEntry.read()]
    CODE=0(0x0)
    >> Record (0x7B, 0, 256) could not be read

Revision: B © Ericsson Enterprise 2004