Skip Headers
Oracle® Communications Unified Inventory Management Release Notes
Release 7.2.2

Part Number E36034-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

Oracle® Communications Unified Inventory Management

Release Notes

Release 7.2.2

E36034-03

July 2013

This document provides the following information about Oracle Communications Unified Inventory Management (UIM) Release 7.2.2 Patchset 2.

This document also includes information about the previous releases, UIM Release 7.2, 7.2.2 and 7.2.2 Patchset 1. See "UIM 7.2 Release Notes", "UIM 7.2.2 Release Notes", and "UIM 7.2.2 Patchset 1 Release Notes".

For UIM installation instructions, refer to UIM Installation Guide. For Design Studio installation instructions and compatibility information, see Design Studio Installation Guide.

Technology Pack Version Compatibility

Table 1 indicates the technology pack versions that are supported on the most recent releases of UIM. See Design Studio Installation Guide for information about compatible UIM and Design Studio versions.

Table 1 Technology Pack Version Compatibility

Technology Pack UIM 7.1.1 UIM 7.1.2 UIM 7.2 UIM 7.2.2

MPLS L3 VPN Technology Pack

2.1.0 b56

2.2.0

7.2.0

7.2.2

Consumer VoIP Technology Pack

1.1.0 b56

1.2.0

7.2.0

7.2.2

Metro Ethernet Technology Pack

1.1.0 b56

1.2.0

7.2.0

7.2.2

L2 VPN Technology Pack

1.1.0 b56

1.2.0

7.2.0

7.2.2

GSM 3GPP Technology Pack

Not supported

Not supported

7.2.0

7.2.2

Cable TV Technology Pack

Not supported

Not supported

7.2.0

7.2.2


Design Studio Compatibility

New features in UIM 7.2.2 Patchset 2 require the use of Design Studio Release 7.2.2.4.

Product Documentation

This section provides information about the UIM documentation set.

Note:

The documentation set is not being updated for UIM 7.2.2 Patchset 2. Continue using the UIM 7.2.2 documentation set along with these Release Notes.

Note:

If you have not installed UIM 7.2.2 and plan on installing UIM 7.2.2 Patchset 2, then perform the installation as a new installation and not a patch installation. Use the UIM 7.2.2 documentation, but note that the software pack will be named slightly differently.

How to access documentation

Documentation is available, in the following media packs, on the Oracle software delivery Web site at:

https://edelivery.oracle.com

  • The Documentation for Oracle Communications Unified Inventory Management Media Pack contains most of the Unified Inventory Management product documentation, including the technology pack documentation.

  • The Oracle Communications Unified Inventory Management Developer Documentation Media Pack contains documentation that is targeted for developers, such as UIM Developer's Guide. This Documentation Pack requires a password for access.

Acrobat Reader is required to view the documentation. If you do not have Adobe Acrobat Reader, download a free copy from Adobe Systems at:

http://www.adobe.com/

Documentation set

The core documentation set for the Unified Inventory Management 7.2.2 release includes the following:

  • UIM Installation Guide

  • UIM System Administrator's Guide

  • UIM Security Guide

  • UIM Developer's Guide

  • UIM Information Model Reference

  • Oracle Communications Information Model Reference

  • UIM Cartridge and Technology Pack Guide

  • UIM technology pack implementation guides

  • UIM online Help

  • Design Studio for UIM online Help

UIM 7.2.2 Patchset 2 New Features

This section provides information about the new features introduced in UIM 7.2.2 Patchset 2.

Note:

The documentation set is not being updated for UIM 7.2.2 Patchset 2. Continue using the UIM 7.2.2 documentation set along with these Release Notes.

Cloning Logical Devices

UIM 7.2.2 Patchset 2 introduces the ability to clone logical devices. Cloning is different from the existing ability to duplicate entities because it can copy associations in addition to the entity itself. By default, the cloned logical device is an exact copy of the original (aside from entity ID), but you can customize the content of the clone.

By default, the following associations and mappings are copied when you clone a logical device:

  • Device interface hierarchy

  • Mapped physical devices

  • Equipment associations with physical devices

  • Mappings between device interfaces provided by the logical device and ports and connectors provided by physical devices and equipment

  • Cross-connects between device interfaces

You can customize the clone in the following ways:

  • Specifying names of logical device, physical device, and equipment created as part of the cloning operation

  • Assigning the cloned device to a different property location

  • Excluding specific items in the logical device hierarchy

  • Excluding specific physical device mappings and equipment associations

You can begin a logical device cloning operation from physical device search results or from a Physical Device Summary work area. In this situation, the logical device associated to the physical device is cloned. If you want to copy only the physical device, you can use the existing Duplicate feature. Equipment entities associated to the physical device are not copied during by the Duplicate operation, however.

To clone a logical device:

  1. Do one of the following:

    • In the Search Results panel of a Logical Device Search work area, select a logical device and click the Clone button.

    • In the Search Results panel of a Physical Device Search work area, select a physical device that has a logical device association and click the Clone button.

    • In a Logical Device Summary work area, select Clone from the Actions menu.

    • In the Physical Device Summary work area of a physical device that has a logical device association, select Clone from the Actions menu.

    The Logical Device - Clone work area appears. The work area includes panels that display information about the existing logical device, some of which you can change for the cloned logical device.

  2. (Optional) In the Entity Cloning Information panel, enter text in the Logical Device Name and Physical Device Name fields.

    These names are used for all entities of the relevant types created during the cloning.

  3. (Optional) In the Entity Cloning Information panel, enter a prefix in the Equipment Name Prefix field.

    This prefix and an underscore character is added to the names of all Equipment entities created during the cloning.

  4. (Optional) Specify a different property location for the cloned device:

    1. In the Location for Cloned Device panel, click the Select button.

      The Property Location Search work area appears.

    2. Search for property locations.

    3. Select a property location and then click OK.

      The Property Location Search area closes and the Location for Cloned Device panel updates to reflect the new property location.

  5. (Optional) Select devices and interfaces to exclude from cloning:

    1. In the Logical Device Hierarchy panel, expand the hierarchy.

      Each logical device and device interface has a check box that is selected by default.

    2. De-select any logical devices or device interfaces that you do not want to include in the cloned logical device. De-selecting a parent device in the hierarchy automatically de-selects its children.

  6. (Optional) Select mapped physical devices and equipment to exclude from cloning:

    1. In the Logical Device Hierarchy panel, select a logical device or device interface.

      The Mapped Physical Device Hierarchy panel displays the hierarchy of mapped physical devices and associated equipment for the selected logical device or device interface. Physical devices and equipment in the hierarchy are selected unless the corresponding logical device or device interface is de-selected in the Logical Device Hierarchy panel.

    2. De-select any physical devices or equipment that you do not want to include in the cloned logical device.

  7. Click the Clone button.

    The Logical Device - Clone work area closes and the Summary work area for the cloned logical device appears.

Network Location Support for Equipment and Physical Device Entities

UIM 7.2.2 Patchset 2 introduces network location support for Equipment and Physical Device entities. There are three ways in which these entities can be associated with network locations:

  • By associating a Physical Device or Equipment entity with a logical device that has a network or network entity code or with a logical device in the hierarchy of a parent logical device with such a code.

  • By specifying a network location code when you create the entity. A Network Location field now appears in the Create work area for Equipment and Physical Device entities.

  • By editing a Equipment or Physical Device entity to include a network code. A Network Location field appears in the Information work area that you see when you edit entities of these types.

Network location codes are propagated downward through physical device and equipment hierarchies. The highest-level entity that has a network location code is the location parent for the hierarchy.

Note:

Equipment and Physical Device entities cannot be assigned network entity codes. Network entity codes are valid only for logical devices.

Because equipment hierarchies can include only other Equipment entities, the propagation of network location codes is straightforward. All Equipment entities below the location parent are assigned the network location code assigned to the parent. You cannot change these codes for the child entities unless you also change the code for the parent.

Figure 1 illustrates a small Equipment hierarchy. All the entities have the network code PLANTXUSXA.

