Appendix C  
Calendar Server 5.x to 6.0 Upgrade/Migration Process

This appendix describes how to upgrade/migrate Sun™ ONE or iPlanet™ Calendar Server 5.x to Calendar Server  6.0, including:

Upgrade/Migration Process for upgrading to Calendar Server  6.0
XSL Tips for merging changes into the Calendar Server 6.0 XSL files

 

---

Upgrade/Migration Process

To upgrade to Calendar Server  6.0:

On the server where Calendar Server 5.x is installed, change to the /opt/SUNWics5/cal/sbin directory and stop Calendar Server 5.x:

./stop-cal

Backup the following Calendar Server 5.x directories and files:
Calendar database directory–Default location is:
/var/opt/SUNWics5/csdb.
Calendar Server logs directory–Default location is:
/var/opt/SUNWics5/logs.
ics.conf configuration file–Default is:
/opt/SUNWics5/cal/bin/config/ics.conf.
Backup any Calendar Server 5.x files that you have customized, including:
User interface (UI) XSL files in /opt/SUNWics5/cal/bin/data
Mail formatting files–Default location is:
/opt/SUNWics5/cal/bin/config/language/
default.html file–Default location is:
/opt/SUNWics5/cal/bin/html/language/
HTML files–For example, in:
/opt/SUNWics5/cal/bin/html/language/
Time-zone files such as timezones.ics and change_timezone.xml.

The language directory includes the files for the language you are using. For example, en–English, de–German, es–Spanish, fr–French, ja–Japanese, zh-TW–Traditional Chinese, or zh-CN–Simplified Chinese.

Change to the /opt/SUNWics5/cal/ directory and uninstall Calendar Server 5.x. You must be running as superuser (root). For example:

./uninst

Remove all files under the /opt/SUNWics5 directory.
Run the Java Enterprise System installer to install Calendar Server 6.0 in the /opt/SUNWics5 directory. For information, refer to the Sun Java Enterprise System Installation Guide.
Change to the /opt/SUNWics5/cal/sbin directory and run the comm_dssetup.pl utility to configure your Sun ONE Directory Server 5.x to work with Calendar Server 6.0. For information about comm_dssetup, refer to the "Directory Server Setup Script (comm_dssetup.pl)".
Run the Calendar Server 6.0 configuration program (csconfigurator.sh) to create a new ics.conf configuration file. For more information, refer to "Calendar Server Configuration Program (csconfigurator.sh)"
If you want to keep your 5.x configuration, copy the ics.conf file from your backup location or tape to the /etc/opt/SUNWics5/config/ics.conf file.
Set the UNIX user and group IDs (default is icsuser and icsgroup) and permissions for the ics.conf file. For example:

chown icsuser:icsgroup /opt/SUNWics5/cal/config/ics.conf
chmod 600 /opt/SUNWics5/cal/config/ics.conf

Run the cs5migrate utility to migrate your Calendar Server 5.x database to 6.0. For information, refer to the "cs5migrate Utility".
If the cs5migrate migration is successful, copy the migrated 6.0 database to the /var/opt/SUNWics5/csdb directory. Make sure that the owner of all files in the /csdb directory is icsuser and icsgroup (or the user ID and group ID you have specified in the ics.conf file).
The Calendar Server 6.0 XSL. XML, HTML, and mail formatting files have significant changes from the 5.x release. If you saved the 5.x files in Step 3, you must manually merge your customization changes from the 5.x files to the 6.0 files. For tips for merging changes into XSL files, see "XSL Tips".
Change to the /opt/SUNWics5/cal/sbin directory and start Calendar Server 6.0:

./start-cal

Login to Calendar Server 6.0 using Calendar Express and make sure that you are able to view the Calendar Server components (events and todos).

 

---

XSL Tips

If you are merging changes into the Calendar Server 6.0 XSL files, follow these tips and guidelines to avoid common mistakes:

Do not use the wrong syntax when accessing an attribute. For example:

./element@attribute

This should be:

./element/@attribute

The slash (/) before the ampersand (@) is very important.

Do not put a slash (/) at the end of a node. For example:

/node1/node2/

This should be:

node1/node2

Do not use non-matching open and close braces. For example, to have different background colors depending on a value, you might write multiple <TD bgcolor={$bgcolor_variable}> within different <xsl:when> statements, all finally ending with a single </TD>.

