Preface
This document provides information about the following areas of Oracle Communications Order and Service Management (OSM) that can be customized:
-
Web services
-
Extensible Markup Language (XML) Application Programming Interface (API)
-
Automation
-
Security Callback
-
Behaviors
-
Custom menu items and action items
-
Localization of OSM
This document also provides a process example of provisioning a Plain Old Telephone Service (POTS) customer using unbundled local loop to illustrate various types of customization.
Audience
This document is intended for programmers who have a working knowledge of:
-
System interfaces
-
XML
-
Java development
-
Java Messaging Service (JMS)
-
Web services
This document assumes that you have read OSM Concepts, and have a conceptual understanding of:
-
Oracle Communications Service Catalog and Design - Design Studio configuration
-
Orders
-
Order states
-
Tasks
-
Task states
-
Notifications
-
Behaviors
-
Web services
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 that have purchased support 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.
Diversity and Inclusion
Oracle is fully committed to diversity and inclusion. Oracle respects and values having a diverse workforce that increases thought leadership and innovation. As part of our initiative to build a more inclusive culture that positively impacts our employees, customers, and partners, we are working to remove insensitive terms from our products and documentation. We are also mindful of the necessity to maintain compatibility with our customers' existing technologies and the need to ensure continuity of service as Oracle's offerings and industry standards evolve. Because of these technical constraints, our effort to remove insensitive terms is ongoing and will take time and external cooperation.