Figure 1 Network Location Code for Equipment Hierarchy

Description of Figure 1 follows
Description of "Figure 1 Network Location Code for Equipment Hierarchy"

Physical device hierarchies can include other physical devices. In addition, physical devices can be associated with Equipment entities. In this kind of hierarchy, all physical devices in the hierarchy and all Equipment entities associated with physical devices in the hierarchy are automatically assigned the network location code of the parent physical device. You cannot change the automatically assigned network location codes.

Figure 2 illustrates a physical device hierarchy in which physical devices are associated with Equipment entities. All of the entities in this hierarchy are assigned the PLANTXUSXA network code of the parent physical device.

Figure 2 Network Location Code Physical Device Hierarchy

Description of Figure 2 follows
Description of "Figure 2 Network Location Code Physical Device Hierarchy"

Logical device hierarchies can be complex because logical devices can be associated with physical devices, which in turn can be associated with Equipment entities. In addition, logical devices can have network location codes or network entity location codes.

In a logical device hierarchy, child logical devices inherit the network location code or network entity location code of the parent logical device. Physical devices and Equipment entities inherit only the network location code.

In the hierarchy shown in Figure 3, the logical devices have inherited the parent logical device's network entity location code (PLANTXUSXA.K02). Physical devices associated with logical devices in the hierarchy inherit only the network location code (PLANTXUSXA). You cannot change any of the automatically assigned network location or network entity location codes.

Figure 3 Network and Network Entity Location for Logical Device Hierarchy

Description of Figure 3 follows
Description of "Figure 3 Network and Network Entity Location for Logical Device Hierarchy"

Network location associations to Equipment and Physical Device entities cannot be made if the association currently or potentially conflicts with a network location association. The conflict does not necessarily have to be direct: it can result from associations related to hierarchies in which the entity participates. For example, you cannot directly assign a network location code to an Equipment entity that is associated to a physical device that has inherited a network location from a parent physical device. In this situation, the Equipment entity already has a network location code that it inherits from the associated physical device. Similarly, you cannot remove or change an inherited network location or network entity location code without either removing the entity in question from its hierarchy or association. Alternatively, you can change or remove the network location or network entity location code from the location parent entity. Removing or changing that code removes or changes it in all entities that have inherited it.

Enhancements to Pipe Entities

You can now select network locations and network entity locations as the source, intermediate, and target types for path analysis for pipes. New Network/Entity Location entries appear in the Type fields in Path Analysis Search work area. See UIM Concepts and UIM online Help for more information about path analysis.

In addition, the Pipe Summary work area has been enhanced to display information about termination points that is similar to what is displayed in the Connectivity Details work area. The Termination Points panel in the Pipe Summary work area now includes network location and termination information for logical devices, physical devices, and equipment that are associated with the pipe's termination points. If the termination points do not have a resource associations, this information is omitted. If more than one resource is associated with a termination point, information about only the first resource is displayed.

The location information is derived the locations of the resources associated with the termination point. If the resource has no location information, no location is shown for the termination point.

Virtual Connectivity Enhancement

To support virtual connectivity (introduced in UIM 7.2.2 Patchset 1), you can now select the sub-interface corresponding to the associated parent channel when assigning a device interface to a termination point of a channelized connection. The device interface must be provided by a logical device at the same Network entity code as the termination point.

Selecting this sub-interface is not mandatory; you can select a different interface. You cannot select a sub-interface corresponding to a different channel on the facility.

Service Information Displayed for Logical Devices and Pipes

You can now view information about the services whose configurations include assignments or references to a logical device or pipe that you are viewing. Pipe Summary and Logical Device Summary work areas now include Services panels that display the name and other identifying information of services, the type of relationship with the entity (assignment or reference), the start and end dates of the relationship, and the number of parties. Figure 4 illustrates the new panel.

Figure 4 Logical Device Summary Work Area with Services Panel

Description of Figure 4 follows
Description of "Figure 4 Logical Device Summary Work Area with Services Panel"

Network Topology and Map Viewer Enhancements

UIM 7.2.2 Patchset 2 includes enhancements related to the network visualization and map viewer.

Network Entity Location Support

Network nodes can now represent network locations and network entity locations. A network location is a property location that has been assigned a network location code. A network entity location is a network location that hosts a network entity.

You use the same procedure for representing and removing network and network entity locations that you do for other entities. See the UIM online Help for more information.

When you choose a connectivity for a network edge to represent, UIM checks the network location and network edge associations of the network nodes against the end points of the connectivity. If the connectivity has end points other than those associated to the network nodes, UIM prevents you from selecting that connectivity.

There are some restrictions on when you can remove a network location or network entity location association from a node:

  • When a network node is connected to a network edge that represents a channelized connectivity, you cannot remove the node's association to a network or network entity location. In this situation, the connectivity is associated to the network or network entity location, so removing the node-to-location association would result in data inconsistency.

  • When a network node is associated to a logical device, device interface, physical device, or physical port, you cannot remove the node's association to a network or network entity location. In this situation, the network or network entity location is also associated to the additional resource that the node represents. Removing the node-to-location association would cause data inconsistency.

There are two ways to associate a node with both a logical device and a network location or network entity location:

  • Associate the node with a network location and then associate it with a logical device. When you associate the logical device, the work area used to select the device automatically includes the location as a search criterion.

  • Associate the node with a logical device that is already hosted by a network entity location. The association from the node to the location is made automatically in this situation.

If you remove a logical device from a network node, the network location association is also removed unless the network node is connected to a network edge that is associated with a connectivity.

Map Viewer Support for Connectivity and Property Locations

The Map View has been enhance in UIM 7.2.2 Patchset 2 to support the display of edges associated with channelized connectivity and nodes associated with network locations. For example, the Network Visualization depicted in Figure 5 includes three network nodes, each of which is associated with a network location. Two network edges, each associated with a channelized connectivity, connect the nodes.

Figure 5 Network Visualization with Network Locations and Connectivities

Description of Figure 5 follows
Description of "Figure 5 Network Visualization with Network Locations and Connectivities"

In the Map Viewer, these nodes and edges along with their associated resources, are depicted as shown in Figure 6. One node is selected to show its details.

Associating and Referencing Channelized Connectivity in Service Configurations

You can now associate or reference a channelized connectivity as a configuration item in a service configuration. Before you can make such an associate or reference in UIM, the TDM Facility specification must be added as an association or reference configuration item to the specification of the relevant Service Configuration specification. See Design Studio online Help for information about adding associations and references to configuration specifications. See UIM online Help for information about associating and referencing resources as configuration items.

This feature has been added to support leased line services. A leased line is a service contract between a provider and a customer in which the provider delivers a telecommunications line for service locations. It is sometimes known as a private circuit or data line. This line can be offered as channelized connectivity.

The Connectivity Details work area now includes information about the assignment of the connectivity. The General Information tab displays the current assignment status and the name and ID of the service (if any) to which the connectivity is assigned.

In addition, Channels tab of the Connectivity Details work area now contains a Services column in the channels table. This column lists all the services that consume connectivities enabled by the channels (riders). For example, in Figure 7, connectivity ABC/DEF/E3/E3/1 is riding on channel 1 of the connectivity ABC/DEF/E4/E4/1 Connectivity ABC/DEF/E3/E3/1 is assigned to service TDMService3.

Figure 7 Service Assignments for Connectivity Channels

Description of Figure 7 follows
Description of "Figure 7 Service Assignments for Connectivity Channels"

Fixes in UIM 7.2.2 Patchset 2

Table 2 lists customer-reported bugs that have been fixed in UIM 7.2.2 Patchset 2.

Table 2 Fixed Bugs

Bug/SR Component Description

16773119

Framework

Issue

Specifications are not visible in UIM after deployment of a cartridge bundle.

Resolution

The software has been modified to ensure that specifications are displayed properly after deployment of a cartridge bundle.

16773109

Framework

Issue

The session timeout value set in Weblogic is not reflected in UIM.

Resolution

The software has been modified to ensure that the timeout value set in Weblogic is honored in UIM.

16784456

Install

