Netcool/OMNIbus

Version 8 Release 1

Object Server OSLC Interface

Reference Guide

IBM

SC27-6269-00
Netcool/OMNIbus
Version 8 Release 1

Object Server OSLC Interface

Reference Guide

IBM

SC27-6269-00
 Note
Before using this information and the product it supports, read the information in “Notices” on page 115.

This edition applies to version 8, release 1 of IBM Tivoli Netcool/OMNIbus (product number 5724-S44) and to all
subsequent releases and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 1994, 2017.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Figures
1. Relationships between event management
OSLC resources . . . . . . . . . . . 1

© Copyright IBM Corp. 1994, 2017 iii

iv IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
About this publication
Tivoli Netcool/OMNIbus is a service level management (SLM) system that delivers
real-time, centralized monitoring of complex networks and IT domains.

The IBM Tivoli Netcool/OMNIbus ObjectServer OSLC Interface Reference Guide

describes the services, resources, and common behaviors of the Open Services for
Lifecycle Collaboration (OSLC) Application Programming Interface (API) that is
called the ObjectServer OSLC Interface. It also describes how to enable the API and
provides examples of service provider definitions, RDF/XML payloads, and HTTP
requests and responses.

Intended audience
This publication is intended for administrators who are responsible for configuring
Tivoli Netcool/OMNIbus.

Publications
This section lists publications in the Tivoli Netcool/OMNIbus library and related
documents. The section also describes how to access Tivoli publications online and
how to order Tivoli publications.

Your Tivoli Netcool/OMNIbus library

The following documents are available in the Tivoli Netcool/OMNIbus library:

v IBM Tivoli Netcool/OMNIbus Installation and Deployment Guide,
Includes installation and upgrade procedures for Tivoli Netcool/OMNIbus, and
describes how to configure security and component communications. The
publication also includes examples of Tivoli Netcool/OMNIbus architectures and
describes how to implement them.
v IBM Tivoli Netcool/OMNIbus Administration Guide,
Describes how to perform administrative tasks using the Tivoli
Netcool/OMNIbus Administrator GUI, command-line tools, and process control.
The publication also contains descriptions and examples of ObjectServer SQL
syntax and automations.
v IBM Tivoli Netcool/OMNIbus Web GUI Administration and User's Guide,
Describes how to perform administrative and event visualization tasks using the
Tivoli Netcool/OMNIbus Web GUI.
v IBM Tivoli Netcool/OMNIbus User's Guide,
Provides an overview of the desktop tools and describes the operator tasks
related to event management using these tools.
v IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide,
Contains introductory and reference information about probes and gateways,
including probe rules file syntax and gateway commands.
v IBM Tivoli Monitoring for Tivoli Netcool/OMNIbus Agent User's Guide,
Describes how to install the health monitoring agent for Tivoli
Netcool/OMNIbus and contains reference information about the agent.
v IBM Tivoli Netcool/OMNIbus Event Integration Facility Reference,

© Copyright IBM Corp. 1994, 2017 v

 Describes how to develop event adapters that are tailored to your network
environment and the specific needs of your enterprise. This publication also
describes how to filter events at the source.
v IBM Tivoli Netcool/OMNIbus Error Messages Guide,
Describes system messages in Tivoli Netcool/OMNIbus and how to respond to
those messages.
v IBM Tivoli Netcool/OMNIbus Web GUI Administration API (WAAPI) User's Guide,
Shows how to administer the Tivoli Netcool/OMNIbus Web GUI using the XML
application programming interface named WAAPI
v IBM Tivoli Netcool/OMNIbus ObjectServer HTTP Interface Reference Guide, Describes
the URIs and common behaviors of the Application Programming Interface
(API) that is called the ObjectServer HTTP Interface. Describes how to enable the
API and provides examples of JSON payloads, and HTTP requests and
responses.
v IBM Tivoli Netcool/OMNIbus ObjectServer OSLC Interface Reference Guide, Describes
the services, resources, and common behaviors of the Open Services for Lifecycle
Collaboration (OSLC) Application Programming Interface (API) that is called the
ObjectServer OSLC Interface. Describes how to enable the API and provides
examples of service provider definitions, RDF/XML payloads, and HTTP
requests and responses.
If you use other IBM products to extend the functionality of Tivoli
Netcool/OMNIbus, such as DB2, IBM Tivoli Monitoring, or Tivoli Common
Reporting, see the information center for that product to obtain relevant
publications.

Accessing terminology online

The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at the
following Web address:

http://www.ibm.com/software/globalization/terminology

Accessing publications online

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli Downloads site at:

ftp://public.dhe.ibm.com/software/tivoli/Netcool/NetcoolOmnibus/library/

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File > Print window that allows Adobe Reader to print letter-sized pages on
your local paper.

vi IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully.

With this product, you can use assistive technologies to hear and navigate the
interface. You can also use the keyboard instead of the mouse to operate some
features of the graphical user interface.

Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:

http://www.ibm.com/software/tivoli/education

Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM
provides the following ways for you to obtain the support you need:
Online
Go to the IBM Software Support site at http://www.ibm.com/software/
support/probsub.html and follow the instructions.
IBM Support Assistant
The IBM Support Assistant (ISA) is a free local software serviceability
workbench that helps you resolve questions and problems with IBM
software products. The ISA provides quick access to support-related
information and serviceability tools for problem determination. To install
the ISA software, go to http://www.ibm.com/software/support/isa.
Documentation
If you have a suggestion for improving the content or organization of this
guide, send it to the Tivoli Netcool/OMNIbus Information Development
team at:
mailto://[email protected]

Conventions used in this publication

This publication uses several conventions for special terms and actions and
operating system-dependent commands and paths.

Operating system-dependent variables and paths

This publication uses the UNIX convention for specifying environment variables
and for directory notation.

When using the Windows command line, replace $variable with %variable% for
environment variables, and replace each forward slash (/) with a backslash (\) in
directory paths. For example, on UNIX systems, the $NCHOME environment
variable specifies the path of the Netcool® home directory. On Windows systems,
the %NCHOME% environment variable specifies the path of the Netcool home
directory. The names of environment variables are not always the same in the
Windows and UNIX environments. For example, %TEMP% in Windows
environments is equivalent to $TMPDIR in UNIX environments.

About this publication vii

 If you are using the bash shell on a Windows system, you can use the UNIX
conventions.

Netcool home location

The Netcool home location is the base directory where Tivoli Netcool/OMNIbus is
installed. The Netcool home location is defined by the NCHOME environment
variable. The value of NCHOME is as follows:
v UNIX Linux $NCHOME defaults to /opt/IBM/tivoli/netcool
v Windows %NCHOME% defaults to C:\IBM\Tivoli\Netcool

Where a directory or command path starts with the variable NCHOME, the
information applies to all supported operating systems.

Other products that use the NCHOME environment variable, for example IBM
Tivoli Network Manager IP Edition, can be installed into the Netcool home
location. Each product installs its specific components and files into a dedicated
product subdirectory in the Netcool home location. Files that are common to all
products are installed in shared subdirectories in the Netcool home location.

Operating system-specific directory names

Where Tivoli Netcool/OMNIbus files are identified as located within an arch

directory under NCHOME, arch is a variable that represents your operating system
directory, as shown in the following table.
Table 1. Directory names for the arch variable
Directory name represented by arch Operating system
aix5 AIX® systems
hpux11hpia HP-UX Itanium-based systems
linux2x86 Red Hat Linux and SUSE systems
linux2s390 Linux for System z®
solaris2 Solaris systems
win32 Windows systems

OMNIHOME location

Probes and gateways, and older versions ofTivoli Netcool/OMNIbus use the
OMNIHOME environment variable in many configuration files. Set the value of
OMNIHOME as follows:
v UNIX Linux Set $OMNIHOME to $NCHOME/omnibus
v Windows Set %OMNIHOME% to %NCHOME%\omnibus

Web GUI home directory

WEBGUI_HOME
Refers to the directory where the Web GUI is installed. This directory is
known as the Web GUI home directory. The defaults are as follows:
UNIX Linux /opt/IBM/tivoli/netcool/omnibus_webgui
Windows C:\IBM\tivoli\netcool\omnibus_webgui

viii IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
 The Web GUI home directory is distinct from the Jazz for Service
Management home directories

Jazz for Service Management home directories

WAS_HOME
Refers to the location where WebSphere Application Server is installed.
This location can be specified during installation. The defaults are as
follows:
UNIX Linux /opt/IBM/WebSphere/AppServer
Windows C:\Program Files\IBM\WebSphere\AppServer
JazzSM_HOME
Refers to the location where Jazz for Service Management is installed. This
location can be specified during installation. The defaults are as follows:
UNIX Linux /opt/IBM/JazzSM
Windows C:\Program Files\IBM\JazzSM
JazzSM_WAS_Profile
Refers to the location of the application server profile that is used for Jazz
for Service Management. This location is in the /profile/ subdirectory of
the Jazz for Service Management home directory:
UNIX Linux /opt/IBM/JazzSM/profile
Windows C:\Program Files\IBM\JazzSM\profile
DASH_HOME
Refers to the location where Dashboard Application Services Hub is
installed. This location can be specified during installation. The defaults are
as follows:
UNIX Linux /opt/IBM/JazzSM/ui
Windows C:\Program Files\IBM\JazzSM\ui

For other Jazz for Service Management installation directories, see the Jazz for
Service Management information center at http://www-01.ibm.com/support/
knowledgecenter/SSEKCU/welcome.

Cueing graphic conventions

Tivoli Netcool/OMNIbus documentation contains cueing graphics to indicate that
parts of a topic or instruction apply only under certain conditions. The following
table describes what each graphic means.
Table 2. Tivoli Netcool/OMNIbus cueing graphics
Graphic Description

PureData
Web GUI The text or instruction applies only to the Web GUI component.

UNIX The text or instruction applies only to UNIX operating systems, including AIX
and Solaris. The following cueing graphics are used for AIX and Solaris where
required:

AIX Solaris

Linux The text or instruction applies only to Linux operating systems.

About this publication ix

 Table 2. Tivoli Netcool/OMNIbus cueing graphics (continued)
Graphic Description

Windows The text or instruction applies only to Windows operating systems.

32-bit The text or instruction applies only to 32-bit operating systems.

64-bit The text or instruction applies only to 64-bit operating systems.

FIPS 140-2 The text or instruction applies only to using or configuring FIPS 140-2
encryption.

Default The text or instruction describes default behavior or applies only to default
configurations.

Fix Pack 1 The text or instruction applies only to the fix pack number indicated by the
graphic. Features or enhancements described in the text are only available
after you install the indicated fix pack.

Note: Fix packs for the server component and the Web GUI component are
released separately. Web GUI fix packs are indicated as follows:

PureData
Web GUI Fix Pack 1

Administrator The text or instruction applies only to Web GUI administrators. That is, users
that have the ncw_user and ncw_admin roles assigned.

C The text or instruction applies only to the C programing language.

Java The text or instruction applies only to the Java™ programing language

Typeface conventions

