Deploy. A step-by-step guide to successfully deploying your new app with the FileMaker Platform

Transcription

1 Deploy A step-by-step guide to successfully deploying your new app with the FileMaker Platform

2 Share your custom app with your team! Now that you ve used the Plan Guide to define your custom app requirements, and used the Create Guide to build your custom app, you re ready to consider hosting options. It s time to evaluate your needs and determine what hosting platform is best for you and how to deploy on your preferred choice. This guide walks you through the steps of deploying your custom app using the FileMaker Platform.

3 Share your custom app using the FileMaker In this guide Build a custom app Platform This ebook is the last in a three-part series which covers steps for deploying a custom app using the FileMaker Platform. Use this guide to help decide which products you ll need to successfully deploy your custom app with your team. Use the FileMaker Platform Determine deployment strategy Deployment on FileMaker Cloud. 17 Deployment on FileMaker Server. 23 Considerations for system administrators

4 The steps to building Three principles to help you build a custom app a custom app Building a custom app starts with three principles. Plan Create Deploy These principles, illustrated in three separate guides, lead you through the process of creating a custom app that transforms the way you do business. Explore what you can do with custom apps. Start with Plan. The FileMaker Custom App Success Framework Develop your custom app with Create, a stepby-step guide to working with the FileMaker Platform. 4 Put your custom app into action. Learn how to make it available to your team with Deploy.

5 Use the FileMaker Platform Your FileMaker apps are hosted on either FileMaker Cloud or FileMaker Server. FileMaker Pro and FileMaker Pro Advanced allow you to connect from Mac or Windows desktops. FileMaker Go enables you to connect from ipad and iphone devices. FileMaker WebDirect lets you use your hosted app via a web browser. FileMaker Cloud FileMaker Server FileMaker Go FileMaker Pro FileMaker Pro Advanced FileMaker WebDirect 5 NOTE: FileMaker Cloud is currently available in the United States, Canada, Europe, Middle East, and Africa.

6 - Build a custom app Determine deployment strategy This ebook is the last in a three-part series which covers steps for deploying a custom app using the FileMaker Platform. Use this guide to help decide which products you ll need to successfully deploy your custom app with your team. - Use the FileMaker Platform - Determine deployment strategy - Deploy on FileMaker Cloud - Deploy on FileMaker Server - Considerations for system administrators 6

7 Deployment strategy The term deployment refers to the various technologies and techniques developers use to make apps available to users. It also refers to the standard practices and procedures by which a hosted FileMaker app is maintained and kept running. Developing your deployment strategy is an integral part of designing an app and should be done early in the design process. 7

8 What is a hosted file? Hosted files allow many people to see and share the same data. Hosted files allow you to securely share information among FileMaker Pro, FileMaker Go, and FileMaker WebDirect users. FileMaker Cloud FileMaker Server With a hosted file, you can: - Monitor and administer custom apps - Automate backups for disaster recovery - Secure your data via SSL encryption FileMaker Go FileMaker Pro FileMaker Pro Advanced FileMaker WebDirect - Provide robust scalability and network resilience - Deploy interactive apps to the desktop, ios, and the web - Troubleshoot with statistics and logs - Integrate with ODBC/JDBC 8

9 Deploying FileMaker Apps: FileMaker Cloud or FileMaker Server Decide what s right for you FileMaker Cloud FileMaker Cloud offers the simplicity, performance, and reliability you expect with FileMaker Server without having to spend time and resources deploying and maintaining a server. FileMaker Cloud offers minimal administrative overhead, low up-front costs, speedy deployment, and instant scalability. Easily share information with your team in the cloud. FileMaker Cloud provides secure, reliable access to your custom apps. FileMaker Server FileMaker Server is fast and reliable server software for securely sharing and maintaining custom apps. It is a separate software application that runs on a dedicated machine, offers 24-hour access, automatic backups, and robust security features. If you require use of PHP for web publishing, you should use FileMaker Server. You may want to stay with FileMaker Server if you are currently using it and it s working for you. 9 Compare FileMaker Server with FileMaker Cloud FileMaker Cloud FileMaker Server