Issue

The Service Purge tool (ora_uim_dbtools.jar) fails with Sequence Does Not exist error

Resolution

The software has been fixed to ensure that the sequence ROWLOCKENTITY_SEQ is changed successfully.


Known Issues in UIM 7.2.2 Patchset 2

Table 3 lists the known issues in UIM 7.2.2 Patchset 2.

Note:

These issues are visible only if you are using Oracle Fusion Middleware 11g R1 Patch Set 6 (11.1.1.7).

Table 3 Known Issues

Bug Number Description Notes

17056388

The Express Configuration dialog box does not close when you click OK or Cancel.

You can close the dialog box and see the resulting changes by refreshing the browser after clicking OK or Cancel.

17023610

If you navigate to a Card Summary work area from an Equipment tree view, the tree view is blank when you navigate back by using the Recent Items menu.

The Equipment tree view displays correctly if you navigate from the Card Summary work area to the Shelf Summary work area before opening the tree view.

16773312

The Related Pages menu disappears after navigating back to a Pipe or Network Summary work area from the Network Topology work area.

Use the Tasks panel to search for the Pipe or Network Summary work area.


Documentation Updates in UIM 7.2.2 Patchset 2

The documentation set is not being updated for UIM 7.2.2 Patchset 2. Continue using the UIM 7.2.2 documentation set along with these Release Notes.

Note:

If you have not installed UIM 7.2.2 and plan on installing UIM 7.2.2 Patchset 2, then perform the installation as a new installation and not a patch installation. Use the UIM 7.2.2 documentation, but note that the software pack will be named slightly differently.

UIM 7.2.2 Patchset 1 Release Notes

This section includes information about UIM 7.2.2 Patchset 1, including new features introduced, known issues, and resolved issues.

Features Introduced in UIM 7.2.2 Patchset 1

This section provides information about features and capabilities introduced in UIM 7.2.2 Patchset 1.

Note:

The documentation set is not being updated for UIM 7.2.2 Patchset 1. Continue using the UIM 7.2.2 documentation set along with these Release Notes.

Logical Device Link in the Equipment Summary View

The Equipment Summary work area has been enhanced in UIM 7.2.2 Patchset 1 to include a logical device link. The logical device link is shown (see Figure 8) if a physical device associated to the equipment is associated to a logical device.

Figure 8 Logical Device Link

Description of Figure 8 follows
Description of "Figure 8 Logical Device Link"

You can navigate to the Logical Device Summary work area by clicking the Logical Device link. You can use the Recent Items link to navigate back to the Logical Device Summary work area.

Pipe Summary Work Area Displays Child Pipe Bandwidth Consumption

Pipes that represent packet connectivity do not have a Pipe Hierarchy panel. As a result, previous versions of UIM did not display bandwidth consumption by child pipes for packet connectivity.

The Pipe Summary work area has been enhanced in UIM 7.2.2 Patchset 1 to show the bandwidth consumption by child pipes.Refer to Figure 9.

Figure 9 Child Bandwidth Consumption Panel

Description of Figure 9 follows
Description of "Figure 9 Child Bandwidth Consumption Panel"

The following details are included in the Child Consumption table:

  • ID

  • Name

  • Specification

  • Inventory status

  • Consumption Percentage

  • Capacity Consumed

Pipe Termination Point Summary - Parent Entity Name of Resource Termination

The Termination Point Summary work area has been enhanced in UIM 7.2.2 Patchset 1 to show parent entity details for resource terminations.

Parent entity details are displayed for Physical Connector, Physical Port, and Device Interface entities.

The following details are new in the Resource Terminations table (see Figure 10):

  • Parent Name

  • Parent Type

  • Parent Specification

Figure 10 Parent Entity Details

Description of Figure 10 follows
Description of "Figure 10 Parent Entity Details"

You can navigate to the Summary work area of the parent entity by clicking the Parent Name. You can use the Recent Items link o navigate back to the Pipe Termination Point Summary work area.

Associated Logical Devices, Pipes, and Connectivities Added to the Network Summary Work Area

The Network Summary work area has been enhanced in UIM 7.2.2 Patchset 1 to include Associated Logical Devices and Associated Pipes/Connectivities panels (see Figure 11). These panels list the entities that represent the nodes and edges of the network.

Figure 11 Associated Logical Devices and Associated Pipes/Connectivities Panels

Description of Figure 11 follows
Description of "Figure 11 Associated Logical Devices and Associated Pipes/Connectivities Panels"

You can navigate to the Summary work area of the associated logical devices, pipes, or connectivities by clicking their respective ID column. You can use the Recent Items link to navigate back to the Network Summary work area.

Enhancements to Reservation Search

Reservation searches have been enhanced in UIM 7.2.2 Patchset 1 to include the following major changes:

  • New search criterion - Reserved By

  • New columns in the Search Results work area - Resource Name and Reserved By

  • New column in the Reservation List work area - Reserved By

New Search Criterion

A new search criterion called Reserved By has been introduced, enabling you to search for reservations based on the user who created them. Refer to Figure 12.

Figure 12 New Reservation Search Criterion

Description of Figure 12 follows
Description of "Figure 12 New Reservation Search Criterion"

New Columns in the Search Results Work Area

The Reservation Search Results table now contains the following new columns (see Figure 13):

  • Resource Name - displays the name of the resource that is reserved

  • Reserved By - displays the name of the user who created the resource reservation

Figure 13 New Columns in the Reservation Search Results Work Area

Description of Figure 13 follows
Description of "Figure 13 New Columns in the Reservation Search Results Work Area"

New Column in the Reservation List Work Area

The Reservation List work area now contains a Reserved By column to display the name of the user who created the resource reservation. Refer to Figure 14.

Figure 14 New Column in the Reservation List Work Area

Description of Figure 14 follows
Description of "Figure 14 New Column in the Reservation List Work Area"

In-line Selection of Role for Party and Place on Service Summary Work Area

The Service Summary work area has been enhanced in UIM 7.2.2 Patchset 1 to simplify the process of assigning roles to parties and places that you associate with a service.

This enhancement introduces the following capabilities:

  • You can create and associate a role when you search for a party to associate with the service.

  • You can create and associate a role when you search for a place to associate with the service.

Create and Associate Role to Party through the Party Search Work Area

You now have the ability to create roles for the party and associate the party with a service or any other entity.

When you associate the party to a service, the Associate Party dialog box is displayed. This dialog box allows you to search for and select the desired party. The Party Role dropdown lists the roles associated with that party and now includes the Create Role option.

The following steps detail how to create a role and associate the party.

  1. From the Tasks panel, select Services.

    The Service work area appears.

  2. Select the desired service and click the service ID.

    The Service Summary work area appears.

  3. Select the desired party and click Associate.

    The Associate Party dialog box appears.

  4. Select the desired party, click the dropdown in the Party Role column, and select the Create Role option.

    The Inventory Role - New panel appears.

    Note:

    The section header contains the name of the party to which the role will be assigned.
  5. From the Specification dropdown, select the role specification.

  6. Add any characteristics (if any), in the Char 2 field, and click Create Role.

    Note:

    Clicking Cancel closes the role creation section.
  7. On successful role creation, the newly created role is automatically selected in the dropdown for that party.

  8. Select the parties to associate, select the role from the dropdown, and click OK to associate.

    The associated parties are now listed in the Summary work area within the party panel.

Create and Associate Role to Place through the Place Search Work Area

You now have the ability to create roles for the place and associate the place with a service or any other entity.

When you associate the place to a service, the Associate Place dialog box is displayed. This dialog box allows you to search for and select the desired place. The Place Role dropdown lists the roles associated with that place and now includes the Create Role option.

