In-worker service configuration

In-worker service configurations are controlled through properties. Each in-worker service type has several properties that define its behavior and options, and each property is prefixed by the service type. The following prefixes are available:

• InWorkerService.dis - for the Data Import Server in-worker service
• InWorkerService.disScript - for the Data Import Server with Script in-worker service
• InWorkerService.las - for the Log Aggregator Service in-worker service
• InWorkerService.ltds - for the Local Table Data Service in-worker service
• InWorkerService.tdcp - for the Table Data Cache Proxy in-worker service
• InWorkerService.tailer - for the Tailer in-worker service

Most of these properties should not be changed, but the following options may be of interest to administrators.

• <prefix>.context.<name> - This allows additional configuration contexts to be added to the available options. These are fully-specified contexts from the property files. To add further context options, simply add a newly-named property. For example, the tailer includes:
  • InWorkerService.tailer.context.query=service.name=tailer1_query
  • InWorkerService.tailer.context.merge=service.name=tailer1_merge
• <prefix>.allowedGroups - This specifies the list of ACL groups for which this service is available. Most in-worker services are only available to superusers, but an administrator may wish to specify an additional administration group such as iris-service-administrators. The following example would add this to the DIS service allowed groups:
  • InWorkerService.dis.allowedGroups=iris-superusers,iris-service-administrators
• <prefix>.dbServerClasses - This specifies the server classes allowed to run the query. Most in-worker services run on either a query server or a merge server, but the tailer can run on either:
  • InWorkerService.tailer.dbServerClasses=Query,Merge