PK H\lCoa,mimetypeapplication/epub+zipPKH\lCiTunesMetadata.plistd artistName Oracle Corporation book-info cover-image-hash 581371187 cover-image-path OEBPS/dcommon/oracle-logo.jpg package-file-hash 424223238 publisher-unique-id E23716-01 unique-id 349636814 genre Oracle Documentation itemName Oracle® Communications Network Integrity MSS Integration Cartridge Guide, Release 7.1 releaseDate 2012-01-18T23:17:11Z year 2012 PK.j idPKH\lCMETA-INF/container.xml PKYuPKH\lCOEBPS/cover.htmO Cover

Oracle Corporation

PK[pTOPKH\lCOEBPS/mss_studio_ext.htmC Design Studio Extension

7 Design Studio Extension

This chapter contains examples and explanations on how to extend certain aspects of the Oracle Communications Network Integrity MSS Integration cartridge. Refer to Network Integrity Developer's Guide for more information. See Network Integrity Concepts for guidelines and best practices for extending cartridges.

The following examples are explained in this section:

Importing Additional Information from the MSS Extract Schema

The MSS Import action imports equipment and circuit information from Oracle Communications MetaSolv Solution (MSS) from specific fields in the MSS staging tables. You can extend the MSS Import action to import information from other fields available in the MSS Extract Schema.

Use the following guidelines to extend the MSS Import action to import additional information from the MSS Extract Schema:

  1. Identify the additional fields and the corresponding entities from the MSS Extract Schema to add to the scope of the MSS Import action.

  2. Determine the required API mapping and the corresponding TMF814 entities for the additional information. See Network Integrity Optical TMF814 CORBA Cartridge Guide for more information.

  3. Identify the processor that models the additional TMF814 entities.

  4. Extend the MSS Import action to import and model the additional entities.

Importing Additional Information from MSS

The MSS Import action imports equipment and circuit information from MSS from specific fields in the MSS staging tables. You can extend the MSS Import action to import information from other fields that are not available in the MSS Extract Schema.

Use the following guidelines to extend the MSS Import action to import additional information from outside the MSS Extract Schema:

  1. Identify the additional fields and the corresponding entities from MSS to add to the scope of the MSS Import action.

  2. Determine the MSS Extract Schema tables for the additional information.

  3. Use the custom fields in each of the MSS Extract Schema tables to populate the additional fields for each entity.

  4. Extend the MSS Extraction script to populate the additional information in the custom fields for each entity.

  5. Identify the additional fields and the corresponding entities from the MSS Extract Schema to add to the scope of the MSS Import action.

  6. Determine the required API mapping and the corresponding TMF814 entities for the additional information. See Network Integrity Optical TMF814 CORBA Cartridge Guide for more information.

  7. Identify the processor that models the additional TMF814 entities.

  8. Extend the MSS Import action to import and model the additional entities.

PK1r]PKH\lCOEBPS/mss_cart_usage.htmL Cartridge Usage

3 Cartridge Usage

This chapter explains how to use the Oracle Communications Network Integrity MSS Integration cartridge.

Creating an MSS Import Scan

The MSS Import Scan action imports inventory data from Oracle Communications MetaSolv Solution (MSS). See "Import from MSS Action" for more information.

You must already have created a data source in the Network Integrity WebLogic Server domain that points to the MSS extract database, and MSS must be configured as the import system. See "Configuration Dependencies" for more information.

To create an MSS Import scan:

  1. Create a scan, as explained in the Network Integrity Help.

  2. On the General tab, do the following:

    1. From the Scan Action list, select Import from MSS.

      The Scan Type field displays Import.

    2. (Optional) To refine the scope of the imported data, enter the following MSS import parameters:

      • In the Network Location field, specify the network location. Enter either the CLLI code or the coded location format.

      • In the Status field, specify the status of the data to import.

      • To filter the imported nodes by name, enter one or more names (separated by commas) in the Node Name field and choose a value from the Node Name Qualifier list.

      • In the Node ID field, enter one or more node IDs separated by commas.

      • In the Scope field, specify the scope of data to be imported.

      • In the Run MSS Extract field, specify whether you want to run the MSS extract procedure before running the MSS Import scan.

      See Table 6-2, "Cartridge UI Parameters Design Studio Construction" for more information.

  3. Make any other required configurations.


Note:

The Scope tab is automatically set to the MSS Extract Schema configured on the Import System screen of Network Integrity.

Resolving Discrepancies

The MSS Integration cartridge allows you to resolve most discrepancies from Network Integrity, uploading the resolution directly to MSS. See "About Discrepancy Resolution" for more information.

To resolve a discrepancy:

  1. Search for discrepancies. See Network Integrity Concepts for more information.

  2. In the Search Results table, right-click a discrepancy and select Correct in MSS.

    The MSS Integration cartridge calls the appropriate API to resolve the discrepancy in MSS.

The following list identifies the types of discrepancies that the MSS Integration cartridge can resolve from within Network Integrity:

Though the MSS Integration cartridge detects other types of discrepancies, they must be manually fixed from within MSS. Network Integrity fails the Resolve in MSS action if you try to resolve an unsupported discrepancy type, setting the discrepancy status to Not Implemented.

PKg#QLPKH\lCOEBPS/mss_studio_const.htm Y Design Studio Construction

6 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 NameResult CategoryUI ParametersProcessors

Import from MSS

Device

See Table 6-2

See Table 6-3

Detect Equipment Discrepancies

Device

See Table 6-2

See Table 6-4

MSS Circuit Discrepancy Detection

Circuit

See Table 6-2

See Table 6-5

Resolve in MSS

Device

N/A

See Table 6-6


Table 6-2 Cartridge UI Parameters Design Studio Construction

Parameter NameTypeDescriptionUI 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:

  • Equipments, STM Links, and Circuits

  • Equipments and STM Links only

  • Equipments 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 NameVariable

Equipment DAOs Initializer

Input: N/A

Output:

  • daoLocator

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

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 NameVariable

Equipment Filters Initializer

Input: N/A

Output: N/A

Discrepancy Detector

Input: N/A

Output: N/A

This processor extends the Base Detection cartridge.

Discrepancy Filter

Input: N/A

Output: N/A


Table 6-5 Circuit Discrepancy Detection Processors Design Studio Construction

Processor NameVariable

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 NameVariable

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


PKH4Y YPKH\lCOEBPS/title.htm* Oracle Communications Network Integrity MSS Integration Cartridge Guide, Release 7.1

Oracle® Communications Network Integrity

MSS Integration Cartridge Guide

Release 7.1

E23716-01

January 2012


Oracle Communications Network Integrity MSS Integration Cartridge Guide, Release 7.1

E23716-01

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

