Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Table of Contents
Overview ..................................................................................................................................................... 2
Introduction ............................................................................................................................................................................ 2
System Requirements ............................................................................................................................................................. 2
Preparation ............................................................................................................................................................................. 2
Software Manifest................................................................................................................................................................... 3
Overview
An overview of the MMC installation process
Introduction
This document describes how to install the Mobolize Management Console (MMC). The MMC is a web
application running on an Apache Tomcat 7.0 application server and utilizing MySQL 5.5 as its database.
Although the MMC is a Servlet based application it has not been certified to run on other Servlet 2.4 compliant
application servers such as Red Hat JBoss, IBM WebSphere or Oracle GlassFish. Furthermore, the MMC is
currently designed to use MySQL as its database and is not currently compatible with Oracle or Microsoft
SQLServer. The MMC also includes a reporting sub-application that is packaged as a separate application but is
only usable via the MMC.
System Requirements
Table 1: MMC system requirements
Item
Operating System
Required Software
Minimum configuration
Description
Multiple platforms supported:
Linux: any 2.6-based distribution
Windows: any Server version >= 2003
Java (6, 7 or later)
Apache Tomcat (7.0.x)
MySQL (5.5 or later)
Per 5000 clients:
CPU: 2 GHz
RAM: 4 GBs
Disk: 100 GBs
Preparation
Prior to any installation tasks, you must determine the following details:
Hostname and port This is the location by which administrators will browse to the MMC and by
which clients will connect to and communicate with the MMC. This hostname and port may need to be
given to your Mobolize representative so that client software downloads are automatically homed to
your MMC installation instead of the defaulting to the Mobolize cloud-hosted MMC; otherwise, the
hostname and port can be explicitly configured via the Mobolize YML configuration file.
Connection mode Access to the MMC may be encrypted via SSL. Encrypted communication is safer
but requires additional configuration and may require the purchase of an SSL certificate. Common
methods of implementing SSL are:
o Configuring Tomcat to directly encrypt communications using SSL
A certificate will be installed onto the server and Tomcat configured to use it
o Configuring a proxy to terminate SSL connections on behalf of Tomcat
A certificate will be installed onto a proxy that will forward connections to Tomcat.
If the certificate is self-signed or not purchased from an internationally recognized entity, the
certificate will have to be configured on all clients in addition to being configured on the server.
MOBOLIZE ON-PREMISE MANAGEMENT CONSOLE 2
Proprietary and Confidential
Database (MySQL) user-level account information If you have a pre-existing MySQL installation, you
or your database administrator (DBA) must provision the schema and database accounts to be used
by the MMC and its reporting sub-application. If you are installing MySQL for the first time, a script is
provided to assist in performing these tasks.
Mobolize systems The MMC may optionally connect to external systems hosted by Mobolize. You
can get this information from your Mobolize representative.
o Mobolize License Server URL This will be used by the MMC to connect to the Mobolize
license server to retrieve your licenses purchased from Mobolize.
o Mobolize Download Server URL This will be used by the MMC and clients for software
downloads and new version updates.
o SMTP (Email server) information This will be the email account the MMC uses to send email
alerts.
Software Manifest
The following software will be required for the installation. In some cases you may have the software already
installed or provided for you by your own IT department.
MySQL 5.5
Install Options
Select Full install when prompted..
Optional: install MySQL Workbench
o The default options are sufficient
Configuration
Choose the type Server Machine
Choose the usage Transactional Database
Choose connection setting Online Transaction Processing (OLTP)
The account created at installation time is the account used to administer the overall database, which
will be different than the user used by the MMC to connect to the database.
Validation
To validate the MySQL server installation, you can use MySQL Workbench to connect to it to confirm it is up
and running.
Windows Start Menu, clicking on the Java tab and entering 1024 or higher into the
Maximum Memory Pool field.
HTTP and Non-SSL / Un-encrypted Network Configuration or Removal
o The default Tomcat installation listens for connection requests on port 8080. You can continue
to allow connections on this port, which is non-SSL/un-encrypted, or change it to port 80, which
is the default port for such connections. To do so, edit <tomcat>/conf/server.xml:
Find a section that looks like and change 8080 to 80:
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" />
o If you will be using SSL, you can disallow connections to this port by removing the setting by
removing the entire <Connector/> line.
HTTPS and SSL / Encrypted Network Configuration
o To configure Tomcat for direct SSL termination, refer to these instructions:
http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html
o If a proxy is used to terminate SSL, consult the documentation for your proxy
Optional: Consult the documentation for RemoteIPValve to forward client IP addresses
from a proxy to Tomcat. http://tomcat.apache.org/tomcat-7.0doc/api/org/apache/catalina/valves/RemoteIpValve.html
Extra Information
o You will need to restart Tomcat to recognize any new, removed or changed settings
o You may need to add an inbound firewall rule to allow access to the ports you have configured.