topology.RouteManager (NSP Network Functions Manager

topology
RouteManager

A route manager is used by an OSS application to store multiple managed routes. The OSS is then informed, via the OSSI event channel, of the changes to the paths of the managed routes.

A separate route manager must be created for each application. This allows for separate sets of managed routes for different applications. JMS events may be filtered by application.

The OSS application is responsible for creating the route manager using the regular generic.GenericObject.configureChildInstance method using the topology.TopologyManager singleton as the parent.

The route manager and its set of managed routes are persisted. The paths of the managed route are not persisted.

Inheritance Hierarchy
- ManagedObject
  - topology. RouteManager

Parent Hierarchy
- topology.TopologyManager
  - topology.RouteManager [tpgy-mgr:[application-${applicationName}]]

Children Hierarchy
- topology.RouteManager

Relationships
- many topology.RouteManagers may be direct children of one topology.TopologyManager (child-parent relationship)

public class RouteManager

Relative Name=[[application-${applicationName}]]
Displayed Name=Managed Route Client
configureChildInstanceWithResult() does not return children.
configureInstanceWithResult() does not return children.
findMultipleFilteredInstances() does not return children.

Properties
applicationName	The system-wide unique application name used to identify a specific OSS application. Only the characters a-z, A-Z, 0-9, and _ are allowed in the name. type=string access=read-create minimum=1 maximum=32 Mandatory on create Displayed(tab/group)=Application Name
managedRoutes	The set of `topology.RouteSet` that are currently being managed for this application. type=Set (topology.RouteKey) access=read-only