PK _V/*PKH\lCOEBPS/preface.htm Preface

Preface

This guide explains the functionality and design of the Oracle Communications Network Integrity MSS Integration cartridge.

Audience

This guide is intended for Network Integrity administrators, developers, and integrators.

This guide assumes that you are familiar with the following documents:

This guide assumes that you are familiar with the following Oracle products and cartridges:

This guide assumes that your are familiar with the following concepts:

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

PK-  PKH\lCOEBPS/mss_modeling.htm About Cartridge Modeling

5 About Cartridge Modeling

This chapter explains how the imported data is modeled.

About Cartridge Modeling

To facilitate discrepancy detection and resolution, the Oracle Communications Network Integrity MSS Integration cartridge models the imported data from Oracle Communications MetaSolv Solution (MSS) to the Oracle Communications Information Model.

The MSS Integration cartridge uses different modeling logic depending on the action it is performing. See the following sections for more information:

About Import Data Modeling

This section explains how Network Integrity models data imported from MSS.

You can configure various parameters in the Network Integrity UI to determine the quantity of data to import from MSS. Network Integrity logically applies the parameters to filter the imported data. When no filtering parameters are configured in the UI, Network Integrity imports all MSS data.

API Mapping

Network Integrity uses APIs to map the imported MSS data to the Information Model, which allows the MSS data to map directly to TMF814 entities. The MSS Integration cartridge uses TMF814 specifications to model the MSS data.

Table 5-1 shows the relationship between the imported MSS data, physical TMF814 entities, and physical Information Model entities.

Table 5-1 MSS Data Modeling to the Physical Information Model Tree

MSS Data ObjectTMF814 EntityInformation Model Entity

Network Node

Managed Element (ME)

Physical Device, Logical Device

Equipment

Equipment Holder (Rack)

Equipment

Equipment

Equipment Holder (Shelf)

Equipment

Equipment

Equipment Holder (Sub-Shelf)

Equipment

Mounting Position

Equipment Holder (Slot)

Equipment Holder

Mounting Position

Equipment Holder (Sub-Slot)

Equipment Holder

Equipment

Equipment (Card)

Equipment

Port

Physical Termination Point (PTP)

Physical Port


Table 5-2 shows the relationship between the imported MSS data, logical TMF814 entities, and logical Information Model entities.

Table 5-2 MSS Data Modeling to the Logical Information Model Tree

MSS DataTMF814 EntityInformation Model Entity

Network Node from ee_equipment

ME

LogicalDevice

Port from ee_port_address

Point Termination Port (PTP) and Floating Termination Point (FTP)

DeviceInterface

(Port) Circuit and (Rack/Shelf) Circuit from ce_port_address

Connection Termination Point (CTP)

DeviceInterface

N/A

LayeredParameters

DeviceInterfaceConfigurationItem


Field Mapping

The following tables explain the field mappings for each imported MSS object.

Table 5-3 Physical Device Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

Id

Static

ee_equipment.network_node_id/ nn_network_node.NETWORK_NODE_ID

No

name

Static

ee_equipment.nw_node_name/ nn_network_node.NETWORK_NODE_NAME

No

description

Static

N/A

No

discoveredVendorName

Dynamic

ee_equipment.vendor_name

No

serialNumber

Static

ee_equipment.serial_nbr

No

physicalLocation

Static

ee_equipment.loc_id_clli_code/ nn_network_node.NETWORK_NODE_LOC_CLLI_CODE

No

softwareRev

Dynamic

ee_equipment.software_release_identifier

No

modelName

Dynamic

ee_equipment.equipspec_type/ nn_network_node.NETWORK_NODE_TYPE

No

nativeEmsName

Static

ee_equipment. nw_node_name/ nn_network_node.NETWORK_NODE_NAME

No

userLabel

Dynamic

ee_equipment.nw_node_name/ nn_network_node.NETWORK_NODE_NAME

No

owner

Dynamic

ee_equipment.vendor_name

No


Table 5-4 Root Equipment Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

Id

Static

ee_equipment.nw_node_name/Equipment_type-mounting-position

No

name

Static

ee_equipment.equipment_acronym

No

description

Static

N/A

No

discoveredVendorName

Dynamic

ee_equipment.vendor_name

Yes

serialNumber

Static

ee_equipment.serial_nbr

Yes

physicalLocation

Static

ee_equipment.loc_id_clli_code

No

discoveredPartNumber

Dynamic

ee_equipment.vendor_part_number

Yes

hardwareRev

Dynamic

ee_equipment.version_of_hardware_installed

No

modelName

Dynamic

ee_equipment.equipspec_type

No

nativeEmsName

Static

ee_equipment.equipment_acronym

No

expectedObjectType

Dynamic

N/A

No

serviceState

Dynamic

ee_equipment.availability_status

Valid values are IN_SERVICE, OUT_OF_SERVICE, IN_MAINTENANCE, UNKNOWN, TESTING

No

userLabel

Dynamic

ee_equipment.equipment_name

No

owner

Dynamic

ee_equipment.vendor_name

No


Table 5-5 Non-Root Equipment Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

Id

Static

Derived with parent-id from equipmentType-mounting_position_seq

No

name

Static

Derived from ee_mounting_position_hier.equipment_acronym_hier

No

description

Static

N/A

No

discoveredVendorName

Dynamic

Derived from ee_mounting_position_hier.vendor_name_hier

No

serialNumber

Static

Derived from ee_mounting_position_hier. serial_nbr_hier

Yes

physicalLocation

Static

ee_equipment.loc_id_clli_code

This field value corresponds to the root equipment.

No

discoveredPartNumber

Dynamic

Derived from ee_mounting_position_hier.vendor_part_number_hier

Yes

hardwareRev

Dynamic

N/A

Yes

modelName

Dynamic

Derived from ee_mounting_position_hier.equipspec_type_hier

No

nativeEmsName

Static

Derived from ee_equipment.equipment_acronym_hier

No

expectedObjectType

Dynamic

N/A

No

serviceState

Dynamic

ee_mounting_position_hier.availability_status_hier

This field is assigned one of the following values: IN_SERVICE, OUT_OF_SERVICE, IN_MAINTENANCE, UNKNOWN, TESTING.

No

userLabel

Dynamic

Derived from ee_mounting_position_hier.equipment_name_hier

No

owner

Dynamic

Derived from ee_mounting_position_hier.vendor_name_hier

No


Table 5-6 Equipment Holder Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

Id

Static

Derived with parent-id from /holder_type-mounting-position

No

name

Static

Derived from ee_mounting_position_hier.mtg_pos_nbr_hier

The slot number is equivalent to mounting position number.

No

description

Static

N/A

No

serialNumber

Static

N/A

No

physicalLocation

Static

N/A

No

modelName

Dynamic

ee_equipment.equipment_spec_type

No

nativeEmsName

Static

holder_type-ee_mounting_position_hier.mtg_pos_nbr_hier

No

userLabel

Dynamic

ee_equipment.equipment_acronym

No

owner

Dynamic

ee_equipment.vendor_name

No


Table 5-7 Physical Port Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

Id

Static

Derived with parent-id from /port-ee_port_address.portaddr_seq

No

name

Static

Derived from port-ee_port_address.portaddr_seq

Yes

description

Static

N/A

No

portNumber

Static

N/A

No

customerPortName

Static

N/A

No

vendorPortName

Static

N/A

No

serialNumber

Static

N/A

No

physicalLocation

Static

N/A

No

nativeEmsName

Static

N/A

No

direction

Dynamic

Bidirection

No

tpProtectionAssociation

Dynamic

N/A

No

edgePoint

Dynamic

True

No

physicalAddress

Static

ee_port_address.node_address when ee_port_address.portaddr_type value corresponds to physical

No


Table 5-8 Logical Device Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

Id

Static

N/A

No

name

Static

ee_equipment.nw_node_name

Yes

description

Static

N/A

No

specification

Static

N/A

No

nativeEmsAdminServiceState

Static

N/A

No

nativeEmsServiceState

Static

N/A

No

nativeEmsName

Static

ee_equipment.ems_nms_name

No

physicalLocation

Static

ee_equipment.loc_id_clli_code

No


Table 5-9 Media Interface Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

Id

Static

N/A

No

name

Static

Derived from port-ee_port_address.portaddr_seq

No

description

Static

N/A

No

ifType

Static

PTP, FTP, or CTP, according to the entity being modeled

No

interfaceNumber

Static

N/A

No

customerInterfaceNumber

Static

N/A

No

vendorInterfaceNumber

Static

N/A

No

nativeEmsName

Static

N/A

No

nativeEmsAdminServiceState

Static

N/A

No

nativeEmsServiceState

Static

N/A

No

mtuSupported

Static

N/A

No

mtuCurrent

Static

N/A

No

physicalAddress

Static

N/A

No

physicalLocation

Static

N/A

No

minSpeed

Static

N/A

No

maxSpeed

Static

N/A

No

nominalSpeed

Static

N/A

No

connectionState

Dynamic

ce_circuit.status(M2)

No

tpMappingMode

Dynamic

N/A

No

Direction

Dynamic

Bidirection

No

tpProtectionAssociation

Dynamic

N/A

No

edgePoint

Dynamic

N/A

No

userLabel

Dynamic

N/A

No

owner

Dynamic

N/A

No

activeEmsConnectorPresent

Static

N/A

No


Table 5-10 Pipe Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

name

Static

ce_circuit.ecckt

Yes

Id

Static

ce_circuit.circuit_design_id

No

gapPipe

Static

Hard-coded to FALSE

No

physicalLocation

Static

ce_circuit.loc_A_clli_code

No

layerRate

Dynamic

ce_circuit.rate_code

No

Rerouted

Dynamic

Hard-coded to FALSE

No

partial

Dynamic

Derived: set to FALSE if the number of ports is greater than one, else it is TRUE.

No


Table 5-11 Transport Pipe Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

name

Static

ce_circuit.ecckt

Yes

Id

Static

ce_circuit.circuit_design_id

No

gapPipe

Static

Hard-coded to FALSE

No

physicalLocation

Static

ce_circuit.loc_A_clli_code

No

layerRate

Dynamic

ce_circuit.rate_code

No

Rerouted

Dynamic

Hard-coded to FALSE

No

partial

Dynamic

Derived: set to FALSE if the number of ports is greater than one, else it is TRUE.

No


Table 5-12 STM Link Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

name

Static

ce_circuit.ecckt

Yes

Id

Static

cle_circuit.circuit_design_id

No

gapPipe

Static

Hard-coded to FALSE

No

physicalLocation

Static

ce_circuit.loc_A_clli_code

No

layerRate

Dynamic

ce_circuit.rate_code

No


Table 5-13 Trail Path Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

name

Static

ce_circuit_position.ecckt

Yes

gapPipe

Static

Hard-coded to FALSE

No

layerRate

Dynamic

ce_circuit_position.rate_code

No

channel

Dynamic

ce_circuit_position.jklm

Yes


Table 5-14 Trail Pipe Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

name

Static

ce_circuit_position.ecckt

Yes

AEnd

Static

Derived from the originating port name

No

ZEnd

Dynamic

Derived from the terminating port name

No

channel

Dynamic

ce_circuit_position.jklm

Yes


Table 5-15 Pipe Termination Point Field Mapping

Information Model AttributeInformation Model SupportMSS Inventory FieldUsed for Discrepancy Detection

name

Static

Hierarchical name derived from of the following:

  • ce_port_address.equipment_acronym_hier

  • ce_port_address.mtg_pos_nbr_hier

  • ce_port_address.portaddr_seq

Yes

physicalLocation

Static

ce_port_address.clli_code

No

Device

Dynamic

ce_port_address.nw_node_name

Yes

Directionality

Dynamic

ce_port_address.a_z_other_cd

Yes


Data Import Algorithm

This section explains the various algorithms and logic used to model the imported MSS inventory data.

Import Equipment Hierarchy Algorithm

This algorithm uses spring framework pagination to incrementally retrieve node names from each page created by the Page Creator processor. This algorithm uses the following logic:

  1. Gets all the node names from EquipmentExportDAO.

  2. For each node:

    1. Creates a physical and logical device in the Information Model.

    2. Gets the root equipment (such as a shelf, or rack) from EquipmentExportDAO.

  3. For each root equipment:

    1. Verifies that the occupiedMountingPositions attribute value is 0:

      • If yes, the equipment is modeled as a rack.

      • If no, verifies whether the root equipment has a mounting position. If there is a mounting position, the equipment is modeled as a shelf.

    2. Associates the rack and shelf to the physical device and states the equipment type (rack or shelf) in the equipment name.

    3. Retrieves the child equipment hierarchy from EquipmentPositionHierDAO (child equipment are represented as EquipmentPositionHier entities).

    4. Queries the ports in the root equipment hierarchy from EquipmentPortAddressDAO (ports are represented as EquipmentPortAddress entities).

    5. Creates a list that maps card IDs to their ports.

    6. For each EquipmentPortAddress entity, verifies if leafEquipmentId equals EquipmentId.

      • If yes, models the port as a physical port (FTP) and associates it with the parent equipment. Models a media interface, associates it to the physical port, and sets the media interface as a child of the logical device.

      • If no, fills the card ID and all ports with the leafEquipmentId value as the list of associated ports.

    7. Builds the child equipment hierarchy in the Information Model with the EquipmentPositionHier entities.

    8. Saves the modeling information to th ephysical and logical trees.

Build Equipment Hierarchy Algorithm

The input for this algorithm is the list of EquipmentPositionHier entities and the map of cards-to-ports. Each EquipmentPositionHier is an immediate child (either a card or shelf) of the root equipment. This algorithm uses the following logic:

  1. Gets the list of mounting position numbers down the hierarchy for each EquipmentPositionHier entity.

  2. For each mounting position number:

    1. Models a shelf object as an equipment entity if its parent is a rack object and the shelf is not yet built in this hierarchy and associates the child with its parent.

    2. Models a card object as an equipment entity if the shelf is already built. Models a slot object as an equipment holder entity for the card. If the slot is already built, models a sub-slot object as an equipment holder entity. Associates children objects with their parent.

    3. Gets the list of ports associated with the card from the map of cards-to-ports.

    4. Models each port as a physical port and a media interface entity. Associates the media interface and the physical port with the logical device.

    5. Adds the EquipmentPortAddressDAO entities to each port as a collection.

Import Circuit Hierarchy Algorithm

MSS and the MSS Integration cartridge distinguish between the following types of circuits:

  • STM (physical circuit, such as STM1 or STM4)

  • HOT (logical circuit, such as VC4)

  • LOP (logical circuit, such as E1, E3, or E4)

Table 5-16 shows the relationship between the imported MSS data, physical TMF814 entities, and physical Information Model entities.

Table 5-16 MSS Circuit Data Mapping to Information Model

MSS DataTMF814 EntityInformation Model Entity

STM-Type Circuit

STM Link

Link

LOP-Type Circuit

Customer Circuit or LOP

Pipe

HOT-Type Circuit

HOT

Transport Pipe


MSS organizes logical circuits as children to physical circuits. The input for this algorithm is the list of EquipmentPortAddress entities produced by the Build Equipment Hierarchy algorithm. This algorithm uses the following logic:

  1. For each port entity from the EquipmentPortAddress table:

    1. Gets the CircuitPortAddress instance containing the circuit ID corresponding to an STM link passing through that port.

    2. Queries the CircutExport table to get the STM link with the circuit ID.

    3. Obtains the aPort and zPort for the STM link from the CircuitPortAddress table.

    4. Models the STM link as an optical topological link entity, models its ports as pipe termination point entities, and associates the ports to their link.

    5. Adds the modeled STM link circuit ID to the stmSet collection.

  2. Identifies all VC4 HOT circuits for all the STM circuit IDs in the stmSet collection by querying the trail from CircuitPositionDAO. For each trail:

    1. Identifies E4 customer circuits by counting its children in the CircuitPosition table. For each E4 customer circuit:

      • Queries the CircuitExport table for the circuit ID and models the CircuitExport objects as a pipe entities.

      • Queries the ports for the circuit from the CircuitPortAddress table, models them as PTPs, and associates them to their pipe entity.

      • Queries the trail path from the CircuitPosition table, models them as trail path entities, and associates them to their pipe entity.

      • Verifies the JKLM value for the trail path, and corrects it if necessary.

    2. Identifies VC4 HOT circuits by evaluating the layer rate code. For each VC4 HOT circuit:

      • Models them as transport pipe entities.

      • Queries the CircuitExport table for circuit ID and models the CircuitExport object as a transport pipe entity.

      • Queries the parent STM link from the CircuitPosition table, and queries the STM link ports from the CircuitPortAddress table.

      • Determines the start-port and end-port from the STM link ports, models them as pipe termination points entities, and associates them to their transport pipe entity.

      • Queries the trail paths from the CircuitPosition table, models them as trail path entities, and associates them to their pipe entity.

    3. Adds the modeled transport pipe circuit ID to the vc4sForLops list.

  3. Queries E1 and E3 trail circuits for each VC4 circuit in the vc4sForLop list. For each trail circuit:

    • Queries circuits from the CircuitExport table and models them as pipe entities.

    • Queries customer circuit ports from the CircuitPortAddress table, models them as pipe termination point entities, and associates the ports to the pipe.

    • Queries trail paths from the CircuitPosition table, models them as trail path entities, and associates them to the pipe.

    • Verifies the JKLM value for the trail path, and corrects it if necessary.

About Discrepancy Resolution Modeling

The Discrepancy Resolution action uses different field mappings depending on the type of entity being resolved.

Discrepancy Resolution Field Mapping for Equipment

The MSS Integration cartridge uses MSS CORBA API methods to resolve equipment discrepancies. Each API method runs a Type Java object. Table 5-17 explains the field mapping for physical entities mapping to circuits in the Information Model.

Table 5-17 Equipment Resolution Field Mapping

MSS CORBA APIInformation Model AttributeAPI Type Field

MetaSolv.CORBA.WDIEquipmentTypes.EquipSpecQuery (Equipment entity)

  • discoveredVendorName

  • discoveredPartNumber

  • Manufacturer

  • partNumber

MetaSolv.CORBA.WDIEquipmentTypes_v2.EquipmentInstallation (Equipment entity)

  • serialNumber

  • name

  • serviceState

  • hardwareRev

  • EquipmentModification.serialNumber

  • startingMountingPosition (derived)

  • Status

  • ConfigurationModificationSeq.hardwareVersion

MetaSolv.CORBA.WDIEquipmentTypes_v2.EquipmentUpdate (Equipment entity)

  • serialNumber

  • hardwareRev

  • EquipmentModification.serialNumber

  • ConfigurationModificationSeq.hardwareVersion

MetaSolv.CORBA.WDIEquipmentTypes_v2.EquipInstallQuery (Equipment entity)

  • Name

  • physicalLocation

  • discoveredPartNumber

  • modelName

  • acronym

  • installedAtLocationCode

  • partNumber

  • type

MetaSolv.CORBA.WDIEquipmentTypes_v2.NetworkElementQuery (Equipment entity)

  • Name

  • physicalLocation

  • Name

  • networkLocation

MetaSolv.CORBA.WDIEquipmentTypes_v2.NetworkElementCreate (PhysicalDevice entity)

  • Name

  • physicalLocation

  • Description

  • Name

  • locId

  • Description

MetaSolv.CORBA.WDIEquipmentTypes_v2.NetworkElementResult (PhysicalDevice entity)

  • ID

  • networkNodeId

MetaSolv.CORBA.WDINetworkLocationTypes_v2.NetworkLocationQuery (PhysicalDevice entity)

  • physicalLocation

  • locationCode


Discrepancy Resolution Field Mapping for Circuits

Table 5-18 explains the field mapping for circuit entities mapping to circuits in the Information Model.

Table 5-18 Circuit Resolution Field Mapping

Information Model EntityInformation Model AttributeConnection Field

Pipe

Specification Name

Ratecode

Pipe

Termination points

Ports

Pipe

Channel

Circuit positions

Pipe

PipeTerminationPoint.Originating.location

ALocation

Pipe

PipeTerminationPoint.Terminating.location

ZLocation


PKA mlPKH\lC!OEBPS/img/mss_action_imp_proc.gif,GIF89a~w!,~rr%?'A)D+F,H.K,E/M1O3R3K3K <]">_&9Q&:Q'Dj(Fl+Jq,Ls-@V-Mu.@W.Ox0Qz1S|2T~4F\5G]5W6Y7[8\8]8]8]9]9^:Ma:^:_:_=Nc=b>a>b@c@cAcAeBeCeDUiEgHXlIjJkJ~KlL\oLnN^qNoQqScuTtUdvWvXwYxZy[i{[j{\z^|_|bobpcddguhujwjmzpq~rrrrrstvwxy|}~ԛěԛŞǡȢݥ˫έϯѱҴ´ôӸƺrֺԺɼɽ׿ԛԺrԛrԛԛԺH*\ȰÇ#JHŋ3jȱǏ CRdITRTE˗0ce%"jɳϟ@vU2%PP(]ʴӧPJEeJZʵׯ`{z)e;]˶-[(ZWػxI2ZҺu#f͕+\̘u`&p@7̹^hBY7svJR7.':Vϸs( 3Z'%'Z{R3JZs C9zǻeDhpܴ./MU߁B#i!Ut|u[呅Jͤ!Lg-'}R#%"iq_eQ(ҋzZ\Ej S_`QP#:nHRMv=:fet5ݔ$2 \8bhe'u`IX$D&[uaJt5'N5ӝ߂eTu"^$$Z@Ezj) W' Zi[b!>5C!sOig!RթSQwRI+> I9U-+!>E] \hDJUDT#fkoAdkY JUx/+UO(aSZH2زƴedR^ݠfTP+KK&z D  8GZÊLҎI)uhdA2t, 2aT /U6֐>`J(/'0Ba1$4B$N;R ҈[&'% [ Th qyn 2u$d>;PL h! pH*v K&MB:0't3ҍn%>}La)K(529dDވ'D+; n0a) /ҀX1wRPt9`{ay$DZCd@)5XJjT|vMɚHU)P!2L_'ݐNyJ@BKI@J@+V-*Jq4r@(t QPJĪ tvĪW֊R `)pH2PX5RJX@H*ړh<∥w|%@POq'w=٧~+ "tqz⯼?ц,@/7}3ח~.  ۟>/A(,mldv?iӟg~;7HVv>1xx&zi w؀8h0wF Xg؁8h0zr q0h2oV-6f y49;hf8i=y`i!zKiM(OhQShUxL脻|ЅR(VHZggg}ֆnhp}t8VkgY0N`izx8hi}~ hii6Ȉ A HfƉ@1"(h؊芈FHx~V?16 BiHv8hXc֌X>(׈ƈF@F&Af8hhi| 爏먏gg0`ih iihh h ِIv ɐ ~f> W !F`*h,9% )q 2ْ'Y?ɊA08F9h~lT)O> /ؕ\a镌db i0ni9Aяxivxyzٗ|kȗ tYgy9h |?x!uFaroƙfii iS0 ihh9h 89hV3ii9~盺i  )F@&Af9hyy繝= h9hg gٟiiyiIAa) 0)Zj :~Afii,.ڢ0:2hM0X`57h4c@A  PhRKjO~ ـShUڤWji[ g`iH0g ii*khm ohq:Vh&Qy y*j~Ƨ@A YgЉ*g ji6f* hZ*ziV@ xɪ} ڡZj Zj: B:Ίh46jiF [pJ~f>񥃖 c i暥g~ﺮhehJAAxz i ;VzhЧ[g;;hgjfjֱc&h&K_ֲ h.K3h0 p ;= ?ۗA;Zt AAh@ltBlD<ĈV>h DwMJauv]i^c̽efb fk⋗golfiL=:Z̊xF~\g죁,gZr6}Lv;!lT[R<쯊츔ʐ6A_6>ZY"-TYٍ &Zي$zZM!ڦ-?}; JیݠNۈiیbi-gqo]lֈf }]+gNZuvXrbQʜ~V6fhe؜ّ%:^9Z=e/ɽyځ١>qh#'*" +x` i0/6.g8Ωly6.?h;iLHYDy V1P~r攐&!~"߈fbgeniiiY f惶&=Iy{笩I>hI*aLn-rLkl!ΫX(pI'eeɍ~h&\gΌgg؋H. n[>!&HӮh~&fxڎgNVd.Άgn~.N^g >fO_6^g鈶eaioioenN#/g!Oڸ)h&_o=Y>M^Dioi}(fQ~x'QoS8VgXRwugfvhlOr&.C0ggtyJ{gq^X|eHÃ{ciig!~ 2fgoiyfV xoQ_Vؼ^Gb'~ffc_ZuYT&Sf"1Ń6 UgڏĈۏguV7t~>| qqrqG{!8 DP ZQA NĨ=xcƆMDRʓlKeYS͜:|̠B5p@o%!RV]RVMbװV- ԴkjW&ĝV,޽t S\kX0aň6f|8⸴&*Ē+R[.}WPVꪭ_W=cRmkO$2tҩ?|y <דv7WQWi'j3J8#äp  pç:P¸H-MhAP(c"4CHEB}TQD')0K-eӚ*JSA "5LJUjWUYk}VUY+`iפ|=HfeYQZjuYg6.'ker6Yue]w߅7^y祷^{7_}_8`&`F8afa8b'b/8c78^3~9dG&dOF9eWfe_9fgfoyfE:g:h&hF:ifi:jj:kZif#vzuVd>mAFs 8NVnӶb[?|_|]Nfǟ+w-Bq/OtTbgvk9`w~]yo:z?ZgZ{{|Pl!A˟~{C_}݇\`9}/ ^1sD@b+`4kJb㓼6=n3~ѓ1lH celSz-ܚ&b8nN핯!.v_sk$?5bi)_U)zՋBEU#y^?վNK{Zu6I#\h5#M\JġA\D7 dD-)iqpŌFaf Ws%nwI&4␞--a6­t$ϖN/&34dL ujޗc(ϖ<Ln Xa,J%~׺,mOo={=u`l,/ C|blkc ty\y<Ȟ(ε󗹕)QCjE3]ito|%M&u:Kʥ[]lb]]eY^4#S {n:8f.oeL_VXi\{NM,Zn{e3/6]:͝&aK}uy$uЈ>]C~ CPTqKW{gKojȃ}cĤE+J;jdX>blN):3:7B[(qr/+@*UZ/:)[7+6L;djY/w@;@) 3A s@Atce+{Z>|==ss[ , B<9,/'d&”`3-d424;*|<:0lB{AXC?h5 Ķ!0N;BCڴGRJD63 B#1N:Gԫh(< 5{E34DXP~!ECEULT$X :O@itDA]$ *Dj4$rCpܾcA?"L_ EstCwkGTt4D{8|Y;!3DŽTTb?:zitHȊGid#rrG=4w-l=FrbGp=ǡ; ÕԊ,,˳āX@Jl!$Q,ٞ ,# zA%$>E XJJ:JOGy:|A.ht'HHvJuCJKPSZ<˚EȔH ƪDBre{[Ìǀ4K[,I1EF^c.ܛHJ3?#DtԊJL`$d[B#KCzMYͣJ˚ ̔>lN({NH}Q@)D8͵8d"4CH4@bJ25'T}#TwP|ʧoTcP~qOħ Is1b"6;|0-;LQ53'&J6L<˿u4e+ㄭ$zƅ)K݊;3\0VTXe,eY~YX!XQte@4M|ŗK +4ס9M$}XSӇR"Rk`Z+d%gZUNZ]*0{@uV3mfV MǃWUl}V] CM+0/W=?'ũieM[#z%Z,Q,U}!J] )uP]ם\J՝5m\PǐBuv! ߅N5 OX2pއ]uY(_T݁-A%}yߍ($^U_M_5)ѤX-UZ;vւax  ޾-ȢB^z\ޟNZKIaFuOz1 )5Ea{I^MYׁYku+⫻N5z'Ћ3r%]MS,Fq4%#juD.3\ME1ZKQ<+ۣc\eeL>mF4v81Bˎ TVI~(+m]MOZ[.>+HXEOP*Uғյll堺Fc~AJ|[iEevmc\ZU`yf۳206^nf̗Ngmfk_lsnP9Ų`aOf;_`RG%V|t~Xn-fbnYtģZ4hbfW֏lggzI煃DZgf^ial?]gzdw $efm߽ զ&Cj|Kee,Sr=:ejʫLEi$żF?=b[S"Rv8n~I1^n[{ꒆx!/k6uSt8ž5Fm$؟渻OqV;v[rLPcZ괾ϣ9[j6\h;mhl!gfEH1~4;>vbniAצ.LOۛ*jA2hS:9n3m'6_eznH 9%4V書fhn=!̚&rdjt?F$?3䫞r`' iWorNiN=ssY.퇁YIswEw^n}tj`.Y>1nIn}s Dc1rNOss|q!VQߎ6GuPP 4[_ לg6&wc_o&fWo0mrqtKv\wp'w{EyW{o]yco{{{T{'7GWg;PK*1,,PKH\lC&OEBPS/img/mss_action_circ_disc_det.gifGIF89aFw!,Frr%?,E3K&:Q.@W5G]=NcDUiJ~L\oScu[i{bpjwq~rrxyԛúrԺԛԺrԛrԛԛԺH*\ȰÇ#JHŋ3jȱǏ CIɓ(S\ɲ˃ ȜI͛8m@0fΟ@љC<4gҗs4hJ& V:j֩\zM5lձP``j ׶6.۹L&޴e({T 5x⠌&~ 421P̛v94 A2AV߄C!l6iێ{z HXx< ;Pzrp.ܽ+\|Bg sPs 'ǿ   MO 9 IY尔pՇ8"w&E"n)]ɡuЋhX1b88p%pDudoI]MI$nT6]VnYz+\%&wd*tsi)pmrwМiYyM)9ze{eq܉Ιɩ-뀲ƪЬ(P(rh= { z(ՊЮ&N[_1!Z0;A&3\)ea ;$Q[k/n6l$0w _frEY&wgp0Ggo!G72n%Wwl)'{rx \^0 w-}B30{J5սY{ZWȵ՚v@ DKR(PءkY=~U;7YvKen ^P߲~H~)x`&Nj1 A 9i nPZpʫ :u>;ɞǽIzn _ask]Gz A|m__s AvA~AeXG,A[{@@k^¬`HE(:b)0;< W B8 `dl.Hap=AzҹW@I-% ѕBʬ5Cp 5D 4 0MD E ,2BLwB-RQ@ػCʌp3Q6m,WG4uLCӵ }mkAA: y@VH(R D <% sy1lA|%=iǼ"ܐV ĭ{-?rptHa0+t 2dhd4{hoj+n.Ss!i1k@`szlB /qQ|T>BI(AsgЖ4ѓ})#Z͌ncl(Kd'ELG3'Ґf'Q@P q)Z$@pjA )zKޔmq@Zif Gm:ǐ!$eFjiȬ^o(1|D^&3̮y^^=P´w}_X xaBt c YL ͘FW:N?+(є0RiZXދ_uiuF|)mCcov3uM "YVreԖ 22s݂LW1%u ]h1_6M~s=č^٬ ]{ _7-LJųSu~]⡱QT#1dy2(ĶE#)*ɋucڬJ@.!SHS\%0eRngK'k1+k[ P!1?JT&/M]#- oe-oX>2ƭp~,ht^37ֵzr ܃9Nfh)G> IH{R {FWs4AQf15\S02%fbؔ%pӛrdܼtwv] /e%-bD@UPۛ¹y Ψ39d/Z9n m 9w6ׄ{:Mzη~NOEr8'N[ϸ7{ N(OW0gN8Bt9 h X0(zK^tVoJx^8w+yNw+)a:`wӀ5Hw}${G"={_|H'\@ t;^ 1we'7{x4xkwtWz` iׄFgGfxahuvul'$z*HxDw|gH{u}YW%i?p(S:ؔgX`}c}N}s aɞq4 s:oy:jp<*ʡɨKz`ڏ+v:[jzJ{Z iʡا!fW-(ZJ wQ :(SXH hoz9|g ј Z *ǩ&gNI銆D*ڡe' wrZ{ؕk0zw%yڰg7wz*bWhW4J| .x*{W<AR:ZzFhhΪz4Goqi\HZRB{p.Ȫ;kI{coGw=+gqۄzY(QL跦fuV+[sZrۡY3moۙanK陞AKz.+s~1( kk}a 빿:pXrʆ}gj[ jګ+@CxˮM sx::A1۝{ \o4[s,&3wE p,LJ'ݫ^ &$.K׸Ye{y!{3lsPZċHLo*M\ 謞יִ@,ʺu%X\:\YLг2З82wif{LъȈ\m=Ɏ܉ ʫ-ќ+ݹ<~smx.00˾y?MD=G]$ErgMȍLmI%DkZMr;pk{acpePktmp\rIզLw:m؊U  |zҔC,Ҵu׋Cؗ]W\7ץIMt-stK}MJlvm_}~w%-旤A AY)ܭr佩qM]=,]״{-~6 ^p)uؘv^,:#psw.Fҕl Mo .t\#l'3+0Y2.]8:^}V>~QA>vWRwBL7OnG>F.n+q|D; ^N=d^f~h;PKچ̈́PKH\lC$OEBPS/img/mss_action_eq_disc_det.giflGIF89a:w!,:rr%?,E3K&:Q.@W5G]=NcDUiJ~L\oScujwq~rrxyrԺԛԺrԛrԛԛԺH*\ȰÇ#JHŋ3jȱǏ CIɓ(S\R!0cʜI͛ϟ?uJL-4'ҊKJbԩXsL2WCb:Xd4{hڈl UnӷjJý|u80\#vKs/>qɔm(!9se1{9/Bѣc"]uj;۴AשkMc2u{=x#: (E~$7: PN$%oT"bC^9=&9eye%9ٙIjɠp9(y6$(C¡%УVD)uw`Ѧu)z:$A`*EΦ,z*:Q*:z+ + ){,: jCjkQIkZ ن{[w4 E.Zwy/pR/oNl7kGtpj Ch g;4qf7t1e'1d/b!+4a%$^r2g,ws9Lsa3BLGM^4K1}ӼY=ֳi-ׯym, 6Dd'tg6ErO=duwz[7p},N͛)>9IY>ijy N -]P"NXn& /)#9/I -Y y"k_cEjoŢ{[QSA1`AhqH ȗl!aE (rB@*g1uL9bQX'_i'NѡIdJ#Õ)MT#ĂL0U$Łl/]$@K:c5vQB(9"mIx=bx f\!œ-B#b" $:n2ER'KJ\@)Eɶ$`Il^ ђ@<}K /KL |1Qɢe2 OiifʱZcg &qv':fj31M{uŜY@y @oOXf!AP,4% COâ$cim,PQJ䱨A@$.1)APqH`J)NcS0:hXJѼ0Jᆚ!50IMSUL.U=IW."^%OVMŌ eE**V$P]kSoWpw]\[ÁΦ~+` TW!aK76=٭Uk RXlv4]g=Z63Mi)Z2=k[0-m[/wK5@p\ @sE Pwfʮvz xKMz%o@ͯ~LM;'L [ΰ7s b(yKaؼ 0|kL˘m2w,f2@]xl8Ϲv^g$t6vM$43f-zv#-Iy7@jg#Sw[Z! ~ok\c,k3 b}M&pvmE?8h#w>eq ܪ.e^&ᅷjNIlm@yFvvp[Esrsoxq@<S/x;.y2aq6C]i WF7mBo<0S0 ꖴ WxU =i#>{Ľ=/oxw8}wiC{遗%~'6wkǷDvfKy߅۱~Q6w3GjGyQ[X>={T-{1^N ӷny]q#x778mr ~-\'I9UC=ځ>k֓y ~[Ϋjwfj^ywv {-t^']%|rxAvdVO G*`,(84XAyՀgcȃ7$`guE`h恫qFuw%h0G^vXh{6TGķ]wWwvw|vey'Apg]'yr؆yx8cw~gj_U~bFc~v Xdx}G{3j7|sLj^F6c^2ȃf\yr6t؈qavs7n$FAezZ'qtjp(߶`oHvȊ_ƌኻHX|ݘ],v*&UFrmH G(v老jYXr-Xawx r|'8} ~KxtmpǑy#U}ilfH}*ivf|(z:Y]qBK؄]xLIW+Ƀ`G7);ys208]Avd&tq)e|ǒdXvٓ/ؗ1Ygcۇ~wa(lnv"hi%y#77a|i8g/鏝FWhu5smIׇEy1(~GdYXy'֒ Z8ɑ{PV9G fYP)gwcX"){hih9y#jxɕvE6 *^)9p_n :^)y:+=<h)jTZv՛;H֙ w8<ڣ>%'b.IբPH*rFM QoSZXMZ}+5b:d:z'jj ڦi adoJ!dƈ|ڧrؔ`&Vw* lj'LJ]AʛhWʖ:Tɦ atj74sڪZz;PK6qlPKH\lC!OEBPS/img/mss_action_disc_res.gifGIF89a^w!,^rr%?,E3K&:Q.@W5G]=NcDUiJ~L\oScu[i{bpjwq~rrxyԛúrrԺԛԺrԛrԛԛԺH*\ȰÇ#JHŅ hȱG z(I!G\ RdB,c|L0ky`:YbP3ʡ 5ҥ 5*QU;JiDV\(cرe͊MH6ljmZ\ Bk½r*VpBi #D\VA_H_ +_lY.愚=s ϓ ,J_MڳoK; n-\8r,*l7ں| \?XٿUb|Mcʥ)in}% ٵ|rnzijea.\n4бiK[b)P_q@gYY'Ui'Py (KK(F|!`bAB5oBu/BA~o=0ST¥pZpY9WB mj'q ,rXNKL,%,ټ%\&yـ_$4t-WtH㩴[LpVKUeM/_^ q U--g%BmWBqC5wBu/u7ByA}ٱP\W9I^QB u>瞇6`t^x|ʞ^ナvB˅AŻuAE@͗|A5}j|mOw=/.dB~B>B5AuAo&e 1[q`Y x ~|*o'?6d BЄei(CиhZ0 hRg=&TI.qQ`*NpS"As9TBǝG%jR%{./1ޓjlSŪ?Ҋl*kif1kU:B=Y&IgғpT+3WWܵ%AEܺ !Q kKұu cSSJ`,)3KIbҳmzą_1I[Պ1q a٪+ER;~mp8\bVZF2ͅs]T ZKւh+D%իIzҽj$]-#2ߪEH_.-y<ȁ˒`,+ .ȃ {\r2A=B DCْ.ٔN))("Q9UWIkY^ٕ \ @Pc/@;%gkٖ+lhYqpysv)xuIG9i*)Yɔ )yI7@8) Y9ٙ9yً>)P~ i QɛXb0ɋA.)-YҙIXݙ 6Ɋ멞i+ҞO9陟x/#i$)%Eّ zi*j-:yʊt꧈ )^:Z`ωX*ɫ,: j} ߹Jz$k*gɢ$窌zJQ:i͸ᘧ19ʰ+ѺZK0 *I 믓"Z}Z1ʮ Ij!ʳ꧞jڡ8E2*IG+)ۮVJ *X\{ڬI:a˨: j*Jo *z| (KZ ;(yyɦp+L@[RZ q" TK۰θs-+{K*kC[k[ҢޚëY zڷkK&`{۸ {x[EY[; {k% |{[(ʽA(ض;=!S{o N#,5˓+v-1<=;ɝ< yѡ9,* BzA LL/l;U a ھcŔ{`moLʫƼ8!,zlík,\Ƅ\Ȇ|z~L tȳM늘Y+#J0 ,%_ Xh YiÑg˦|dn̠|yZ͸Wܽp̰,͸h{\#͈6|ɚ ټHh,黇;P+?iɄ<JUl< ] Q=-=5i;Nɼ907ζ(YK9*+/4-.9 <_lӜ[p, ^`O\ІܙB-H-a)dIֿ-lմHɗqzֺqik6ٚ ˘uMf\Mʲ9ϡ-׷̙ I`*)9|-QhY̵mp QLЦM׍"]pY{"3API-7mK' ݒٹ|Ֆ ~,|5 M+Hힷ͎+^{mn >EMξ$ Gޝ^'6YQٙ .iq;0X.9MҾ ɫ؇~潻m߶[{׳<}xJܮYΚh\N8≚n΋=]~޾MkYގ/.#˃< q=ق,ᅍqݒ"^(Q7 Dne)ꡌ:Pn7m! *L =슎)_-l hMV2.H۬>.Ylա.ޞy)̏~Ӽ.L9ގ*nN$iAΙ;m <ƞnRLŠ̂ܫx, )*)nM*l%6=95yNʺyP'`[}I!&Y nOϸܡ6[/r螣|v p;/ \_yԹ}#/]\ zO_|*͎ F ?Jhp*2"/{(3Õ̺ NI zGcDi'$vL^9O}&29PE-5Pt,k!9O)A1;^K̊DB4QP2IHIz$5ND:Wz'xzT3e8~ԧ?jTbġ)jRCrѼ)թ.Ԡ*W}VqU֔XW:Vլ= ;PKn>PKH\lC)OEBPS/img_text/mss_action_eq_disc_det.htm Description of the illustration mss_action_eq_disc_det.gif

processors belonging to the equipment discrepancy detection action

PKh;PKH\lC+OEBPS/img_text/mss_action_circ_disc_det.htm Description of the illustration mss_action_circ_disc_det.gif

processors belonging to the circuit discrepancy detection action

PK<{PKH\lC OEBPS/toc.ncx 5 Oracle® Communications Network Integrity MSS Integration Cartridge Guide, Release 7.1 Cover Table of Contents Oracle Communications Network Integrity MSS Integration Cartridge Guide, Release 7.1 Preface Overview About Cartridge Components Cartridge Usage About Collected Data About Cartridge Modeling Design Studio Construction Design Studio Extension Copyright PKཊ* PKH\lCOEBPS/mss_overview.htmt Overview

1 Overview

This chapter gives an overview of the Oracle Communications Network Integrity MSS Integration cartridge.

About the MSS Integration Cartridge

The MSS Integration cartridge is used to integrate Network Integrity with Oracle Communications MetaSolv Solution (MSS), to retrieve inventory data from MSS, and to compare the imported data with discovered network data.

You can use the MSS Integration cartridge to perform the following types of actions:

  • Import: This action retrieves specified equipment and circuit information from MSS and models it in the Oracle Communications Information Model.

  • Discrepancy Detection: This action compares the imported MSS data with the results of an Assimilation or Discovery scan action type and reports any differences.

  • Resolution: This action resolves discrepancies on equipment and circuits by correcting entities, associations, and attributes in MSS.

See "MSS Integration Cartridge Actions" for more information.

Limitations

The MSS Integration cartridge has the following limitations:

  • Network Node Resolution: The MSS CORBA createNetworkElement API method is run by the Resolve in MSS action to create a network nodes in MSS. You must use MSS to search for the created node, manually updating it with the type and associating it with the network system, which allows later resolution actions to create equipment and hierarchies under the new node. Network Integrity cannot upload entire equipment hierarchies under a new network node with a single Resolve in MSS action. Subsequent discrepancy detection actions are likely to detect new entity+ discrepancies on the child entities of the new network node.

  • Port Resolution: There is no API support to create or delete ports. The ports associated to card equipment are obtained from the equipment specification. There is no API support to update MSS equipment. Therefore, Network Integrity cannot resolve entity+ or entity- discrepancies on ports. You must manually resolve such discrepancies from MSS.

  • Partial Circuits: The MSS Integration cartridge cannot resolve discrepancies on partial circuits from Network Integrity. Network Integrity assigns the Ignored state to discrepancies on partial circuits.

  • Network Integrity cannot detect discrepancies on all Information Model fields. See "Field Mapping" for a list of tables listing the fields used for discrepancy detection.

  • The MSS Integration cartridge suppresses discrepancies on empty slots and sub-slots.

  • Rack, shelf, and card hierarchy: MSS does not follow a consistent standard for identifying equipment types. Therefore, the MSS Integration cartridge uses a logical algorithm for modeling equipment. See "Data Import Algorithm" for more information.

  • For discrepancy resolution on customer circuits to work properly, the MSS instance service type configuration must be aligned with customer circuit bandwidth. Possible customer circuit bandwidths in SDH networks are E1, E3, and E4. MSS service type configuration defines the circuit auto-build source higher bandwidth to target lower bandwidth. Network Integrity cannot define multiple service type definitions with same source higher bandwidth to different target lower bandwidths.

    Table 1-1 lists the service type configurations for each customer circuit type.

    Table 1-1 Service Type Configurations for Customer Circuit Types

    Circuit TypeFirst Level Service TypeSecond Level Service TypeThird Level Service TypeFourth Level Service Type

    E1

    STMX-VC4 (X=1, 4, 16)

    VC4-TUG3 (Pos=3)

    TUG3-VC12 (Pos=28)

    VC12-E1 (Pos=1)

    E3

    STMX-VC4

    VC4-TUG3 (Pos=3)

    TUG3-VC3 (Pos=3)

    VC3-E3 (Pos=1)

    E4

    STMX-VC4

    VC4-E4 (Pos=1)

    N/A

    N/A



    Note:

    SDH network standards expect the service type position definition for a TUG3-VC12 circuit to be 21. However, MSS models TUG3-VC12 circuits with a position value of 28. The mssTUG3VC12ChannelPositionsCount MBean attribute is set to 28 to align Network Integrity with the way MSS models this circuit.

  • When uploading customer circuits to MSS to resolve discrepancies, Network Integrity sets the Customer Account ID and Product Catalog ID a configurable, static value. You must use MSS to manually assign uploaded circuits with the correct Customer Account ID and Product Catalog ID. Configure the MSS Customer Account ID and MSS Product Catalog ID MBean attributes to set the static value that Network Integrity assigns to uploaded customer circuits. See "Setting Up Cartridge MBeans" for more information. The Customer Account ID and MSS Product Catalog ID values must be valid values taken from the MSS database.

  • In MSS, it is possible to model a fully-protected HOT circuit two different ways:

    • As a single HOT between two devices, connected by two paths

    • As two separate unprotected HOTs between two devices

    By default, the MSS Integration cartridge matches against two separate unprotected HOTs between two devices.

    To match against fully-protected HOTs modeled as a single HOTs between two devices, connected by two paths, you can do one of the following:

    • Extend the Import from MSS action to separate protected HOT circuits into two unprotected HOT circuits. The protected HOT circuits must not have the same originating or terminating port.

    • Extend the Assimilate Optical Circuits action on the Network Integrity Optical Circuit Assimilation Cartridge, adding a processor to find separate HOTs that should be merged, modeling them as single HOTs with multiple paths.

    If you extend the assimilation or the import action, you must also extend your discrepancy resolution actions to understand the extended circuit model.

Dependencies

The MSS Integration cartridge has the following dependencies.

Run-Time Dependencies

For the MSS Integration cartridge to work at run time, the following dependencies must be met:

  • MSS 6.2 or later must already be installed.

    • MSS must be configured with the MSS Extract Schema. The MSS database must be populated using the extraction script.

  • Network Integrity must be configured with a database connection to the MSS Extract Schema.

    • The data source for the MSS Extract Schema must be created in the Network Integrity WebLogic server domain.

  • Network Integrity must be configured with the common object request broker architecture (CORBA) Name Service details.

  • Network Integrity must be configured with Enterprise Java Bean (EJB) connection details.

Design Studio Dependencies

To build the MSS Integration cartridge in Oracle Communications Design Studio, the following cartridges are required in Design Studio:

  • Base Detection Cartridge

  • Optical Model Cartridge

  • TMF814 Model Cartridge

  • (Optional) Network Integrity Optical TMF814 CORBA cartridge, including all its dependencies: required if you want the ability to reconcile MSS data with productized Optical TMF814 Discovery data.

  • (Optional) Network Integrity Optical Circuit Assimilation cartridge, including all its dependencies: required if you want the ability to reconcile MSS data with productized Optical Circuit Assimilation data.

Configuration Dependencies

This section describes the necessary configurations you must perform before you can use the MSS Integration cartridge.

Configuring the JDBC Data Source Driver

  1. Log in to the Oracle WebLogic Server Administration Console for Network Integrity using administrator credentials.

  2. Under JDBC, select Data Sources.

    The Summary of JDBC Data Sources screen appears.

  3. Click the New button.

    The Create New Data Source screen appears.

  4. Do the following:

    1. In the Name field, enter a name.

    2. In the JNDI Name field, enter a unique JNDI name to be used by Network Integrity. For example, jdbc/NIMSSDatasource.

    3. In the Database Type field, enter Oracle.

    4. In the Database Driver field, select Oracle's Driver (Thin) for service connections; Versions:9.0.1,9.2.0,10,11.

  5. Click Next.

    The Transaction Options screen appears.

  6. Do the following:

    1. Select the Support Global Transaction check box.

    2. Select the Emulate Two-Phase Commit option.

  7. Click Next.

    The Connection Properties screen appears.

  8. Do the following:

    1. In the Database Name field, enter the SID or service name of the database.

    2. In the Host Name field, enter the IP address or host name of the system on which the database running.

    3. In the Port field, enter the port number used to communicate with the database.

    4. In the Database User Name field, enter the database user name.

    5. In the Database User Password field, enter the database user password.

  9. Click Next.

    The Test Database Connection screen appears.

  10. Click the Test Configuration button.

    The console displays a success or failure message.

  11. Click Next.

  12. Select the check box corresponding to the target server.

  13. Click Finish.

    The data source is created.

Configuring MSS as the Import System

To enable Network Integrity to import data from MSS, MSS must be configured as the import system in Network Integrity.

To set MSS as your import system:

  1. In Network Integrity, in the Tasks pane, click Manage Import Systems.

    The Import System screen appears.

  2. Click the Create or Edit icon.


    Note:

    The Create icon is available only if no import system is configured. The Edit icon is available only if an import system is already configured.

    The Edit Import System dialog box appears.

  3. Do the following:

    1. In the Name field, enter a name for your import system.

      For example, MSS.

    2. In the Address field, enter the unique JNDI name for the JDBC data source.

      For example, jdbc/NIMSSDatasource.

      See "Configuring the JDBC Data Source Driver" for more information.

    3. Click Save and Close.

Adding JacORB JAR Files to the Cartridge Project

The Discrepancy Resolution action uses a third-party object request broker (ORB) called JacORB to establish CORBA connectivity with MSS. The JacORB JAR files must be manually added to the /lib directory of the cartridge project.

To add the JacORB JAR files to the cartridge project:

  1. Download version 2.3.1 of JacORB from the JacORB Web site:

    http://www.jacorb.org

  2. Open the JacORB ZIP file and extract the following JAR files from the /lib directory:

    • slf4j-api-1.5.6.jar

    • slf4j-jdk14-1.5.6.jar

    • jacorb.jar

    • logkit-1.2.jar

  3. Copy the extracted JAR files to the MSS_Cartridge/lib cartridge project directory.

  4. Add the JacORB JAR files to the cartridge project classpath:

    1. In Design Studio, switch to the Navigation perspective.

    2. Right-click MSS_Cartridge and select Properties.

      The Properties for MSS_Cartridge dialog box appears.

    3. In the Navigation pane, click Java Build Path.

    4. On the Libraries tab, click the Add JARs button.

      The Add JARs dialog box appears.

    5. Select the new JacORB JAR files and click Add.

      The new JacORB JAR files are added to the JARs and class folders on the build path list.

    6. Click OK.

      The Properties for MSS_Cartridge dialog box closes.

    7. Save the project.

Setting Up Cartridge MBeans

The MSS Integration cartridge uses generic Network Integrity MBeans to communicate discrepancy resolution commands with MSS. These MBeans contain property groups and properties configured with model variables. The default values are set when the cartridge is deployed. You must use Enterprise Manager to define the MBeans.

The configured MBean values are set in the MSS CORBA Properties Initializer processor during run time.

See Network Integrity System Administrator's Guide for information about setting MBeans using Enterprise Manager.

Table 1-2 lists the generic Network Integrity MBeans used to communicate with MSS. Set each MBean with the value required to connect the cartridge to your MSS system.

Table 1-2 Cartridge MBeans Required for Discrepancy Resolution

Attribute NameProperty GroupMBean Property Name

MSS CORBA Password

Resolve in MSS:MSS CORBA Property Initializer:MSSCORBAConnectionDetails

MSSCORBAPassword

Required to establish the MSS CORBA connection for MSS equipment upload.

Use the runPropertyEncryptor.sh script to encrypt this property. See Network Integrity System Administrator's Guide for more information.

MSS CORBA IOR

Resolve in MSS:MSS CORBA Property Initializer:MSSCORBAConnectionDetails

MSSCORBAIOR

Required to establish the MSS CORBA connection for MSS equipment upload.

MSS CORBA UserId

Resolve in MSS:MSS CORBA Property Initializer:MSSCORBAConnectionDetails

MSSCORBAUserId

Required to establish the MSS CORBA connection for MSS equipment upload.

MSS EJB JNDI Name

Resolve in MSS:MSS CORBA Property Initializer:MSSEJBConnectionDetails

MSSEJBJNDIName

Required to establish the MSS EJB connection for MSS circuit upload.

MSS EJB URL

Resolve in MSS:MSS CORBA Property Initializer:MSSEJBConnectionDetails

MSSEJBURL

Required to establish the MSS EJB connection for MSS circuit upload.

MSS EJB UserId

Resolve in MSS:MSS CORBA Property Initializer:MSSEJBConnectionDetails

MSSEJBUserId

Required to establish the MSS EJB connection for MSS circuit upload.

MSS EJB Password

Resolve in MSS:MSS CORBA Property Initializer:MSSEJBConnectionDetails

MSSEJBPassword

Required to establish the MSS EJB connection for MSS circuit upload.

Use the runPropertyEncryptor.sh script to encrypt this property. See Network Integrity System Administrator's Guide for more information.

MSS Customer Account ID

Resolve in MSS:MSS CORBA Property Initializer:MSSEJBConnectionDetails

MSS Customer Account Id

Used to assign customer circuits created by Network Integrity to a customer account.

MSS Product Catalog ID

Resolve in MSS:MSS CORBA Property Initializer:MSSEJBConnectionDetails

MSS Product Catalog Id

Used to specify the catalog reference for customer circuits created by Network Integrity.

MSS TUG3-VC12 Channel Positions Count

Resolve in MSS:MSS CORBA Property Initializer:MSSEJBConnectionDetails

mssTUG3VC12ChannelPositionsCount

Used to specify the number of positions in MSS service type defined for TUG3 to VC12.

Enable Container Resolution

MSS Circuit Discrepancy Detection:Partial Circuit Discrepancy Filter:ResolutionProperties

enableContainerResolution

Set to false and is used to not display discrepancies on container entities in Network Integrity. Network Integrity cannot resolve discrepancies on containers.

Enable STM Resolution

MSS Circuit Discrepancy Detection:Partial Circuit Discrepancy Filter:ResolutionProperties

enableSTMResolution

Set to false and is used to not display discrepancies on STMs in Network Integrity. Network Integrity cannot resolve discrepancies on STMs.

Enable HOT Resolution

MSS Circuit Discrepancy Detection:Partial Circuit Discrepancy Filter:ResolutionProperties

enableHOTResolution

Set to false and is used to not display discrepancies on HOTs in Network Integrity. Network Integrity cannot resolve discrepancies on HOTs.


Password properties should be encrypted using the runPropertyEncryptor.sh script. See Network Integrity System Administrator's Guide for more information about encrypting properties.

When encrypting MBean properties, you must enter the property name as it appears in the MBean Property Name column of Table 1-2. For example, enter MSSCORBAPassword when encrypting the MSS CORBA Password attribute.

Downloading and Opening the Cartridge Files in Design Studio

To open, view, and extend the MSS Integration cartridge, you must first download the cartridge ZIP file from the Oracle software delivery Web site:

https://edelivery.oracle.com

The MSS Integration cartridge ZIP file has the following structure:

  • Base_Detection_Cartridge

  • MSS_Cartridge

  • Optical_Model

  • TMF814_Model

The MSS_Cartridge project contains the extendable Design Studio files.

See Network Integrity Concepts for guidelines and best practices for extending cartridges. See Network Integrity Developer's Guide for information about opening files in Design Studio.

Compiling and Deploying the Cartridge

To compile and deploy the MSS Integration cartridge, you must first add JacORB JAR files to the cartridge project. See "Adding JacORB JAR Files to the Cartridge Project" for more information.

For information about compiling cartridges, see Network Integrity Developer's Guide.

For information about deploying cartridges using Design Studio, see Network Integrity Developer's Guide. For information about deploying cartridges using the Cartridge Deployer Tool, see Network Integrity Installation Guide.

PKI ttPKH\lCOEBPS/content.opfX Oracle® Communications Network Integrity MSS Integration Cartridge Guide, Release 7.1 en-US E23716-01 Oracle Corporation Oracle Corporation Oracle® Communications Network Integrity MSS Integration Cartridge Guide, Release 7.1 2012-01-18T23:17:11Z Oracle® Communications Network Integrity MSS Integration Cartridge Guide, Release 7.1 PKu:]XPKH\lCOEBPS/dcommon/prodbig.gif GIF87a!!!)))111BBBZZZsss{{ZRRcZZ!!1!91)JB9B9)kkcJJB991ssc絽Zcc!!{祽BZc!9B!c{!)c{9{Z{{cZB1)sJk{{Z{kBsZJ91)Z{!{BcsRsBc{9ZZk甽kBkR!BZ9c)JJc{!))BZks{BcR{JsBk9k)Zck!!BZ1k!ZcRBZcZJkBk1Z9c!R!c9kZRZRBZ9{99!R1{99R{1!1)c1J)1B!BJRkk{ƽ絵ތkk絵RRs{{{{JJsssBBkkk!!9ss{{ZZssccJJZZRRccRRZZ))cBBJJ99JJ!!c11991199Z11!c!!))Z!!!1BRck{)!cJBkZRZ,HP)XRÇEZ֬4jJ0 @ "8pYҴESY3CƊ@*U:lY0_0#  5tX1E: C_xޘeKTV%ȣOΏ9??:a"\fSrğjAsKJ:nOzO=}E1-I)3(QEQEQEQEQEQEQE֝Hza<["2"pO#f8M[RL(,?g93QSZ uy"lx4h`O!LŏʨXZvq& c՚]+: ǵ@+J]tQ]~[[eϸ (]6A&>ܫ~+כzmZ^(<57KsHf妬Ϧmnẁ&F!:-`b\/(tF*Bֳ ~V{WxxfCnMvF=;5_,6%S>}cQQjsOO5=)Ot [W9 /{^tyNg#ЄGsֿ1-4ooTZ?K Gc+oyڙoNuh^iSo5{\ܹ3Yos}$.nQ-~n,-zr~-|K4R"8a{]^;I<ȤL5"EԤP7_j>OoK;*U.at*K[fym3ii^#wcC'IIkIp$󿉵|CtĈpW¹l{9>⪦׺*ͯj.LfGߍԁw] |WW18>w.ӯ! VӃ :#1~ +މ=;5c__b@W@ +^]ևՃ7 n&g2I8Lw7uҭ$"&"b eZ":8)D'%{}5{; w]iu;_dLʳ4R-,2H6>½HLKܹR ~foZKZ࿷1[oZ7׫Z7R¢?«'y?A}C_iG5s_~^ J5?œ tp]X/c'r%eܺA|4ծ-Ե+ْe1M38Ǯ `|Kյ OVڅu;"d56, X5kYR<̭CiطXԮ];Oy)OcWj֩}=܅s۸QZ*<~%뺃ȶp f~Bðzb\ݳzW*y{=[ C/Ak oXCkt_s}{'y?AmCjޓ{ WRV7r. g~Q"7&͹+c<=,dJ1V߁=T)TR՜*N4 ^Bڥ%B+=@fE5ka}ędܤFH^i1k\Sgdk> ֤aOM\_\T)8靠㡮3ģR: jj,pk/K!t,=ϯZ6(((((((49 xn_kLk&f9sK`zx{{y8H 8b4>ÇНE|7v(z/]k7IxM}8!ycZRQ pKVr(RPEr?^}'ðh{x+ՀLW154cK@Ng C)rr9+c:׹b Жf*s^ fKS7^} *{zq_@8# pF~ [VPe(nw0MW=3#kȵz晨cy PpG#W:%drMh]3HH<\]ԁ|_W HHҡb}P>k {ZErxMX@8C&qskLۙOnO^sCk7ql2XCw5VG.S~H8=(s1~cV5z %v|U2QF=NoW]ո?<`~׮}=ӬfԵ,=;"~Iy7K#g{ñJ?5$y` zz@-~m7mG宝Gٱ>G&K#]؃y1$$t>wqjstX.b̐{Wej)Dxfc:8)=$y|L`xV8ߙ~E)HkwW$J0uʟk>6Sgp~;4֌W+חc"=|ř9bc5> *rg {~cj1rnI#G|8v4wĿhFb><^ pJLm[Dl1;Vx5IZ:1*p)إ1ZbAK(1ׅ|S&5{^ KG^5r>;X׻K^? s fk^8O/"J)3K]N)iL?5!ƾq:G_=X- i,vi2N3 |03Qas ! 7}kZU781M,->e;@Qz T(GK(ah(((((((Y[×j2F}o־oYYq $+]%$ v^rϭ`nax,ZEuWSܽ,g%~"MrsrY~Ҿ"Fت;8{ѰxYEfP^;WPwqbB:c?zp<7;SBfZ)dϛ; 7s^>}⍱x?Bix^#hf,*P9S{w[]GF?1Z_nG~]kk)9Sc5Ո<<6J-ϛ}xUi>ux#ţc'{ᛲq?Oo?x&mѱ'#^t)ϲbb0 F«kIVmVsv@}kҡ!ˍUTtxO̧]ORb|2yԵk܊{sPIc_?ħ:Ig)=Z~' "\M2VSSMyLsl⺿U~"C7\hz_ Rs$~? TAi<lO*>U}+'f>7_K N s8g1^CeКÿE ;{+Y\ O5|Y{/o+ LVcO;7Zx-Ek&dpzbӱ+TaB0gNy׭ 3^c T\$⫫?F33?t._Q~Nln:U/Ceb1-im WʸQM+VpafR3d׫é|Aү-q*I P7:y&]hX^Fbtpܩ?|Wu󭏤ʫxJ3ߴm"(uqA}j.+?S wV ~ [B&<^U?rϜ_OH\'.;|.%pw/ZZG'1j(#0UT` Wzw}>_*9m>󑓀F?EL3"zpubzΕ$+0܉&3zڶ+jyr1QE ( ( ( ( ( ( ( (UIdC0EZm+]Y6^![ ԯsmܶ捆?+me+ZE29)B[;я*wGxsK7;5w)}gH~.Ɣx?X\ߚ}A@tQ(:ͧ|Iq(CT?v[sKG+*רqҍck <#Ljα5݈`8cXP6T5i.K!xX*p&ќZǓϘ7 *oƽ:wlຈ:Q5yIEA/2*2jAҐe}k%K$N9R2?7ýKMV!{W9\PA+c4w` Wx=Ze\X{}yXI Ү!aOÎ{]Qx)#D@9E:*NJ}b|Z>_k7:d$z >&Vv󃏽WlR:RqJfGإd9Tm(ҝEtO}1O[xxEYt8,3v bFF )ǙrPNE8=O#V*Cc𹾾&l&cmCh<.P{ʦ&ۣY+Gxs~k5$> ӥPquŽўZt~Tl>Q.g> %k#ú:Kn'&{[yWQGqF}AЅ׮/}<;VYZa$wQg!$;_ $NKS}“_{MY|w7G!"\JtRy+贾d|o/;5jz_6fHwk<ѰJ#]kAȎ J =YNu%dxRwwbEQEQEQEQEQEQEQEQEQE'fLQZ(1F)hQ@X1KEQE-Q@ 1KE3h=iPb(((1GjZ(-ʹRPbR@ 1KE7`bڒyS0(-&)P+ ڎԴP11F)h&:LRmQ@Q@Š(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((&xǧ[]eid!~Bz0̼q?Y}m vZ3]A`QphNযtPJ$j@WB3(,w$Wۼ#m3fvx\V|Z7ۼVOmc991JM.5ӪhnV 2Bq}jQYWcag]E7dtbS Y3h$#`pÃ(NM[MTKPMBdLW^yTH[;J g Ҿfl~g6;:6(zepZZǍO $< UwGVǙKfs'hBjnnic8EeK` cW(ǫijiqjBYʋ,2GqD.hɾ+FD򩜑 v>r?i_n|}?3ݛss[NVu {-B{Gs3+-0ʑ}*q<7x&7Q1i7vP r0?/€ +xV+{O+8fv'$+r +xV[{9/VF[ +r +ψn'bj C9L6`V1#f~oNc%K9v4%VZ8fWh[$a9S#UxoH4M_~ncoڠa~_c]V=<7Gga *L v$A@tH5_dkt$n8g{ZLt}oloydIvg8q4(mn%. 9I#%d`pAdI19(=~E<;<75r.F̣fSe6WW~GCj֚]E3Nfq9^d)8k(ý{I5<{W+mq~7ggq*Sȱ2#wpʑǞĹxSv9xKƑe,Sϔ&Q($wZ>wi'үc*YFRCJ q]$:DtῆOt{oxOzBFo%$qC*q% @Wohtr{yK$#(?1V r~cyZ襯?'u@49KÚ47R[ 1Ri#y;2@<îY}3rYZZk}P3cd-@'u^@>|(ᨥM֏8EICyWVdU*W6CZge!% Zdtwbۀ!J2 9g'dQQG<+;IaXT5X=jM9*_q,~)x*CV>!2*ΘTŝņ=:*?ְ(hsxׇ4hnzbG!FwNey1\ >x_5Ŭ{''Dx#W7 8;VLj|'`?о 9,-gGw1rG o_xg}0 $Tc*C²訨A%wG9QB/V3hQ-֬'$ĠcbX(ŏP'Tۊ{|pO_#[[K*6sG*\(%hey^_'ߍ7g=tׅt|4uY6 H2unYI#1#?c+;i^OmJqyy߻Í⸿zm4]>b86жFPs7_{Mm2[t!W^n#TUQ}NJJɐgo5N=I9YA\ #|!մsvdzn. TE@j@Xz>t}&]?ui-^t͘gvWS@{<}Oڶy߾Ms77OZ[O}ROiOh~*7tș cLt}oloydIvg8q<?6~,GU}h;l8W*J1| ;£FVuVa>whGب'"bq]5_-44LEtbnk ;N8"?%5=UɫWfO1369cABcumӴl*PX+WQ<[oqsA*92<G(~wmdg8l۟qq]CkoQH8Ppb1 h_~E֩/xkc1 rjƷi#ukXϷ̋{&rZP{ }3N˵!7'ZϸwOgWǚb?}Jآ1<-]ij"0q؄0#h;OnҶ(17m:t-d漙r'.IĞѼ]GaY9DʞkLJr:آ#n巸9 I]H#W ??nr;y{y{mn88i^ ]c&[W7`R 3@%DžkZx{=F.<miwVV?-xGNC%<ד.@=~UEcѴGT,R_:o58b@ۦ:օg%vc|3$FeOU(kO^7KI<9 = d>Wo,y~^6n8LU(kO^7KI<9 = O~xmvMPm^H݂J*F:V ^+k ;|9șY&CG(T8ֻ(  [F%gKY%32y&\ ˒z('oikkQ2 ζ( zw]ɍ<\\>\K;v09v̊ 9UQwP{ =2;; H--c`FIŽI'Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@/P+j7֗WKKra ߦMue 7w$9brc:W?J oU;w]-|K^'x2-8;ݙ.=[RuPS)s32,00}k+/CcaSm5/5u9n Hݵl8n;qH;~&Oo!Ԯui&DŶY T#ѭuO_=u[%Q' Uo0>\i^W(-$Z6-21d].S 8|6oimu*"?Y%rrI OxRGci-跶hQ:rb cMw'>h>(Wt۽J84[olȁwʹ|1S=bvU.s4Q^2'[k&mpJܪ ',۲*|izܾcz.!HU2# rQ^w{/mI^n2@f F:7c>Y;jħ3pI`+9 c?.x+-zėhՠҼfUkpP)s⅞z喇w%Ƙ ٧˞˿^F#瑶qX5kv#:}Žy:2w;?6:MWƺ]Aht&FFC1ר=OW+q~乾Sj.F3v.PpA=y[o 6wjhsIC` s(OcH4>Ufhͷ!$ :N:Vvw"*m@T2n0YzxkMѠYۤE1hYǓ<Ԡ.em6IO~#,_iiDLv$lvcdNqW>/K1hbO.K@yN[HsgDŽ|-w'v(>Y>UЪ"=8O25 K-_&,r A#x[5Lj'3ZD~Yb'~7x_4}VD}MrI>}m(r9: duDѮ h3s5a0$◍ YVkkܦܮț*u`p)O⎥oy+RX (WIKlWBuSsddmplOr9Z5so=f#ŗe;S1rWa_ßoGb?w28$ uĞ |QZqϢ}au $:I@*XmgRg $Z}xB## +&9?^Figݥ,c MpZ7yo}yѬ&D*rWf~bnrI'<נP__iD*kb|9^Կ\Ys4=TGnxc9"5~ o- $B޸@V焾S^iRKFBa8"|U@8k㯆 jlI#TQ-$sJ_KaHrhc@cz\h>f4Jikv[)el9Aր8ڟ+';nٶ=̈qx9;| )6[]7Borqqf`6!'+*7drMz'NՌ}_69, [<R[gHM,Iluf9$I<+㫏 q%d"EycYc F d {=_g ]4K*F%Y !w$Tz' B}Br"i[s=s]p|Qc?d6FzmvwVєUU;u%Mqo$q\^mf?f p 9# t!~]%\4X|YW3NMlxGᏅ]6;N"I Bc9????6޽x+MFj>qe+l>T3GS]%|2_r:F‚d=I(V};v5 soj"As7B:jEE^\߂FK绚 n՘1U\ Aր< Ŀv,bwˤeUp ziOFzuyMʑI-B$@ڵ龵tUW!|u9uݟ|9iI<< r@;Ƈm,Z檺 吸^7ʆ2Ly# s7/ym",x64u gWtne*c rd+cWFDAyv$FF*TNw8(P'TۊIwZ[-N|+j ݸyq8$z_YuK)ZEUs '<yV?-z \khI©w=ScZo4htR{`n]Ueܬ1=+S[4:,gEv 9R 7zwp]ɝA G^/wך < E"o6B PewnIg_q,w(#*7FNNI>Q/~eWu c.UAGsU&[jrDj 6~u9<ƥs~.&{xdIXdhK8'S8ָ?gK\ΗJBx%ϒm^K)u#pIf?0b=°5٤RbN85@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@Q@S>2%yZꚁ'wo7.m=}mo/=gXSˑmÑAP'J4OX8|:ywFe8RJ((((~o|[ƙUc(FCm*0Xgqa&9z [IjfW-1Szw]ɍ<\?)//O"ּC^iqڵCv\0;qY@l,8- ;!1.I' 8$ƬQEQ\~㯷Pռg-<6}(ij7 ,,-cKGވTzpGP@OIoxHU{mZ&x6wfEF/i u .6M7\8a$~5WLzBrR\ ^qu FSPމitpڤlXpK>w6rP|sO<5`_.uO|@~X6]\Cy#(*J6nEG??z-'R56j\*|3qqr:' fJhK}tFW΂T͑@^S خ gFqZ W?>)Ԥխm:g pۈ*NOxI熿k?t>T {q)~ cg{qnCF]bcrG:ҹ :5R+SQ j隷 [?C`W ^1pz=gm?j5wzc"( SRG# <ÿ6^ uCRȲ(*\9b:n PA<x=AG<#k;Q.r 7/Mgqk> }NB镡ڎApI#޹Ox]#úusLۓ*8s _J o@4~:}fZ׾"]G-ͅQ0ȸeQݎI>qx^ˮx~/jPjK,gR!;^~Q6x+ziO볽J7A"Qnv8IG}]xK7$̠Ƥtv@g'dQP*ҵ|_jZ."-AxZXWb p={ żFaV\ILݏI5mCۿGV,,n5?VqW^HaMnvFO$T~=#߆EӌcyF@Tp[~f,@bBSΛ hֺɮh-pj2|Ŕ+7l -ie#Uaaaosv*]B>Ew\Bӂ:?Hj+]3G71h= qyJ)s70=ypp<\> u3:&XAF~bb:W$NMg]]a*b`,*$ sA5bx8zf]\sgp:0`AA~%xQ~ ZھE*gQFR~-Iy=OUjOs+)mn6rQB@at9@ç {WrxzG#"@>j)b@Ó@_K9&EɾCo7Jj:Gs|0v:V6F1~qGˆ'%5GX)*ΙGVCeby#@r?!f}QRIv#1fsXI @Q~u|AwS.o.6 nX;8LAB@g6_g;q׽c;?y']HVfwi؞4; Vnݻ ]qd/ᖗ#,b#Bg%r7/$F PJ%_5{Oīe#:)pz?K0~nw>x4msV2qvP.|C_xz?j*|wc!+[s]E/#uq{r}B{KgԧBn1;Cں(O?϶}#?7cj]Nh!8OS ~zWQ@OcF+u_G~(>! ZDXΠ0Uwn+(o^Լ/Mex]U s*O_[#h۞r1^GgR"ig8Ip|q3^co6Q<3&7#dr2 ^W?ٮ%.ܲePF'Ԛ<q~:A.tgq `FAH]ͤjyrXIq R aFO@85-+A];PUvpc99 ہb=?;?_?tvn+"a> 9ޭwϦPEPozϊEc5Ee.T't !A۵X⟍< ܾȮt0RpGd1Oុ$kj6v|$[,3|`5_\cGcumIX!~?֫rˑA-^0s@[qo,sA*H2AG9+v7gt; ]>p;]cP#J~#U~ZGZrlw`r[ ~]+ŗgu9<]>h_h;]cbZ}WYkzVGtێpI#z'u(uzn, S@-8umZd7mp]y/$:D?~*ëH8PnPmB Ua˸z\n{H"  ! GJx7:{3Ou1$z8'lQ^?UMo7\6+X㯗'\nnc7[> ypF@ BQ^o>(KXe]\pnAP6l ov?hwO>+>:Q\?2&Aiۮ0PQ99=N93~2?4irkHX̅ ;rBJM{e񿋴-O-Oު @B0UaeNX zp>5R+SQs3CPF߇ki$t,- Cl_>/Ir@.>Ŧ̪ ?8aW8.5v<:~El!80LyQ ϮW?'%Ujė.&_wW^nHAWAI=w ?J (((((((((((((((/,;BG=7.2|{%c_9^6NUGCنOA39d_ ]!EraU1˷q'+ 7ß5m[IѾ}nO  ?޿TJY=񧙦'iJ?9~VT#*zUѝ>;qj|b aݝo=%$B([SZh:JUxV}Z];el8I۴wc0(o&^XMB;fUDWGyy w?±k? 5)%p9TR*̌ǎA$>,+Rmt.{Hg.Juڬskn巸9 I]H#P?xn~m9PiY0 ap;Eyo -X驇x ʭ4I@%Xi <ۋx-.2Hyn |%ԯ>*F=Y.`I%Jo | (>7|;?}Uo'Gt3Ҭ|AO"ɦW2QvсJ{x+R𿊼c^i$踶X]"Pă= v6sayku2n#r0!G# _ClCj%2A+$ A+D6goiRZ޲o%# }2@(%$B(f"mR4)-oYnoczKAfSnH {ÿ xGn$]Z%] aڹ|* x:3rՉmqY\IǿƭONv%O 偹"# Y'ws}E&#/I$;I\ȻYq7檓Y_-,3i˸0 eR"HolMw/n4մ6Hav6@UOL9 ^xkQ0D=%yfe\0I;I{>m5CHP rs(YgakC.ʄUW-ےJBi_Z޳]躄6r`(7;ů4x-2Msd;m*ǽNpT9gZ׿5xxPI&N՚6߀9^8H4_V\[A*HFWR2"k,|Yx.? Oi ,XXL`cEY/Ɛ.0vGe۸Pm^'}{¬yF  HA^^wxOa54.!;$nvH%c V|a]Y8D~a:=p~:V/hjgg7-B# Wqn7a.|.#"7!̓*&O? vW?m+X!}h`9ى@XeC=hO}Q\M" ۏ'$ɯ3/>.k74eo^h㶒0[ !"s9'߽n|CI^^x 4x4'Zo۹ZO$M{QEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQE_??dW,y^wlnyLՊ((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((PK}}PKH\lCOEBPS/dcommon/contbig.gif`GIF87a!!!111999BBBJJJRRRccckkksss{{{skk{{ZRRRJJƽ{sZRJRJB91)kcZB9)sskZRJ1޽ƽ{{ssskkkcƵZZRccZRRJJJB{BB9991ssckkZccR))!RRB!!JJ1))99!11ƌ)1R)k֔)s1RZJR{BJs9R1J!11J1J9k{csZk!1J!)cBR9J1B)91B!cRs{!)s!){1B!k!s!{ksksckckZc9B)1!)!)BJ9B1919έƌ!!)JJcZZ{!!!1RR{JJsBBkJJ{!!9BB{1!!J9)!!Z!!c1!!kR!!s9Z!BckJs)19!!c!!ZRZ,H rrxB(Kh" DժuICiи@S z$G3TTʖ&7!f b`D 0!A  k,>SO[!\ *_t  Exr%*_}!#U #4 & ֩3|b]L ]t b+Da&R_2lEٱZ`aC)/яmvUkS r(-iPE Vv_{z GLt\2s!F A#葡JY r|AA,hB}q|B`du }00(䡆<pb,G+oB C0p/x$…– ]7 @2HFc ) @AD \0 LHG',(A` `@SC)_" PH`}Y+_|1.K8pAKMA @?3҄$[JPA)+NH I ,@8G0/@R T,`pF8Ѓ)$^$ DDTDlA@ s;PKPKH\lCOEBPS/dcommon/darbbook.cssPKPKH\lC!OEBPS/dcommon/O_signature_clr.JPG"(JFIF``C    $.' ",#(7),01444'9=82<.342C  2!!22222222222222222222222222222222222222222222222222" }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3Rbr $4%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz ?( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (?O '~MQ$Vz;OlJi8L%\]UFjޙ%ԯS;rA]5ފ<׈]j7Ouyq$z'TQuw7Ŀ KX߁M2=S'TQt?.5w'97;~pq=" ~k?`'9q6 E|yayM^Om'fkC&<5x' ?A?Zx'jß={=SßM gVC.5+Hd֪xc^)Җufz{Cީ|D Vkznq|+Xa+{50rx{|OG.OϞ~f/ xxX[2H )c+#jpUOZYX\=SG ߨC|K@;_߆'e?LT?]:?>w ڔ`D^So~xo[Ӡ3i7B:Q8 Vc-ďoi:FM292~y_*_闱YN\Fr=xZ3鳎OwW_QEzW~c]REeaSM}}Hӏ4&.E]u=gMѠ+mF`rNn$w9gMa꺢nTuhf2Xv>އ a(Û6߭?<=>z'TQuw7Ŀ KX߁M2=S'TQt?.5Kko\.8S$TOX߀Gw?Zx汴X)C7~.i6(Щ=+4{mGӭ¸-]&'t_kV*I<1)4thtIsqpQJ+> \m^[aJ5)ny:4o&QEnyAEPEEss 72,PDۢ׃K W{Wjr+wگ iM/;pd?~&?@;7E4gv8 $l'z'TQuw7Ŀ Gֱ=ɿ&G?. iR(5W*$|?w᫼gkmIbHe/_t>tg%y.l}N5[]+Mk0ĠeHdPrsst'UiC,y8`V%9ZIia|ܪvi מYG,o}+kk{YbyIeb*sAtի82zWoEK5z*o-eo;n(P u-I)4Š(HQEQEQEQEhz(X/Đ?}Bk˩ ݏrk0]4>8XzV? }6$}d^F>nU K ?Bտk_9׾x~w'ߞ  uDŽtL ؈5c-E/"|_Oo.IH쐍=i*Iw5(ںw?t5s.)+tQ2dUt5Vĺ.jZ"@IRrZƅY4ߡ_;}ų(KyQf1Aǵt?sZg+?F5_oQR&Dg߿]6FuRD u>ڿxl7?IT8'shj^=.=J1rj1Wl$얲cPx;E,p$֟ˏkw qg"45(ǛkV/=+ũ)bYl~K#˝J_כ5&\F'I#8/|wʾ_Xj Q:os^T1.M_|TO.;?_  jF?g N 8nA2F%i =qW,G=5OU u8]Rq?wr'˻S+۾.ܼ 87Q^elo/T*?L|ۚ<%<,/v_OKs B5f/29n0=zqQq(ª=VX@*J(э(f5qJN_EVǞQEOuoѕOuoa5}gO?:߂8Wא|cڽ~]N&O( (<]>͠@VQ=^~U ̴m&\խ5i:}|}r~9՝f}_>'vVֲ$~^f30^in{\_.O F8to}?${φ|#x^#^n~w=~k~?'KRtO.㌡h![3Zu*ٷճ(ԟ]z_/W1(ԟ]v~g|Yq<ז0 ; b8֮s,w9\?uEyStKaª@\,)) (!EPEPEPEPEPzѧts{v>C/"N6`d*J2gGӧWqBq_1ZuΓ\X]r?=Ey88Mp&pKtO-"wR2 K^-Z< \c>V0^@O7x2WFjs<׻kZ(<Т(OFw/6$1[:ޯԯ#q~4|,LVPem=@=YLUxӃV}AUbcUB.Ds5*kٸAeG>PJxt͝ b88?*$~@ׯD VkraiJs}Q.20x&mXξ,Z]“A-J#`+-E/"<]\a'tZGy.(|lދ~gMK OZdxDŽU9T6ϯ^<Ϡt5CZ]].t۫S=s`ڳ%8iVK:nqe+#<.T6U>zWoy3^I {F?J~=G}k)K$$;$de8*G Uӟ4Ocºw}|]4=ݣ\x$ʠms?q^ipw\"ȿPs^Z Q_0GڼU.t}ROM[G#]8wٞ ӫ87}Cgw vHȩBM55vof =A_٭`Ygx[6 P,5}>蚊(0(+?>+?> k|TuXq6_ +szk :u_ Z߶Ak_U}Jc2u/1[_»ݸG41-bሬ۴}}Eȹפ_c?5gi @cL\L<68hF_Ih>X4K7UТ sMj =J7CKo>Օ5s:߀t ~ηaٿ?|gdL8+gG%o?x`دOqȱwc¨&TW_V_aI=dpG!wu۞սZ1yL50$(l3(:~'ַo A}a3N*[0ǭ HKQV}G@֜$ 9of$ArNqUOgË05#m?D)^_h//5_/<?4}Jį+GkpG4"$ r| >S4Ђ"S 1%R:ȝ 8;PKPz PKH\lCOEBPS/dcommon/feedback.gif7GIF89a'%(hp|fdx?AN5:dfeDGHɾTdQc`g*6DC\?ؘ||{;=E6JUՄfeA= >@,4`H.|`a (Q 9:&[|ځ,4p Y&BDb,!2@, $wPA'ܠǃ@CO~/d.`I @8ArHx9H75j L 3B/` P#qD*s 3A:3,H70P,R@ p!(F oԥ D;"0 ,6QBRɄHhI@@VDLCk8@NBBL2&pClA?DAk%$`I2 #Q+l7 "=&dL&PRSLIP)PɼirqМ'N8[_}w;PK-PKH\lCOEBPS/dcommon/booklist.gifGIF89a1޵֥΄kZ{Jk1Rs!BZ)B),@I9Z͓Ca % Dz8Ȁ0FZЌ0P !x8!eL8aWȠFD(~@p+rMS|ӛR$ v "Z:]ZJJEc{*=AP  BiA ']j4$*   & 9q sMiO?jQ = , YFg4.778c&$c%9;PKː5PKH\lCOEBPS/dcommon/cpyr.htm Oracle Legal Notices

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2013, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Oracle Logo

PKSPKH\lCOEBPS/dcommon/masterix.gif.GIF89a1ޜΌscJk1Rs!Bc1J),@IS@0"1 Ѿb$b08PbL,acr B@(fDn Jx11+\%1 p { display: none; } /* Class Selectors */ .ProductTitle { font-family: sans-serif; } .BookTitle { font-family: sans-serif; } .VersionNumber { font-family: sans-serif; } .PrintDate { font-family: sans-serif; font-size: small; } .PartNumber { font-family: sans-serif; font-size: small; } PKeӺ1,PKH\lCOEBPS/dcommon/larrow.gif#GIF87a絵ƌֵƽ{{ss֜ƔZZ{{{{ZZssZZccJJJJRRBBJJJJ991111))!!{,@pH,Ȥrl:ШtpHc`  өb[.64ꑈ53=Z]'yuLG*)g^!8C?-6(29K"Ĩ0Яl;U+K9^u2,@@ (\Ȱ Ë $P`lj 8x I$4H *(@͉0dа8tA  DсSP v"TUH PhP"Y1bxDǕ̧_=$I /& .)+ 60D)bB~=0#'& *D+l1MG CL1&+D`.1qVG ( "D2QL,p.;u. |r$p+5qBNl<TzB"\9e0u )@D,¹ 2@C~KU 'L6a9 /;<`P!D#Tal6XTYhn[p]݅ 7}B a&AƮe{EɲƮiEp#G}D#xTIzGFǂEc^q}) Y# (tۮNeGL*@/%UB:&k0{ &SdDnBQ^("@q #` @1B4i@ aNȅ@[\B >e007V[N(vpyFe Gb/&|aHZj@""~ӎ)t ? $ EQ.սJ$C,l]A `8A o B C?8cyA @Nz|`:`~7-G|yQ AqA6OzPbZ`>~#8=./edGA2nrBYR@ W h'j4p'!k 00 MT RNF6̙ m` (7%ꑀ;PKl-OJPKH\lCOEBPS/dcommon/index.gifGIF89a1޵ΥΥ{sc{BZs,@IM" AD B0 3.R~[D"0, ]ШpRNC  /& H&[%7TM/`vS+-+ q D go@" 4o'Uxcxcc&k/ qp zUm(UHDDJBGMԃ;PK(PKH\lCOEBPS/dcommon/bookbig.gif +GIF89a$!!!)))111999BBBJJJRRRZZZccckkksss{{{skkB991)))!!B11))1!JB9B9!!cZ9ƭƽssk{ZZRccZRRJJJBBB9c!!ν)1)k{s絽ƌkssֽZccJRRBJJ{9BB)11)99!!))11!!k!JZ!)RcJccBcs)1c)JZ!BR!)BZ)99J!Rk9!c11B)Z{)9Bkc1kB9BZ!Z{9Rs)Jkksk9kB1s1Jk9Rƥc{k9s)Z{1k91)s1Rk)Jc1J!))BZ!1k{csc{)19B!)Bcsc{ksc{kZs!RkJkJkքc{9Zks{ck9R)Bks9R9R1J!)Z1B!)c)9)99BR19kksBBJcc{ccBBZ))9kk!!199c11ZBB{9!!R!!Z!!c))!!kR!!s!!BcksRZ1c9B)R91c1)Z!R9B9k1)RcZ{)!1B9JB9B)!)J9B!& Imported from GIF image: bookbig.gif,$!!!)))111999BBBJJJRRRZZZccckkksss{{{skkB991)))!!B11))1!JB9B9!!cZ9ƭƽssk{ZZRccZRRJJJBBB9c!!ν)1)k{s絽ƌkssֽZccJRRBJJ{9BB)11)99!!))11!!k!JZ!)RcJccBcs)1c)JZ!BR!)BZ)99J!Rk9!c11B)Z{)9Bkc1kB9BZ!Z{9Rs)Jkksk9kB1s1Jk9Rƥc{k9s)Z{1k91)s1Rk)Jc1J!))BZ!1k{csc{)19B!)Bcsc{ksc{kZs!RkJkJkքc{9Zks{ck9R)Bks9R9R1J!)Z1B!)c)9)99BR19kksBBJcc{ccBBZ))9kk!!199c11ZBB{9!!R!!Z!!c))!!kR!!s!!BcksRZ1c9B)R91c1)Z!R9B9k1)RcZ{)!1B9JB9B)!)J9BH`\Ȑ:pظа"A6DBH,V@Dڹ'G"v Æ ܥ;n;!;>xAܽ[G.\rQC wr}BŊQ A9ᾑ#5Y0VȒj0l-GqF>ZpM rb ;=.ސW-WѻWo ha!}~ْ ; t 53 :\ 4PcD,0 4*_l0K3-`l.j!c Aa|2L4/1C`@@md;(H*80L0L(h*҇҆o#N84pC (xO@ A)J6rVlF r  fry†$r_pl5xhA+@A=F rGU a 1х4s&H Bdzt x#H%Rr (Ѐ7P`#Rщ'x" #0`@~i `HA'Tk?3!$`-A@1l"P LhʖRG&8A`0DcBH sq@AXB4@&yQhPAppxCQ(rBW00@DP1E?@lP1%T` 0 WB~nQ@;PKGC PKH\lCOEBPS/dcommon/rarrow.gif/GIF87a絵ƌֵƽ{{ss֜ƔZZ{{{{ZZssZZccJJJJRRBBJJJJ991111))!!{,@pH,Ȥrl:ШLlԸ NCqWEd)#34vwwpN|0yhX!'+-[F 'n5 H $/14w3% C .90" qF 7&E "D mnB|,c96) I @0BW{ᢦdN p!5"D`0 T 0-]ʜ$;PKJV^PKH\lCOEBPS/dcommon/mix.gifkGIF89aZZZBBBJJJkkk999sss!!!111cccֽ{{{RRR)))猌ƭ{s{sks!,@@pH,B$ 8 t:<8 *'ntPP DQ@rIBJLNPTVEMOQUWfj^!  hhG H  kCúk_a Ǥ^ h`B BeH mm  #F` I lpǎ,p B J\Y!T\(dǏ!Gdˆ R53ټ R;iʲ)G=@-xn.4Y BuU(*BL0PX v`[D! | >!/;xP` (Jj"M6 ;PK枰pkPKH\lCOEBPS/dcommon/doccd_epub.jsM /* Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2012.3.17 */ function addLoadEvent(func) { var oldOnload = window.onload; if (typeof(window.onload) != "function") window.onload = func; else window.onload = function() { oldOnload(); func(); } } function compactLists() { var lists = []; var ul = document.getElementsByTagName("ul"); for (var i = 0; i < ul.length; i++) lists.push(ul[i]); var ol = document.getElementsByTagName("ol"); for (var i = 0; i < ol.length; i++) lists.push(ol[i]); for (var i = 0; i < lists.length; i++) { var collapsible = true, c = []; var li = lists[i].getElementsByTagName("li"); for (var j = 0; j < li.length; j++) { var p = li[j].getElementsByTagName("p"); if (p.length > 1) collapsible = false; for (var k = 0; k < p.length; k++) { if ( getTextContent(p[k]).split(" ").length > 12 ) collapsible = false; c.push(p[k]); } } if (collapsible) { for (var j = 0; j < c.length; j++) { c[j].style.margin = "0"; } } } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(compactLists); function processIndex() { try { if (!/\/index.htm(?:|#.*)$/.test(window.location.href)) return false; } catch(e) {} var shortcut = []; lastPrefix = ""; var dd = document.getElementsByTagName("dd"); for (var i = 0; i < dd.length; i++) { if (dd[i].className != 'l1ix') continue; var prefix = getTextContent(dd[i]).substring(0, 2).toUpperCase(); if (!prefix.match(/^([A-Z0-9]{2})/)) continue; if (prefix == lastPrefix) continue; dd[i].id = prefix; var s = document.createElement("a"); s.href = "#" + prefix; s.appendChild(document.createTextNode(prefix)); shortcut.push(s); lastPrefix = prefix; } var h2 = document.getElementsByTagName("h2"); for (var i = 0; i < h2.length; i++) { var nav = document.createElement("div"); nav.style.position = "relative"; nav.style.top = "-1.5ex"; nav.style.left = "1.5em"; nav.style.width = "90%"; while (shortcut[0] && shortcut[0].toString().charAt(shortcut[0].toString().length - 2) == getTextContent(h2[i])) { nav.appendChild(shortcut.shift()); nav.appendChild(document.createTextNode("\u00A0 ")); } h2[i].parentNode.insertBefore(nav, h2[i].nextSibling); } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(processIndex); PKo"nR M PKH\lCOEBPS/dcommon/toc.gifGIF89a1ΥΥ{c{Z{JkJk1Rk,@IK% 0| eJB,K-1i']Bt9dz0&pZ1o'q(؟dQ=3S SZC8db f&3v2@VPsuk2Gsiw`"IzE%< C !.hC IQ 3o?39T ҍ;PKv I PKH\lCOEBPS/dcommon/topnav.gifGIF89a1ֽ筽ޭƔkZZk{Bc{,@ ) l)-'KR$&84 SI) XF P8te NRtHPp;Q%Q@'#rR4P fSQ o0MX[) v + `i9gda/&L9i*1$#"%+ ( E' n7Ȇ(,҅(L@(Q$\x 8=6 'נ9tJ&"[Epljt p#ѣHb :f F`A =l|;&9lDP2ncH R `qtp!dȐYH›+?$4mBA9 i@@ ]@ꃤFxAD*^Ŵ#,(ε  $H}F.xf,BD Z;PK1FAPKH\lCOEBPS/dcommon/bp_layout.css# @charset "utf-8"; /* bp_layout.css Copyright 2007, Oracle and/or its affiliates. All rights reserved. */ body { margin: 0ex; padding: 0ex; } h1 { display: none; } #FOOTER { border-top: #0d4988 solid 10px; background-color: inherit; color: #e4edf3; clear: both; } #FOOTER p { font-size: 80%; margin-top: 0em; margin-left: 1em; } #FOOTER a { background-color: inherit; color: gray; } #LEFTCOLUMN { float: left; width: 50%; } #RIGHTCOLUMN { float: right; width: 50%; clear: right; /* IE hack */ } #LEFTCOLUMN div.portlet { margin-left: 2ex; margin-right: 1ex; } #RIGHTCOLUMN div.portlet { margin-left: 1ex; margin-right: 2ex; } div.portlet { margin: 2ex 1ex; padding-left: 0.5em; padding-right: 0.5em; border: 1px #bcc solid; background-color: #f6f6ff; color: black; } div.portlet h2 { margin-top: 0.5ex; margin-bottom: 0ex; font-size: 110%; } div.portlet p { margin-top: 0ex; } div.portlet ul { list-style-type: none; padding-left: 0em; margin-left: 0em; /* IE Hack */ } div.portlet li { text-align: right; } div.portlet li cite { font-style: normal; float: left; } div.portlet li a { margin: 0px 0.2ex; padding: 0px 0.2ex; font-size: 95%; } #NAME { margin: 0em; padding: 0em; position: relative; top: 0.6ex; left: 10px; width: 80%; } #PRODUCT { font-size: 180%; } #LIBRARY { color: #0b3d73; background: inherit; font-size: 180%; font-family: serif; } #RELEASE { position: absolute; top: 28px; font-size: 80%; font-weight: bold; } #TOOLS { list-style-type: none; position: absolute; top: 1ex; right: 2em; margin: 0em; padding: 0em; background: inherit; color: black; } #TOOLS a { background: inherit; color: black; } #NAV { float: left; width: 96%; margin: 3ex 0em 0ex 0em; padding: 2ex 0em 0ex 4%; /* Avoiding horizontal scroll bars. */ list-style-type: none; background: transparent url(../gifs/nav_bg.gif) repeat-x bottom; } #NAV li { float: left; margin: 0ex 0.1em 0ex 0em; padding: 0ex 0em 0ex 0em; } #NAV li a { display: block; margin: 0em; padding: 3px 0.7em; border-top: 1px solid gray; border-right: 1px solid gray; border-bottom: none; border-left: 1px solid gray; background-color: #a6b3c8; color: #333; } #SUBNAV { float: right; width: 96%; margin: 0ex 0em 0ex 0em; padding: 0.1ex 4% 0.2ex 0em; /* Avoiding horizontal scroll bars. */ list-style-type: none; background-color: #0d4988; color: #e4edf3; } #SUBNAV li { float: right; } #SUBNAV li a { display: block; margin: 0em; padding: 0ex 0.5em; background-color: inherit; color: #e4edf3; } #SIMPLESEARCH { position: absolute; top: 5ex; right: 1em; } #CONTENT { clear: both; } #NAV a:hover, #PORTAL_1 #OVERVIEW a, #PORTAL_2 #OVERVIEW a, #PORTAL_3 #OVERVIEW a, #PORTAL_4 #ADMINISTRATION a, #PORTAL_5 #DEVELOPMENT a, #PORTAL_6 #DEVELOPMENT a, #PORTAL_7 #DEVELOPMENT a, #PORTAL_11 #INSTALLATION a, #PORTAL_15 #ADMINISTRATION a, #PORTAL_16 #ADMINISTRATION a { background-color: #0d4988; color: #e4edf3; padding-bottom: 4px; border-color: gray; } #SUBNAV a:hover, #PORTAL_2 #SEARCH a, #PORTAL_3 #BOOKS a, #PORTAL_6 #WAREHOUSING a, #PORTAL_7 #UNSTRUCTURED a, #PORTAL_15 #INTEGRATION a, #PORTAL_16 #GRID a { position: relative; top: 2px; background-color: white; color: #0a4e89; } PK3( # PKH\lCOEBPS/dcommon/bookicon.gif:GIF87a!!!)))111999BBBJJJRRRZZZccckkksss{{{ޭ{{ZRRcZZRJJJBB)!!skRB9{sν{skskcZRJ1)!֭ƽ{ZZRccZJJBBB999111)JJ9BB1ZZB!!ﭵBJJ9BB!!))Jk{)1!)BRZJ{BsR!RRJsJ!J{s!JsBkks{RsB{J{c1RBs1ZB{9BJ9JZ!1BJRRs!9R!!9Z9!1)J19JJRk19R1Z)!1B9R1RB!)J!J1R)J119!9J91!9BkksBBJ119BBR!))9!!!JB1JJ!)19BJRZckތ1)1J9B,H*\hp >"p`ƒFF "a"E|ժOC&xCRz OBtX>XE*O>tdqAJ +,WxP!CYpQ HQzDHP)T njJM2ꔀJ2T0d#+I:<жk 'ꤱF AB @@nh Wz' H|-7f\A#yNR5 /PM09u UjćT|q~Yq@&0YZAPa`EzI /$AD Al!AAal 2H@$ PVAB&c*ؠ p @% p-`@b`uBa l&`3Ap8槖X~ vX$Eh`.JhAepA\"Bl, :Hk;PKx[?:PKH\lCOEBPS/dcommon/conticon.gif^GIF87a!!!)))111999BBBJJJRRRZZZccckkksss{{{ZRR޽{{ssskkkcccZ991ccRZZBBJJZck)19ZcsBJZ19J!k{k)Z1RZs1!B)!J91{k{)J!B!B911)k{cs!1s!9)s!9!B!k)k1c!)Z!R{9BJcckZZcBBJ99B119{{!!)BBRBBZ!))999R99Z!!999c1!9!)19B1)!B9R,  oua\h2SYPa aowwxYi 9SwyyxxyYSd $'^qYȵYvh ч,/?g{н.J5fe{ڶyY#%/}‚e,Z|pAܠ `KYx,ĉ&@iX9|`p ]lR1khٜ'E 6ÅB0J;t X b RP(*MÄ!2cLhPC <0Ⴁ  $4!B 6lHC%<1e H 4p" L`P!/,m*1F`#D0D^!AO@..(``_؅QWK>_*OY0J@pw'tVh;PKp*c^PKH\lCOEBPS/dcommon/blafdoc.cssL@charset "utf-8"; /* Copyright 2002, 2011, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2011.10.7 */ body { font-family: Tahoma, sans-serif; /* line-height: 125%; */ color: black; background-color: white; font-size: small; } * html body { /* http://www.info.com.ph/~etan/w3pantheon/style/modifiedsbmh.html */ font-size: x-small; /* for IE5.x/win */ f\ont-size: small; /* for other IE versions */ } h1 { font-size: 165%; font-weight: bold; border-bottom: 1px solid #ddd; width: 100%; } h2 { font-size: 152%; font-weight: bold; } h3 { font-size: 139%; font-weight: bold; } h4 { font-size: 126%; font-weight: bold; } h5 { font-size: 113%; font-weight: bold; display: inline; } h6 { font-size: 100%; font-weight: bold; font-style: italic; display: inline; } a:link { color: #039; background: inherit; } a:visited { color: #72007C; background: inherit; } a:hover { text-decoration: underline; } a img, img[usemap] { border-style: none; } code, pre, samp, tt { font-family: monospace; font-size: 110%; } caption { text-align: center; font-weight: bold; width: auto; } dt { font-weight: bold; } table { font-size: small; /* for ICEBrowser */ } td { vertical-align: top; } th { font-weight: bold; text-align: left; vertical-align: bottom; } ol ol { list-style-type: lower-alpha; } ol ol ol { list-style-type: lower-roman; } td p:first-child, td pre:first-child { margin-top: 0px; margin-bottom: 0px; } table.table-border { border-collapse: collapse; border-top: 1px solid #ccc; border-left: 1px solid #ccc; } table.table-border th { padding: 0.5ex 0.25em; color: black; background-color: #f7f7ea; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } table.table-border td { padding: 0.5ex 0.25em; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } span.gui-object, span.gui-object-action { font-weight: bold; } span.gui-object-title { } p.horizontal-rule { width: 100%; border: solid #cc9; border-width: 0px 0px 1px 0px; margin-bottom: 4ex; } div.zz-skip-header { display: none; } td.zz-nav-header-cell { text-align: left; font-size: 95%; width: 99%; color: black; background: inherit; font-weight: normal; vertical-align: top; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-header-link { font-size: 95%; } td.zz-nav-button-cell { white-space: nowrap; text-align: center; width: 1%; vertical-align: top; padding-left: 4px; padding-right: 4px; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-button-link { font-size: 90%; } div.zz-nav-footer-menu { width: 100%; text-align: center; margin-top: 2ex; margin-bottom: 4ex; } p.zz-legal-notice, a.zz-legal-notice-link { font-size: 85%; /* display: none; */ /* Uncomment to hide legal notice */ } /*************************************/ /* Begin DARB Formats */ /*************************************/ .bold, .codeinlinebold, .syntaxinlinebold, .term, .glossterm, .seghead, .glossaryterm, .keyword, .msg, .msgexplankw, .msgactionkw, .notep1, .xreftitlebold { font-weight: bold; } .italic, .codeinlineitalic, .syntaxinlineitalic, .variable, .xreftitleitalic { font-style: italic; } .bolditalic, .codeinlineboldital, .syntaxinlineboldital, .titleinfigure, .titleinexample, .titleintable, .titleinequation, .xreftitleboldital { font-weight: bold; font-style: italic; } .itemizedlisttitle, .orderedlisttitle, .segmentedlisttitle, .variablelisttitle { font-weight: bold; } .bridgehead, .titleinrefsubsect3 { font-weight: bold; } .titleinrefsubsect { font-size: 126%; font-weight: bold; } .titleinrefsubsect2 { font-size: 113%; font-weight: bold; } .subhead1 { display: block; font-size: 139%; font-weight: bold; } .subhead2 { display: block; font-weight: bold; } .subhead3 { font-weight: bold; } .underline { text-decoration: underline; } .superscript { vertical-align: super; } .subscript { vertical-align: sub; } .listofeft { border: none; } .betadraft, .alphabetanotice, .revenuerecognitionnotice { color: #e00; background: inherit; } .betadraftsubtitle { text-align: center; font-weight: bold; color: #e00; background: inherit; } .comment { color: #080; background: inherit; font-weight: bold; } .copyrightlogo { text-align: center; font-size: 85%; } .tocsubheader { list-style-type: none; } table.icons td { padding-left: 6px; padding-right: 6px; } .l1ix dd, dd dl.l2ix, dd dl.l3ix { margin-top: 0ex; margin-bottom: 0ex; } div.infoboxnote, div.infoboxnotewarn, div.infoboxnotealso { margin-top: 4ex; margin-right: 10%; margin-left: 10%; margin-bottom: 4ex; padding: 0.25em; border-top: 1pt solid gray; border-bottom: 1pt solid gray; } p.notep1 { margin-top: 0px; margin-bottom: 0px; } .tahiti-highlight-example { background: #ff9; text-decoration: inherit; } .tahiti-highlight-search { background: #9cf; text-decoration: inherit; } .tahiti-sidebar-heading { font-size: 110%; margin-bottom: 0px; padding-bottom: 0px; } /*************************************/ /* End DARB Formats */ /*************************************/ @media all { /* * * { line-height: 120%; } */ dd { margin-bottom: 2ex; } dl:first-child { margin-top: 2ex; } } @media print { body { font-size: 11pt; padding: 0px !important; } a:link, a:visited { color: black; background: inherit; } code, pre, samp, tt { font-size: 10pt; } #nav, #search_this_book, #comment_form, #comment_announcement, #flipNav, .noprint { display: none !important; } body#left-nav-present { overflow: visible !important; } } PKʍPKH\lCOEBPS/dcommon/rightnav.gif&GIF89a1ֽ筽ޭƔkZZk{Bc{,@ ) l)- $CҠҀ ! D1 #:aS( c4B0 AC8 ְ9!%MLj Z * ctypJBa H t>#Sb(clhUԂ̗4DztSԙ9ZQҀEPEPEPEPEPEPEPM=iԍP Gii c*yF 1׆@\&o!QY00_rlgV;)DGhCq7~..p&1c:u֫{fI>fJL$}BBP?JRWc<^j+χ5b[hֿ- 5_j?POkeQ^hֿ1L^ H ?Qi?z?+_xɔŪ\썽O]χ>)xxV/s)e6MI7*ߊޛv֗2J,;~E4yi3[nI`Ѱe9@zXF*W +]7QJ$$=&`a۾?]N T䏟'X)Ɣkf:j |>NBWzYx0t!* _KkoTZ?K Gc+UyڹgNuh^iSo5{\ܹ3Yos}.>if FqR5\/TӮ#]HS0DKu{($"2xִ{SBJ8=}Y=.|Tsц2UЫ%.InaegKo z ݎ3ֹxxwM&2S%';+I',kW&-"_¿_ Vq^ܫ6pfT2RV A^6RKetto^[{w\jPZ@ޢN4/XN#\42j\(z'j =~-I#:q[Eh|X:sp* bifp$TspZ-}NM*B-bb&*xUr#*$M|QWY ~p~- fTED6O.#$m+t$˙H"Gk=t9r娮Y? CzE[/*-{c*[w~o_?%ƔxZ:/5𨴟q}/]22p qD\H"K]ZMKR&\C3zĽ[PJm]AS)Ia^km M@dК)fT[ijW*hnu Ͳiw/bkExG£@f?Zu.s0(<`0ֹoxOaDx\zT-^ѧʧ_1+CP/p[w 9~U^[U<[tĽwPv[yzD1W='u$Oeak[^ |Gk2xv#2?¹TkSݕ| rݞ[Vi _Kz*{\c(Ck_܏|?u jVڔ6f t?3nmZ6f%QAjJf9Rq _j7Z-y.pG$Xb]0')[_k;$̭?&"0FOew7 z-cIX岛;$u=\an$ zmrILu uٞ% _1xcUW%dtÀx885Y^gn;}ӭ)場QEQ@Q@Q@Q@Q@Q@!4xPm3w*]b`F_931˜[ן+(> E ly;<;MF-qst+}DH @YKlLmؤciN<|]IU)Lw(8t9FS(=>og<\Z~u_+X1ylsj'eՃ*U3`C!N9Q_WܱhKc93^ua>H ƕGk=8~e#_?{ǀe-[2ٔ7;=&K挑5zsLdx(e8#{1wS+ΝVkXq9>&yஏh$zq^0~/j@:/«Vnce$$uoPp}MC{$-akH@ɫ1O !8R9s5ԦYmϧ'OUṡ5T,!Ԛ+s#1Veo=[)g>#< s)ƽُA^䠮ωFUj(ǩ|N3Jڷ睁ϱuږZYGOTsI<&drav?A^_f׻B$,O__ԿC`it{6>G׈C~&$y؎v1q9Sc1fH[ѽ>,gG'0'@Vw,BO [#>ﱺg5ΒFVD%Yr:O5 Tu+O멃]ی38Ze}R&ѝ_xzc1DXgس;<,_,{ƽY'AS#oF.M#~cBuEx7G+Y)(5q+GCV;qF+CLQ)qEC&6z𿊘z}?&w=+)??&\g{;V??׻xGœdٿ׼-Nc')3K]N)iLTӿCdb7Q^a N sd>Fz[0S^s'Zi 77D}kWus ab~~H(>.fif9,~|Jk;YN3H8Y(t6Q݉k͇_÷Z+2߄&[ +Tr^藺97~c܎=[f1RrBǓ^kEMhxYVm<[џ6| kqbѱ| YA{G8p?\UM7Z66 g1U1igU69 u5Pƪ:VVZC=[@ҹ¨$kSmɳО\vFz~i3^a Osŧυ9Q}_3 όO{/wgoet39 vO2ea;Ύ7$U#?k+Ek&dpzbӱ+TaB0gN{[N7Gי}U7&@?>Fz~E!a@s ?'67XxO*!?qi]֏TQN@tI+\^s8l0)2k!!iW8F$(yOּT.k,/#1:}8uT˾+5=O/`IW G֯b.-<= HOm;~so~hW5+kS8s.zwE| ?4ӿw/K N 9?j(#0UT` Wzw}:_*9m>󑓀F?ELzv=8q:=WgJ`nDr Zе<ֹ](Q@Q@Q@Q@Q@Q@Q@Q@ 'IdC0EYJVcMty_~u+Sw-aO n<[YJgL#6i g5ЖDZ14cʝ!!\/M}/_AYR__>oC? _?7_G#RERW쏞KB}JxGSkǕA pƱơP m]hwB7U$Zq M95"3q1ioATߚ{g.t uu2k=;h#YB= fgS :TdLԃ!44mFK{Hrd^7oz|BVr<{)6AXգV»|>*/hS܏z͆OM=Εq (s|s׊LKQI :9NJ)P+!ʣoAF>+=@I}"x/}۠1aנc¹4emC:>p_xWKX` >R3_S½èųp3޺u3N e یbmͺ<_ mnݮ1Op?Gm)Qb%N585'%Ahs\6yw!"&Ɨ._wk)}GP;Z!#\"< *oƾ\)}N>"լ/~]Lg}pBG X?<zZ#x69S=6) jzx=y9O&>+e!!? ?s~k5Gʏ)?*ce7Ox~k5􇔾Q/e7/Ԑ#3OgNC0] ;_FiRl>Q.g>!%k#ú:Kn'&}?U@\pџPtp)v<{_i}Oվֲ3XIYIx~b<D?(=_JXH=bbi=Oh?_ C_O)}oW쏜? %Ƶ;-RYFi`wۭ{ϖZMtQ$"c_+ԃx1*0b;ԕ݋ESQEQEQEQEQEQEQEQEQEQZ(1F)h1K@XLRE&9P (bf{RӨ&)PEPEPbԴPGKZ(iإbn(:A%S0(-&)P+ ڎԴP11F)h&:LRmQ@Q@Š(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((PKje88PKH\lCOEBPS/dcommon/help.gif!GIF89a1εֵ֜֜{kZsBc{,@ )sƠTQ$8(4ʔ%ŌCK$A HP`$h8ŒSd+ɡ\ H@%' 6M HO3SJM /:Zi[7 \( R9r ERI%  N=aq   qƦs *q-n/Sqj D XZ;PKއ{&!PKH\lCOEBPS/mss_cart_components.htm About Cartridge Components

