This chapter describes how to install cosNotificationApp in an Erlang Environment.
Before starting the installation process for cosNotification, the application Orber must be running.
When using the Notification Service the cosNotification
application
first must be installed using cosNotificationApp:install()
or
cosNotificationApp:install(Seconds)
, followed by cosNotificationApp: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 function start_time_service/2
in the cosTime
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 property MaxEventsPerConsumer
, i.e.,
the gcLimit
should be less than MaxEventsPerConsumer
and greater than 0.
It is possible to configure cosNotification to type check, by invoking corba_object:is_a/2, supplied IOR:s or not. The default behavior is that the IOR:s will be validated.
The Factory is now ready to use. For a more detailed description see Examples.