Tivoli Netcool Supports
Guide to
event ownership tools
by
Jim Hutchinson
Document release: 2.0
Supports Guide to event ownership tools
Table of Contents
1Introduction...................................................................................................................................2
1.1Overview......................................................................................................................................2
1.2Design..........................................................................................................................................2
1.3Tools............................................................................................................................................3
1.3.1Re-assign tool...........................................................................................................................3
1.3.2Assign tool................................................................................................................................3
2SQL file content............................................................................................................................4
IBM Copyright 2014
1
Supports Guide to event ownership tools
1 Introduction
1.1 Overview
Netcool/OMNIbus users are not able to take ownership of events that are already owned by another user unless
they are administrators. This behaviour is part of the Netcool/OMNIbus security model and cannot be updated
through customisation.
However, some customers want to allow users to reassign all events from one user to another, for
shift work, without the need for administrator intervention. Whilst some other customers would like
to give users the ability to assign individual events to themselves.
The purpose of the workaround provided within this document is to allow Netcool/OMNIbus administrators the
option to configure their Netcool/OMNIbus system, such that the Netcool/OMNIbus security model is maintained
whilst allowing the users to assign events to themselves.
1.2 Design
The setting of UserID can only occur if the user is an administrator.
Netcool/OMNIbus triggers are run as the administrator, which allows them to reassign events.
For a normal user to cause a reassign trigger action, the normal user must run a tool on a custom table, to trigger
the event reassignment. This is because the alerts.status is protected by the Netcool/OMNIbus security model.
For the given event ownership tools two custom tables are used:
•
•
custom.my_assign
◦ Identifier
varchar(255) primary key
◦ ToUserID
int
custom.reassign
◦ Serial
incr primary key
◦ ToUserID
int
◦ FromUserID
int
The user accessible tool then inserts the required event data into the custom table to cause the temporal trigger to
action.
The trigger actions themselves are SQL statements:
Assign a specific event using the selected events Identifier:
update alerts.status via assigned.Identifier set OwnerUID = assigned.ToUserID;
Assign all events from a user to the current user:
update alerts.status set OwnerUID = reassigned.ToUserID where OwnerUID = reassigned.FromUserID;
The workaround does not include any audit features, such as logging who has reassigned alarms to themselves,
and what alarms were reassigned. This type of behaviour can be added by the Netcool/OMNIbus administrator as
required using the Netcool/OMNIbus features or customised utilities.
IBM Copyright 2014
2
Supports Guide to event ownership tools
1.3 Tools
The following tools can be added to the AlertsMenu, so that users can access them from the event list.
1.3.1 Re-assign tool
The re-assign tool allows users to assign another users events to themselves.
No events need to be selected for the tool to work.
Tool Details:
Name : Re-assign [x] enabled
SQL : [x] enabled
insert into custom.reassign (FromUserID, ToUserID) values ($prompt.UserAssign, %uid);
Description :
Allows user to re-assign another users events to themselves from a list of users.
1.3.2 Assign tool
The assign tool allows users to select and event and assign the event to themselves.
The event that needs to be reassigned must be selected in the event list, so that the Identifier can be used to
reassign the alarm to the user, who is running the event list.
Tool Details:
Name : My assign tool [x] enabled
SQL : [x] enabled
insert into custom.my_assign (Identifier,ToUserID) values ( '@Identifier', %uid);
Description:
Allows any user to select and event and assigned to themself.
IBM Copyright 2014
3
Supports Guide to event ownership tools
2 SQL file content
create table custom.my_assign persistent
(
Identifier
varchar(255) primary key,
ToUserID
int
);
go
grant
grant
grant
grant
go
select
insert
update
delete
on
on
on
on
table
table
table
table
custom.my_assign
custom.my_assign
custom.my_assign
custom.my_assign
to
to
to
to
role
role
role
role
'AlertsUser';
'AlertsUser';
'AlertsUser';
'AlertsUser';
create table custom.reassign persistent
(
Serial
incr primary key,
ToUserID
int,
FromUserID
int
);
go
grant
grant
grant
grant
go
select
insert
update
delete
on
on
on
on
table
table
table
table
custom.reassign
custom.reassign
custom.reassign
custom.reassign
to
to
to
to
role
role
role
role
'AlertsUser';
'AlertsUser';
'AlertsUser';
'AlertsUser';
create or replace trigger group nc_assign;
go
create or replace trigger nc_reassign
group nc_assign
priority 1
comment 'Re-assign events'
every 15 seconds
evaluate
select FromUserID, ToUserID from custom.reassign bind as nc_reassign
begin
for each row reassigned in nc_reassign
begin
update alerts.status
set OwnerUID = reassigned.ToUserID
where OwnerUID = reassigned.FromUserID;
end;
delete from custom.reassign;
end;
go
create or replace trigger nc_my_assign
group nc_assign
priority 1
comment 'Assign events'
every 15 seconds
evaluate
select Identifier, ToUserID from custom.my_assign bind as nc_assign
begin
for each row assigned in nc_assign
begin
update alerts.status
via assigned.Identifier
set OwnerUID = assigned.ToUserID;
end;
delete from custom.my_assign;
end;
go
IBM Copyright 2014
4