Skip Headers
Oracle® Communications Network Integrity Optical TMF814 CORBA Cartridge Guide
Release 7.1

E23711-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 About Cartridge Components

This chapter provides information about the components that make up the Oracle Communications Network Integrity Optical TMF814 CORBA cartridge.

Processor Workflow

When a TMF814 scan action type is run, the Optical TMF814 CORBA cartridge runs the following processors, in the following order:

  1. CORBA Property Initializer

  2. TMF814 CORBA Property Initializer

  3. CORBA Connection Manager

  4. TMF814 Property Initializer

  5. TMF814 Property Customizer

  6. TMF814 Session Manager

  7. TMF814 Device Recorder Initializer

  8. TMF814 ME Collector

  9. TMF814 Device Modeler

  10. TMF814 Equipment Collector

  11. TMF814 Equipment Modeler

  12. TMF814 PTP Collector

  13. TMF814 PTP Modeler

  14. TMF814 CTP Discoverer for PTP

  15. Huawei MSTP EndPoint Collector

  16. Huawei MSTP EndPoint Modeler

  17. TMF814 FTP Collector

  18. TMF814 FTP Modeler

  19. TMF814 CTP Discoverer for FTP

  20. TMF814 Device Persister

  21. TMF814 Device Recorder Persister

  22. TMF814 Cross-Connect Discoverer

  23. TMF814 Topological Link Collector

  24. TMF814 Topological Link Modeler

  25. TMF814 Pipe Persister

The Optical TMF814 CORBA cartridge supports a recording mode for recording TMF814 data. See "About Recording Mode" for more information.

Figure 4-1 illustrates the processor workflow of the Optical TMF814 CORBA cartridge.

Figure 4-1 Optical TMF814 CORBA Cartridge Processor Workflow

Optical TMF814 CORBA cartridge processor workflow

Actions

The processors in this cartridge are run by the following actions:

  • Discover Abstract TMF814 action: this is an abstract action that can be extended in Oracle Communications Design Studio to discover specified network and connectivity objects, using specified ORB Properties and ORB Arguments. This action does not contain UI parameters. The definition of UI parameters and how they appear is the responsibility of the extending action.

  • Discover TMF814 action: this action, which extends the Discover Abstract TMF814 actions is a complete and deployable action, configured using UI parameters, so you have full control over what is and is not discovered. This action can be extended to add new UI parameters, but the original UI parameters must remain. This action can also be extended to discover additional types of network and connectivity objects.

  • Discover Huawei U200 action: this action, which extends the Discover TMF814 action, is used to discover Huawei-specific multiple spanning tree protocol (MSTP) endpoints. This action is configured using UI parameters, so you have full control over what is and is not discovered. This action is complete and deployable and can be extended to discover other types of Huawei devices.

See "Design Studio Construction" for information about how the actions are built.

Depending on the discovery action used, discovered device and result group names are discovered differently:

  • When you use the Discover TMF814 action, device and result group names are taken from the TMF814 managed element name.

  • When you use the Discover Huawei U2000 action, device and result group names are taken from the TMF814 managed element nativeEmsName.

You can extend the Optical TMF814 CORBA cartridge to model device and result group names to use custom name schemas in order to match the naming used in your inventory system. See "Discovering Custom Device or Result Group Names" for more information.

Processors

This section describes the processors that are used to discover and model TMF814 physical equipment and termination point (TP) data. These processors can be configured to selectively discover and model either physical or logical objects, or both.

CORBA Property Initializer

This processor is imported from the CORBA cartridge. It initializes all the properties required to create the ORB and NameServer objects and write them to the corbaSeed (a JavaBean class). See CORBA Cartridge Guide for more information.

TMF814 CORBA Property Initializer

This processor reads the ORBProperties and ORBArguments parameters from the UI and passes them to the CORBA Connection Manager processor through the corbaSeed. ORBProperties and ORBArguments are used during ORB initialization.

See CORBA Cartridge Guide for information about ORBProperties and ORBArguments.

CORBA Connection Manager

This processor is imported from the CORBA cartridge. It takes the corbaSeed from the CORBA Property Initializer processor and initiates the ORB to establish common object request broker architecture (CORBA) connectivity. This processor provides the client-side ORB and NameServer objects for extending cartridges. See CORBA Cartridge Guide for more information.

