
W
EB
F
ILTER
A
PPENDICES
S
ECTION
A
PPENDIX
D
M86 S
ECURITY
U
SER
G
UIDE
497
Step 2: Choose a deployment host for updates
Decide where to host Mobile Client update files:
•
A Web server you maintain
•
Mobile Server Web Filter
Host MC file on your Web server
This choice is advantageous for environments with multiple
Mobile Server appliances, since update files need to be
copied to only one server instead of each Web Filter appli-
ance.
NOTES
: If you choose to host update packages on your own
Web server:
• The Web server’s URL must be specified in the Package
Configuration window. If this URL changes at any point in time,
before using the “new” server, you must first update the “old”
server with the package containing the “new” URL, so that
clients know where to get current updates. Thereafter, any
newer packages should be uploaded to the “new” server.
• The MIME types map may need to be modified in order to
support custom file extensions for .mcxml (text/xml) and .mccfg
(text/xml).
Host MC files on the Mobile Server (Web Filter)
This choice is convenient for hosting Mobile Client updates
since this Web Filter is already accessible by the Mobile
Client application. However, performance issues may arise
when a new version of the Mobile Client is available and is
being requested by multiple end user workstations simulta-
neously.
The MCU checks for Mobile Client updates after each
successful synchronization attempt. By default, synchroni-
zation attempts occur once per hour (unless you have modi-
fied the Mobile Server configuration to specify otherwise).
When a new Mobile Client version is detected, the MCU
immediately attempts to download it. Because the clients do