Pre-installation checklist

Servers

Operating system

OpenSuse 42

Amazon Linux

▢ Fedora 26

▢ Windows Server 2016

The product is tested on OpenSuse 42 but should run on most modern Linux versions. It uses sysvinit rather than systemd for startup and shutdown.

On Linux, Jiglu is distributed as RPMs so you will need to be able to install these. We don't currently provide Debian packages but installing Debian's rpm package will allow Jiglu to be installed.

Windows Server is available only with paid licences.

Application server

Tomcat 7.0+

Tomcat is our preferred web application container. Other application servers are available on request with paid licences.

Mail server

Sendmail

▢ Postfix

Apache James

For Linux we support both Sendmail and Postfix as MTAs, with a preference for Sendmail.

For Windows we support Apache James as a local MTA to transfer messages into Jiglu.

Database

PostgreSQL 9.0+

▢ Oracle 11g

▢ SQL Server 2016

PostgreSQL will be suitable for most small to medium installations. Oracle and SQL Server are only available with paid licences.

 Clients

Web browsers

▢ Internet Explorer 11

▢ Microsoft Edge 12+

▢ Google Chrome

▢ Firefox

▢ Apple Safari 9+

▢ Opera 36+

Jiglu will work with all modern browsers supporting HTML 5. In earlier browsers it will try and degrade gracefully but some features may not be available.

Mail readers

▢ Outlook

▢ Thunderbird

▢ Apple Mail

▢ GMail

▢ Hotmail

▢ Yahoo Mail

Jiglu supports all mail readers conforming to current Internet standards. XHTML 1.0 support is necessary when a user has chosen to receive HTML messages from the system.

Integration

DNS

▢ Physical / virtual machine address (A)

▢ Jiglu webapp address (A)

Jiglu mail domain (MX)

The machine on which Jiglu runs will need a static IP address. There will need to be a domain name to access the web application, which will resolve to the server IP address. For best practice the machine domain name and the web application domain name should not be the same.

A domain name is required for mail, either resolving to the server itself if accessible externally or to another host with an MTA that knows how to forward mail to the machine with Jiglu.

Routing

▢ Routing to physical / virtual machine

Routing may need to be changed to ensure that users can access the web application and the MTA can receive messages.

Incoming mail

▢ Routed via smart host

▢ Own mail server

Outgoing mail

▢ Routed via smart host

▢ Own distribution

The system will need to be able to receive incoming mail. The simplest way to deal with this is to have an MTA on the same machine as Jiglu. If the machine is behind a firewall, then routing will be required, either by opening up the firewall for the MTA port or forwarding on messages at another MTA that is accessible externally.

To send out mail to users, the system will need an MTA to connect to. It can either use the MTA running on the same machine or an external ‘smart host’ (an MTA that knows how to relay mail to anywhere), for which the domain name will need to be known. Credentials may be needed for this host.

LDAP

▢ LDAP server address and port

▢ User and password to connect

▢ Repository context

▢ Class holding user data

▢ Field mappings

If the system is to use an external LDAP repository (such as Microsoft Active Directory or OpenLDAP) to authenticate users then Jiglu will need to know where the LDAP repository is, who to connect to it as and where in the repository it can find the user information it needs.

To map data from the repository into the system, Jiglu will need to know the class used to represent users, and which fields can be used for username, email address, given name and family name.

Written by Stephen Hebditch. Published on .
5.0.0
What needs to be considered and set up prior to Jiglu installation.