Planning an Upgrade to Siebel 7 > Upgrade Scenario > Scenario for Upgrading the Test or Production Environment >

Postupgrade Tasks for the Test or Production Environment Scenario


Table 12 lists the tasks to complete after upgrading the test or production environment. See Upgrade Guide for Microsoft Windows for detailed information about each task.

Table 12.  Postupgrade Tasks for the Test or Production Environment Scenario
Step
Date
Owner
Task
Duration
  1.  
Day 12
Siebel Upgrade Consultant
  • Copy all files from the 6.3 file system to the \att subdirectory of the version 7.5 Siebel File System.
  • Update the file system attachment records that are based on obsolete tables.
 
  1.  
Day 12
 
Generate reporting relationships so the three visibility hierarchies—position, organization, and access groups—will display the correct information. See Upgrade Guide for Microsoft Windows for instructions.
30 min. to compile;
1 min. to generate reporting relationships
  1.  
Day 12
 
Manually migrate data from custom extensions that are now obsolete.
For a list of tables that require attention, review the xtndobstbl.log file under SIEBEL_ROOT\siebsrvr\log. Identify any joins in these tables, and review Siebel Tools for custom assignment or workflow objects that map to extension columns in obsolete tables.
 
  1.  
Day 12
 
Compile a new Siebel Repository File (SRF) using Siebel 7.5 Tools with all projects selected. The new Siebel repository will be created after a successful upgrade of the custom database schema. Save the compiled SRF to the directory, \client\objects\enu.
 
  1.  
Day 12
 
Connect to the Siebel Database Server using the new SRF file.
 
  1.  
Day 12
 
If you deploy to mobile users with local databases, run the DICTUTL utility to verify that all dock objects and rule definitions are correct.
 
  1.  
Day 12
 
Review the dictutl2.log file located under SIEBEL_ROOT\siebsrvr\bin.
 
  1.  
Day 12
Siebel Upgrade Consultant
Review duplicate login IDs.
  • From the application-level menu, select User Administration > Users view.
  • Query for *+*. This query will produce a list of all names that are appended with +row_id.
 
  1.  
Day 12
 
Upgrade the encryption method from the standard encryptor to the RC2 encryption method.
4 hours
  1.  
Day 12
 
Set up global time zone support. For detailed instructions, see Siebel Tools Reference.
6 hours
  1.  
Day 12
 
Synchronize server components. From the application-level menu, choose View >Site Map >Server Administration > Enterprise Configuration > Batch Component.
 
  1.  
Day 13
 
Create a BASE package.
 
  1.  
Day 13
 
Create a language package.
 
  1.  
Day 13
 
Create the Siebel upgrade wizard kit.
2 hours
  1.  
Day 13
 
Create the Siebel client executable kit.
2 hours
  1.  
Day 13
 
Create the Siebel client executable_enu kit.
2 hours
  1.  
Day 13
 
Add components to upgrade kits.
1 hour
  1.  
Day 13
 
Activate the upgrade kits.
 
  1.  
Day 13
 
Apply versions.
 
  1.  
Day 13
 
Distribute the upgrade kits.
 
  1.  
Day 13
 
Regenerate the database template file. See Upgrade Guide for Microsoft Windows for more information.
 
  1.  
Day 13
 
Extract mobile users.
 
  1.  
Day 13
 
Upgrade connected clients.
 
  1.  
Day 13
 
Upgrade mobile clients.
 


 Planning an Upgrade to Siebel 7 
 Published: 18 June 2003