The messaging system The default set of message groups for each queue. Only used if a queues group list is unset (note: empty is not unset). Enable messaging queues defined as profile in queues. The profile names are the final queue names. Control the messaging interface. The default protocol is "scmp" but "scmps" (secure protocol) is used when valid SSL certificate and key are configured. Local bind address and port of the messaging system. 0.0.0.0:18180 accepts connections from all clients, 127.0.0.1:18180 only from localhost. The IP access control list for clients which are allowed to connect to the interface. SO_REUSEADDR socket option for the TCP listening socket. SSL encryption is used if key and certificate are configured. Additional local bind address and port of the messaging system in case SSL encryption is active. The IP access control list for clients which are allowed to connect to the interface. SO_REUSEADDR socket option for the TCP listening socket. Set the parameters for each messaging queue. The queues are used when listed in the "queues" parameter. Several queues can be used in parallel. For queues with without databases leave the processor parameters empty. Define the list of message groups added to the queue. If unset, then the defaultGroups will be used. A queue will always add the default group "STATUS_GROUP". This parameter overrides defaultGroups. The IP access control list for clients which are allowed to join the queue. The maximum size in bytes of a message to be accepted. Clients which send larger messages will be disconnected. The default is 1MB. List of plugins required by this queue. This is just a convenience parameter to improve configurations readability. The plugins can also be added to the global list of module plugins. Example: dbstore Interface name. For now, use "dbstore"to use a database. Use empty for testing or playbacks without a database. Define the database connection parameters. Selected the database driver to use. Database drivers are available through plugins. The default plugin is dbmysql which supports the MYSQL database server. It is activated with the core.plugins parameter. Set the database read connection which is reported to clients that connect to this server. If a remote setup should be implemented, ensure that the hostname is reachable from the remote computer. Set the database write connection which is private to scmaster. A separate write connection enables different permissions on the database level for scmaster and clients. If enabled, the plugin will check the database schema version and refuse to start if the version doesn't match the latest version. If disabled and the an object needs to be stored, which is incompatible with the database schema, this object is lost. Leave this option enabled unless you know exactly what are you doing and what the consequences are. The directory served by the http server at staticPath. The URL path at which html files and assets are available. All files under filebase will be served at this URL path. The URL path at which the broker websocket is available. Enable database storage. Enable/disable the database. If the database is not enabled, the processed data is not stored persistently. Leave this option enabled unless you know what you are doing. Database backend SeisComP supports different database backends. Select the one you want to use. Different backends require different additional packages to be installed on your host system. MySQL/MariaDB server. Create database If you already have a database and want to reuse it, you can skip this step. If you want to let setup create the database for you, check this option. MYSQL root password. To create the database root access to the database is required. Please enter the root password to the database server you are going to use. The server hostname will be entered in the next steps. Run as super user. Activate this option to run the database setup script with super user rights. For instance, some MariaDB installation do not allow root access per password and require privileged system access. Drop existing database. When a database with the same name exists already, should it be destroyed and recreated? If you say no here, an error will be raised if the database to be created already exists. Database name. Database name to use. If you want to avoid conflicts with existing databases or if you have multiple installations, change the default name. If you are unsure, keep the default. Database hostname. The hostname of the computer running the database server. In most cases it is this computer (localhost). This hostname is private and not published to any client connection to this computer. Database read-write user. The database username for read-write access to the database. This account will not be visible to clients connecting to your system unless read-only and read-write accounts are not separated. Database read-write password. The database user password for read-write access to the database. This account will not be visible to clients connecting to your system unless read-only and read-write accounts are not separated. Database public hostname. The hostname of the computer running the database server. In most cases, it is this computer (localhost). This hostname is sent to all connected clients who in turn will try to resolve it. If all modules run locally, you can leave the defaults. Database read-only user. The database user that will have read-only access to the database. This account will be visible to all clients connecting to your system. Database read-only password. The database user password for read-only access to the database. This password will be visible to all clients connecting to your system. PostgresSQL server version 9 or later. Create database If you already have a database and want to reuse it, you can skip this step. If you want to let setup create the database for you, check this option.<br><br> Note: By default, the PostgresSQL server do not allow to login with username and password. Due to this reason, the SeisComP scmaster module can establish a connection after database initialization. Please check the SeisComP documentation how to change the server configuration. Drop existing database. When a database with the same name exists already, should it be destroyed and recreated? If you say no here, an error will be raised if the database to be created already exists. Database name. Database name to use. If you want to avoid conflicts with existing databases, or if you have multiple installations, change the default name. If you are unsure, keep the default. Database hostname. The hostname of the computer running the database server. In most cases it is this computer (localhost). This hostname is private and not published to any client connection to this computer. Database read-write user. The database username for read-write access to the database. This account will not be visible to clients connecting to your system unless read-only and read-write accounts are not separated. Database read-write password. The database user password for read-write access to the database. This account will not be visible to clients connecting to your system unless read-only and read-write accounts are not separated. Database public hostname. The hostname of the computer running the database server. In most cases it is this computer (localhost). This hostname is sent to all connected clients who in turn will try to resolve it. If all modules run locally, you can leave the defaults. Database read-only user. The database user that will have read-only access to the database. This account will be visible to all clients connecting to your system. Database read-only password. The database user password for read-only access to the database. This password will be visible to all clients connecting to your system. SQLite3 database. Create database If you already have a database and want to reuse it, you can skip this step. If you want to let setup create the database for you, check this option. Override existing database file. When a database with the same name exists already, should it be overriden? If you say no here, an error will be raised if the database to be created already exists. Path to database file scmaster [options] generic#help generic#version generic#config-file generic#plugins generic#print-config-vars generic#validate-schema-params generic#dump-settings generic#daemon verbosity#verbosity verbosity#v verbosity#quiet verbosity#component verbosity#syslog verbosity#lockfile verbosity#console verbosity#debug verbosity#log-file verbosity#print-context verbosity#print-component verbosity#log-utc verbosity#trace The non-encrypted bind address. Format [ip:]port The encrypted bind address. Format: [ip:]port