In the documentation for Configuring a Sitecore Processing server it's mentioned that,
You can configure a processing server in much the same way as you configure a content delivery or content management server.
Basically, you need to review settings which identify the Instance uniquely which helps in EventQueue and similar stuff when setting up a cluster of Sitecore servers pointing to same SQL database.
One such setting which I know already is
<setting name="InstanceName" value="" />. The default value of this setting is empty so Sitecore will take Computer Name when the value is empty.
Also, few not to miss recommendations from above link - when setting up a cluster of Processing servers.
Application initialization or the appropriate module (IIS 7.5), so you can successfully start Sitecore after you recycle the application pool. If you do not do this, Sitecore will not be launched and its application pool may shut down due to inactivity.
- Synchronize all servers to a single reliable time source for example
Network Time Protocol (NTP)
Update: For correct settings for
processing or aggregation instances or for
Sitecore.Analytics.Processing.Aggregation.ProcessingPools.config, you can download the correct excel files, which goes with your Sitecore version, from here - Configure a processing server.
If it helps, to make your task easy there are some PowerShell scripts to configure server role (like cd, cm, processing, aggregation, reporting, etc) i.e. enabling/disabling
.config files posted on this SSO question here. However configuring settings within a
.config file is a manual effort in my knowledge.