MetaDefender Core
Pre-installation configuration
MetaDefender Core supports Ignition file to pre-define settings for the product installation. Following are relevant settings with values are supported for the ignition file while working in the Central Hub deployment:
eula=true[global]dbmode=2[dbserver]type=remotehost=<postgres-server-ip>port=<integer> user=<postgres-username>password=<postgres-password>[cache]host=<redis-server-ip>port=<redis-server-port>[nas]host=<nas-server-host>port=<integer> // NAS server port, usually 8888worker_count=<integer> // total number of internal worker, at least 4connection_key=<connection-key-to-nas>[broker]host=<rabbitmq-server-host>port=<integer> // RabbitMQ server port, 5672 by defaultuser=<rabbitmq-username>password=<rabbitmq-password>| Section | Key | Value type | Accepted values | Description |
|---|---|---|---|---|
| [global] | ||||
| dbmode | number | 2 | Must be 2 to indicate this MetaDefender Core is an instance in Central Hub deployment. | |
| [dbserver] | ||||
| type | string | remote | Must be remote to indicate that remote database is used. | |
| host | string | Remote PostgreSQL server address where MetaDefender Core connects to. | ||
| port | number | Remote PostgreSQL server port where MetaDefender Core connects to. | ||
| user | string | PostgreSQL main user's name which MetaDefender Core uses to login PostgreSQL server and setup database. Unicode characters are not supported. User privilege: Main PostgreSQL User | ||
| password | string | PostgreSQL main user's password which MetaDefender Core uses to login PostgreSQL server and setup database. Unicode characters are not supported. User privilege: Main PostgreSQL User | ||
| [cache] | ||||
| host | string | Redis caching server address where MetaDefender Core connects to. | ||
| port | number | Redis caching server port where MetaDefender Core connects to. | ||
| [nas] | ||||
| host | string | File storage server address where MetaDefender Core connects to. | ||
| port | number | File storage server port where MetaDefender Core connects to. | ||
| worker_count | number | 4 or above | Number of internal worker threads are used to communicate to that file storage server. | |
| connection_key | string | The same connection key which is used to set up File storage server | ||
| [broker] | ||||
| host | string | RabbitMQ server address where MetaDefender Core connects to. | ||
| port | number | RabbitMQ server port where MetaDefender Core connects to. | ||
| user | string | Username where MetaDefender Core uses to connect and login RabbitMQ | ||
| password | string | User password where MetaDefender Core uses to connect and login RabbitMQ |
Example:
eula=true[global]dbmode=2[dbserver]type=remotehost=192.168.1.100port=5432user=postgrespassword=admin[user]name=adminpassword=adminemail=admin@localapikey=ccccc[cache]host=192.168.1.101port=6379[nas]host=192.168.1.102port=8888worker_count=4connection_key=5f8214e3bba948f5a921d70d5aa2966f[broker]host=192.168.1.103port=5672user=adminpassword=adminPost-installation configuration
All settings related to Central Hub components could be found and modified at MetaDefender Core own configuration file (Linux) or MetaDefender Core registry key (Windows). For example:
[broker]host=10.40.50.95port=5672user=myuserpassword=mypass[cache]host=10.40.50.95port=6379[nas]host=10.40.50.95port=8888worker_count=4connection_key=ff78cb9061f0438b9b3415ca5466f7fb[global]dbmode=2instance_name=metadefender_corerestaddress=*restport=8008[logger]logfile=/var/log/ometascan/ometascan.logloglevel=infonginx_logfile=/var/log/ometascan/nginx-ometascan.log- Once finished with the configuration modification, restart MetaDefender Core service to take effect.