Zulu 2

From 360Works Product Documentation Wiki
Jump to: navigation, search

Zulu is an extension for FileMaker Server which runs as a standalone server application alongside FileMaker Server and lets Apple Calendar (and compatible clients) see your FileMaker table(s) as native calendars. You can manipulate your records in Calendar and when you do, you’re manipulating the FileMaker records directly: Calendar will even respect FileMaker’s record level access privileges and record locking so you can filter records based on privilege set and if someone else is editing an event when you try to do the same.

Visit the Zulu site to learn, download a demo, or purchase Zulu for your FileMaker Server.

Contents

Getting Started

Installation

Integrate with FileMaker

Integrate with Apple Calendar

Reporting a Problem

Customizing Zulu 2 behavior using the context descriptor file

Google Calendar Sync

Setting up your first sync with Google Calendar

Exchange Calendar Sync

Setting up your first sync with Exchange/Office365 Calendar

Frequently Asked Questions

If you ever run into a problem that you cannot solve, you can always contact 360Works support either by e-mail at support@360works.com or by calling our office at (770) 234-9293.

As we encounter common issues with Zulu, this section will be updated to help out future users who may encounter similar problems:


Does Zulu 2 support repeating events?

Does Zulu 2 support Google/Exchange attendees?

I don't see any calendars during configuration.

Does Zulu 2 support different time zones?

How can I publish my Zulu 2 calendars on a non-standard (not "/zulu") installation context?

I don't have Zulu 2 installed on the same machine as my FileMaker Server, how can I make it communicate with the proper server?

How do I migrate Zulu to another server?


Troubleshooting

Events aren't syncing anymore

If you have Zulu set to Auto-Sync, error messages won't show up in the Admin Console. First step is to turn off Auto-Sync and then run a Manual Sync. You will then see the error the sync is encountering displayed. That will give you a bit more to work with when diagnosing the problem.

If you recently changed a field name or other detail on your layout and republished your calendars - be sure to update the sync configuration on any associated calendar in the Sync Admin utility. To update it, just click "Edit" and step through the configuration and verify each detail.

Events sync to iCal but I can't edit or modify them

Check and make sure the credentials you used to add the calendar have the correct access privileges. Also make sure you didn't subscribe to a read-only calendar. If you're getting an error when you try to modify them, try clearing the iCal cache. See here: http://www.wikihow.com/Clear-the-iCal-Cache

Common Errors

Requested minimum modification lies too far In the past

This error message occurs when too much time has past since your last sync, the only way to resolve this is to delete your sync data, then perform another initial sync. Instructions to do so can be found here: Reset Sync Data

Installer Hangs

If the Zulu installer hangs during installation, please force quit the installer and then follow the instructions below to recover. This typically occurs when you've had a previous install go bad for whatever reason and the 360Works service is in a bad state.

Mac
  1. Launch the Terminal and run the following commands:
    1. cd /Library/LaunchDaemons
    2. sudo launchctl unload com.prosc.TomcatDaemon.plist
  2. Now download a fresh copy of Zulu and rerun the installer.
Windows
  1. Open the Services application
    • You can launch it by searching "Services" in the start menu or launching the task manager (Ctrl + Alt + Del) and going to the "Services" tab.
  2. Find the "360Works" service
  3. Right click it and click "Stop"
  4. Now download a fresh copy of Zulu and rerun the installer.

Dates & times are coming in incorrect! Does this have to do with TimeZones?

Yes. TimeZones can be very picky, especially with Outlook since they don't align with Java timezones. Presently Zulu operates properly when configured properly between GMT-11 and GMT+12. Be careful if your timezone set in your calendar or on your system is observing DST, as this can throw times off by an hour.

Zulu uses your system timezone by default for conversions, you can change this by modifying the system timezone or by modifying the Zulu context.xml file. Locations below, modify the zulu.timezone parameter, set the value to a Java timezone (see list here: http://joda-time.sourceforge.net/timezones.html). Use the Canonical ID.

Mac: /Library/360Works/Applications/conf/Catalina/localhost/zulu.xml

Windows: C:\Program Files\360Works\Applications\conf\Catalina\localhost\zulu.xml

Google

On the Google end, just go to your calendar settings on the calendar your syncing with and make sure the timezone matches up with the timezone your system is set to.

Outlook

Ensuring your time zones match up in Outlook can be pain as they differ. Keep in mind even though you have UTC+8 on Outlook and your system is set to UTC+8, the city you've chosen for your timezone can be affected by DST and therefore be an hour off when you sync. Exchange has different methods for changing timezone, on Office365 you can click Settings and then "Region and time zone".

Still no luck? Report a problem and we will take a look

Report a problem

Advanced Configuration

Filtering Events

Custom formatting data coming from Apple Calendar

Customizing what is logged in your Zulu logfile

Using Zulu with SSL

Important: Hosting Provider Installation

A hosting provider installation customizes the URL startpoint of your installation. On a default installation your local URL will look like "127.0.0.1/zulu", but a hosting provider installation allows you to customize the start point. For example, you could set it to "127.0.0.1/360WorksEventsCalendar". This feature also allows you to run multiple installations side by side. During the install this is set by the "application name" popup.

If you choose to do a hosting provider installation, please keep in mind you will need to customize your publish script in FileMaker to include this new URL startpoint. In Zulu 2.07 and earlier, please follow these instructions. For Zulu 2.08 and later, you can customize the startpoint by modifying the "$ZuluApplicationName" variable in the publish script.

Known Issues

Known Issues

Personal tools
Namespaces

Variants
Actions
Plug-in Products
Other Products
Navigation
Toolbox