Configure Multiple Query Manipulation Servers
IDOL Data Admin uses QMS to manage your keywords and promotions for Search Optimizer. If you have more than one QMS, you can use IDOL Data Admin to manage multiple instances, by adding an additional configuration file called additionalIdolConfigurations.json
in the same directory as your IDOL Data Admin config.json
file.
The additionalIdolConfigurations.json
contains a configurations
array, which contains one configuration object for each QMS group that you want to include.
Each QMS group configuration must contain the properties in the following table.
Property | Type | Description |
---|---|---|
displayName
|
String | The display name to use for the QMS group in the IDOL Data Admin user interface. The IDOL Data Admin user interface shows this display name in a menu at the top of the window, which allows you to switch between your different QMS groups. |
qms
|
Object | The configuration object for the QMS, which defines the host, port, and other settings. This object contains the same properties and options as the qms object in your config.json file. |
agentstore
|
Object | The configuration object for the QMS Agentstore component for this QMS, which defines the host, port, and other settings. This object contains the same properties and options as the agentstore object in your config.json file. |
statsServer
|
Object | The configuration object for the Statistics Server for this QMS group, which defines the host, port, and other settings. This object contains the same properties and options as the statsServer object in your config.json file. |
You can also optionally include the properties in the following table.
Property | Type | Description |
---|---|---|
view
|
Object | The configuration object for the IDOL View Component to use for this QMS group, which defines the host, port, and other settings. This object contains the same properties and options as the view object in your config.json file. If you do not configure the view object, IDOL Data Admin uses the default View component defined in your main IDOL Data Admin configuration file. |
content
|
Object | The configuration object for the IDOL Content component for this QMS, which defines the host, port, and other settings. This object contains the same properties and options as the content object in your config.json file. If you do not configure the content object, IDOL Data Admin uses the default Content component defined in your main IDOL Data Admin configuration file. |
Example Configuration
The following JSON example provides an example configuration for one extra QMS group, in addition to the default QMS group defined in your config.json
.
{ "configurations" : [ { "displayName": "qms_1:16000", "qms": { "server": { "protocol": "HTTP", "host": "qms1.example.com", "port": 16000, "indexProtocol": "HTTP", "indexPort": null, "serviceProtocol": "HTTP", "servicePort": null }, "blacklist": "ISO_BLACKLIST", "typeAheadMode": "Index", "enabled": true }, "agentstore": { "enabled": true, "distributed": false, "dah": { "protocol": "HTTP", "host": "qms1.example.com", "port": 9160, "serviceProtocol": "HTTP", "servicePort": 9162 }, "dih": { "protocol": "HTTP", "host": "qms1.example.com", "port": 9170, "indexProtocol": "HTTP", "indexPort": 9171, "serviceProtocol": "HTTP", "servicePort": 9172 }, "standard": { "protocol": "HTTP", "host": "qms1.example.com", "port": 9250, "indexProtocol": "HTTP", "indexPort": 9251, "serviceProtocol": "HTTP", "servicePort": 9252 } }, "statsServer": { "protocol": "HTTP", "host": "qms1.example.com", "port": 19870, "productType": [ "IDOLPROXY", "STATS", "DAH" ], "enabled": true } } ] }