Configure a separate set of JMQ notification parameters for each plug-in you intend to create.
For example, suppose you configure two plug-ins named jmq1 and jmq2. Assume you want to enable new-message notifications for both plug-ins and purged-message notifications for the jmq2 plug-in only. In this case, you would run the local.store.notifyplugin command three times, as follows:
configutil -o local.store.notifyplugin.jmq1.NewMsg.enable -v 1 |
configutil -o local.store.notifyplugin.jmq2.NewMsg.enable -v 1 |
configutil -o local.store.notifyplugin.jmq2.PurgeMsg.enable -v 1 |
You also must specify parameters that enable the plug-ins to communicate with the Message Queue service.
For step-by-step instructions for configuring the all the notification parameters, see To Configure a JMQ Notification Plug-in.
Configure the plug-in names.
To configure two plug-ins named jmq1 and jmq2, you would enter the following command:
configutil -o local.store.notifyplugin -v '/opt/SUNWmsgsr/lib/libjmqnotify$jmq1$$/opt/SUNWmsgsr/ \ lib/libjmqnotify$jmq2' |
In this example, two instances of the plug-in library are run.
Use a single dollar sign ($) to separate the library name from the parameter that specifies the plug-in name.
Use two dollar signs ($$) to separate the first plug-in instance from the next one.
Enclose the entire value in single quotes ('value'); if you do not, the shell will interpret the dollar signs.
In this example, the first instance builds its configuration from parameters with the name jmq1:
local.store.notify.jmq1.* |
The second instance builds its configuration from parameters with the name jmq2:
local.store.notify.jmq2.* |