This publication uses the following typeface conventions:

Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip: and Operating system considerations:)
v Keywords and parameters in text
Italic
v Citations (examples: titles of publications, diskettes, and CDs)
v Words defined in text (example: a nonswitched line is called a
point-to-point line)
v Emphasis of words and letters (words as words example: "Use the word
that to introduce a restrictive clause."; letters as letters example: "The
LUN address must start with the letter L.")
v New terms in text (except in a definition list): a view is a frame in a
workspace that contains data
v Variables and values you must provide: ... where myname represents....
Monospace
v Examples and code examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text

x IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options

List of abbreviations
The API documentation for the ObjectServer HTTP interface and the ObjectServer
OSLC interface use the following abbreviations and terms.
HTTP Hyper Text Transfer Protocol. HTTP version 1.1 is defined in RFC2616.
Unless otherwise noted, the term HTTP is used in this document to mean
both HTTP and HTTPS.
HTTPS
Hyper Text Transfer Protocol Secure, as defined in RFC2818.
JazzSM
Jazz for Service Management, which is available from https://
www.ibm.com/developerworks/mydeveloperworks/groups/service/
html/communityview?communityUuid=69ec672c-dd6b-443d-add8-
bb9a9a490eba.
JSON JavaScript Object Notation, as defined in ECMA-262.
MIME Multipurpose Internet Mail Extensions. MIME media types are defined in
IANA MIME Media Types.
OSLC Open Services for Lifecycle Collaboration, as defined at
http://open-services.net.
REST Representational State Transfer, as originally and informally described in
Architectural Styles and the Design of Network-based Software Architectures.
URI Uniform Resource Identifier, as defined in RFC3986.
XML eXtensible Markup Language, as defined by W3C.

About this publication xi

xii IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Chapter 1. Overview of the ObjectServer OLSC interface
The Open Lifecycle for Services Collaboration (OSLC) interface is an event server
provider that presents a resource-linked data view of events and the associated
journal and detail resources. The OSLC interface gives access to three key
ObjectServer resources: event, journal, and details. In addition, the interface gives
read-only access to two further ObjectServer resources: person and group. The
person and group resources represent ownership data in the event and journal
resources.

You can enable the interface by setting properties in the ObjectServer.

The ObjectServer hosts another API that is called the HTTP interface. This API
provides access to table data in the ObjectServer through a structured URI format
that uses HTTP. POST, PATCH, GET, and DELETE requests. For more information
about the HTTP interface, see the IBM Tivoli Netcool/OMNIbus HTTP Interface
Reference Guide.

The following figure shows the relationships that can exist between the
ObjectServer resources that can be accessed by using the OSLC interface.

Figure 1. Relationships between event management OSLC resources

© Copyright IBM Corp. 1994, 2017 1

Enabling the HTTP interface and OSLC interface in the ObjectServer
The ObjectServer HTTP and OSLC interfaces are disabled by default, because the
interfaces need to be configured for a secure setup.

Before you begin

Work out which ObjectServers in your environment need to be accessed via HTTP
or HTTPS. Not all ObjectServers in an environment need to grant access to
ObjectServer data through an HTTP-based mechanism.

About this task

Because the hosting of the HTTP and OSLC interfaces in the ObjectServer requires
an embedded HTTP server, the ObjectServer can serve files to HTTP clients.
Although the ObjectServer can serve pages, it is not optimized for page-serving,
unlike an Apache web server. For this reason, do not use the ObjectServer to host
anything other than rudimentary HTML or JavaScript pages.

Procedure
1. To enable the interfaces, set the NRestOS.Enable property to TRUE.
2. To configure the embedded HTTP server so that the interfaces are active on an
HTTP port, specify the listening port for the connection type. For example, to
make the interfaces listen on port 8080, set the properties as follows:
NHttpd.EnableHTTP : TRUE
NHttpd.ListeningPort : 8080
3. If you want the interfaces to be active on an HTTPS port on 9090, set the
properties that are shown in the following example. Because an HTTPS port is
SSL encrypted, a certificate file that contains an appropriate certificate needs to
be created and protected by a password.
NHttpd.SSLEnable : TRUE
NHttpd.SSLListeningPort : 9090
NHttpd.SSLCertificate : “certificatelabel”
4. To enable file-serving from the ObjectServer, set the NHttpd.EnableFileServing
property. The root of the served pages is defined by the NHttpd.DocumentRoot
property.
5. To generate the members resource reference list in the RDF/XML payload of
Event, Journal, and Detail query capability responses in both Collection and
ResponseInfo resource instances, set the NRestOS.OSLCRDFMsgFormat to
“MIGRATION”. For more information about this parameter and why you might
need to set it, see the section Updates to the HTTP interface and OSLC interface in
the Release Notes.

ObjectServer properties that control the HTTP interface and

OSLC interface
ObjectServer properties that control the HTTP and OSLC interfaces.

The following table lists the ObjectServer properties that control the HTTP interface
and the OSLC interface.

2 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Table 3. Properties and command-line options for controlling the HTTP interface and the
OSLC interface
Property Command-line option Description
NRestOS.Enable TRUE | FALSE -nrestosenable TRUE | FALSE Enables the HTTP interface
and the OSLC interface to
the ObjectServer.

The default is FALSE, which

means that the interfaces are
disabled.
NRestOS.OSLCResource -nrestososlcrescfg string The path to the OSLC
ConfigFile string resource configuration file.
This JSON file defines how
columns from the
ObjectServer schema are
mapped to properties in the
OSLC event domain.

The default is
$OMNIHOME/etc/restos/
resourcecfg.json.

The following table lists the ObjectServer properties that control the embedded
HTTP server.
Table 4. Properties and command-line options for controlling the embedded HTTP server
Property Command-line option Description
NHttpd.AccessLog string -nhttpd_accesslog string Specifies the name and
location of the log file where
the server logs all requests
that it processes.

The default is
$OMNIHOME/log/
NCOMS_http_access.log.
NHttpd.Authentication -nhttpd_authdomain string Specifies the authentication
Domain string domain that is used when
requesting authentication
details over the HTTP or
HTTPS connection.

The default is omnibus.

Chapter 1. Overview 3
 Table 4. Properties and command-line options for controlling the embedded HTTP
server (continued)
Property Command-line option Description
NHttpd.ConfigFile string -nhttpd_configfile string Specifies the path to a JSON
configuration file.

The default is
$OMNIHOME/etc/
libnhttpd.json, which
enables mimeType settings
and HTTP headers in HTTP
response files.

For more information about

the libnhttpd.json
configuration file, see
Advanced ObjectServer
HTTP Interface
Configuration
NHttpd.DocumentRoot string -nhttpd_docroot string Specifies the document root
of the embedded web
service.

The default is
$OMNIHOME/etc/restos/
docroot.
NHttpd.EnableFileServing -nhttpd_enablefs TRUE | Use this property to enable
TRUE | FALSE FALSE default file serving by the
ObjectServer. This allows the
ObjectServer to act as a
simple HTTP server that
serves files from the local
filesystem.

The default is FALSE.

NHttpd.ExpireTimeout -nhttpd_exptimeout unsigned Specifies the maximum time,
unsigned in seconds, that an HTTP 1.1
connection remains idle
before it is dropped.

The default is 15.

NHttpd.ListeningHostname -nhttpd_hostname string Specifies the listening host
string name or IP address that can
be used as the hostname part
of a URI to the ObjectServer
HTTP or HTTPS interface.

The default is hostname.

NHttpd.SSLListeningPort -nhttpd_sslport integer Specifies the port on which
integer the ObjectServer listens for
HTTPS requests.

The default is 0.
NHttpd.SSLCertificate string -nhttpd_sslcert string Specifies the name of the SSL
certificate of the server.

The default is ''.

4 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Table 4. Properties and command-line options for controlling the embedded HTTP
server (continued)
Property Command-line option Description
NHttpd.SSLEnable TRUE | -nhttpd_sslenable TRUE | Enables the use of SSL
FALSE FALSE support.

The default is FALSE.

NRestOS.OSLCRDFMsgFormat nrestososlcrmf string Set this property to the string
string MIGRATION to redevelop any
utilities that are based on the
ObjectServer OSLC interface
so that the members resource
reference list is generated in
a Collection resource
instance instead of a
ResponseInfo resource
instance in the RDF/XML
payload of the Event, Detail,
and Journal query capability.

The MIGRATION setting means

that the members resource
reference list is generated in
both a Collection and a
ResponseInfo resource
instance. Redevelop your
OSLC utilities to generate the
members resource reference
list only in the Collection
resource instance. After the
code that generates the list in
ResponseInfo resource
instance is removed, reset
this property.

For more information about the properties and command-line options of the
ObjectServer, see the IBM Tivoli Netcool/OMNIbus Administration Guide.

Enabling and configuring the IBM JazzSM service provider registry

If your environment uses Jazz for Service Management (JazzSM), you can
configure the ObjectServer to register with the JazzSM service provider registry.
The ObjectServer is registered as an event OSLC service provider. Registrations to
JazzSM registries are configured and managed by the OSLC service provider
registry table, registry.oslcsp.

About this task

Access to this table is granted only to the root user and administrators that have
the OSLCAdmin role. Registrations cannot be updated. Registration records can be
only inserted and deleted, not updated.

Chapter 1. Overview 5
 Procedure
v To create a registration, insert a registration entry into the registry.oslcsp table.
The following example shows a sample SQL INSERT command for the JazzSM
service provider registry that runs on the host jazzsm.company.com, on port 9080,
with the default credentials:
INSERT INTO registry.oslcsp ( Name, RegistryURI,
RegistryUsername, RegistryPassword )
VALUES ( ’MyRegistration’,
’http://jazzsm.company.com:9080/oslc/pr’,
’system’, ’manager’ );

After the insert is made, the ObjectServer attempts to register the OSLC interface
of the local ObjectServer with the defined JazzSM service provider registry. If the
registration is successful, the registration URI that was created is stored in the
RegistrationURI field. The Registered field is set to 1. If the registration is not
successful, the Registered field is set to 0.
v To remove a registration from a JazzSM service provider registry, delete the
registration entry from the table. For example, to remove the registration that is
shown in the previous example, use the SQL DELETE command that is shown
in the following example:
DELETE FROM registry.oslcsp WHERE Name=’MyRegistration’;

If the registration record contains a registration URI that is registered with the
defined JazzSM service provider registry, the ObjectServer deletes the record
after you delete the row from the table.

What to do next

If a registration fails, see the ObjectServer log file.

registry.oslc table
This table is used to configure and manage registrations of OSLC service providers
to IBM® JazzSM service registries.
Table 5. OSLC service provider registration table registry.oslcsp.
Column Type Description
Name VARCHAR(64) A user-defined name for the
registration table entry.
RegistryURI VARCHAR(1024) The OSLC service provider
services record of the registry
service. RegistryURI is the
primary key of the table.
RegistryUsername VARCHAR(64) The user that is used to
authenticate with the JazzSM
service provider registry.
RegistryPassword VARCHAR(64) The password that is used to
authenticate with the JazzSM
service provider registry.

6 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Table 5. OSLC service provider registration table registry.oslcsp. (continued)
Column Type Description
Registered integer Indicates whether the entry
has a registration record with
the JazzSM registry service.
Possible values are as
follows:
v 0: The entry does not have
a registration.
v 1: The entry has a
registration.
RegistrationURI VARCHAR(1024) The URI of the registration
record in the JazzSM service
provider registry for this
ObjectServer.
LastRegistered time The date and time of the last
successful registration to the
JazzSM service provider
registry.

Configuring single sign-on with Jazz SM

If IBM Jazz for Service Management (Jazz SM) is deployed in the environment, you
can configure the ObjectServer to participate in the OSLC Single Sign-On (SSO)
environment via the Jazz SM authentication services and LTPA tokens via its
security services component.

About this task

For the OSLC interface to participate in the OSLC SSO environment, the
ObjectServer requires the details of the location of the Jazz SM authentication
service and appropriate access credentials to that service.

For more information about the security services of Jazz SM, see its developer
works wiki: https://www.ibm.com/developerworks/community/wikis/
home?lang=en#!/wiki/W8b1151be2b42_4819_998e_f7de7db7bfa2/page/Security
%20Services

For more information about property value encryption, see the OMNIbus
documentation: http://www-01.ibm.com/support/knowledgecenter/
SSSHTQ_7.4.0/com.ibm.netcool_OMNIbus.doc_7.4.0/omnibus/wip/admin/
reference/omn_adm_propsfileencryption.html?lang=en
Table 6. Authentication service property settings
Property name Type Description
enabled Boolean Defines whether the
specified authentication
service is used to validate
LTPA tokens with.

The default is FALSE

Chapter 1. Overview 7
 Table 6. Authentication service property settings (continued)
Property name Type Description
uri String The URI to the Jazz SM
security service
authentication trust token
service. Unless the context
root or port was changed, it
will only be necessary to
change “localhost” to the
host name where the service
is running. If HTTPS is to be
used, ensure that the public
key of the service was
imported into the OMNIbus
keystore and change the port
to the HTTPS port, which by
default is 16311.

The default is
http://localhost:16310/
TokenService/services/
Trust”
username String The name of the user that
the OSLC interface uses to
authenticate with the
authentication service.

The default is system

password String The password of the user
that the OSLC interface uses
to authenticate with the
authentication service. The
password can be stored in
this configuration file in
either plain text or as an AES
encrypted string generated
via the
“nco_aes_crypt”utility.

The default is manager

osusername String All commands in the
ObjectServer run as a specific
user, as it is that user that
defines what can be seen and
accessed. If the user name
that is contained in a
validated LTPA token does
not match any ObjectServer
user, the OSLC interface runs
the request as this fail-safe
ObjectServer user.

It is recommended that the

ObjectServer user set is
synchronized with those
being used in the SSO
environment.

The default is root

8 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Procedure
1. To configure SSO support, edit the server configuration file. The server
configuration file location is specified by the ObjectServer property
NRestOS.ServerConfigFile. The default server configuration file is
$OMNIHOME/etc/restos/servercfg.json
2. Use the following values in the authentication service settings section:
{
"authsrv" : {
"enabled" : false,
"uri” : "http://localhost:16310/TokenService/services/Trust",
"username" : "system",
"password" : "manager",
"osusername" : "root"
}
}
3. Save the file.

Adding event collection identifier patterns

To add an event collection identifier pattern (ECIP), insert a new row in the
registry.oslcecip table.

Results

After an ECIP definition is inserted into registry.oslcecip table it, a database trigger
is invoked. The trigger creates a registration request row in the
registry.oslcecip_regs table for this ECIP against each provider registry with which
the ObjectServer is registered. The registration request is read up by the OSLC
provider, converted to a provider record template, and registered with the Jazz for
Service Management registry.

Example

This example describes how to create a query pattern for a computer system
resource type . The common query pattern that Tivoli Netcool/OMNIbus uses for
locating events that are related to a computer system is to use the fully qualified
domain name that is in the Node column of the event schema. The source type
URI for a computer system is as follows:
http://open-services.net/ns/crtv#ComputerSystem

The property values that are available to this resource type include an fqdn
property that can be used for this pattern. Therefore, write the SQL INSERT
statement into the registry.oslcecip table as follows:
INSERT INTO registry.oslcecip
(Name,Description,ResourceType,QueryPattern)
VALUES
(’ComputerSystem’,
’Query pattern for computer system resources type.’,
’http://open-services.net/ns/crtv#ComputerSystem’,
’Node=\’@http://open-services.net/ns/crtv#fqdn\’’ );
Related reference:
“registry.oslcecip table” on page 10
This table is used by OSLC service providers to configure and manage event
collection identifier patterns (ECIPs).

Chapter 1. Overview 9
 “registry.oslcecip_regs table” on page 11
This table is used to manage registrations of event collection identifier patterns
(ECIPs). When an ECIP is inserted in the registry.oslcecip table, a row is also
inserted in the registry.oslcecip_regs table for any provider register with which the
ObjectServer OSLC provider is registered.

Removing event collection identifier patterns

To remove an event collection identifier pattern (ECIP), remove the entry for the
ECIP from the registry.oslcecip table.

Results

When an entry is deleted from registry.oslcecip table, a database trigger is invoked.

The trigger deletes any registration rows in the registry.oslcecip_regs table for this
ECIP. The deletion of the registration row deletion is read by the OSLC provider
and any associated provider record template that is registered with a Jazz for
Service Management registry is removed.

Example

The following example shows the SQL statement to remove a query pattern for
computer system resources:
DELETE FROM registry.oslcecip WHERE Name=’ComputerSystem’;
Related reference:
“registry.oslcecip table”
This table is used by OSLC service providers to configure and manage event
collection identifier patterns (ECIPs).
“registry.oslcecip_regs table” on page 11
This table is used to manage registrations of event collection identifier patterns
(ECIPs). When an ECIP is inserted in the registry.oslcecip table, a row is also
inserted in the registry.oslcecip_regs table for any provider register with which the
ObjectServer OSLC provider is registered.

registry.oslcecip table
This table is used by OSLC service providers to configure and manage event
collection identifier patterns (ECIPs).
Table 7. Event collection identifier patterns table registry.oslcecip
Column Type Description
CIPId Incremental A unique integer key that is
automatically assigned to the
row by the ObjectServer. This
ID is used as a foreign key
between the ECIP definition
and the Jazz for Service
Management registry
provider template
registration.
ResourceType varchar(1024) The resource type URI of the
ECIP. The resource type URI
is not limited to this set and
any unique URI can be used
to identify the resource type.

10 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Table 7. Event collection identifier patterns table registry.oslcecip (continued)
Column Type Description
Name varchar(64) The name of the ECIP.
Description varchar(1024) The description of the ECIP.
QueryPattern varchar(4096) The query pattern, which is
defined as an SQL WHERE
clause that refers to resource
properties.

registry.oslcecip_regs table
This table is used to manage registrations of event collection identifier patterns
(ECIPs). When an ECIP is inserted in the registry.oslcecip table, a row is also
inserted in the registry.oslcecip_regs table for any provider register with which the
ObjectServer OSLC provider is registered.
Table 8. OSLC ECIP registry rable registry.oslcecip_regs
Row Type Description
CIPId Integer The foreign integer key that
is assigned to the related
event collection identifier
pattern in the
registry.oslcecip table.
RegistryURI varchar(1024) The JazzSM service provider
registration that this provider
record template registration
is associated too in the
registry.oslcsp table.
Registered integer Indicates whether the entry
has a registration record with
the Jazz for Service
Management registry service.
Possible values are as
follows:
v 0: The entry does not have
a registration.
v If the entry has a value
that is not 0, the entry has
a registration.
RegistrationURI varchar(1024) The URI of the registration
record in the Jazz for Service
Management service
provider registry for this
ObjectServer.
LastRegistered time The date and time of the last
successful registration with
the Jazz for Service
Management service
provider registry.
RequestTime time The date and time of the
request to register the
associated ECIP as a
provider record template.

Chapter 1. Overview 11
12 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Chapter 2. OSLC services
The format and nature of the event management OSLC URIs that are hosted in the
ObjectServer

Base URI

The base URI for the OSLC interface is as follows.

http://host:port/objectserver/oslc/

Service provider service

The OLSC pattern for service providers introspects a service provider registry, for
example the registry that is in Jazz for Service Management. When an HTTP GET
request is made on the root URI of the service, a redirection to the service provider
URI is returned. In real-life environments, use the OSLC interface through the
service provider definition, where these URIs are discovered and used opaquely.

If the environment has no registry, the Tivoli Netcool/OMNIbus event

management service provider definition is available through the URI that is shown
in the following example. This shows a sample service provider definition for the
default ObjectServer, NCOMS.
http://host:port/objectserver/oslc/services

The service provider services URI supports the following HTTP methods: GET.

Service provider service: GET request

The elements of an HTTP GET request to retrieve the service provider definition.
Table 9. Service provider services URI: GET request
Element Description
HTTP method GET
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
application/x-oslc-em-service-
description+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
services

Related reference:
“Authentication mechanisms” on page 58
Connections to the OSLC interface require a set of Tivoli Netcool/OMNIbus user
credentials for authentication. The only supported authentication scheme is basic
HTTP authentication. If no basic HTTP credentials are provided in the HTTP
© Copyright IBM Corp. 1994, 2017 13
 Authorization header, a 401 (Not Authorized) HTTP response is returned.
“Example: Service provider service GET request” on page 83

Service provider service: GET response

The elements of an HTTP GET response for the retrieval of the service provider
definition.
Table 10. HTTP GET elements
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
application/x-oslc-em-service-
description+xml
Normal HTTP response codes 200 (OK): The response body contains the
RDF/XML ServiceProvider. For more
information, see http://open-
services.net/bin/view/Main/
OslcCoreVocabulary#ServiceProvider.
Error HTTP response codes 500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Common HTTP codes are 401

(Unauthorised), 403 (Forbidden), 406 (Not
Acceptable).

Related reference:
“HTTP response codes” on page 57
The common set of HTTP response codes for an HTTP method from the
ObjectServer OSLC interface.
“Error RDF/XML message payload” on page 59
The OSLC interface might return an RDF/XML error message payload of OSLC
type Error in any nonsuccess response code, such as 500.
“Example: Service provider service GET response” on page 83

14 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Resource shape service
The resource shape service returns the definition of the service provider. The
resource support the event management resources in the OLSC interface.

The following example shows the URI of the resource shape service.
http://host:port/objectserver/oslc/shape

The following HTTP methods are supported: GET.

Related reference:
Appendix A, “Property XML name spaces,” on page 61

Resource shape service: GET request

The elements of an HTTP GET request to retrieve the service provider definition.
Table 11. Resource shape service: GET request
Element Description
HTTP method GET
Query parameters
type
Required: Specifies the required
resource shape. Valid values are event,
journal, or details.
create
Required: Specifies whether the resource
shape is required. Valid values are true
or false.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
application/x-oslc-em-service-
description+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
services

Related reference:
“Authentication mechanisms” on page 58
Connections to the OSLC interface require a set of Tivoli Netcool/OMNIbus user
credentials for authentication. The only supported authentication scheme is basic
HTTP authentication. If no basic HTTP credentials are provided in the HTTP
Authorization header, a 401 (Not Authorized) HTTP response is returned.
“Example: Shape service GET request” on page 84

Chapter 2. OSLC services 15

 Resource shape service: GET response
The elements of an HTTP GET response for the retrieval of the service provider
definition.
Table 12. Resource shape service: GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
application/x-oslc-em-service-
description+xml
Normal HTTP response codes 200 (OK): The response body contains the
RDF/XML ServiceProvider definition.
For more information, see
http://open-services.net/ns/
core#ResourceShape.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Common HTTP code are 401

(Unauthorized), 403 (Forbidden), 406 (Not
Acceptable).

Related reference:
“HTTP response codes” on page 57
The common set of HTTP response codes for an HTTP method from the
ObjectServer OSLC interface.
“Error RDF/XML message payload” on page 59
The OSLC interface might return an RDF/XML error message payload of OSLC
type Error in any nonsuccess response code, such as 500.
“Example: Shape service GET response” on page 84

16 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Chapter 3. ObjectServer OSLC resources
The OLSC resources that are hosted in the ObjectServer.

ObjectServer OSLC resources: event

This resource provides a representation of an event that is stored in the
ObjectServer.

Event definition
Tivoli Netcool/OMNIbus has a flat event schema that it is possible to modify. You
can modify or remove any column of the schema except for the core columns, such
as Serial and Identifier. You can also add new columns. The dynamic nature of the
schema means that the OSLC event resource definition is also likely to be dynamic,
which means that different environments have different shapes, except for the core
column section.

You can use a configuration file to define which non-core columns are in the event
resource. To define the columns, edit the configuration file. This definition is used
to generate the resource representation that is presented by an HTTP request to the
resource URI. For example, you can restrict the non-core columns in the schema to
only those columns that you have defined.

To define which non-core columns are in the event resource, a configuration file is
provided. This definition is used to generate the resource representation that is
presented by an HTTP request to the resource URI. Also use the configuration file
to define the XML name space that contain the properties of the resource. Six name
spaces are used in the default setup.

The following table shows the event resource, as defined by the default
configuration file, which contains only the core columns and the OMNIbus
required properties.
Table 13. Core properties and Tivoli Netcool/OMNIbus-specific properties of the event
resource shape
Event
column or
description
in Tivoli
Prefixed Represent- Netcool/
name Occurs Read-only Value type ation OMNIbus
dcterms: zero-or-one false string Not Identifier
identifier applicable
dcterms: zero-or-one false datetime Not First
created applicable Occurence
oslcem: zero-or-one false resource Reference OwnerUID
ownerUID
oslcem: zero-or-one false integer Not Severity
severity applicable
oslcem: zero-or-one false string Not Summary
summary applicable

© Copyright IBM Corp. 1994, 2017 17

 Table 13. Core properties and Tivoli Netcool/OMNIbus-specific properties of the event
resource shape (continued)
Event
column or
description
in Tivoli
Prefixed Represent- Netcool/
name Occurs Read-only Value type ation OMNIbus
oslcem:node zero-or-one false string Not Node
applicable
oslcem:agent zero-or-one false string Not Agent
applicable
oslcem: zero-or-one false string Not AlertGroup
alertGroup applicable
oslcem: zero-or-one false datetime Not Last
last applicable Occurrence
Occurrence
oslcem:tally zero-or-one false integer Not Tally
applicable
oslcem: zero-or-one false boolean Not Acknow
acknowledg applicable ledged
ed
oslcem:serial zero-or-one true integer Not Serial
applicable
oslcem: zero-or-one true integer Not ServerSerial
serverSerial applicable
oslcem: zero-or-one true integer Not ServerName
serverName applicable
oslcem: zero-or-one false string Not AlertKey
alertKey applicable
oslcem: zero-or-one false string Not Manager
manager applicable
oslcem: zero-or-one true datetime Not StateChange
stateChange applicable
oslcem: zero-or-one true datetime Not InternalLast
internalLast applicable
oslcem:type zero-or-one false integer Not Type
applicable
oslcem:class zero-or-one false integer Not Class
applicable
oslcem:grade zero-or-one false integer Not Grade
applicable
oslcem: zero-or-one false resource Reference OwnerGID
OwnerGID
oslcem: zero-or-one false string Not TaskList
taskList applicable
oslcem: zero-or-one false string Not SuppressEscl
suppressEscl applicable
oslcem:flash zero-or-one false integer Not Flash
applicable

18 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Table 13. Core properties and Tivoli Netcool/OMNIbus-specific properties of the event
resource shape (continued)
Event
column or
description
in Tivoli
Prefixed Represent- Netcool/
name Occurs Read-only Value type ation OMNIbus
oslcem: zero-or-one false integer Not ExpireTime
expireTime applicable
oslcem: zero-or-one false string Not Customer
customer applicable
oslcem: zero-or-one false string Not Service
service applicable
oslcem: zero-or-one false integer Not ProbeSub
probeSub applicable SecondId
SecondId
oslcem: zero-or-one true resource Reference URL that
journal fetches all the
journals that
are associated
with the
event
oslcem:detail zero-or-one true resource Reference URL that
fetches all the
details that
are associated
with the
event

For more information about the alerts.status table, see the IBM Tivoli
Netcool/OMNIbus Administration Guide.

Event creation factory

An event resource is created by posting an RDF/XML event resource description
document to the creation factory URI.

The following example shows a sample URI.

http://host:port/objectserver/oslc/factory/event

The following HTTP methods are supported: POST.

Event creation factory: POST request

The requirements for a POST request to the event resource creation factory URI.
Table 14. Event creation factory: POST request
Element Description
HTTP method POST
Query parameters Not applicable

Chapter 3. ObjectServer OSLC resources 19

 Table 14. Event creation factory: POST request (continued)
Element Description
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Content-type application/rdf+xml
Example http://localhost/objectserver/oslc/
factory/event

Related reference:
“Authentication mechanisms” on page 58
Connections to the OSLC interface require a set of Tivoli Netcool/OMNIbus user
credentials for authentication. The only supported authentication scheme is basic
HTTP authentication. If no basic HTTP credentials are provided in the HTTP
Authorization header, a 401 (Not Authorized) HTTP response is returned.
“Example: Event creation” on page 69
This example creates an event and sets various properties.
“Example: Event creation factory POST request” on page 85

Event creation factory: POST response

The elements of an HTTP POST response for the creation of an event resource
through the event creation factory
Table 15. Event creation factory: POST response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Location
The URI of the created resource.
Content-type application/rdf+xml
Normal HTTP response codes 201 (Created): The URI of created
resource contained in the HTTP header
Location of the response. The response
body contains an RDF/XML success
message.

20 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Table 15. Event creation factory: POST response (continued)
Element Description
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden)406
(Not acceptable), and 415 (Unsupported
Media Type).

Related reference:
“Success RDF/XML message payload” on page 58
The OSLC interface returns an RDF/XML success message payload of OSLC type
ResponseInfo.
“Error RDF/XML message payload” on page 59
The OSLC interface might return an RDF/XML error message payload of OSLC
type Error in any nonsuccess response code, such as 500.
“Example: Event creation factory POST response” on page 86

Event query capability

The event query capability allow queries to be made against the event set that is
contained in Tivoli Netcool/OMNIbus.

The following example shows a sample URI of the event query capability.
http://host:port/objectserver/oslc/query/events

The following HTTP methods are supported: GET.

Event query capability: GET request

The requirements for a HTTP GET request to the event resource query capability
URI.
Table 16. Event query capability: GET request
Element Description
HTTP method GET

Chapter 3. ObjectServer OSLC resources 21

 Table 16. Event query capability: GET request (continued)
Element Description
Query parameters
oslc:where
Defines the conditions that the related
resources must satisfy. This parameter is
equivalent to the WHERE clause of an
SQL statement.
oslc.select
Defines the properties of the event
resource that should appear in the
results of the HTTP response. This
parameter is equivalent to the column
component of an SQL SELECT
statement.
oslc.orderBy
Defines the sort order of the result set.
This parameter is equivalent to the
ORDER BY clause of an SQL SELECT
statement.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
query/events
http://localhost/objectserver/oslc/
query/events?oslc.where=oslcem
%3Aseverity%3D5&oslc.orderBy=oslcem
%3Aserial
http://localhost/objectserver/oslc/
query/events?oslc.select=oslcem
%3Aseverity

Related reference:
“Authentication mechanisms” on page 58
Connections to the OSLC interface require a set of Tivoli Netcool/OMNIbus user
credentials for authentication. The only supported authentication scheme is basic
HTTP authentication. If no basic HTTP credentials are provided in the HTTP
Authorization header, a 401 (Not Authorized) HTTP response is returned.
“Example: Event query capability GET request” on page 86

22 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Event query capability: GET response
The elements of an HTTP GET response to the event resource query capability
URI.
Table 17. Event query capability: GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains the
RDF/XML event resource query response
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: Event query result” on page 70
The result message from the query capability is nonstandard but optimized to
prevent unnecessary repetitive fetches of individual events. When a query is
resolved, the OSLC interface has all of the events already. Consequently, in
addition to generating a ResponseInfo section detailing the members of the result,
the message also provides all of the requested properties of the events in the
response too.
“Error RDF/XML message payload” on page 59
The OSLC interface might return an RDF/XML error message payload of OSLC
type Error in any nonsuccess response code, such as 500.
“HTTP response codes” on page 57
The common set of HTTP response codes for an HTTP method from the
ObjectServer OSLC interface.
“Example: Event query capability GET response” on page 86

Chapter 3. ObjectServer OSLC resources 23

 Event resource
Every event in Tivoli Netcool/OMNIbus has its own instance URI. You can use the
URI to fetch, update, and delete events. The opacity of the interface means that
you do not need to look up a key field to manually create the resource URI.
Resource URIs are returned to the caller in HTTP responses from the creation
factory and query capability.

The following example shows a sample event resource URI.

http://host:port/objectserver/oslc/event/keyfield

Where keyfield is the key field of the event resource.

The following HTTP methods are supported: GET, PATCH, DELETE.

The update of an event is supported only through a PATCH request. The semantics
of an HTTP PUT request do not translate well to event updates. An event resource
is updated by patching an RDF/XML event resource description document to the
specific event resource instance URI. Because this is a PATCH operation, specify
only the properties that are to be updated.

Event resource: GET request

The requirements for a HTTP GET request to an event resource instance URI.
Table 18. Event resource: GET request
Element Description
HTTP method GET
Query parameters
oslc:select
Defines the properties of the event
resource that appear in the results of the
HTTP response. This parameter is
equivalent to the column list component
of an SQL SELECT statement.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
event/9999%2BNCOMS

Related reference:
“Authentication mechanisms” on page 58
Connections to the OSLC interface require a set of Tivoli Netcool/OMNIbus user
credentials for authentication. The only supported authentication scheme is basic
HTTP authentication. If no basic HTTP credentials are provided in the HTTP
Authorization header, a 401 (Not Authorized) HTTP response is returned.
“Example: Event resource GET request” on page 87

24 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Event resource: GET response
The elements of a HTTP GET response to an event resource instance URI.
Table 19. Event resource: GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains the
RDF/XML event resource description of
the event.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
404 (Not Found): The requested row was
not found in the table because the row
was deleted.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: Event” on page 67

“Example: Event resource GET response” on page 87

Event resource: PATCH request

Table 20. Event resource: PATCH request
Element Description
HTTP method PATCH
Query parameters Not applicable.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml

Chapter 3. ObjectServer OSLC resources 25

 Table 20. Event resource: PATCH request (continued)
Element Description
Request body An RDF/XML partial description of the
event resource, which contains the
event-defining properties to update.
Example http://localhost/objectserver/oslc/
event/9999%2BNCOM

Related reference:
“Example: Event PATCH” on page 70
This example updates the creator, lastOccurence, acknowledged, ownerGID and
location properties.
“Example: Event resource PATCH request” on page 88

Event resource: PATCH response

The elements for a HTTP PATCH response to an event resource instance URI.
Table 21. Event resource: PATCH response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
404 (Not Found): The requested row was
not found in the table because the row
was deleted.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden)406
(Not acceptable), and 415 (Unsupported
Media Type).

