Applications Administration Guide > D&B Integration > Process of Integrating D&B Data >

Running the Siebel Update Server Components

There are two ways to run the Siebel update server components:

• From within the Siebel application
• From a command line interface, using Siebel Server Manager

The procedures for running the update processes from both within the Siebel application and from the command line are shown in Table 84. Whatever procedures you choose to follow, make sure that the D&B Update Manager (D&B) process is complete before you start the D&B Update Manager (Siebel) process.

NOTE:  If you have just installed the Siebel Server or if you have made changes to the Siebel Name Server, you need to synchronize before running the Siebel update server component. For more information about synchronizing server components, see Siebel System Administration Guide.

TIP:   If you are going to run the D&B Update Mgr (Multi-task) component, make sure that the maximum number of tasks (MaxTasks parameter) is set correctly to accommodate the number of tasks that you specified in the dnbtask.cfg file. For information about MaxTasks, see Siebel System Administration Guide.

To run the D&B Update Manager (D&B) server component from within your Siebel application (single task process)

1. Check that the Dun and Bradstreet component group is enabled.
2. Submit a component job for D&B Update Mgr (D&B); make sure to set the Mode to Asynchronous.
3. When the D&B Update Mgr (D&B) is done, open the log directory. If there have been problems with the process, there will be a log file, which you should review. The log file is named DNBUpMgrDNB_TaskNumber.log.

For information on running server components, see Siebel System Administration Guide.

To run the D&B Update Manager (D&B) server component from within your Siebel application (multiple task process)

1. Check that the Dun and Bradstreet component group is enabled.
2. Prepare a component job for D&B Update Mgr (Multi-task):
   • Make sure to set the Mode to Asynchronous.
   • Create a job parameter where Name is Task Code (Abbreviation is DNBTaskCode) and Value is DNB.
   • If the data is being loaded for the first time, create a job parameter where Name is Configuration File Name (Abbreviation is DNBConfigFile) and Value is dnbinitial.sql.
3. Submit the component job.
4. When the process is done, open the log directory. If there have been problems with the process, there will be a log file, which you should review.

For information on running server components, see Siebel System Administration Guide.

To run the D&B Update Manager (Siebel) server component from within your Siebel application (single task process)

1. Check that the Dun and Bradstreet component group is enabled.
2. Submit a component job for D&B Update Mgr (Siebel); make sure to set the Mode to Asynchronous.
3. When the D&B Update Mgr (Siebel) is done, open the log directory. If there have been problems with the process, there will be a log file, which you should review. The log file is named DNBUpMgrDNB_TaskNumber.log.

For information on running server components, see Siebel System Administration Guide.

To run the D&B Update Manager (Siebel) server component from within your Siebel application (multiple task process)

1. Check that the Dun and Bradstreet component group is enabled.
2. Prepare a component job for D&B Update Mgr (Multi-task):
   • Make sure to set the Mode to Asynchronous.
   • Create a job parameter where Name is Task Code (Abbreviation is DNBTaskCode) and Value is Siebel.
3. Submit the component job.
4. When the process is done, open the log directory. If there have been problems with the process, there will be a log file, which you should review.

For information on running server components, see Siebel System Administration Guide.

To run the D&B Update Manager (D&B) server component from a command line (single or multiple task process)

1. Log in to the server using Server Manager. Use a command with this format:

   SIEBEL_ROOT\siebsrvr\bin\>srvrmgr /g gateway /e enterprise_name /u db_username /p password /s siebserver

   Examples:

   >srvrmgr /g evlab6 /e siebel /u sadmin /p sadmin /s evlab6

2. At the srvrmgr prompt, enter one of the following commands:
   • start task for comp DNBUpMgrDNB (for single task process)
   • start task for comp DNBUpMgrMultiTask with DNBTaskCode=DNB (for multitask process)
   • start task for comp DNBUpMgrMultiTask with DNBTaskCode=DNB, DNBConfigFile=dnbinitial.sql (for initial data loading; see Multiple D&B Update Manager (D&B) Processes with First Time Data Loading)
3. During the DNBUpMgrDNB or DNBUpMgrMultiTask server process, monitor the status by entering the list task command:

   list task for comp DNB%

4. When the D&B Update Mgr (D&B) or D&B Update Mgr (Multi-task) server process is finished, open the log directory. If there have been problems with the process, there will be a log file, which you should review. The log files are named DNBUpMgrDNB_TaskNumber.log or DNBUpMgrMultiTask_TaskNumber.log.

For information on running server components, see Siebel System Administration Guide.

To run the D&B Update Manager (Siebel) server component from a command line (single or multiple task process)

1. Log in to the server using Server Manager. Use a command with this format:

   SIEBEL_ROOT\siebsrvr\bin\>srvrmgr /g gateway /e enterprise_name /u db_username /p password /s siebserver

   Examples:

   >srvrmgr /g evlab6 /e siebel /u sadmin /p sadmin /s evlab6

2. At the srvrmgr prompt, enter one of the following commands:
   • start task for comp DNBUpMgrSIEB (for single task process)
   • start task for comp DNBUpMgrMultiTask with DNBTaskCode=Siebel (for multitask process)
3. During the DNBUpMgrDNB or DNBUpMgrMultiTask server process, monitor the status by entering the list task command:

   list task for comp DNB%

4. When the D&B Update Mgr (D&B) or D&B Update Mgr (Multi-task) server process is finished, open the log directory. If there have been problems with the process, there will be a log file, which you should review. The log files are named DNBUpMgrDNB_TaskNumber.log or DNBUpMgrMultiTask_TaskNumber.log.

For information on running server components, see Siebel System Administration Guide.