Zulu Updating

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


Installing a new build of Zulu.

If you've downloaded a new build of Zulu, installing it is almost the same as what you did when you first installed.

Log into your FileMaker Server and stop the Web Publishing Engine.

Note that 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.

=Uninstalling the Plugin Version

Prior to version 1.018, Zulu included two installation options, a server-side plugin and a servlet. So many of the new features require the servlet version that we've dropped the older plugin option. So navigate to the Web Publishing plugins folder on your server...

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

...and remove the old version of the plugin.

Using the Installer

Next, run the installer, selecting Uninstall if that is an option, to remove the old build. Now run the installer to install the new build of Zulu just as you did the first time, restarting the web publishing engine when you're finished.

That's it!

Remember that if you used to employ the plugin version, this new version of Zulu doesn't require port 8040 in your urls, so you'll need to make a quick change to your publish script, and tell your users that you have new urls: more here.

Custom or Hosted Deployments

A note about customized installations. If you've modified Zulu.xml this will will not be overwritten by the new installer, so your settings there will persist. However, if you need parameters included in newer version of Zulu.xml (you know who you are) you can either remove Zulu.xml before reinstalling, or copy and paste the new additional parameters into your copy of Zulu.xml That file can be found here:

For FileMaker Server 11

\FileMaker Server\Web Publishing\publishing-engine\cwpe-tomcat\conf\Catalina\localhost\zulu.xml

For FileMaker Server 12

\FileMaker Server\Web Publishing\publishing-engine\jwpc-tomcat\conf\Catalina\localhost\zulu.xml

iOS 5

If you were using Zulu calendars on your iPhone or iPad prior to iOS 5, you'll want to delete and recreate your calendar accounts on those devices after upgrading to the newest build of Zulu.You won't need to do this every time, just the first time you move from pre iOS 5 to the new builds.

Personal tools

Plug-in Products
Other Products