Related reference:
“Success RDF/XML message payload” on page 58
The OSLC interface returns an RDF/XML success message payload of OSLC type

26 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

ResponseInfo.
“Example: Event resource PATCH response” on page 89

Event resource: DELETE request

The requirements for a HTTP DELETE request to an event resource instance URI.
Table 22. Event resource: DELETE request
Element Description
HTTP method DELETE
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Example

Related reference:
“Example: Event resource DELETE request” on page 89

Event resource: DELETE response

The elements for a HTTP DELETE response to an event resource instance URI
Table 23. Event resource: DELETE response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.
Error HTTP response codes 404 (Not Found): The requested row was
not found in the table because the row
was deleted.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Chapter 3. ObjectServer OSLC resources 27

 Related reference:
“Success RDF/XML message payload” on page 58
The OSLC interface returns an RDF/XML success message payload of OSLC type
ResponseInfo.
“Example: Event resource DELETE response” on page 89

OSLC resource: Journal

This resource represents an informational log entry by a Tivoli Netcool/OMNIbus
user or an automatic action based. The log entry is based on an update that is
made on an associated event. The log messages become a journal of the actions
that occurred during the resolution and management of that event. A journal can
be related to only one event, but one event can have many journals.

Journal definition
You can define the set of properties that make up a journal resource, in the same
way as the event resource. The Tivoli Netcool/OMNIbus journal schema is fixed
and cannot be changed. Consequently, the valid modifications that you can make
to the journal definition are limited to XML name spaces and types.

The following table shows the default journal resource, as defined by the default
definition configuration file.
Table 24. Default properties of the journal resource shape
Event
column or
description
in Tivoli
Prefixed Represent- Netcool/
name Occurs Read-only Value type ation OMNIbus
dcterms: zero-or-one true string Not KeyField
identifier applicable
dcterms: zero-or-one false datetime Not Chrono
created applicable
oslcem: zero-or-one false resource Reference ownerUID
ownerUID
dcterms: zero-or-one false string Not Text, Text, ....,
content applicable Text

Where Text is
a journal text
column.
These entries
are
concatenated.
oslcem:event zero-or-one true resource Reference The URI of
the event to
which this
journal is
related.

For more information about the alerts.journal table, see the IBM Tivoli
Netcool/OMNIbus Administration Guide.

28 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Journal creation factory
A journal resource is created by posting an RDF/XML journal resource description
document to this creation factory URI.

The following example shows a sample URI.

http://host:port/objectserver/oslc/factory/journal

The following HTTP methods are supported: POST.

Journal creation factory: POST request

The requirements for a HTTP POST request to the journal resource creation factory
URI.
Table 25. Journal creation factory: POST request
Element Description
HTTP method POST
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Content-type application/rdf+xml
Request body An RDF/XML journal resource description,
which describes the journal to create.
Example http://localhost/objectserver/oslc/
factory/journal

Related reference:
“Example: Journal creation” on page 74

“Example: Journal creation factory POST request” on page 90

Journal creation factory: POST response

The elements of an HTTP POST response for the creation of a journal resource
through the journal creation factory URI.
Table 26. Journal creation factory: POST response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml

Chapter 3. ObjectServer OSLC resources 29

 Table 26. Journal creation factory: POST response (continued)
Element Description
Normal HTTP response codes 201 (Created): The URI of the created
resource is in the HTTP header Location
of the response. The response body
contains the RDF/XML success message.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden)406
(Not acceptable), and 415 (Unsupported
Media Type).

Related reference:
“Success RDF/XML message payload” on page 58
The OSLC interface returns an RDF/XML success message payload of OSLC type
ResponseInfo.
“Example: Journal creation factory POST response” on page 90

Journal query capability

The journal query capability allow queries to be made against the journal set
contained in Tivoli Netcool/OMNIbus.

The following example shows a sample URI.

http://host:port/objectserver/oslc/query/journals

The following HTTP methods are supported: GET.

Related reference:
“Example: Journal query capability GET request” on page 91

Journal query capability: GET request

The requirements for a HTTP GET request to the journal resource query capability.
Table 27. Journal query capability: GET request
Element Description
HTTP method GET

30 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Table 27. Journal query capability: GET request (continued)
Element Description
Query parameters
oslc.where
Defines the conditions that related
resources must satisfy. This parameter is
equivalent to the WHERE clause of an
SQL statement.
oslc.select
Defines the properties of the journal
resource that should appear in the
results of the HTTP response. This
parameter is equivalent to the column
list component of an SQL SELECT
statement.
oslc.orderBy
Defines the sort order of the result set.
This parameter is equivalent to the
ORDER BY clause of an SQL SELECT
statement.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
query/journals
http://localhost/objectserver/oslc/
query/journals?oslc.where=oslcem
%3Aevent%7Boslcem%3AserverSerial%3D99
%20and%20oslcem %3AserverName%3D
%22NCOMS%22%7D&oslc.orderBy=dcterms
%3Acreated

Related reference:
“Example: Journal creation” on page 74

“Example: Journal query capability GET request” on page 91

Journal query capability: GET response

The elements of an HTTP GET response to the journal resource query capability
URI.

Chapter 3. ObjectServer OSLC resources 31

 Table 28. Journal query capability: GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: Journal query result” on page 74
The result message from the query capability is nonstandard but optimized to
prevent unnecessary repetitive fetches of individual journals. When a query is
resolved, the OSLC interface has all of the journals already. Consequently, in
addition to generating a ResponseInfo section detailing the members of the result,
the message provides all the requested properties of the journals in the response.
“Example: Journal query capability GET response” on page 91

Journal resource URI

Every journal in Tivoli Netcool/OMNIbus has its own instance URI. Use this URI
to fetch, update, and delete journals. The opacity of the interface means that you
never need to look up a key field to manually create the resource URI. Resource
URIs are returned to the caller in HTTP responses from the creation factory and
query capability.

The following example shows a sample URI.

http://host:port/objectserver/oslc/journal/keyfield

Where keyfield is the key field of the journal resource.

The following HTTP methods are supported: GET, PATCH, DELETE.

32 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Updates to journal are supported only by a PATCH request. The semantics of an
HTTP PUT request do not translate well to journal updates. A journal resource is
updated by patching an RDF/XML journal resource description document to the
specific journal resource instance URI. Because this operation is a PATCH
operation, you need to specify only the properties that are to be updated.

Journal resource: GET request

The requirements for a HTTP GET request to a journal resource instance URI.
Table 29. Journal resource: GET request
Element Description
HTTP method GET
Query parameters
oslc:select
Defines the properties of the journal
resource that are in the results of the
HTTP request. This parameter is
equivalent to the column list component
of an SQL SELECT statement.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
journal/9999%3A0%3A1337257936

Related reference:
“Example: Journal resource GET request” on page 92

Journal resource: GET response

The elements of a HTTP GET response to a journal resource instance URI.
Table 30. Journal resource: GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.

Chapter 3. ObjectServer OSLC resources 33

 Table 30. Journal resource: GET response (continued)
Element Description
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
404 (Not Found): The requested row was
not found in the table because the row
was deleted.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorized), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: Journal” on page 73

“Example: Journal resource GET response” on page 92

Journal resource: PATCH request

The requirements for a HTTP PATCH request to a journal resource instance URI.
Table 31. Journal resource: PATCH request
Element Description
HTTP method PATCH
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Content-type application/rdf+xml
Request body An RDF/XML partial description of the
journal resource, which defines the
properties that need to be updated.
Example http://localhost/objectserver/oslc/
journal/9999%3A0%3A1337257936

Related reference:
“Example: Journal PATCH” on page 74
This example updates the journal text.
“Example: Journal resource PATCH request” on page 93

34 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Journal resource: PATCH response
The elements for a HTTP PATCH response to a journal resource instance URI.
Table 32. Journal resource: PATCH response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
404 (Not Found): The requested row was
not found in the table because the row
was deleted.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden)406
(Not acceptable), and 415 (Unsupported
Media Type).

Related reference:
“Example: Journal resource PATCH response” on page 93

Journal resource: DELETE request

The requirements for a DELETE request to a journal resource instance URI.
Table 33. Journal resource: DELETE request
Element Description
HTTP method DELETE
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml

Chapter 3. ObjectServer OSLC resources 35

 Table 33. Journal resource: DELETE request (continued)
Element Description
Request body Not applicable
Example http://localhost/objectserver/oslc/
journal/9999%3A0%3A1337257936

Related reference:
“Example: Journal resource DELETE request” on page 93

Journal resource: DELETE response

The elements for a HTTP DELETE response to an journal resource instance URI.
Table 34. Journal resource: DELETE response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.
Error HTTP response codes 404 (Not Found): The requested row was
not found in the table because the row
was deleted.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorized), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: Journal resource DELETE response” on page 94

36 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

OSLC resource: Details
A detail resource represents additional information or a data value for an event. It
usually consists of raw event data from the event source. If an event is not mapped
successfully to the Tivoli Netcool/OMNIbus schema, the raw elements can be
populated as details, so that the failed mapping can be corrected. A detail can be
associated only with one event, but an event can have many details.

Details definition
You can also define the set of properties that make up a detail resource, in the
same way as the event and journal resources. The Tivoli Netcool/OMNIbus details
schema is fixed and cannot be changed. Consequently, the valid modifications that
the you can make to the detail definition are limited to XML name spaces and
types.

The following table shows the default detail resource that is defined by the default
configuration file.
Table 35. Default properties of the detail resource shape
Event
column or
description
in Tivoli
Prefixed Value- Represent- Netcool/
name Occurs Read-only type ation OMNIbus
dcterms: zero-or-one true string Not KeyField
identifier applicable
oslcem: zero-or-one false Boolean Not AttrValue
attrValue applicable
oslcem: zero-or-one false integer Not Sequence
sequence applicable
oslcem: zero-or-one false string Not Name
detailName applicable
oslcem: zero-or-one false string Not Detail
detailValue applicable
oslcem:event zero-or-one true resource Reference The URI of
the detail to
which this
detail is
related.

For more information about the alerts.details table, see the IBM Tivoli
Netcool/OMNIbus Administration Guide.
Related information:
alerts.details table

Chapter 3. ObjectServer OSLC resources 37

 Details creation factory
A detail resource is created by posting an RDF/XML detail resource description
document to this creation factory URI.

The following example shows a sample URI.

http://host:port/objectserver/oslc/factory/detail

The following HTTP methods are supported: POST

Details creation factory: POST request

The requirements for a HTTP POST request to the detail resource creation factory
URI.
Table 36. Details creation factory: POST request
Element Description
HTTP method POST
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Content-type application/rdf+xml
Request body An RDF/XML description of the detail
resource, which describes the details to
create.
Example http://localhost/objectserver/oslc/
factory/detail

Related reference:
“Example: Detail creation factory POST request” on page 94

Event details: POST response

The elements of an HTTP POST response for the creation of a journal resource
through the detail creation factory URI.
Table 37. Event details: POST response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml

38 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Table 37. Event details: POST response (continued)
Element Description
Normal HTTP response codes 201 (Created): The URI of the inserted
row is contained in the HTTP header
Location of the response. The response
body contains a JSON success message.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden)406
(Not acceptable), and 415 (Unsupported
Media Type).

Related reference:
“Example: Details creation factory POST response” on page 95

Query capability
The detail query capability allow queries to be made against the detail set in Tivoli
Netcool/OMNIbus.

The following example shows the query capability.

http://host:port/objectserver/oslc/query/details

The following HTTP methods are supported: GET.

Event details query capability: GET request

The requirements for a HTTP GET request to the detail resource query capability
URI.
Table 38. Event details query capability: GET request
Element Description
HTTP method GET

Chapter 3. ObjectServer OSLC resources 39

 Table 38. Event details query capability: GET request (continued)
Element Description
Query parameters
oslc:where
Defines the conditions that related
resources must satisfy. This parameter is
equivalent to the WHERE clause of an
SQL statement.
oslc:select
Defines the properties of the detail
resource that appear in the results of the
HTTP response. This parameter is
equivalent to the column list component
of an SQL SELECT statement.
oslc:orderBy
Defines the sort order of the result set.
This parameter is equivalent to the
ORDER BY clause of an SQL SELECT
statement.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
query/details
http://localhost/objectserver/oslc/
query/details?oslc.where=oslcem
%3Aevent%7Boslcem%3AserverSerial%3D99
%20and%20oslcem %3AserverName%3D
%22NCOSM%22%7D&oslc.orderBy=oslcem
%3Asequence

Related reference:
“Example: Detail query capability GET request” on page 95

Event details query capability: GET response

The elements of an HTTP GET response to the detail resource query capability
URI.
Table 39. Event details query capability: GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml

40 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Table 39. Event details query capability: GET response (continued)
Element Description
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: Detail query result” on page 77
The result message from the query capability is nonstandard but optimized to
prevent unnecessary repetitive fetches of individual details. When a query is
resolved the OSLC interface has all of the details already. Consequently, in addition
to generating a ResponseInfo section that details the members of the result, the
message provides all the requested properties of the details in the response.
“Example: Detail query capability GET response” on page 95

Event details resource

Every detail in Tivoli Netcool/OMNIbus has its own instance URI. Use this URI to
fetch, update, and delete details. The opacity of the interface means that you never
need to look up a key field to manually create the resource URI. Resource URIs are
returned to the caller in HTTP responses from the creation factory and query
capability.

The following example shows a sample URI.

http://host:port/objectserver/oslc/detail/keyfield

Where keyfield is the key field of the event details resource.

The following HTTP methods are supported: GET, PATCH, DELETE.

Only PATCH requests can be used to update event details. The semantics of a
HTTP PUT request do not translate well to detail updates. A detail resource is
updated by patching an RDF/XML detail resource description document to the
specific detail resource instance URI. Because this is a PATCH operation, specify
only the properties that are to be updated.

Chapter 3. ObjectServer OSLC resources 41

 Event detail resource: GET request
The requirements for a HTTP GET request to a detail resource instance URI.
Table 40. Event detail resource: GET request
Element Description
HTTP method GET
Query parameters
oslc:select
Defines the properties of the detail
resource that appear in the results of the
HTTP response. This parameter is
equivalent to the column list component
of an SQL SELECT statement.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
detail/ABCDEFG%23%23%23%230

Related reference:
“Example: Detail resource GET request” on page 96

Event detail resource: GET response

The elements of a HTTP GET response to a detail resource instance URI.
Table 41. Event detail resource: GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.

42 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Table 41. Event detail resource: GET response (continued)
Element Description
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
404 (Not Found): The requested row was
not found in the table because the row
was deleted.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: Detail” on page 76

“Example: Detail resource GET response” on page 96

Event detail resource: PATCH request