2 About Cartridge Components

This chapter provides information about the components of the Oracle Communications Network Integrity MSS Integration cartridge.

MSS Integration Cartridge Actions

You can use the MSS Integration cartridge to run the following actions:

Import from MSS Action

The Import from MSS (Import) action is run by the MSS Import scan action type in Network Integrity.

The Import action connects to Oracle Communications MetaSolv Solution (MSS) and retrieves the specified inventory information. The Import action writes the inventory information to staging tables and models it after the Oracle Communications Information Model. The staging tables are populated with data source information, allowing row mappers and data access objects (DAOs) to reference the tables for follow-on actions, such as Discrepancy Detection or Discrepancy Resolution.

The Import action consists of the following processors run in the following order:

  1. Equipment DAOs Initializer

  2. Page Initializer

  3. Page Creator

  4. Node Collector

  5. Device Modeler

  6. Equipment Hierarchy Collector

  7. Equipment Hierarchy Modeler

  8. Hierarchy Persister

  9. STM Link Discoverer

  10. VC4 Circuit Discoverer

  11. VC3 VC12 LOP Discoverer

Figure 2-1 illustrates the processor workflow of the Import from MSS action.

Figure 2-1 Import from MSS Action Processor Workflow

processors belonging to the MSS Import action

Equipment DAOs Initializer

