Describes the replication synchronization process flow, and options available for diagnosing problems at each step of the process.
Process flow
This diagram shows a logical view of replication synchronization communications between the enterprise information system (EIS), Sybase Unwired Platform components, and device clients. Relay server is included as an optional component.
Troubleshooting options
This section describes the options available for diagnosing replication synchronization processing flow problems.
- In Sybase Control Center, enable data services (DS) subsystem logging by setting its log level. The output is written in the server log.
- Review subsystem messages for information about getting data and sending transactions.
- For cache activities, you can enable domain logging on the package using Sybase Control Center, and then review data in cache sub-systems (Cache Refresh and DS Interface specifically) for the period domain logging is enabled. See Domain Logs and Domain Log Categories related documentation in System Administration and Sybase Control Center for Sybase Unwired Platform online help for complete details.
- If you like to troubleshoot at the system-level (which will record all domains and packages activities), you can enable MMS logging by setting the log level in Sybase Control Center. The output is written in the server log.
- Select the desired application package, and enable domain logging on that package. Review the captured log messages in Sybase Control Center.
- For quick troubleshooting to locate system errors, you can check the package-level client log and MBO/Operation history in the Sybase Control Center.
- View the MBO/Operation history in Sybase Control Center for errors during back-end interaction with the EIS.
- On
the data-tier node, review the database error logs:
- errorlog.txt – database system errors
- clusterdb_errorlog.txt – cluster DB server log
- monitordb_errorlog.txt – monitor and domainlog DB server log
- Enable relay server tracing by setting verbosity to 1 or higher. You can do that by editing the rs.config file of your Relay Server and running the rshost utility. Check theSystem Administration topic on Relay Server Setup.
- Review the relay server log files. The logging for rshost.exe is directed to the myrshost.log file in the C:\temp directory.
- Check the IIS log files (windows\logfiles\W3SVC1 and HTTPERR). The IIS server log path is configurable from inetmgr from . The recommended location is C:\Inetpub\LogFiles.
On Unwired Server, check the Sybase Unwired Platform outbound enabler log for replication synchronization entries: SUP_HOME\Servers\UnwiredServer\Logs\NodeName.RSOEnum.log (for example, smpqa01SMPServer1a.RSOE1.log).
- Use the platform-specific client logging API (com.sybase.persistence.LogRecord in Java, and Sybase.Persistence.ILogRecord in C#) to capture log messages and upload them (Client Log) to Unwired Server. You can view these messages in the Sybase Control Center user interface