The requirements for a HTTP PATCH request to a detail resource instance URI.
Table 42. Event detail resource: PATCH request
Element Description
HTTP method PATCH
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Content-type application/rdf+xml
Request body An RDF/XML partial description of the
detail resource, which defines the properties
to update.
Example http://localhost/objectserver/oslc/
detail/ABCDEFG%23%23%23%230

Related reference:
“Example: Detail PATCH” on page 76
This example updates the detail property of the resource.
“Example: Detail resource PATCH request” on page 97

Chapter 3. ObjectServer OSLC resources 43

 Event detail resource: PATCH response
The elements for a HTTP PATCH response to a detail resource instance URI.
Table 43. Event detail resource: PATCH response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
404 (Not Found): The requested row was
not found in the table because the row
was deleted.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden)406
(Not acceptable), and 415 (Unsupported
Media Type).

Related reference:
“Example: Detail resource PATCH response” on page 97

Event detail resource: DELETE request

The requirements for a DELETE request to a detail resource instance URI.
Table 44. Event detail resource: DELETE request
Element Description
HTTP method DELETE
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml

44 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Table 44. Event detail resource: DELETE request (continued)
Element Description
Request body Not applicable
Example http://localhost/objectserver/oslc/
detail/ABCDEFG%23%23%23%230

Related reference:
“Example: Detail resource DELETE request” on page 98

Event detail resource: DELETE response

The elements for a HTTP DELETE response to a detail resource instance URI.
Table 45. Event detail resource: DELETE response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: Detail resource DELETE response” on page 98

Chapter 3. ObjectServer OSLC resources 45

OSLC resource: Person
This utility resource provides a meaningful representation of Tivoli
Netcool/OMNIbus user. Events are owned by a user to indicate which user is
processing a particular event. The Tivoli Netcool/OMNIbus schema stores only a
numeric user identifier in the event itself. This utility resource gives you a means
of obtaining the user name and actual name of the users that are processing
events. Tivoli Netcool/OMNIbus users are created through the supplied
administration tools, so require only read-only access.

No creation factory or query capability is available for this resource.

The following example shows a sample URI.

http://host:port/objectserver/oslc/user/userid

Where userid is the Tivoli Netcool/OMNIbus user ID of the resource.

The following HTTP methods are supported: GET.

Person resource: GET request

The requirements for a HTTP GET request of a user resource instance URI.
Table 46. User resource: GET request
Element Description
HTTP method GET
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
user/0

Related reference:
“Example: Group resource GET request” on page 101

46 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Person resource: GET response
The elements of a HTTP GET response of a user resource instance URI.
Table 47. User resource: GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: Group” on page 80

“Example: Group resource GET response” on page 101

OSLC resource: Group

This utility resource provides a meaningful representation of a Tivoli
Netcool/OMNIbus group. Events are owned by a group to indicate which group is
processing a particular event. The Tivoli Netcool/OMNIbus schema stores only a
numeric group identifier in the event itself. This utility resource provides gives you
a means of obtaining the group name. Tivoli Netcool/OMNIbus groups are created
through the existing administration tools, so require only read-only access.

No creation factory or query capability is available for this resource.

The following example shows a sample URI.

http://host:port/objectserver/oslc/user/groupid

Where groupid is the Tivoli Netcool/OMNIbus group ID of the resource.

Chapter 3. ObjectServer OSLC resources 47

 The following HTTP methods are supported: GET.

Group resource: GET request

The requirements for a HTTP GET request of a group resource instance URI.
Table 48. Group resource: GET request
Element Description
HTTP method GET
Query parameters Not applicable
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Example http://localhost/objectserver/oslc/
group/0

Related reference:
“Example: Person resource GET request” on page 101

Group resource: GET response

The requirements for a HTTP GET request of a group resource instance URI.
Table 49. Group resource: GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains an
RDF/XML success message.

48 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 Table 49. Group resource: GET response (continued)
Element Description
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“Example: User” on page 80

“Example: Person resource GET response” on page 101

Event collection identifer pattern

An event collection identifier pattern resource presents a query pattern in the form
of a URI template. This URI template is defined as an RFC 6570 encoded string
and an unordered list of variables requiring expansion within it that string, whose
values are derived from the named resource properties. The definition of a
template that will match a collection of resources is not event resource specific,
therefore a event collection identifier pattern is defined as an Collection Identifier
Pattern instance.

Collection identifier pattern definition

This resource defines to an OSLC consumer how to fetch a collection of resources
from a the service provider and also provides the means to construct a URI by
using a URI template.

The details of the resource are as follows:

v Name: CollectionIdentifierPattern
v Type URI: http://jazz.net/ns/ism/event/omnibus#CollectionIdentifierPattern
Table 50. Query pattern shape description
Read- Value Represen-
Prefixed name Occurs only type tation Range Description
dcterms:title exactly-one true XMLLiteral N/A N/A A title string that can be used
for display.
dcterms: zero-or-one true String N/A N/A A description of the
description collection identifier pattern,
which can be used for
display.

Chapter 3. ObjectServer OSLC resources 49

Table 50. Query pattern shape description (continued)
Read- Value Represen-
Prefixed name Occurs only type tation Range Description
oslc:resourceType exactly-one true Resource Reference N/A The type of resource that this
collection identifier pattern
requires for the resolution of
expansions in URI templates.
oslcem:clause zero-or-one true String N/A N/A Human readable
representation of the patterns
filter as an SQL WHERE
clause.
rr:uriTemplate exactly-one true Local Inline rr: Describes the collection
resource URITemplate identifier pattern in the form
of a URI template (RFC 6570)
and the expansions required
within it.

URITemplate resource
This resource resource defines an RFC 6570 encoded template URI string and the
set of variables that require values for expansion into the template to construct a
valid and useable URI.

If the values of variables cannot be discovered by parsing the URI template, it is

necessary to provide an unordered list of the variables that require expansion. For
example, if resource property names are used. Because the colon (:) character is a
significant character in URI template syntax, colon-separated name spaces and
names cannot be used. A template variable maps the place holder name in the URI
template to the resource property name.

The details of the resource are as follows:

v Name: URITemplate
v Type URI: http://jazz.net/ns/ism/registry#URITemplate
Table 51. URITemplate shape
Read- Value Represen-
Prefixed name Occurs only type tation Range Description
rr:uriPattern exactly- true String N/A N/A The RFC 6570 formatted URI
one template. The template is
URL-encoded where required.
rr:uriTemplate one-or- true Local Inline rr: URITemplate Describes a variable that
Variable many resource Variable requires so that it can be
expanded in the URI template
and maps the variable name to
the resource property. Used
when values cannot be
discovered by parsing the URI
template. For more information,
see “URITemplateVariable” on
page 51.

50 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 URITemplateVariable
This resource associates the name of a resource property with a named variable in
a URI template that requires expansion. The value required for the variable is
obtained from the named property in the resource instance. This mapping from
variable name to property name solves the problem that is caused by the
significance of the colon character (:) in the URI template syntax.

The details of the resource are as follows:

v Name: URITemplateVariable
v Type URI: http://jazz.net/ns/ism/registry#URITemplateVariable
Table 52. URITemplate shape
Prefixed Read- Value Represen-
name Occurs only type tation Range Description
oslc:name exactly- true String N/A N/A The place holder name in a URI
one template of the property that
needs to be expanded.
rdf:value exactly- true String Inline rr: URITemplate The string representation of the
one Variable property in the resource from
which the value of the variable is
obtained. Also contains
information about how the value
is expanded.

There is a one-to-one relationship between the variable name and the resource
property. If a resource has more than one instance of the named property, only one
can be used. A URI template needs to be defined, if possible, with a list of values
in mind. If a list of values is supported by the template, this support needs to be
opaquely communicated to OSLC consumers. Currently, OSLC consumers need to
build a URI for each property value, fetch the resource collections, and combine
the property values and resource collections.

Event collection identifier pattern query capability

The event collection identifier pattern query capability allow queries to be made
against the event collection identifier pattern set that is contained in Tivoli
Netcool/OMNIbus. The query capability is in figure 54. .

The event collection identifier pattern query capability allow queries to be made
against the event collection identifier pattern set that is contained in Tivoli
Netcool/OMNIbus

The following example shows a sample URI.

http://host:port/objectserver/oslc/query/ecips

The following HTTP methods are supported: GET,

Related reference:
“Example: Event Collection Identifier Pattern response” on page 79
The result message from the query capability is nonstandard but optimized to
prevent unnecessary repetitive fetches of individual event collection identifier
patterns. When a query is resolved, the OSLC interface has all the event collection
identifier patterns already. Consequently, in addition to generating a collection
block detailing the members of the result, the message provides all the requested
properties of the events in the response.

Chapter 3. ObjectServer OSLC resources 51

 Event collection identifier pattern query capability: GET request
The requirements for a HTTP GET request to the event collection identifier pattern
(ECIP) resource query capability URI.
Table 53. ECIP query capability URI: GET request
Element Description
HTTP method GET
Query parameters
oslc:where
Defines the conditions that related
resources must satisfy. This parameter is
equivalent to the WHERE clause of an
SQL statement.
oslc:select
Defines the properties of the event
resource that appear in the results of the
HTTP response. This parameter is
equivalent to the column list component
of an SQL SELECT statement.
oslc:orderBy
Defines the sort order of the result set.
This parameter is equivalent to the
ORDER BY clause of an SQL SELECT
statement.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Examples http://localhost/objectserver/oslc/
query/ecips
http://localhost/objectserver/oslc/
query/ecips?oslc.where=oslc
%3AresourceType%3D%22http%3A%2F
%2Fopen-services.net%2Fns%2Fcrtv
%23ComputerSystem%22
&oslc.orderBy=oslcem%3Aserial
http://localhost/objectserver/oslc/
query/ecips?oslc.select=oslc
%3AresourceType

Related reference:
“Authentication mechanisms” on page 58
Connections to the OSLC interface require a set of Tivoli Netcool/OMNIbus user
credentials for authentication. The only supported authentication scheme is basic
HTTP authentication. If no basic HTTP credentials are provided in the HTTP
Authorization header, a 401 (Not Authorized) HTTP response is returned.
“Event collection identifier pattern query capability: GET request” on page 98

52 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Event collection identifier pattern query capability: GET response
The elements of an HTTP GET response to the event collection identifier pattern
resource query capability URI.
Table 54. ECIP query capability URI : GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains the
RDF/XML event resource description of
the event.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“HTTP response codes” on page 57
The common set of HTTP response codes for an HTTP method from the
ObjectServer OSLC interface.
“Success RDF/XML message payload” on page 58
The OSLC interface returns an RDF/XML success message payload of OSLC type
ResponseInfo.
“Error RDF/XML message payload” on page 59
The OSLC interface might return an RDF/XML error message payload of OSLC
type Error in any nonsuccess response code, such as 500.
“Event collection identifier pattern query capability: GET response” on page 98

Chapter 3. ObjectServer OSLC resources 53

 Event collection identifier pattern resource
Every event collection identifier pattern in Tivoli Netcool/OMNIbus Web GUI has
its own instance URI. Use the URI to fetch a specific event collection identifier
patterns. The ObjectServer OSLC interface cannot be used to create, update, or
delete these resources.

The following example shows a sample URI.

http://host:port/objectserver/oslc/query/ecip/ecipid

Where ecipid is the ID of the event collection identifier pattern resource.

The following HTTP methods are supported: GET,

Related reference:
“Example: Event Collection Identifier Pattern” on page 78

Event collection identifier pattern: GET request

The requirements for a HTTP GET request to an event collection identifier pattern
resource instance URI.
Table 55. ECIP resource URI: GET request
Element Description
HTTP method GET
Query parameters
oslc:select
Defines the properties of the event
resource that appear in the results of the
HTTP response. This parameter is
equivalent to the column list component
of an SQL SELECT statement.
Request headers
Authorization
Required
Host
Required
Accept application/rdf+xml
Request body Not applicable
Examples http://localhost/objectserver/oslc/ecip/
9999

Related reference:
“Authentication mechanisms” on page 58
Connections to the OSLC interface require a set of Tivoli Netcool/OMNIbus user
credentials for authentication. The only supported authentication scheme is basic
HTTP authentication. If no basic HTTP credentials are provided in the HTTP
Authorization header, a 401 (Not Authorized) HTTP response is returned.
“Event collection identifier pattern resource: GET request” on page 100

54 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Event collection identifier pattern: GET response
The elements of a HTTP GET response to an event collection identifier pattern
resource instance URI.
Table 56. ECIP query capability URI : GET response
Element Description
Response headers
Server
The name of the HTTPd engine.
Date
The date or time of the response.
Connection
The state of the connection. Possible
states are Close or Keep-Alive.
Content-type application/rdf+xml
Normal HTTP response codes 200 (OK): The response body contains the
RDF/XML event resource description of
the event.
Error HTTP response codes 400 (Bad Request): The resource shape
request does not use the type and create
query parameters correctly. One or both
of these parameters are missing from the
request, or the values of the parameters
are invalid.
404 (Not Found): The requested row was
not found in the table because the row
was deleted.
500 (Internal Server Error): The server
failed to complete the request due to an
unexpected internal problem. The
response body contains the RDF/XML
error and more information.

Other common HTTP error response codes

are 401 (Unauthorised), 403 (Forbidden),
and 406 (Not acceptable).

Related reference:
“HTTP response codes” on page 57
The common set of HTTP response codes for an HTTP method from the
ObjectServer OSLC interface.
“Success RDF/XML message payload” on page 58
The OSLC interface returns an RDF/XML success message payload of OSLC type
ResponseInfo.
“Error RDF/XML message payload” on page 59
The OSLC interface might return an RDF/XML error message payload of OSLC
type Error in any nonsuccess response code, such as 500.
“Event collection identifier pattern resource: GET response” on page 100

Chapter 3. ObjectServer OSLC resources 55

56 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Chapter 4. Common behaviors
Characteristics that are common to all requests from, and all responses to the
ObjectServer OSLC interface.

HTTP and HTTPS support

The ObjectServer OSLC interface supports HTTP or HTTPS connectivity at HTTP
1.0 or HTTP 1.1.

HTTP response codes

The common set of HTTP response codes for an HTTP method from the
ObjectServer OSLC interface.

Success message codes

The following table shows the common HTTP success message codes.
Table 57. Common HTTP success message codes
HTTP method HTTP response code Comments
GET 200 (OK)
POST 201 (Created) The HTTP header
Locationcontains the URI for
the newly created resource.
PATCH 200 (OK)
DELETE 200 (OK)

Error message codes

The following table shows the common HTTP error message codes.
Table 58. Common HTTP error message codes
HTTP response code Comments
400 Bad Request. Check the request payload and
query parameters.
401 Not Authorized. The request does not
contain valid authentication credentials.
403 Access to the defined resource is denied. The
authentication credentials that were used to
make the connection are denied access to the
resources that are specified in the request.
404 The requested resource was not found. The
request might be deleted.
406 The requested accept MIME type is not
supported.
415 Specified content MIME type is not
supported.

© Copyright IBM Corp. 1994, 2017 57

 Table 58. Common HTTP error message codes (continued)
HTTP response code Comments
500 Internal server error. For more information,
check the RDF/XML error message payload.

OSLC query parameters

Syntax documentation about the OSLC query parameters that are supported by the
Tivoli Netcool/OMNIbus OSLC interface.
oslc:where
http://open-services.net/bin/view/Main/
OslcSimpleQuerySyntaxV1?sortcol=table;table=up#oslc_where
oslc:select
http://open-services.net/bin/view/Main/
OslcSimpleQuerySyntaxV1?sortcol=table;table=up#oslc_select
oslc:orderBy
http://open-services.net/bin/view/Main/
OslcSimpleQuerySyntaxV1?sortcol=table;table=up#oslc_orderBy

Authentication mechanisms
Connections to the OSLC interface require a set of Tivoli Netcool/OMNIbus user
credentials for authentication. The only supported authentication scheme is basic
HTTP authentication. If no basic HTTP credentials are provided in the HTTP
Authorization header, a 401 (Not Authorized) HTTP response is returned.

Because basic HTTP credentials are insecure, use HTTPS to ensure that the socket
communication is encrypted.

For more information about using SSL to encrypt communications, see the IBM
Tivoli Netcool/OMNIbus Installation and Deployment Guide.

Success RDF/XML message payload

The OSLC interface returns an RDF/XML success message payload of OSLC type
ResponseInfo.

The error message gives details about the server return code failure in Tivoli
Netcool/OMNIbus that relates to the request.

The following table shows the columns that are provided in the success message
payload.
Table 59. Error DCF/XML message payload
Prefixed Represent-
name Occurs Read-only Value ation Description
oslc:id exactly-one true string Not The key field
applicable of the
affected
resource.

58 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 For more information about error message payloads, see the OSLC description at
http://open-services.net/bin/view/Main/OslcCoreVocabulary#Error.
Related reference:
“Example: RDF/XML success message” on page 81

Error RDF/XML message payload

The OSLC interface might return an RDF/XML error message payload of OSLC
type Error in any nonsuccess response code, such as 500.

The following table shows the columns that are provided in the error message
payload.
Table 60. RDF/XML error message payload
Prefixed Represent-
name Occurs Read-only Value ation Description
oslc: zero-or-one true string Not The HTTP
statusCode applicable status code
that is
reported with
the error.
oslc: zero-or-one true string Not A message
message applicable that describes
the error.
oslc: zero-or-one true either Either Extended
extended information
Error (type=
Extended
Error)

Related reference:
“Example: RDF/XML error message” on page 81

Message encryption
Encryption of the message payload is not supported.

Accept MIME types

The accept MIME types supported by the ObjectServer OSLC interface.

The supported MIME types are as follows.

application/rdf+xml (RDF/XML)

Chapter 4. Common behaviors 59

Content MIME types
The content MIME types supported by the ObjectServer OSLC interface.

The supported MIME types are as follows.

application/rdf+xml (RDF/XML)

Response caching
Events in the ObjectServer change constantly as a result of user or programmatic
actions. Because the OSLC interface is hosted directly with the event data, there is
no penalty to access the data. The interface does not cache any data, such as
responses, at any level. Each OSLC request is resolved separately each time in the
same way as any request upon the event data from any of the interfaces of the
ObjectServer.

60 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Appendix A. Property XML name spaces
v “DCTERMS”
v “CRTV”
v “OSLCEM”
v “OSLCEMP”
v “OSLCEMB”
v “OSLCEMM” on page 62

DCTERMS
Prefix dcterms
URI http://purl.org/dc/terms/
Description
Dublin Core Terms as defined by the Dublin Core Metadata Initiative.

CRTV
Prefix crtv
URI http://open-services.net/ns/crtv#
Description
Name space for placeholders for properties that are considered to be
generic to a resource in the ObjectServer OLSC interface.

OSLCEM
Prefix oslcem
URI http://jazz.net/ns/ism/event/omnibus#
Description
Name space for placeholders for properties that are core to, or required for,
Tivoli Netcool/OMNIbus.

OSLCEMP
Prefix oslcemp
URI http://jazz.net/ns/ism/event/omnibus/itnm#
Description
Name space for placeholders for properties that are core to, or required for,
IBM Tivoli Network Manager IP Edition so that this product can work
with Tivoli Netcool/OMNIbus event data.

OSLCEMB
Prefix oslcemb
URI http://jazz.net/ns/ism/event/omnibus/tbsm#
Description
Name space for placeholders for properties that are core to, or required for,
IBM Tivoli Business Service Manager so that this product can work with
Tivoli Netcool/OMNIbus event data.

© Copyright IBM Corp. 1994, 2017 61

 OSLCEMM
Prefix osclemm
URI http://jazz.net/ns/ism/event/omnibus/misc#
Description
Name space for placeholders that do not fit into any other name space. If
you add any columns to the schema, these columns need to be in this
name space.

