Sun Java System Calendar Server: Calling All Best Practices
By Joesciallo-Oracle on Sep 26, 2007
Someone was asking recently about Calendar Server best practices information on one of the support aliases. So I went searching the Calendar Server documentation, and discovered this best practice tip:
Duplicate parameters are allowed in the ics.conf file. The system takes the value of the last instance of the parameter in the file.
Best Practices: To avoid confusion, add your customizations to the end of the file in a section you create for that purpose. For example, you can create a comment line with the following text: ! My ics.conf Changes. Then add any new parameters or any parameters that you are modifying, and their values. Add comments to each parameter describing why the change was made and add the current date. This will give you a history of the changes made to the system for later reference.
If you make extensive customizations, to improve processing efficiency, you might consider commenting out the original parameter that you are replacing. Also, periodically review the file, commenting out obsolete duplicate parameters.
Other BP tips that folks suggested include:
Take nightly backups then run csdb check on the backup DP, to capture any DB corruption.
Implement the Calendar Server automatic backup facility.
These were just a few tips that came up. Have a Calendar Server best practice? Feel free to add to this entry by posting in the Comments.