Documentation resources for the Tivoli Netcool/OMNIbus V7.4 HTTP interface and OSLC interface

The documentation for the HTTP interface and the OSLC interface is provided below.

Document title	Document
HTTP/OSLC Interface	objectserver_httposlc_interface.pdf
ObjectServer HTTP Interface Developer Overview	objectserver_http_overview.pdf
ObjectServer OSLC Interface Developer Overview	objectserver_oslc_overview.pdf

As a language-independent means of accessing ObjectServer data, two HTTP-based application programming interfaces (APIs) are provided in Tivoli Netcool/OMNIbus V7.4:

• A lightweight API that is called the HTTP interface
• A resource-based interface that is called the OSLC interface.

Both APIs are hosted in the ObjectServer and use the same technology as the HTTP interface for probes. Both interfaces can be secured by an HTTPS connection. Access to the URI is authenticated by a known ObjectServer user through basic HTTP authentication. The HTTP interface provides access to table data in the ObjectServer through a structured URI format that uses HTTP. POST, PATCH, GET, and DELETE requests are supported against table URIs or row URIs. For content, application/json messages are supported. Table row data is returned and accepted through a single common JSON message format that is called a row set. A URI that represents an SQL command factory can be used to execute arbitrary SQL commands. The OSLC interface is an event server provider that presents a resource-linked data view of events and also the associated journal and detail resources. Messages are exchanged in RDF/XML syntax. The ObjectServer can be registered in the Jazz™ for Service Management (JazzSM) service provider registry. Tivoli Netcool/OMNIbus V7.4 does not ship JazzSM. Both interfaces can be enabled and configured by setting properties in the ObjectServer.