Guidelines for Both UTC and Non-UTC Deployments

This topic is part of About Global Time Zone and Universal Time Coordinated (UTC).

This topic describes some guidelines that apply for deploying with UTC, or for deploying without UTC. Additional requirements are noted in other topics to which they apply.

Caution: Once you have already deployed your Siebel applications using UTC and created user date-time data in UTC format, it is not supported to stop using UTC by setting the Universal Time Coordinated system preference to False. Otherwise, incorrect time stamp values might be created and displayed.

If you do not want to deploy with UTC or are not ready to do so, then it is possible to set the Universal Time Coordinated system preference to False in limited circumstances:

For a new installation, you can set Universal Time Coordinated to False after completing installation steps, as long as you have not created any user date-time data in UTC format.
For an upgrade to the current version from a prior Siebel version deployed without UTC, Universal Time Coordinated might be either False or True, depending on the version you upgrade from. You can set this system preference to False, as long as you have not created any user date-time data in UTC format, and have not converted historical date-time data to UTC format.

For more information, see About UTC System Preferences and Setting UTC System Preferences.

Caution: For an upgrade to the current version, if Universal Time Coordinated is True following the upgrade and you do intend to deploy with UTC, then you must run the UTC conversion utility before any new date-time data is created in UTC format. For details, see Converting Historical Data to UTC.

You perform all of the UTC conversion steps within the overall context of upgrade and other roll-out processes described in Siebel Bookshelf documentation.

For deployments using Siebel Replication Manager, first synchronize all of the regional nodes, then re-extract the regional nodes after you upgrade and convert to UTC.

For deployments using Siebel Remote and Siebel Mobile Web Clients, first synchronize all of the local databases, then reinitialize and re-extract the local databases after you upgrade and convert to UTC. Synchronize all of the local databases before upgrading.

If you deploy with UTC for new or upgrade deployments, then you must set the Default Time Zone system preference. See About UTC System Preferences and Setting UTC System Preferences.

When deploying with UTC for new or upgrade deployments that contain custom date-time fields, you must perform the tasks in Enabling Custom Date-time Fields and Columns for UTC.

Deploying Siebel applications using UTC does not require you to set the operating system clock for the database server computer or operating system instance to UTC (a GMT time zone without DST). This optional task is described in Setting the Database Server to UTC.

Siebel eScript provides a set of methods for working with UTC data, along with methods for non-UTC date-time data. Use the appropriate methods for your deployment. All processing of UTC data performed by eScripts is completely independent of the UTC conversion capabilities of the Application Object Manager.

Caution: If you import appointment or activity data into the Siebel application (with UTC enabled) from another system that does not use UTC, then additional requirements apply. For more information, see Converting Historical Data to UTC.

Related Books

Siebel Installation Guide

Siebel Database Upgrade Guide

Siebel Remote and Replication Manager Administration Guide

Using Siebel Tools

Siebel Developer's Reference

Siebel eScript Language Reference