Bookshelf Home | Contents | Index | PDF |
Applications Administration Guide > D&B Integration > Configuring D&B IntegrationFor general guidance on configuration, refer to Table 76.
A number of specific configuration topics are discussed in this section:
TIP: When debugging in your test environment, increase the event log level to 4 to see more details in the log file. However, it is strongly recommended that you set the level to 1 (the default) when you run in a production environment in order to prevent the log file from overflowing. For information on event logging, see System Monitoring and Diagnostics Guide for Siebel Business Applications. Update Server Process ConfigurationThe D&B update server processes use the Batch Real-Time Integration (RTI) technology and the RTI configuration files (dnbmaps.sql for single task and dnbmaps.tsq for multiple tasks). You can edit the RTI configuration files to suit your business requirements. The general syntax of the RTI maps specified in the configuration files is as follows: UPDATE_SOME_TABLE.MOD1TABLE = [Target Table to update] UPDATE_SOME_TABLE.MOD1WHERE = [A WHERE clause] UPDATE_SOME_TABLE.MOD1INSERT = [TRUE/FALSE] UPDATE_SOME_TABLE.MOD1UPDATE = [TRUE/FALSE] UPDATE_SOME_TABLE.MOD1DELETE = [TRUE/FALSE] UPDATE_SOME_TABLE.MOD1SQL = [A Valid SQL Query] The RTI configuration files are located in the Field Mapping for the D&B Update Manager Process lists the default mapping for the D&B Update Manager (Siebel) server component. Use caution when making changes to these RTI configuration files. It is recommended that you engage a qualified professional for your customization process. CAUTION: Do not change the default DELETE setting in the existing UPDATE* sections. Do not set DELETE to TRUE. If your business need necessitates deleting rows in the target table as part of the D&B Update Manager process, consult Siebel Professional Services for help with this customization process. Account Promotion and Prospect List Creation ConfigurationYou can select specific fields that will be populated by the D&B promotion to a Siebel account or by the D&B list-creation process. These are controlled by maps in the business component user properties within the DNB Account and DNB Contact business components. These maps are listed in Table 82. Using Siebel Tools, you can change, add, or delete source and destination field mapping. Reference the map descriptions given in Table 82 to determine which map to use for a given set of source and destination fields. Use caution when making changes to these maps. It is recommended that you engage a qualified professional for your customization process. CAUTION: Although the delete capability is available, it is recommended that you deactivate unwanted map entries instead of deleting them. This is safer and can be accomplished by checking or clicking the deactivate column for the undesired entry. You can create an entry using the following syntax: Name Column: [MAP NAME]: [DESTINATION FIELD] Value Column: [D&B SOURCE FIELD] NOTE: Each map works only with a specific Destination Business Component and a specific Source Business Component. Running the D&B Update Manager (D&B) Process Without Updating or Deleting Existing DataDepending on your business process, you may want to run the D&B Update Manager (D&B) server component without updating or deleting any existing data in the S_DNB_ORG table. This is done by editing the RTI configuration file. To edit the RTI configuration file so that existing data in the S_DNB_ORG table is not updated or deleted
Running the D&B Update Manager (Siebel) Process Without Updating Account Name or Account LocationDepending on your business process, you may want to run the D&B Update Manager (Siebel) server component without updating the existing account names and account locations. This is done by editing the RTI configuration file. To edit the RTI configuration file so that account names are not updated
To edit the RTI configuration file so that account locations are not updated (single task)
To edit the RTI configuration file so that account locations are not updated (multiple task) |
Applications Administration Guide |