The following steps detail how to create a role and associate the place.

  1. From the Tasks panel, select Services.

    The Service work area appears.

  2. Select the desired service and click the service ID.

    The Service Summary work area appears.

  3. Select the desired place and click Associate.

    The Associate Place dialog box appears.

  4. Select the desired place, click the dropdown in the Place Role column, and select the Create Role option.

    The role creation section appears.

    Note:

    The section header contains the name of the place to which the role will be assigned.
  5. From the Specification dropdown, select the role specification.

  6. Add any characteristics (if any), in the Char 2 field, and click Create Role.

    Note:

    Clicking Cancel closes the role creation section.
  7. On successful role creation, the newly created role is automatically selected in the dropdown for that place.

  8. Select the places to associate, select the role from the dropdown, and click OK to associate.

    The associated places are now listed in the Summary work area within the place panel.

UIM Topology Enhancements

The Network Topological View work area has been enhanced in UIM 7.2.2 Patchset 1. You can now select a set of pipes or TDM connectivities from the network canvas and use the selected pipes or TDM connectivities to create nodes and edges in the network. Previously, you had to create nodes and edges separately and then associate pipes and connectivities. Pipes and connectivities are displayed as edges and the devices to which they are associated (if any) are displayed as nodes representing those devices.

As with all network nodes, the nodes represent parent devices, not the interfaces, ports, or other entities that they provide. For example, if a pipe is terminated on a device interface, the network node represents the logical device that provides the interface. If a pipe or connectivity is terminated on a physical device that is associated with a logical device, then the node represents the logical device. See UIM Concepts for more information about how the UIM topology represents device hierarchies.

When you want to perform a layout at the time a pipe or TDM is translated onto the network, you can use the Auto-layout feature.

Note:

UIM prevents you from creating nodes and edges from a pipe or connectivity that is already associated with a network edge.
Associating TDM Connectivity

You can now automatically create nodes and edges based on existing TDM connectivities. A new icon (see Figure 15) has been added in the toolbar which can be used to select existing TDM Connectivity entities.

Figure 15 Associate TDM Connectivity Icon

Description of Figure 15 follows
Description of "Figure 15 Associate TDM Connectivity Icon"

  1. From the Topological View toolbar, click the Associate Connectivity icon.

    The Associate Connectivity dialog box appears.

  2. In the Search panel, click Search.

    The existing TDM connectivities appear in the Search Results panel.

  3. Select the desired TDM connectivities from the Search Results panel and click OK.

    UIM creates nodes and edges, along with their associated entities. Refer to Figure 16.

Figure 16 TDM Connectivity Translated into Network Nodes and Edges

Description of Figure 16 follows
Description of "Figure 16 TDM Connectivity Translated into Network Nodes and Edges"

Note:

If you select a TDM connectivity that is terminated to a property location and not to the device interface of a logical device associated to the property location, then the network node is not associated with the property location, but has the same name as the property location.
Associating Pipes

You can now automatically create nodes and edges based on existing pipes. A new icon (see Figure 17) has been added in the toolbar which can be used to select existing Pipe entities.

Figure 17 Associate Pipe Icon

This screen shot shows the new Associate Pipe icon.
  1. From the Topological View toolbar, click the Associate Pipe icon.

    The Associate Pipe dialog box appears.

  2. In the Search panel, click Search.

    The existing pipes appear in the Search Results panel.

  3. Select the desired pipes from the Search Results panel and click OK.

    UIM creates nodes and edges, along with their associated entities. Refer to Figure 18.

Figure 18 Pipe Translated into Network Nodes and Edges

Description of Figure 18 follows
Description of "Figure 18 Pipe Translated into Network Nodes and Edges"

When a pipe is terminated to a network, the network node has the network's name as its name, but the association is not there.

When two pipes terminate on different device interfaces, which are associated to the same logical device, then the network canvas translates the pipes as shown in Figure 19.

Figure 19 Pipes Associated to the same Logical Device

Description of Figure 19 follows
Description of "Figure 19 Pipes Associated to the same Logical Device"

UIM Custom Network Address Search Enhancement

The Custom Network Address Search has been enhanced in UIM 7.2.2 Patchset 1 to include the following major changes:

  • Additional Inventory Group Criteria

  • New API in Custom Network Address and Inventory Group searches

Additional Inventory Group Criteria

In the Custom Network Address Search panel, a new multi-select dropdown has been introduced which populates all inventory group instances. When you select one or more inventory groups, UIM searches for only the custom network addresses that are associated with those inventory groups. Every time you select a Custom Network Address specification, the inventory group multi-select dropdown is refreshed. Figure 20 shows the new multi-select dropdown field.

Figure 20 Inventory Group Multi-Select Dropdown

Description of Figure 20 follows
Description of "Figure 20 Inventory Group Multi-Select Dropdown"

The Search Results panel includes a column that shows the inventory groups with which the custom network addresses are associated. Refer to Figure 21.

Figure 21 Inventory Group Column

Description of Figure 21 follows
Description of "Figure 21 Inventory Group Column"

New API in Custom Network Address and Inventory Group

A new API, extendFilterForAdditionalCriteria(), provides the ability to extend the existing search criteria for Custom Network Address searches and Inventory Group searches.

You can extend this API through a custom extension point to invoke a custom ruleset that defines your specific search criteria needs.

Virtual Connectivity

UIM 7.2.2 Patchset 1 now supports virtual connectivity and termination. You can create Channelized Connectivity entities with VC4, VC3, VC2, VC11, and VC12 rate codes.

A connectivity is considered virtual when it does not terminate on its own device interface but rather on the sub-interfaces of the device interface on which its parent facility is terminated. VC4 facilities are a good example. A VC4 facility is used to abstract out the optical physical transport of traffic between two points in an SDH network. A VC4 facility effectively delivers a 155Mb connectivity. This connectivity can be configured now to carry lower-order traffic within lower-order containers (C4, C3s and C12s) to deliver E4, E3 and E1 services.

VC4 connectivities are used extensively in SDH networks to provide logical connectivity. A large part of SDH capacity planning is determining VC4 network location-to-location routes and monitoring the utilization levels of those routes. High utilization levels of the 16 lower-order (VC12) channels within VC4s is the main driver for deciding that a new VC4 path is required.

You can configure VC4 and VC3 connectivities to provide capacity at other levels. VC2, VC11 and VC12 connectivities have single-channel structures defined by the UIM Signal Architecture.

UIM 7.2.2 Patchset 1 supports gap analysis for VCn connectivities.

Note:

You cannot use a single channel of a facility to enable a connectivity when all three share the same rate code. For example, a VC4 channel provided by a VC4 facility cannot be used to enable another VC4 connectivity.
Virtual Termination

UIM 7.2.2 Patchset 1 supports the virtual termination of connectivities on device interfaces that already have channel terminations. Connectivities can be virtually terminated on the same device interfaces that already terminate its enabling channels. A connectivity that has a single default channel with the same rate code as its parent can be terminated on the same device interface that its parent is terminated on.

For example, virtual termination can be used when enabling a DS1 facility that is enabled by a DS1 channel from a DS3 facility. (See Figure 22.) The DS1 facility is virtually terminated on the same DS1 interfaces used to terminate its enabling DS1 channel. The DS0 channels provided by the DS1 facility can then be automatically terminated on sub-interfaces. These DS0 channel terminations are required to create cross-connects when the DS0 channels are used to enable DS0 service trails.

Figure 22 Virtual Termination on a DS1 Facility

Description of Figure 22 follows
Description of "Figure 22 Virtual Termination on a DS1 Facility"

Figure 23 illustrates an STMx facility providing a VC4 channel. This channel is used to enable a VC4 facility. Virtual terminations are created from the VC4 facility endpoints to the same VC4 sub-interfaces that already terminate the enabling VC4 channels. The VC4 facility is configured to have a single VC4 channel that enables an E4.

Figure 23 Virtual Termination on a VC4 Channel

Description of Figure 23 follows
Description of "Figure 23 Virtual Termination on a VC4 Channel"

Dense Wavelength Division Multiplexing Technology

Dense Wavelength Division Multiplexing (DWDM) is an optical technology used to increase bandwidth over existing fiber optic backbones. DWDM works by combining and transmitting multiple signals simultaneously at different wavelengths on the same fiber. In effect, one fiber is transformed into multiple virtual fibers. So, if you were to multiplex eight OC48 signals into one fiber, you would increase the carrying capacity of that fiber from 2.5 Gbps to 20 Gbps. Currently, because of DWDM, single fibers have been able to transmit data at speeds up to 400Gbps.