TMF814 Property Initializer

This processor initializes properties required by other processors in the Discover Abstract TMF814 action. All properties are populated into a JavaBean class named tmf814Properties. These properties can be customized by other processors usin the oracle.communications.integrity.tmf814discovery.beans.TMF814Properties Java class method. Table 4-1 lists the available properties.

Table 4-1 TMF814 Property Initializer Properties and Values

Property Name Description Value

Username

Indicates the EMS user name, used while getting the EMS session from the session factory.

Extending cartridges may supply a default value.

Password

Indicates the EMS password, used while getting the EMS session from the session factory.

Extending cartridges may supply a default value.

collectCTP

Indicates the type of CTPs to collect:

  • A current TP is a CTP that is, or can be cross-connected in the current mapping configuration.

  • An in-use TP is a CTP that is used by an subnetwork connection (SNC) in any state, or a CTP that is terminated and mapped.

  • A potential contained TP (contained in a PTP or CTP) is a CTP that is capable of supporting all possible mapping configurations at the specified layer rates and is contained by the specified termination.

Valid values: NONE, CURRENT, IN_USE, POTENTIAL

collectEquipment

Indicates whether to collect Equipment and Equipment Holder details. If this value is FALSE, only MEs and connection termination points (CTPs) associated with floating termination points (FTPs) are collected and modeled.

Valid values: TRUE, FALSE

collectTP

Indicates whether to collect physical termination points (PTPs) or floating termination points (FTPs), or both.

Valid values: ALL, NONE, ONLY_PTP, ONLY_FTP

crossConnectCollectionType

Indicates the method used to collect cross-connects:

  • A value of USE_SNC collects cross-connects using multi layer subnetwork (MLSN) Manager APIs.

  • A value of USE_ME_MANAGER collects cross-connects using ME Manager APIs.

Cross-connects are not collected if the value is set to NONE.

Ensure the correct value is used, according to your vendor specifications.

Valid values: USE_SNC, USE_ME_MANAGER, NONE

crossConnectModelCustomizerImplClass

Allows you to customize cross-connect modeling.

n/a

ctpCollectionDepth

Indicates the hierarchical depth to which CTPs are collected (because TPs can contain several levels of child TPs), depending on the API used by the vendor to call CTPs.

Valid values: positive integers

ctpModelCustomizerImplClass

A class implementing the oracle.communications.integrity.tmf814discovery.model.ctp.CTPModelCustomizer interface.

To discover additional attributes for CTPs, add a similar implementation interface to the system.

n/a

discovererFactoryImplClass

A default implementation of the Discoverer Factory class, used to provide a custom collection mechanism.

n/a

emsManagerName

Name of the EMSMgr_I manager used to obtain the manager from EmsSession_I.getManager.

n/a

equipmentFetchSize

Indicates the number of Equipment or Holders to fetch at a time.

Valid values: positive integer

equipmentInventoryManagerName

Indicates the name of the Equipment inventory manager.

n/a

includeHigherOrderCCs

Specifies whether higher-order cross-connects of other SNCs are collected.

Valid values: TRUE, FALSE

layerRateList

Filters TPs based on layer rates while collecting in-use and potential CTPs. An empty list indicates to the element management system (EMS) to report all CTPs of all rates.

Valid values: Comma separated list of layer rates as numerical values.

managedElementManagerName

Indicates the name of the ME manager.

n/a

meFetchSize

Indicates number of MEs to fetch at a time, as opposed to obtaining them all at once.

n/a

mlsnManagerName

Name of the MultiLayerSubnetworkMgr_I manager used to obtain the manager from EmsSession_I.getManager.

n/a

modelCollectionType

Indicates whether to model logical or physical devices, or both.

Valid values: logical, physical, both (=null)

namingService

EMS naming service.

n/a

namingServiceFormat

The EMS naming service format. A value of STRINGIFIED indicates that the namingService property value is a CORBA stringified object reference. A value of PLAIN indicates that the namingService property value is in a specific format.

Valid values: PLAIN, STRINGIFIED

rootPOA

Indicates the name of the root Portable Object Adapter (POA)

n/a

