| Bookshelf Home | Contents | Index | PDF | ![]() |
|
Siebel Global Deployment Guide > Deploying with Global Time Zone > About Global Time Zone and Universal Time Coordinated (UTC) > Guidelines for Both UTC and Non-UTC DeploymentsThis 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 may be created and displayed. If you do not want to deploy with UTC or are not ready to do so, it is possible to set the Universal Time Coordinated system preference to FALSE in limited circumstances:
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, 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 UTC conversion steps within the overall context of upgrade and other roll-out processes described in Siebel Bookshelf documentation. See relevant guides such as Going Live with Siebel Business Applications, Siebel Database Upgrade Guide, Siebel Remote and Replication Manager Administration Guide, and Siebel Installation Guide for the operating system you are using. For deployments using Siebel Replication Manager, first synchronize all regional nodes, then re-extract the regional nodes after you upgrade and convert to UTC. For more information about these tasks, see Siebel Remote and Replication Manager Administration Guide. For deployments using Siebel Remote and Siebel Mobile Web Clients, first synchronize all local databases, then reinitialize and re-extract the local databases after you upgrade and convert to UTC. Synchronize all local databases before upgrading. For more information about these tasks, see Siebel Remote and Replication Manager Administration Guide. If you deploy with UTC for new or upgrade deployments, 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 machine 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. For information about the UTC methods in eScript, see Siebel eScript Language Reference. CAUTION: If you import appointment or activity data into the Siebel application (with UTC on) from another system that does not use UTC, additional requirements apply. For more information, see Converting Historical Data to UTC. |
![]() |
![]() |
| Siebel Global Deployment Guide | Copyright © 2008, Oracle. All rights reserved. | |