3 Installing cosNotification
3.1 Installation Process
This chapter describes how to install cosNotificationApp in an Erlang Environment.
3.1.1 Preparation
Before starting the installation process for cosNotification, the application Orber must be running.
3.1.2 Configuration
When using the Notification Service the
cosNotification
application first must be installed usingcosNotificationApp:install()
orcosNotificationApp:install(Seconds)
, followed bycosNotificationApp:start()
.Then the Event Channel Factory must be started:
cosNotificationApp:start_global_factory()
- starts and returns a reference to a factory using default configuration parameters. This operation should be used for a multi-node Orber.
cosNotificationApp:start_global_factory(Options)
- starts and returns a reference to a factory using given configuration parameters. This operation should be used for a multi-node Orber.
cosNotificationApp:start_factory()
- starts and returns a reference to a factory using default configuration parameters.
cosNotificationApp:start_factory(Options)
- starts and returns a reference to a factory using given configuration parameters.
The following options exist:
{pullInterval, Seconds}
- determine how often Proxy Pull Consumers will check for new events with the client application. The default value is 20 seconds.
{filterOp, OperationType}
- determine which type of Administrator objects should be started, i.e.,'OR_OP'
or'AND_OP'
. The default value is'OR_OP'
.
{timeService, TimeServiceObj | 'undefined'}
- to be able to use Start and/or Stop QoS this option must be used. See the functionstart_time_service/2
in thecosTime
application. The default value is'undefined'
.
{filterOp, OperationType}
- determine which type of Administrator objects should be started, i.e.,'OR_OP'
or'AND_OP'
. The default value is'OR_OP'
.
{gcTime, Seconds}
- this option determines how often, for example, proxies will garbage collect expired events. The default value is 60.
{gcLimit, Amount}
- determines how many events will be stored before, for example, proxies will garbage collect expired events. The default value is 50. This option is tightly coupled with the QoS propertyMaxEventsPerConsumer
, i.e., thegcLimit
should be less thanMaxEventsPerConsumer
and greater than 0.
The Factory is now ready to use. For a more detailed description see Examples.