Logs management

Open iServer WebManager, and view log information on the Log tab when SuperMap iServer server is running. The Log system of SuperMap iServer includes system log, operation log, service access log and network data check log. The service access log is stored in %SuperMap iServer_HOME%/logs, supporting to download service access log to the local form the server. Please refer to Service access logs for more information.

• System logs
• Operation logs
• Service access logs
• Logs configuration
  • System logs configuration
  • Operation logs configuration
  • Service access logs configuration
• Network data checking logs

System logs

Log information is divided into 6 levels: Off, Error, Warn, Info, Debug, and All. Please refer to Table 1 Level Description of System Logs.

Table 1 Level Description of System Logs

The system log of current server will be listed on the Logs tab, including log level, Abstract, Time. You can filter the logs to display by level and number of displayed items, as below shown:

Operation logs

The operation log is the operation records of the service manager, and the records that service visitors edit the detailed GIS services, such as add, modify, delete and so on.

The operation logs only have one level: Info. Please refer to Table 2 Level Description of Operation Logs.

Table 2 Level Description of Operation Logs

The operation log of current server will be listed on the Logs tab, including log level, Abstract, Time. You can filter the logs to display by number of displayed items, as below shown:

Service access logs

Service access logs is that service administrator controls all services published by SuperMap iServer, and get the HTTP request data stream HAR file.

HAR (HTTP Archive), is a common file format to store HTTP request response information based on JSON. The HAR file can be used by other HTTP analysis tools (Fiddler, Firebug, httpwatch, etc.), which is used to analyze all the exception information of service interaction published by Client and SuperMap iServer. Noe it supports HAR1.2. The HAR file should be UTF-8.

A HAR file is a JSON object. You can view it by JsonView tool. The data structure of HAR is as follows:

{

  "log" : {

    "version" : "1.2",

    "creator" : {},

                    "browser" : {},

                    "pages" : {},

    "entries" : {},

    "comment" : ""

              }

}

• version [string]: HAR version.
• creator [object]: The program name and version info to create HAR file.
• browser [object, optional]: Browser name and version info.
• pages [array, optional]: Page list. If the application does not support to group according to the page, this field can be leave out.
• entries [array]: All list of http request.
• comment [string, optional]: Comment.

In the Logs/Service Access Logs tab, it will list all service access logs of the current server. There are two rows: File name and File size. It provides the Download logs button to down the logs to local, as shown below:

Click the Download logs button,and you can download all service access logs to the local as .zip, as shown below:

After unzip the service access log, there are .har files (You can configure the name of service access log through Service Access Logs). You can open these .har files by the HTTP tools (such as Fiddler, Firebug, httpwatch, etc.) to analyze the abnormal interactions between the client and the server.

For example, we can take the Fiddler as an example. Open the Fiddler, and select File->Import Sessions. Select HTTPArchive in the pop up dialog box and click Next to find the .har files. The HTTP request data will be listed in the left of Fiddler page. If you select one or more HTTP request data and click the Replay button, the details of abnormal services will reappear (the passed parameter), which makes it easier for users and support professional to further analysis, debugging and processing.

Logs configuration

Log configuration contains the configuration of system logs, operation logs and service access logs:

System logs configuration

In the Logs/Log Configuration tab, you can configure SuperMap iServer system log, please refer to Table 3 Parameters Description for System Logs Configuration. After configuring, click Save.

Table 3 Parameters Description for System Logs Configuration

Operation logs configuration

In the Logs/Log Configuration tab, you can configure SuperMap iServer operation log, please refer to Table 4 Parameters Description for Operation Logs Configuration. After configuring, click Save.

Table 4 Parameters Description for Operation Logs Configuration

Service access logs configuration

In the Logs/Log Configuration tab, you can configure SuperMap iServer service access log, please refer to Table 5 Parameters Description for Service Access Logs Configuration. After configuring, click Save. The default storage is: %SuperMap iServer_HOME%/logs/iServerHTTPArchive.har.

Table 5 Parameters Description for Service Access Logs Configuration

You can configure service access logs through XML configuration file (Refer to iServer configuration file introduction). Add the following configuration information to iserver-system.xml:

<harLog>
    <enabled>false</enabled> 
    <name>iServerHTTPArchive</name> 
    <monitorURLs/>
</harLog>

• <enabled>: sets whether to open service access logs. The default is false.

• <name>: The file name of output service access log. The default name is iServerHTTPArchive. It supports to customize.

• <monitorURLs>: the service URL address of SuperMap iServer to monitor.

Network data checking logs

When starting iServer, the background program will check the network dataset and turn table, and throw a warning for network dataset. If it needs the transportation analysis, it should adjust the network data according the log to ensure the correctness of the network analysis function.

For example, when starting iServer services, the console quotes the following warning:

You can modify the network dataset according to warnings to ensure the correctness of the network analysis function.