![]() In many cases, what you can do through the Admin Console GUI you can also do through the Admin API. The Admin API is different from the Admin Console, but I’ll note here the Admin Console uses a version of the same REST API. Personally, I find the constant refreshing of Volume Status and System Statistics - every twenty seconds - distracting, but there appears to be no way to change it. This view provides a more efficient overview of general server status, reducing the number of clicks to get at some basic information. Logging in to the Admin Console lands on a new Dashboard, comprising configuration, drive space, and system performance. This is the same technology as the FileMaker Cloud console, which should make it easier for FileMaker’s engineering team to keep the two products aligned, and for us as administrators to switch between two different contexts. Up until FileMaker Server 16, the browser-based console to which we were accustomed had been built on Java and Ajax, while the new FileMaker Server 17 Admin Console is based on Node.js and Angular. The clean, flat user interface not only looks good, but also provides a modern foundation. This is different than the SSL certificate, and contains details of the exact configuration of the license agreement. Rather than a license key, FileMaker Server now requires a license certificate. Now, after installation and during deployment, you use the Admin Console to configure the server for a particular environment, for example by enabling WebDirect, the Data API, or ODBC / JDBC. For example, by default only FileMaker Pro Advanced and FileMaker Go have access to a server. Where before there was a multi-step deployment assistant, now there are more defaults. ![]() Installation of FileMaker Server 17 is very streamlined. Admin Console is still the front end to an on-premise server this is not a strictly cloud-based product (though you could host FMS on an AWS EC2 instance or similar).The FMS 17 Admin Console still makes available FMS-only features like scheduled scripts and directory authentication FileMaker Cloud requires use of the Admin API to schedule scripts, and directory authentication is not available at all.One still accesses Admin Console on port 16000 (remote) or 16001 (local).Before we explore these changes, let’s first briefly review some key points that remain unchanged. That being said, some of the capabilities to which we are accustomed have moved within the GUI, others are accessible from only the command line or Admin API, and a few have been removed altogether. Principally, FileMaker Server still provides developers and administrators the on-premise deployment features on which we rely. While at first glance it appears similar to the FileMaker Cloud console, FileMaker Server is best approached as a different product with a different feature set. The FileMaker Server 17 Admin Console is the new graphical user interface to FileMaker Server (FMS) many administrative functions are also available via the command line interface (CLI) and Admin API. FileMaker Server - Reliable For On-Premise Deployment Summary: Like a souped-up, redesigned car-this year’s model-heading into an open mountain track, you’ll want to take it slow at first, but once you get familiar with the new navigation and “steering”, you should find the FMS 17 Admin Console a delight to drive. While FileMaker provides an excellent overview of the differences, here I will highlight changes that affect us most here at Beezwax and some adjustments we’re making to compensate. However, the update also brings some of the biggest changes in administrative functionality in years, perhaps ever. If you are familiar with the FileMaker Cloud console, you’ll feel right at home in the new FileMaker Server 17 Admin Console. ![]() Changes in FMS 17 Admin Console and How We’re AdaptingįileMaker Server 17 introduces a new generation of Admin Console, refreshed, fast, and reliable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |