Catalogs

The Catalogs are central repositories of objects, and classes of objects, that you can use for managing traffic. You can store the following object types:

Some catalog types might be license dependent. See the Ivanti Web site (www.ivanti.com) for more information.

•Locations catalog: Contains location-based configuration objects used for Global Load Balancing (GLB) and the Traffic Manager's multi-site cluster management capability.

•DNS Server: Contains zonefiles and zone configurations used with the Traffic Manager's authoritative Domain Name Server (DNS) capability.

•GLB Services catalog: Contains GLB service configurations used by the Traffic Manager to load balance clients across different geographic locations.

•Service Discovery Plugins catalog: Contains scripts used by a pool to retrieve a remotely-autoscaled list of back-end nodes.

•Web Accelerator catalogs: Contains application scopes and profiles used by Ivanti Web Accelerator.

•Rules catalog: Contains TrafficScript and RuleBuilder rules.

•Java Extensions catalog: Contains Java Extensions and any supporting Java class files that the extensions require. These Java Extensions can be invoked from a TrafficScript rule.

•Monitors catalog: Stores health monitors you can use to check the correct operation of nodes in a pool.

•SSL catalogs: Contains SSL resources: server and client certificates, certificate authorities and certificate revocation lists.

•Authenticators catalog: Contains definitions of remote LDAP authentication services. These services can be accessed from TrafficScript to look up information about a user and to verify their password.

•Kerberos catalog: Contains configuration resources needed by the Traffic Manager to allow it to participate in Kerberos realms.

•SAML catalogs: Contains resources used by the Traffic Manager to participate in SAML-based single sign-on authentication.

•Service Protection classes: holds classes that define the policies and security measures used by the Traffic Manager to filter unwanted traffic.

•Session Persistence classes: Contains classes that manage session persistence information for client connections.

•Bandwidth classes: Contains bandwidth allocations that you can use to manage bandwidth usage.

•Service Level Monitoring classes: Contains classes that monitor node response time and conformance to agreed levels of service.

•Rate Shaping classes: Contains classes you can use to queue and rate-shape requests to impose maximum request rates.

•Cloud Credentials classes: Holds the information required to allow the Traffic Manager to communicate with cloud provider APIs.

•Extra files: Contains additional files and resources accessible from TrafficScript rules (using resource.get()), or used to provide error messages in pool configuration.

Virtual servers, pools and rules can each reference objects in the Catalog. If you edit an item in the catalog, the changes you make propagate to every service that uses the item.

To access the catalogs, click Catalogs in the top navigation bar. To edit or add to the items in a catalog, click the appropriate Edit link.

Each catalog type is described in more detail later in this document.