tation are accessible for free download. OSS solution developers can use the API specification and reference implementa- tion code to develop OSS/J API in products that are planned to be certified. To certify the developed API, the solution developer has to download the technology compatibility kit within the Java community process, which is a test suit that is available for free. The test suite needs to be run against the API developed by the service provider. The test execution will generate a test report that will specify if the test run was successful. On obtaining a successful test run in the report, the solution developer needs to send the test execution report to the OSS/J certification committee. The certification committee will validate the report and the process used to create it. Once the certification committee acknowledges the certification of the product, the certification can then be published. The published certificates will also have a reference to the test execution report. The publication of the test report eases the procurement of certified products for faster integration. 25.5 MTOSI and OSS/J MTOSI focuses on reducing the cost of integration in a commercial environment by providing a full XML interface specification detailing the model, operations and communications enabling out of the box interoperability. The focus of OSS/J is also reduction of the integration cost in a partner/open-source environment. OSS/J pro- vides a Java interface specification that offers basic operations but does not contain the model or interaction as specific as in MTOSI. Instead, OSS/J allows sharing of reference implementations to enable interoperability. Thus it becomes evident that MTOSI and OSS/J are complementary technologies. Using a mapping/media- tion approach MTOSI and OSS/J can interoperate. For a closed partner engage- ment, OSS/J is best suited where as for an out-of-the-box commercial environment MTOSI is the best. Fundamentals of EMS, NMS and OSS/BSS OSS/J frame work MTOSI adapter MTOSI Figure 25.2 M