CRM vs NRCS

Basically a system will be sufficient for working  if it already has proper amount of market share. The most important key is how to deploy it to your users. For example, NRCS is News / Reporter management, and CRM is Customer / Sales management. You can even run a CRM with NRCS concept. IT staff only needs to survey a popular, recent solution that can run on modern machines and devices.

NRCS: server admin

• Corosync, Java, PostgresQL (packages)
• server.log (Admin Guide)
• /(app root)/server/data (uploaded files)

NRCS: log checks

The best tool to use for reading the octopus logs is the LogReader most of the time located under /octopus/tools/LogReader. Logs include server side and client side logs.

API.log

calls to REST API are logged here, which are the calls from Mobile/Table clients as well

AS.log

ActiveSync - subscription to lists, i.e. wires, stories, etc

autoActions.log

automatic actions - create, archive, delete, etc.

clientErrors.log

client errors sent from the clients to the server

clients.log

number and list of active desktop clients

...and more. referred to the Admin Guide.

NRCS: MOS agents and devices

There might be just one MOSAgent handling multiple MOS devices, or one MOSAgent per MOS device. First solution is less RAM consuming and also is
used when some MOS devices should work on the same ports as you can not have two or more services running on the same ports. Advantage of the
second solution is that you can start/stop or restart daemon only for one particular MOS device, but it consume more RAM. So it is up to your
preferences. The second solution is recommended.

NRCS: action tracking

• Who edited particular story?
• Who edited the rundown?

For Octopus, Login to the octopus server and open the simpleLogger.log located under /octopus/server/log/%date%/ and search for the particular changes.