Cisco Cisco Prime Optical 10.3 Developer's Guide
Cisco Prime Optical 10.3 GateWay/CORBA Programmer Reference Guide
584
For NE-related alarms, Prime Optical inserts the original probable cause in the alarm’s
nativeProbableCause field. The TMF-mapped probable cause is available in the probableCause
field.
nativeProbableCause field. The TMF-mapped probable cause is available in the probableCause
field.
5.2 Resolving the Notification Service
GateWay/CORBA can integrate with external notification services. When GateWay/CORBA
starts, a reference to EventNotifyChannelFactory is resolved. GateWay/CORBA makes the
following attempts to resolve the object:
starts, a reference to EventNotifyChannelFactory is resolved. GateWay/CORBA makes the
following attempts to resolve the object:
1. Resolve initial references with the default service name of NotificationService to resolve the object.
You can change the service name by setting the corbagw.notification.ServiceName property in the
corbagw.properties file.
corbagw.properties file.
2. Resolve the object through the naming service. The default naming service entry is
services.NotifyChannelFactory. You can change the naming service entry by setting the
corbagw.notification.NamingContext property in the corbagw.properties file.
corbagw.notification.NamingContext property in the corbagw.properties file.
3. Resolve the object directly through the Interoperable Object Reference (IOR). You can change the
URL of the IOR file by setting the corbagw.notification.FactoryIORFile property in the
corbagw.properties file. The default location for the IOR file is
file://localhost/CTM_baseDir/cfg/NotificationService.ior. You can specify a URL that points to a
remote web server.
corbagw.properties file. The default location for the IOR file is
file://localhost/CTM_baseDir/cfg/NotificationService.ior. You can specify a URL that points to a
remote web server.
5.3 Tips to Improve Notification Throughput
While GateWay/CORBA and the bundled notification server are developed and tuned to provide
high throughput, you might want to take additional steps to improve throughput and avoid any
loss of notifications. You should implement the StructuredPushConsumer interface defined by
the Object Management Group (OMG) and implement the push_structured_event method. The
notification server invokes this method on the NMS.
Because all CORBA calls are blocking, the notification server thread blocks until the
high throughput, you might want to take additional steps to improve throughput and avoid any
loss of notifications. You should implement the StructuredPushConsumer interface defined by
the Object Management Group (OMG) and implement the push_structured_event method. The
notification server invokes this method on the NMS.
Because all CORBA calls are blocking, the notification server thread blocks until the
push_structured_event method completes. If you try to perform a time-consuming task
before the method completes, you will block the notification server.
before the method completes, you will block the notification server.
To improve throughput, you should receive the event and forward it to another thread for
processing.
For example:
processing.
For example:
As shown in the example, you must catch all exceptions, or you will stop receiving
notifications.
5.4 Supported Events
The following sections list the attributes of each event.