To serve these objectives, all the APIs of this view share a common SOA-ready middleware foundation and help decouple the business logic from the integration infrastructure and functional interfaces.

Thanks to this common foundation all APIs can be easily deployed on commercially available products or open source distributions of enterprise platforms that comply to Java and Web Services standards. All APIs offer three programatic or message-driven integration profiles: tight coupling with Java/RMI/IIOP, loose coupling with XML/JMS, and cross boundaries with Web Services.

All integration profiles feature: interface definitions, reference implementations, which help in solution deployments, and test suites, used to verify compliance with the standard definitions. Source code is included for reference implementations and test suites.

The Fault Management team also issued a 3GPP Alarm Official Extension to the Fault Management API.

The Trouble Ticket team also issued a X.790 Official Extension to the Trouble Ticket API. Also available, a document describing the differences between Trouble Ticket v1.0 and Trouble Ticket v1.2 plus X.790 extension. Click here to download it.

Reminder: the Order Management API incorporates and replaces the OSS/J Service Activation API. The Fault Management API supersedes the fault management part of the Quality of Service API.

	Downloads1				Available Profiles
API Name	Specification2	Reference Implementation	Conformance Test Suite3	Questionnaire4	Java	XML/ JMS	WS	Support
Trouble Ticket v1.2			Source Binary
Inventory v1.2			Source Binary			only specs	only specs
Fault Management v1.0			Source Binary
Order Management v1.0			Source Binary
Discovery v1.0			Source Binary			specs and test suite	specs and test suite
Common v1.5			Source Binary

²The specifications of the OSS/J APIs downloadable from this page are copies of the corresponding OSS/J API specifications available from the JCP website at http://www.jcp.org/en/jsr/tech?listBy=3&listByType=tech. Two different licenses are associated with the specifications of the OSS/J APIs: the license from the JCP "Specification Lead" company associated with the OSS/J specifications downloadable from the JCP website ("JCP license"), and the TM Forum license associated with the OSS/J specifications downloadable from this page ("TM Forum license"). If you are seeking to create and distribute an implementation of an OSS/J specification only under the auspices of the TM Forum, which also allows partial or full implementations of OSS/J APIs without having the implementations to have passed the applicable TCK (provided that the licensee does not assert that a partial implementation is "conformant" under the TM Forum's policies), then the terms and conditions of the TM Forum License shall control. If, however, you are seeking to create and distribute an implementation of an OSS/J specification under the auspices of the Java Community Process, you need to download the specification from the JCP website and accept the terms and conditions of the accompanying Specification License, which only grants certain rights for distributed implementations that do pass the applicable TCK. The companies that serve as Specification Leads under the JCP for the OSS/J APIs available for download from this page have consented to this dual licensing approach.

The download file for each Specification includes the documentation, the Java interfaces, the XML Schema and the Web Services description in WSDL format.

Technical Notes:

The APIs listed in the table above: 

• are based on the OSS/J Common API v1.5
• are aligned with the OSS/J Design Guidelines 2.0
• share a common data model (OSS/J CBE) derived from the TM Forum SID v6
• have been generated with the same set of tools
• are available to the public as final releases or as maintenance releases