Installing Zulu as a Servlet

From 360Works Product Documentation Wiki
Jump to: navigation, search
Getting Setup with Zulu: InstallingInstalling as ServletInstalling the Plugin VersionZulu Google SetupIntegrating your file • ‎Zulu Sync • ‎Serving the Sample FileRegistrationInstalling Zulu Manually
About Zulu The big pictureLimitationsRequirementsDifferences between servlet and pluginHostingSecurity
Troubleshooting TroubleshootingTesting ConfigurationsUmlautsURLs Used By ZuluUpdatingLogs
Google Sync with Google • ‎Sharing a Google CalendarGoogle ContactsGoogle ResetAppointment Slots
Calendars Repeating EventsDate Ranges • ‎Read Only CalendarsDeleting EventsInvitationsSwitching CalendarsMultiple CalendarsPropertiesSee it in iCalMy site
Contacts Contact GroupsContacts IntegrationsRelated Contact FieldsAddress BookZulu Phone Fax Email
Does Zulu work with... AndroidBlackberryMultiple MachinesOutlookMobileMeiPhone
Extra Credit Adding FieldsTime ZonesDuplicating RecordsCalc FieldsAccess PrivledgesRefreshFilteringPost Editing ScriptsAlarms and notifications



1. Enable XML Web Publishing.

Open the Server Admin Console for your FileMaker Server and enable XML Web Publishing:

Enable XML Publishing

If this pane of the Server Admin Console isn't active, you likely haven't installed the web publishing component of FileMaker Server: do that first. (You don't need Server Advanced, just the web publishing component of Server.) You can find more information about installing this part of FileMaker Sever here: FileMaker Server Getting Started Guide.

2. Set Google Sync to Manual.

If you are upgrading to a newer version of Zulu and are currently running Google sync on Auto, please set to Manual. This ensures that Zulu does not attempt a sync when the Web Publishing Engine is off.

3. Stop the Web Publishing Engine.

Using the FileMaker Server Admin Console, stop the web publishing engine by selecting "Stop Web Publishing" from the console's Server menu.

If you're moving from the plugin version to the servlet, remove the plugin from:

FileMaker Server/Web Publishing/publishing-engine/wpc/Plugins

4. Place the file on your server and install.

Move the entire "Zulu..." folder to your FileMaker Server (in a 2 machine deployment make sure to do this on the Web Publishing server) and unzip or extract it. Double click on the appropriate installer for your operating system (Mac installer or Windows Installer). Follow the instructions and you're done. If "Uninstall" is an option, select that before running the installer a second time to install.

You'll be asked for a user name and password: these are the credentials you'll use to administer Zulu. They are not the username and password to your FileMaker system: enter any combo you can make up and remember.

5. Restart FileMaker Web Publishing.

Using the FileMaker Server Admin Console, start the web publishing engine by selecting "Start Web Publishing" from console's Server menu.

6. That's It!

The plugin should be ready to go. Visit http://<host>/zulu where <host> is the IP address or domain name of your FileMaker Server to confirm that Zulu is running.

Note that if you're moving from the plugin version to the servlet for the first time you'll need to change the URLs Used By Zulu.


If you're running the plugin in Demo mode (for 2 hours at a time) you're all done. Just restart FileMaker Server's Web Publishing to use it for another 2 hours.

If you've purchased Zulu, now you'll register. Click here to learn how: Zulu Registration.

Next Steps

Serve the Sample File

Confirm your installation and see Zulu at work by serving the Zulu Sample File on your server.

Zulu Serving The Sample File


Why isn't this working?

  • You'll know the Zulu is running is working when you load the "Your Calendar Has Been Published" page at the end of the integration with you file. Or, simply visit http://<host>/zulu where <host> is the IP address or domain name of your FileMaker Server (or it's web publishing component in a multi-machine installation). There you'll see the name of the plugin, the version number, and your registration information, if you've registered (otherwise the plugin will be running in demo mode). If this page doesn't come up then either web publishing is not running on your FileMaker Server or the installation of the servlet failed.
  • You can get to the FileMaker Server Admin Console by opening a web browser and entering http://<host>:16000 where <host> is the IP address or domain name of the master machine in your FileMaker Server deployment.
  • If you have trouble logging in to your Server Admin Console, check out FileMaker's Server documentation (for example fms10_help.pdf) or this article. Server documentation can be downloaded here.
  • If the Server Admin Console says that it can't connect to the web publishing server, you may need to restart the FileMaker Server (this can happen if you're running a lot of IWP on the same WPE). And sometimes restarting it from the admin console doesn't work. If this is the case for you, close your databases using the Admin Console the end the Web Publishing processes on the server using the Task Manager. Finally, restart the server from the command prompt.
    • On Windows, open the command prompt window...
      • to Start FileMaker Server, type: net start "FileMaker Server"
      • to Stop FileMaker Server, type: net stop "FileMaker Server"
    • On Mac, you must be logged in to the machine where FileMaker Server is running. Open the Terminal application and enter the start or stop command:
      • to Start FileMaker Server, type: sudo launchctl start com.filemaker.fms
      • to Stop FileMaker Server, type: sudo launchctl stop com.filemaker.fms
Personal tools

Plug-in Products
Other Products