Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Database Upgrade Guide for DB2 UDB for z/OS > Performing the Siebel Repository Merge > Creating a New SRF FileEnvironments: Development environment only. This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade. You can optionally create an .srf file immediately after the repository merge. This enables you to run an application and evaluate whether you have resolved attribute conflicts correctly. After the you have completed the upgphys portion of the upgrade, you must create a new .srf file. This file includes the merged repository changes. If you will review your UI in more than one language, set the Tools Language setting and compile an .srf file for each language. For information about how to compile an .srf file for a specific language, see Siebel Global Deployment Guide. Requirements: The repository merge must have been successful. Compiling a New SRF File Immediately After the Repository MergePerform this optional procedure immediately after the repository merge and before you perform the upgphys upgrade in the development environment. Repeat this procedure as needed to help evaluate how you have resolved attribute conflicts. Do not use this procedure to compile an .srf file if you have completed the upgphys upgrade. Instead, see Compiling a New .srf File After the Upghys Upgrade. To compile a new .srf file after the repository merge
Compiling a New .srf File After the Upghys UpgradeAfter completing the upgphys upgrade in the development environment, you must compile a new .srf file. This updates the file with the merged repository changes. This is the .srf file you will copy to the Siebel Servers in your test environment. To compile a new .srf file after the upgphys upgrade
|
![]() |
![]() ![]() |
Siebel Database Upgrade Guide for DB2 UDB for z/OS | Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |