...
The SMTP Transport Adaptor (hereinafter the SMTP adaptor) is intended to send FIX messages from FIXServer to from FIXEdge server to clients using SMTP protocol.
...
Note that all changes in properties file are applied only after FixEdge FIXEdge restart.
Integration with
...
FIXEdge
Execute the following steps to integrate the SMTP adaptor into the FixEdgeFIXEdge:
- Open the FixEdge FIXEdge properties file (FIXEdge.properties by default).
- Find 'TransportLayer.TransportAdapters' property
- Add 'TransportLayer.TransportAdapters' property in case it does not exist
Set 'TransportLayer.SmtpTA' to the value of 'TransportLayer.TransportAdapters' property:
Code Block language xml TransportLayer.TransportAdapters = TransportLayer.SmtpTA
If 'TransportLayer.TransportAdapters' property already has a value - append ',TransportLayer.SmtpTA' to the value:
Code Block language xml TransportLayer.TransportAdapters = ...,TransportLayer.SFSAdaptorDLL,TransportLayer.SmtpTA
Add 'TransportLayer.SmtpTA.Description' property with value - SMTP adaptor name:
Code Block language xml TransportLayer.SmtpTA.Description = SMTP Transport Adaptor DLL
Add 'TransportLayer.SmtpTA.DllName' property with value - path to the SMTP adaptor dll:
Code Block language xml TransportLayer.SmtpTA.DllName = bin/SMTPAdaptorDll.dll
Add 'TransportLayer.SmtpTA.Type' property with 'DLL'value:
Code Block TransportLayer.SmtpTA.Type = DLL
Add the set of default properties:
Code Block TransportLayer.SmtpTA.SMTPSessions.DefaultServerName = mail.test_test.com TransportLayer.SmtpTA.SMTPSessions.DefaultServerPort = 25 TransportLayer.SmtpTA.SMTPSessions.DefaultSendingTimeout = 10 TransportLayer.SmtpTA.SMTPSessions.DefaultConnectionTimeout = 10 TransportLayer.SmtpTA.SMTPSessions.DefaultSmartEmailProcessing = false
Add 'TransportLayer.SmtpTA.SMTPSessions property with value - the set of SMTP client's names:
Code Block TransportLayer.SmtpTA.SMTPSessions = TestSmtp
Add properties for each client, like this:
Code Block TransportLayer.SmtpTA.SMTPSession.TestSmtp.ServerName = mail.test_test.com TransportLayer.SmtpTA.SMTPSession.TestSmtp.ServerPort = 25 TransportLayer.SmtpTA.SMTPSession.TestSmtp.To = jsg@test_test_btobits.com TransportLayer.SmtpTA.SMTPSession.TestSmtp.From = jsg@test_test_btobits.com TransportLayer.SmtpTA.SMTPSession.TestSmtp.CC = TransportLayer.SmtpTA.SMTPSession.TestSmtp.BCC =
- Restart FixEdge the FIXEdge server to apply changes.
After changes are applied, the FixEdge FIXEdge properties file may look like this:
...
By default the SMTP adaptor puts log messages into the FIXEdge log. Execute the following steps to configure the SMTP adaptor logging into a separate file:
- Open FixEdge the FIXEdge properties file
Add 'Log.SmtpAdaptorTransportLayer.SmtpTA.File.Name' property with value - path and name of the SMTP adaptor log file.
Code Block Log.SmtpAdaptorTransportLayer.SmtpTA.File.Name = SMTP.log
Restart FixEdgeFIXEdge server
When the SMTP adaptor starts the following record will be written into the log file (xxx is the SMTP adaptor version):
...
Troubleshooting
Problem | Solution |
---|---|
FixEdge FIXEdge start fails and the FixEdge FIXEdge log file contains the following record: [FATAL] 20070215-11:42:25.250 - Transport Layer has failed to initialize: Error loading DLL './/../SMTPAdaptorAddin.dll '. : The specified module could not be found. (126) | FixEdge FIXEdge is unable to find the SMTP adaptor library file. Make sure that 'TransportLayer.SmtpTA.DllName' contains valid path and name. |
FixEdge FIXEdge start fails and the FixEdge FIXEdge log file contains the following record: [FATAL] 20070215-11:45:12.312 - Transport Layer has failed to initialize: Cannot find the 'TransportLayer.SmtpTA.XXX' property. | The SMTP adaptor was not configured properly. The required 'TransportLayer.SmtpTA.XXX' property does not exist in the FixEdge FIXEdge property file. |
FixEdge FIXEdge is started but the FixEdge FIXEdge log file does not contain the 'SMTP Adaptor v.xxx started' record. | Make sure that the SMTP adaptor was configured properly in the FixEdge FIXEdge property file:
Make sure that the FixEdge FIXEdge log file does not contain any related error messages. |
...