62 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Appendix B. Sample service provider definition
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<oslc:ServiceProvider rdf:about="http://localhost/objectserver/oslc/services">
<dcterms:title>
IBM Tivoli Netcool/OMNIbus ObjectServer Service Provider – [NCOMS]
</dcterms:title>
<dcterms:description>
Reference Implementation OSLC for Event Management Service Document
</dcterms:description>
<dcterms:publisher>
<oslc:Publisher>
<dcterms:title>
Open Services for Lifecycle Collaboration in Event Management
</dcterms:title>
<dcterms:identifier>ibm.com/software/tivoli/oslc/em</dcterms:identifier>
<oslc:label>OSLC Event Management</oslc:label>
<oslc:icon rdf:resource="http://localhost/images/tivoli.png"/>
</oslc:Publisher>
</dcterms:publisher>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>rdf</oslc:prefix>
<oslc:prefixBase rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>oslc</oslc:prefix>
<oslc:prefixBase rdf:resource="http://open-services.net/ns/core#"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>dcterms</oslc:prefix>
<oslc:prefixBase rdf:resource="http://purl.org/dc/terms/"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>rdfs</oslc:prefix>
<oslc:prefixBase rdf:resource="http://www.w3.org/2000/01/rdf-schema#"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>foaf</oslc:prefix>
<oslc:prefixBase rdf:resource="http://xmlns.com/foaf/0.1/"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>crtv</oslc:prefix>
<oslc:prefixBase rdf:resource="http://open-services.net/ns/crtv#"/>

© Copyright IBM Corp. 1994, 2017 63

 </oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>oslcem</oslc:prefix>
<oslc:prefixBase rdf:resource="http://jazz.net/ns/ism/event/omnibus#"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>oslcemp</oslc:prefix>
<oslc:prefixBase rdf:resource="http://jazz.net/ns/ism/event/omnibus/itnm#"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>oslcemb</oslc:prefix>
<oslc:prefixBase rdf:resource="http://jazz.net/ns/ism/event/omnibus/tbsm#"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>oslcemm</oslc:prefix>
<oslc:prefixBase rdf:resource="http://jazz.net/ns/ism/event/omnibus/misc#"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>
<oslc:service>
<oslc:Service>
<oslc:domain rdf:resource="http://tivoli-OSLC-prototype:80/ns/oslcem/1.0/#"/>
<oslc:creationFactory>
<oslc:CreationFactory>
<dcterms:title>EM Event Creation Factory</dcterms:title>
<oslc:label>Event Factory</oslc:label>
<oslc:creation
rdf:resource="http://localhost/objectserver/oslc/factory/event"/>
<oslc:resourceShape
rdf:resource="http://localhost/objectserver/oslc/shape?
type=event&amp;create=true"/>
<oslc:resourceType
rdf:resource="http://tivoli-OSLC-prototype:80/ns/oslcem/1.0/#event"/>
<oslc:usage rdf:resource="http://open-services.net:80/ns/core#default"/>
</oslc:CreationFactory>
</oslc:creationFactory>
<oslc:creationFactory>
<oslc:CreationFactory>
<dcterms:title>EM Journal Creation Factory</dcterms:title>
<oslc:label>Journal Factory</oslc:label>
<oslc:creation
rdf:resource="http://localhost/objectserver/oslc/factory/journal"/>
<oslc:resourceShape
rdf:resource="http://localhost/objectserver/oslc/shape?
type=journal&amp;create=true"/>
<oslc:resourceType
rdf:resource="http://tivoli-OSLC-prototype:80/ns/oslcem/1.0/#journal"/>
<oslc:usage
rdf:resource="http://open-services.net:80/ns/core#default"/>
</oslc:CreationFactory>
</oslc:creationFactory>
<oslc:creationFactory>
<oslc:CreationFactory>
<dcterms:title>EM Detail Creation Factory</dcterms:title>
<oslc:label>Detail Factory</oslc:label>
<oslc:creation
rdf:resource="http://localhost/objectserver/oslc/factory/detail"/>
<oslc:resourceShape
rdf:resource="http://localhost/objectserver/oslc/shape?
type=detail&amp;create=true"/>

64 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 <oslc:resourceType rdf:resource="http://tivoli-OSLCprototype:
80/ns/oslcem/1.0/#detail"/>
<oslc:usage rdf:resource="http://open-services.net:80/ns/core#default"/>
</oslc:CreationFactory>
</oslc:creationFactory>
<oslc:queryCapability>
<oslc:QueryCapability>
<dcterms:title>EM Event Query Capability</dcterms:title>
<oslc:label>Event Query</oslc:label>
<oslc:queryBase
rdf:resource="http://localhost/objectserver/oslc/query/events"/>
<oslc:resourceShape
rdf:resource="http://localhost/objectserver/oslc/shape?
type=event&amp;create=false"/>
<oslc:resourceType
rdf:resource="http://tivoli-OSLC-prototype:80/ns/oslcem/1.0/#event"/>
<oslc:usage rdf:resource="http://open-services.net:80/ns/core#default"/>
</oslc:QueryCapability>
</oslc:queryCapability>
<oslc:queryCapability>
<oslc:QueryCapability>
<dcterms:title>EM Journal Query Capability</dcterms:title>
<oslc:label>Journal Query</oslc:label>
<oslc:queryBase
rdf:resource="http://localhost/objectserver/oslc/query/journals"/>
<oslc:resourceShape
rdf:resource="http://localhost/objectserver/oslc/shape?
type=journal&amp;create=false"/>
<oslc:resourceType
rdf:resource="http://tivoli-OSLC-prototype:80/ns/oslcem/1.0/#journal"/>
<oslc:usage rdf:resource="http://open-services.net:80/ns/core#default"/>
</oslc:QueryCapability>
</oslc:queryCapability>
<oslc:queryCapability>
<oslc:QueryCapability>
<dcterms:title>EM Detail Query Capability</dcterms:title>
<oslc:label>Detail Query</oslc:label>
<oslc:queryBase
rdf:resource="http://localhost/objectserver/oslc/query/details"/>
<oslc:resourceShape
rdf:resource="http://localhost/objectserver/oslc/shape?
type=detail&amp;create=false"/>
<oslc:resourceType
rdf:resource="http://tivoli-OSLC-prototype:80/ns/oslcem/1.0/#detail"/>
<oslc:usage rdf:resource="http://open-services.net:80/ns/core#default"/>
</oslc:QueryCapability>
</oslc:queryCapability>
</oslc:Service>
</oslc:service>
</oslc:ServiceProvider>
</rdf:RDF>

Appendix B. Sample service provider definition 65

66 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Appendix C. Examples: Resource RDF/XML payloads
Example: Event
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/3576%2BNCOMS">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#event"/>
<dcterms:identifier>JUnitEventTestInstance@@@@0</dcterms:identifier>
<dcterms:created>2012-05-18T14:46:54</dcterms:created>
<dcterms:creator rdf:resource="http://localhost/objectserver/oslc/user/501"/>
<crtv:severity>4</crtv:severity>
<crtv:summary>This is a test event generated by the JUnit OSLC Event Tests.
(0)</crtv:summary>
<crtv:node>localhost</crtv:node>
<crtv:agent>createEventNew()</crtv:agent>
<crtv:alertGroup></crtv:alertGroup>
<crtv:lastOccurrence>2012-05-18T14:46:54</crtv:lastOccurrence>
<crtv:tally>1</crtv:tally>
<crtv:acknowledged>false</crtv:acknowledged>
<oslcem:serial>3576</oslcem:serial>
<oslcem:serverSerial>3576</oslcem:serverSerial>
<oslcem:serverName>NCOMS</oslcem:serverName>
<oslcem:alertKey>JUnitEventInstance</oslcem:alertKey>
<oslcem:manager>com.ibm.netcool.omnibus.ws.junit.rest.oslc.v1.utils.
ResourceEven</oslcem:manager>
<oslcem:stateChange>2012-05-18T13:46:54</oslcem:stateChange>
<oslcem:internalLast>2012-05-18T13:46:54</oslcem:internalLast>
<oslcem:type>1</oslcem:type>
<oslcem:class>0</oslcem:class>
<oslcem:grade>0</oslcem:grade>
<oslcem:ownerGID rdf:resource="http://localhost/objectserver/oslc/group/0"/>
<oslcem:taskList>0</oslcem:taskList>
<oslcem:suppressEscl>0</oslcem:suppressEscl>
<oslcem:flash>0</oslcem:flash>
<oslcem:expireTime>0</oslcem:expireTime>
<oslcem:customer></oslcem:customer>
<oslcem:service></oslcem:service>
<oslcem:probeSubSecondId>0</oslcem:probeSubSecondId>
<oslcem:journal rdf:resource="http://localhost/objectserver/oslc/query/journals?
oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial%3D3576%20and%20oslcem%3AserverName
%3D%22NCOMS%22%7D&amp;oslc.orderBy=dcterms%3Acreated"/>
<oslcem:detail rdf:resource="http://localhost/objectserver/oslc/query/details?
oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial%3D3576%20and%20oslcem%3AserverName
%3D%22NCOMS%22%7D&amp;oslc.orderBy=oslcem%3Asequence"/>
<oslcemp:eventId></oslcemp:eventId>
<oslcemp:processReq>0</oslcemp:processReq>
<oslcemp:nmosSerial></oslcemp:nmosSerial>
<oslcemp:nmosObjInst>0</oslcemp:nmosObjInst>
<oslcemp:nmosCauseType>0</oslcemp:nmosCauseType>
<oslcemp:nmosDomainName></oslcemp:nmosDomainName>
<oslcemp:nmosEntityId>0</oslcemp:nmosEntityId>
<oslcemp:nmosManagedStatus>0</oslcemp:nmosManagedStatus>
<oslcemp:nmosEventMap></oslcemp:nmosEventMap>
<oslcemp:localNodeAlias></oslcemp:localNodeAlias>

© Copyright IBM Corp. 1994, 2017 67

 <oslcemp:localPriObj></oslcemp:localPriObj>
<oslcemp:localSecObj></oslcemp:localSecObj>
<oslcemp:localRootObj></oslcemp:localRootObj>
<oslcemp:remoteNodeAlias></oslcemp:remoteNodeAlias>
<oslcemp:remotePriObj></oslcemp:remotePriObj>
<oslcemp:remoteSecObj></oslcemp:remoteSecObj>
<oslcemp:remoteRootObj></oslcemp:remoteRootObj>
<oslcemb:bsmIdentity></oslcemb:bsmIdentity>
<oslcemm:poll>0</oslcemm:poll>
<oslcemm:location>NOT UPDATED</oslcemm:location>
<oslcemm:physicalSlot>0</oslcemm:physicalSlot>
<oslcemm:physicalPort>0</oslcemm:physicalPort>
<oslcemm:physicalCard></oslcemm:physicalCard>
<oslcemm:x733EventType>0</oslcemm:x733EventType>
<oslcemm:x733ProbableCause>0</oslcemm:x733ProbableCause>
<oslcemm:x733SpecificProb></oslcemm:x733SpecificProb>
<oslcemm:x733CorrNotif></oslcemm:x733CorrNotif>
<oslcemm:url
rdf:resource="http://localhost/objectserver/restapi/v1/
alerts/status"/>
<oslcemm:extendedAttr></oslcemm:extendedAttr>
<oslcemm:oldRow>0</oslcemm:oldRow>
</rdf:Description>
</rdf:RDF>
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/3576%2BNCOMS">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Event"/>
<dcterms:identifier>JUnitEventTestInstance@@@@0</dcterms:identifier>
<dcterms:created>2012-05-18T14:46:54</dcterms:created>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/501"/>
<oslcem:severity>4</oslcem:severity>
<oslcem:summary>This is a test event generated by the JUnit OSLC Event Tests.
(0)</oslcem:summary>
<oslcem:node>localhost</oslcem:node>
<oslcem:agent>createEventNew()</oslcem:agent>
<oslcem:alertGroup></oslcem:alertGroup>
<oslcem:lastOccurrence>2012-05-18T14:46:54</oslcem:lastOccurrence>
<oslcem:tally>1</oslcem:tally>
<oslcem:acknowledged>false</oslcem:acknowledged>
<oslcem:serial>3576</oslcem:serial>
<oslcem:serverSerial>3576</oslcem:serverSerial>
<oslcem:serverName>NCOMS</oslcem:serverName>
<oslcem:alertKey>JUnitEventInstance</oslcem:alertKey>
<oslcem:manager>com.ibm.netcool.omnibus.ws.junit.rest.oslc.v1.utils.
ResourceEven</oslcem:manager>
<oslcem:stateChange>2012-05-18T13:46:54</oslcem:stateChange>
<oslcem:internalLast>2012-05-18T13:46:54</oslcem:internalLast>
<oslcem:type>1</oslcem:type>
<oslcem:class>0</oslcem:class>
<oslcem:grade>0</oslcem:grade>
<oslcem:ownerGID rdf:resource="http://localhost/objectserver/oslc/group/0"/>
<oslcem:taskList>0</oslcem:taskList>
<oslcem:suppressEscl>0</oslcem:suppressEscl>
<oslcem:flash>0</oslcem:flash>
<oslcem:expireTime>0</oslcem:expireTime>
<oslcem:customer></oslcem:customer>
<oslcem:service></oslcem:service>
<oslcem:probeSubSecondId>0</oslcem:probeSubSecondId>

68 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 <oslcem:journal rdf:resource="http://localhost/objectserver/oslc/query/
journals?oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial%3D3576%20and
%20oslcem%3AserverName%3D%22NCOMS%22%7D&amp;
oslc.orderBy=dcterms%3Acreated"/>
<oslcem:detail rdf:resource="http://localhost/objectserver/oslc/query/details?
oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial
%3D3576%20and%20oslcem%3AserverName%3D%22NCOMS%22%7D&
amp;oslc.orderBy=oslcem%3Asequence"/>
<oslcemp:eventId></oslcemp:eventId>
<oslcemp:processReq>0</oslcemp:processReq>
<oslcemp:nmosSerial></oslcemp:nmosSerial>
<oslcemp:nmosObjInst>0</oslcemp:nmosObjInst>
<oslcemp:nmosCauseType>0</oslcemp:nmosCauseType>
<oslcemp:nmosDomainName></oslcemp:nmosDomainName>
<oslcemp:nmosEntityId>0</oslcemp:nmosEntityId>
<oslcemp:nmosManagedStatus>0</oslcemp:nmosManagedStatus>
<oslcemp:nmosEventMap></oslcemp:nmosEventMap>
<oslcemp:localNodeAlias></oslcemp:localNodeAlias>
<oslcemp:localPriObj></oslcemp:localPriObj>
<oslcemp:localSecObj></oslcemp:localSecObj>
<oslcemp:localRootObj></oslcemp:localRootObj>
<oslcemp:remoteNodeAlias></oslcemp:remoteNodeAlias>
<oslcemp:remotePriObj></oslcemp:remotePriObj>
<oslcemp:remoteSecObj></oslcemp:remoteSecObj>
<oslcemp:remoteRootObj></oslcemp:remoteRootObj>
<oslcemb:bsmIdentity></oslcemb:bsmIdentity>
<oslcemm:poll>0</oslcemm:poll>
<oslcemm:location>NOT UPDATED</oslcemm:location>
<oslcemm:physicalSlot>0</oslcemm:physicalSlot>
<oslcemm:physicalPort>0</oslcemm:physicalPort>
<oslcemm:physicalCard></oslcemm:physicalCard>
<oslcemm:x733EventType>0</oslcemm:x733EventType>
<oslcemm:x733ProbableCause>0</oslcemm:x733ProbableCause>
<oslcemm:x733SpecificProb></oslcemm:x733SpecificProb>
<oslcemm:x733CorrNotif></oslcemm:x733CorrNotif>
<oslcemm:url rdf:resource="http://localhost/objectserver/restapi/v1/
alerts/status"/>
<oslcemm:extendedAttr></oslcemm:extendedAttr>
<oslcemm:oldRow>0</oslcemm:oldRow>
</rdf:Description>
</rdf:RDF>

Example: Event creation

This example creates an event and sets various properties.
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<rdf:Description rdf:about="http://localhost/">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Event"/>
<dcterms:identifier>JUnitEventTestInstance@@@@0</dcterms:identifier>
<dcterms:created>2012-05-18T13:46:54</dcterms:created>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/501"/>
<oslcem:severity>4</oslcem:severity>
<oslcem:summary>This is a test event generated by the JUnit OSLC Event Tests.
(0)</oslcem:summary>
<oslcem:node>localhost</oslcem:node>
<oslcem:agent>createEventNew()</oslcem:agent>
<oslcem:lastOccurrence>2012-05-18T13:46:54</oslcem:lastOccurrence>

Appendix C. Examples: Resource RDF/XML payloads 69

 <oslcem:acknowledged>false</oslcem:acknowledged>
<oslcem:alertKey>JUnitEventInstance</oslcem:alertKey>
<oslcem:manager>com.ibm.netcool.omnibus.ws.junit.rest.oslc.v1.utils.
ResourceEvent</oslcem:manager>
<oslcem:type>1</oslcem:type>
<oslcem:ownerGID rdf:resource="http://localhost/objectserver/oslc/group/0"/>
<oslcemm:location>NOT UPDATED</oslcemm:location>
<oslcemm:url rdf:resource="http://localhost/objectserver/restapi/v1/alerts/
status"/>
</rdf:Description>
</rdf:RDF>

Example: Event PATCH

This example updates the creator, lastOccurence, acknowledged, ownerGID and
location properties.
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/
3576%2BNCOMS">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Event"/>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/
65534"/>
<oslcem:lastOccurrence>2012-05-18T13:47:10</oslcem:lastOccurrence>
<oslcem:acknowledged>false</oslcem:acknowledged>
<oslcem:ownerGID rdf:resource="http://localhost/objectserver/oslc/group/1"/>
<oslcemm:location>UPDATED</oslcemm:location>
</rdf:Description>
</rdf:RDF>

Example: Event query result

The result message from the query capability is nonstandard but optimized to
prevent unnecessary repetitive fetches of individual events. When a query is
resolved, the OSLC interface has all of the events already. Consequently, in
addition to generating a ResponseInfo section detailing the members of the result,
the message also provides all of the requested properties of the events in the
response too.
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/query/events">
<dcterms:title>Event Service Query Results</dcterms:title>
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3576%2BNCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3577%2BNCOMS"/>

70 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3578%2BNCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3579%2BNCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3580%2BNCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3581%2BNCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3582%2BNCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3583%2BNCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3584%2BNCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
3585%2BNCOMS"/>
</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/
3576%2BNCOMS">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Event"/>
<dcterms:identifier>JUnitEventTestInstance@@@@0</dcterms:identifier>
<dcterms:created>2012-05-18T14:46:54</dcterms:created>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/
user/501"/>
<oslcem:severity>4</oslcem:severity>
<oslcem:summary>This is a test event generated by the JUnit OSLC Event Tests.
(0)</oslcem:summary>
<oslcem:node>localhost</oslcem:node>
<oslcem:agent>createEventNew()</oslcem:agent>
<oslcem:alertGroup></oslcem:alertGroup>
<oslcem:lastOccurrence>2012-05-18T14:46:54</oslcem:lastOccurrence>
<oslcem:tally>1</oslcem:tally>
<oslcem:acknowledged>false</oslcem:acknowledged>
<oslcem:serial>3576</oslcem:serial>
<oslcem:serverSerial>3576</oslcem:serverSerial>
<oslcem:serverName>NCOMS</oslcem:serverName>
<oslcem:alertKey>JUnitEventInstance</oslcem:alertKey>
<oslcem:manager>com.ibm.netcool.omnibus.ws.junit.rest.oslc.v1.utils.
ResourceEven</oslcem:manager>
<oslcem:stateChange>2012-05-18T13:46:54</oslcem:stateChange>
<oslcem:internalLast>2012-05-18T13:46:54</oslcem:internalLast>
<oslcem:type>1</oslcem:type>
<oslcem:class>0</oslcem:class>
<oslcem:grade>0</oslcem:grade>
<oslcem:ownerGID rdf:resource="http://localhost/objectserver/oslc/group/0"/>
<oslcem:taskList>0</oslcem:taskList>
<oslcem:suppressEscl>0</oslcem:suppressEscl>
<oslcem:flash>0</oslcem:flash>
<oslcem:expireTime>0</oslcem:expireTime>
<oslcem:customer></oslcem:customer>
<oslcem:service></oslcem:service>
<oslcem:probeSubSecondId>0</oslcem:probeSubSecondId>
<oslcem:journal rdf:resource="http://localhost/objectserver/oslc/query/
journals?oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial%3D3576%20and%20oslcem
%3AserverName
%3D%22NCOMS%22%7D&amp;oslc.orderBy=dcterms%3Acreated"/>
<oslcem:detail rdf:resource="http://localhost/objectserver/oslc/query/
details?oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial%3D3576%20and%20oslcem
%3AserverName
%3D%22NCOMS%22%7D&amp;oslc.orderBy=oslcem%3Asequence"/>
<oslcemp:eventId></oslcemp:eventId>
<oslcemp:processReq>0</oslcemp:processReq>
<oslcemp:nmosSerial></oslcemp:nmosSerial>
<oslcemp:nmosObjInst>0</oslcemp:nmosObjInst>
<oslcemp:nmosCauseType>0</oslcemp:nmosCauseType>
<oslcemp:nmosDomainName></oslcemp:nmosDomainName>

