Cameron Blashka | Informer Implementation Specialist Care and Feeding of Informer How to Ensure Long-term Stability with your Informer system PRESENTER: Cameron Blashka | Informer Implementation Specialist April 26 & April 27, 2017

Overview The Informer System Maintenance Tasks Upgrades Log Files Derby Database Tables Routine Backups & Packages Scheduled Restarts

Informer is a Three-Tier System! Database Server Open Connection Connection Pooling Query Execution Selection Web Server Load Results Grouping Script Execution Sorting Normalization Client Machine Render Results AJAX/JavaScript Group Listing

Upgrading Informer Current Version: 4.7.0 Why Bother Upgrading? Bug fixes New features Improved UI Elasticsearch with Dashboards Check the Release Notes!

Upgrading Informer Download the most recent .war upgrade file Client Portal Support Ticket Place inside the ./webapp folder on the Informer server Restart Informer Done! Note: Once you successfully upgrade, you can delete the .war files for the older versions of Informer!

Log Maintenance Useful when encountering errors Always running in the background Can grow huge when gone unchecked Not necessary to log everything at all times

Log Maintenance Verify the Settings Set up Rolling Logs Admin -> Log Settings –> Restore Default Set up Rolling Logs Affects openinformer.log, not servicelog.txt

Log Maintenance Returns the basics of what Informer is doing log4j.logger.com.entrinsik.informer=info Returns what statements are sent to the database (U2) log4j.logger.com.entrinsik.informer.uoj.STATEMENTS=info Returns what statements are sent to the database (SQL) log4j.logger.com.entrinsik.informer.sql.query=DEBUG Returns what comes back from the database (U2) log4j.logger.com.entrinsik.informer.uoj=DEBUG Returns what comes back from the database (SQL) log4j.logger.com.entrinsik.informer.sql=TRACE

Database Maintenance Large tables over time LAUNCHAUDIT JOBHISTORY DATAARCHIVE Most users don’t need content from 20XX and earlier Can be cleaned up via derby command line to reclaim space

Backups Informer database is located in the ./db folder Make frequent backup in case of catastrophic failure The more space you have, the more liberal you can afford to be with backups Scheduled tasks

Packages Useful for specific object backups Reports Datasources Mappings Less useful for full-system backups Be wary of duplication!

Restarts Releases cached items, on both the application and the server Adjusts memory usage on the server Restarted a potentially frozen Scheduler Can be scheduled during confirmed downtimes, like early morning on weekends

Thank you! Any questions?