REVLY Communication Server Configuration
REVLY Communication Server provides a wizard to setup and configure all software required for your server. Before beginning the setup wizard ensure your server is up to date with all the latest software versions. Login as the root user and enter the following command:
# yum updateAfter your software is up to date. Enter the following command to start the REVLY Client as the root user:
# revlyThe REVLY Client will ask you to enter a password. Enter the root password you set when installing REVLY OS.
Password:
Connecting to 'umi://root@localhost:8123'.
Connected to the REVLY Server running on localhost.localdomain
This software is currently enabled for evaluation purposes only. The trial period will expire in 30 days. Please contact Maxwell Revly to continue using this product after the trial period has expired
Warning: Insecure connection.
Logged in as 'root'. (0)
revly>After logging in to REVLY as the root user, issue the following command to configure your server:
revly> setup communication serverOr use the abbreviation:
revly> setup commPlease answer the questions given by the wizard to setup your communication server. The answer options for multiple choice questions are in parentheses, “()”. The default options, if any, will begin with a capital letter. The default values for non-multiple choice questions are displayed in square brackets, “[]”. To use the default value press the Enter key.
This wizard will help you deploy your REVLY Communication Server.
Do you wish to continue? (Y,n)
: Y
Configuring the REVLY Communication Server.Step 1: SSL Keys and Certificates
The wizard will continue by asking questions used to create a self-signed security certificate for your server. The FQDN entered here does not have to be resolved locally and can begin with “*.”. If your server is to host mail and instant messaging services for example.com you may wish to enter “*.example.com”. The generated certificate will then be valid for any sub-domain of example.com that resolves to the server's IP address such as example.com, mail.example.com, chat.example.com, etc.
Configure SSL Keys and Certificates (OpenSSL)
Configuring SSL. Values entered below will be used to generate configuration files for ssl certificates.
Please answer all questions. You may press the 'ENTER' key to accept default values (, in brackets []).
What is the fqdn for the SSL certificate? Wild cards (*) are accepted. [localhost]
ssl host: *.example.com
What is the country (2 letter code) for this server? [US]
ssl country: US
What is the State or Province Name (full name) for this server? [LA]
ssl state: Louisiana
What is the Locality Name (eg. city) for this server? [New Orleans]
ssl city: New Orleans
What is the Organization (eg. company) for this server? [Maxwell Worthington, LLC.]
ssl organization: Maxwell Worthington, LLC.
What is the Organizational Unit Name (eg. section) for this server? [REVLY]
ssl unit: REVLY
What is the email address of a contact for this server? [postmaster@example.com]
ssl email: postmaster@example.com
Saving Configuration.Step 2: Configure LDAP Server
The wizard will continue by asking questions used to setup LDAP services on this server. Except for the password, the default values should be used to create a standard installation. Using the default password will leave your server in an insecure state.
Configure LDAP Server (OpenLDAP)
Configuring LDAP. Values entered below will be used to generate configuration files for OpenLDAP.
What is the LDAP Suffix for this installation? [revly]
ldap suffix: revly
What is the LDAP User (RootDN) for this installation? [Manager]
ldap user: Manager
What is the LDAP Password (RootPW) for this installation? [********]
Enter new password:
Retype new password:
Saving Configuration.Step 3: Configure Database Server
The wizard will continue by asking questions used to setup database services on your server. Only disallow remote access if you are using “localhost” as the FQDN of your server. You may choose to re-use a previous password. Using the default password will leave your server in an insecure state.
Configure Database Server (MariaDB)
Configuring Database. Values entered below will be used to generate configuration files for MariaDB.
What is the MariaDB Root Password for this installation? [********]
Enter new password:
Retype new password:
Saving Configuration.Step 4: Configure Email Server
The wizard will continue by asking questions used to setup mail services on your server. The default values should be used to create a standard installation.
Configure Email Server (Postfix/Dovecot/Amavisd//ClamAV/Spamassisan)
Configuring Email. Values entered below will be used to generate configuration files for Postfix and Dovecot.
What is the hostname for this installation? [localhost]
email host: mail.example.com
Saving Configuration.Step 5: Configure Groupware Server
The wizard will continue by asking questions used to setup SOGo groupware services on your server. Except for the password, the default values should be used to create a standard installation. You may choose to re-use a previous password. Using the default password will leave your server in an insecure state.
Configure Groupware Server (SOGo)
Configuring SOGo. Values entered below will be used to generate configuration files for SOGo.
What is the database name used by the SOGo Groupware server for this installation? [sogo]
sogo database: sogo
What is the database user used by the SOGo Groupware server for this installation? [sogo]
sogo user: sogo
What is the database password used by the SOGo Groupware server for this installation? [********]
Enter new password:
Retype new password:
Saving Configuration.The wizard will now begin to configure the software used by REVLY Communication Server. This process does not require any further user intervention and will complete in approximately 5 minutes. Below is sample output from the setup process:
Applying REVLY Communication Server configurations.
Applying SSL configuration.
Generating private SSL key and certificate signing request.
Generating a self-signed SSL certificate.
Generating a self-signed SSL certificate for Ejabberd.
Ensuring Apache is running.
Ensuring Apache will startup at boot.
Generating Apache config files
Applying Apache configuration.
Ensuring OpenLDAP is running.
Ensuring OpenLDAP will startup at boot.
Applying LDAP configuration.
Ensuring MariaDB is running.
Ensuring MariaDB will startup at boot.
Applying Database configuration.
Creating email system group.
Creating the system group 'vmail'
Creating email system user.
Creating the system user 'vmail'
Creating mailstore directory.
Setting mailstore permissions.
Applying Postfix (SMTP) configuration.
Insuring Postfix is running.
Insuring Postfix will startup at boot.
Generating Postfix configuration files.
Restarting Postfix
Applying Dovecot (IMAP/POP3) configuration.
Insuring Dovecot is running.
Insuring Dovecot will startup at boot.
Generating Dovecot configuration files.
Reloading Dovecot
Applying Amavisd (AV/SPAM Filter) configuration.
Ensuring Amavisd is running.
Ensuring Amavisd will startup at boot.
Generating Amavisd configuration files.
Reloading Amavisd
Applying ClamAV (Anti-Virus) configuration.
Ensuring Clamd.Amavisd is running.
Ensuring Clamd.Amavisd will startup at boot.
Applying SpamAssassin (Anti-Spam) configuration.
Ensuring SpamAssassin is running.
Ensuring SpamAssassin will startup at boot.
Insuring SOGo is running.
Insuring SOGo will startup at boot.
Creating SOGo database and user.
Generating SOGo config files
Loading Apache configuration.
Applying Memcache configuration.
Ensuring Memcache is running.
Ensuring Memcache will startup at boot.
Restarting Memcache.
Restarting SOGo Insuring Ejabberd is running.
Insuring Ejabberd will startup at boot.
Generating Ejabberd config files
Restarting Ejabberd
REVLY Communcation Server setup complete (0)
revly>