5.4

System Servers
363
server’s source queue. For this to happen, the wire distribution story must be modified. So,
open the story and add the new instruction on a single line, using the following format:
<dev
name><wire code> <distribution queue> [<options>]
n
There must be no spaces between the device name and the wire service code. The [<options>]
should also be on the same line, separated from the distribution queue by a space.
10. (Optional) Test your configuration changes.
11.
Reconfigure the system.
12. Start the keyword server.
When you see the
System being configured message, select the iNEWS Server where
the keyword server is configured and start the keyword server. For instance, type:
NRCS-A$
restart 211
13. (Optional) Back up site files using sitedump command.
System Servers
Utility programs called system servers are usually included on your system at installation. You
cannot customize them; therefore, they are described here in a limited way.
Code Description
<dev name><wire code>
For instance, the wire program’s device name is AP. If you want this
instruction to match all wire stories regardless of their wire service code,
use
######## as the code, because it matches any code. See
“Distribution Name” on page 298 for more information.
<distribution queue>
The distribution queue is where you want stories with the specified code
to be duplicated, such as WIRES.AP-SEARCH.
[<options>]
Finally, you can end the line with any of the following options:
ALWAYS, SILENT, URGENT, FLASH, BULLETIN, or TRANSMIT.
For instance, end the instruction with the ALWAYS option to ensure that
every wire the AP wire program processes is duplicated to the keyword
server’s source queue.
The finished instruction looks like:
AP######## wires.ap-search ALWAYS
n
See the table in“Notification Priority” on page 299 for more information on these options.