1. Web Services Developer's Guide
  2. Preface

Preface

This guide describes the Oracle Communications MetaSolv Solution Access Service Request (ASR) Web Services. These web services are provided with ASR 55 or later and are compatible with MetaSolv Solution 6.3.x.

Audience

This guide is intended for developers who have a working knowledge of web services in general, and who understand XML and Java development, including standard Java practices and J2EE principles. This document is for developers who are integrating MetaSolv Solution ASR with Oracle products, or with other external systems. This guide is intended for integration for users who are responsible for submitting ASRs (based on industry guidelines) to a service provider to initiate or change access services.

Before designing any software that interfaces with the ASR Web Services, you should familiarize yourself with the contents of the Access Service Request Guidelines, which are available at:

http://www.atis.org

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.

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.