Configuring other FCSS parameters
You may not need to configure any other FCSS parameters. In many cases the default parameter settings built into FCSS will be all you need. The following is a list of parameters that you can, however, configure in the inetsvcs.cf file to optimize FCSS performance for your circumstances if you wish.
Configuration parameter |
Function |
SYNCML_MAX_PACKET_SIZE
|
Limits the maximum allowed network packet size in bytes. The default is 0 which makes the maximum network packet size unlimited or controlled by the device. 
NoteThis parameter was formerly SYNC_PACKET_SIZE. If you have already configured it with that name it will continue to work with this release. |
SYNCML_ENFORCE_MD5_AUTH
|
0 - Default. Authentication type is determined by the client. 1 - Enforces MD5 authentication Note This parameter was formerly ENFORCE_MD5_AUTH. If you have already configured it with that name it will continue to work with this release. |
ACTIVESYNC_MAX_WINDOW_SIZE |
Sets the maximum number of items that can be sent to the device in one message. Because the device also supplies a maximum window size, the server will use the smaller of the two values. The default is 25. |
ACTIVESYNC_MAX_PING_INTERVAL |
Overrides the device "push" request interval which is usually 8 to 10 minutes. This is the time, in minutes, after which the server will check for and send any updates to the device when ActiveSync "push" is activated. Because the device also supplies a value, the server will use the smaller of the two values. The default is 8.  CautionSetting this to 1 or 2 minutes may cause fast battery drainage on some devices.
|
ACTIVESYNC_SESSION_TIMEOUT_INTERVAL |
Sets the timeout interval, in seconds, for sessions left alive by a device after a sync is done (some devices do not terminate connections correctly after a sync, leaving a live session to wait for more data). The default is 8. |
ACTIVESYNC_HIGH_VERSION = 120 |
Sets the highest supported ActiveSync protocol version to 12.0 rather than the default 12.1. This is done to prevent some devices, particularly iPhone 3.0 beta, from using the 12.1 version of ActiveSync because of problems with it. FCSS will advertise version 12.0 as the highest supported ActiveSync version, forcing devices to use either version 2.5 or version 12.0 of ActiveSync. |
LOG_LEVEL |
Sets the log level at startup, controlling the amount of information displayed on the FCSS console and written to the FCSS log file created and stored daily where FCSS is installed. The log level values are Basic, Verbose, and Debug, Basic providing the least information and Debug the most. The default value is Basic. You can also set log levels on the FCSS console. |
TRACEXX, where xx are index numbers 01, 02...99. |
Sets trace component logging at startup. Trace component logging options allow you to trace specific events and are used only for troubleshooting. The values are TRACE01, TRACE02, TRACE03, etc., as per Trace components menu options: DISPATCHER, TRANSPORT, HTTP, FC_API, FC_API-ENUMERATION, SYNCML_SESSION, SYNCML_DECODE, SYNCML_ENCODE, SYNCML_DECODE_DETAILS, SYNCML_ENCODE_DETAILS, ACTIVESYNC_SESSION, ACTIVESYNC_DECODE, ACTIVESYNC_ENCODE, ACTIVESYNC_DECODE_DETAILS, ACTIVESYNC_ENCODE_DETAILS. You can also set trace component logging on the FCSS console. Note You must set the log level to Debug, as well as selecting trace component logging options, for trace component logging to
work. |
To configure these parameters:
Add any parameters that you want to configure anywhere in the [SyncServices] section of the inetsvcs.cf file.
Example:
[SyncServices]
PROTOCOL_PORT = 7962
SYNCML_MAX_PACKET_SIZE = 5000
SYNCML_ENFORCE_MD5_AUTH = 1
ACTIVESYNC_MAX_WINDOW_SIZE = 20
ACTIVESYNC_MAX_PING_INTERVAL = 5
ACTIVESYNC_SESSION_TIMEOUT_INTERVAL = 5
ACTIVESYNC_HIGH_VERSION = 120
Example configuration for a normal debug startup with basic component tracing:
LOG_LEVEL = DEBUG
TRACE01 = SYNCML_SESSION
TRACE02 = SYNCML_DECODE
TRACE03 = SYNCML_ENCODE
TRACE04 = ACTIVESYNC_SESSION
TRACE05 = ACTIVESYNC_DECODE
TRACE06 = ACTIVESYNC_ENCODE
TRACE07 = FC_API
Your configuration changes will take effect at startup. After you've installed, registered, and configured FCSS, you can start it.
Licensing FirstClass Synchronization Services
You can run FCSS without a license. In this mode it will support the first 50 users who log in. This is useful for small systems with limited users accessing FCSS and for larger sites that want to evaluate FCSS prior to widespread deployment. Once you install a license, all of the users on your FirstClass system can use FCSS.
To install an FCSS license:
1 Choose Admin > System Profile on the administrator's Desktop.
2 Click Apply License File(s) on the Licensing tab.
3 Browse to the location of your FCSS license file and select the text (nnnnnnn.LIC).
The uploaded file appears in "License application results" and "Licensing summary".
Administering FirstClass Synchronization Services
Checking FCSS status with a web browser
Command |
Function |
ping |
Checks to see if FCSS is running. Recommended method. Does not log in to the server and does not return detailed FCSS info. |
info |
Provides detailed FCSS status. Caution Not recommended unless necessary. Logs in to the server and provides detailed information. Is an "expensive" operation that can degrade server performance. |
To use the ping or info command, type the IP address and relevant command in the address window of your web browser and press Enter.
Example: 127.0.0.1/fcss+ping
Checking FCSS status with the Synchronization Services console
1 Choose Start > All Programs > Accessories > Command Prompt on the Windows desktop of the machine where you installed FCSS.
2 Navigate to the FCServer folder on the hard drive where FCSS is installed.
3 Type fcsync
The console opens, detailing the current FCSS version, configuration settings, and status.
Administering FCSS with the Synchronization Services console
You administer FCSS from the Control menu on the FCSS console.
Command |
Function |
Enable Sync |
Enables synchronization (if previously disabled) |
Disable Sync |
Disables synchronization |
Reset System |
Terminates all sessions and connections, and restarts synchronization server |
List Connections |
Lists the currently active connections on the Synchronization Services console |
List Sessions |
Lists the currently active sessions on the Synchronization Services console |
FirstClass Synchronization Services logging
FCSS automatically logs activity as text files in the FCServer folder where FCSS is installed.
The FCSS logs are named FCSYNC_yyyy_mm_dd_hh_nn_ss.txt, where:
• yyyy, mm, dd, is the date (year, month, day) that the logging was started
• hh, nn, ss is the time (hours, minutes, seconds) that logging was shutdown.
If FCSS is still running at midnight each day, the old log is closed and a new log is created.
The type and amount of information displayed on the FCSS console and written to the log depends on the logging level you set.
To set the logging level:
1 Open the FCSS console.
2 Choose Log Level.
3 Select the logging level you desire.
The log levels are: Quiet, Basic, Verbose, and Debug. Quiet provides the least amount of logging information, Debug provides the most. The default is Basic.
Trace component logging options allow you to trace specific events and are used only for troubleshooting.
Note
You must set the log level to Debug, as well as selecting trace component logging options, for trace component logging to work.
| 
FAQ
FirstClass Tutorials