Running the Integration Daemon

Summary of Steps to Start the Integration Daemon

The following steps are documented for both Microsoft Windows and Linux operating system installations. On Windows, the servers are normally started as Windows Services, although they can be started from the command-line for troubleshooting purposes. On Linux and other operating systems the servers are started on the command-line and run as background processes.

  • Start the ExtraView server
  • Start the Integration Daemon

Start ExtraView Server

Start the application server (i.e., Tomcat, WebLogic) that has the ExtraView application deployed. Once the application server is started, connect to the ExtraView application with a web browser or other client from the machine where the integration daemon is installed in order to ensure connectivity from the integration daemon to the ExtraView application.

Start Integration Daemon

On Microsoft Windows, if the integration daemon was installed as a Windows Service, then simply start the service named ExtraViewIntegrationDaemon. To start the integration daemon on the command-line, you must first open a Command Prompt window and change the current directory to the installation directory, INTEGRATION_HOME:


Next, execute the start_daemon.bat script. The following lines are written to the Command Prompt window as the integration daemon starts:

Salesforce Integration Daemon Started
 Setting event log:C:\ExtraView\integrationdaemon\logs/SalesForce
Attempting to Open Log File: C:\ExtraView\integrationdaemon\logs\error.log
Log is:C:\ExtraView\integrationdaemon\logs\error.log
Running without a queue...
SFC: Logged into Salesforce with the

On Linux, execute the following commands to start the integration daemon:


Stop Integration Daemon

On Microsoft Windows, if the integration daemon was installed as a Windows Service, then simply stop the service named ExtraViewIntegrationDaemon. To stop the integration daemon on the command-line, type [Ctrl]+C on the Command Prompt window where you started the integration daemon. For example:

Running without a queue...
Terminate batch job (Y/N)? y

On Linux, stop the script when it is running in the foreground. If the integration daemon is running in the background (e.g., using nohup or &), then find the process id of the java process running the com.extraview.sccintegration.common.IntegrationDaemon program and stop or kill the process.

State File –

Certain dynamic runtime state variables are maintained in a persistent properties file, named This file is maintained in the INTEGRATION_HOME/data/SalesForce directory and it must be available for writing by the application (e.g., privileges are set appropriately and the file must not be “in use by another application”). The state file contains the state of progress data about the application, such as the latest ExtraView history already processed. Since state information is maintained internally during the operation of the daemon, it will do no good to modify the values in this file while the daemon is running. The values can be modified when the daemon is not running, and the new values will be used when the daemon starts. The following keys and values are examples of state properties; note that all timestamps are maintained in a universal timestamp format, including time zone.

#Cutoff values for EVInterface and PeerInterface
#Thu Feb 09 12:29:24 PST 2012
EV_TIMESTAMP=2012-01-29 13\:40\:39.079 -0800
SF_TIMESTAMP=2012-02-09 12\:29\:29.607 -0800

It is possible to edit this file manually to rework some transactions or correct an error. However, if you do this, you must be careful to preserve the syntax and format of the file.

Error Log

The default location for the file error.log is in the logs sub-directory of the directory in which the Integration Daemon is installed. The log file contains entries recounting integration daemon activity, including exceptions and other entries depending upon the log level setting. Log information includes the Salesforce records that matched and mapped to ExtraView issues, ExtraView issue ids that matched and mapped to Salesforce records, the names/ids of newly created records/issues, actions that failed, and notification of the updating of cutoff thresholds. If the daemon shuts down due to a failure, the log will include as much information about the failure as it is able to ascertain.

Note: Configuration errors such as fields mapped incorrectly, may cause the daemon to shut down, and a log entry to be created. This is because continued operation may result in a loss of synchronization of the ExtraView and Salesforce databases.