Appendix C. Examples: Resource RDF/XML payloads 71

 <oslcemp:nmosEntityId>0</oslcemp:nmosEntityId>
<oslcemp:nmosManagedStatus>0</oslcemp:nmosManagedStatus>
<oslcemp:nmosEventMap></oslcemp:nmosEventMap>
<oslcemp:localNodeAlias></oslcemp:localNodeAlias>
<oslcemp:localPriObj></oslcemp:localPriObj>
<oslcemp:localSecObj></oslcemp:localSecObj>
<oslcemp:localRootObj></oslcemp:localRootObj>
<oslcemp:remoteNodeAlias></oslcemp:remoteNodeAlias>
<oslcemp:remotePriObj></oslcemp:remotePriObj>
<oslcemp:remoteSecObj></oslcemp:remoteSecObj>
<oslcemp:remoteRootObj></oslcemp:remoteRootObj>
<oslcemb:bsmIdentity></oslcemb:bsmIdentity>
<oslcemm:poll>0</oslcemm:poll>
<oslcemm:location>NOT UPDATED</oslcemm:location>
<oslcemm:physicalSlot>0</oslcemm:physicalSlot>
<oslcemm:physicalPort>0</oslcemm:physicalPort>
<oslcemm:physicalCard></oslcemm:physicalCard>
<oslcemm:x733EventType>0</oslcemm:x733EventType>
<oslcemm:x733ProbableCause>0</oslcemm:x733ProbableCause>
<oslcemm:x733SpecificProb></oslcemm:x733SpecificProb>
<oslcemm:x733CorrNotif></oslcemm:x733CorrNotif>
<oslcemm:url rdf:resource="http://localhost/objectserver/restapi/v1/
alerts/status"/>
<oslcemm:extendedAttr></oslcemm:extendedAttr>
<oslcemm:oldRow>0</oslcemm:oldRow>
</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/
3577%2BNCOMS">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/
omnibus#Event"/>

*** CONTENTS STRIPPED TO IMPROVE UNDERSTANDING ***

</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/
3585%2BNCOMS">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Event"/>
<dcterms:identifier>JUnitEventTestInstance@@@@9</dcterms:identifier>
<dcterms:created>2012-05-18T14:46:54</dcterms:created>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/
501"/>
<oslcem:severity>4</oslcem:severity>
<oslcem:summary>This is a test event generated by the JUnit OSLC Event Tests.
(9)</oslcem:summary>
<oslcem:node>localhost</oslcem:node>
<oslcem:agent>createEventNew()</oslcem:agent>
<oslcem:alertGroup></oslcem:alertGroup>
<oslcem:lastOccurrence>2012-05-18T14:46:54</oslcem:lastOccurrence>
<oslcem:tally>1</oslcem:tally>
<oslcem:acknowledged>false</oslcem:acknowledged>
<oslcem:serial>3585</oslcem:serial>
<oslcem:serverSerial>3585</oslcem:serverSerial>
<oslcem:serverName>NCOMS</oslcem:serverName>
<oslcem:alertKey>JUnitEventInstance</oslcem:alertKey>
<oslcem:manager>com.ibm.netcool.omnibus.ws.junit.rest.oslc.v1.utils.
ResourceEven</oslcem:manager>
<oslcem:stateChange>2012-05-18T13:46:59</oslcem:stateChange>
<oslcem:internalLast>2012-05-18T13:46:59</oslcem:internalLast>
<oslcem:type>1</oslcem:type>
<oslcem:class>0</oslcem:class>
<oslcem:grade>0</oslcem:grade>
<oslcem:ownerGID rdf:resource="http://localhost/objectserver/oslc/group/0"/>
<oslcem:taskList>0</oslcem:taskList>
<oslcem:suppressEscl>0</oslcem:suppressEscl>
<oslcem:flash>0</oslcem:flash>

72 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 <oslcem:expireTime>0</oslcem:expireTime>
<oslcem:customer></oslcem:customer>
<oslcem:service></oslcem:service>
<oslcem:probeSubSecondId>0</oslcem:probeSubSecondId>
<oslcem:journal rdf:resource="http://localhost/objectserver/oslc/query/
journals?oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial%3D3585%20and%20
oslcem%3AserverName%3D%22NCOMS%22%7D&amp;oslc.orderBy=dcterms%3Acreated"/>
<oslcem:detail rdf:resource="http://localhost/objectserver/oslc/query/
details?oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial%3D3585%20and%20
oslcem%3AserverName%3D%22NCOMS%22%7D&amp;oslc.orderBy=oslcem%3Asequence"/>
<oslcemp:eventId></oslcemp:eventId>
<oslcemp:processReq>0</oslcemp:processReq>
<oslcemp:nmosSerial></oslcemp:nmosSerial>
<oslcemp:nmosObjInst>0</oslcemp:nmosObjInst>
<oslcemp:nmosCauseType>0</oslcemp:nmosCauseType>
<oslcemp:nmosDomainName></oslcemp:nmosDomainName>
<oslcemp:nmosEntityId>0</oslcemp:nmosEntityId>
<oslcemp:nmosManagedStatus>0</oslcemp:nmosManagedStatus>
<oslcemp:nmosEventMap></oslcemp:nmosEventMap>
<oslcemp:localNodeAlias></oslcemp:localNodeAlias>
<oslcemp:localPriObj></oslcemp:localPriObj>
<oslcemp:localSecObj></oslcemp:localSecObj>
<oslcemp:localRootObj></oslcemp:localRootObj>
<oslcemp:remoteNodeAlias></oslcemp:remoteNodeAlias>
<oslcemp:remotePriObj></oslcemp:remotePriObj>
<oslcemp:remoteSecObj></oslcemp:remoteSecObj>
<oslcemp:remoteRootObj></oslcemp:remoteRootObj>
<oslcemb:bsmIdentity></oslcemb:bsmIdentity>
<oslcemm:poll>0</oslcemm:poll>
<oslcemm:location>NOT UPDATED</oslcemm:location>
<oslcemm:physicalSlot>0</oslcemm:physicalSlot>
<oslcemm:physicalPort>0</oslcemm:physicalPort>
<oslcemm:physicalCard></oslcemm:physicalCard>
<oslcemm:x733EventType>0</oslcemm:x733EventType>
<oslcemm:x733ProbableCause>0</oslcemm:x733ProbableCause>
<oslcemm:x733SpecificProb></oslcemm:x733SpecificProb>
<oslcemm:x733CorrNotif></oslcemm:x733CorrNotif>
<oslcemm:url rdf:resource="http://localhost/objectserver/restapi/v1/
alerts/status"/>
<oslcemm:extendedAttr></oslcemm:extendedAttr>
<oslcemm:oldRow>0</oslcemm:oldRow>
</rdf:Description>
</rdf:RDF>

Example: Journal
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/journal/
3576%3A0%3A1337348819">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<dcterms:identifier>3576:0:1337348819</dcterms:identifier>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/0"/>
<dcterms:created>2012-05-18T14:46:59</dcterms:created>
<dcterms:content>
This is a test journal generated by the JUnit OSLC Journal Tests.
</dcterms:content>

Appendix C. Examples: Resource RDF/XML payloads 73

 <oslcem:event
rdf:resource="http://localhost/objectserver/oslc/event/3576%2BNCOMS"/>
</rdf:Description>
</rdf:RDF>

Example: Journal PATCH

This example updates the journal text.
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description
rdf:about="http://localhost/objectserver/oslc/journal/
3576%3A0%3A1337348819">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<dcterms:content>
This is a test journal generated by the JUnit OSLC Journal Tests.
*********** UPDATED JOURNAL ENTRY **************
</dcterms:content>
</rdf:Description>
</rdf:RDF>

Example: Journal creation

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/0"/>
<dcterms:created>2012-05-18T13:46:59</dcterms:created>
<dcterms:content>
This is a test journal generated by the JUnit OSLC Journal Tests.
</dcterms:content>
<oslcem:event
rdf:resource="http://localhost/objectserver/oslc/event/3576%2BNCOMS"/>
</rdf:Description>
</rdf:RDF>

Example: Journal query result

The result message from the query capability is nonstandard but optimized to
prevent unnecessary repetitive fetches of individual journals. When a query is
resolved, the OSLC interface has all of the journals already. Consequently, in
addition to generating a ResponseInfo section detailing the members of the result,
the message provides all the requested properties of the journals in the response.
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/query/journals">
<dcterms:title>Journal Service Query Results</dcterms:title>

74 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 <rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3580%3A0%3A1337348819"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3583%3A0%3A1337348819"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3584%3A0%3A1337348819"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3581%3A0%3A1337348819"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3582%3A0%3A1337348819"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3585%3A0%3A1337348819"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3577%3A0%3A1337348819"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3578%3A0%3A1337348819"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3576%3A0%3A1337348819"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/journal/
3579%3A0%3A1337348819"/>
</rdf:Description>

<rdf:Description
rdf:about="http://localhost/objectserver/oslc/journal/
3580%3A0%3A1337348819">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<dcterms:identifier>3580:0:1337348819</dcterms:identifier>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/0"/>
<dcterms:created>2012-05-18T14:46:59</dcterms:created>
<dcterms:content>
This is a test journal generated by the JUnit OSLC Journal Tests.
</dcterms:content>
<oslcem:event
rdf:resource="http://localhost/objectserver/oslc/event/3580%2BNCOMS"/>
</rdf:Description>

<rdf:Description
rdf:about="http://localhost/objectserver/oslc/journal/3583%3A0%3A1337348819">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>

** CONTENTS STRIPPED TO IMPROVE UNDERSTANDING **

</rdf:Description>

<rdf:Description
rdf:about="http://localhost/objectserver/oslc/journal/
3579%3A0%3A1337348819">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<dcterms:identifier>3579:0:1337348819</dcterms:identifier>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/0"/>
<dcterms:created>2012-05-18T14:46:59</dcterms:created>
<dcterms:content>
This is a test journal generated by the JUnit OSLC Journal Tests.
</dcterms:content>
<oslcem:event

Appendix C. Examples: Resource RDF/XML payloads 75

 rdf:resource="http://localhost/objectserver/oslc/event/
3579%2BNCOMS"/>
</rdf:Description>
</rdf:RDF>

Example: Detail
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description
rdf:about="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%400%23%23%23%230">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<dcterms:identifier>JUnitEventTestInstance@@@@0####0</dcterms:identifier>
<oslcem:attrValue>true</oslcem:attrValue>
<oslcem:sequence>0</oslcem:sequence>
<oslcem:detailName>EventDetail0</oslcem:detailName>
<oslcem:detailValue>
This is a test detail generated by the JUnit OSLC Detail Tests.
</oslcem:detailValue>
<oslcem:event
rdf:resource="http://localhost/objectserver/oslc/event/
3576%2BNCOMS"/>
</rdf:Description>
</rdf:RDF>

Example: Detail PATCH

This example updates the detail property of the resource.
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description
rdf:about="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%400%23%23%23%230">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<oslcem:detailValue>
This is a test detail generated by the JUnit OSLC Detail Tests.
*********** UPDATED DETAIL ENTRY **************
</oslcem:detailValue>
</rdf:Description>
</rdf:RDF>

76 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Example: Detail creation
<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<oslcem:attrValue>true</oslcem:attrValue>
<oslcem:sequence>0</oslcem:sequence>
<oslcem:detailName>EventDetail0</oslcem:detailName>
<oslcem:detailValue>
This is a test detail generated by the JUnit OSLC Detail Tests.
</oslcem:detailValue>
<oslcem:event
rdf:resource="http://localhost/objectserver/oslc/event/3576%2BNCOMS"/>
</rdf:Description>
</rdf:RDF>

Example: Detail query result

The result message from the query capability is nonstandard but optimized to
prevent unnecessary repetitive fetches of individual details. When a query is
resolved the OSLC interface has all of the details already. Consequently, in addition
to generating a ResponseInfo section that details the members of the result, the
message provides all the requested properties of the details in the response.
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/query/details">
<dcterms:title>Detail Service Query Results</dcterms:title>
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%404%23%23%23%234"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%408%23%23%23%238"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%402%23%23%23%232"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%406%23%23%23%236"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%400%23%23%23%230"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%405%23%23%23%235"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%409%23%23%23%239"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%403%23%23%23%233"/>
<rdfs:member
rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%407%23%23%23%237"/>
<rdfs:member

Appendix C. Examples: Resource RDF/XML payloads 77

 rdf:resource="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%401%23%23%23%231"/>
</rdf:Description>

<rdf:Description
rdf:about="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%404%23%23%23%234">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<dcterms:identifier>JUnitEventTestInstance@@@@4####4</dcterms:identifier>
<oslcem:attrValue>true</oslcem:attrValue>
<oslcem:sequence>4</oslcem:sequence>
<oslcem:detailName>EventDetail4</oslcem:detailName>
<oslcem:detailValue>
This is a test detail generated by the JUnit OSLC Detail Tests.
</oslcem:detailValue>
<oslcem:event
rdf:resource="http://localhost/objectserver/oslc/event/3580%2BNCOMS"/>
</rdf:Description>

<rdf:Description
rdf:about="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%408%23%23%23%238">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>

*** CONTENTS STRIPPED TO IMPROVE UNDERSTANDING ***

</rdf:Description>
<rdf:Description
rdf:about="http://localhost/objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%401%23%23%23%231">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<dcterms:identifier>JUnitEventTestInstance@@@@1####1</dcterms:identifier>
<oslcem:attrValue>true</oslcem:attrValue>
<oslcem:sequence>1</oslcem:sequence>
<oslcem:detailName>EventDetail1</oslcem:detailName>
<oslcem:detailValue>
This is a test detail generated by the JUnit OSLC Detail Tests.
</oslcem:detailValue>
<oslcem:event
rdf:resource="http://localhost/objectserver/oslc/event/3577%2BNCOMS"/>
</rdf:Description>
</rdf:RDF>

Example: Event Collection Identifier Pattern

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:rr="http://jazz.net/ns/ism/registry#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/ecip/2190">
<rdf:type
rdf:resource="http://jazz.net/ns/ism/event/omnibus#CollectionIdentifierPattern"/>
<oslc:resourceType
rdf:resource="http://open-services.net/ns/crtv#ComputerSystem"/>
<dcterms:title>JUnitQP01</dcterms:title>
<dcterms:description>The event collection identifier pattern for a
ComputerSystem resource.</dcterms:description>
<oslcem:clause>Node=’@http://open-services.net/ns/crtv#fqdn’
</oslcem:clause>

78 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 <rr:uriTemplate>
<rr:URITemplate>
<rr:uriPattern>http://localhost/objectserver/oslc/query/
events?oslc.where=oslcem%3Anode+in+%5B{crtv_fqdn}%5D</rr:uriPattern>
<rr:uriTemplateVariable>
<rr:URITemplateVariable>
<oslc:name>crtv_fqdn</oslc:name>
<rdf:value>"{http://open-services.net/ns/crtv#fqdn}"</rdf:value>
</rr:URITemplateVariable>
</rr:uriTemplateVariable>
</rr:URITemplate>
</rr:uriTemplate>
</rdf:Description>
</rdf:RDF>

Example: Event Collection Identifier Pattern response

The result message from the query capability is nonstandard but optimized to
prevent unnecessary repetitive fetches of individual event collection identifier
patterns. When a query is resolved, the OSLC interface has all the event collection
identifier patterns already. Consequently, in addition to generating a collection
block detailing the members of the result, the message provides all the requested
properties of the events in the response.
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:rr="http://jazz.net/ns/ism/registry#">
<oslc:ResponseInfo rdf:about="http://localhost/objectserver/oslc/query/ecips">
<dcterms:title>Event Collection Identifier Pattern Service Query Results
</dcterms:title>
</oslc:ResponseInfo>
<rdf:Description rdf:about="http://localhost/objectserver/oslc/query/ecips">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Collection"/>
<rdf:type rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/ecip/2190"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/ecip/2191"/>
</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/ecip/2190">
<rdf:type
rdf:resource="http://jazz.net/ns/ism/event/omnibus#CollectionIdentifierPattern"/>
<oslc:resourceType
rdf:resource="http://open-services.net/ns/crtv#ComputerSystem"/>
<dcterms:title>JUnitQP01</dcterms:title>
<dcterms:description>The event collection identifier pattern for a
ComputerSystem resource.</dcterms:description>
<oslcem:clause>Node=’@http://open-services.net/ns/crtv#fqdn’</oslcem:clause>
<rr:uriTemplate>
<rr:URITemplate>
<rr:uriPattern>http://localhost/objectserver/oslc/query/
events?oslc.where=oslcem%3Anode+in+%5B{crtv_fqdn}%5D</rr:uriPattern>
<rr:uriTemplateVariable>
<rr:URITemplateVariable>
<oslc:name>crtv_fqdn</oslc:name>
<rdf:value>"{http://open-services.net/ns/crtv#fqdn}"</rdf:value>
</rr:URITemplateVariable>
</rr:uriTemplateVariable>

Appendix C. Examples: Resource RDF/XML payloads 79

 </rr:URITemplate>
</rr:uriTemplate>
</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/ecip/2191">
<rdf:type
rdf:resource="http://jazz.net/ns/ism/event/omnibus#CollectionIdentifierPattern"/>
<oslc:resourceType rdf:resource="http://open-services.net/ns/crtv#QP02"/>
<dcterms:title>JUnitQP02</dcterms:title>
<dcterms:description>The event collection identifier pattern for a QP02
resource.</dcterms:description>
<oslcem:clause>NodeAlias=’@http://open-services.net/ns/crtv#address’
</oslcem:clause>
<rr:uriTemplate>
<rr:URITemplate>
<rr:uriPattern>http://localhost/objectserver/oslc/query/
events?oslc.where=oslcem%3Anode+in+%5B{crtv_address}%5D</rr:uriPattern>
<rr:uriTemplateVariable>
<rr:URITemplateVariable>
<oslc:name>crtv_address</oslc:name>
<rdf:value>"{http://open-services.net/ns/crtv#address}"</rdf:value>
</rr:URITemplateVariable>
</rr:uriTemplateVariable>
</rr:URITemplate>
</rr:uriTemplate>
</rdf:RDF>

Example: Group
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#”
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#">
<oslcem:Group rdf:about="http://localhost/objectserver/oslc/group/0">
<foaf:name>Public</foaf:name>
<oslcem:description>Public Group</oslcem:description>
<oslcem:groupId>0</oslcem:groupId>
</oslcem:Group>
</rdf:RDF>

Example: User
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#”
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#">
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<oslcem:User rdf:about="http://localhost/objectserver/oslc/user/501">
<foaf:name>Test User 02</foaf:name>
<oslcem:userName>testuser02</oslcem:userName>
<oslcem:userId>501</oslcem:userId>
</oslcem:User>
</rdf:RDF>

80 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Example: RDF/XML success message
<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/
event/12571%3ANCOMS">
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<oslc:id>12571%3ANCOMS</oslc:id>
</rdf:Description>
</rdf:RDF>

