Table of Contents
Advertisement
Network and Security Manager Administration Guide
Configuring Binary Data Objects
416
Click New. The New - Rule window appears.
Use the up/down arrow to specify an ID for the rule.
Add a comment for the rule.
Click Deny in the Action field.
Select a source address in the Source tab.
Select a destination address in the Destination tab.
Select FTP in the Service tab.
Select the integer IDs that you created in the Custom Policy Field object in the
Options tab.
Click OK.
4.
When you create the extranet device in NSM, bind the policy to the appropriate interface
and specify the script you want to perform the required update actions. When you update
the device, NSM invokes the script. Any XML output appears in the Job Information
window.
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 273 for information about where to find sources for these files, how to
Copyright © 2010, Juniper Networks, Inc.
Advertisement
Table of Contents
