NOM Maintenance (Maint)

The NOM Maintenance (Maint) application purges expired data, synchronizes global tables from the Central Server and writes changes to the field definitions tables to the Solr schema file. NOM Maintenance resides on the same physical server as the News Object Manager (NOM).

The separate NOM Buddy Maintenance application synchronizes data between the Primary and Buddy Server.

Adjusting NOM Maintenance Processes

There are three processes that may need fine-tuning to run certain tasks when it's the least busiest time for your users:

Delete Expired Items time in NOM Maintenance.
Folder Info time in NOM Maintenance.
NOM Web Services Application Pool recycle time in Internet Information Services (IIS) Manager.

By default, ENPS sets these to 2:00am local time. However, this time may not be the least busy time for your users and may cause disruptions. Think about your show schedule and when is least busy in your newsroom. You must ensure that the three processes are not running on your Primary Server at the exact same time they are running on your Buddy Server:

Field	Primary Server	Buddy Server
NOM Maintenance > Delete expired items each day at	non-busy time	some time later
NOM Maintenance > Scan folders each day at	non-busy time	some time later
IIS > Recycling Settings > Specific time(s)	non-busy time	some time later

In the example below we'll use the following times, with no overlap between the Primary Server times and the Buddy Server times:

Field	Primary Server	Buddy Server
NOM Maintenance > Delete expired items each day at	00:30:00	03:00:00
NOM Maintenance > Scan folders each day at	02:00:00	04:30:00
IIS > Recycling Settings > Specific time(s)	12:05 AM	2:50 AM

If you adjust the NOM Maintenance times you may also need to adjust the create times of any rundowns that are autocreated.

Rundowns should not be set to autocreate within the same hour as the Delete expired items each day at field on the Primary Server. For example, if Delete expired items each day at is set to 00:30:00 (12:30am) on the Primary Server, then no rundowns should be set to autocreate from 12:30am to 1:30am.

Step 1 - Set Times on the Primary Server

Open NOM Maintenance on the Primary Server.
Open Window > Delete Expired Items.
Set the value of the Delete expired items each day at field.

In our example, we set it to 00:30:00 (which is 12:30am).

Delete expired items each day at must be a 24-hour clock value in the range 00:00:00 to 23:59:59.
Open Window > Folder Info.
Set the Scan folders each day at field.

In our example, we set it to 02:00:00 (which is 2:00am).
Open Internet Information Services (IIS) Manager on the Primary Server.
Expand the server name in the Connections pane and click Application Pools.
Right-click NOMWebServiceAppPool and select Advanced settings from the popup menu.
Set the value of the Specific time(s) field.

In our example, we set it to 12:05 AM.

If your server is on a 24 hour locale then this number will be automatically converted to a hh:mm format. In this example, 12:05 AM will be converted to 00:05.

Step 2 - Set Times on the Buddy Server

Now set the same fields on the Buddy Server, but later than those set on the Primary Server so there's no overlap.

Field	Primary Server	Buddy Server
NOM Maintenance > Delete expired items each day at	00:30:00	later
NOM Maintenance > Scan folders each day at	02:00:00	later
IIS > Recycling Settings > Specific time(s)	12:05 AM	later

Open NOM Maintenance on the Buddy Server.
Open Window > Delete Expired Items.
Set the Delete expired items each day at field to a time that's different to what is set on the Primary Server.

In our example, we set it 03:00:00.

Delete expired items each day at must be a 24-hour clock value in the range 00:00:00 to 23:59:59.
Open Window > Folder Info.
Set the Scan folders each day at field to a time that's different to what is set on the Primary Server.

In our example, we set it to 04:30:00.
Open Internet Information Services (IIS) Manager on the Buddy Server.
Expand the server name in the Connections pane and click Application Pools.
Right-click NOMWebServiceAppPool and select Advanced settings from the popup menu.
Set the Specific time(s) field to a time that's different to what is set on the Primary Server.

In our example, we set it to 2:50 AM.

If your server is on a 24 hour locale then this number will be automatically converted to a hh:mm format. In this example, 2:50 AM will be converted to 02:50.

The fields are now set to the example times:

Field	Primary Server	Buddy Server
NOM Maintenance > Delete expired items each day at	00:30:00	03:00:00
NOM Maintenance > Scan folders each day at	02:00:00	04:30:00
IIS > Recycling Settings > Specific time(s)	12:05 AM	2:50 AM

Even though the Buddy Server times 3:00am and 4:30am are likely slightly busier time in the newsroom, this will not be an issue. The important factor is ensuring that the Buddy Server times are different from your Primary Server times, with no overlap.

If you wanted to further space out the times that the three processes run on the Primary Server compared to the Buddy Server, you could have them run in the afternoon on the Buddy Server. For example, you could set Delete expired items each day at to 13:30:00 (which is 1:30pm), and Scan folders each day at to 15:00:00 (which is 3:00pm):

Field	Primary Server	Buddy Server
NOM Maintenance > Delete expired items each day at	00:30:00	13:30:00
NOM Maintenance > Scan folders each day at	02:00:00	15:00:00
IIS > Recycling Settings > Specific time(s)	12:05 AM	2:50 AM