topologicalLinkCollectionType

Indicates the method used to collect topological links:

  • A value of BETWEEN_SN collects topological links between subnetworks only.

  • A value of INSIDE_SN collects topological links inside subnetworks only.

  • A value of ALL collects all topological links.

Topological links are not collected if value is set to NONE.

Ensure the correct value is used, according to your vendor specifications.

Possible values: ALL, BETWEEN_SN, INSIDE_SN, NONE

tpFetchSize

Indicates the number of TPs to fetch at a time, as opposed to obtaining them all at once.

n/a

XCPipeFlushSize

Cross-connect Information Model objects are flushed to the database in batches. This value indicates number of modeled objects flushed to DB in each batch.

Valid value: integer


TMF814 Property Customizer

This processor takes UI parameters for a specific scan and assigns them to properties in the TMF814 Property Initializer processor. See Table 9-3, "TMF814 UI Parameters Design Studio Construction" for a list of available UI parameters.

TMF814 Session Manager

This processor creates a session manager instance (of type oracle.communications.integrity.tmf814discovery.session.SessionManager) that is responsible for managing the EmsSession and TMF814Object managers, as well as creating and managing the emsMgr.EMSMgr_I and multiLayerSubnetwork.MultiLayerSubnetworkMgr_I managers.

This processor also populates the discovered EMS version and updates the TMF814 properties Java bean object.

TMF814 Device Recorder Initializer

This processor initializes Recording Mode (if it has been enabled). See "About Recording Mode" for more information.

TMF814 ME Collector

This processor retrieves a list of MEs using the TMF814 ME Manager. It outputs an Iterable for each ME. To deal with the large number of objects, these iterators can retrieve MEs in chunks (pagination) instead of all at one time.

Pagination is internal to the produced Iterable. The meFetchSize property set in tmf814Properties indicates the number of MEs to be retrieved at a time.

This processor can filter MEs based on name-matching criteria provided through UI parameters. Only those MEs that are matched by specified criteria are considered for further processing.

TMF814 Device Modeler

This processor is run for each Iterable produced by the TMF814 ME Collector processor. It creates the logical and physical device entities. Device entities are not added to the result by this processor.

This processor can be configured to model either physical or logical objects by setting the modelCollectionType property. By default, both types of objects are modeled.

TMF814 Equipment Collector

This processor retrieves a list of Equipment and EquipmentHolders objects for the MEs using the Equipment Inventory Manager. It outputs an Iterable for each EquipmentOrHolder object.

TMF814 Equipment Modeler

This processor is run for each Iterable produced by the TMF814 Equipment Collector processor. It creates the equipment and equipment holder entities and adds them to the Physical Tree. This processor returns either Information Model Equipment or Equipment Holder, depending on which is modeled. See "About Cartridge Modeling" for more information.

TMF814 PTP Collector

This processor is run for each Iterable from the TMF814 Equipment Collector processor. This processor collects all the PTPs for each equipment object. It outputs an Iterable for each PTP.

TMF814 PTP Modeler

This processor is run for each Iterable from the TMF814 PTP Collector processor. This processor models each PTP as a Physical Port or Device Interface object and adds them to either the Physical or Logical Tree.

TMF814 CTP Discoverer for PTP

This processor recursively retrieves and models CTPs for each input PTP obtained from the Iterable produced by the TMF814 PTP Collector processor. The following operation is run for each PTP:

  1. Using an input PTP, a TMF814 operation is run to obtain all its contained CTPs.

  2. Each CTP is modeled as a Device Interface object.

  3. (Optional) The CTP customizer is run.

    Note:

    The ctpModelCustomizerImplClass class is used to configure the CTP customizer. This class is set by the TMF814 Property Initializer processor.
  4. The CTP is added to the Logical Tree.

  5. Depending on the ctpCollectionDepth parameter, for each collected CTP, a TMF814 operation is run to obtain its child CTPs. For each child CTP, the operation restarts at step 2.

Huawei MSTP EndPoint Collector

This processor collects multi-service transmission platform (MSTP) endpoints (ATM and Ethernet ports) using Huawei-specific APIs and outputs an Iterable for each endpoint collected. The produced Iterable is similar to the one explained for the TMF814 ME Collector processor.

