Prerequisites
- A Linux or Windows server with the following installed:
- java
- tomcat
- Version 6, 7 and 8 are supported. However, we do not support an in place upgrade of Tomcat due to the changes in structure.
- mysql
- MySQL 5.5 and 5.6 are supported.
- If using Linux, the server must have a GUI (desktop), and one extra java class library from iEnterprises - please contact iEnterprises support for the extra class library.
- The Swift MEAP installer from iEnterprises (typically a zip file)
- If you do not have the Installer, and you are a license customer, please contact iEnterprises support.
- A .war file specific to your data source type, also from iEnterprises.
- If you do not have the war file, and you are a license customer, please contact iEnterprises support.
- If you want to use SSL (https), a self- or CA- signed SSL certificate.
...
A minimal installation only requires about 150 MB of disk space, however, log file size varies depends on your logging level and length of time you keep your logs. For a small installation, 1 GB of disk space is more than sufficient space for logs.
| Warning | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Note: Your firewall must be opened for users to access Swift MEAP. Please see more information in the Graphical Installer section. |
Before beginning the installation, you should confirm tomcat's JVM memory allocation. You may need to add entries to the catalina.sh or startup.sh file in Linux, or the Java options tab in the tomcat monitor properties in Windows. We suggest as a minimum allocation:
-Djavax.servlet.request.encoding=UTF-8
-Dfile.encoding=UTF-8
-Xmx1024m
-Xms2024m
-XX:PermSize=256m
-XX:MaxPermSize=1024m
-XX:NewSize=64m
Please see the tomcat documentation for further instructions on setting these parameters.
If you are installing on Windows, jump to Windows Installation
If you are installing on Linux, jump to Linux Installation
Log files for the installer are kept in the installer's directory under logs/ Should anything go wrong at any point, you may refer to the logs for further information.
...
Planning considerations
iEnterprise Mobile™ is very flexible, and may be installed on a great many different types of machines with many different options. This guide is intended as a reference for a basic installation. Furthermore, this guide assumes good familiarity with Windows/Linux commands.
Security
The server can be configured to use HTTP or HTTPS, it can use a single port for all communication or the adminstration console can be configured on a different port to the client (mobile device) users. Splitting ports allows administrators more control, they can restrict who can access the administration console and it does not need to be on a public URL. Network administrators who are familiar with networking filtering / port forwarding / network configuration may be required to alter these settings.
A VPN can also be used for communication. In such cases, access is dependent on the client device supporting the VPN. You will need to contact your VPN provider for client availablility. Users will be required to login to a separate VPN application on the client devices before opening the iEnterprise Mobile™ application.
Multiple servers
iEnterprise Mobile™ utilizes MySQL and Apache Tomcat. Each Tomcat instance can support multiple iEnterprise Mobile™ applications, so you can install multiple instances on the same physical machine / tomcat instance. However, doing so has some potential drawbacks:
- Each iEnterprise Mobile™ instance will have its own set of jobs running, potentially on different schedules. For example, we poll the data source for all changes since we last connected (usually every 10 minutes). If one instance is installed on a single physical server, it is one job reading/writing all changes to disk for all of its users. If you install a second / third / forth instance on the same machine you are multiplying the amount of disk I/O operations, as well as the amount of memory required to run separate jobs. If one iEnterprise Mobile™ console has a particulary heavy workload, all instances could be affected.
- If errors occur on one environment or an update is required to any one of the iEnterprise Mobile™ servers, a Tomcat restart is sometimes required. This is especially true if a server is being upgraded. Usually restart times are small, but it is a consideration that if one server is being upgraded and a restart is required, all instances will be offline for a short period. The client users will be unaffected as the device will queue requests until the server is available again.
- Risk of failure. If there is a hardware / operating system / networking issue and multiple servers are installed, potentially all users of all servers are affected.
Further reading
For specific information relating to hardware / software, please see the following sub pages:
| Child pages (Children Display) |
|---|