6 Creating components

Add components to entities in Oracle Communications Design Studio PSR Designer. A component represents a specific element needed to complete the entity. The component shows relationships to possible entities that can act as this element.

Topics in this document

About components

When defining a CFS, RFS, or resource, you can add one or more components that reference another entity. This sets a relationship between the entities such that they are associated with each other in your system's processes.

For example, the Voice Mail CFS has a Mailbox component that links to the VoiceMailBox RFS. In turn, that RFS has an Activation Target component that connects to the VoiceMailServer resource.

In your diagram, each component links to another entity. A CFS can link to locations and RFSs. An RFS and a resource can link to locations, RFSs, and resources.

A CFS requires at least one component.

Set one of these link types for each component:
  • Exclusive: At run time, the component can't be shared with other service instances. For example, a VoIP RFS might have an exclusive component for a telephone number. In the Residential Phone example, there's an exclusive relationship between the VoIP Line RFS and the TelephoneNumber resource. See Example of a PSR Designer diagram.
  • Shared: At run time, the component can be shared with other service instances. For example, a mobile RFS might have a shared component for a home location register, because an HLR can maintain several user accounts simultaneously and isn't exclusive to any one service.
  • Reference: At run time, a target entity references a source entity. For example, a fixed voice CFS might have a reference component for a service location, which is a physical address.
  • ConfigHierarchy: In Oracle Communications Unified Inventory Management (UIM), an intermediate hierarchical structure is referenced at run time. You can use this for a relationship between an RFS and a resource. The ConfigHierarchy link type indicates that a UIM realization of a resource component should result in a hierarchy of configuration items and should not generate a UIM entity.

Components are specific to the entity in which you create them and don't need to have unique names.

About cardinality

Cardinality determines how many times a data element can appear in an entity and is used when defining characteristics.

For example, if a service has a characteristic for telephone number, the cardinality minimum might be 1 and the maximum 2. When that service is provisioned to a customer, they can have one or two phone numbers as part of that service.

Creating components

Create a component as part of defining a CFS, RFS, or resource:
  1. To start creating a component, do one of the following:
    • On the page for a CFS, RFS, or resource, click Components in the Sections list. Then click the Create Component icon.
    • In a diagram, right-click a CFS, RFS, or resource, and select Create Component.
  2. Enter a name and optional description.
  3. Select the type of entity the component will link to.
  4. Click Create.
  5. Continue defining the component in either of these ways:
    • Click the newly created component on the Components page of your entity.
    • Click the component name or the to-do list icon in the diagram.
    The component's page appears.
  6. Select a link type. See About components for information about each one.
  7. Set the minimum and maximum cardinality. See About cardinality.
  8. Under Options, add one or more entities of the type you set for this component. For example, if you selected Resource Facing Service Component for the type, add one or more RFSs. Then do one of the following:
    • Click the Add icon and select an existing entity.
    • Click the Create icon and create a new entity. The new entity won't appear in your diagram until you explicitly add it.
    You can also connect the component to an entity in the diagram. See Linking entities.
  9. Click the Previous page arrow at the top left.