Example: RDF/XML error message

<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/factory/event">
<rdf:type rdf:resource="http://open-services.net/ns/core#Error"/>
<oslc:statusCode>400</oslc:statusCode>
<oslc:message>Object not found</oslc:message>
</rdf:Description>
</rdf:RDF>

Appendix C. Examples: Resource RDF/XML payloads 81

82 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Appendix D. Examples: HTTP requests and responses
Example: Service provider service GET request
GET /objectserver/oslc/services HTTP/1.1
Accept: application/x-oslc-em-service-description+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Service provider service GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/x-oslc-em-service-description+xml
Content-Length: 8094

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<oslc:ServiceProvider rdf:about="http://localhost/objectserver/oslc/services">
<dcterms:title>IBM Tivoli Netcool/OMNIbus ObjectServer Service Provider
- [NCOMS]</dcterms:title>
<dcterms:description>Reference Implementation OSLC for Event Management
Service Document</dcterms:description>
<dcterms:publisher>
<oslc:Publisher>
<dcterms:title>Open Services for Lifecycle Collaboration in Event Management
</dcterms:title>
<dcterms:identifier>ibm.com/software/tivoli/oslc/em</dcterms:identifier>
<oslc:label>OSLC Event Management</oslc:label>
<oslc:icon rdf:resource="http://localhost/images/tivoli.png"/>
</oslc:Publisher>
</dcterms:publisher>
<oslc:prefixDefinition>
<oslc:PrefixDefinition>
<oslc:prefix>rdf</oslc:prefix>
<oslc:prefixBase rdf:resource="http://www.w3.org/1999/02/
22-rdf-syntax-ns#"/>
</oslc:PrefixDefinition>
</oslc:prefixDefinition>

***** TRUNCATED ******

<oslc:queryCapability>
<oslc:QueryCapability>
<dcterms:title>EM Event Query Capability</dcterms:title>
<oslc:label>Event Query</oslc:label>
<oslc:queryBase rdf:resource="http://localhost/objectserver/oslc/

© Copyright IBM Corp. 1994, 2017 83

 query/events"/>
<oslc:resourceShape rdf:resource="http://localhost/objectserver/oslc/shape?
type=event&amp;create=false"/>
<oslc:resourceType rdf:resource="http://tivoli-OSLC-prototype:80/ns/
oslcem/1.0/#event"/>
<oslc:usage rdf:resource="http://open-services.net:80/ns/core#default"/>
</oslc:QueryCapability>
</oslc:queryCapability>
</oslc:Service>
</oslc:service>
</oslc:ServiceProvider>
</rdf:RDF>

Example: Shape service GET request

GET /objectserver/oslc/shape?type=event&create=true HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Shape service GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 8094

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<oslc:ResourceShape rdf:about="http://localhost/objectserver/oslc/shape?
type=event&amp;create=true">
<dcterms:title>Event Type Creation Shape</dcterms:title>
<oslc:describes rdf:resource="http://tivoli-OSLC-prototype:80/ns/
oslcem/1.0/#event"/>
<oslc:property>
<oslc:Property>
<oslc:name>identifier</oslc:name>
<oslc:valueType rdf:resource="http://www.w3.org:80/2001/
XMLSchema#string"/>
<oslc:occurs rdf:resource="http://open-services.net:80/ns/
core#Exactly-one"/>
<oslc:propertyDefinition rdf:resource="http://purl.org:80/
dc/terms/identifier"/>
<oslc:readOnly rdf:resource="http://www.w3.org/2001/
XMLSchema#boolean">false</oslc:readOnly>
</oslc:Property>
</oslc:property>
<oslc:property>
<oslc:Property>
<oslc:name>created</oslc:name>
<oslc:valueType rdf:resource="http://www.w3.org:80/2001/
XMLSchema#dateTime"/>
<oslc:occurs rdf:resource="http://open-services.net:80/

84 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 ns/core#Exactly-one"/>
<oslc:propertyDefinition rdf:resource="http://purl.org:80/
dc/terms/created"/>
<oslc:readOnly rdf:resource="http://www.w3.org/2001/
XMLSchema#boolean">false</oslc:readOnly>
</oslc:Property>
</oslc:property>

***** TRUNCATED ******

<oslc:property>
<oslc:Property>
<oslc:name>oldRow</oslc:name>
<oslc:valueType rdf:resource="http://www.w3.org:80/2001/
XMLSchema#integer"/>
<oslc:occurs rdf:resource="http://open-services.net:80/ns/
core#Exactly-one"/>
<oslc:propertyDefinition rdf:resource="http://tivoli-OSLC-prototype:80/ns/
oslcemm/1.0/#oldRow"/>
<oslc:readOnly rdf:resource="http://www.w3.org/2001/
XMLSchema#boolean">false</oslc:readOnly>
</oslc:Property>
</oslc:property>
</oslc:ResourceShape>
</rdf:RDF>

Example: Event creation factory POST request

POST /objectserver/oslc/factory/event HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Content-Type: application/rdf+xml
Host: localhost
Connection: keep-alive
Content-Length: 1570

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Event"/>
<dcterms:identifier>JUnitEventTestInstance@@@@0</dcterms:identifier>
<dcterms:created>2012-07-04T15:28:11</dcterms:created>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/501"/>
<oslcem:severity>5</oslcem:severity>
<oslcem:summary>This is a test event generated by the JUnit OSLC Event Tests.
(0)</oslcem:summary>
<oslcem:node>localhost</oslcem:node>
<oslcem:agent>createEventNew()</oslcem:agent>
<oslcem:lastOccurrence>2012-07-04T15:28:11</oslcem:lastOccurrence>
<oslcem:acknowledged>false</oslcem:acknowledged>
<oslcem:alertKey>JUnitEventInstance</oslcem:alertKey>
<oslcem:manager>ResourceEvent</oslcem:manager>
<oslcem:type>1</oslcem:type>
<oslcem:ownerGID rdf:resource="http://localhost/objectserver/oslc/group/0"/>
<oslcemm:location>NOT UPDATED</oslcemm:location>
<oslcemm:url rdf:resource="http://localhost/objectserver/restapi/alerts/status"/>
</rdf:Description>
</rdf:RDF>

Appendix D. Examples: HTTP requests and responses 85

Example: Event creation factory POST response
HTTP/1.1 201 Created
Location: http://localhost/objectserver/oslc/event/12581%3ANCOMS
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:31:53 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 818

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/
12581%3ANCOMS">
<rdf:type rdf:resource="http://open-services.net/ns/
core#ResponseInfo"/>
<oslc:id>12581%3ANCOMS</oslc:id>
</rdf:Description>
</rdf:RDF>

Example: Event query capability GET request

GET /objectserver/oslc/query/events HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Event query capability GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 39777

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/query/events">
<dcterms:title>Event Service Query Results</dcterms:title>
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12581%3ANCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12582%3ANCOMS"/>

86 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 <rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12583%3ANCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12584%3ANCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12585%3ANCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12586%3ANCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12587%3ANCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12588%3ANCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12589%3ANCOMS"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/event/
12590%3ANCOMS"/>
</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/
12581%3ANCOMS">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Event"/>
<dcterms:identifier>JUnitEventTestInstance@@@@0</dcterms:identifier>
<dcterms:created>2012-07-04T16:28:11</dcterms:created>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/501"/>
<oslcem:severity>5</oslcem:severity>
<oslcem:summary>This is a test event generated by the JUnit OSLC Event Tests.
(0)</oslcem:summary>
<oslcem:node>localhost</oslcem:node>

***** TRUNCATED ******

<oslcemm:oldRow>0</oslcemm:oldRow>
</rdf:Description>
</rdf:RDF>

Example: Event resource GET request

GET /objectserver/oslc/event/12589%3ANCOMS HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Event resource GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 4355

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/

Appendix D. Examples: HTTP requests and responses 87

 12589%3ANCOMS">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Event"/>
<dcterms:identifier>JUnitEventTestInstance@@@@8</dcterms:identifier>
<dcterms:created>2012-07-04T16:28:11</dcterms:created>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/501"/>
<oslcem:severity>5</oslcem:severity>
<oslcem:summary>This is a test event generated by the JUnit
OSLC Event Tests. (8)</oslcem:summary>
<oslcem:node>localhost</oslcem:node>
<oslcem:agent>createEventNew()</oslcem:agent>
<oslcem:alertGroup></oslcem:alertGroup>
<oslcem:lastOccurrence>2012-07-04T16:28:11</oslcem:lastOccurrence>
<oslcem:tally>1</oslcem:tally>
<oslcem:acknowledged>false</oslcem:acknowledged>
<oslcem:serial>12589</oslcem:serial>
<oslcem:serverSerial>12589</oslcem:serverSerial>
<oslcem:serverName>NCOMS</oslcem:serverName>
<oslcem:alertKey>JUnitEventInstance</oslcem:alertKey>
<oslcem:manager>ResourceEvent</oslcem:manager>
<oslcem:stateChange>2012-07-04T15:31:59</oslcem:stateChange>
<oslcem:internalLast>2012-07-04T15:31:59</oslcem:internalLast>
<oslcem:type>1</oslcem:type>
<oslcem:class>0</oslcem:class>
<oslcem:grade>0</oslcem:grade>
<oslcem:ownerGID rdf:resource="http://localhost/objectserver/oslc/group/0"/>
<oslcem:taskList>0</oslcem:taskList>
<oslcem:suppressEscl>0</oslcem:suppressEscl>
<oslcem:flash>0</oslcem:flash>
<oslcem:expireTime>0</oslcem:expireTime>
<oslcem:customer></oslcem:customer>
<oslcem:service></oslcem:service>
<oslcem:probeSubSecondId>0</oslcem:probeSubSecondId>
<oslcem:journal rdf:resource="http://localhost/objectserver/oslc/query/
journals?oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial%3D12589%20and
%20oslcem%3AserverName%3D%22NCOMS%22%7D&amp;oslc.
orderBy=dcterms%3Acreated"/>
<oslcem:detail rdf:resource="http://localhost/objectserver/oslc/query/
details?oslc.where=oslcem%3Aevent%7Boslcem%3AserverSerial%3D12589%20and
%20oslcem%3AserverName%3D%22NCOMS%22%7D&amp;oslc.
orderBy=oslcem%3Asequence"/>

***** TRUNCATED ******

<oslcemm:url rdf:resource="http://localhost/objectserver/restapi/alerts/
status"/>
<oslcemm:extendedAttr></oslcemm:extendedAttr>
<oslcemm:oldRow>0</oslcemm:oldRow>
</rdf:Description>
</rdf:RDF>

Example: Event resource PATCH request

PATCH /objectserver/oslc/event/12621%3ANCOMS HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Content-Type: application/rdf+xml
Host: localhost
Connection: keep-alive
Content-Length: 1092

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"

88 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/
12621%3ANCOMS">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Event"/>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/
65534"/>
<oslcem:lastOccurrence>2012-07-04T15:33:27</oslcem:lastOccurrence>
<oslcem:acknowledged>true</oslcem:acknowledged>
<oslcem:ownerGID rdf:resource="http://localhost/objectserver/oslc/group/1"/>
<oslcemm:location>UPDATED</oslcemm:location>
</rdf:Description>
</rdf:RDF>

Example: Event resource PATCH response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 814

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/
12621%3ANCOMS">
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<oslc:id>12621:NCOMS</oslc:id>
</rdf:Description>
</rdf:RDF>

Example: Event resource DELETE request

DELETE /objectserver/oslc/event/12621%3ANCOMS HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Event resource DELETE response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:38:53 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 814

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"

Appendix D. Examples: HTTP requests and responses 89

 xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/event/
12621%3ANCOMS">
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<oslc:id>12621:NCOMS</oslc:id>
</rdf:Description>
</rdf:RDF>

Example: Journal creation factory POST request

POST /objectserver/oslc/factory/journal HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Content-Type: application/rdf+xml
Host: localhost
Connection: keep-alive
Content-Length: 817

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/0"/>
<dcterms:created>2012-07-04T15:34:44</dcterms:created>
<dcterms:content>This is a test journal generated by the JUnit OSLC Journal Tests.
</dcterms:content>
<oslcem:event rdf:resource="http://localhost/objectserver/oslc/event/
12661%3ANCOMS"/>
</rdf:Description>
</rdf:RDF>

Example: Journal creation factory POST response

HTTP/1.1 201 Created
Location: http://localhost/objectserver/oslc/journal/
12661%3A0%3A1341416084
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:31:53 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 818

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/journal/
12661%3A0%3A1341416084">
<rdf:type rdf:resource="http://open-services.net/ns/

90 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 core#ResponseInfo"/>
<oslc:id>12661:0:1341416084</oslc:id>
</rdf:Description>
</rdf:RDF>

Example: Journal query capability GET request

GET /objectserver/oslc/query/journals HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Journal query capability GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 8761

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/query/
journals">
<dcterms:title>Journal Service Query Results</dcterms:title>
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal/
12680%3A0%3A1341416084"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal/
12679%3A0%3A1341416084"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal/
12675%3A0%3A1341416084"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal/
12676%3A0%3A1341416084"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal/
12677%3A0%3A1341416084"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal
/12678%3A0%3A1341416084"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal/
12671%3A0%3A1341416084"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal/
12672%3A0%3A1341416084"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal/
12673%3A0%3A1341416084"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/journal/
12674%3A0%3A1341416084"/>
</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/journal/
12680%3A0%3A1341416084">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<dcterms:identifier>12680:0:1341416084</dcterms:identifier>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/0"/>
<dcterms:created>2012-07-04T16:34:44</dcterms:created>
<dcterms:content>This is a test journal generated by the JUnit
OSLC Journal Tests.</dcterms:content>
<oslcem:event rdf:resource="http://localhost/objectserver/oslc/event/

Appendix D. Examples: HTTP requests and responses 91

 12680%3ANCOMS"/>
</rdf:Description>

***** TRUNCATED ******

<rdf:Description rdf:about="http://localhost/objectserver/oslc/journal/
12674%3A0%3A1341416084">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<dcterms:identifier>12674:0:1341416084</dcterms:identifier>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/0"/>
<dcterms:created>2012-07-04T16:34:44</dcterms:created>
<dcterms:content>This is a test journal generated by the JUnit
OSLC Journal Tests.</dcterms:content>
<oslcem:event rdf:resource="http://localhost/objectserver/oslc/event/
12674%3ANCOMS"/>
</rdf:Description>
</rdf:RDF>

Example: Journal resource GET request

GET /objectserver/oslc/journal/12674%3A0%3A1341416084 HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Journal resource GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:35:22 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 1242

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/journal/
12674%3A0%3A1341416084">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<dcterms:identifier>12674:0:1341416084</dcterms:identifier>
<oslcem:ownerUID rdf:resource="http://localhost/objectserver/oslc/user/0"/>
<dcterms:created>2012-07-04T16:34:44</dcterms:created>
<dcterms:content>This is a test journal generated by the JUnit OSLC
Journal Tests.</dcterms:content>
<oslcem:event rdf:resource="http://localhost/objectserver/oslc/event/
12674%3ANCOMS"/>
</rdf:Description>
</rdf:RDF>

92 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Example: Journal resource PATCH request
ATCH /objectserver/oslc/journal/12681%3A0%3A1341416084 HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Content-Type: application/rdf+xml
Host: localhost
Connection: keep-alive
Content-Length: 677

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/journal/
12681%3A0%3A1341416084">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Journal"/>
<dcterms:content>This is a test journal generated by the JUnit OSLC Journal Tests.
*********** UPDATED JOURNAL ENTRY **************</dcterms:content>
</rdf:Description>
</rdf:RDF>

Example: Journal resource PATCH response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 814

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/journal/
12681%3A0%3A1341416084">
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<oslc:id>12681:0:1341416084</oslc:id>
</rdf:Description>
</rdf:RDF>

Example: Journal resource DELETE request

DELETE /objectserver/oslc/journal/12681%3A0%3A1341416084 HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Appendix D. Examples: HTTP requests and responses 93

Example: Journal resource DELETE response
HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 814

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/journal/
12681%3A0%3A1341416084">
<rdf:type rdf:resource="http://open-services.net/ns/core#
ResponseInfo"/>
<oslc:id>12681:0:1341416084</oslc:id>
</rdf:Description>
</rdf:RDF>

Example: Detail creation factory POST request

POST /objectserver/oslc/factory/detail HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Content-Type: application/rdf+xml
Host: localhost
Connection: keep-alive
Content-Length: 771

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<oslcem:attrValue>0</oslcem:attrValue>
<oslcem:sequence>0</oslcem:sequence>
<oslcem:detailName>EventDetail0</oslcem:detailName>
<oslcem:detailValue>This is a test detail generated by the JUnit OSLC
Detail Tests.</oslcem:detailValue>
<oslcem:event rdf:resource="http://localhost/objectserver/oslc/event/
12711%3ANCOMS"/>
</rdf:Description>
</rdf:RDF>

94 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

Example: Details creation factory POST response
HTTP/1.1 201 Created
Location: http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%400%23%23%23%230
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:31:53 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 818

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%400%23%23%23%230">
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<oslc:id>JUnitEventTestInstance@@@@0####0</oslc:id>
</rdf:Description>
</rdf:RDF>

Example: Detail query capability GET request

GET /objectserver/oslc/query/details HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Detail query capability GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 16:32:16 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 8761

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/query/
details">
<dcterms:title>Detail Service Query Results</dcterms:title>
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%404%23%23%23%234"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%408%23%23%23%238"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%402%23%23%23%232"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%406%23%23%23%236"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/

Appendix D. Examples: HTTP requests and responses 95

 JUnitEventTestInstance%40%40%40%400%23%23%23%230"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%405%23%23%23%235"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%409%23%23%23%239"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%403%23%23%23%233"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%407%23%23%23%237"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%401%23%23%23%231"/>
</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%404%23%23%23%234">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<dcterms:identifier>JUnitEventTestInstance@@@@4####4</dcterms:identifier>
<oslcem:attrValue>4</oslcem:attrValue>
<oslcem:sequence>4</oslcem:sequence>
<oslcem:detailName>EventDetail4</oslcem:detailName>
<oslcem:detailValue>This is a test detail generated by the JUnit
OSLC Detail Tests.</oslcem:detailValue>
<oslcem:event rdf:resource="http://localhost/objectserver/oslc/event/
12725%3ANCOMS"/>
</rdf:Description>

***** TRUNCATED ******

<rdf:Description rdf:about="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%401%23%23%23%231">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<dcterms:identifier>JUnitEventTestInstance@@@@1####1</dcterms:identifier>
<oslcem:attrValue>1</oslcem:attrValue>
<oslcem:sequence>1</oslcem:sequence>
<oslcem:detailName>EventDetail1</oslcem:detailName>
<oslcem:detailValue>This is a test detail generated by the JUnit
OSLC Detail Tests.</oslcem:detailValue>
<oslcem:event rdf:resource="http://localhost/objectserver/oslc/event/
12722%3ANCOMS"/>
</rdf:Description></rdf:RDF>

Example: Detail resource GET request

GET /objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%400%23%23%23%230 HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Detail resource GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 16:25:12 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 1240

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"

96 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%400%23%23%23%230">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<dcterms:identifier>JUnitEventTestInstance@@@@0####0
</dcterms:identifier>
<oslcem:attrValue>0</oslcem:attrValue>
<oslcem:sequence>0</oslcem:sequence>
<oslcem:detailName>EventDetail0</oslcem:detailName>
<oslcem:detailValue>This is a test detail generated by the JUnit OSLC
Detail Tests.</oslcem:detailValue>
<oslcem:event rdf:resource="http://localhost/objectserver/oslc/event/
12721%3ANCOMS"/>
</rdf:Description>
</rdf:RDF>

Example: Detail resource PATCH request

