Siebel Database Upgrade Guide for DB2 for z/OS > Performing the Siebel Repository Merge >

Creating a New Siebel Repository File


Upgrades: All upgrades.

Environments: Development environment only.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

You can optionally create a Siebel Repository File (.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.

Prerequisite: The repository merge must have been successful.

Compiling a New SRF File Immediately After the Repository Merge

Perform this optional procedure immediately after the repository merge and before you perform the upgphys upgrade in the development environment. Repeat this procedure as necessary 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 Upgphys Upgrade.

To compile a new .srf file after the repository merge

  1. Navigate to the following directory on an upgraded Siebel Server you will use to test applications in the development environment. Verify that this is not the directory where Siebel Tools is installed:

    Windows: SIEBEL_ROOT\OBJECTS\language

    UNIX: $SIEBEL_ROOT/OBJECTS/language

    where:

    language is the installed language, for example, ENU.

  2. Rename the siebel.srf file to siebel_release.srf.
  3. On the Siebel Tools development workstation, connect to the database against which you ran the merge.
  4. Start Siebel Tools.
  5. Choose File, and then Open Repository.
  6. Select New Customer Repository.
  7. Choose Tools, and then Compile Projects.
  8. Select All Projects.
  9. Enter the path to the Siebel Server OBJECTS directory where you renamed the siebel.srf file, and specify siebel.srf as the filename.

    NOTE:  Do not enter the path to the Siebel Tools OBJECTS directory. You will overwrite and destroy the Siebel Tools .srf file.

  10. Click Compile.
  11. Copy the contents of the Siebel Tools WEBTEMPL directory to the Siebel Server WEBTEMPL directory.
  12. Start the application.

Compiling a New .srf File After the Upgphys Upgrade

After 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

  1. Navigate to the following directory on an upgraded Siebel Server you will use to test applications. Verify that this is not the directory where Siebel Tools is installed:

    Windows: SIEBEL_ROOT\OBJECTS\language

    UNIX: $SIEBEL_ROOT/OBJECTS/language

    where:

    language is the installed language, for example, ENU.

  2. Rename the siebel.srf file to siebel_release.srf.
  3. On the Siebel Tools development workstation, connect to the database against which you ran the merge.
  4. Start Siebel Tools.
  5. Choose File, and then Open Repository.
  6. Select Siebel Repository.
  7. Choose Tools, and then Compile Projects.
  8. Select All Projects.
  9. Enter the path to the Siebel Server OBJECTS directory where you renamed the siebel.srf file, and specify siebel.srf as the filename.

    CAUTION:  Do not enter the path to the Siebel Tools OBJECTS directory. You will overwrite and destroy the Siebel Tools .srf file.

  10. Click Compile.

    Siebel Tools creates a new .srf file and places it at the specified location on the Siebel Server.

Siebel Database Upgrade Guide for DB2 for z/OS Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.