The NovoMotion Interface Control is used by system administrators to configure the operation of the NovoMotion interface. Once the user has logged in through the NovoMotion U2 Login, the user will have access to the NovoMotion Interface Control.
The first display of the Interface Control allows for stopping and starting of the interface phantom. Note that it also displays the maintenance expiration date.
If the Start Phantom is highlighted, the interface is not running. Conversely, the Stop Phantom button will be highlighted when the interface is operational.
The Service Phantom Status shows any auxiliary phantoms that are executing to process specific files.
NOTE: If the interface phantom is stopped, the service phantoms will continue on to completion of their current task. If an administrator does not want to wait for the service phantom to compete, they would use normal U2 logoff functionality to stop the process. This would most often occur if a batch load of data was occurring and a system reboot was deemed necessary.
The Edit Settings button can be used to set up information about how the user wants the phantom to run.
Load Auth Codes is used when new authorization codes need to be added.
|Days of Operation||Used to set/exclude specific days from the phantom process|
|Polling Frequency||Nbr of seconds between invocations of the phantom|
|Max Worker Phantoms||Process will spawn up to n phantoms based on this setting|
|Maximum Work Size||Used to control maximum records before delay|
|Error Interval||Nbr of seconds between error checks|
|Error Action||Indicator if errors should be moved to quarantine, deleted, or re-processed|
|Error Log Level||Used to control level of records that write to the event log - At start-up this is set to 0 so all events are logged. Once any issues are resolved, it should be set to a higher number.|
|Action File||Used to set the maximum work file size for the Action file.|
|Quarantine File||Used to set the maximum work file size for the Quarantine file.|
|Disable All Triggers||Checkbox used to stop the write of ACTION records - even if triggers exist.|
|Original File Name||Used to convert file names when writes occur across accounts. For instance - say that you update the IPL file from one main account using a VOC pointer to another account. One would use this set of fields to push the action to the correct account for the correct name.|
|New File Name||This in the file name that the Original File Name will become.|
|Output Action File||This is the file name in the sending account for the action file in the receiving account.|
|Table Master Include||This is used indicate which TM tables are being sent. If a trigger is enabled for the TM file, this information is used to limit the action records to only those TM tables that are being sent to the SQL server.|
|From Email||Used to easily identify emails from the interface.|
|Notification Group||Shows potential notification groups set up through EXCHANGE|
|Refresh/Display Interval||Used to set number of seconds before refresh of the information in the Interface Control.|
Commands to execute during UniQuery execution of the NovoMotion phantom:
This is used for specialized operating system commands. Please contact NovoRoi Systems for further information.