Siebel Business Rules Administration Guide > Creating and Deploying Rules > Using Siebel Object Importer >

Importing Siebel Objects

In order to compose rules to act on Siebel objects, you must first:

• Generate a minimal set of HaleyAuthority objects that are required for implementing rules in Siebel applications. This import happens implicitly when you do your first import of Siebel objects for a new HaleyAuthority knowledge base.

  For detailed information, see Siebel Concepts, Relations, Actions, Functions, and Predicates.

• Import Siebel objects into HaleyAuthority. You expicitly choose to import the Siebel objects on which your rules are based. See Using Siebel Object Importer.

When you import specific Siebel business objects, business components, and fields on which to build your rules, Siebel Object Importer automatically creates HaleyAuthority concepts and relations to represent those objects.

For detailed information on the mapping between Siebel Objects and HaleyAuthority concepts and relations, see Siebel Object Model Mapping to the HaleyAuthority Semantic Role Model.

Table 3 provides the fundamental relations and their phrasings that are automatically created in HaleyAuthority by Object Importer. Names of automatically-created relations are of the form:

siebelparentobject_siebelchildobject

The object names are rendered in lower case with no spaces and are connected with an underscore.

Note the following Object Importer restrictions and limitations:

• You can only import one Business Object at a time.
• The following fields cannot be imported:
  • Non-UTC date/time fields; that is, fields of Type DTYPE_DATETIME
  • Calculated fields without Type
  • Fields of Type DTYPE_CLOB
• You must not manually modify concepts and relations that are built among Siebel objects in HaleyAuthority. Such changes must result only if the relations change in the Siebel Repository, and you then make those changes by using Object Importer to synchronize the HaleyAuthority knowledge base with the Siebel Repository.

Once a particular Siebel object is imported, it can be used by anyone with access to the HaleyAuthority authoring environment to build other rules.

Before importing Siebel objects into HaleyAuthority, see Using Object Importer and Deployment Log Files for information on enabling the Object Importer log file.

To import Siebel objects into HaleyAuthority

1. Launch HaleyAuthority in either of the following ways:
   • Choose Start > Program Files > Program Group that contains Siebel Tools > Siebel Business Rules Developer.
   • Choose Start > Program Files > Haley Systems > HaleyAuthority Enterprise.
2. In HaleyAuthority, choose File > Import > Siebel Object.

   Siebel Object Importer Wizard launches.

3. From the Siebel Object Importer Wizard Welcome screen, click Next.
4. In the Login screen, enter database connection parameters, then click Next. For each of the Master Repository database and the runtime datasource:
   • Specify (or browse to) the Siebel application cfg file (for example, uagent.cfg or siebel.cfg) which points to the applicable database. It is typically located in the \BIN\LANG directory in your Siebel server root directory (or Siebel client root directory for a local database), where LANG is the language code (for example, ENU).
   • Enter the login credentials to the applicable database.
   • Choose the datasource - ServerDataSrc, GatewayDataSrc, Sample, or Local.
   • For the runtime data connection, also choose Server or Local mode.
5. In the Pick Task screen, click the Import Siebel objects radio button, then click Next.
6. From the Pick Business Object screen, select one business object from the picklist, then click Next.

   NOTE:  If you import a business component or field that has been imported previously, then Object Importer does not create duplicate concepts

7. The Pick Business Components screen lists the hierarchy of business components of the business object you chose in Step 6. Click the checkbox of each business component of this business object that you want to import. Click expansion icons to see and select child business components. Click Next.

   NOTE:  If you expand a business component to select a child business component, then its parent business component is automatically selected.

   NOTE:  You can import different fields for a business component by importing the business component more than once, adding new fields in subsequent imports.

8. The Pick Business Component Fields screen lists the fields of the first business component that you chose in Step 7. In the Available Fields list, click each field you want to import. Click the right arrow to move the selected fields to the Selected Fields list or click the double right arrow to move all of the available fields. Click Next.

   The fields for the next business component you chose in Step 7 display in the Available Fields list. Repeat this step to select fields for each business component you chose in Step 7.

9. The Finish screen displays the hierarchy of business object, business components, and fields to be imported. Confirm to import this hierarchy by clicking Finish.
10. To import more objects, click Yes, else click No.

    The Output screen displays a log of the concepts, relations, and dictionary objects that are automatically created in HaleyAuthority.

    NOTE:  For multi value fields (MVFs), concepts are created for the target business component of the MVF and for its primary.

For overview information about Siebel Object Importer, see About Siebel Object Importer.