The Network Processor assembles an abstract service level model for the device, called the Service Model. For each device affected, if the device is managed by a Network Processor, the Policy Server sends the device-specific changes to the Network Processor. The Policy Server takes user input and computes all its effects on the modeled network. If you have a device type/OS combination that is not present in file MIPSA_registry.xml, you must create a new cartridge registry file, as outlined in "Creating or Editing a Cartridge Registry File" or "Creating or Editing a Cartridge Registry File - Juniper Example".
When a transaction arrives, the Network Processor looks in the cartridge registry file ( MIPSA_registry.xml) and selects a capabilities file based on the supported device type and OS. The Cartridge registry maps device type/OS combinations to capabilities files. The output is the CLI, the set of commands specific to the target device type. It governs the structure of the Device model.Ī command generation (Java or XQuery script). A capabilities file contains:Ī service model transformation (Java or XQuery script).Ī device model schema definition (XML Schema). For more information see, "Capabilities and Options". It is applicable to device/OS combinations with identical CLI behavior. It may be composed of multiple capabilities units.Ī Capabilities file defines an instance of specific, concrete, complete behavior (including command syntax) for a service or a set of services. It contains a set of data elements that defines the complete device state.Ī Cartridge is a vendor-specific implementation of a set of services for a given family of device types running the same operating system. It resembles the information model configured by the user.Ī Device model is a device-specific XML document derived from the service model. The main components are described as follows:Ī Network Processor is a processing component that performs the conversion of user changes into a set of CLI commands for delivery to devices.Ī Service model is a device-independent representation of service objects and their relationships. The Component Manager is responsible for starting, stopping, and restarting the Network Processor, and for reporting component failures.įigure 7-3 Network Processor Data Flowchart from the Interface to the Target Deviceĭescription of ''Figure 7-3 Network Processor Data Flowchart from the Interface to the Target Device'' The Network Processor runs under the control of the Component Manager. The Network Processor provides multi-vendor capability, with vendor-specific pieces delivered as cartridges. The Network Processor and cartridge reduces the system restart time, and improves overall system stability. Multiple Network Processors can each load an instance of the same cartridge, thereby allowing to scale up to a higher number of managed devices.
#Backup exec discovering devices Activator#
You can develop new cartridges and configuration policies using the IP Service Activator SDK.
The Network Processor component allows the introduction of service support on new device types or variants of existing types. Supporting an enhanced stateful activation model, the Network Processor uses a persistent store in the Oracle Database to keep a record of the details and state of services deployed on devices.
The Network Processor uses Activation Cartridges that include XML-based vendor-specific and service-specific definitions for a number of device types.