DWDM-based networks can carry different types of traffic at different speeds over an optical channel. DWDM-based networks can transmit data in SONET /SDH, and Ethernet, and can handle bit rates between 100 Mbps and 2.5 Gbps. So DWDM can act as bearer and other technologies can ride over it.

UIM 7.2.2 Patchset 1 supports DWDM as channelized connectivity, including the ability to carry SONET, SDH and Ethernet in DWDM channels.

To support the feature, a new cartridge (ora_uim_dwdm.jar) has been introduced. The cartridge defines the signal hierarchy and ratecodes supported by DWDM. It also defines compatibility between DWDM ratecodes and other technologies ratecodes.

You can create DWDM channelized connectivities with rate codes from OM160, OM96, OM80, OM40 through OM4.

The signal architecture defined by the DWDM cartridge determines how connectivities can be channelized. For example, an OM40 facility can be channelized down to OM8, OM4, and OM1. Figure 24 shows this channelization.

Figure 24 OM40 Channelization

Description of Figure 24 follows
Description of "Figure 24 OM40 Channelization"

You can enable an STM16 facility with an OM1 channels. For example, you can create an OM4 facility, channelize it down to OM1, and then use an OM1 channel to enable an STM16 facility. Figure 25 illustrates this scenario.

Figure 25 STM16 Facility Enabled by an OM1 Channel

Description of Figure 25 follows
Description of "Figure 25 STM16 Facility Enabled by an OM1 Channel"

You can also enable 10GE, 40GE and 100GE pipes with OM1, OM4, and OM10 DWDM channels.

Figure 26 illustrates a 10GE pipe enabled by an OM1 channel.

Figure 26 10Ge Pipe Enabled by an OM1 Channel

Description of Figure 26 follows
Description of "Figure 26 10Ge Pipe Enabled by an OM1 Channel"

Figure 27 illustrates a 40GE pipe enabled by an OM4 channel.

Figure 27 40Ge Pipe Enabled by an OM4 Channel

Description of Figure 27 follows
Description of "Figure 27 40Ge Pipe Enabled by an OM4 Channel"

You can also enable a 100GE pipe with an OM10 channel.

This feature supports enabling an OC192 SONET TDM Facility with a 10 Gbps DWDM channel and enabling an OC48 SONET TDM Facility with a 10 Gbps DWDM Channel.

Note:

Only a TDM facility with a transmission signal type of Optical can be enabled with a DWDM channel.

Fixes in UIM 7.2.2 Patchset 1

Table 4 lists customer-reported bugs that have been fixed in UIM 7.2.2 Patchset 1.

Table 4 Fixed Bugs

Bug/SR Component Description

15959097

Installation

Issue

Core dump happening while upgrading from 7.2.0.2 to 7.2.2 on Solaris.

Resolution

Software code has been modified to prevent a core dump from occurring during a software load upgrade.


Known Issues in UIM 7.2.2 Patchset 1

Table 5 lists the known issues in UIM 7.2.2 Patchset 1.

Table 5 Known Issues

Bug Number Description Notes

14634611

Configuring and saving high-rate-code SONET and SDH facilities takes a long time

Configuring, reconfiguring, and saving SONET and SDH facilities with high rate codes, such as STM 1024 to VC-x or VT-x, takes a long time. When such changes are saved this also is known to take a significant amount of time.

To avoid this issue, configure these facilities in steps or use Web services.

14635050

Processing signals displayed when no channels exist.

The connectivity channel and search tree views displays processing signals that were configured earlier, even if there are no channels currently under those processing signals.

14665548

Root node sometimes not visible in the Capacity tab

When you configure a facility by using the Capacity tab, the root node can sometimes disappear.

Click the Zoom to Fit button to restore the root node to the viewable area of the Capacity tab.

14754088

Auto-termination of channels for OC48 and higher rate facilities takes a long time.

When assigning interfaces to TDM facilities like OC48 or higher rate codes the auto-termination of TDM channels to the appropriate sub device interfaces is noted to take more than 2 minutes to complete.

14841339

Unable to channelize SDH facility below VC3 without TUG-3

It is not currently possible to channelize an SDH facility to VC3 or a lower rate (VC2,VC12, or VC11) without multiplexing through TUG-3.


Documentation Updates in UIM 7.2.2 Patchset 1

The documentation set is not being updated for UIM 7.2.2 Patchset 1. Continue using the UIM 7.2.2 documentation set along with these Release Notes.

Note:

If you have not installed UIM 7.2.2 and plan on installing UIM 7.2.2 Patchset 1, then perform the installation as a new installation and not a patch installation. Use the UIM 7.2.2 documentation, but note that the software pack will be named slightly differently.

UIM 7.2.2 Release Notes

This section includes information about UIM 7.2.2, including new features introduced, known issues, and resolved issues.

Features Introduced in UIM 7.2.2

This section provides information about features and capabilities introduced in UIM 7.2.2.

Support For Channelized Connectivity

UIM 7.2.2 includes enhanced support for time-division multiplexing (TDM), a form of channelized connectivity that divides a signal into recurrent time slots, one for each channel.

UIM provides specialized features to support several different TDM technologies, including SONET (Synchronous Optical Network), SDH (Synchronous Digital Hierarchy), T-Carrier (TDM carrier), E-Carrier (European TDM carrier), and J-Carrier (Japanese TDM carrier). Each of these technologies defines a hierarchy of possible channel arrangements that provide varying bandwidth capacities.

You use Channelized Connectivity entities to represent channelized connectivity in UIM. Channelized Connectivity entities are not based on specifications in the same way as other entities. Instead, there is a TDM Facility specification that you can open in Design Studio and modify by adding characteristics that apply to all entities of this type. See Design Studio Release Notes for additional information about entity-level characteristics.

The UIM signal architecture, a hierarchical arrangement of specifications that defines signal structures for Channelized Connectivity entities. The signal architecture determines the available multiplexing options when you configure channels for a channelized connectivity. The signal architecture also defines compatible signal relationships that enable channelized connectivity to be transported on the channels of SONET and SDH facilities.

UIM uses rate codes to define the technology and bit-rate capacity that applies to channelized connectivity entities. Each rate code definition includes:

  • A name, such as STS1 or VC3

  • A networking technology, such as SDH or SONET

  • A bit rate and unit of measure, such as 51.840 Mbps or 48.960 Mbps

You can also associate rate codes with device interfaces. See "Enhancements to Logical Device and Device Interfaces" for more information.

The work area for Channelized Connectivity entities is organized into four tabs:

  • You use the General Information tab (see Figure 28) to view and edit basic information about Channelized Connectivity entities. This information includes the connectivity identifier, end point locations, rate code, technology, and so on.

    Figure 28 General Information Tab in the Connectivity Details Work Area

    Description of Figure 28 follows
    Description of "Figure 28 General Information Tab in the Connectivity Details Work Area"

  • You use the Capacity tab in the Connectivity Details work area (see Figure 29) to channelize a connectivity and thereby configure its capacity. The channelization options depend on connectivity's rate code and technology. The Capacity tab displays a canvas in which a hierarchy of nodes and levels represents the connectivity's channelization.

    Figure 29 Capacity Tab in the Connectivity Details Work Area

    Description of Figure 29 follows
    Description of "Figure 29 Capacity Tab in the Connectivity Details Work Area"

  • You use the Connectivity Design tab in the Connectivity Details work area (see Figure 30) to enable and terminate connectivity. The Connectivity Design tab includes a large table that shows the end points of the connectivity, gaps in the connectivity path, pipes and channels assigned to segments, and other information. You can take actions such as assigning transport, accepting connectivity gaps, and adding interconnections. The path control area in the upper-left portion of the Connectivity Design tab enables you to control which paths exist for the connectivity and which one is displayed.

    Figure 30 Connectivity Design Tab in the Connectivity Details Work Area

    Description of Figure 30 follows
    Description of "Figure 30 Connectivity Design Tab in the Connectivity Details Work Area"

  • You use the Channels tab in the Connectivity Details work area (see Figure 31) to view the channel hierarchy of a connectivity. A table shows information about the connectivity and its channels in a expanding hierarchical format.

    Figure 31 Channels Tab in the Connectivity Details Work Area

    Description of Figure 31 follows
    Description of "Figure 31 Channels Tab in the Connectivity Details Work Area"

