Outgoing email in Tridium Niagara Ax using a Free GMail account

The email OutgoingAccount component is required for sending emails from a station. This component is located in the email palette .

Drag the EmailService from the palette and drop it on the Services group in the tree as shown below.

 

Now click on the plus sign to expand the EmailServices and then double click on the OutgoingAccount to bring up the property sheet.

 OutgoingAccount property sheet view 

The OutgoingAccount has the following properties that need changing from there default settings:

Hostname

This is the name of the mail server. In this example the host name is smtp.gmail.com

Port

This is the port number associated with the email account. Typically email outgoing account port numbers are port "25", however, if you leave the setting at its default value of "-1" the OutgoingAccount will search for and use a valid port. However Gmail uses  a different port , so in the port textbox type 465.

Account

This is the name of the distinct account that is authorized for access to the "Hostname" mail server. For example, if you are using an email account named "jon@gmail.com", your account name is your full GMail address.

Password

This is the login credential for the GMail address specified in the Account field.

Enabled

This field allows you to activate or deactivate the account by choosing true or false, respectively.

Debug

This Boolean property turns Debug mode on true or off, as desired. When Debug is turned on, you can see detailed debug information in a station's standard output view (WorkbenchAX Platform > Application Director view) when the Station tries to send or receive email. This can be used to troubleshoot the accounts and faults.

Use Ssl

The Ssl (Secure Socket Layer) option is available on the OutgoingAccount starting in NiagaraAX-3.5. The option list allows you to disable Ssl (false) or enable it (true). Enable Ssl for communication with a host email server that requires it.

 Niagara-AX, set up your "Outgoing Account" as pictured below:

Be sure to verify your DNS servers are correctly assigned .

To allow Gmail SMTP to work with the Niagara-AX email service, Gmail 2-step verification must be disabled. Please be warned that this will leave your Gmail account more vulnerable to outside intrusion. I recommend creating and utilizing a new Gmail account that will be solely used for SMTP relays.

On the top right, locate the "Account" icon.  Click the "My Account" button.

From the menu, click "Sign-in & Security".

From the menu on the left select Signing in to Google

Locate "2-Step Verification".

  Click the "Settings" hyperlink. To disable 2-Step Varication.

How To Set Eclipse Build Path For Niagara-AX

The Eclipse Niagara Plugin handles editing the Eclipse project build path to include module JAR file dependencies when a new module is created through the New AX Module wizard. It may not always be possible to include a module as a dependency through the wizard.
The Eclipse project Referenced Libraries build path can be set directly from within Eclipse to reference the necessary module JAR files which enable syntax checking in the Eclipse IDE.
To add a module JAR file dependency, right click on the Java project in the Eclipse IDE. In the context menu that displays, select the Build Path option. From this option, select Configure Build Path....

The Properties dialog for the Java project will display. Within this dialog, ensure that the Java Build Path tree menu item is selected and displaying in the main dialog view. Select the Libraries tab from the display tab options. 

From the button panel of the Libraries tab, click the Add Variable... button. The New Classpath Entry dialog will display.  

In the dialog list select the NIAGARA_HOME variable entry. This is the environment variable which points to the Niagara installation on your development platform.
Click the Extend... button. The Variable Extension dialog will display.

From the dialog list, select the modules directory. The module tree will expand to display all module JAR files in the directory.

Select the module you wish to include on the build path by clicking the module. Once selected, click the OK button of the Dialog. The dialog will close.

To save your changes to the Java project build path, click the OK button of the Properties dialog. The build path of the Java project will be updated with the reference to the module JAR file.

Niagara AX Community Modules

The project consists of a library of modules for the Tridium Niagara AX platform distributed under GPL license. AX programmers are encouraged to use and expand the library.

There is a lot of nice stuff in this module from enum to boolean, dropdown menu for px pages and  more. Check it out. 

Download it from source forge:
http://sourceforge.net/projects/niagaraaxcommun/files/latest/download

Chrome says it no longer supports the Niagara ax wbapplet plug-in

Upon a log-in attempt via chrome, wbapplet does not start and the browser states "This plug-in is not supported."

There are changes Java compatibility in Chrome:

NPAPI support by Chrome

The Java plug-in for web browsers relies on the cross platform plugin architecture NPAPI, which has long been, and currently is, supported by all major web browsers. Google announced in September 2013 plans to remove NPAPI support from Chrome by "the end of 2014", thus effectively dropping support for Silverlight, Java, Facebook Video and other similar NPAPI based plugins. Recently, Google has revised their plans and now state that they plan to completely remove NPAPI by late 2015. As it is unclear if these dates will be further extended or not, we strongly recommend Java users consider alternatives to Chrome as soon as possible. Instead, we recommend Firefox, Internet Explorer and Safari as longer-term options. As of April 2015, starting with Chrome Version 42, Google has added an additional step to configuring NPAPI based plugins like Java to run — see the section Enabling NPAPI in Chrome Version 42 and later below.

Enabling NPAPI in Chrome Version 42 and later
As of Chrome Version 42, an additional configuration step is required to continue using NPAPI plugins.

1. In your URL bar, enter:  chrome://flags/#enable-npapi 
2. Click the Enable link for the Enable NPAPI configuration option.
3. Click the Relaunch button that now appears at the bottom of the configuration page.