The long-awaited v2017.1 has been released and is now available both for licensed customers and for those who are still in the evaluation phase.
The new release is packed full of new features including new event monitors, personal dashboards, new dependency options, new dashboard panel types and much more.
Two of the biggest changes are the move to 64-bits and a new high-performance database that replaces our previous file-based data store.
The move to 64 bits has the biggest impact and there are some things you should be aware of. First, if you have the FrameFlow interface running on IIS, you’ll need to change a setting in your application pool. An IIS application pool can support 32-bit applications or 64-bit applications but not both at the same time. Now that FrameFlow is a 64-bit app you’ll need to go to the advanced settings for your application pool and turn off the option for 32-bit support. During setup, the configuration utility will provide complete details about the required steps.
Second, if you have ODBC event monitors you’ll need to redefine your data sources as 64-bit DSNs otherwise the new 64-bit FrameFlow service won’t be able to see them. Similarly, if you are using our Oracle event monitor you will need to install the 64-bit Oracle Client otherwise your event monitors will not be able to connect.
There’s one more thing you should know about the move to 64 bits. First, expect to see the FrameFlow services use more memory than before. It’s now typical to see memory usage in the region of 1GB which is still not a lot in modern times but probably more than you’re used to seeing. If you’re running FrameFlow in a virtual machine with a tight memory limit, consider allocating a bit more RAM for the VM.
Sign up now to get our monthly newsletter, all about server and network monitoring, delivered to your inbox once per month.