Channelized Connectivity entities include enhanced support for location. Taking advantage of the new Property Location entity, channelized connectivity end points can be located at properties that you have designated as network locations or at specific logical devices (network devices) associated with those locations. See "Enhancements to Logical Device and Device Interfaces" and "Property Location" for more information.

UIM can automatically terminate the channels of a TDM facility on the sub-devices of the device interface on which the facility itself is terminated. Automatic termination requires that the hierarchy of device interfaces and sub-interfaces match the channel hierarchy of the facility.

Enhancements to Logical Device and Device Interfaces

Logical devices and device interfaces have been enhanced in UIM 7.2.2 to support channelized connectivity features:

  • You can now define the location of a logical device by associating it with a network location (a Property Location entity that has been assigned a network location code). A logical device that is located at a property location is known as a network device and it can terminate channelized connectivity. See "Property Location" and "Support For Channelized Connectivity" for more information.

  • You can associate rate codes with device interfaces. Associating a rate code with a device interface means that a channelized connectivity with a matching or compatible rate code can be terminated on the interface.

  • A new Device Identifier field has been added to uniquely identify a device among all devices associated with a particular property location.

  • You can now create interface-bound cross-connects within a logical device to represent connectivity between device interfaces. These cross-connects are included in connectivity paths.

These capabilities are built into all newly created logical devices. You can add them to existing logical devices as part of an upgrade from an earlier version of UIM or in a separate step. See UIM Installation Guide for more information about upgrading.

Property Location

UIM 7.2.2 introduces stronger location capabilities to support the new channelized connectivity features. A new entity, Property Location., represents a piece of land with defined legal boundaries that can be used to identify the location of logical devices and connectivity termination. Property Location entities do not have specifications, but can be enhanced with entity-level characteristics. See Design Studio Release Notes for additional information about entity-level characteristics.

You can define property locations as network locations. Network locations are property locations that host a service provider's inventoried network infrastructure. You define a property location as a network location by assigning it a network location code. Network location codes are strings of up to 10 alphanumeric characters, with letters in upper case. Network location codes can be CLLI (Common Language Location Identifier) codes, but UIM does not validate against the CLLI standard.

In UIM, network locations host network devices (logical devices associated with that location). Network locations can include a set of network entity codes that refer to devices hosted there.

When you create a property location and enter its address, you can choose to validate the address by using a geocoding application such as Oracle eLocation. Validating addresses ensures accuracy and limits duplication caused by similar addresses.

Optimizing Concurrent Resource Allocation

Developers can now optimize concurrent resource allocation in UIM by implementing row locking during searches. You implement row locking by setting LockPolicy values during searches. The new row-lock pattern achieves the same result as database row-locking, but conventional row-locking is not used.

Row locking is a data model pattern that can be statically applied to a UIM entity through the metadata files. It is enabled and used through custom code. When row locking is implemented for an entity and an entity finder API is called, lock policy details may be provided to the API. If lock policy details are provided, selected entity rows are locked.

In most UIM environments, telephone number entities are heavily used. As a result, UIM now uses row locking by default for assigning and reserving telephone numbers. For example, when two clients simultaneously search by ZIP code for a telephone number to reserve or assign, the search results do not return the same number to both clients. Instead, each telephone number entity that meets the search criteria is locked prior to returning the search results.

See UIM Developer's Guide for more information about concurrent resource allocation and row locking.

Cooperation Framework Reference Cartridges

The cooperation framework enables you to extend UIM to work with other systems. The following reference cartridges support the cooperation framework:

  • ora_uim_ipaddress_cooperation

    In the IP address cooperation, UIM works with INAM. For example, UIM manages services, and INAM manages IP addresses. When a service resource assignment requires an IP address, INAM is the IP address resource repository from which UIM finds a resource to assign.

  • ora_uim_vlanid_cooperation

    In the VLAN ID cooperation, UIM works with MSS. For example, MSS manages service configurations, and UIM manages VLAN IDs. When a service resource assignment requires a VLAN ID, UIM is the VLAN ID resource repository from which MSS finds a resource to assign.

  • ora_uim_connectivity_cooperation

    In the connectivity cooperation, UIM works generically with an external system to manage connectivity resources. For example, UIM sends a Work Order to an external system, such as MSS, to request a lease on connections.

Fixes in this Release

Table 6 lists customer-reported bugs that have been fixed in UIM 7.2.2.

Table 6 Fixed Bugs

Bug/SR Component Description

14659063

3-6145233046

WEBSVC

Issue

Updates to characteristic values made by Web services are not reflected in the UIM interface.

Resolution

Characteristic values are now updated correctly.

14620629

3-6183090591

SERVICE

Issue

Configuration items in Service Configuration remain in Unassigned status even when they are assigned.

Resolution

UIM now updates the status correctly.

14551031

3-6071397381

TN

Issue

Rulesets for telephone number assigned to an inventory group do not fire.

Resolution

Rulesets now fire correctly in this scenario.

14105862

TN

Issue

If partitioning is enabled, the disconnect telephone number recall process does not work.

Resolution

The telephone number recall process now finds telephone numbers regardless of the partition.

13779338

3-5336494981

WEBSVC

Issue

The NOT_EQUALS operator for searches based on service status is ignored in API calls.

Resolution

The code has been modified to implement search criteria correctly.

13411623

SERVICE

Issue

Search based on assignment status takes a long time.

Resolution

The code has been optimized to improve search performance in this situation.


Known Problems

Table 7 lists the known issues in UIM 7.2.2.

Table 7 Known Issues

Bug Number Description Notes

14634611

Configuring and saving high-rate-code SONET and SDH facilities takes a long time

Configuring, reconfiguring, and saving SONET and SDH facilities with high rate codes, such as STM 1024 to VC-x or VT-x, takes a long time. When such changes are saved this also is known to take a significant amount of time.

To avoid this issue, configure these facilities in steps or use Web services.

14635050

Processing signals displayed when no channels exist.

The connectivity channel and search tree views displays processing signals that were configured earlier, even if there are no channels currently under those processing signals.

14665548

Root node sometimes not visible in the Capacity tab

When you configure a facility by using the Capacity tab, the root node can sometimes disappear.

Click the Zoom to Fit button to restore the root node to the viewable area of the Capacity tab.

14754088

Auto-termination of channels for OC48 and higher rate facilities takes a long time.

When assigning interfaces to TDM facilities like OC48 or higher rate codes the auto-termination of TDM channels to the appropriate sub device interfaces is noted to take more than 2 minutes to complete.

14841339

Unable to channelize SDH facility below VC3 without TUG-3

It is not currently possible to channelize an SDH facility to VC3 or a lower rate (VC2,VC12, or VC11) without multiplexing through TUG-3.

15959097

Error during upgrade from UIM 7.2.0.2 to UIM 7.2.2

An error related to the Map Viewer application occurs during the upgrade process. This error prevents the upgrade from completing successfully

You can avoid this problem by undeploying the Map Viewer before beginning the upgrade. When you perform the upgrade, select the option to deploy the Map Viewer.

Note: If you have customized any styles or themes in the Map Viewer, your changes will be lost during the upgrade.


Documentation Updates

A number of enhancements have been made to the UIM documentation set for Release 7.2.2:

  • A new guide, UIM Cartridge and Technology Pack Guide, has been added. This book replaces the earlier UIM Base Cartridges Guide. It includes information about creating, packaging, customizing, and deploying cartridges in addition to reference information about base cartridges.

  • The ”Localizing UIM” chapter in the UIM Developer's Guide was extended to include instructions on localizing the online Help in addition to information about localizing the user interface.