This processor reads the data source information from the Import System values and initializes the DAOLocator instance. The DAOLocator instance is used by other processors and actions to retrieve equipment and circuit data.

Page Initializer

If Run MSS Extract is set to True in the Network Integrity UI, this processor runs the MSS extraction script.

Also, this processor counts all the unique network nodes from the MSS extract tables, according to the scope defined in the Network Integrity UI, and determines the number of pages needed to list all the nodes. By default, a page can contain 50 nodes. This processor produces a pageCountList iterable object.

Page Creator

This processor creates pages listing unique network node names imported from MSS matching the filtering criteria set in the Network Integrity UI. This processor outputs the node names list in a response object.

Node Collector

This processor collects all root equipment from MSS for each node on the node name list produced by the Page Creator processor. The collected root equipment are placed in the nodesMapByNodeName map, which indexes each node name and its value.

The output iterable object loops over nodeNamesSet, geting one node name per loop.

Device Modeler

This processor models each imported network node as PhysicalDevice and LogicalDevice entities and outputs a root equipment list for each modeled node.

Equipment Hierarchy Collector

This processor retrieves port information for the equipment hierarchy from EquipmentPositionHierDAO and EquipmentPortAddressDAO. This processor outputs a map listing port-to-card IDs.

Equipment Hierarchy Modeler

