Appendix D
Installation Information
& Technical
Requirements
1 of 7
Appendix D
Table of Contents:
Context................................................................................................. 3
The MJog Messaging System ................................................................ 3
MJog Host – MJog Service and Web Server........................................... 3
MJog Host – Local Administration Account ........................................... 4
Server URLs and Ports .......................................................................... 4
Proxy Authentication ............................................................................ 4
MJog Product Updates .......................................................................... 5
Installation and Ongoing Product Support ........................................... 5
Workstation Access to MJog ................................................................. 5
Text Sending - NHSmail ........................................................................ 6
Text Sending – MJog Premium Service ................................................. 6
NHSmail – POP and SMTP ..................................................................... 6
Data Protection .................................................................................... 7
2 of 7
Appendix D
MJOG INSTALLATION REQUIREMENTS
Context
This document describes the host software and hardware requirements for a
successful MJog installation. Some aspects will only apply in specific circumstances,
depending on network, security and custom configurations.
The MJog Deployment Team will assist in determining your exact requirements and
advise accordingly.
The MJog Messaging System
The MJog Messaging System consists of a number of Windows services (depending
on your technical environment and Clinical System); a self-contained web server
application and an SQL database.
The installation of all MJog related components will be performed on one machine
that acts as the MJog host computer. All client computers (workstations) access and
control MJog via a web browser across your internal network.
MJog Host – MJog Service and Web Server
The MJog services and self-contained web server run as Windows services on the
host computer and utilise either the SQLite or Microsoft SQL Server 2005 Express
database engines (installed with MJog). The database choice will depend on local
considerations and the MJog Deployment Team will advise accordingly. Either of
these choices will install alongside other SQL applications if needed and the
installation will automatically create the required ODBC data sources for MJog.
The host installation requirements are:
Windows Server:
o
Windows Server 2003 SP2 or above (all editions)
o
Windows Server 2008 (including R2)
Windows Workstation:
o
Windows 7 (32 and 64 Bit versions)
o
Windows 8 (all versions)
Internet access using port 80 and 443 (see Server URLs and Ports section
for further information)
Minimum 2GB RAM
Minimum free disk space of 10Gb (MJog can occupy up to 2GB depending on
local conditions)
3 of 7
Appendix D
Technical note:
If Windows firewall is used, an exception must be added on the local LAN for
port 80 to allow workstation access to the Web Server installed with MJog.
If McAfee AntiVirus is used, an exception may need to be added under 'Access
Protection / Prevent mass mailing worms from sending mail' for 'httpd.exe' to
allow MJog to send messages via NHS Mail.
MJog Host – Local Administrator Account
Both for the installation and ongoing support, it will be necessary for a user account
with local administration rights to be made available to the MJog Deployment and
Support Teams when required. The account name and password should be
entrusted to a full time user that can grant access to the MJog Support /
Development Team when needed.
Server URLs and Ports
For management, support and operational reasons we also connect automatically
with our own systems.
The MJog server URLs currently in use are:
http://www.mjog.com
http://www.mjog.net
https://www.mjog.net
http://hc1.mjog.net
https://hc1.mjog.net
http://hc3.mjog.net (Voice/Text Combined systems)
https://hc3.mjog.net (Voice/Text Combined systems)
We use the standard port numbers of 80 and 443 (http and https respectively). We
access many different URLs under these domains, so full access to these domains is
required.
Proxy Authentication
If you have not deployed proxy servers and user account authentication for proxy
server access, you should not need to consider this section. However, should proxy
servers and user account authentication be in use, this section deals with the issues
this can raise.
MJog runs on the host, by default, using the inbuilt Windows local service account,
which has no user access rights outside of that individual machine. When MJog tries
to communicate externally, the local service account cannot authenticate through
your proxy server. In order to resolve this, it will be necessary to create an account
that MJog can use to authenticate and grant MJog internet access. We enter these
4 of 7
Appendix D
account details into MJog, and each time MJog tries to gain access to the internet
via the proxy, these account details will be used to authenticate.
MJog Product Updates
Updates to the MJog Messaging System are also released through the domains
listed in the Server URLs and Ports section. All updates are issued as small EXE
or SQL statement files (text files with a file extension of SQL) that MJog then
automatically downloads and installs as required.
It is necessary for any proxy and firewall settings to allow these EXE and SQL files
to be downloaded by MJog (and any authentication accounts used by MJog), from
the server URLs listed in Server URLs and Ports.
We will never release software that has not been tested, and only release software
for the purposes of updating and maintaining our own products.
Installation and Ongoing Product Support
For both installation and ongoing product support it will be necessary to preapprove technical arrangements that allows remote access to the MJog host. Some
CCGs already have their own solution in place for third party suppliers and this can
be discussed with the MJog Team.
We have our own preferred web-based solution, Away From My Desk. This is a
commercial application that allows the remote user (i.e. a user at the Trust/PCT) to
invite us to connect to a PC for the purpose of Support or maintenance. This access
is granted on a per-use basis and is always under the control of the remote user at
the Trust. There is no way we can connect without the direct involvement of the
user each and every time.
We have purposefully chosen a product offering:
High levels of encryption (256bit)
An invitation based connection system
Web based access over port 80 and 443
A system already widely used within the NHS
We are already successfully using this proven solution in many Trusts and PCTs.
Workstation Access to MJog
All user access to MJog is via a web browser and can be accessed from any PC on
the same network. MJog will only have been product tested with Internet Explorer
7, 8 & 9, Chrome and Firefox 25 and above, though MJog uses industry standard
browser technology and should be compatible with other leading browsers.
5 of 7
Appendix D
The MJog solution provides user access control at application level to restrict access
to MJog and control user permissions once connected and logged in. Actions
undertaken by end users also form part of an internal audit log available to system
administrators.
Text Sending – NHSmail
In order to use MJog you will need an appropriate NHSmail account to be used
solely for the despatch of SMS messages via the HSCIC SMS gateway. This account
needs to be a standard NHSmail user account with its own username and password.
A generic mailbox cannot currently be used, as SMTP capability is not available for
generic accounts.
We would suggest an account name that is NOT specifically named to an individual
as ALL outbound messages will have the sender details appended to it - this is a
HSCIC controlled setting and we cannot change this. An address such as
YOURORGANISATION.text@nhs.net or YOURORGANISATION.mjog@nhs.net would
be ideal.
Please be advised that the NHSmail password will expire periodically. MJog has the
functionality to automatically update the password at set intervals, however, from
time to time an automatic change fails and you will need to ensure you change the
password in advance of expiration (using the NHSmail web site portal) and update
the MJog configuration with the new password. MJog provides an onscreen
reminder that a password will need to be updated after 90 days.
Currently text messages despatched via the NHSmail SMS gateway incur no direct
cost to the sending organisation.
Text Sending – Premium Service
Messages sent using the MJog Premium SMS Service are despatched via our SMS
gateways so there is no need for any additional accounts to be setup. All
configuration will be undertaken by the MJog Deployment Team at the time of
installation and forms part of your electronic account with us.
SMS messages despatched via our secure systems can be replied to by the recipient
at no additional cost to our customers. Reply messages are charged to the sender at
their normal message rate. Replies to a message sent from MJog are then routed
back to your account and displayed within your MJog system.
NHSmail – POP and SMTP
MJog sends messages to the NHSmail servers, from the MJog host, using SMTP and
collects message status notifications via POP3. MJog connects using the secure
ports and server addresses provided by HSCIC. As the MJog host is within N3,
secure access to the HSCIC SMTP and POP3 NHSmail servers is normally available
without interception.
6 of 7
Appendix D
Should access to HSCIC servers be restricted by CCG policy, we would need this
restriction lifting for the standard NHSmail server addresses and ports, though only
the MJog host system requires access, which can be achieved by means of a single
machine name / IP Address exception to the firewall / router configurations:
SMTP: send.nhs.net (TLS port 587)
POP3: pop,nhs.net (SSL port 995)
Data Protection
As with all messaging services, MJog requires at least the minimum information to
perform message delivery, but the content of all messages is entirely within the
discretion and control of each site. Minimal patient identifiable information (first
name, last name, date of birth, mobile/email/land line number and patient ID) is
held within the MJog database on the locally hosted MJog machine. MJog holds no
clinical information.
7 of 7