Siebel Business Rules Administration Guide > Installing the Business Rules Infrastructure >
Supported Installation and Uninstallation Scenarios
This topic describes the installation and uninstallation scenarios that are supported by Oracle Corporation for implementation of HaleyAuthority rules with Siebel applications. You must observe the following general guidelines for setting up Siebel applications to implement HaleyAuthority rules:
- HaleyAuthority may only be installed once for each machine. If you attempt to install Siebel Tools and HaleyAuthority on a machine that already has HaleyAuthority installed, the installation appears to succeed, but the second HaleyAuthority instance actually fails silently and is not installed.
- In a single development or production environment, consisting of Siebel Tools, Siebel Master Repository, and Siebel database, you must have no more than one instance of HaleyAuthority and one instance of the HaleyAuthority knowledge base.
HaleyAuthority is Windows-compatible only and is installed by default with Siebel Tools. CAUTION: To implement HaleyAuthority rules with Siebel applications, you must install and uninstall HaleyAuthority only as part of the Siebel Tools install and uninstall processes.
By default, HaleyAuthority is installed in the \RULE subdirectory of the Siebel Tools root directory. CAUTION: Do not change the name of the \RULE subdirectory during installation or after installation. However, you can opt to change the Siebel Tools root directory during installation, but not after installation.
The \RULE\Documents subdirectory contains Haley documentation for using HaleyAuthority, including the HaleyAuthority User's Guide. You can access the User's Guide from HaleyAuthority's Help menu. Two program groups are created for HaleyAuthority in Start > Programs: one as Haley Systems at the top level of the hierarchy, and one as Siebel Business Rules Developer at the same level as Siebel Tools. HaleyAuthority appears as a standalone program in Windows' Control Panel's Add/Remove programs. However, users must never uninstall HaleyAuthority separately from Siebel Tools. Instead, uninstall Siebel Tools, which includes uninstallation of HaleyAuthority. If you uninstall HaleyAuthority separately, then HaleyAuthority cannot be re-installed separately and work with Siebel applications. Instead, you must then uninstall Siebel Tools, then re-install Siebel Tools, including HaleyAuthority. NOTE: If you uninstall Haley, then reinstall Haley (all as part of uninstalling and installing Siebel Tools) and then open an existing knowledge base, you will generate an error if you attempt to deploy or test rule modules. To avoid the error, you must first run Object Importer to recreate the siebel.dat file, which stores various information about the knowledge base and runtime database.
Check your Control Panel's Add/Remove programs list for any independent listing of HaleyAuthority only as a precaution after uninstalling HaleyAuthority as part of a Siebel Tools uninstall. Remove any instance of HaleyAuthority that you find. NOTE: Even if Haley provides a new release of HaleyAuthority, you must only install HaleyAuthority as part of the Siebel Tools installation in order for HaleyAuthority to work with Siebel applications. Siebel's Object Importer plug-in is tied to a particular release of HaleyAuthority, so a new HaleyAuthority release is not typically compatible with Siebel applications.
If you must have multiple instances of Siebel Tools installed on a machine, as in a development environment, then you must choose a custom installation of Siebel Tools and explicitly uncheck the Siebel Business Rules Developer checkbox for all but one of the Siebel Tools installations. For detailed information about installing and uninstalling Siebel applications, see Siebel Installation Guide for the operating system you are using.
|