You can control the look and feel of the web interface by changing the template that the interface uses. The template is normally placed at \Program Files\Easy Automation\templates\WebserverTemplate.xml, but you can change that by changing the 'Web Server Template' setting. For information on changing settings see Settings. The WebserverTemplate.xml is a standard Easy Automation template file. For more information on how template files work you see Templates.

There are a number of variables in the template whose values are automatically filled in, and the purpose of the template is to surround those values with html. Here is a list of the values and what they contain.

• content - the main content of the page that will be displayed. This includes the list of scripts, or messages, or whatever the current page is about.
• programName - the name of the application (Easy Automation)
• version - the version of Easy Automation.
• computerName - the name of the computer serving up the web interface.
• current time - the time the page was generated.
• current date - the date the page was generated.
• menu - the menu for the current page being displayed.
• pageName - the name of the page name being displayed.
• help - instructions on how to work with the current page.

All of the elements generated by easy automation have classes set on them that can be used to manipulate the look of the page using a CSS file. Two CSS files ship with Easy Automation. One called desktop.css and one called mobile.css. Using the default template the mobile.css file will only be used if the max width of the device rendering the page is 480 pixels wide or less. Every class used in the UI is defined in desktop.css even if the file does not modify the class, so you can use that file as a reference for all the classes used.

The templates are loaded when the Script Manager starts up. If you make changes to a template the changes will not take place until the script manager is shut down and then restarted.

The Web Server Certificate Used for HTTPS Connections

The other thing you may want to change related to the web interface is the certificate used if you want to access the server using https. The certificate is specified with the 'Web Server Certificate Path' setting. The default certificate is in the modules path and is athyrium.pem. It is a self signed and totally bogus certificate. You can change this with a real certificate that matches the computer the service is running on if you like. If you write scripts that catch http requests, those triggers will also use this same certificate if they are setup to use https as well. See the 'When a web page is requested' trigger in the Easy Automation Editor for more information.

The E-mail Template

There is a second template that can also be customized. That is the EmailTemplate.xml. That template is used to format e-mails from the Script Server. Most of the fields for that template are the same as for the web server template. The fields that are different are...

• content - for this template it is the body of the email.
• log level - the log level of the log message being sent, which may be empty if the e-mail is not about a log event.
• log time - the time the log message occured, which may be empty if the e-mail is not about a log event.
• log computer name - the computer that sent the log message, which may be empty if the e-mail is not about a log event.
• port - the port the webserver is running on, on the central server.
• log file name - the filename for the log file on the computer, which may be empty if the e-mail is not about a log event.