1. REST API for Unified Inventory ManagementREST API for Unified Inventory Management
  2. Reconfiguring Network Resources

Reconfiguring Network Resources

Oracle Communications Unified Inventory Management (UIM) includes a REST API that optimizes the network utilization by maintaining connectivity and reconfiguring the networks.

The REST API supports the GET, POST, PATCH, and DELETE methods for the following features:

  • Rehome
  • Groom
  • Replace card

Note the following when working with these resources:

  • The ID of each project or activity has a prefix of BusinessIdentifier. Below are the BusinessIdentifiers of each project or activity:

    • Activity(33),
    • RehomeProject(34),
    • GroomProject(35),
    • ReplaceCardProject(36),

  • The REST API methods are implemented to support business operations.

  • Rehome REST API is used for changing the termination of a connectivity or pipe even if it has the trails (pipe or connectivity) riding on them. The REHOME POST operation encapsulates the following operations:

    • Creation of project.
    • Creation of rehome activity.
    • Creation of activity item with the rehomed connectivity or pipe details.
    • Optional submission of the activity and the project based on the query parameter submit.

  • Groom REST API is used to change the design of a connectivity or pipe even if the trails are riding on it. This API moves a rider from source bearer to target bearer. The GROOM POST operation encapsulates the following operations:

    • Creation of project.
    • Creation of groom activity.
    • Creation of activity item with the groom connectivity or pipe details.
    • Optional submission of the activity and the project based on the query parameter submit.

  • ReplaceCard REST API is used to replace the source card from its parent equipment slot and reassign the target card. Pipe, connectivity, or service consumers terminated on physical ports of source card are also rehomed to the target card ports. The REPLACECARD POST operation encapsulates the following operations:

    • Creation of project.
    • Creation of replacecard activity.
    • Creation of activity item with the source or target card details along with the connectivity, pipe, or service consumer details.
    • Optional submission of the activity and the project based on the query parameter submit.

  • The SUBMIT REST task is designed to submit the activity and the project together. The submit task is designed as an asynchronous operation and all the corresponding impacted items are stored in the activity.

  • The GET REST API is designed to view the status and the corresponding impacted items of the performed action.