Jeppesen Distribution Manager Installation Instructions for Administrators
The Jeppesen Distribution Manager (JDM)
application is downloaded from the Jeppesen website and installed on a
customer's computer. The user will need
administrative privileges on their computer to install the JDM application and
application updates. The JDM application
requires the following administrative privileges:
·
Install
to Program Files folder
·
Install
drivers
·
Change
folder permissions
Users with insufficient privileges,
whether detected by the installer or imposed by the User Account Control/Group
policy settings, will not be able to install the software.
Once the JDM application has been successfully
installed, the user can access it via a shortcut placed on the computer's
desktop. The user must be connected to
the internet to login to the application for the first time. On the JDM login screen, the user must enter
the Username and Password provided by Jeppesen account services. If the user does not have internet
connectivity, the message in Figure 1 will pop up immediately.
Figure 1 Unable to
Connect
Once internet connectivity is verified,
the user can select Cancel on the
screen in Figure 1 and enter the Jeppesen Username and Password on the login
screen. If the user still cannot login
to the application, it might mean that the corporate firewall is blocking
access to the Jeppesen servers. If the
user selects to "Enter Proxy Settings" from Figure 1, the following
screen appears to capture the proxy information.
Figure 2 Proxy Settings
Another way to access the proxy settings
screen is from the main login screen (see Figure 3) or from the menu bar in the
upper left corner of the JDM login screen - JDM > Proxy Settings.
Figure
3 Main login screen
In the Proxy Host field, enter the IP
address for the proxy host, for example 134.215.98.97:9090. The JDM application does not read proxy
information that might be set up in a proxy auto-config (PAC) file configured
for your site. The user will need to
enter this information in manually. The
username and password for the proxy settings will most likely be the user's computer
login credentials. The JDM username and
password will not work in the proxy settings window. The user will only need to enter the proxy
information during the initial login for authentication, and it will be saved
for future logins. However, if the user
changes their password on the computer, the password will also need to be
changed in the proxy settings dialog.
Once the proxy settings have been
entered correctly, the user will be taken back to the JDM login screen. The user must enter their Jeppesen username
and password to view services and perform operations in the JDM application.
JDM uses https (port 443) for the
Jeppesen server connection. The redirect
through the proxy host will allow the connection to the Jeppesen server and the
Cloud server from within the JDM application.
The Amazon servers that host Jeppesen data on the Cloud utilize IP
addresses that change dynamically every time they are called. The
following addresses are used by the JDM client:
FUNCTION |
NEW
(as of 29 May 2019) |
PREVIOUS |
||
DOMAIN
NAME / URL |
IP
ADDRESS |
DOMAIN
NAME / URL |
IP
ADDRESS |
|
Application login, settings. |
https://jsum.jeppesen.com |
Amazon EC2 & Cloudfront (see note below) |
https://jsum.jeppesen.com |
169.143.11.151 |
Client installers, documents |
https:// jsumsweb.jeppesen.com |
|||
Database downloads (NavData,
Obstacles, SafeTaxi, Airport Directory, Basemap) |
https://jsumdata.jeppesen.com |
|||
Database downloads (terminal charts) |
|
|
||
Database downloads (terrain) |
|
NOTE-1 (Jeppesen 169.143.x.x addresses)
Jeppesen owns the entire 169.143.0.0/16 subnet range.
If your firewall is set up to allow/block based on IP address, you can allow
the entire 169.143.0.0/16 range to ensure that all Jeppesen addresses are
allowed.
NOTE-2 (Amazon Cloudfront,
EC2, & S3):
For those customers that reference specific IP
addresses when enabling Internet access, reference the URL below for a current
list of IP ranges for the service. Please note that these ranges will change
over time.
Tip: search for CLOUDFRONT, EC2 and S3 to find all relevant IP ranges
https://ip-ranges.amazonaws.com/ip-ranges.json
Recommended reference material:
·
"Allowing
AWS Storage Gateway Access Through Firewalls and Routers" - http://docs.aws.amazon.com/
·
"Determining
IP address ranges needed for *.amazon.com" - https://kb.meraki.com/