|
Sun Java
System Communications Sync Release Notes |
Sun Java System
Communications Sync 2005Q4 is a software product that runs on a Windows
personal computer and allows users to synchronize Sun Java System
Calendar
Server events and tasks with mobile devices and personal information
managers
(PIMs) such as Microsoft Outlook. The Release Notes are intended
primarily for
Calendar Server and system administrators. End users should refer to
the Sun
Java System Communications Sync 2005Q4 online help for information.
The Release
Notes document
information available at the time of the release, including:
·
Supported PIMs and Mobile Devices
·
What’s New in Sun Java
System
Communications Sync 2005Q4
·
Problems Fixed in This Release
·
Known Problems and Limitations
Read
this document before your end users install and start using Sun Java
System
Communications Sync 2005Q4. For an online version, see the following
documentation Web site:
http://docs.sun.com/db/coll/1313.1
Check this site
periodically to
view the most up-to-date documentation.
Sun Java System
Communications
Sync 2005Q4 supports the following PIMs and mobile devices:
·
Microsoft
Outlook 98/2000/2003
·
Palm
OS
v3.x/v4.x/v5.x
·
Pocket
PC 3.x/2002/2003 Mobile Devices with Active Sync Manager
To install and
run Sun Java System Communications Sync 2005Q4, you
need the following:
·
Sun
Java System Calendar Server account (not required for installation but
needed
to sync events and tasks with Calendar Server)
·
Windows
personal computer with:
o
16
MB
RAM (32 MB is recommended)
o
Microsoft
Windows
XP SP2 , Windows 2000 SP4, Windows
98 and Windows NT 4.0
operating systems
·
PIM
or
mobile device you plan to use. Requirements are:
o
PIMs
and mobile devices require the linking device (for example, a cable or
infrared) and the associated software.
o
Palm
devices require HotSync Manager. Versions 4.1.0 and 6.0.1 were tested.
o
Pocket
PC devices require Microsoft Active Sync. Version 3.1 and Version 3.5
were
tested.
o
Microsoft
Outlook must be installed in either Corporate or Group mode and not in
“no-email” mode. You must have selected Outlook as the default email
client;
you can't have the “simple MAPI” option selected.
·
Web
browser- Internet
Explorer 4.0 or higher or Netscape 4.5 or higher
You can obtain
the Sun Java System Communications Sync 2005Q4 installation program
from the
Sun Java System download site or the Sun Java Enterprise System
Accessory CD.
Or contact your Sun technical support representative or account manager
to
obtain the program.
Before you
install or upgrade (reinstall) Sun Java System Communications Sync
2005Q4,
consider these items:
·
If you are
upgrading from an earlier version of Sun ONE
Synchronization to Sun Java System Communications Sync 2005Q4, you must
first
uninstall the earlier version of the product.
·
Before you run the
installation program, you must first install
each PIM or mobile device you plan to use.
·
To run the
installation program on a personal computer, you
must be logged on as a member of the Administrators local group.
Upgrading (or
reinstalling) Sun Java System Communications Sync allows you to upgrade
your
current version of the Sun Java System Communications Sync software or
to add
support for an additional PIM or mobile device.
To install or
upgrade (reinstall) Sun Java System Communications Sync 2005Q4, follow
these
steps:
1.
Read
the Readme file, if you have not already done so.
2.
If
necessary, unzip the installation program file.
4.
If
you are upgrading (or reinstalling), perform one last synchronization
to
ensure that all data is the same.
5.
Backup
your master data, either on your PIM or mobile device or on Calendar
Server.
6.
Start
the installation program (SunJavaCommSync.exe).
7.
Follow
the instructions in the series of screens.
8.
When
the installation is complete, click Finish.
Note: Depending
on the platform you are installing on, you might need to restart your
operating
system. The installation program will prompt you if a restart is
needed.
The
following are the list of new features included in
Sun Java Synchronization 2005Q4
·
The
User Interface has been changed to include all the features within
single panel.
·
Per application
(calendar and task)
selectability for forcing full sync.
·
Support
for new Palm Database structure (TungstenT5, Treo 650).
·
Added
Alarm Type field in order to sync Audio alarm setting for Outlook
·
New profile can be
created between
the supported devices and the Calendar Server.
·
User
can rename the profile, remove the profile, and select any profile as
current profile.
·
One-way
synchronization allows to specify the
master record which will be taken while conflicts are encountered.
·
Filter
settings has been enhanced to set text and date filter criteria by
grouping the filter conditions with AND and OR operators.
·
Added
browse option to specify the target location for the log files.
·
Settings
can be made to store the log files for selected number of days.
·
Log
files can be viewed easily. No need to navigate to the folder to see
the log files.
·
Using
Schedule sync feature the synchronizing activity can be automated to
occur within a scheduled interval.
·
Problems after Running the csvdmig Migration Utility
·
Sun Java System Communications Sync 2005Q4 Known
Problems
If your site
runs the csvdmig
migration utility to use hosted
(virtual) domains, Sun Java System Communications Sync users will see
the
following message when they try to synchronize their data to Calendar
Server:
Cannot access
calendar data source. Check general troubleshooting
under online help.
The csvdmig utility adds a
domain name to each
calendar ID (calid)
for calendar
names in the Calendar Server database and LDAP directory server. For
example,
suppose you run csvdmig
to migrate a user named jsmith,
with the domain as sesta.com. A
calendar name that was jsmith:public-calendar
is changed to jsmith@sesta.com:public-calendar.
Consequently,
Sun Java System Communications Sync cannot find jsmith’s calendar with
the
revised name.
To synchronize
with their Sun Java System Calendars, users must perform these steps
(which are
also included in the Sun Java System Communications Sync online help):
1.
On
the Sun Java System Communications Sync screen, click Settings.
2.
On
the Settings screen, click the Data Sources tab.
3.
Select
Sun Java System Calendar.
5.
Click
OK on the Sun Java System Translator dialog.
6.
On
Calendar Options, reselect your existing Sun Java System Calendar name
in the drop-down list.
7.
Click
OK. Important: Do not click Cancel.
8.
On
the Sun Java System Translator dialog, click Yes.
9.
Repeat
steps 4-8 for Sun Java System Tasks.
10.
Important: On the
General tab on the Settings screen, check “Force
full synchronization”.
Users should
then be able to synchronize with their Sun Java System Calendars. If
this
doesn't resolve the problem, contact your Sun technical support
representative.
|
Table 3 Sun Java System
Communications Sync 2005Q4 Known Problems |
|
|
For Palm Desktop, Sun
Java System Sync returns “A specified module is
not found” error. When attempting to sync
Palm Desktop data to Calendar Server 6.0, Sun Java System Sync returns
“A specified module could not be found.” The rsSync.log file also
indicates that the rstPalmDT.dll could not be found.
Workaround:
Change the data folder in the Palm Desktop to the original default
installation folder. |
|
|
The list of events and
their details are not displayed before
confirming the delete of events. |
|
|
Only one user at a time can use Sun Java System Synchronization. |
|
|
Tasks are not synced properly between Calendar Server and a Palm device. |
|
|
4758779 |
Sync shows conflict even
if user modifies only one data source PIM or device. Sync an event from
Calendar Server to a PIM or device, and then delete or add characters
in the title, location, or notes, on the PIM or device. A subsequent
resync back to Calendar Server results in a
conflict. This problem was reported on Outlook, but it also occurs on
other PIMs and devices. |
|
Only exceptions made to the recurring events on Windows CE are synced to the Calendar Server. |
|
|
While syncing, task
fields with value of “None” are passed a value
after syncing. For example, create a
task on Outlook with the Start Date set to “None” and the Due Date set
to a specific value. Sync to Calendar Server and edit the title for the
task. If you sync again, on Outlook the Start
Date is set to the Due Date value. |
|
|
Changing mapping reports
error and forces a full sync. For example, suppose
location on Calendar Server is mapped to notes on Palm, with the
formula Note= “Event Located in:” + location.
After syncing an event originating in Calendar Server with location
information as Bangalore, the notes in Palm would read as ‘Event
Located in: Bangalore’. Do not try to edit the placeholder, which in
this case is ‘Event Located in:’. This can
lead to unexpected behavior. If you want to change the location by
editing in Palm, change only “ |
|
|
Multi-day event is
removed on Windows CE when modified on Calendar Server and synced. |
|
|
Once the final
installation screen is displayed you cannot navigate
back to the earlier screens to edit the selections made. However, the install instructions state that it is possible to navigate to the previous screens and edit the selection. |
|
|
Tasks are not synced
properly to Windows CE devices. |
|
|
Record Filter shows only
records created on the data source other than Calendar Server. |
|
|
When filters are set Sun
Java System Communications Sync deletes only those events that fall
within the filter range. All events are not deleted. |
|
|
All day recurring events
are not synced properly between Outlook and Calendar Server. |
|
|
Data duplication occurs
with Sun Java System Synchronization. |
|
|
Sync reports an unknown
error and forces a full sync because of a translator exception. |
|
|
Deleting
notes for an event on Palm or Windows CE devices is not reflected in
Calendar Server. Create a new event on a
Palm or Windows CE device with some text in the notes field and then
sync to Calendar Server. If you delete the notes text on the Palm or Windows CE device and then resync to Calendar Server,
the Calendar Server event still has the previous notes. |
|
|
Sun Java System
Communications Sync does not create logs according to the levels
defined. |
|
|
Sun Java System
Communications Sync prompts for deletion of a
record while actually modifying a record. Sun Java System
Communications Sync 2005Q4 prompts for the deletion of a record when
changing a record from normal to recurring and syncing the changes. For example, create a
non-recurring event on Calendar Server and sync
it to a PIM or device. Then, change the event on Calendar Server to a
recurring event and resync. Sync prompts for the deletion of the event.
Click Yes. Sync will delete and then recreate the event. |
|
|
Performance when syncing
large data sets is slow. Use date filters to sync
large data sets, because filters sync only a subset from the master
database to the slave database. However, keep in mind which is your
master database. Sun Java System Communications
Sync 2005Q4 considers PIMs such as Outlook and Palm Desktop to be
master databases and handheld devices to be slave databases when
syncing with Calendar Server. Calendar Server acts as a master or slave
database depending on whether you are syncing it with a handheld device
or a PIM, respectively. |
|
|
Full sync that merges
data from different sources can cause problems. |
|
|
Sun Java System
Communications Sync 2005Q4 does not sync categories properly. |
|
|
Sun Java System
Communications Sync allows the user to sync between any two data
sources. |
|
|
Remove mail related
information from Sun Java System Communications
Sync 2005Q4. Sun Java System
Communications Sync 2005Q4 does not support synchronization of email.
However, not all email related information has been removed from the
product. For example, Outlook still expects the Outlook Mail to be set
as the default mail client. Also, when you choose a new profile such as
Windows CE or Outlook, you get options to sync mail. |
|
|
Due dates are synced
erroneously when no due time is specified for tasks. |
|
|
Tasks with no due date
are no synced properly between Palm Desktop and Calendar Server. |
|
|
Events on Calendar Server
that continue to the next day not synced properly to Palm devices. |
|
|
Reminders are not synced properly to a Palm device from Calendar Server. |
|
|
Untitled tasks on Palm
can be synced with Calendar Server but vice versa is not allowed. |
|
|
Recurring events and
tasks are synced as individual events and tasks on the destination. |
|
|
Administrator must grant
access permissions to the end user. Sun Java System Sync
software must be installed by an Administrator. The Administrator needs
to assign rights to the end users of the Sun Java System Sync
directories. When a user without proper permissions tries to use Sun
Java System Sync, the following error messages
are displayed: |
|
|
Sun Java System Sync does not allow multiple calendars to be synchronized simultaneously. |
|
|
Alarm not synchronized
properly. |
|
|
Notes for events are not
updated correctly when events are synced from the Calendar Server to
Palm Desktop. Syncing Calendar events to Palm Desktop causes the text to be displayed on a single line on Palm Desktop. For example, <Line 1>[]<Line 2> |
|
|
Single tasks or recurring
tasks with due dates on Palm are synced a day earlier. |
|
|
Recurring Events created
on Palm and synchronized to Calendar Server are deleted on Calendar
Server but not on Palm. Now, delete the complete
series of recurring events on Palm. All events except for the one just
modified is deleted. Once again synchronize the data. All the events on
Calendar Server are deleted including the one appearing
on Palm. |
|
|
i18n: Multiple data does not work properly with Sun Java System
Communications Sync translator in Outlook. |
|
|
New line in notes created
on the Calendar Sever is not synced to Windows CE device. |
|
|
Using Sun Java System
Sync with other XTND Connect Sync software may not work properly. |
|
The following
documentation was revised for Sun Java System Communications Sync
2005Q4:
·
Release
Notes (this document).
·
Online
Help-The online help (XTNDConnect-PC.chm) is available with the Sun
Java System
Communications Sync software. You access the help by clicking a Help
button on
the various windows or by directly opening the XTNDConnect-PC.chm
file.
http://docs.sun.com/db/coll/S1_Sync_11
Sun Java System
Communications Sync 2005Q4 is available in English only and has not
been
localized in other languages. Release 2005Q4 has undergone limited
internationalization (i18n) testing with favorable results for
single-byte
character sets including French, Spanish, and German. The results of
i18n
testing with Simplified Chinese, however, were unfavorable (see Bug IDs
4713884, 4713889, and 4713914). Localized versions for Simplified
Chinese and
other languages that use multibyte character sets may be available in a
future
release depending on the business requirements.
If you have
problems, contact
customer support using one of the following methods:
·
Use
the Sun Java System Support site:
http://sunsolve.sun.com/pub-cgi/show.pl?target=home
From this
location, use the CaseTracker and
CaseView tools to log problems.
·
Call
the telephone dispatch number associated with your maintenance
contract.
To help us
assist you in
resolving your problem, please have the following information
available:
·
Sun
Java System Communications Sync version including the Product ID and
Build numbers from the Additional Information box in the About Sun Java
System
Communications Sync screen.
For example: Version
2005Q4, Product Id 209-101, Build 2005090517.
·
PIM
or mobile device you are using. For example: Palm III or Microsoft
Outlook 2000.
·
Browser
and version. For example: Internet
Explorer 6.0.
·
Specific
error and problem description, including the data type you are
trying to synchronize. For example: Calendar data.
·
Zipped
debug log file, if applicable.
Useful Sun Java
System
information can be found at the following locations:
·
Documentation
for Sun Java System Communications Sync 2005Q4
http://docs.sun.com/db/coll/S1_Sync_11
·
Sun
Java System Documentation
http://docs.sun.com/app/docs/prod/java.sys#hic
·
Sun
Java System Professional Services
http://www.sun.com/servicessolutions/
http://www.sun.com/software
http://sunsolve.sun.com/pub-cgi/show.pl?target=home
http://sunsolve.sun.com/pub-cgi/show.pl?target=home
http://developers.sun.com/
http://www.sun.com/training/
·
Sun
Software Data Sheets
http://wwws.sun.com/software
Copyright
©
2005 Sun Microsystems, Inc. All rights reserved.