NOM.ini Settings

If enabled, allows the News Object Manager to break UDP packets into smaller sizes when the packet is larger than the value set in MaxUDPSize. If the packet is larger than the value in MaxUDPSize, and this setting is not enabled, the update will not be sent.

Specify whether changes to a user's personal folder are broadcast to other workstations. This is desirable if a user is working on multiple machines. If this setting is enabled it will be enabled for all of the users on the server.

If you are experiencing issues with the Web Service being unable to connect to the NOM at times when the NOM is in the middle of a resource-intensive operation (such as freezing page numbers in a long Rundown), you may experience errors in the Event Viewer and/or users being unable to establish any connection with the server.

This setting will allow you to increase the number of incoming socket connections the NOM can buffer while it is "busy." Changing this setting will require a restart of the NOM.

Incoming wires are in English.

Number of times the NOM will re-send UDP packages to ensure that they are received by the client. The client ignores redundant messages. This option will increase network traffic.

Maximum size of UDP packets for the NOM to send. If this value is set higher than the settings for your routers or switches, users may not receive dynamic updates in the client.

Specify the number of minutes after the NOM starts that it will begin processing AutoCreates.

Number of seconds to wait between creating Rundowns for the AutoCreate process.

Determines if the NOM sends UDP broadcast messages into the local subnet.

Send Top Line Messages as UDP broadcasts instead of point-to-point messages provided that this option is supported by your site's router. This allows users to see their Top Line Messages on each machine if they are logged into multiple client workstations.

Specifies whether to use the Buddy Server. The Buddy Server should be disabled when maintenance is being performed on it.

NetBIOS name of your Central Server.

Refer to Choose Central Server for more information.

Allows ENPS users to connect to the server, even if Solr is not running.

Although search is impacted in ENPS, a failure of the Solr service will not affect other ENPS functionality.

Determines whether the NOM waits for the Solr ENPS core to complete start up before allowing client connections.

Instructs the NOM to sort folder items more quickly when there are large number of items such as MOS object folders.

The NOM uses this method automatically if a folder contains more than 32,000 items.

Ensures that the <itemUserTimingDur> field is removed from a story when a user clears the values in the MOS User Duration column.

If enabling this setting, change the NOM.ini on all ENPS servers that use a Chinese locale.

Maximum number of running Winsock controls with closed connections. If this limit is reached a warning is logged and excess controls are unloaded.

Number of days to preserve Top Line group or personal messages before they are deleted during maintenance.

Configure a server to operate as a MOS Repeater.

See Build a MOS Repeater for more details.

Interval in hours to write information from the NOM Statistics and MOS Status windows to the NOMSTATS log file in NOM\LOGS.

Instructs the NOM to ignore roReq messages for Rundowns which have the MOS Control Active checkbox selected since MOS object updates will be sent automatically.

For more information on MOS Protocol messages refer to http://www.mosprotocol.com.

Number of minutes before the NOM closes unresponsive connections.

Enable Trace logging.

Trace log file creates a log of all of the communications that take place between the NOM and the client workstations. The log is stored in \NOM\LOGS\TRACE.LOG on the ENPS WORK drive.

Use the new version of MOSXMLizer rather than the legacy version. The new version uses a new HTML control that may improve the efficiency of MOS-activated rundowns.

Default behavior when this setting is missing from NOM.ini:

• Disabled if multithreading is off.

• Enabled if multithreading is on.

Number of simultaneous connections before a warning is logged.

If a MOS device creates too many connections it may indicate a problem with the device.

This setting must be enabled in both the NOM.ini Settings and News Wire Profiler Settings.

Controls whether the NOM Watch starts an ENPS server component automatically. Do not modify this field unless instructed to do so by ENPS Support.

Delay in milliseconds between NOM Maintenance (Maint) operations.

Number of days before MOS logs are purged. Note that once MOS connections are working properly, it is not necessary for MOS traffic be logged routinely. Logging can be turned on or off from the NOM application's MOS screen as needed.

Names of the global tables that will not be synced with the Central Server, separated by semicolons. Exclude specific global tables from syncing with your site’s Central Server. This setting should only be used for diagnostic and testing purposes and after speaking to the ENPS helpdesk.

Determines whether the ENPS Client adjusts the roEdStart tag in an roCreate message based on Daylight Savings Time.

By default, the ENPS Client adjusts roEdStart to reflect the local time automatically. For example, if a newscast's Editorial Start Time is 17:00 and the local server is in Eastern Standard Time, ENPS would send the MOS device an roEdStart of 22:00. During Daylight Savings Time the server would send the MOS device an roEdStart of 21:00.

You can also set the ENPS Client to not adjust the time automatically. This may be necessary for backward compatibility with some MOS systems that are set to receive an unadjusted time in roEdStart.

For more information on MOS Protocol messages refer to http://www.mosprotocol.com.

Interval in seconds for the NOM to attempt to contact a non-responsive MOS device.

Enforce rigorous XML validity checking on incoming MOS messages. This option is disabled by default for compatibility with devices that use older versions of the MOS protocol.

Number of seconds for MOS devices to time out their connections. You can override this setting for specific devices by using a MOS Timeouts property.

Set a timeout value for a specific MOS device by entering its fully qualified MOS ID and setting it equal to a timeout value from 1 to 60 seconds. For example: aveed.server2.camden.wtn.mos=15

If a MOS device is not listed under [MOS Timeouts] in the NOM.ini file, the ENPS Client will use the default timeout value specified in the MOS Timeout property.

No longer used. Refer to the ENPS API Documentation for information about publishing from ENPS.

No longer used. Refer to the ENPS API Documentation for information about publishing from ENPS.

No longer used. Refer to the ENPS API Documentation for information about publishing from ENPS.

No longer used. Refer to the ENPS API Documentation for information about publishing from ENPS.

No longer used. Refer to the ENPS API Documentation for information about publishing from ENPS.

No longer used. Refer to the ENPS API Documentation for information about publishing from ENPS.

Maximum size in bytes for the WALKCS.DAT file, between roughly 4MB and 100MB.

This file is used by the WalkCS application to track which files have been compounded.