Planning an Upgrade to Siebel 7 > Upgrade Scenario > Scenario for Upgrading the Development Environment >

Postupgrade Tasks for the Development Environment Scenario


Table 9 lists the tasks to complete after upgrading the development environment. See Upgrade Guide for Microsoft Windows for detailed information about each task.

Table 9.  Postupgrade Tasks for the Development Environment Scenario
Step
Date
Owner
Task
Duration
  1.  
Day 4
Siebel Upgrade Consultant
Manually archive the state.log log file.
 
  1.  
Day 4
 
Identify custom extensions that were on tables that are now obsolete, and move these extensions to alternate tables in 7.5.
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.
4-8 hours
  1.  
Day 4
 
Review the upgcust.log file under SIEBEL_ROOT\siebsrvr\log. to identify and resolve any business component and join conflicts.
4-8 hours
  1.  
Day 4
 
If you are implementing Organization visibility, set visibility modes for access control.
  • Verify whether or not the current application uses multi-organization visibility.
  • In Siebel Tools, query for business components with the Popup Visibility Type property set to Catalog, change value to Organization if necessary.
  • Query for applets with the Auto Query Mode property, set to New Query or 'None' to no value if necessary.
  • Query for views with the Visibility Applet Type property set to Catalog, change value to Organization if necessary.
4 hours
  1.  
Day 4
 
Review the mapclash.log file under SIEBEL_ROOT\siebsrvr\log to identify and resolve duplicate EIM mappings (custom EIM mappings that conflict with Siebel System provided mappings).
8 hours
  1.  
Day 4
Siebel Upgrade Consultant
 
Back up the new custom repository into the custrep.dat file located under SIEBEL_ROOT\siebsrvr\Oracle.
You need this file for the production repository upgrade.
 
  1.  
Day 4
 
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.
27 min.
  1.  
Day 4
 
Connect to the server database using the new SRF file.
 
  1.  
Day 5
 
Regenerate the database template file used by Siebel Remote. See Upgrade Guide for Microsoft Windows for more information.
 
  1.  
Day 5
 
Extract Siebel Tools developers and clients by executing a database extract server task (DBEXTRACT) from the new Siebel Server for a developer. For instructions, see Siebel Tools Reference.
Confirm that a developer can initialize a local database.
2 hours
  1.  
Day 5
 
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 5
 
Review the dictutl2.log file located under SIEBEL_ROOT\siebsrvr\bin.
 
  1.  
Day 5
 
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 5
 
Upgrade the encryption method from the standard encryptor to the RC2 encryption method.
Set business component field user properties to the values defined in Upgrade Guide for Microsoft Windows.
8 hours
  1.  
Day 5
Siebel Upgrade Consultant
Set up global time zone support. For detailed instructions, see Siebel Tools Reference.
If you are extending date-time columns for a future configuration:
  • Set the Physical Type column property to UTC Date Time.
  • Set the Type property of business component field column property to DTYPE_UTCDATETIME.
8 hours
  1.  
Day 6
 
Run the Web Client Migration Wizard to upgrade custom view and applet definitions. In Siebel 7.5 Tools, select Tools > Upgrade > Web Client Migration. For detailed instructions, see Upgrade Guide for Microsoft Windows.
5 min.
  1.  
Day 6
 
Review the migrated applets and views and identify the following by query the Comments field.
  • New applet or new view migrated: MigN
  • Modified applet or view migrated: MigM
  • New applet or view to be migrated: TBMN
  • Modified applet or view to be migrated: TBMM
  • Verify the result through edit layout.
If necessary, manually regenerate customized applets in Siebel 7.5.
 
  1.  
Day 6
 
Use the Web Layout Wizard to migrate applets or views.
  • In Siebel Tools, highlight the applets or views (must belong to same class), right click and then select Web Layout Wizard.
  • Select the model applet, and for list applets, select the maximal visible columns.
 
  1.  
Day 6
 
Manually adjust list applet columns sequence and form applet fields layout, as necessary.
8 hours
  1.  
Day 6
Siebel Upgrade Consultant
Review client side interfaces:
  • Outbound customer applications, for example, one that invokes a desktop application such as Excel from a Siebel Client.
  • Inbound customer applications, for example, automation interface in the Windows client.
16 hours
for two interfaces
  1.  
Day 6
 
Configure the Siebel File System Manager.
If the File System Manager is set up incorrectly, users cannot access attachments.
 
  1.  
Day 6
Siebel Expert Services,
Siebel Upgrade Consultant
Modify dock objects.
 
  1.  
Day 10
Siebel Upgrade Consultant
Back up the new custom repository export file, custrep.dat, located under SIEBEL_ROOT\siebsrvr\Oracle.
You need this file for repository upgrade of the test and production environments.
 


 Planning an Upgrade to Siebel 7 
 Published: 18 June 2003