6 About Design Studio Construction

This chapter provides information on the composition of the Oracle Communications Network Integrity MSS Integration cartridge from the Oracle Communications Design Studio perspective.

Model Collections

The MSS Integration cartridge models imported data to the TMF814 Generic specification. See Network Integrity Optical TMF814 CORBA Cartridge Guide for more information.

Actions

The following tables outline the Design Studio construction of the MSS Integration cartridge and associated components:

Table 6-1 Actions Design Studio Construction

Action Result Category Scan Parameter Groups Processors

Import from MSS

Device

See Table 6-2

See Table 6-3

Detect Equipment Discrepancies

Device

N/A

See Table 6-4

MSS Circuit Discrepancy Detection

Circuit

N/A

See Table 6-5

Resolve in MSS

Device

N/A

See Table 6-6


Table 6-2 Cartridge Scan Parameter Groups Design Studio Construction

Characteristic Name Type Description UI Label

NetworkLocation

Text box

The network location. Enter either the common language location identifier (CLLI) code, or the coded location from MSS.

Network Location

Status

Drop down

List: All, Installed equipment, Equipment under maintenance

The status of the root equipment.

Status

NodeNameQualifier

Drop down

Works in combination with the NodeName parameter to filter the imported nodes by name and qualifier.

Node Name Qualifier

NodeName

Text box

The device name or a list of device names.

Node Name

NodeId

Text box

The node ID or a list of node IDs.

Node Id

Scope

Drop down

List:

  • Equipment, STM Links, and Circuits

  • Equipment and STM Links only

  • Equipment only

The scope of data to import from MSS.

Scope

RunMSSExtract

Drop down

Boolean to determine whether to run MSS incremental extraction procedure before the scan run.

Run MSS Extract


Table 6-3 Import Processors Design Studio Construction

Processor Name Variable

Equipment DAOs Initializer

Input: N/A

Output:

  • daoLocator

    The data access object (DAO) locator class that performs data lookup on the views.

Page Initializer

Input: daoLocator

Output:

  • pageCountList

    An iterable list object for each page created.

  • pageSize

    The size of each page.

  • filterString

    The configurations entered in the Network Integrity UI for filtering the imported data.

Page Creator

Input:

  • daoLocator, pageSize, filterString

  • pageIndex

    An instance of the pageCountList iterable object.

Output:

  • nodeNameList

    A list of imported node names corresponding to the filtered UI configurations.

Node Collector

Input: daoLocator, nodeNameList

Output:

  • nodesMapByNodeName

    A map of node names to a list of corresponding root equipment.

  • nodeSet

    The list of node names.

Device Modeler

Input:

  • nodesMapByNodeName

  • node

    An entry from the nodeSet object.

Output:

  • collectedPortsUnderNode

    A list of ports belonging to the current node object.

  • logicalDevice

    A modeled logical device.

  • physicalDevice

    A modeled physical device.

  • rootEquipments

    A list of root equipment objects for the current node object.

Equipment Hierarchy Collector

Input:

  • daoLocator, logicalDevice, physicalDevice, nodesMapByNodeName

  • rootEquipment

    An entry from the current rootEquipments object.

Output:

  • cardsToPortsMap

    A list mapping ports to their corresponding cards.

  • equipmentHierarchyDetails

    The equipment hierarchy details for the imported data.

Equipment Hierarchy Modeler

Input: cardsToPortsMap, equipmentHierarchyDetails, rootEquipment, collectedPortsUnderNode, physicalDevice, logicalDevice

Output: N/A

Hierarchy Persister

Input: logicalDevice, physicalDevice

Output: N/A

STM Link Discoverer

Input: collectedPortsUnderNode, daoLocator, physicalDevice

Output:

  • stmList

    A complete list of synchronous transport modules (STMs).

VC4 Circuit Discoverer

Input: stmList, daoLocator, physicalDevice

Output:

  • igForCircuits

    The circuits inventory group.

  • vc4sForLops

    A list of VC4 circuits from which lower order pipes (LOPs) are collected.

VC3 VC12 LOP Discoverer

Input: daoLocator, igForCircuits, PhysicalDevice, vc4sForLops

Output: N/A


Table 6-4 Equipment Discrepancy Detection Processors Design Studio Construction

Processor Name Variable

Equipment Filters Initializer

Input: N/A

Output: N/A

Discrepancy Detector

This processor is imported from the NetworkIntegritySDK cartridge project.

Discrepancy Filter

Input: N/A

Output: N/A

Check Auto Resolution Selected

This processor is imported from the NetworkIntegritySDK cartridge project.

MSS Auto Resolve Selected Discrepancies

Input: autoResolutionManager

Output: N/A

Identify Auto Resolving Discrepancies

This processor is imported from the NetworkIntegritySDK cartridge project.

Prepare Resolving Discrepancies

This processor is imported from the NetworkIntegritySDK cartridge project.


Table 6-5 Circuit Discrepancy Detection Processors Design Studio Construction

Processor Name Variable

Circuit Discrepancy Name Filter Initializer

Input: N/A

Output: isTopLevel

Missing Entity Filter Initializer

Input: isTopLevel

Output: N/A

This processor extends the Optical Circuit Discrepancy Detection action on the Optical Circuit Assimilation cartridge.

Partial Circuit Discrepancy Filter

Input: N/A

Output: N/A

Discrepancy Detector

Input: N/A

Output: N/A

This processor extends the Base Detection cartridge.


Table 6-6 Discrepancy Resolution Processors Design Studio Construction

Processor Name Variable

CORBA Property Initializer

Input: N/A

Output:

  • corbaSeed

    A JavaBean that holds properties related to the CORBA cartridge, for CORBA connectivity. See Network Integrity CORBA Cartridge Guide for more information.

MSS CORBA Property Initializer

Input: corbaSeed

Output:

  • corbaSeed

  • mssCORBAConnectionDetails

    The property group containing the MBean configuration required to establish CORBA connectivity with MSS.

  • mssEJBConnectionDetails

    The property group containing the MBean configuration required to establish EJB connectivity with MSS.

CORBA Connection Manager

Input: corbaSeed

Output:

  • namingServer

    The Naming context for the MSS system.

  • orb

    The object request broker (ORB) instance.

Resolution Framework Initializer

Input: mssCORBAConnectionDetails, mssEJBConnectionDetails

Output:

  • baseResolutionElement

    An instance of the data structure used to run resolution actions in MSS.

MSS Resolution Initializer

Input: mssCORBAConnectionDetails, mssEJBConnectionDetails, namingServer, orb, baseResolutionElement

Output: mssCORBAConnectionDetails, mssEJBConnectionDetails

Resolution Framework Dispatcher

Input: mssCORBAConnectionDetails, mssEJBConnectionDetails, baseResolutionElement

Output: mssCORBAConnectionDetails, mssEJBConnectionDetails