Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Applications Administration Guide > D&B Integration > Integrating D&B Data > About Siebel Update Server ComponentsWhen 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 topic 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. After enabled, each component can be run as a batch task. Figure 6 shows how the staging tables are mapped to the D&B Account tables. Figure 7 shows how the D&B Account tables are mapped to the Siebel Account tables. Default table mapping exists from the D&B Account tables to the Siebel Account tables that are used by the D&B Update Manager (Siebel) server component. For more information, see Field Mapping for the D&B Update Manager Process. 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, a section to set tasks for the D&B Update Manager (D&B) process and a section 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 uses D-U-N-S number ranges to set up three simultaneous tasks. The DNBUpMgrDNB portion of the file looks as follows: These three ranges translate into the following three DNBUpMgrDNB tasks, each taking care of loading records within a particular D-U-N-S number range:
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, then 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 when there are no D&B records in the Siebel database, you can use a special SQL file (dnbinitial.sql) which is optimized to load only inserts. Consequently, data is loaded faster than when you use 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 is set to dnbmaps.tsq. NOTE: The dnbinitial.sql file assumes that you dropped the indexes on the D&B Account tables when loading data. For more information, see Loading D&B Data Using Sample Scripts. Multiple D&B Update Manager (Siebel) ProcessesBy default the dnbtask.cfg file uses the tables updated to set up five simultaneous tasks. The DNBUpMgrSieb portion of the file looks as follows: 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 can edit the file to change the number of parallel processes created. However, the order of the updates within individual tasks is important; for example UPDATE_INDUST must 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, then 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. |
![]() ![]() |
Siebel Applications Administration Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |