Problems with extended characters on POA with a CAP protocol.

Extended characters do not show properly after a calendar synchronization.

US ASCII characters are displayed correctly.

Problems show only with a CAP protocol.

Synchronization via a SOAP protocol works fine.

Resolution of the problem requires a design change that is not feasible in the GroupWise 6.5 version. It is recommended to upgrade to GroupWise 7.0.1 version.

As an alternate workaround for the GroupWise 6.5, use a trick for changing protocols within Teamware Mobile server 2.x.

Steps to reconfigure default Teamware back-end protocols:

1. Log on to the admin interface: http://your.twm.server.com/admin/

2. Select "Back-end Connectivity -> Create" to create new back-end profile. Name it, for instance, MyGWServer2.

3. Configure all protocols like for the default configuration. It is possible to point new profile to the same POA that was already used with any existing back-end profile.

4. Each item of the new back-end profile has a corresponding XML file. They can be found under:

/opt/teamware/mobile/syn4j/config/sync4j/server/engine/source

5. Those files looks similar like (here using MyGWServer2 profile name):

groupware_calendar_mygwserver2_C6N2Y_sync_source.xml
    groupware_contacts_mygwserver2_Qw087_sync_source.xml
    groupware_events_mygwserver2_hBgFI_sync_source.xml
    groupware_todos_mygwserver2_j8772_sync_source.xml

6. The contacts item is configured by default with the SOAP protocol. Open by a text editor the contacts XML file and search for a line: