Siebel -- EBC creation, client data end Configuration

EBC is an external BC, that is, the data source is not a Siebel database, but an external database, such as ERP.
EBC can perform queries, inserts, deletes, updates, and other actions, or even call functions in an external database.
The following describes the general steps of defining an EBC instance by taking the data obtained from an external view as an example:
1. create the required view in the external data source (it is best not to include aggregate functions. If you really want to use aggregate functions, consider using functions or packages) and assign necessary permissions. If the external data source is sqlserver, skip step 2.
2. Save the SQL statement of the created view as the XXX. DDL file.
3. Start tools, select new Wizard, select the General subtab in the pop-up window, and select exetenal table Schema
Import
Select a locked project. If a DLL file exists in the second option, select dll/analytics. Otherwise, select ODBC ([color = Red ]).
Oracle Database cannot select view, sqlserver
Yes ). [/Color] [color = Black] fill in a three-character table name, [/color] [color = Black] select database type-select one
Data sources (if the data source is not configured, it will be added in the following steps, this time can be left blank), click Finish! [/Color]
4. in step 2, we created a table. In fact, the configuration in this tool is basically complete, because the new table is external, but we can use it as a Siebel table.

 

5. to define the data source, first introduce the creation of the client:
. Before creating an ODBC connection to the target database, you must test the connection. Select the application configuration file XXX. cfg. For example, if Field Service is SFs. cfg, locate
[Datasources] Location
Insert the following content:
[XXX]
Connectstring = {ODBC data source name} eg: erp_prod
Tableowner = {external data source table owner} eg: Apps
DLL = {DLL used by external data sources} For example, Oracle uses eg: sscdo90.dll. For details, refer to the relevant documentation.
Sqlstyle = {SQL style} eg: oraclecbo
Dspassword = {default database user password} eg: Apps
Dsusername = {default database user} eg: Apps
Save and exit!
5.2. Definitions of data sources on the server side:
Create an ODBC data source on the server. If you add a tnsname connection string to Oracle, connect to the target database.
Choose Management> server configuration> enterprise> configuration information.
Copy a server data source and select a proper name and alias.
Modify the following parameters in the configuration information subview:
Data Source connect string: tnsname or ODBC name
DB connector dll: DLL used for database connection
Default Username Password: Default Database User Password
Data Source Default User name: Default Database User
Click the Advanced button to modify the following parameters:
SQL style: SQL Style
Click Save.
Navigate to the component definition view, select the component to use the data source, select "enable reconfiguration" from the menu, and modify the following parameters:
Om-named Data Source Name: Add ", data source alias created in configuration information configuration" Save and select "Submit reconfiguration" in the menu ".
Note: Some system components also need to add data sources, such as workflow process manager. Otherwise, the workflow or other functions may become unavailable.
6. Go back to the third step. If the data source does not select to create a new record in the Data sourse of the created table, enter name and Chanel.
The data source defined in the client and server must have the same name to reduce the update and maintenance workload.

 

This article from: http://www.itjaj.com/archiver/tid-2058.html