Configuring with MetaDefender Distributed Cluster
Starting from MetaDefender Kiosk 4.7.10, administrators can integrate with the MetaDefender Distributed Cluster (MDDC) (2.3.0 or later) to serve very large deployments while offering improved auto-scaling, high availability and fault tolerant capabilities for MetaDefender Core.
For instruction to setup MetaDefender Distributed Cluster, refer to MetaDefender Distributed Cluster
The following features are not supported in MetaDefeder Distributed Cluster 2.3.0
- Hash lookup feature (supported in MDDC 2.4.0)
- Manifest generation from Core (supported in MDDC 2.4.0)
- Kiosk gets stuck at processing when one of the Core workers has no license
- Logs may show message as 'MetaDefender Core' instead of 'MetaDefender Distributed Cluster'
Setting up MetaDefender Distributed Cluster with MetaDefender Kiosk consists of the following steps:
Detecting the MetaDefender Distributed Cluster server URL
MetaDefender Kiosk muse be able to reach the MDDC server URL
- Access the MetaDefender Kiosk Management Conosle at
http(s)://<ip or dns>:8009. You can also access the Kiosk Management Console using Windows Start > OPSWAT > MetaDefender Kiosk Management Console. - Click Configuration and enter your MetaDefender Distributed Cluster URL e.g
http(s)://<ip or dns>:8899
Authenticating the MDDC connection
You must authenticate your connection by obtaining an API key from the MetaDefender Distributed Cluster Management Console
- Access the MDDC Management Console
- Select User Management
- Click the desired user with an Administrator role and copy the contents of the
API keyfield. If an API key has not been previously generated click theGeneratelink and make sure to save changes. - Return to the MetaDefender Kiosk Management Console and click the
Configurationtab - Paste your MDDC API key value in the
API Keyfield
Associating workflows in Kiosk to workflows in MDDC
Refer to Selecting a Server to Process Files
