Configure DC Local Server Mode

Configuration files location

You can find the configuration files here:

 plauti/dclocalserver

The server usually works with the system user.
You can find the files in the 'Root' directory. If you change the running user, follow the 'User' directory to find the files.

Windows - Root

    c:\Windows\System32\config\systemprofile\plauti\dclocal_server

Windows - User

c:\Users\username\plauti\dclocal_server

Linux - Root

 /root/plauti/dclocal_server

Linux - User

 /home/username/plauti/dclocal_server

Configure DC Local Server Mode

Before you can use DC Local Server Mode with a new Dynamics environment, you need to change some settings in the properties file, located in:

config/application.properties

Set batch profile

The batch profile setting determines how many resources DC Local will take up on your machine. The higher you set this, the quicker the jobs get processed. When set to 'High', DC Local will take up the maximum amount of resources to run jobs. If you have multiple processes running on your server, pick a lower setting. 

Set the environment

To establish a connection, DC Local needs to know which environment it will work with: Production or Sandbox. The default setting is Production. Make sure that the environment mentioned in the file matches your Salesforce environment.

You can also set the environment to Custom so you can only log into the server through a custom URL. In that case, also set a custom domain to use for logging in.

Set an email address

Optionally, set one or more email addresses to receive information when something goes wrong. Separate them with commas.

See below for an example of the configuration file where the environment has been set to Sandbox, and two email addresses to receive information have been set. Lines with a '#' in front of them are commented out. Remove the '#' to activate a setting parameter.

# Plauti DC Local configuration file


logging.level.root=INFO
logging.level.com.plauti.dcl=DEBUG
dcl.sf.namespace=dupcheck


# Low | Medium | High
dcl.batch-profile=Medium


# Service Mode Types -> SF (Salesforce), MS (Microsoft)
dcl.service-mode.type=MS
dcl.service-mode.email-list=john.smith@plauti.com, jane.doe@plauti.com


# Instance Url FOR MS Dynamics
#dcl.service-mode.url=https://enteryourmsdynamicsinstanceurlhere.crm4.dynamics.com

Use DC Local Server Mode

1. Connect your Dynamics 365 environment to DC Local

1. Log into your Dynamics 365 environment on any device.
2. On the device where you installed DC Local Server Mode, open a command-line interface.
   To start DC Local in server mode, type in the following command:
   Windows:

   net start dclocal

   Linux:

   sudo service dclocalserver start

3. Open the log file. You can find it in:

   logs/app.log/spring.log

4. Look up the verification URL in the log file. Navigate to the URL. 
5. The connection page will ask you for a verification code. Find the code in the log file. Enter it on the page and click 'Connect'.
6. Dynamics asks you to allow access to Duplicate Check. Click 'Allow'.

You are now connected.

You can stop DC Local Server using the following commands:

Windows

net stop dclocal

Linux

 sudo service dclocalserver stop

Windows

Go to Services.

Linux

sudo service dclocalserver status

2. Send a job to the DC Local server

1. On the server, start DC Local in server mode (see above).
2. In Dynamics 365, go to Duplicate Check Job, and click + Add New Job at top left.
3. Enter the job details and click Next. 
4. At the Processing options, select DC Local and click Start.
5. Optionally, check the progress in the spring.log file.
6. The job results will be sent back to Dynamics 365 after the job completes. Find it there in the Duplicate Check Jobs overview to process the results.