This document provides information that you can use when working with the Oracle Communications Unified Inventory Management (UIM) application program interfaces (APIs). This document also provides information that you can use when working with Oracle Communications Network System Orchestration Java Manager APIs which are also UIM APIs. The UIM APIs can be extended through custom code. The APIs, or extended APIs, can be called from various places, such as from custom rulesets, custom web services, or customized portions of the user interface (UI).
This document provides information on common things you need to do when working with any of the UIM APIs, such as working with transactions, handling errors, and logging messages. This information is described in Chapter 2, "Working with Transactions, Exceptions, and Logging".
The bulk of this document is an overview of numerous UIM APIs, which were specifically selected to describe API usage patterns and best practices for implementing common business scenarios. Code samples are provided to show correct usage of the APIs and expectations of implementing the APIs. This information is described in Chapter 3, "Implementing a Generic Service Fulfillment Scenario" and Chapter 4, "Implementing a Channelized Connectivity Enablement Scenario".
Lastly, this document provides a listing of the following:
UIM entity manager classes
Network Service Orchestration Java managers
Code examples for common utility methods
This information is described in Appendix A, "UIM Entity Managers", Appendix B, "Network Service Orchestration Java Managers" and Appendix C, "Common Utility Code Examples".
This document does not cover detailed Javadoc information, nor does it cover model and domain information provided in other UIM documentation. This document assumes that you are familiar with UIM functionality, and are planning to extend UIM functionality by implementing a custom solution based on information provided in UIM Developer's Guide or Network Service Orchestration Implementation Guide.