PATCH /objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%400%23%23%23%230 HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Content-Type: application/rdf+xml
Host: localhost
Connection: keep-alive
Content-Length: 694

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%400%23%23%23%230">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Detail"/>
<oslcem:detailValue>This is a test detail generated by the JUnit
OSLC Detail Tests. *********** UPDATED DETAIL ENTRY **************
</oslcem:detailValue>
</rdf:Description>
</rdf:RDF>

Example: Detail resource PATCH response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 814

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%400%23%23%23%230">

Appendix D. Examples: HTTP requests and responses 97

 <rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<oslc:id>JUnitEventTestInstance@@@@0####0</oslc:id>
</rdf:Description>
</rdf:RDF>

Example: Detail resource DELETE request

DELETE /objectserver/oslc/detail/JUnitEventTestInstance
%40%40%40%400%23%23%23%230 HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Detail resource DELETE response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 15:32:03 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 814

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/detail/
JUnitEventTestInstance%40%40%40%400%23%23%23%230">
<rdf:type rdf:resource="http://open-services.net/ns/core#ResponseInfo"/>
<oslc:id>JUnitEventTestInstance@@@@0####0</oslc:id>
</rdf:Description>
</rdf:RDF>

Event collection identifier pattern query capability: GET request

GET /objectserver/oslc/query/ecips HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Event collection identifier pattern query capability: GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 16:32:16 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 8761

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"

98 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide

 xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:rr="http://jazz.net/ns/ism/registry#">
<oslc:ResponseInfo rdf:about="http://localhost/objectserver/oslc/query/ecips">
<dcterms:title>Event Collection Identifier Pattern Service Query Results
</dcterms:title>
</oslc:ResponseInfo>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/query/ecips">
<rdf:type rdf:resource="http://jazz.net/ns/ism/event/omnibus#Collection"/>
<rdf:type rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/ecip/2190"/>
<rdfs:member rdf:resource="http://localhost/objectserver/oslc/ecip/2191"/>
</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/ecip/2190">
<rdf:type
rdf:resource="http://jazz.net/ns/ism/event/omnibus#CollectionIdentifierPattern"/>
<oslc:resourceType
rdf:resource="http://open-services.net/ns/crtv#ComputerSystem"/>
<dcterms:title>JUnitQP01</dcterms:title>
<dcterms:description>The event collection identifier pattern for a
ComputerSystem resource.</dcterms:description>
<oslcem:clause>Node=’@http://open-services.net/ns/crtv#fqdn’
</oslcem:clause>
<rr:uriTemplate>
<rr:URITemplate>
<rr:uriPattern>http://localhost/objectserver/oslc/query/
events?oslc.where=oslcem%3Anode+in+%5B{crtv_fqdn}%5D</rr:uriPattern>
<rr:uriTemplateVariable>
<rr:URITemplateVariable>
<oslc:name>crtv_fqdn</oslc:name>
<rdf:value>"{http://open-services.net/ns/crtv#fqdn}"</rdf:value>
</rr:URITemplateVariable>
</rr:uriTemplateVariable>
</rr:URITemplate>
</rr:uriTemplate>
</rdf:Description>

<rdf:Description rdf:about="http://localhost/objectserver/oslc/ecip/2191">
<rdf:type
rdf:resource="http://jazz.net/ns/ism/event/omnibus#CollectionIdentifierPattern"/>
<oslc:resourceType rdf:resource="http://open-services.net/ns/crtv#QP02"/>
<dcterms:title>JUnitQP02</dcterms:title>
<dcterms:description>The event collection identifier pattern for a QP02
resource.</dcterms:description>
<oslcem:clause>NodeAlias=’@http://open-services.net/ns/crtv#address’
</oslcem:clause>
<rr:uriTemplate>
<rr:URITemplate>
<rr:uriPattern>http://localhost/objectserver/oslc/query/
events?oslc.where=oslcem%3Anode+in+%5B{crtv_address}%5D</rr:uriPattern>
<rr:uriTemplateVariable>
<rr:URITemplateVariable>
<oslc:name>crtv_address</oslc:name>
<rdf:value>"{http://open-services.net/ns/crtv#address}"</rdf:value>
</rr:URITemplateVariable>
</rr:uriTemplateVariable>
</rr:URITemplate>
</rr:uriTemplate>
</rdf:RDF>

Appendix D. Examples: HTTP requests and responses 99

Event collection identifier pattern resource: GET request
GET objectserver/oslc/ecip/2190 HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Event collection identifier pattern resource: GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 16:25:12 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 650

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#"
xmlns:oslcemp="http://jazz.net/ns/ism/event/omnibus/itnm#"
xmlns:oslcemb="http://jazz.net/ns/ism/event/omnibus/tbsm#"
xmlns:oslcemm="http://jazz.net/ns/ism/event/omnibus/misc#"
xmlns:rr="http://jazz.net/ns/ism/registry#">
<rdf:Description rdf:about="http://localhost/objectserver/oslc/ecip/2190">
<rdf:type
rdf:resource="http://jazz.net/ns/ism/event/omnibus#CollectionIdentifierPattern"/>
<oslc:resourceType
rdf:resource="http://open-services.net/ns/crtv#ComputerSystem"/>
<dcterms:title>JUnitQP01</dcterms:title>
<dcterms:description>The event collection identifier pattern for a
ComputerSystem resource.</dcterms:description>
<oslcem:clause>Node=’@http://open-services.net/ns/crtv#fqdn’
</oslcem:clause>
<rr:uriTemplate>
<rr:URITemplate>
<rr:uriPattern>http://localhost/objectserver/oslc/query/
events?oslc.where=oslcem%3Anode+in+%5B{crtv_fqdn}%5D</rr:uriPattern>
<rr:uriTemplateVariable>
<rr:URITemplateVariable>
<oslc:name>crtv_fqdn</oslc:name>
<rdf:value>"{http://open-services.net/ns/crtv#fqdn}"</rdf:value>
</rr:URITemplateVariable>
</rr:uriTemplateVariable>
</rr:URITemplate>
</rr:uriTemplate>
</rdf:Description>
</rdf:RDF>

100 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Example: Person resource GET request
GET /objectserver/oslc/user/500 HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Person resource GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 16:12:42 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 814

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<foaf:Person rdf:about="http://localhost/objectserver/oslc/user/500">
<foaf:name>Test User 01</foaf:name>
<oslcem:userName>testuser01</oslcem:userName>
<oslcem:userId>500</oslcem:userId>
</foaf:Person>
</rdf:RDF>

Example: Group resource GET request

GET /objectserver/oslc/group/1 HTTP/1.1
Accept: application/rdf+xml
Authorization: Basic dGVzdHVzZXIwMTpuZXRjb29s
Host: localhost
Connection: keep-alive

Example: Group resource GET response

HTTP/1.1 200 OK
Cache-Control: no-cache
Server: libnhttpd
Date: Wed Jul 4 17:14:08 2012
Connection: Keep-Alive
Content-Type: application/rdf+xml
Content-Length: 814

<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:oslc="http://open-services.net/ns/core#"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:crtv="http://open-services.net/ns/crtv#"
xmlns:oslcem="http://jazz.net/ns/ism/event/omnibus#">
<foaf:Group rdf:about="http://localhost/objectserver/oslc/group/1">
<foaf:name>System</foaf:name>
<oslcem:description>System Group</oslcem:description>
<oslcem:groupId>1</oslcem:groupId>
</foaf:Group>
</rdf:RDF>

Appendix D. Examples: HTTP requests and responses 101

JSON configuration file with MIME type settings and HTTP headers
This example shows a $OMNIHOME/etc/libnhttpd/json configuration file, which is
edited to define MIME type settings and HTTP headers in HTTP responses that are
returned by the HTTP interface and OSLC interface. To enable MIME type settings
and HTTP headers, enable the NHttpd.ConfigFile property.

The sections that enable MIME type settings and HTTP headers are as follows:
httpResponse
Defines the HTTP headers that are in the HTTP responses that are returned by
the HTTP interface and OLSC interface. It has the following subsections:
corsHeaders
Overrides Cross-Origin Resource Sharing (CORS) HTTP headers. By
default, the default headers are overridden to indicate that the Location
HTTP header are be allowed and exposed. This setting is required for
HTTP 201 Create responses messages.
httpHeaders
For user-defined HTTP headers. These headers are added to all HTTP
responses. Use this section to add static values for clients. A sample header
is provided in the example.

mimeTypes
This section assigns a file extension, for example .html, to a MIME type. When
file-serving is enabled, these definitions are used to determine the MIME type
for the file. They also set the Content-Type HTTP header so that browsers can
handle the file correctly. The $OMNIHOME/etc/libnhttpd/json file has a default
set of MIME type settings that you can add to.

Example
{
"_comment" : "This file provides additional configuration data to the embedded HTTP
socket library (libnhttpd).",
"httpResponse" : {
"_comment" : "This section defines a set of user defined static elements that
should be returned in an HTTP response, such as HTTP headers.",
"corsHeaders" : [
{
"name" : "Access-Control-Allow-Headers",
"value" : "Location"
},
{
"name" : "Access-Control-Expose-Headers",
"value" : "Location"
}
],
"httpHeaders" : [
]
},
"mimeTypes" : {
"_comment" : "This section maps MIME types to file extensions. It is used by
libnhttpd to determine the MIME type for a file that is to be served from
its file serving URI.",
"application/json" : [
"json"
],
"application/rdf+xml" : [
"rdf"
],

102 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
 "application/xslt+xml" : [
"xsl", "xslt"
],
"image/jpeg" : [
"jpg", "jpeg"
],
"image/gif" : [
"gif"
],
"image/png" : [
"png"
],
"text/css" : [
"css"
],
"text/javascript" : [
"js"
],
"text/HTML" : [
"htm", "html"
],
"text/plain" : [
"txt", "log"
],
"text/xml" : [
"xml"
]
}
}

Appendix D. Examples: HTTP requests and responses 103

104 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Appendix E. Resource shape configuration file
The default resource shape definition configuration file.
{
"event" :
[
{
"nsprefix" : "dcterms",
"nsuri" : "http://purl.org/dc/terms/",
"types" : [
{
os" : "Identifier",
"oslc" : "identifier",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "FirstOccurrence",
"oslc" : "created",
type" : "dateTime",
"systemColumn" : "false"
},
{
"os" : "OwnerUID",
"oslc" : "creator",
"type" : "ResourceUID",
"systemColumn" : "false"
}
]
},
{
"nsprefix" : "crtv",
"nsuri" : "http://open-services.net/ns/crtv#",
types" [
{
"os" : "Severity",
"oslc" : "severity",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "Summary",
"oslc" : "summary",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "Node",
"oslc" : "node",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "Agent",
"oslc" : "agent",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "AlertGroup",
"oslc" : "alertGroup",
"type" : "string",

© Copyright IBM Corp. 1994, 2017 105

 "systemColumn" : "false"
},
{
"os" : "LastOccurrence",
"oslc" : "lastOccurrence",
"type" : "dateTime",
"systemColumn" : "false"
},
{
"os" : "Tally",
"oslc" : "tally",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "Acknowledged",
"oslc" : "acknowledged",
"type" : "boolean",
"systemColumn" : "false"
}
]
},
{
"nsprefix" : "oslcem",
"nsuri" : "http://jazz.net/ns/ism/event/omnibus#",
"types" : [
{
"os" : "Serial",
"oslc" : "serial",
"type" : "integer",
"systemColumn" : "true"
},
{
"os" : "ServerSerial",
"oslc" : "serverSerial",
"type" : "integer",
"systemColumn" : "true"
},
{
"os" : "ServerName",
"oslc" : "serverName",
"type" : "string",
"systemColumn" : "true"
},
{
"os" : "AlertKey",
"oslc" : "alertKey",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "Manager",
"oslc" : "manager",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "StateChange",
"oslc" : "stateChange",
"type" : "dateTime",
"systemColumn" : "false"
},
{
"os" : "InternalLast",
"oslc" : "internalLast",
"type" : "dateTime",
"systemColumn" : "false"

106 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
},
{
"os" : "Type",
"oslc" : "type",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "Class",
"oslc" : "class",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "Grade",
"oslc" : "grade",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "OwnerGID",
"oslc" : "ownerGID",
"type" : "ResourceGID",
"systemColumn" : "false"
},
{
"os" : "TaskList",
"oslc" : "taskList",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "SuppressEscl",
"oslc" : "suppressEscl",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "Flash",
"oslc" : "flash",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "ExpireTime",
"oslc" : "expireTime",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "Customer",
"oslc" : "customer",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "Service",
"oslc" : "service",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "ProbeSubSecondId",
"oslc" : "probeSubSecondId",
"type" : "integer",
"systemColumn" : "false"
},

Appendix E. Resource shape configuration file 107

 {
"os" : "",
"oslc" : "journal",
"type" : "ResourceJournal",
"systemColumn" : "true"
},
{
"os" : "",
"oslc" : "detail",
"type" : "ResourceDetail",
"systemColumn" : "true"
}
]
},
{
"nsprefix" : "oslcemp",
"nsuri" : "http://jazz.net/ns/ism/event/omnibus/itnm#",
"types" : [
{
"os" : "EventId",
"oslc" : "eventId",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "ProcessReq",
"oslc" : "processReq",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "NmosSerial",
"oslc" : "nmosSerial",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "NmosObjInst",
"oslc" : "nmosObjInst",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "NmosCauseType",
"oslc" : "nmosCauseType",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "NmosDomainName",
"oslc" : "nmosDomainName",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "NmosEntityId",
"oslc" : "nmosEntityId",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "NmosManagedStatus",
"oslc" : "nmosManagedStatus",
"type" : "integer",
"systemColumn" : "false"
},
{

108 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
 "os" : "NmosEventMap",
"oslc" : "nmosEventMap",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "LocalNodeAlias",
"oslc" : "localNodeAlias",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "LocalPriObj",
"oslc" : "localPriObj",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "LocalSecObj",
"oslc" : "localSecObj",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "LocalRootObj",
"oslc" : "localRootObj",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "RemoteNodeAlias",
"oslc" : "remoteNodeAlias",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "RemotePriObj",
"oslc" : "remotePriObj",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "RemoteSecObj",
"oslc" : "remoteSecObj",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "RemoteRootObj",
"oslc" : "remoteRootObj",
"type" : "string",
"systemColumn" : "false"
}
]
},
{
"nsprefix" : "oslcemb",
"nsuri" : "http://jazz.net/ns/ism/event/omnibus/tbsm#",
"types" : [
{
"os" : "BSM_Identity",
"oslc" : "bsmIdentity",
"type" : "string",
"systemColumn" : "false"
}
]
},

Appendix E. Resource shape configuration file 109

 {
"nsprefix" : "oslcemm",
"nsuri" : "http://jazz.net/ns/ism/event/omnibus/misc#",
"types" : [
{
"os" : "Poll",
"oslc" : "poll",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "Location",
"oslc" : "location",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "PhysicalSlot",
"oslc" : "physicalSlot",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "PhysicalPort",
"oslc" : "physicalPort",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "PhysicalCard",
"oslc" : "physicalCard",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "X733EventType",
"oslc" : "x733EventType",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "X733ProbableCause",
"oslc" : "x733ProbableCause",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "X733SpecificProb",
"oslc" : "x733SpecificProb",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "X733CorrNotif",
"oslc" : "x733CorrNotif",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "URL",
"oslc" : "url",
"type" : "Resource",
"systemColumn" : "false"
},
{
"os" : "ExtendedAttr",
"oslc" : "extendedAttr",

110 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
 "type" : "string",
"systemColumn" : "false"
},
{
"os" : "OldRow",
"oslc" : "oldRow",
"type" : "integer",
"systemColumn" : "false"
}
]
}
],
"journal" :
[
{
"nsprefix" : "dcterms",
"nsuri" : "http://purl.org/dc/terms/",
"types" : [
{
"os" : "KeyField",
"oslc" : "identifier",
"type" : "string",
"systemColumn" : "true"
},
{
"os" : "UID",
"oslc" : "creator",
"type" : "ResourceUID",
"systemColumn" : "false"
},
{
"os" : "Chrono",
"oslc" : "created",
"type" : "dateTime",
"systemColumn" : "false"
},
{
"os" : "Text",
"oslc" : "content",
"type" : "journal",
"systemColumn" : "false"
}
]
},
{
"nsprefix" : "oslcem",
"nsuri" : "http://jazz.net/ns/ism/event/omnibus#",
"types" : [
{
"os" : "Serial",
"oslc" : "event",
"type" : "ResourceEvent",
"systemColumn" : "false"
}
]
}
],
"detail" :
[
{
"nsprefix" : "dcterms",
"nsuri" : "http://purl.org/dc/terms/",
"types" : [
{
"os" : "KeyField",
"oslc" : "identifier",
"type" : "string",

Appendix E. Resource shape configuration file 111

 "systemColumn" : "true"
}
]
},
{
"nsprefix" : "oslcem",
"nsuri" : "http://jazz.net/ns/ism/event/omnibus#",
"types" : [
{
"os" : "AttrVal",
"oslc" : "attrValue",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "Sequence",
"oslc" : "sequence",
"type" : "integer",
"systemColumn" : "false"
},
{
"os" : "Name",
"oslc" : "name",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "Detail",
"oslc" : "detail",
"type" : "string",
"systemColumn" : "false"
},
{
"os" : "Identifier",
"oslc" : "event",
"type" : "ResourceEvent",
"systemColumn" : "false"
}
]
}
]
}

112 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Appendix F. List of abbreviations
The API documentation for the ObjectServer HTTP interface and the ObjectServer
OSLC interface use the following abbreviations and terms.
HTTP Hyper Text Transfer Protocol. HTTP version 1.1 is defined in RFC2616.
Unless otherwise noted, the term HTTP is used in this document to mean
both HTTP and HTTPS.
HTTPS
Hyper Text Transfer Protocol Secure, as defined in RFC2818.
JazzSM
Jazz for Service Management, which is available from https://
www.ibm.com/developerworks/mydeveloperworks/groups/service/
html/communityview?communityUuid=69ec672c-dd6b-443d-add8-
bb9a9a490eba.
JSON JavaScript Object Notation, as defined in ECMA-262.
MIME Multipurpose Internet Mail Extensions. MIME media types are defined in
IANA MIME Media Types.
OSLC Open Services for Lifecycle Collaboration, as defined at
http://open-services.net.
REST Representational State Transfer, as originally and informally described in
Architectural Styles and the Design of Network-based Software Architectures.
URI Uniform Resource Identifier, as defined in RFC3986.
XML eXtensible Markup Language, as defined by W3C.

© Copyright IBM Corp. 1994, 2017 113

114 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

© Copyright IBM Corp. 1994, 2017 115

 IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
958/NH04
IBM Centre, St Leonards
601 Pacific Hwy
St Leonards, NSW, 2069
Australia

IBM Corporation
896471/H128B
76 Upper Ground
London SE1 9PZ
United Kingdom

IBM Corporation
JBF1/SOM1
294 Route 100
Somers, NY, 10589-0100
United States of America

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the

116 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
 names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs.

Portions of this product include software developed by Daniel Veillard.

v libxml2-2.7.8
The libxml2-2.7.8 software is distributed according to the following license
agreement:
© Copyright 1998-2003 Daniel Veillard.
All Rights Reserved. Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation files (the
“Software”), to deal in the Software without restriction, including without
limitation the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE DANIEL VEILLARD BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
Except as contained in this notice, the name of Daniel Veillard shall not be used in
advertising or otherwise to promote the sale, use or other dealings in this Software
without prior written authorization from him.

If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

Trademarks
AIX, IBM, the IBM logo, ibm.com®, Informix, Netcool, System z, Tivoli®, and Tivoli
Enterprise Console® are trademarks or registered trademarks of International
Business Machines Corporation in the United States, other countries, or both.

Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-based
trademarks are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States, other countries, or both.

Notices 117
 Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc. in the United States,
other countries, or both.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Other company, product, or service names may be trademarks or service marks of

others.

118 IBM Tivoli Netcool/OMNIbus: Object Server OSLC Interface Reference Guide
Notices 119
IBM®

Printed in the Republic of Ireland

SC27-6269-00