UIM 7.2 Release Notes

This section includes information about UIM 7.2, including new features introduced, known issues, and resolved issues.

Features Introduced in UIM 7.2

This section provides information about features and capabilities introduced in UIM 7.2.

Coordinated OSS Suite Release

UIM 7.2 is part of a coordinated release of the Oracle Communications OSS (Operational Support Systems) application suite. UIM and the other OSS applications are designed to work together seamlessly on a common platform with a unified user experience. The other applications in the suite are Order and Service Management (OSM), ASAP, and Design Studio.

The 7.2 release provides end-to-end service fulfillment scenarios for GSM services. Service Fulfillment Web services support an end-to-end provisioning workflow from OSM (for service order management) via UIM (for inventory management) to ASAP (for activation). See "Service Fulfillment Web Services" for more information.

The 7.2 release also includes a reference implementation, design patterns, and other artifacts that can be used for other domains such as Enterprise, SaaS, Cloud, and so on.

The OSS suite is designed for scalability, making it suitable for deployments that range from small single-server development and test environments to large-scale, multi-node cluster implementations that demand optimized performance and high availability.

User Interface Enhancements

The UIM user interface has been updated to the Oracle Communications Platform, based on Oracle Fusion technology. The new interface provides a common look and feel with other Oracle Communications applications such as Order and Service Management (OSM).

Specific enhancements include:

  • Improved display of error messages

  • Links are grouped by function in work areas

  • Improved information display through the use of interactive tables

  • Improved design of graphic elements, such as icons

  • Ability to search for characteristics in all entities

  • Display of search results on the same work area as search criteria

  • Ability to filter, sort, and scroll through all search results

  • Ability to apply conditions to entities from search results

  • Recent Items capability, enabling you to navigate back to work areas you have used previously.

See UIM Concepts and UIM online Help for more information about the UIM user interface.

Installation Improvements

The UIM installation process has been enhanced for release 7.2. Improvements include:

  • Support for automated cluster installation

  • Support for silent installation

  • Support for uninstallation

See UIM Installation Guide for information about installation procedures.

Business Interaction Enhancements

External systems can now interact with UIM via Web Services in the context of business interactions (BIs). Previously, business interactions had been available only by using the UIM interface.

With these enhancements, Web Services can be used to perform actions such as creating and managing services, service configurations, and resources in business interaction contexts. They can also be used to assign existing resources to service configurations in a business interaction.

This enhancement takes advantage of the Service Fulfillment Web services introduced in the 7.2 release. See "Service Fulfillment Web Services" for more information.

Several new business interaction actions have been added as part of this enhancement:

  • Approve Configuration. This action does not change the business interaction status, but changes service configurations from In Progress to Designed.

  • Cancel Hierarchy. This action changes the status of the parent business interaction and all of its children from Created or In Progress to Canceled. This action affects service configurations and their parent services, but the exact result depends on the combination of statuses of the services and service configurations.

  • Complete Hierarchy. This action changes the status of the parent business interaction and all of its children from In Progress to Completed and changes the statuses of entities to reflect the actions defined in the items in all business interactions in the hierarchy. Completing the business interaction hierarchy also changes the status of service configurations and their parent services. The general result is to change service configurations from Issued to Completed status, which causes the parent services to change to In Service status.

  • Issue Configuration. This action does not affect the status of the business interaction, but changes the status of service configurations from Designed to Issued.

Business interactions that are created as the result of requests by Web services are somewhat different from business interactions created in the UIM user interface:

  • Requests from external systems are sent in the form of XML documents. UIM uses the content of the XML documents to create or update business interactions. The documents are stored as attachments to the relevant business interactions for future reference. You can view these XML documents in UIM.

  • Business interactions managed by Web services can include service configurations as items. This capability is not available in business interactions created in the user interface. After a business interaction has been created by Web services, however, you can use the user interface to work with the service configurations it includes.

  • The parent service of a service configuration in a business interaction does not appear as a business interaction item. The parent service is visible in current inventory. Business interaction status transitions do cause status transitions in parent services, however.

Service Fulfillment Web Services

UIM 7.2 includes Web services for managing services and service-related resources. These Web services are used in the end-to-end GSM service fulfillment solution supported by the GSM/3GPP Technology Pack. (See "GSM 3GPP Technology Pack".) These same Web services can also be used for any type of service fulfillment scenario.

The Web services make use of enhancements to business interactions introduced in UIM 7.2. See "Business Interaction Enhancements".

Five new Web service operations control business interactions in UIM:

  • CaptureInteraction. Sends an order request to UIM to add, change, or disconnect a service. The order information from the request is stored in UIM as a business interaction.

  • ProcessInteraction. Performs the actions necessary to move a planned service into current inventory. These actions are stored in an XML attachment to the business interaction that was created by CaptureInteraction.

    ProcessInteraction retrieves the attachment and processes the items it contains. Each item creates or updates a service, including any default service configuration items defined by the Service specification. An extension point enables you to use a ruleset to customize the process.

  • UpdateInteraction. Transitions UIM entities to specific life-cycle states within the context of a business interaction. UpdateInteraction can trigger APPROVE, ISSUE, CANCEL, and COMPLETE actions for a business interaction.

  • GetConfiguration. Retrieves a service configuration based on the search option specified in the request. You can search by configuration ID, entity ID, version number, configuration status, and effective date.

  • GetInteraction. Retrieves a business interaction based on an external ID or business interaction ID.

    When GetInteraction is called before ProcessInteraction, the response returns only the business interaction data. Service data is not returned because ProcessInteraction has not yet processed the business interaction into current inventory. When GetInteraction is called after ProcessInteraction, the response returns both business interaction data and service data.

  • UpdateConfiguration. Transitions the state of a service or service configuration. For services, the valid actions are COMPLETE, CANCEL, DISCONNECT, SUSPEND, and RESUME. For service configuration, the valid actions are APPROVE, ISSUE, CANCEL, and COMPLETE.

GSM 3GPP Technology Pack

The GSM/3GPP Technology Pack provides the specifications, characteristics, and rules required to model and deploy a GSM/3GPP service into UIM.

The GSM/3GPP Technology Pack also supports the modeling and managing of key logical resources including the IMSI (international mobile subscriber identification), SIM cards, and MSISDN (mobile subscriber integrated services digital network) number, all of which are required to configure GSM/3GPP services. The technology pack supports the modeling of key devices used to register service components in the network, including the HLR (home location register) and voicemail server.

You can create, change, and discontinue GSM/3GPP services and the service configurations using Web service operations. The technology pack also supports operation in a standalone mode, where you can add, change, or disconnect GSM/3GPP services and invoke configuration automation logic manually using the UIM user interface.

See GSM 3GPP Technology Pack Implementation Guide for detailed information.

Cable TV Technology Pack

The Cable TV Technology Pack enables cable television service providers to model their services, provisionable video streams, customer premise equipment, subscriber information, and service locations.

The Cable TV Technology Pack supports the following network types:

  • Multi-Service Operator (MSO)

  • Region

  • Cluster

  • Office

A new Media Stream entity has been added to support this technology pack. It can also be used to model resources for other domains, such as IPTV.

See Cable TV Technology Pack Implementation Guide for detailed information.

Configuration Reference

Configuration items can now reference entities in addition to being able to consume them. A referenced entity is one that is important to another entity's configuration, but is not consumed by it. In other words, the referenced entity's capacity or availability is not affected by its relationship to the referencing entity configuration.

For example, in the GSM domain, a mobile service must be provisioned on a Home Location Register (HLR), but the HLR is not consumed by the service. In UIM, the mobile service configuration references an HLR rather than assigning it. Similarly, a cable controller enables a cable television service but is not consumed by it. In UIM, a cable service configuration would reference a cable controller.

All entities that currently support configuration, with the exception of pipes, can use the new entity reference feature.

The process of setting up reference relationships in Design Studio and implementing them in UIM is very similar to the current process for allocation or assignment. See Design Studio online Help and UIM online Help for more information.

Security Enhancements

