Unwired Platform Logs

Unwired Platform log files provide valuable troubleshooting information. Log file information is aggregated and displayed in the Sybase Control Center administrative console. You can use a text editor to review log files from the command line using a text editor if Sybase Control Center is not available, or to concentrate your review to a particular log.

To begin troubleshooting Unwired Platform issues, see:

Sybase Unwired Platform > Troubleshooting > Troubleshooting Basics > Collecting Information > Log Files for information about how to access and view Unwired Platform log files.
Sybase Control Center for Sybase Unwired Platform online documentation for more information about using the console to view messages and log files.

The following logs are particularly helpful when troubleshooting for the Sybase Mobile Sales solution:

Component	Log file location
Sybase SAP DOE Connector (DOE-C)	Main server log: `<UnwiredPlatform_InstallDir>`\UnwiredPlatform\Servers\UnwiredServer\logs\`<hostname>`-server.log HTTP requests log: `<UnwiredPlatform_InstallDir>`\UnwiredPlatform\Servers\UnwiredServer\logs\`<hostname>`-http.log Messaging Server log: `<UnwiredPlatform_InstallDir>`\UnwiredPlatform\Servers\UnwiredServer\logs\JmsBridge\`<hostname>`_JmsBridge_JmsBridge_`<timestamp>`.txt
Unwired Server	Useful for servlet deployment errors: Sybase\UnwiredPlatform\Servers\UnwiredServer\logs\deploy.log Failures that prevent SUP from initializing: Sybase\UnwiredPlatform\Servers\UnwiredServer\logs\bootstrap*
Sybase Messaging	Contains Sybase Messaging and connection information and errors. You can access the Sybase Messaging (MOCA) log from Sybase Control Center. The log is split when it reaches the Debug Trace Size (KB) indicated in Sybase Control Center, so additional mocalog.txt.bak files may exist in the folder. In the left navigation pane of Sybase Control Center, select Device Users. In the right administration pane, click the Devices tab, and select MBS to view messaging-based synchronization devices. Select a device, then Get Trace. The default location is `<UnwiredPlatform_InstallDir>`\UnwiredPlatform\Data\Messaging\ClientTrace for a cluster or `<UnwiredPlatform_InstallDir>`\UnwiredPlatform\Servers\MessagingServer\Data\ClientTrace for a single node installation.

Component

Log file location

Sybase SAP DOE Connector (DOE-C)

Main server log: <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\UnwiredServer\logs\<hostname>-server.log

HTTP requests log: <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\UnwiredServer\logs\<hostname>-http.log

Messaging Server log: <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\UnwiredServer\logs\JmsBridge\<hostname>_JmsBridge_JmsBridge_<timestamp>.txt

Unwired Server

Useful for servlet deployment errors: Sybase\UnwiredPlatform\Servers\UnwiredServer\logs\deploy.log

Failures that prevent SUP from initializing: Sybase\UnwiredPlatform\Servers\UnwiredServer\logs\bootstrap*

Sybase Messaging

Contains Sybase Messaging and connection information and errors. You can access the Sybase Messaging (MOCA) log from Sybase Control Center. The log is split when it reaches the Debug Trace Size (KB) indicated in Sybase Control Center, so additional mocalog.txt.bak files may exist in the folder.

In the left navigation pane of Sybase Control Center, select Device Users.
In the right administration pane, click the Devices tab, and select MBS to view messaging-based synchronization devices.
Select a device, then Get Trace.
The default location is <UnwiredPlatform_InstallDir>\UnwiredPlatform\Data\Messaging\ClientTrace for a cluster or <UnwiredPlatform_InstallDir>\UnwiredPlatform\Servers\MessagingServer\Data\ClientTrace for a single node installation.