Page Comparison

...

1. configure the SMTP transport adaptor (TA);
2. create a business rule for notifications forwarding.

The SMTP TA is configured in the FixEdge.properties file.

The configuration section for the SMTP the SMTP TA usually exists in the FixEdgethe FixEdge.properties file by default – so it is required just to specify the correct ServerName, To, and From properties:

...
# SMTP server host. Required when DefaultServerName not defined
TransportLayer.SmtpTA.SMTPSession.TestSMTPClient.ServerName = mail.test.com
TransportLayer.SmtpTA.SMTPSession.TestSMTPClient.To = user@test.com;
TransportLayer.SmtpTA.SMTPSession.TestSMTPClient.From = user@test.com;
...

Once the SMTP the SMTP TA client is configured in the FixEdgethe FixEdge.properties file, you could reference it in the BL_Configuration.xml config file.

Actually, once the session changes its state, a fake FIX message (35=C) is generated by the FIXEdge the FIXEdge and routed to the Business Layer.

There are such entries in FIXEdge logs:

2015-03-26 15:18:12,413 UTC   TRACE   [BL_Layer]  140009470453504  Process incoming message. [8=FIX.4.4 9=189 35=C 49=fake 56=fake 34=1 52=99990909-17:17:17 164=7 94=0 42=20150326-15:17:09
147=[NOTE] FIXEDGE:ICEProxy Established 33=5 58=N 58=1 58=FIXEDGE:ICEProxy 58=Established 58=AttemptToConnect 10=238 ]

The tag 147 is automatically filled by the pattern: [<Category>] <SenderCompID:TargetCompID> <Actual Session state>

So you should create a BL rule that will forward such notifications to the SMTP the SMTP client.

The example of such a rule:

...

This rule sends the notification to the SMTP the SMTP client if any of configured FIX sessions changes its state.

...