This processor models root equipment and its floating termination points (FTPs) from the map as physical port and media interface entities. Its associated ports are derived from the output map from the Equipment Hierarchy Collector processor and are modeled as physical port and media interface entities.

This processor builds the equipment hierarchy by parsing the equipment hierarchy string. Slots and subslots are modeled as equipment holders, and cards are modeled as equipment. This processor saves processed card IDs to an index object to avoid processing duplicate card IDs in different hierarchy for the same parent.


Note:

The equipment hierarchy string in MSS must define the equipment type for equipment for this processor to successfully build the hierarchy.

Hierarchy Persister

This processor saves the logical and physical device trees and saves the modeled hierarchy for each network node.

STM Link Discoverer

This processor discovers synchronous transport module (STM) links from the list of ports produced by the Equipment Hierarchy Modeler processor.

This processor retrieves the STM Circuit information from CircuitExportDAO and CircuitPositionDAO and models each as DisPipe entities. The STM links are modeled with a valid VC4 channel index value.

This processor outputs a list of STM links in an stmSet object.

VC4 Circuit Discoverer

This processor retrieves the VC4 circuit information from the STM Link Discoverer processor. It verifies whether the circuit is a customer circuit. Customer circuits are modeled as E4 circuits with a VC4 display string. Non-customer circuits are modeled as transport pipes with a VC4 higher order transport display string.

