Help Center

Local Navigation

BlackBerry MDS Connection Service log files

Changing how the BlackBerry MDS Connection Service creates a log file

Change the logging level for BlackBerry MDS Connection Service log files

You can change the logging level for the BlackBerry® MDS Connection Service log file, which includes the event log, UDP log files, and TCP log files.

  1. In the BlackBerry Administration Service, on the Servers and components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > MDS Connection Service.
  2. Click an instance of the BlackBerry MDS Connection Service.
  3. On the Logging tab, click Edit instance.
  4. In the File logging destination, UDP logging destination, TCP logging destination, or EventLog logging destination sections, select one of the following logging levels from the Log level drop-down list:
    • To write events to the log files, click Event.
    • To write error messages to the log files, click Error.
    • To write warning messages to the log files, click Warning.
    • To write daily activities to the log files, click Informational.
    • To write additional information to the log files that can help you troubleshoot issues with the BlackBerry MDS Connection Service, click Debug.
  5. Click Save all.

Change the interval that the BlackBerry MDS Connection Service writes information to a log file

The interval that the BlackBerry® MDS Connection Service writes information to a log file applies to all BlackBerry MDS Connection Service log files, including the event log, UDP log files, and TCP log files.

  1. In the BlackBerry Administration Service, on the Servers and components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > MDS Connection Service.
  2. Click an instance of the BlackBerry MDS Connection Service.
  3. On the Logging tab, click Edit instance.
  4. In the File logging destination section, in the Log timer interval field, type the interval in milliseconds. The default value is 30000.
  5. Click Save all.

Change the host and port number that the BlackBerry MDS Connection Service connects to when it sends UDP log file messages

The SNMP agent for the BlackBerry® Enterprise Server receives UDP log file messages from the same host and port number that the BlackBerry MDS Connection Service connects to when it sends UDP log messages.
  1. In the BlackBerry Administration Service, on the Servers and components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > MDS Connection Service.
  2. Click an instance of the BlackBerry MDS Connection Service.
  3. On the Logging tab, click Edit instance.
  4. In the UDP logging destination section, in the Location field, type the host name and port number using the format <host_name>:<port_number>.
  5. Click Save all.

Change the host and port number that the BlackBerry MDS Connection Service connects to when it sends TCP log file messages

  1. In the BlackBerry® Administration Service, on the Servers and components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > MDS Connection Service.
  2. Click an instance of the BlackBerry MDS Connection Service.
  3. On the Logging tab, click Edit instance.
  4. In the TCP logging destination section, in the Location field, type the host name and port number using the format <host_name>:<port_number>.
  5. Click Save all.

Change the activities that the BlackBerry MDS Connection Service writes to a log file

The settings for the activities that the BlackBerry® MDS Connection Service writes to a log file apply to all log files, including the event log, UDP log files, and TCP log files.

  1. In the BlackBerry Administration Service, on the Servers and components menu, expand BlackBerry Solution topology > BlackBerry Domain > Component view > MDS Connection Service.
  2. Click an instance of the BlackBerry MDS Connection Service.
  3. On the Logging tab, click Edit instance.
  4. In the Logging section, perform any of the following tasks:
    Task Steps

    Monitor activity at the SRP network layer.

    In the SRP logging turned on drop-down list, click True.

    Monitor activity at the IPPP network layer.

    In the IPPP logging turned on drop-down list, click True.

    Monitor activity at the UDP network layer.

    In the UDP logging turned on drop-down list, click True.

    Monitor activity at the GME network layer.

    In the GME logging turned on drop-down list, click True.

    Monitor HTTP headers for request and response messages that the web server sends or receives when users retrieve content from the Internet and intranet on BlackBerry devices.

    In the HTTP logging turned on drop-down list, click True.

    Monitor HTTP headers and the body of response messages that the web server sends when users retrieve content from the Internet and intranet on BlackBerry devices.

    In the Verbose HTTP logging turned on drop-down list, click True.

    Monitor activity that occurs between the BlackBerry MDS Connection Service and the target server when the BlackBerry MDS Connection Service uses a TLS connection.

    In the TLS logging turned on drop-down list, click True.

    Monitor the certificate revocation status that the BlackBerry device retrieves from the OCSP server.

    In the OCSP logging turned on drop-down list, click True.

    Monitor BlackBerry device requests to access a user profile or certificate from the LDAP directory.

    In the LDAP logging turned on drop-down list, click True.

    Monitor CRLs that the BlackBerry device retrieves from the CRL server.

    In the CRL logging turned on drop-down list, click True.

    Monitor PGP® key status and revocation information that the BlackBerry device retrieves from the PGP server.

    In the PGP logging turned on drop-down list, click True.

  5. Click Save all.

Using BlackBerry MDS Connection Service log files to view information for proxied connections to BlackBerry devices

The BlackBerry® Enterprise Server writes data for each BlackBerry device connection that the BlackBerry MDS Connection Service proxies in the BlackBerry MDS Connection Service log files.

You can find the BlackBerry MDS Connection Service log files on the computer that hosts the BlackBerry Enterprise Server. You can identify BlackBerry MDS Connection Service log files by the component identifier MDAT in the log file name.

Log file example: BlackBerry device user initiates the proxied connection

<LAYER = IPPP, DEVICEPIN = u29, DOMAINNAME = test.rim.net, CONNECTION_TYPE = DEVICE_CONN, CONNECTIONID = 852164874, DURATION(ms) = 3500, MFH_KBytes = 0.908, MTH_KBytes = 38.218, MFH_PACKET_COUNT = 1, MTH_PACKET_COUNT = 2>

Log file example: BlackBerry Enterprise Server initiates the proxied connection (push)

<LAYER = IPPP, DEVICEPIN = <devicepin>, DOMAINNAME = kmtestd, CONNECTION_TYPE = PUSH_CONN, CONNECTIONID = -432667474, DURATION(ms) = 600090, MFH_KBytes = 0, MTH_KBytes = 10.477, MFH_PACKET_COUNT = 0, MTH_PACKET_COUNT = 4>

Information in BlackBerry MDS Connection Service log files for proxied connections to BlackBerry devices

Attribute

Description

LAYER

protocol layer that the BlackBerry® MDS Connection Service uses to proxy BlackBerry device connections

DEVICEPIN

PIN or BlackBerry® Enterprise Server user ID of the BlackBerry device that connects using a proxy server

DOMAINNAME

domain that requests the BlackBerry device connection

CONNECTION_TYPE

initiator of the proxied connection, which can be either the BlackBerry device user (DEVICE_CONN) or BlackBerry Enterprise Server (PUSH_CONN )

CONNECTIONID

unique identifier for an IPPP connection, where - (minus sign) indicates a push connection

DURATION(ms)

duration of the proxied BlackBerry device connection, in milliseconds

MFH_KBytes

size of messages that the BlackBerry device sends, in KB

MTH_KBytes

size of messages that the BlackBerry device receives, in KB

MFH_PACKET_COUNT

number of packets that the BlackBerry device sends

MTH_PACKET_COUNT

number of packets that the BlackBerry device receives


Was this information helpful? Send us your comments.