10 What are the benefits of FileMaker Cloud? FileMaker Cloud offers: - Minimal administrative overhead - Low-up front costs - Speedy deployment - Instant scalability - SSL/TLS level encryption - Auto-maintenance to keep your system fine-tuned - Automatic backups for disaster recovery - An Admin Console for easy viewing of your system and custom app performance - Proactive notifications of system performance, capacity usage, and update availability FileMaker Cloud - AWS authentication support via OAuth 10 FileMaker Cloud FileMaker Cloud FAQ FileMaker Cloud Technical Specifications

11 Is FileMaker Cloud for you? Can you identify with one or more of these situations? You have to control up-front expenditures on hardware You don t have enough administrative resources for ongoing server maintenance You have immediate or seasonal needs to scale your deployment You want to protect your data by storing it offsite in case of an emergency If you answered yes to any of these scenarios, then FileMaker Cloud is for you. 11 FileMaker Cloud FileMaker Cloud FAQ FileMaker Cloud Technical Specifications

12 What are the benefits of FileMaker Server? With FileMaker Server you can: - Monitor and administer custom apps remotely - Automate backups for disaster recovery - Schedule your scripts - Secure your data via SSL encryption - Provide robust scalability and network resilience - Deploy interactive apps to the web - Troubleshoot with statistics and logs FileMaker Server - Integrate with ODBC/JDBC - Use Custom Web Publishing with PHP 12

13 Consider external SQL data sources for FileMaker Cloud and FileMaker Server Consider data sources for FileMaker Cloud The following ESS data sources are supported by FileMaker Cloud and FileMaker Server: - MS SQL Server MS SQL Server MS SQL Server 2012 SP1 - MySQL Community Edition (free) The following Linux ODBC drivers are supported by FileMaker Cloud: - Microsoft ODBC Driver 11 for SQL Server (version , 64-bit) - MySQL Connector/ODBC (version 5.2.5, x86, 64-bit) - Oracle Database 12c Release 1 Client (version , 64-bit) - Oracle 12c R1 - Oracle 11g R2 FileMaker Server also supports: - IBM i 7.1 (AS/400) (via Actual Technologies Adapter) - IBM DB (via Actual Technologies Adapter) - PostgreSQL (via Actual Technologies Adapter) 13

14 Determine authentication method Choose an authentication method FileMaker Pro allows you to define local accounts, or to use external accounts that employ external authentication through Open Directory and Active Directory. Consult with your IT team to determine the best method. Obtain SSL certificate FileMaker products include SSL certificates for testing use only. For production environments, you need to purchase a compatible custom 3rd-party certificate. FileMaker Cloud provides a 90-day trial Comodo SSL certificate. You can renew the Comodo certificate by clicking the renewal link in the FileMaker Cloud Admin Console, or import a different custom certificate. You must purchase the SSL certificate from the certificate authority. 14 FileMaker Network Security and SSL Supported SSL Certificates Encryption at Rest Support for Encrypted Passwords

15 Extending the availability of your apps Type of clients Tested Theoretical* Host is FIleMaker Server Host is FileMaker Cloud FileMaker Pro Yes Yes FileMaker Pro (for User Connections) Yes Yes FileMaker Go Yes Yes FileMaker WebDirect Yes Yes Custom Web Publishing (CWP)** Yes No FileMaker Data API Yes No ODBC/JDBC Yes Yes *Connections are limited only by hardware, app design, operating system, or license agreement. ** CWP is based on simultaneous request events, rather than persistent connections. 15

16 - Build a custom app Deployment on FileMaker Cloud - Use the FileMaker Platform - Determine deployment strategy - Deployment on FileMaker Cloud - Deployment on FileMaker Server - Considerations for system administrators 16