UIM security has been enhanced for the 7.2 release. Both authentication (identifying users by login and password) and authorization (controlling access to specific parts of UIM) are now handled mainly by the application server rather than by UIM itself.

By default, you now use two external systems to manage most aspects of UIM security:

  • WebLogic Server Administration Console enables you to manage users and groups. You create and delete users and assign passwords in this application.

  • Oracle Enterprise Manager enables you to create security roles and security policies that define what work areas users can access and what actions they can take.

You can optionally use other tools that provide additional security functionality. For example, you can use Oracle Internet Directory and Oracle Identity Management to manage users and user identities.

See UIM System Administrator's Guide for more information about security.

Entity security is still performed by the application itself. API security must be implemented through the extensibility framework. See UIM Developer's Guide for more information about implementing these kinds of security.

Fixed Bugs

Table 8 lists customer-reported bugs that have been fixed in UIM 7.2.

Table 8 Fixed Bugs

Bug/SR Component Description

12845120

3-4047562061

PIPE

Issue

Multiple links displayed between segments of paths returned by path analysis.

Resolution

Error handling has been improved to eliminate this issue.

12429084

3-3234110301

TOPOLOGY

Issue

Korean characters displayed incorrectly in Topology View.

Resolution

UIM now uses iLOG 8.7, which resolves the issue.

12784178

3-404971166

EQUIP

Issue

No ability to move directly from the Physical Port Summary work area to the parent Equipment work area directly.

Resolution

A link to the parent Equipment, Physical Device, or Logical Device Summary work area was added in the Information panel of Physical Port, Connector, and Device Interface Summary work areas.

13058636

3-4099038881

TOPOLOGY

Issue

When searching for entities in the Topology View, results are not highlighted.

Resolution

Topology search results are now highlighted correctly.

11936858

PIPE

Issue

Visualizations of enabled pipes displayed as loops when the pipe termination points are not terminated.

Resolution

Pipe visualizations display correctly in this scenario.

12684644

3-3880100411

INVGRP

Issue

UIM allows entities from an unrelated specification to be added to an inventory group when added from the entity Summary work area.

Resolution

UIM correctly enforces specification relationships in this scenario.

13085395

3-4618324529

PIPE

Issue

UIM displays an error when you delete a pipe that has multiple configuration versions.

Resolution

Pipes are now deleted correctly.

13034844

3-4618324441

BUSINT

Issue

Status of an Equipment entity not updated correctly when removed from a business interaction.

Resolution

Status is now updated correctly.

12779298

3-4041199011

CONFIG

Issue

UIM incorrectly allows the same path to be assigned twice in enabling two different configuration versions.

Resolution

UIM now checks for and prevents duplicate assignments.

12798824

3-4083224871

PIPE

Issue

UIM displays an error when performing a path analysis with Enforce Direction and Include Partial Paths selected.

Resolution

The path analysis now concludes successfully.

13055205

3-4618324491

BUSINT

Issue

When an entity is deleted from a business interaction and the business interaction is completed, the entity status is not updated.

Resolution

UIM now updates entity status correctly in this scenario.

11936859

WEBSVC

Issue

UIM unable to auto-generate both service ID and service configuration ID.

Resolution

UIM can now auto-generate both types of IDs, even when the service creation action is initiated by Web services.

12793967

3-4045444161

PIPE

Issue

When a signal structure is removed from a Pipe entity, the capacity provided by the structure is not removed. As a result, when new capacity is added, multiple rows are displayed in the Capacity Provided panel.

Resolution

Capacity provided is now removed successful when a signal structure is removed.

12818763

3-4040373271

NETWORK

Issue

Rectangular borders are displayed incorrectly around network nodes when they are associated with resources.

Resolution

Borders are no longer used for nodes associated with Logical Device, Physical Device, Custom Network Address, and Equipment entities. You can right-click on these nodes and select from a menu to go to the corresponding Summary work area.

12965344

3-4082046551

TOPOLOGY

Issue

Ohm symbol displayed for pipes in Topology View.

Resolution

iLog configuration has been changed so that this symbol does not display.

13106123

3-4627778801

DEVICE

Issue

Begins with operator does not work in search for Logical Device entities from Termination Point Summary work area.

Resolution

Begins with operator now works for all entity searches.

12790138

3-4089898551

DEVICE

Issue

Inability to view physical ports assigned to device interfaces in a Logical Device hierarchy.

Resolution

Physical ports are displayed as hyperlinks in a separate column in Logical Device and Device Interface hierarchies.

12344389

3-3194555561

EXTEND

Issue

Slow application startup when AspectJ is enabled.

Resolution

This issue has been resolved by configuration changes.


Known Issues

Table 9 lists the known issues in UIM 7.2. See "Limitations on Actions in Business Interaction Contexts" for information about restrictions on actions you can take in a business interaction context.

Table 9 Known Issues

Bug Number Description Notes

13812505

High transaction failure rate in cluster environments.

UIM in some cluster environments experiences a high rate of transaction failure. The high failure rate is related to JMS cache synchronization.

You can avoid this issue by setting up the cluster in active- passive configuration. The issue will be resolved in a patch release.

13813260

Blue screen displayed in Map View when opened from Recent Items.

In some cases, when you return to the Map View work area by using Recent Items, a blue screen is displayed rather than the work area.

You can open the Map View work area normally from the Network Summary work area.

13474861

Map View does not open in Internet Explorer 8 with SSL enabled.

The Map View cannot be displayed in Internet Explorer 8 when UIM is configured for Secure Socket Layer (SSL) access.

Use Internet Explorer 7 in this scenario.

13411623

Search based on assignment status takes a long time.

Searching for entities by assignment status is slow, particularly when searching for entities in Unassigned status.

12694608

Out of space error caused by deployment architecture.

You may experience Out of Memory errors if you deploy multiple cartridges with rulesets or super-cartridges that require server redeployment. The error may occur after 3 - 8 redeployments. After the error occurs, you must restart the WebLogic server.

You can avoid the error by manually restarting the server periodically while you are installing cartridges.

10242392

System allowing the creation of duplicate IDs.

When you create ranges of equipment or logical device entities, IDs that duplicate existing entities can be created.

When you create ranges of entities, take care to specify ranges that do not duplicate existing entities.

Note: This issue does not apply to TN range creation.


Limitations on Actions in Business Interaction Contexts

There are some limitations that affect actions you can take while in a business interaction context.

  • If you are working in a business interaction context and you navigate to an entity that is not business-interaction-enabled, the context is temporarily changed to Current. When you navigate back to a business-interaction-enabled entity, the original context is restored. Actions that you take on entities while outside the business interaction are effective at the time you make them.

  • You cannot create entity configurations while working in a business interaction context. This restriction applies to the three business-interaction-enabled entity types that can have configurations: logical device, pipe, and network.

  • To prevent unintended deletions of entities, actions that involve mappings are limited in a business interaction context. You see an error message if you attempt any of the following actions while working in a business interaction context:

    • Adding or removing a logical device account in a logical device

    • Adding or removing a logical device mapping to or from a physical device

    • Adding or removing a device interface mapping to or from a physical port

    • Adding or removing a device interface mapping to or from a physical connector

    • Adding or removing a physical connector mapping to or from a device interface

    • Adding or removing a physical port mapping to or from a device interface

  • Actions that are normally supported in a business interaction context are restricted if an affected entity or an entity it provides (such as an physical port provided by an Equipment entity) is involved in one of the following mappings:

    • Logical device to a physical device

    • Device interface to physical port or physical connector

    These are the specific actions that result in errors in this case:

    • Removing a logical device from a logical device hierarchy

    • Deleting a logical device

    • Deleting a device interface

    • Deleting equipment

    • Deleting a physical device

    • Deleting a physical port

    • Deleting physical connector

    • Removing a physical device from a physical device hierarchy

    • Remove equipment from a physical device hierarchy

    • Removing equipment from an equipment/equipment holder relationship

    • Moving equipment

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.


Oracle Communications Unified Inventory Management Release Notes, Release 7.2.2

E36034-03

Copyright © 2012, 2013 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 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.

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.