Worker Configuration
By default, Integration Manager fully embeds the Job Execution Service within the application. This is meant to facilitate a quick start experience. For distributed and production environments, it is likely you will want more control over how the services are deployed, including, but not limited to:
• Externalizing the Worker Service and Messaging Broker
• Running multiple Workers for additional workload bandwidth
• Running multiple Workers to support workload segregation
Externalizing the Worker Service and Messaging Broker
For convenience, a set of distributed services is already installed with Integration Manager. You may enable the basic externalized configuration by performing the following steps:
1. Go to the services console and **Stop** Actian Integration Manager.
2. Go to ../Actian/IntegrationManager/conf and open application.properties.
3. Find the entry named "worker.embedded" and change the value to "false".
4. Go back to the services console:
a. **Start** Actian Messaging Broker.
b. **Start** Actian DataCloud Worker.
c. **Start** Actian Integration Manager.
To revert to the fully embedded configuration
1. Go to the services console:
a. **Stop** Actian Messaging Broker.
b. **Stop** Actian DataCloud Worker.
c. **Stop** Actian Integration Manager.
2. Go to ../Actian/IntegrationManager/conf and open application.properties.
3. Find the entry named "worker.embedded" and change the value to "true".
4. Go back to the services console and **Start** Actian Integration Manager.
Running Multiple Workers for Additional Workload Bandwidth
If you are using an externalized configuration, you can also run multiple Workers on different machines with network connectivity to the messaging broker. When multiple Workers are configured, they will compete for any work on the default job queue. You can enable this by performing the following steps:
1. Download and install the Worker Service on the desired machine or VM.
2. Go to ../Actian/IntegrationManager/conf and open application.properties.
3. Find the entry named "queue.host" and change the value from "localhost" to the IP address or fully qualified domain name of the machine hosting the messaging broker.
4. Go to the services console and **Start** Actian DataCloud Worker.
Running Multiple Workers to Support Workload Segregation
In some cases, you may want to segregate workloads based on workload type or customer type, for example, short versus long running integration jobs. You can segregate Workloads by creating multiple Destinations, which are configurations for Worker Pools. You can enable this by performing the following steps:
1. Create a new Destination record within your configuration database.
2. Download and install the Worker Service on the desired machine or VM.
3. Go to ../Actian/IntegrationManager/conf and open application.properties.
4. Find the entry named "queue.host" and change the value from "localhost" to the IP address or fully qualified domain name of the machine hosting the messaging broker.
5. Find the entry named "worker.destinationId" and set the value to the ID field of the Destination record you created in Step 1.
6. Go to the services console and **Start** Actian DataCloud Worker.