Huawei MSTP EndPoint Modeler

This processor is run for each Iterable produced by the Huawei MSTP EndPoint Collector processor. It models each input endpoint as a physical port and mapping device interface and adds it to its parent equipment in the Information Model Tree.

TMF814 FTP Collector

This processor retrieves a list of all FTPs and outputs an Iterable for each FTP object. A property set in tmf814Properties specifies whether to collect FTP details. The produced Iterable is similar to the one explained for the TMF814 ME Collector processor.

TMF814 FTP Modeler

This processor is run for each Iterable produced by the TMF814 FTP Collector processor. This processor creates Device Interface objects for the input FTPs and adds them to the Logical Tree.

TMF814 CTP Discoverer for FTP

This processor recursively retrieves and models CTPs for each input FTP obtained from the Iterable produced by the TMF814 FTP Collector processor. The following operation is run for each FTP:

  1. Using an input FTP, a TMF814 operation is run to obtain all its contained CTPs.

  2. Each CTP is modeled as a Device Interface object.

  3. (Optional) The CTP customizer is run.

    Note:

    The ctpModelCustomizerImplClass class is used to configure the CTP customizer. This class is set by the TMF814 Property Initializer processor.
  4. The CTP is added to the Logical Tree.

  5. Depending on the ctpCollectionDepth parameter, for each collected CTP, a TMF814 operation is run to obtain its child CTPs. For each child CTP, the operation restarts at step 2.

TMF814 Device Persister

This processor adds the logical and physical devices to the result and persists it. This processor closes and discards any CORBA iterators used.

TMF814 Device Recorder Persister

This processor persists the recorded data to a file, if the Recording Mode is enabled. See "About Recording Mode" for more information.

TMF814 Cross-Connect Discoverer

This processor collects and models cross-connects according to the following operation:

  1. Run TMF814 operation to collect cross-connects.

  2. For each collected cross-connect:

    1. Model the cross-connect according to the Optical Model for Network Integrity. See Network Integrity Developer's Guide for more information.

    2. (Optional) Run the Cross-connect Customizer processor.

      Note:

      The crossConnectModelCustomizerImplClass is used to configure the Cross-connect Customizer processor.
    3. Add modeled entity to the result group.

    4. Send last result group, or any result group equal to the configured flush size to the Network Integrity database.

Cross-connect collection is controlled by the crossConnectCollectionType parameter.

Cross-connects are modeled as pipe entities and sent to the Network Integrity database in batches. Batch sizes are configurable using the XCPipeFlushSize property.

Cross-connect modeling can be extended by creating a Cross-connect Customizer processor. See "Design Studio Extension" for more information.

TMF814 Topological Link Collector

This processor collects all the EMS STM links and returns an Iterable that collects Topological Link objects. The produced Iterable is similar to the one explained for the TMF814 ME Collector processor.

TMF814 Topological Link Modeler

This processor is run for each Iterable produced by the TMF814 Topological Link Collector processor. This processor models each input topological link object according to the Optical Model for Network Integrity, and adds it to the result group. See Network Integrity Developer's Guide for more information.

TMF814 Pipe Persister

This processor persists all the cross-connect and topological link pipes and writes the recorded data to corresponding files. See "About Recording Mode" for more information about the recorded data files.

About Recording Mode

The Optical TMF814 CORBA cartridge can be configured to record all discovered MEs, topological links, and cross-connects. The recorded files (ME_Name.me for MEs, EMS_Name.ems for topological links, and EMS_Name.cc for cross-connects) are saved to the WL_Domain_Home/corbaData/Scan_Name/EMS_Name directory, where:

If the TMF814 scan action type has been configured to not discover MEs, topological links, or cross-connects, the corresponding file is not generated.

Recording Mode is controlled with the tmf814.properties file in the WeLogic_Domain_Home/config/corbaConfig/ directory. Enable this feature by editing the tmf814.properties files so that MODE=RECORD. Disable this feature by editing the tmf814.properties files so that MODE=NORMAL. Configure the CHUNK SIZE property to contol the number of cross-connects written to EMS_Name.cc at a time. Recording Mode can be enabled or disabled by an administrator without needing any server or application restarts. The recording processors reads this file each time it is run.