Services
Service Architecture
-
BM-Core is BlueMind's core component. It serves a a single management center for data and business rules. It is the only component that accesses the database.
-
All functionalities are exposed as Web Services and can therefore be driven by other applications.
-
All components, whether internal or external, use Web Services. This is useful for limiting incoming and outgoing BlueMind Mail flows (which are restricted to Web Services flows and mail flows) and ensuring the use of consistent management rules whatever the point of entry of a modification.
Packages supplied with BlueMind
Packages are available in /var/spool/bluemind-pkgs/.
Aptitude (Debian/Ubuntu) and yum (RedHat) shell commands are used to search and list available and/or installed packages.
Services used by BlueMind
| Service BlueMind | Usage |
|---|---|
| bm-core | main service |
| bm-eas | syncing of mobile devices through the Exchange Active Sync protocol |
| bm-elasticsearch | indexing and search service |
| bm-iptables | local firewall |
| bm-keydb | Redis-compatible PubSub service |
| bm-lmtpd | lmtp (local mail transfer protocol) service |
| bm-mapi | communication with MAPI |
| bm-milter | manages e-mail flow rules (application of signatures and disclaimers, etc.) |
| bm-nginx | HTTP + IMAP server |
| bm-node | server communication and service maintenance |
| bm-pimp | adjusts BlueMind service configuration according to machine resources (RAM, CPU...) |
| bm-postgresql | BlueMind's main database, manages the postgresql service |
| bm-tika | detection and extraction of metadata and texts from documents |
| bm-webserver | web-based platform for access to applications and services |
| bm-ysnp | SMTP and IMAP authentication |
| postfix | e-mail service |
| telegraf | supervision and metrology tools |
Data used by BlueMind
Estimated performance and file size
For an estimate of the performance and volume of folders containing BlueMind data, visit Minimum disk performance.
Backup
The saved data are placed in the :
- /var/backups/bluemind
/etc
The files and directories found in /etc/ contain the configuration of the components BlueMind uses.
| File/directory | Content |
|---|---|
| bm | bm.ini, bm-node certificates and ssh keys |
| bm-node | rsync.excludes |
| bm-webmail | php5-fpm configuration for BlueMind and nginx-webmail.conf |
| keydb | KeyDB configuration |
| nginx | nginx configuration |
| php5 | php5 configuration |
| postfix | postfix configuration, including transport maps ⚠️ You can add extra postfix maps but under no circumstances should you remove or edit existing maps used by BlueMind. |
| postgresql | postgresql configuration |
/usr/share
Subfolders located in /usr/share/ contain web modules and applications. The data in these directories is installed by the BlueMind packages and must not be edited.
- bm-conf/logs: applicative logs default configuration (log4)
/var/spool
/var/spool/subdirectories contain the data used by BlueMind (excluding the data contained in the postgresql database):
| Directory | Content |
|---|---|
| bm-docs | BlueMind documents (user/resource photos) |
| bm-elasticsearch | ElasticSearch index |
| bm-hsm | archived emails |
| bm-filehosting | linked email attachments |
| cyrus/data | emails |
| postfix | postfix queues |
| bluemind-pkgs | BlueMind installation data - used during installation and as long as you don't have a subscription |
/var/lib
The data found in /var/lib/ must not be edited manually.
| Directory | Content |
|---|---|
| bm-ca | certification authority generated during installation |
| postgresql | postgresql database |
Logs
Logs are written into subdirectories of the /var/log/ directory:
| Directory | Content |
|---|---|
| bm | core logs |
| bm-elasticsearch | elasticsearch logs |
| bm-lmtpd | LMTP service logs |
| bm-mapi | mapi service logs |
| bm-node | node logs |
| bm-tika | Tika logs |
| bm-webserver | webserver logs |
| bm-webmail | webmail logs |
| bm-ysnp | YNSP logs |
| keydb | KeyDB logs |
For more information, please see Logs