EuroRunner interfaces with ENOM for outgoing notices and also incoming notices.
Both Transit Notices (to a network operator) and Contract notices (to any other counterparty) can be sent by ENOM.
To set-up EuroRunner to allow sending of notices by ENOM; set the following properties for any of Network, Network Group, Contract or Contract Group:
Then set-up specific templates for the notices to be sent/viewed as using the properties for any of Flange, Point, Journey, Network, Network Group, Contract or Contract Group:
Note: Template selections will depend on object type, there may be custom templates available, you should know when you need to use these rather than the default templates.
If you also wish to send weekly notices, you should complete the weekly sections with the same settings.
When you send a notice within EuroRunner, EuroRunner converts the raw data from the database into XML. This XML is then transformed using XSL into ENOM XML; this is then saved as a file and put into the ENOM inbox folder for ENOM to pick up.
EuroRunner interfaces with ENOM for outgoing notices and also incoming notices. Notices coming from ENOM are placed in the EuroRunner inbox (see File Services).
The ENOM notice receivers run asynchronously under Notice Manager. To be identified as containing an ENOM notice an XML notice must have its main element called <message> for Edig@s v2 messages or <gmsl_enom> for Edig@s v3.
Once identified as being from ENOM Notice Manager identifies if the notice contains Allocations (TDD or TDR for Edig@s v2) or Confirmations (HCN, HDT, TDT, TWT, BRA, BDW, SDA, SWA, SA, BR, MOP, BRO, CB for Edig@s v2, NOMRES for Edig@s v3).
Allocations are processed by the EuroRunnerAR.AllocationReceiverQC component, in the EuroRunnerARQC COM+ Application.
Confirmations are processed by the EuroRunnerCR.ConfirmationReceiverQC component, in the EuroRunnerCRQC COM+ Application.
For sending notices using ENOM, the ENOM inbox must be set-up, it is configurable during the installation of EuroRunner Server, and is stored in the registry (see the ENOM section of the Registry documentation), it can be any fixed, mapped or UNC drive i.e. \\server\share\folder.
EuroRunner is not picking up messages from ENOM.
When ENOM receives a message via FTP, it creates an XML file in a specified folder; this is generally EuroRunner’s inbox. If messages do not seem to be getting through to EuroRunner then there could be a number of possibilities:
ENOM needs to be configured to create XML files when it receives a message i.e. via FTP. To set-up ENOM to generate XML files, open up ENOM and go to Maintenance > System.
If you type in the path name instead of browsing for it, please ensure that the folder exists and that you have read & write permissions on the folder.
The folder location is defined in the registry (see the File Services section of the Registry documentation). EuroRunner looks in the inbox sub-folder of the location stored in the registry.
To check if the registry contains the correct folder location:

EuroRunner cannot send messages to ENOM/ENOM is not picking up outgoing EuroRunner messages, and there are no error messages from EuroRunner/ENOM
As EuroRunner simply creates an XML file in a folder to send messages to ENOM, there is not actually a lot that can fail with this part of the process with regards to ENOM or EuroRunner.
If EuroRunner cannot create the file in the specified location then the most likely causes would be:
The ENOM inbox is defined in the registry (see the ENOM section of the Registry documentation). This value is the path to the folder where EuroRunner will create the XML notice.
To check if the registry contains the correct folder location:

Ensure that this path actually exists; the simplest method is to copy this path then open up Windows explorer and paste it into address bar.
If you are certain the folder actually exists then the problem maybe that the folder is not actually accessible via EuroRunner.
This can sometimes be the issue when the target folder is located on a mapped or UNC network drive. If the drive has not been mapped correctly or the user is not authenticated.
If the folder exists and is accessible but EuroRunner still cannot create the XML file, the problem could be with actual file permissions on the folder.
Ensure that the target folder’s file permissions are set correctly and that the user that EuroRunner is running as (EuroRunnerUser by default unless changed during install) has read & write permissions to the folder.
Messages are getting to ENOM but are not being sent by ENOM
When ENOM receives a message it does a variety of things depending upon what is configured in the settings.
ENOM sends messages it receives from EuroRunner via FTP, there are several places in ENOM that require configuration for the FTP settings. If the FTP settings have not been set up, ENOM will not be able to send the messages.
This screen is the general FTP allow/disallow setting. Tick the Use FTP checkbox to allow ENOM to FTP.
If you require a proxy server to FTP in your network then you can enter a proxy server on this screen also. (Most networks permit FTP'ing therefore do not require a proxy server)
This screen defines exactly which FTP server is contacted and sent messages to.
Each recipient in the Name dropdown list requires:
Once all the settings have been entered click Save.
To configure ENOM to send messages as soon as it receives them from EuroRunner go to the Maintenance > System screen, on the General tab and tick the box called Send Messages Immediately.
When this box is ticked, ENOM will attempt to send the message via FTP to the correct counterparty as soon as it receives a new message.
When ENOM is performing a send/receive, it creates a log to show the process, to view this log, double click on the 4th pane in the status bar of ENOM:
This will display a screen listing the last process that occurred and informing you of any errors that may have occurred.
Note: If no FTP settings have been configured and a send/receive occurs, the process log will still say Getting FTP Lock...Got FTP Lock. This does not mean that ENOM has connected to an FTP server, the FTP lock is simply a database entry which is set when ENOM performs a send/receive.
Message leaving EuroRunner are causing a decode failure in ENOM
When ENOM receives a message that it has problems decoding from XML into its own format, ENOM produces a decode failure. ENOM will display a message box informing you of the file which had the decode problem.
ENOM will create a new file under the ENOM inbox called XMLFiles.log, this file contains a list of all decode problems that ENOM has encountered.
Under the inbox a new folder will be created call XML_Failed, this folder contains the message that failed along with another file with the same name as the failed message with a .LOG suffix. This file contains detailed information about the decode failure i.e:
19 Jul 06 11:54 ENOMSVR [GMSL] : MessageNOMINT01.Unit 'KWH' invalid.
In the example above ENOM has received a message which has an unknown unit, this would be rectified by adding a new unit to ENOM to match the unknown unit then the failed message could be moved into ENOM's inbox, or the message could be resent from EuroRunner.
See the ENOM section of the Registry documentation.