Bookshelf Home | Contents | Index | PDF |
Applications Administration Guide > D&B Integration > Process of Integrating D&B Data > About Siebel Update Server ComponentsWhenever you load or reload D&B data, you must update the D&B Account tables and the Siebel Account tables in the Siebel database. This update is accomplished by running server components:
Overview of the Update ProcessThis section outlines the process of loading D&B data from the staging tables to the D&B Account tables through to updating the Siebel account tables. This process recommends using the D&B Update Manager MultiTask server component to run server component tasks in parallel. However, use of the single task D&B Update Manager (D&B) and D&B Update Manager (Siebel) server components is also documented in this chapter.
Single Task Siebel Update Server ComponentsThe update server components are part of the Dun and Bradstreet Enterprise Component Group. This group and each of its D&B Batch Components must be enabled. Once enabled, each component can be run as a batch task. Figure 29 shows how the staging tables are mapped to the D&B Account tables. Figure 30 shows how the D&B Account tables are mapped to the Siebel Account tables. Field Mapping for the D&B Update Manager Process lists the default table mapping from the D&B Account tables to the Siebel Account tables that are used by the D&B Update Manager (Siebel) server component. Multiple Task Siebel Update Server ComponentYou can use the server component DNBUpMgrMultiTask to spawn multiple Update Manager processes. Running several parallel processes helps you maximize your performance with large data loads and gives you greater scheduling flexibility. You can control the number of processes that are created by editing the dnbtask.cfg file. The dnbtask.cfg file contains two sections, one to set tasks for the D&B Update Manager (D&B) process and the second to set tasks for the D&B Update Manager (Siebel) process. The dnbtask.cfg file is located in the sqltempl subdirectory, in the server installation directory. Multiple D&B Update Manager (D&B) ProcessesBy default the dnbtask.cfg file sets up three simultaneous tasks, based on D-U-N-S number ranges. The DNBUpMgrDNB portion of the file looks like this: These three ranges translate into three DNBUpMgrDNB tasks, each taking care of loading records within a particular D-U-N-S number range: ,100000000 means D-U-N-S numbers < 100000000 100000000,200000000 means D-U-N-S numbers >=100000000 and < 200000000 200000000, means D-U-N-S numbers >=200000000 Edit the file to change the number of parallel processes created or the range of D-U-N-S numbers updated. CAUTION: If you use DNBUpMgrMultiTask to run multiple UpdateMgr processes, you must make sure that processes running at the same time have mutually exclusive ranges. Unpredictable results occur if multiple processes collide. Multiple D&B Update Manager (D&B) Processes with First Time Data LoadingThe first time you load D&B data, that is, when there are no D&B records in the database, you may use a special SQL file (dnbinitial.sql) which is optimized to do only inserts. This results in faster loading of data than using the dnbmaps.tsq file. To use the dnbinitial.sql file, set the server component parameter DNBConfigFile to dnbinitial.sql. For examples, see Running the Siebel Update Server Components. For subsequent updates, the DNBConfigFile should be set to dnbmaps.tsq. NOTE: The dnbinitial.sql file assumes that you dropped the indexes on the D&B Account tables when loading data (Loading D&B Data Using Sample Scripts). Multiple D&B Update Manager (Siebel) ProcessesBy default the dnbtask.cfg file sets up five simultaneous tasks, based on tables updated. The DNBUpMgrSieb portion of the file looks like this: Task2 = UPDATE_INDUST, COMMIT, UPDATE_SIEBEL_INDUST, COMMIT, Task3 = UPDATE_SIEBEL_ADDR_PHY, COMMIT, UPDATE_SIEBEL_ADDR_MAIL Task5 = UPDATE_SIEBEL_LOC1, COMMIT, UPDATE_SIEBEL_LOC2, COMMIT, UPDATE_SIEBEL_LOC3 You may edit the file to change the number of parallel processes created. However, note that the order of the updates within individual tasks is important; for example UPDATE_INDUST should be done before UPDATE_SIEBEL_INDUST. Use caution when updating the DNBUpMgrSieb portion of the dnbtask.cfg file. CAUTION: If you have modified the RTI configuration file to insert new accounts into the Siebel Accounts table, do not run the multiple task process. Instead you must run the single task D&B Update Mgr (Siebel) server component. Make sure you have modified the dnbmaps.sql file used by the single task server component. The order of the updates is critical to data integrity if new accounts are being added. |
Applications Administration Guide |