Deployment questions How do I uninstall MirrorSync? To uninstall on Mac, run the 'Mac Uninstaller. On Windows, run 'C: On either platform, you can also run the 'Works Admin. However, this does not remove the Works service, which is shared by other Works applications such as Zulu. You must use the uninstaller to completely remove the Works service. Installation for hosting providers To install multiple instances of MirrorSync, choose the Hosting provider option in the installer.
This is exactly the same as the regular installation process, except that it will allow you to rename the instance of MirrorSync. You can continue running the installer as many times as you like, once per client, renaming each instance to something unique. These copies can then be managed via the Admin utility, which is found either in your Program Files or Applications folder. When installing additional instances of the application, only a single Tomcat process will be installed which is shared by all of the MirrorSync instances.
Hosting providers should read the next item about using sub-admin accounts with MirrorSync. If MirrorSync is being installed on a different computer than your FileMaker Server, read the 'split server deployments' section below. Here's an example: We at Works use the installer for our hosting clients as well, and find it easy to update and manage. If you are curious as to what the installer actually does, it modifies and adds the following: Downloads and installs an instance of Tomcat 7 into that folder.
Only one copy of Tomcat is installed, regardless of how many copies of MirrorSync are running Copies and renames the installer's MirrorSync. Modifies the http. If you prefer to skip the installer and manually deploy using your own instance of Tomcat that you've set up, please note and follow these instructions: Make sure that it is readable and writeable to the process that Tomcat is running as.
This is where MirrorSync stores its private data including the internal sync database and the stored configurations. If you have a strong preference for locating this someplace else, because of disk space for example, configure a 'directory' system property in Tomcat to point to some other path.
Rename the MirrorSync. Drop that. Modify the the MirrorSync. See tomcat documentation on how to do this. Regardless of whether you use the installer or not, if you install enough instances of MirrorSync, you may start to run out of memory. If the memory error messages you get talk about PermGenSpace, then the memory problem is related to loading the MirrorSync classes, not the memory used during actual sync operations.
In this case, modify the file at C: We have reported this as a bug to FileMaker. In the meantime, there is another solution for this problem: Insert the full administrative user account information here, and MirrorSync will use that when downloading files or generating download links without prompting the users.
In this way, your MirrorSync users can download files without ever needing full FileMaker Server admin credentials. Split server deployments If your FileMaker deployment is split onto multiple machines, you can use any of these three configurations: If you choose this option, then it is also recommended that you install MirrorSync on the FileMaker Server.
This will enable download links to work. This is a good option if you prefer to deploy MirrorSync on Linux. Regardless of which computer you install on, be sure that when you are configuring MirrorSync, you specify that the Web Publishing and Database Servers are on different computers. This option is on the first screen in the configuration process.
How do I install MirrorSync on Linux? MirrorSync runs very well in Linux - it's our preferred deployment platform, and it's how we deploy our live demo file. We assume that you are familiar with Linux, and have already installed Java and Tomcat version 7.
Here is the setup process: Copy the MirrorSync. Set the adminUsername property, and either the adminPassword or preferably the adminPasswordHash. While you're in this file, skim over the other properties to see if you want to customize any of them. If desired, configure Apache to forward requests on port 80 to Tomcat, using a ProxyPass directive. Otherwise, just access MirrorSync on the Tomcat port typically Either comment out or increase the Timeout setting in the Apache configuration, if it's set to 60 seconds.
It is not uncommon for some operations in MirrorSync to take minutes, depending on the amount of data involved. MirrorSync is untested and unsupported for use in this configuration. In addition, the legal licensing agreement for creating runtime versions of FileMaker specifically disallows any automated transfer of data between the runtime version and FileMaker Server. This restriction means that no sync process can legally be used to transfer data between the runtime edition and FileMaker Server, whether that is from a 3rd party or a home-grown automation process.
What if I need to redeploy FileMaker Server? If using a Mac, no additional steps should be required. However, if you are running Windows, you'll want to re-run the installer for MirrorSync after redeploying FileMaker Server. I am running MirrorSync 2. What do I need to do to upgrade to 3?
Read the documentation on this at Updating from MirrorSync 2 to 3 Installing without a network connection The MirrorSync installer normally needs a network connection during the installation process. It uses this to download a copy of Apache Tomcat 7 from the Apache web site, as well as doing a network license check to validate the license key. If you are in an environment that has no outbound network capabilities, you can still install MirrorSync, but you'll need to follow these extra steps: Contact support works.
Be sure to include your license key and registration information. Download Apache Tomcat 7 from https: Now you should be able to run the installer without any network connection. How do I migrate MirrorSync from one server to another?
If the hostname or IP address of your FileMaker Server that is embedded in the sync configuration has changed, then either plan on redistributing new offline files to your users, or contact Works support for help with this. If the hostname or IP address does not change, and all that is changing is which server MirrorSync is running on, then follow these instructions: Stop Tomcat on the old server, by using the utility at C: Copy the folder at C: Make sure you have matched the file permissions from the previous computer.
Install MirrorSync on the new computer. Run the MirrorSync admin utility. Edit the configuration and modify the addresses of the MirrorSync server if necessary. They will be recreated with updated values when you paste the script steps. Networking questions Can MirrorSync send encrypted data?
Yes, it can. There are two network channels for encryption: SSL encryption can be enabled or disabled for each channel separately. In most cases, the connection from the syncing client to MirrorSync is more important for encrypting, since the connection between MirrorSync and FileMaker Server is usually on the same computer or the same LAN.
To encrypt data between the syncing client and MirrorSync, make sure that you have a valid SSL connection installed on the web server where MirrorSync is installed. You can test this by going to https: Once that is working, all you need to do is check the SSL box in the spoke configuration screen in MirrorSync.
Once that is complete, JDBC communication is automatically encrypted. If you select the XML option, and get an error saying that you have a self-signed certificate, then you will need to follow the Custom SSL Certificate setup instructions. You may also need to follow the instructions at Web Server settings are set correctly. MirrorSync configures these during installation but doesn't always succeed.
HIPPA compliance depends on a large number of requirements. However, one of those requirements is to transmit only encrypted data. See the question above if you experience difficulties. What ports are required for MirrorSync? Can I change them? During the MirrorSync configuration client only requires port 80, although it will connect more quickly if all ports are open. For the connection between MirrorSync and your server, it depends on which type of database server you're using: If these three conditions are met, MirrorSync will only use standard ports 80 or , which are allowed by default on almost all firewalls.
This will likely require custom configuration of your company firewall, if you have one. When configuring MirrorSync, select the option that says 'My internal and external IP addresses are different.
If this happens, it will try for 60 seconds and then automatically switch to the external network.
Aug 23, - That's why it is always our suggestion to upgrade to the newest version of to install a newer old version of FileMaker (i.e. FileMaker 12 or 13). Once designed, most are difficult to update and can be almost impossible to change. FileMaker Pro 13 serves as a foundation, providing a diverse suite of of the FileMaker Pro scripting language should provide for ample interactivity. Files from previous versions of FileMaker Pro must be converted to the new file Please update your operating system before upgrading to FileMaker Pro
FileMaker databases in the. However, there are some notable compatibility issues between v15 and v See "Upgrading from versions " below for more information. Databases in the. Earlier formats. See below for details. If you are thinking of upgrading to the latest version of FileMaker, now is also good opportunity to take inventory of all of your FileMaker files to determine if they are properly secured and to make sure that they are not being used to store PIRN data.
Inactive files required for archival purposes should be converted to the current version of FileMaker and backed up or archived, and earlier versions of those files sitting on your computer should be removed from your local machine. Upgrading from versions FileMaker 15 uses the same. Users simply need to upgrade to FileMaker Pro 15, and for hosted databases, the server is upgraded to FileMaker Server There are, however, a few compatibility issues to be aware of.
Features Compatibility Each new version of FileMaker comes with new client-facing features available to developers. However, even though versions all use the same file format, new features in later versions are not backward compatible and will not be available to users of earlier versions. In most cases, such features would simply be invisible to clients using earlier versions.
For example, v12 users will not see slide controls or popovers which were introduced in v Version 15 introduced few major end user changes of note, but if you are developing in FileMaker 15, it is best to make sure all the users of your system have updated to 15 as well. You also may want to enable the setting that specifies the minimum version of FileMaker Pro allowed to open your database file; this will prevent users running earlier versions from logging in and seeing unexpected results.
Hosting and Security Compatibility If your database s are hosted, there are potential security-related compatibility issues when the version of FileMaker Server doesn't match the version of FileMaker Pro used to open a database. In general, it's best practice to ensure FileMaker Server and all FileMaker Pro users accessing that server are all running on the same version of the platform. Some examples of issues with mismatched server and client versions: FileMaker Pro Upgrading from versions Issues to Consider FileMaker uses the.
FileMaker 15 is not compatible with this format, and. Similarly, the. Thus, once you convert a database to. Should I upgrade? With sufficient resource planning and testing, there is no reason to wait to upgrade from a pre-FileMaker 12 version. For areas that have multiple hosted solutions or very large and complex multi-user hosted FileMaker solutions, planning and testing may take some time.
For other less complicated systems, and certainly for standalone solutions, the process should be relatively straightforward. Instructions For guidelines related to the planning and testing process, please read [istcontrib: FileMaker's Conversion Checklist is also a helpful resource for planning your conversion process. Assistance If after reading the documentation available at the links above you believe you need assistance with converting your databases to the latest version, contact filemaker-support mit.
Upgrading from versions 6 and earlier To upgrade a file from version 6 or earlier. You can find more detailed instructions in FileMaker's knowledge base. This process is not trivial. If you need assistance with converting your databases to the latest version, FileMaker 13, contact filemaker-support mit. Running a "Mixed" Environment Although it is possible for more than one version of FileMaker to reside on a single machine, it is recommended that only the latest version of FileMaker be installed on any given system.
Users need to be able to access some databases in version 12 until the transition is complete and all the databases have been upgraded to This is a temporary condition. You are developing or supporting databases for users who are on different versions of FileMaker, and you need to test which features will work for which versions. You still have an earlier version of FileMaker Server as your host, and your users are also on that same version. Your client and server versions should match: You are encouraged to upgrade server and clients as soon as possible.
For help with planning your migration and transi