Table of Contents
Advertisement
API
1 2
The following sections contain more information:
Section 12.1, "Overview," on page 283
Section 12.2, "Setting Novell ZENworks Network Access Control Properties," on page 284
Section 12.3, "Setting Firewall Rules," on page 285
Section 12.4, "Novell ZENworks Network Access Control Events Generated," on page 285
Section 12.5, "Novell ZENworks Network Access Control Requests Supported," on page 289
12.1 Overview
The Novell ZENworks Network Access Control Application Programming Interface (API) is based
on the Java Message Service (JMS). Novell ZENworks Network Access Control ships with version
3.1 of the
ActiveMQ JMS provider
JMS.
Novell ZENworks Network Access Control API communication is illustrated in
page
284, where:
JMS Message Bus — Novell ZENworks Network Access Control ships with ActiveMQ Java
Messanging Service (JMS).
XML file — This Extensible Markup Language (XML) file is created by you and contains one
or more requests.
JMS Event Receiver — An external program that subscribes (listens) to topics and can take
action base on the information received.
JMS Requestor — An external program that makes requests of Novell ZENworks Network
Access Control.
Script — A script that can be invoked when an event occurs.
JJS — A proprietary messaging framework that is used for communication between the MS
and ESs and for intra-cluster communication (ES-to-ES).
The JMS bus is used to send requests (such as test endpoints, change access status, and set
configuration properties that cannot be set via the Novell ZENworks Network Access Control user
interface), and to publish events (such as test results and endpoint status change) to external third
parties.
(http://activemq.apache.org/), an open source implementation of
12
Figure 12-1 on
API
283
Advertisement
Table of Contents