This processor produces a list of CircuitExport DAOs for each transport pipe.

VC3 VC12 LOP Discoverer

This processor queries the lower order pipes (LOPs) from the vc4sForLops list and models them as E3 circuits with a VC3 display string or as E1 circuits with a VC12 display string, depending on the layer rate codes.

Detect Equipment Discrepancies Action

The Detect Equipment Discrepancies action is run when an Import scan is configured with the Detect Discrepancies check box enabled, triggering the Network Integrity Base Detection cartridge. See "About Discrepancy Detection" for more information.

This action compares TMF814 Discovery scan results with the imported MSS data and returns a list of discrepancies. For more information about the TMF814 Discovery scan action type, see Network Integrity Optical TMF814 CORBA Cartridge Guide.

The Detect Equipment Discrepancies action consists of the following processors run in the following order:

  1. Equipment Filters Initializer

  2. Discrepancy Detector

  3. Discrepancy Filter

Figure 2-2 illustrates the processor workflow of the Detect Equipment Discrepancies action.

Figure 2-2 Detect Equipment Discrepancies Action Processor Workflow

Description of Figure 2-2 follows
Description of "Figure 2-2 Detect Equipment Discrepancies Action Processor Workflow"

Equipment Filters Initializer

This processor applies the equipment filters set in the Network Integrity UI on the Discrepancy Detection process. This processor also automatically filters out discrepancies that are not relevant to MSS equipment.