If the parser complains about non-matching braces, you might write <TD> as &lt;TD&gt;.

Instead, however, use either of these methods:

Define a new variable and set its value depending on the different states and then use this new variable in the <TD> line.
Or, define bgcolor separately using <xsl:attribute> for that <TD>.

In either case you end up with just one <TD> line. In general, do not use “linearized” tags, such as &lt; TR>.

Do not close tags before they should be closed. For example:

<INPUT type="checkbox" name="ceGroupInviteAll"/>     <xsl:choose>       <xsl:when test="/calendar/usrctx/userprefs@ceGroupInviteAll='0'">         </xsl:when>           <xsl:otherwise>           <xsl:attribute name="checked"/>       </xsl:otherwise>     </xsl:choose>

Notice the slash (/) at the end of the first line. It closes the INPUT tag; thus the attribute being checked later is ignored by most parsers. The correct way to do this is remove the last slash (/) in the first line and put </INPUT> when finished. For example:

<INPUT type="checkbox" name="ceGroupInviteAll">     <xsl:choose>       <xsl:when test="/calendar/usrctx/userprefs@ceGroupInviteAll='0'">         </xsl:when>           <xsl:otherwise>           <xsl:attribute name="checked"/>       </xsl:otherwise>     </xsl:choose> </INPUT>

Do not use undeclared variables. Make sure variables are declared before they are used. Some parsers ignore undeclared variables, but other parsers flag them as errors.
Do not use spaces in variable names. For example:

<xsl:variable name="test ">

Do not use multiple variables with same name. Do not redeclare the same variable at different levels.
Do not use position(.). This should be position().
Do not use "//node". For example:

<xsl:value-of select="//panel[@name='weekgrid']/weekcal[1]/weekday[1]/command[2]"/>

Do not use the double slash (//).

Do not use entities such as &nbsp; and &amp;. They should be declared as entities in the DOCTYPE line. For example:

<!DOCTYPE xsl:stylesheet [<!ENTITY nbsp "&#160;">]>

Do not use hex values. Values such as &#149; must be declared as an entity in the DOCTYPE line. For example:

<!DOCTYPE xsl:stylesheet [<!ENTITY nbsp "&#160;"> <!ENTITY bullet "&#149;">]>

To use #149 within the xsl, write it as:

<xsl:text>&bullet;</xsl:text>

Do not use a wrong stylesheet tag. Use the following for any new xsl file you write:

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">

Do not use comments within <xsl text>. For example:

<xsl:text><!-- This is a comment --></xsl:text>.

Do not write comments inside the <xsl:text> node.

Do not use very complex patterns in template rules. Instead of very complicated and long rules, use “and” and “or” and try to use <xsl:choose> within the rules to make them simpler.
Do not use counting to check for existence. To check if a node exists, instead of checking if count(node) is greater than zero, just check if node exists.
Do not use too many XSLT functions. Try to reduce use of XSLT functions such as string-length, especially in heavily used templates.
Do not use for-each. Try to use apply-templates where possible instead of for-each. This leads to a better and more natural style for XSLT.
Do not use preceding [-sibling] or following [-sibling] axes.
Do not evaluate the same node multiple times in the same template. When the same node needs to be evaluated multiple times, do it once and save the result in a variable.
Do not use angle brackets in conditional expressions. Use &lt; and &gt; instead of “<” and “>” in conditional expressions.
Do not use value="" for radio buttons and check boxes: For example:

<xsl:attribute name="checked" value=""/>

This should be:

<xsl:attribute name="checked"/>

Do not use non-existent nodes and attributes. For example, if usrctx and intervalMinutes do not exist under the /calendar/usrctx node:

/usrctx/@intervalMinutes

Do not use xsl code between open and close BR. For example:

<BR> <xsl:if>.......</xsl:if></BR>

For an empty line use only <BR/>.

Do not use too many spaces or too much indentation. Although it makes the xsl more readable, spaces can make the xsl behave differently.
Do not use too many variables in the i18n.xsl file. Also, do not declare variables that are not used in the application.

Previous      Contents      Index      Next

---

Copyright 2003 Sun Microsystems, Inc. All rights reserved.