A new app: Plauti Server

To improve user experience, maintenance, and feature consistency, DC Local Server Mode has been replaced by a new app: Plauti Server. 

DC Local Server Mode still works, so you can try out Plauti Server for Sandbox while still keeping DC Local Server for Production for now. However, DC Local Server will not be updated anymore, so in order to receive all maintenance and security updates we recommend fully switching to Plauti Server soon.

Of course you can also replace DC Local Server Mode with Plauti Server straight away. 
Note that upon its release, no changes were made in the code with regard to the processing of Deduplicate jobs compared to DC Local Server.

Replacing DC Local Server with Plauti Server

These steps describe the process of replacing DC Local Server Mode by Plauti Server in one go.
For testing Plauti Server in Sandbox while continuing to use DC Local Server for production, see below.

To replace Duplicate Check Server Mode with Plauti Server:

1. Copy the configuration files ('application.properties' in particular) and uninstall DC Local Server Mode as described in Uninstall DC Local or DC Local Server Mode.
2. Install Plauti Server as described in Install Plauti Server on Windows or Install Plauti Server on Linux.
3. Open Plauti Server and connect it with your Org or Environment as described in Getting Started with Plauti Server.
4. Configure the Plauti Deduplicate Settings the same way as your previous DC Local settings:
   • In the application.properties file you saved, find the Batch Profile at dcl.batch-profile. This corresponds with the 'CPU' setting in the System Resource Usage section of the Plauti Deduplicate Settings in Plauti Server.
     In addition, you can add a maximum memory to be used as well.
   • In DC Local Server, all jobs were run automatically. To replicate this, enable ‘Auto Run Jobs’ in Plauti Server for your Org or Environment.
5. For DC Local Server, the server where you installed DC Local Server Mode needed to be able to reach https://www.plauti.com/support//plautilocal.blob.core.windows.net. For Plauti Server this has changed to https://www.plauti.com/support//plautiapps.blob.core.windows.net. Update your server settings accordingly.

Testing in Sandbox while using DC Local Server for Production

It is technically possible to have Plauti Server and DC Local Server installed on the same machine next to each other. However, each time you start Plauti Server, it will detect that DC Local Server is still installed and will show a message for this. 

Furthermore, and more importantly, if you have them both connected to the same Org or Environment, they will both try to pick up the same Deduplicate jobs. But if you connect Plauti Server to Sandbox and DC Local Server to Production this will not be a problem.

Of course you can also install Plauti Server on a different machine for testing purposes instead. Still, if Plauti Server and DC Local Server, although on different machines, are connected to the same Org or Environment, they will both try to fetch and run the same jobs. 

To install Plauti Server for testing purposes while keeping DC Local Server for Production on the same machine:

1. Copy the configuration files ('application.properties' in particular) as described in the first section of Uninstall DC Local or DC Local Server Mode. Do not uninstall DC Local Server yet.
2. Install Plauti Server as described in Install Plauti Desktop on Windows or Install Plauti Desktop on MacOS.
3. Open Plauti Server and connect it with your Sandbox Org or Test Environment as described in Getting Started with Plauti Server. Note that for some Salesforce Sandboxes you might need the ‘Custom Domain’ login option.
4. Configure the Plauti Deduplicate Settings the same way as your previous DC Local settings:
   • In the application.properties file you saved, find the Batch Profile at dcl.batch-profile. This corresponds with the 'CPU' setting in the System Resource Usage section of the Plauti Deduplicate Settings in Plauti Server.
     In addition, you can add a maximum memory to be used as well.
   • In DC Local Server, all jobs were run automatically. To replicate this, enable ‘Auto Run Jobs’ in Plauti Server for your Org or Environment.
5. For DC Local Server, the server where you installed DC Local Server Mode needed to be able to reach https://www.plauti.com/support//plautilocal.blob.core.windows.net. For Plauti Server this has changed to https://www.plauti.com/support//plautiapps.blob.core.windows.net. Update your server settings accordingly.
6. Test Plauti Server. 
   Once you're happy with how it performs:
7. Uninstall DC Local Server.
8. Add your Production Org or Environment as a second Connection in Plauti Server. If you don't want to see Sandbox jobs in Plauti Server anymore you can delete the Sandbox connection.
9. Update the Plauti Deduplicate Settings for the Production connection, such as Auto Run Jobs.

Troubleshooting

• Problem: when a Deduplicate job is detected, it starts automatically, but then fails.
  Answer: make sure DC Local Server has been uninstalled or at least its service is stopped, or if it is still up and running, make sure that DC Local Server and Plauti Server are connected to different Orgs or Environments. If Plauti Server has a Connection to the same Org or Environment as DC Local Server, Auto Run should be disabled for that connection in the Plauti Deduplicate Settings for Server.