Archive for the ‘Functional Topic’ Category

Authentication Methods in Siebel

 

Authentication is the process of verifying the identity of the user before he gains access to the application. The process consists of collection of user credentials (such as User Id and Password) and comparing them with pre-stored values.

Following three general authentication methods are supported by Siebel:

 

1)    Database Authentication

  • A separate database login for each user.
  • Users will provide credential details to DBA. DBA will add/modify/delete those users to database.

 

2)    Directory Server Authentication

  • Single database login can be shared among multiple users.
  • Users can directly modify their credentials within Siebel application. It will automatically be synchronized with the directory server.
  • Third party directory server is required.

 

3)    Web Single Sign-On

  • Login once and access multiple applications. This facility is internally managed through tokens.
  • Single database login can be shared among multiple users.
  • Users need to provide their credentials to the DBA.
  • Third party directory server is required.

 

Integration Components

Integration Components (ICs) are the building blocks of Integration Objects. As IO is mapped to BO, in the same fashion, IC is mapped to corresponding BC.

  • One or more IC constitutes the integration object.
  • At least one IC will be primary corresponding to primary business component of the business object.
  • There would be zero or more child IC with respect to child business components in the business object.
  • Each MVG in business component is exposed as a child IC under the integration object.

Integration components have following Integration Component Keys (ICK):

  • User Keys – Set of fields to determine the records uniquely
  • Status Keys – To store the Siebel Row ID and operation status for insert, update or delete scenarios

On creating the integration objects through Siebel Wizard:

  • Calculated Fields at the business component are imported automatically as inactive fields in Integration Component.
  • For any unneeded field, mark it as Inactive. Never delete a field from Integration component as it will be added again when Business Object is upgraded.

Integration Objects – Types

There are two types of Integration Objects as follow:

1. Internal IO

  1. Describes structure of data being read or written to Siebel application
  2. Represents a subset of Siebel Business Object

 

2. External IO

  1. Describes of structure of data being exchanged between Siebel application and External application
  2. Is required in two scenarios:
    • External application is unable to handle data in Siebel format
    • Additional manipulation is required before saving the received data at Siebel end

 

Integration Objects

 

Integration Objects (IO) defines the structure of data to be exchanged between Siebel application and external system. IO represents hierarchical data structures.

IO also used as templates to create memory-resident instances for data processing by business services.

IO consists of Integration Components (IC). One of them is marked as Primary IC. IC further consists of Integration Component Fields (ICF).