Integration Platform Technologies: Siebel Enterprise Application Integration > External Business Components > Process of Configuring External Business Components >

Specifying Run-Time Parameters

After the data source definition is named in Siebel Tools, you specify the run-time parameters by configuring the data source definition, and updating the server component definition.

If testing using the Siebel Developers Web Client, add a [DataSource] section to the client .cfg file.

This task is a step in Process of Configuring External Business Components.

Configuring the Data Source Definition

As part of specifying the run-time parameters, configure the data source definition.

To configure the data source definition

1. Navigate to Administration - Server Configuration > Enterprises > Profile Configuration.
2. Copy an existing InfraDatasources named subsystem type.
3. Change the Profile and Alias properties to the Data Source name configured in Siebel Tools.
4. Update the profile parameters to correspond to the external RDBMS:
   • DSConnectString = data source connect string
     • For the Microsoft SQL Server or the IBM DB2 databases, create an ODBC or equivalent connection and input the name of this in the parameter.
     • For an Oracle RDBMS, this value should specify the TNS name associated with the database and not an ODBC or other entry.
   • DSSQLStyle = database SQL type

     See Table 49 for a listing of the supported SQL types.

   • DSDLLName = DLL Name corresponding to the SQL type

     See Table 49 for a listing of the supported connector DLL names and SQL Styles.

   • DSTableOwner = data source table owner
   • DSUsername = default user name used for connections (Optional)
   • DSPassword = default password used for connections (Optional)

     NOTE:  The DSUsername and the DSPassword parameters are optional. However, to avoid receiving a log in prompt when accessing the external data source, specify DSUsername and the DSPassword. If specified, this will override the default user name and password.

The DSUsername and the DSPassword parameters are activated only when using the Database Security Adapter. For more information, see Configuring a User in LDAP or ADSI Security Adapter To Access EBCs.

Configuring a User in LDAP or ADSI Security Adapter To Access EBCs

It is not a good idea to assume that the login to your primary data source is always the same as the login to the external data source.

If you are using the Lightweight Directory Access Protocol (LDAP) or the Microsoft Active Directory Service Interfaces (ADSI) setup for the Siebel application and you try to access an EBC, the security adapter is called to authorize the user trying to access the external database.

When LDAP or ADSI authentication is used, the username and password values for the external data source is provided in the ADSI SharedCredentialsDN parameter and the CredentialAttributeType attribute.

For example, the name of your external data source is: MyExtDataSrc, and your ADSI is configured with the following parameters:

SharedCredentialsDN= cn=sharedcred,ou=people,dc=siebel,dc=com

CredentialAttributeType = mail

In your ADSI server modify the mail attribute for the following entry:

cn=sharedcred,ou=people,dc=siebel,dc=com

Before modifying, one value must already exist (assuming sadmin and db2 are the user name and password for the ServerDataSrc data source, which is the primary data source):

type=ServerDataSrc username=sadmin password=db2

Add additional values to the mail attribute (assuming mmay and mmay are the user name and password for the MyExtDataSrc data source, which is the external data source):

type=MyExtDataSrc username=mmay password=mmay

After adding the new value for the external data source to the mail attribute, you are able to access EBCs.

Configuring the Data Source Definition for the Siebel Developers Web Client

If testing using the Siebel Developers Web Client, add a [DataSource] section to the client .cfg file for the data source definition named in Siebel Tools. In this example, WindyCity is the data source being added.

To configure the data source definition in the Siebel Developer Web Client

1. Add the data source definition named in Siebel Tools. In this example, the data source definition named is WindyCity:

   [DataSources]

   Local = Local

   Sample = Sample

   ServerDataSrc = Server

   GatewayDataSrc = Gateway

   WindyCity = WindyCity

2. In the data source section of the application's .cfg file, add the following parameters (for the supported SQL types and connector DLL names, see Table 49):

   [WindyCity]

   Docked = TRUE

   ConnectString = data source connect string

   SqlStyle = database SQL type

   TableOwner = data source table owner

   DLL = DLL Name corresponding to the SQL type

   DSUsername = user id (Optional)

   DSPassword = password (Optional)

Supported Connector DLL Names and SQL Styles

When defining the DLL and SQL files for importing the external schema, the external database being used might not be the same as the Siebel database. Table 49 contains the supported connector DLL names and the corresponding SQL styles.

Updating the Server Component to Use the New Data Source

As part of specifying the run-time parameters, update the server component to use the new data source.

To update the server component to use the new data source

1. Navigate to Administration - Server Configuration > Enterprises > Component Definitions.
2. In the Component Definitions list applet, select your Application Object Manager Component. For example, select the Call Center Object Manager (ENU).
3. Select Start Reconfiguration from the Menu drop-down list on the Component Definitions list applet.

   The Definition State of the component will be set to Reconfiguring. Reselect your application component after selecting the Start Reconfiguring menu item.

4. In the Component Parameters list applet, query for OM - Named Data Source name, and update the Value by adding the alias name of the datasource specified in the To configure the data source definition section.

   The format of the OM - Named Data Source name parameter is a comma-delimited list of data source aliases. It is recommended that you do not modify the default values, and that you add their new data sources to the preexisting list.

5. After the parameter values are reconfigured, commit the new configuration by selecting Commit Reconfiguration from the Menu drop-down list on the Component Definitions list applet.

   The new parameter values are merged at the enterprise level.

   To cancel the reconfiguration before it has been committed, select Cancel Reconfiguration from the Menu drop-down list on the Component Definitions list applet.