Discrepancy Detector

This processor extends the Detect Discrepancies action from the Base Detection cartridge. See Network Integrity Developer's Guide for more information.

Discrepancy Filter

This processor collects the discrepancies generated by the Discrepancy Detector processor and sets the priority and status for discrepancies on physical ports.

Discrepancies on physical ports are labeled with the message Manually correct in MSS and Network Integrity sets the status to Ignored, because Network Integrity cannot resolve this type of discrepancy.

MSS Circuit Discrepancy Detection Action

The MSS Circuit Discrepancy Detection action is run when an Assimilate Optical Circuits scan is configured with the Detect Discrepancies check box enabled, which triggers the Network Integrity Base Detection cartridge. See "About Discrepancy Detection" for more information.

This action compares the results of an Assimilate Optical Circuits scan with the imported MSS data and returns a list of discrepancies. For more information about the Assimilate Optical Circuits scan action type, see Network Integrity Optical Circuit Assimilation Cartridge Guide.

The MSS Circuit Discrepancy Detection action consists of the following processors run in the following order:

  1. Circuit Discrepancy Name Filter Initializer

  2. Missing Entity Filter Initializer

  3. Partial Circuit Discrepancy Filter

  4. Discrepancy Detector

Figure 2-3 illustrates the processor workflow of the MSS Circuit Discrepancy Detection action.

Figure 2-3 MSS Circuit Discrepancy Detection Action Processor Workflow

Description of Figure 2-3 follows
Description of "Figure 2-3 MSS Circuit Discrepancy Detection Action Processor Workflow"

Circuit Discrepancy Name Filter Initializer

This processor applies the filters set in the Network Integrity UI on the Discrepancy Detection process.

Missing Entity Filter Initializer

This processor extends the Optical Circuit Discrepancy Detection action on the Network Integrity Optical Circuit Assimilation cartridge. See Network Integrity Optical Circuit Assimilation Cartridge Guide for more information.

Partial Circuit Discrepancy Filter

This processor collects the discrepancies generated by the Missing Entity Filter initializer processor. Discrepancies on partial pipe entities with a name that begins with GENERATED_ are labeled with the message Manually correct in MSS and the status is set to Ignored, as Network Integrity cannot resolve this type of discrepancy.

Discrepancy Detector

This processor extends the Detect Discrepancies action from the Base Detection cartridge. See Network Integrity Developer's Guide for more information.

Resolve in MSS Action

The Resolve in MSS action resolves discrepancies between your network data and the imported data by updating equipment and circuit hierarchy in MSS. See "About Discrepancy Resolution" for more information.

The Resolve in MSS action consists of the following processors run in the following order:

  1. CORBA Property Initializer

  2. MSS CORBA Property Initializer

  3. CORBA Connection Manager

  4. Resolution Framework Initializer

  5. MSS Resolution Initializer

  6. Resolution Framework Dispatcher

Figure 2-4 illustrates the processor workflow of the Resolve in MSS action.

Figure 2-4 Resolve in MSS Action Processor Workflow

processors belonging to the discrepancy resolution action

CORBA Property Initializer

This processor is extended from the Resolve Abstract action on the Network Integrity Cartridge for CORBA (CORBA cartridge). It initializes the common object request broker architecture (CORBA) connection parameters. See Network Integrity CORBA Cartridge Guide for more information.

MSS CORBA Property Initializer

This processor sets the CORBA object request broker (ORB) properties in the JacORB to establish CORBA connectivity with MSS.

CORBA Connection Manager

This processor is extended from the Resolve Abstract action on the CORBA cartridge. It returns the ORB and the naming server corresponding to the MSS Inventory CORBA server NameService. See Network Integrity CORBA Cartridge Guide for more information.

Resolution Framework Initializer

This processor initializes the BaseResolutionElement resolution framework class used to register the handlers required to resolve discrepancies in MSS.

MSS Resolution Initializer

This processor registers the following entity handlers to the BaseResolutionElement class:

  • DeviceHandler

  • EquipmentHandler

  • PhysicalPortHandler

  • DeviceInterfaceHandler

  • CircuitHandler

  • PipeTerminationPointHandler

  • TrailPathHandler

Resolution Framework Dispatcher

This processor runs the BaseResolutionElement class to evaluate and treat discrepancies using the appropriate registered entity handlers.

About Discrepancy Detection

The MSS Integration cartridge extends the Base Detection cartridge to run its Discrepancy Detection action.

Table 2-1 lists the possible discrepancies that can be reported and the types of entity that each discrepancy can be found on.

Table 2-1 Discrepancy Types

Discrepancy TypeEntity Types

Extra Entity (Entity+)

Physical device, equipment, equipment holder, physical port, pipe (STM/HOT/LOP), pipe termination point, trail path, trail pipe

Missing Entity (Entity-)

Physical device, equipment, equipment holder, physical port, pipe (STM/HOT/LOP), pipe termination point, trail path, trail pipe

Attribute Value Mismatch (Attribute)

Physical device, logical device, equipment, equipment holder, pipe


For more information about discrepancies, or about the Base Detection cartridge, see Network Integrity Developer's Guide.

About Discrepancy Resolution

The MSS Integration cartridge has two distinct Discrepancy Resolution actions: one for circuits and another for equipment. The cartridge communicates equipment resolution using a CORBA connection and communicates circuit resolution using an Enterprise JavaBean (EJB) connection.

This section lists the discrepancy types that the MSS Integration cartridge can resolve from Network Integrity. All other discrepancy types must be resolved manually in MSS.

This action automatically uses the correct handler depending on the type of discrepancy being resolved. Table 2-2 lists the discrepancy types and the handler used to resolve the discrepancy.

Table 2-2 Discrepancy Resolution Handlers

HandlerHandled Entity TypesDiscrepancy Type

DeviceHandler

Physical device

Entity+

EquipmentHandler

Equipment, equipment holder

Entity+, Attribute value mismatch

PipeTerminationPointHandler

Pipe termination point

Entity+, Entity-

TrailPathHandler

Trail path

Entity+, Entity-

CircuitHandler

Pipe (customer circuit)

Entity+ (LOP, TrailPipe upload), Entity- (LOP, TrailPipe delete), Attribute value mismatch (for timeslot)

PhysicalPortHandler

Physical port

Entity+, Entity-


Each handler runs creation and removal operations to fully resolve discrepancies. For discrepancies on MSS equipment, the handlers run CORBA API methods and populate Java classes with the resolution information.

Network Integrity updates the status of discrepancies as they are being resolved:

  • Processed: Network Integrity successfully processed the discrepancy.

  • Failed: Network Integrity could not successfully process the discrepancy. The reasonForFailure field explains the cause of the failure. Network Integrity logs exceptions and failure reasons.

  • Ignored: Network Integrity does not support making this resolution in MSS. You must manually resolve this discrepancy in MSS.

  • Not Implemented: Network Integrity could not upload the resolution to MSS. You can manually resolve this discrepancy in MSS, or extend or develop a handler to resolve the discrepancy from Network Integrity.

For more information about discrepancy resolution, see Network Integrity Developer's Guide.

Extra Entity (Entity+) Discrepancy Resolution

Entity+ discrepancies occur when an entity exists in your network but is missing from the imported data. Network Integrity resolves this type of discrepancy by creating the missing entity in MSS.

Network Node Creation

Entity+ discrepancies occur on physical or logical devices when the corresponding network node does not exist in MSS. The MSS Integration cartridge resolves this discrepancy by doing the following:

  • Queries location_id using the MSS CORBA getLocationI API method. This method belongs to NetworkLocationSubSession of the InfrastructureSession interface.

  • Creates a network node in MSS in the location returned by the getLocation API by running the MSS CORBA createNetworkElement API method. This method belongs to NetworkElementSubSession of the EquipmentSession interface.

  • You must open the MSS UI and search for the created node, updating it with the type and manually associating it with the network system, which allows later resolution actions to create equipment and hierarchies under the new node.


Note:

Creating a network node can cause additional discrepancies on the next Discrepancy Detection action, such as new Entity+ discrepancies on MSS equipment or equipment hierarchy belonging to the new network node. This is normal.

Equipment Creation

Entity+ discrepancies occur on equipment when the corresponding rack, shelf, sub-shelf, or card does not exist in MSS. The MSS Integration cartridge resolves this discrepancy by doing the following:

  • Traverses the Information Model equipment hierarchy. For each equipment found, creates equipment in MSS using the MSS CORBA installEquipment API method. This method belongs to InstallationSubSession of the EquipmentSession interface.

  • For each root equipment, queries for its parent and obtains network_node_id using the CORBA getNetworkElement API method. This method belongs to NetworkElementSubSession of the EquipmentSession interface.

  • For each equipment, queries for EquipmentSpecification using the MSS CORBA queryEquipSpec_v2 API method and obtains equip_spec_id. This method belongs to SpecificationSubsession of the EquipmentSession interface. NativeEMSName, discoveredPartNumber, and modelName on modeled Information Model equipment are used to identify the equipment specification in MSS.

Ensure that the equipment specification for the equipment being created exists in MSS before uploading the equipment from Network Integrity. Port creation is determined by the card equipment specification.

Circuit Creation

Entity+ discrepancies occur on circuits when a circuit does not exist in MSS. You must resolve the discrepancies on equipment, HOTs, and STMs and reconcile the data again before you can upload the resolution for customer circuits. It is recommended that you limit your first discrepancy detection scan to equipment, HOTs, and STMs. Expand subsequent scans to detect all discrepancies.

The MSS Integration cartridge resolves this discrepancy by doing the following:

  • Uploads customer circuits to MSS by creating new end-to-end customer connections using the EJB createNewCustomerConnection API method. This method also assigns ports and channels to the uploaded circuit if the information is available.

  • If the channel information is not available, the MSS Integration cartridge builds the channel hierarchy at the given circuit position using the EJB autoBuild API method and updates the provisioning information. The method derives the circuit position based on the synchronous digital hierarchy (SDH).

  • Prepares the port and channel assignment containers for the circuit based on the traced circuit information.

  • Calls the EJB updateCircuit and updateProvisioningInfo API methods to pass updated circuit and provisioning information to MSS.

You can use a wrapper API to call multiple MSS methods in a single transaction.

You can also extend the circuit resolution handler to use custom logic.

STM links and higher-order transport (HOT) circuits cannot be uploaded to or corrected in MSS with API methods from Network Integrity. Discrepancies on STMs and HOTs must be corrected manually in MSS.

Because VC4 HOTs span across multiple links in a network, you should follow these guidelines while creating HOTs in MSS:

  1. Create the facility connection for the VC4 rate code.

  2. Using CLR/DLR design, assign the channel from the STM links to the HOT.

  3. In the network system, create the connection spanning the entire VC4 HOT.

  4. Associate the VC4 HOT to the network system.

Channel Assignment Creation on a Trail Pipe

Entity+ discrepancies occur on trail pipes when a circuit in MSS is missing its channel assignment. This discrepancy occurs when channel assignments were not assigned to the circuit in MSS or when a circuit is rerouted.

When dealing with unassigned channel assignments, the MSS Integration cartridge resolves this discrepancy by assigning the circuit to the channel in MSS.

You can identify a rerouted circuit when Network Integrity reports multiple Entity+ and Entity- discrepancies. By filtering on the circuit name, you can see that the discrepancies are all relat= ed.

The MSS Integration cartridge resolves rerouted circuits by creating or correcting the channel assignments on trail pipes in MSS.

TrailPath Assignment to a Circuit

Entity+ discrepancies on trail paths are resolved by assigning the trail path to a circuit and updating the provisioning information. The MSS Integration cartridge resolves this discrepancy by doing the following:

  • Calls the updateCircuit method to assign the entire trail path to the customer circuit.

  • Calls the updateProvisioningInfo method to pass and update the provisioning information on the customer circuit.

PipeTerminationPoint Assignment to a Circuit

Entity+ discrepancies on pipe termination points are resolved by assigning the pipe termination point to a circuit and updating the circuit with the provisioning information. The MSS Integration cartridge resolves this discrepancy by doing the following:

  • Assigns the pipe termination point to the circuit using the updateCircuit method.

  • Calls the updateProvisioningInfo MSS method with the PipeTerminationPoint information to update the circuit.

Missing Entity (Entity-) Discrepancy Resolution

Entity- discrepancies occur when an entity exists in the imported data and not in your network data. Network Integrity resolves this type of discrepancy by deleting the entity from MSS.

Take special care when resolving Entity- discrepancies, because there can be many underlying causes. Review the cause carefully, choosing to resolve the root cause (either from Network Integrity or manually in MSS).

Network Node Deletion

Entity- discrepancies occur on physical or logical devices when the corresponding network node does not exist in your network. The MSS Integration cartridge resolves this discrepancy by doing the following:

  • Queries the network node using the MSS CORBA getNetworkElement API method. This method belongs to NetworkElementSubSession of the EquipmentSession interface. This method may not return the network node if it was deleted while resolving another discrepancy.

  • Searches for root equipment. For each root equipment, traverses the hierarchy and deletes the lowest-level equipment. See "Equipment Deletion" for more information.

  • Deletes the parent network node after all child equipment are deleted. Network nodes are deleted using the MSS CORBA deleteNetworkElement API method.

Equipment Deletion

Entity- discrepancies occur on equipment when the corresponding rack, shelf, sub-shelf, or card does not exist in your network. The MSS Integration cartridge resolves this discrepancy by doing the following:

  • Queries the equipment using the MSS CORBA searchEquipmentInstall_v2 API method. This method belongs to InstallationSubSession of the EquipmentSession interface.

  • Uninstalls the equipment from MSS using the MSS CORBA uninstallEquipment API method at the location obtained from equipment_id.

Circuit Deletion

Entity- discrepancies occur on circuits when an additional circuit exists in MSS. The MSS Integration cartridge resolves this discrepancy by doing the following:

  • Locates the additional circuit in MSS and calls the MSS EJB deleteCircuit API method with a specific circuit ID or name.

Channel Assignment Deletion on a Trail Pipe

Entity- discrepancies occur on trail pipes when a trail pipe in the network is missing its channel assignment. This discrepancy occurs when a cross-connect is missing in the network or a customer circuit is down.

To resolve this discrepancy, you must repair the circuit in the network or release the circuit from MSS.

TrailPath Unassignment from a Circuit

Entity- discrepancies on trail paths are resolved by unassigning the trail path from a circuit and updating the provisioning information. The MSS Integration cartridge resolves this discrepancy by doing the following:

  • Calls the updateCircuit method to unassign the entire trail path from the customer circuit.

  • Calls the updateProvisioningInfo MSS method to update the circuit.


Note:

