Juniper NETWORK AND SECURITY MANAGER 2010.3, Administration Manual

Page: 470 / 1016

Configuring Binary Data Objects
Binary data objects provide an efficient way of handling large binary files of configuration
data that are typical in Secure Access and Infranet Controller device configurations.
These files are the only configuration objects that are not imported when you import a
device configuration. Without this special handling, their size could overwhelm server
resources.
These files must be copied separately onto the client UI device, and configured as shared
objects. As a result, only the large binary files that you need to manage in NSM are
imported, and those files can be shared across multiple devices.
Binary data files handled in this way include:
• Custom sign-in access pages
•
Custom sign-in meeting pages
•
Antivirus live update files
• Antivirus live update patch files
• Endpoint Security Assessment Plug-in (ESAP) packages
•
Third-party host checker policies
•
Secure virtual workspace wallpaper images
• Hosted Java applets
• Custom Citrix client CAB files
See“Managing Large Binary Data Files (Secure Access and Infranet Controller Devices
Only)” on page 271 for information about where to find sources for these files, how to
upload them to NSM, and how to link to them from to include them in a device object
configuration.
Adding Binary Data Objects
Before creating the object in the Object Manager, you must copy the file from its source
to the file system of your client UI device:
1.
In the Configure panel of the NSM main navigation tree, select Object Manager >
Binary Data .
2.
Click the Add icon. In the New Binary Data dialog box, give the object a name, select
a color for the icon, add an optional comment, and select the binary file that the
object will reference by navigating to it in the client UI file system.
3.
Click OK to add the object to the Binary Data list in the Object Manager.
Copyright © 2010, Juniper Networks, Inc. 420
Network and Security Manager Administration Guide