17 To use FileMaker Cloud you need to: Purchase FileMaker Cloud software AND - Bring your own license (BYOL) from FileMaker purchased on an annual basis billed annually with connections available in the following tiers: 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 75, and Buy license from AWS on an hourly or annual basis billed monthly or annually with connections available in the following tiers: 5, 10, 25, and 100 Purchase AWS services - FileMaker Cloud requires the purchase of Amazon EC2 - All purchases come with 40GB of Elastic Block Storage with additional storage available for purchase. - Data transfer from AWS to the Internet is billed based on usage. - First 1,000 notifications each month are included in your purchase. s in excess of 1,000 a month are billed based on usage. - AWS services are billed separately by AWS on a monthly basis 17 How to Buy AWS Services FileMaker Cloud software

18 FileMaker Cloud purchasing options Select one of the four purchase options for FileMaker Cloud Bring Your Own License (BYOL) or Buy from AWS Buy a new license from FileMaker, Inc. Bring your existing annual license via BYOL to AWS Convert your existing perpetual license and bring it to AWS Buy a new license from AWS Marketplace How to Buy Purchase Process

19 AWS service considerations Amazon EC2 - Virtual computing environment for running your custom app. - Instance size needed varies depending on the amount of processing power, memory, and networking capacity needed to run your custom apps. Elastic Block Storage (EBS) - All purchases come with 40 GB. Additional storage is available for purchase and comes in increments of 20 GB. - Used for the primary live version of your custom app, configurations files, plug-ins, and any other configuration information. - Used for saving point-in-time backups, called snapshots, of your data. Data transfer - The transfer of data from AWS to the Internet, called data transfer out. - Data transfer is billed based on usage and can vary month by month. s - Notifications sent from the FileMaker Cloud Admin Console. - First 1,000 notifications each month are included in your purchase. - s in excess of 1,000 a month are billed based on usage. 19 AWS Services

20 FileMaker Cloud backups Automatic backups when auto-maintenance is enabled, a backup is created and preserved automatically every day. Also, manually create and preserve backups at any time. Restore data from any preserved backup or from just a single file or a specific set of records within that backup. 20 AWS Services

21 FileMaker Cloud in videos 21 FileMaker Cloud FileMaker Cloud FAQ FileMaker Cloud Getting Started Guide

22 - Build a custom app Deployment on FileMaker Server - Use the FileMaker Platform - Determine deployment strategy - Deployment on FileMaker Cloud - Deployment on FileMaker Server - Considerations for system administrators 22

23 Determine the best server deployment When you install FileMaker Server, you ll install three things: 1. Web Server engine 2. Web Publishing Engine 3. Database Server You are given a choice whether to install all three components on one machine, or to install the web pieces on a separate machine. Consider installing both the Web Publishing Engine and Web Server on a separate machine for more robust performance if you anticipate a high web publishing load. 23

24 Determine hardware options One-machine deployment The Web Server provides content via web publishing clients, hosts the web-based Admin Console application, and handles data transfer tasks. The diagram below shows the major server components in a one-machine deployment. Two-machine deployment This deployment separates all of the web publishing-related components from the Database Server. The diagram below shows the major server components in a two-machine deployment. Worker Master 24 Getting Started Chapters 2 and 3

25 Deployment table Use the following table to guide you in your deployment options. How will you use it? FileMaker clients only What deployment fits your needs Single machine with Database Server only. No benefit from a two-machine deployment. App development and testing FileMaker clients and moderate web publishing FileMaker clients and heavy web publishing load Single machine with or without Web Publishing Engine. No benefit from a two-machine deployment. Single machine with Database Server and Web Publishing Engine. Provides reliable web publishing performance in most environments. You can expand to a two-machine deployment later, if web publishing load increases. Two machines. Deploy the Database Server on the master machine. Deploy the Web Publishing Engine and web server on a worker machine. 25 Getting Started

