Configuring Messaging Server Log Settings

Configure trace configuration properties for modules to specify the amount of detail that is written to the log. Messaging Server log settings are cluster-wide, so changes made on the primary node are effective on all nodes.

How changes are applied in a cluster depends on whether you are configuring a primary or secondary server. Sybase recommends you only configure log settings on the primary server. If you change the setting on a secondary server, the configuration is updated only for that server and is temporary (eventually the primary settings are propagated to all servers in the cluster).
Note: The default settings may only need to change in case of technical support situations where, for diagnostic reasons, a request is made to configure the specific module(s) settings, and provide the request log. In all other cases, the administrator or developer should not need to change the settings.

Additionally, you should always use Sybase Control Center to configure server logs. If you manually edit the configuration file, especially on secondary servers in a cluster, the servers may not restart correctly once shut down.

  1. In the Sybase Control Center left navigation pane, click Servers > primaryServer > Log, and in the right pane click Messaging Server > Settings.
  2. Select Default, or one or more of the messaging service modules. Click Show All to show all modules.
    Module Description
    Default Represents the default configuration. The default values are used if optional fields are left blank in a module trace configuration. Required.
    Device Management Miscellaneous functions related to device registration, event notification, and device administration. Enable tracing for problems in these areas.
    JMSBridge The administrative interface for the JmsBridge configuration.
    MO This module handles the delivery of messages between the client and server, including synchronous function calls from client to server. Enable tracing for MO errors and message delivery issues.
    MOCA The Mobile Objects manager for server-to-device requests.
    SUPBridge SUPBridge is the communication module from the messaging server and the Unwired Server. Enable tracing for messaging communications errors.
    TM This module handles the wire protocol, including encryption, compression, and authentication, between the messaging server and clients. All communication between the client and the messaging server passes through TM. Enable tracing for authentication issues, TM errors, and general connectivity issues.
    WorkflowClient The WorkflowClient module.
  3. Click Properties.
    1. Enter trace configuration properties. If you selected multiple modules, a string of asterisks is used to indicate settings differ for the selected modules. You can select the option to view or change the property value for any module.
      Property Description
      Module Display only. Default, module name, or list of module names selected.
      Description (Optional) Custom description of the server module.
      Level Trace level for the module - DISABLED, ERROR, WARN, INFO, DEBUG, DEFAULT. If the default trace level is specified for the module, the module uses the trace level defined for Default. Required.
      Max trace file size (Optional) Maximum trace file size in MB. If the trace file size grows larger than the specified value, the trace file data is backed up automatically.
      User name (Optional) Only data for the specified user name is traced.
      Application Connection ID (Optional) Only data for the specified Application ID is traced.
    2. Click OK.
      Log files for each module are stored in folders of the same name located in: <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\UnwiredServer\logs.
Parent topic: Messaging Server Runtime Logging