1. Using Siebel Tools
  2. What’s New in This Release

11Testing and Troubleshooting Your Customizations

Testing and Troubleshooting Your Customizations

This chapter describes how to use Siebel Tools to test and troubleshoot your customizations. It includes the following topics:

Testing and Troubleshooting Your Modifications

This topic includes the following information:

To test your modifications, you can use a local instance of the Siebel Web Client that runs on your computer. If you compile objects and test the results locally, then consider the following:

  • If you compile modifications to a repository, then any local instances of the Siebel Web Client that are open and that read this repository automatically close, reopen, and then display the modified configuration.

  • You can configure Siebel Tools to automatically open the Siebel Web Client and read the most current repository.

  • To display your modifications in a local instance of the Siebel Web Client, this client must read the repository that you compile.

This task is a step in Roadmap for Setting Up and Using Siebel Tools.

For more information about installing the Siebel Web Client, see the Siebel Installation Guide for the operating system you are using.

For information about using debug windows, see the following information:

    Setting Debug Options to Open the Siebel Client

    The debug options allow you to modify the run time settings that open an instance of the Siebel Web Client in the following situations:

    • You enable Auto-start Web Client.

    • You click the Debug menu, and then click Start to start an instance of the Siebel Web Client. You typically do this if you want to debug Siebel eScript or Siebel VB. For more information, see Siebel eScript Language Reference or Siebel VB Language Reference.

    To set debug options to open the Siebel client

    1. In Siebel Tools, click the View menu, and then click Options.

    2. In the Development Tools Options dialog box, click the Debug tab.

    3. Set the debug options.

      Make sure you set the following options:

      • Executable

      • CFG File

      • Browser

      • Working Directory

      For more information, see Development Options for Debugging.

      Recovering from a Failed Development Server

      This topic describes how to recover from a failed development server or failed repository when you cannot access a backup copy of this server or repository. It requires that a recent image of the repository exist on the computer that a remote user uses, and that this user performed a full Get to create this repository.

      To recover from a failed development server

      1. Log in to Siebel Tools on the remote computer that includes the intact repository.

      2. Archive the projects that this repository contains.

        For more information, see Exporting Objects to an Archive.

      3. Create a new repository:

        • To create a repository record, you can add a new repository object in Siebel Tools.

        • To create the schema in the database for the repository, you can run imprep.ksh for Linux or UNIX.

          For more information, see Exporting and Importing Repositories.

      4. Import the archive you created in Step 2 into the repository you created in Step 3.

        For more information, see Importing Objects from an Archive.

      5. Test the repository you created in Step 3 and make sure it includes the expected functionality.

      6. Check projects into the Siebel Server.