26 For optimal performance on your FileMaker Server - Run FileMaker Server on a dedicated machine so it can be reserved for use as a database server. - Manage or limit other network traffic when FileMaker Server is hosting many clients or a large number of files. - Evaluate and install the capacity needed for your apps, and for other processes running in parallel with FileMaker Server. - Ensure your system s upload and download speeds are adequate for your needs. See Appendix A for more information on the maximum number of connections tested. 26

27 Determine backup strategy It is essential to backup your data on a regular basis. How often you backup your data (everyday, several times a week, or some other frequency) depends on how quickly it changes, how much data you would lose, and how difficult it would be to recreate if it becomes corrupted or lost. With FileMaker Server, you have these options available to you: - Scheduled backups - Progressive backups - Third-party backups 27 Creating Backups

28 FileMaker Server backups A backup is a copy of a database file that can be used if the original is lost, damaged, or otherwise irretrievable. FileMaker Server provides the option of saving complete backups of your files at a scheduled time. You can also maintain progressive backups, which are updated incrementally as your files change. Scheduled Backups Schedule full backups of your files as often as is feasible without adversely affecting how your app performs for your users. This should happen at least once every 24 hours. Progressive Backups Schedule progressive backups as a complement to your full backups. Progressive backups can help fill in the gaps between your full backups, since they are updating much more frequently. Third-party Backups Do not use third-party software for databases while they are live and in use. Doing so can be severely detrimental to the stability of database files and may cause corruption or other irreversible damage. However, you should use third-party software to archive your FileMaker file. 28 Creating Backups

29 Plan for disaster recovery A standby server is a recent copy of your FileMaker Server that is ready to be deployed in its place in the event of a hardware or software failure. This copy can be used as a replacement of the primary server in the event of a hardware or software failure. A standby server does not host databases for clients, but stands ready to replace the primary server when needed. You can also use a standby server temporarily when performing upgrades on the primary server. FileMaker Server Duplicate Server 29 Getting Started Chapter 9

30 FileMaker Server in videos 30

31 - Build a custom app Considerations for system administrators - Use the FileMaker Platform - Determine deployment strategy - Deployment on FileMaker Cloud - Deployment on FileMaker Server - Considerations for system administrators 31

32 What to discuss with your system administrator Required hardware and software Check that you have the right hardware and software for the FileMaker Platform to perform efficiently. Check that you have the right disk subsystem, processor, memory, LAN, WAN. Network configuration Check the number of users that will access the app at the same time. Check the number of User Connections. Check port availability for optimum FileMaker Server performance. Make sure your users are running on a supported OS. Ensure you have performance monitoring tools for FileMaker Server. Decide if you will set up a standby server for failover and disaster recovery. Check that anti-virus software is disabled during server installation. Determine if you need help forwarding ports 5003, 80, 443 in the router. 32 FileMaker Server Technical Specifications Sharing Solutions over a WAN Connecting FileMaker Go to a Hosted Solution

33 What to discuss with your system administrator Deployment Determine how users will access your app, via their desktop, mobile device, and/or browser. Connectivity Check if users need to connect to an External SQL Data Source. Decide if you will install FileMaker Server on one machine or two machines. Evaluate if you will allow data sharing via ODBC and JDBC. Define what kind of data plan you want to set up. Decide if you will need third-party software. Security Decide if you will implement internal or external authentication (Active Directory or Open Directory). Determine if you will need an SSL certificate. 33 Introduction to External SQL Sources ODBC / JDBC Integration Overview Accessing External SQL Data Sources Connecting FileMaker Go to a Hosted Solutions

34 Next steps For a helpful list of resources on getting started with the FileMaker Platform, please visit: FileMaker Learning Center To get your team started with the FileMaker Platform, contact us: 34

35 2017 FileMaker, Inc. All rights reserved. FileMaker, the file folder logo and FileMaker Go are registered trademarks of FileMaker, Inc. in the U.S. and other countries. FileMaker WebDirect and FileMaker Cloud are trademarks of FileMaker, Inc. All other trademarks are the property of their respective owners.