Administering ENS consists of starting and stopping the service, and changing the configuration parameters to control the behavior of the iBiff publisher for ENS.
You use the start-msg ens and stop-message ens commands to start and stop the ENS server. You must be root to run these commands.
To start ENS:
msg_svr_base/sbin/start-msg ens
To stop ENS:
msg_svr_base/sbin/stop-msg ens
Several configuration parameters control the behavior of iBiff. Use the configutil utility program to set these parameters.
Table B–1 iBiff Configuration Parameters
Parameter |
Description |
---|---|
Specifies the maximum size (in bytes) of the header that will be transmitted with the notification. The default is 0 bytes. |
|
local.store.notifyplugin.maxBodySize |
Specifies the maximum size (in bytes) of the body that will be transmitted with the notification. The default is 0 bytes. |
local.store.notifyplugin.eventType.enable |
Specifies if the given event type will generate a notification. The legal values are 1 (to enable) and 0 (to disable). The default value is 1; that is, setting local.store.notifyplugin.ReadMsg.enable to 0 will disable ReadMsg notifications. |
local.store.notifyplugin.ensHost |
Specifies the hostname of the ENS server. The default is 127.0.0.1. |
local.store.notifyplugin.ensPort |
Specifies the TCP port of the ENS server. The default is 7997. |
local.store.notifyplugin.ensEventKey |
Specifies the event key to use for ENS notifications. The default is enp://127.0.0.1/store. The hostname portion of the event key is not used to determine the ENS host. It is simply a unique identifier used by ENS. This key is what the subscriber should subscribe to in order to be notified of events matching this key. |