Preface

This guide explains how to work with Oracle Communications Service Catalog and Design - Design Studio design patterns, guided assistance, and externally created schemas. It explains how to automate builds and provides information about implementing continuous integration to design, create, and deliver operations support system (OSS) solutions across Oracle Communications products.

This guide assumes that you have a conceptual understanding of Design Studio and have read the Concepts guide.

This guide includes examples of typical development code used in given situations. The guidelines and examples may not be applicable in every situation.

Audience

This guide is intended for developers who work with Service Catalog and Design to build the code to support the metadata-driven components of Service Catalog and Design projects. You should have a good working knowledge of development languages such as Java, XPath, XQuery, or SQLcreate service fulfillment solutions.

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.