You must resolve Entity+ discrepancies on trail paths before resolving Entity- discrepancies on trail paths if the discrepancies are reported on the same circuit. Or, you can also resolve the Entity+ and the Entity- discrepancies at the same time and Network Integrity will fix them in the correct order.

PipeTerminationPoint Unassignment from a Circuit

Entity- discrepancies on pipe termination points are resolved by unassigning the pipe termination point from a circuit:

  • Unassigns the pipe termination point from the circuit using the updateCircuit method.

  • Updates the circuit using the updateProvisioningInfo MSS method.

Attribute Value Mismatch (Attribute) Discrepancy Resolution

Attribute discrepancies occur when an entity exists in the imported data and in your network data, but the attribute values in the two sets of information do not match. Network Integrity resolves this type of discrepancy by correcting the attribute values in MSS.

Equipment Mismatch

The MSS Integration cartridge resolves attribute discrepancies on equipment by running the MSS CORBA updateEquipment API method. This method belongs to NetworkElementSubSession of the EquipmentSession interface.

Circuit Channel Assignment Mismatch

This attribute discrepancy appears on trail pipes when a customer circuit is rerouted.

The MSS Integration cartridge resolves attribute discrepancies on circuits by identifying the timeslot on the circuit and using the following APIs:

  • To update a circuit entity attribute, calls the MSS EJB updateCircuit() API method.

  • To update a channel attribute, calls the MSS EJB updateProvisioningInfo() API method.

The MSS Integration cartridge also calls the necessary MSS APIs to unassign the circuit from its timeslot before setting the new attribute value.

PKܠ=G=PKH\lC OEBPS/toc.htm$' Table of Contents

Contents

Title and Copyright Information

Preface

1 Overview

2 About Cartridge Components

3 Cartridge Usage

4 About Collected Data

5 About Cartridge Modeling

6 Design Studio Construction

7 Design Studio Extension

PK<$$$PKH\lCOEBPS/mss_data_col.htm About Collected Data

4 About Collected Data

This chapter explains how the Oracle Communications Network Integrity MSS Integration cartridge treats the data it collects.

About Collected Data

The MSS Integration cartridge retrieves inventory data from the following Oracle Communications MetaSolv Solution (MSS) staging tables:

  • ee_equipment: contains the root equipment information. See Table 4-1 for more information.

  • ee_equipment_mounting_position_hier: contains the equipment hierarchy information for each root equipment. See Table 4-2 for more information.

  • ee_equipment_port_address: contains the circuit-to-equipment association information. See Table 4-3 for more information.

  • ce_circuit: contains circuit information for physical and logical circuits. See Table 4-4 for more information.

  • ce_circuit_position: contains the parent-child-circuit relationship information. See Table 4-5 for more information.

  • ce_port_address: contains the circuit-to-equipment association information. See Table 4-6 for more information.

The following tables describe the contents of the MSS staging tables from where the MSS Integration cartridge retrieves inventory data.

Table 4-1 describes the contents of the ee_equipment staging table, which is made up of the Equipment, Equipment Spec, and Network Location tables from MSS.

Table 4-1 ee_equipment Staging Table

Column NameData TypeDescription

EQUIPMENT_ID

NUMBER (9,0)

The unique table key.

EQUIPMENT_NAME

VARCHAR2 (15 BYTE)

The equipment name.

SOFTWARE_RELEASE_IDENTIFIER

VARCHAR2 (10 BYTE)

The current OS software release. For example, a Northern Telecom DNX-100 DACS with an OS software release of NSR-5.

EQUIPMENT_SPEC_ID

NUMBER (9,0)

A system identifier used for storing and retrieving information about an equipment specification.

VERSION_OF_HARDWARE_INSTALLED

VARCHAR2 (20 BYTE)

The installed hardware equipment version.

SERIAL_NBR

VARCHAR2 (35 BYTE)

The unique equipment identifier. This information is kept in a circuit attribute.

AVAILABILITY_STATUS

CHAR (1 BYTE)

The current object state, where I is Installed, S is Spare, and U is Under Construction.

LOCATION_ID

NUMBER (9,0)

The equipment location ID.

LOC_ID_CLLI_CODE

VARCHAR2 (20 BYTE)

The common language location identifier (CLLI) code value for the A-Location ID.

LOC_ID_NAME

VARCHAR2 (50 BYTE)

The location name for the A-Location ID.

LAST_MODIFIED_USERID

VARCHAR2 (8 BYTE)

The user ID that last modified the record.

LAST_MODIFIED_DATE

DATE

The last modified date of the record.

NETWORK_NODE_ID

NUMBER (9,0)

The unique network node identifier.

EQUIPMENT_ACRONYM

VARCHAR2 (10 BYTE)

The equipment acronym.

VENDOR_PART_NUMBER

VARCHAR2 (25 BYTE)

The equipment part number assigned by the manufacturer.

OCCUPIES_MOUNTING_POSITIONS

NUMBER (4,0)

The number of slots required to mount the equipment (bay/rack/shelf).

TIMING_SOURCE

VARCHAR2 (15 BYTE)

The equipment originating timing signal. Valid values include External, Loop/Line, and Internal.


Table 4-2 describes the contents of the ee_equipment_mounting_position_hier staging table, which is made up of the Mounting Position and Equipment Spec tables from MSS.

Table 4-2 ee_equipment_mounting_position_hier Staging Table

Column NameData TypeDescription

ROOT_EQUIPMENT_ID

NUMBER (9,0)

The parent equipment ID associated with a Network Node.

LOCATION_ID

NUMBER (9,0)

The location ID of the parent equipment.

CLLI_CODE

VARCHAR2 (20 BYTE)

The CLLI code for the parent equipment location.

ASSIGNMENT_SEQ

NUMBER (9,0)

N/A: not used.

EQUIPMENT_NAME

VARCHAR2 (50 BYTE)

The parent equipment name associated to the network node.

NETWORK_NODE_ID

NUMBER (9,0)

The equipment network node ID.

NW_TARGET_IDENTIFIER

VARCHAR2 (25 BYTE)

The equipment network element (NE) address, used to communicate with the OS of an NE.

NW_NODE_NAME

VARCHAR2 (50 BYTE)

The network node name of the parent equipment.

MTG_POS_NBR_HIER

VARCHAR2 (50 BYTE)

The hierarchical mounting position number information from the end card to the parent equipment, delimited by $$. The first *0 is ignored.

MTG_POS_SEQ_HIER

VARCHAR2 (50 BYTE)

The hierarchical mounting position sequence information from the end card to the parent equipment, delimited by $$. The first *0 is ignored.

SLOT_NODE_ADDRESS_HIER

VARCHAR2 (100 BYTE)

The hierarchical slot node address information from the end card to the parent equipment, delimited by $$.

EQUIPMENT_NAME_HIER

VARCHAR2 (100 BYTE)

The hierarchical equipment name information from the end card to the parent equipment, delimited by *.

VENDOR_PART_NUMBER_HIER

VARCHAR2 (150 BYTE)

The hierarchical vendor part number information from the end card to the parent equipment, delimited by $$.

EQUIPMENT_ACRONYM_HIER

VARCHAR2 (75 BYTE)

The hierarchical equipment acronym information from the end card to the parent equipment, delimited by $$.

VENDOR_NAME_HIER

VARCHAR2 (130 BYTE)

The hierarchical vendor name information from the end card to the parent equipment, delimited by $$.

GROUP_IDENTIFIER_HIER

VARCHAR2 (100 BYTE)

The hierarchical group identifier information from the end card to the parent equipment, delimited by $$. You can use this value to associate mounting positions and port addresses with additional information for an equipment.

EQUIPSPEC_TYPE_HIER

VARCHAR2 (350 BYTE)

The hierarchical equipment spec type information from the end card to the parent equipment, delimited by $$.

LAST_MODIFIED_USERID

VARCHAR2

The user ID that last modified the record.

LAST_MODIFIED_DATE

DATE

The last modified date of the record.


Table 4-3 describes the contents of the ee_equipment_port_address staging table, which contains equipment port address information from MSS.

Table 4-3 ee_equipment_port_address MSS Staging Table

Column NameData TypeDescription

LOCATION_ID

NUMBER (9,0)

The location ID after a successful full extraction into this staging table.

EQUIPMENT_ID

NUMBER (9,0)

A unique identifier used to store and retrieve information about equipment.

PORTADDR_SEQ

NUMBER (9,0)

The unique identifier and sequence port address for an equipment specification or equipment.

NODE_ADDRESS

VARCHAR2 (30 BYTE)

The physical or logical address for a specific port or channel addressing designation on a port address. This value can be derived from the node address of the equipment specification. There are three types of node address:

  • static addresses, which remain constant regardless of where the device is installed

  • variable addresses, that derive their value from their hierarchy (such as a DCM card in a DCM shelf, whose node address is a combination of its shelf and bay values)

  • variable addresses, that derive their value from the slot in which they are installed (such as a slow-speed card in a DDM2000 shelf, whose node address is sequentially determined)

RATE_CODE

VARCHAR2 (10 BYTE)

The bit rate associated with a circuit, facility, or equipment.

EXCHANGE_CARRIER_CIRCUIT_ID

VARCHAR2 (53 BYTE)

The assigned or provided circuit number (EC ID).

CIRCUIT_DESIGN_ID

NUMBER (9,0)

The unique identifier for storing and retrieving information about a circuit.

PORT_ADDR_STATUS

CHAR (1 BYTE)

The current circuit position status, where 1 is Unassigned, 2 is Pending installation work order, 3 is In service, 4 is Pending removal work order, 5 is Trouble, 6 is Reserved, and 7 is Reserved Capacity.

PORTADDR_TYPE

CHAR (1 BYTE)

The port address type, either physical or virtual. Physical ports have hard-wired connections and include their enabled (software) ports. Virtual ports have no actual physical appearance or connection and are entirely in the software of the equipment.

CIRCUIT_POSITION_NUMBER_CP

NUMBER (9,0)

The sub-position within a mounting position for plug-in cards that have multi position capabilities. This field identifies the multiple position number of a transmission facility circuit (TFC) or a channel number within a carrier system. This number may correspond to the mounting position of the equipment used to terminate the TFC. This column on this table is a foreign key describing the circuit position that this port address enables.

CIRCUIT_DESIGN_ID_CP

NUMBER (9,0)

A system identifier used for storing and retrieving information about a circuit. This column on this table is a foreign key describing the circuit position that this port address enables.

NODE_ADDR_LEVELS

VARCHAR2 (2 BYTE)

The number of equipment (from circuit_attachable) used to determine node_address.

ORIG_ASSIGNMENT_IND

CHAR (1 BYTE)

An identifier used to designate whether an equipment assignment is the original assignment in a cross-connect chain. This identifier is used by the Discrepancy Resolution action.

LAST_MODIFIED_USERID

VARCHAR2 (32 BYTE)

The user ID that last modified the record.

LAST_MODIFIED_DATE

DATE

The last modified date of the record.


Table 4-4 describes the contents of the ce_circuit staging table, which contains the physical and logical circuit information from MSS.

Table 4-4 ce_circuit Staging Table

Column NameData TypeDescription

CIRCUIT_DESIGN_ID

NUMBER(9, 0)

The circuit ID.

ECCKT

VARCHAR2(90)

The exchange carrier circuit ID.

ECCKT_TYPE

VARCHAR2(3)

The exchange carrier type.

TYPE

CHAR

The circuit type.

STATUS

CHAR

The circuit status.

RATE_CODE

VARCHAR2(10)

The circuit capacity.

SERVICE_TYPE_CATEGORY)

VARCHAR2(20

N/A

SERVICE_TYPE_CODE

VARCHAR2(10)

N/A

NST_CON_CATEGORY_CD

NUMBER(10)

N/A

NST_CON_TYPE

NUMBER(10)

N/A

LOC_A_CLLI_CODE

VARCHAR2(20)

The start location CLLI code.

LOCATION_ID

NUMBER

The start location ID.

LOC_A_NAME

VARCHAR2(20)

The start location name.

LOC_Z_CLLI_CODE

VARCHAR2(20)

The end location CLLI code.

LOCATION_ID_2

NUMBER(9)

The end location ID.

LOC_Z_NAME

VARCHAR2(20)

The end location name.

LAST_MODIFIED_USERID

VARCHAR2(8)

The user ID that last modified the record.

LAST_MODIFIED_DATE

DATE

The date the record was last modified.


Table 4-5 describes the contents of the ce_circuit_position staging table, which contains relationship information between parent and child circuits.

Table 4-5 ce_circuit_position Staging Table

Column NameData TypeDescription

CIRCUIT_DESIGN_ID

NUMBER(9, 0)

The circuit ID.

LOCATION_ID

NUMBER(9,0)

The location ID.

PARENT_CIRCUIT_DESIGN_ID

NUMBER(9, 0)

The parent circuit ID.

PARENT_ECCKT

VARCHAR2(60)

The parent circuit exchange carrier circuit ID.

CIRCUIT_POSITION_NUMBER

NUMBER(5)

The circuit position number in the parent circuit.

ASSIGNMENT_SEQ

NUMBER(3)

N/A

PARENT_TYPE

CHAR

The parent circuit type.

PARENT_SERVICE_TYPE_CATEGORY

VARCHAR2(20)

N/A

PARENT_SERVICE_TYPE_CODE

VARCHAR2(10)

N/A

PARENT_ECCKT_TYPE

VARCHAR2(3)

N/A

PARENT_RATE_CODE

VARCHAR2(10)

N/A

CIRCUIT_NODE_STATUS

CHAR

N/A

STS_CHAN_NBR

NUMBER(3)

N/A

VTG_CHAN_NBR

NUMBER(1)

N/A

VT_CHAN_NBR

NUMBER(1)

N/A

JKLM

VARCHAR2(50)

The circuit channel information.

LAST_MODIFIED_USERID

VARCHAR2(8)

The user ID that last modified the record.

LAST_MODIFIED_DATE

DATE

The date the record was last modified.

PROTECTED_PATH_TRI

CHAR

The protected path indicator.


Table 4-6 describes the contents of the ce_port_address staging table, which contains information that associates circuits to equipment.

Table 4-6 ce_port_address Staging Table

Column NameData TypeDescription

CIRCUIT_DESIGN_ID

NUMBER(9)

The circuit ID.

EQUIPMENT_ID

NUMBER(9)

The connected equipment ID.

PORTADDR_SEQ

NUMBER(9)

The connected port address.

PORT_ADDR_STATUS

CHAR(1)

The status of the connected port.

LOCATION_ID

NUMBER(9, 0)

The location ID.

ASSIGNMENT_SEQ

NUMBER(9)

N/A

EQUIPMENT_NAME

VARCHAR2(50)

The equipment name.

CIRCUIT_POSITION_NUMBER_CP

NUMBER(9)

The parent circuit position number.

CIRCUIT_DESIGN_ID_CP

NUMBER(9)

The parent circuit ID.

RATE_CODE

VARCHAR2(10)

The circuit capacity.

A_Z_OTHER_CD

CHAR(1)

N/A

EQUIPMENT_ID_VE

NUMBER(9)

The connected equipment parent equipment ID.

PORTADDR_SEQ_VE

NUMBER(9)

N/A

NODE_ADDR_LEVELS

VARCHAR2(2)

N/A

NETWORK_NODE_ID

NUMBER(9)

The node ID.

ORIG_ASSIGNMENT_IND

CHAR(1)

N/A

ADDTIONAL_ASSIGNMENT_SEQ_NBR

NUMBER(2)

N/A

PORTADDR_TYPE

CHAR(1)

N/A

CLLI_CODE

VARCHAR2(20)

The location CLLI code.

MTG_POS_NBR_HIER

VARCHAR2(50)

The mounting position number hierarchy.

MTG_POS_SEQ_HIER

VARCHAR2(50)

The mounting position sequence hierarchy.

SLOT_NODE_ADDRESS_HIER

VARCHAR2(100)

The slot node address hierarchy.

EQUIPMENT_NAME_HIER

VARCHAR2(500)

N/A

VENDOR_NAME_HIER

VARCHAR(130)

N/A

GROUP_IDENTIFIER_HIER

VARCHAR(100)

N/A

EQUIPSPEC_TYPE_HIER

VARCHAR(350)

N/A

LAST_MODIFIED_USERID

VARCHAR2(8)

The user ID that last modified the record.

LAST_MODIFIED_DATE

DATE

The last modified date of the record.


PKxY9PK H\lCoa,mimetypePKH\lC.j id:iTunesMetadata.plistPKH\lCYuMETA-INF/container.xmlPKH\lC[pTOOEBPS/cover.htmPKH\lC1r]OEBPS/mss_studio_ext.htmPKH\lCg#QLOEBPS/mss_cart_usage.htmPKH\lCH4Y Y?1OEBPS/mss_studio_const.htmPKH\lC _V/*OEBPS/title.htmPKH\lC-  OEBPS/preface.htmPKH\lCA mlIOEBPS/mss_modeling.htmPKH\lC*1,,!OEBPS/img/mss_action_imp_proc.gifPKH\lCچ̈́&EOEBPS/img/mss_action_circ_disc_det.gifPKH\lC6ql$ \OEBPS/img/mss_action_eq_disc_det.gifPKH\lCn>!lOEBPS/img/mss_action_disc_res.gifPKH\lCh;)%OEBPS/img_text/mss_action_eq_disc_det.htmPKH\lC<{+zOEBPS/img_text/mss_action_circ_disc_det.htmPKH\lCཊ* ёOEBPS/toc.ncxPKH\lCI ttۛOEBPS/mss_overview.htmPKH\lCu:]X(OEBPS/content.opfPKH\lC_ *OEBPS/dcommon/prodbig.gifPKH\lCY@ 1OEBPS/dcommon/doclib.gifPKH\lC}}n2OEBPS/dcommon/oracle-logo.jpgPKH\lCOEBPS/dcommon/contbig.gifPKH\lCOEBPS/dcommon/darbbook.cssPKH\lCMά""!OEBPS/dcommon/O_signature_clr.JPGPKH\lCPz OEBPS/dcommon/feedbck2.gifPKH\lC-sOEBPS/dcommon/feedback.gifPKH\lCː5OEBPS/dcommon/booklist.gifPKH\lCSOEBPS/dcommon/cpyr.htmPKH\lC!:3.3OEBPS/dcommon/masterix.gifPKH\lCeӺ1,OEBPS/dcommon/doccd.cssPKH\lC7 $OEBPS/dcommon/larrow.gifPKH\lC#KOEBPS/dcommon/indxicon.gifPKH\lCS'"OEBPS/dcommon/leftnav.gifPKH\lChu,$OEBPS/dcommon/uarrow.gifPKH\lCl-OJ?OEBPS/dcommon/oracle.gifPKH\lC( OEBPS/dcommon/index.gifPKH\lCGC  OEBPS/dcommon/bookbig.gifPKH\lCJV^:OEBPS/dcommon/rarrow.gifPKH\lC枰pkUOEBPS/dcommon/mix.gifPKH\lCo"nR M OEBPS/dcommon/doccd_epub.jsPKH\lCv I &OEBPS/dcommon/toc.gifPKH\lC r~$'OEBPS/dcommon/topnav.gifPKH\lC1FAZ)OEBPS/dcommon/prodicon.gifPKH\lC3( # ,OEBPS/dcommon/bp_layout.cssPKH\lCx[?:Y:OEBPS/dcommon/bookicon.gifPKH\lCp*c^?OEBPS/dcommon/conticon.gifPKH\lCʍCOEBPS/dcommon/blafdoc.cssPKH\lC+&ZOEBPS/dcommon/rightnav.gifPKH\lCje88[OEBPS/dcommon/oracle-small.JPGPKH\lCއ{&!>OEBPS/dcommon/help.gifPKH\lCܠ=G=OEBPS/mss_cart_components.htmPKH\lC<$$$ :7OEBPS/toc.htmPKH\lCxY9R\OEBPS/mss_data_col.htmPK66(