 |
Synchronizing with mobiles and other desktop applications
About FirstClass Synchronization Services
FirstClass Synchronization Services (FCSS) synchronizes user data such as calendar events, contacts, and tasks between a server and a wide variety of mobile devices and desktop applications.
Users' devices communicate with FCSS by sending commands through a standard HTTP data connection over a wired or wireless data network.
 NoteMost mobile devices have PUSH turned on by default. This consumes a lot of sync threads. We recommend that your users turn on FETCH for every 15-30 minutes instead of PUSH. As well as saving the battery life of their devices, this will avoid the need for you to configure multiple FCSS instances behind a load balancer when you anticipate more than 100 users with PUSH turned on.
Overriding FCSS configuration with a web browser
The FirstClass Web Server Configuration Tool allows you to temporarily reconfigure FCSS using a web browser. Configuration is done on the fly, without having to restart the server. This is useful for setting tracing and debugging options.
The configuration changes you make using this tool only persist until the server is restarted, at which time the original configuration parameters are once more in effect.
To reconfigure FCSS with the FirstClass Web Server Configuration Tool:
1 Log in to the applicable server using the URL for the server followed by \configure.
You can log in using an SHA hash password, if you have one, or a clear text password.
2 Choose Set Configuration Parameters at Select an Option.
3 Type the parameter you want to change at "Parameter".
You can copy the parameter from the display below and paste it into this field.
4 Type the value you want for this parameter at "Value".
You can type a completely new value or copy the value from the display below and modify or add to it.
Note
Some parameters, such as MyIP, can't be changed on the fly.
5 Click Set.
Checking FCSS status with a web browser
You can use the FirstClass Web Server Configuration Tool to check FCSS status on a browser, just as you can use it to configure FCSS. Choose the information you want to see at Select an Option.
In addition, you can use the following commands:
Syntax
|
Sample reply |
http://<fcss server>/fcsync/ping |
|
OpenText FC Sync Services 12.1.035 (Windows) |
http://<fcss server>/fcsync/info |
|
OpenText FC Sync Services 12.1.035 (Windows) Supported Commands: Sync,FolderSync,GetItemEstimate,Search,Settings,Ping,Provision Supported ActiveSync Protocols: 2.5,12.0,12.1,14.0,14.1
WSGI Server Configuration: CherryPy WSGI Server 192.168.15.75 on SSL port 8443 with certificate cert.pem and key key.pem, running 5 threads. OpenSSL 1.0.1h release using SSL protocol TLSv1. CherryPy WSGI Server 192.168.15.75 on HTTP port 8000, running 10 threads |
http://<fcss server>/fcsync/info/?config |
|
OpenText FC Sync Services 12.1.035 (Windows) Supported Commands: Sync,FolderSync,GetItemEstimate,Search,Settings,Ping,Provision Supported ActiveSync Protocols: 2.5,12.0,12.1,14.0,14.1
WSGI Server Configuration: CherryPy WSGI Server 192.168.15.75 on SSL port 8443 with certificate cert.pem and key key.pem, running 5 threads. OpenSSL 1.0.1h release using SSL protocol TLSv1. CherryPy WSGI Server 192.168.15.75 on HTTP port 8000, running 10 threads.
HTTP Server Configuration: FirstClass Server: 192.168.15.75 FirstClass Server port number: 510 Network is secure: HTTPS is not mandatory for security critical operations Mobile Device Capabilities: ipad : image-w=64 image-h=64 supports-subcontainers=1 add-on-slow-sync=1 return-empty-sync-response=1 wp8 : image-w=64 image-h=64 supports-subcontainers=0 add-on-slow-sync=1 return-empty-sync-response=1 iphone : image-w=64 image-h=64 supports-subcontainers=1 add-on-slow-sync=1 return-empty-sync-response=1 samsungsghi337m : image-w=64 image-h=64 supports-subcontainers=1 add-on-slow-sync=1 return-empty-sync-response=1 default : image-w=64 image-h=64 supports-subcontainers=0 add-on-slow-sync=0 return-empty-sync-response=1 android : image-w=64 image-h=64 supports-subcontainers=1 add-on-slow-sync=1
return-empty-sync-response=1 playbook : image-w=64 image-h=64 supports-subcontainers=0 add-on-slow-sync=1 return-empty-sync-response=0 blackberry : image-w=64 image-h=64 supports-subcontainers=0 add-on-slow-sync=1 return-empty-sync-response=0 Watch-dog task interval: 5 seconds Inactive session
timeout: 8 seconds Active session timeout: 250 seconds |
http://<fcss server>/fcsync/?ThreadCount=GET |
|
System Thread Count sessions :0 threads :1 ssl_threads :0 thread_pool_size :10 ssl_thread_pool_size:10 Note To turn on thread counting (the number of active HTTP and HTTPS threads in the system), specify ThreadCounting=1 in the fcsync.cfg file (or whatever you named this file if you renamed it). When thread counting is on, if the thread count for a thread pool reaches the maximum, a warning message appears in the log. There is either insufficient thread pool capacity or a possible denial-of-service attack. |
| |
