Zulu 2 Context Descriptor Customization
Zulu 2 is deployed as an application running in the Apache Tomcat application server. This means it shares some characteristics with all other Tomcat applications. One of these shared characteristics is the context descriptor file. This file contains an XML structure that outlines several key-value pairs that you can use to customize certain aspects of Zulu. The context descriptor file is named after the context chosen during installation (for example: if Zulu is installed at "/zulu" then the context descriptor file will be named "zulu.xml"
Locating the context descriptor file
The context descriptor file gets deployed into the 360Works directory when you install Zulu 2. Depending on your operating system and installation choices, it should typically be located in either of the following locations:
- /Library/360Works/Applications/conf/Catalina/localhost/zulu.xml (where "zulu" is the context name chosen during installation)
- C:\Program Files\360Works\Applications\conf\Catalina\localhost\zulu.xml (where "zulu" is the context name chosen during installation)
Editing the context descriptor file
The directory where the context file exists is typically write protected, so it is recommended that it be copied out of this folder into a writable folder such as the desktop, edited, then pasted back into the appropriate context directory.
Do not remove the context descriptor file from the localhost folder, only copy it and paste it elsewhere. Removing the context descriptor file might cause problems with the application.
Customizable context options
Default filemaker credentials
Parameter name: "jdbc.username"/"jdbc.password"
You can modify the credentials that Zulu will use to access FileMaker Server when no authentication information is provided by the client. This is useful for publishing read only calendars to CalDAV clients. They will not require authentication from the client, and will obey whatever privilege set the account you provide belongs to.
FileMaker Server host
Parameter name: "jdbc.host"
This parameter allows you to point Zulu 2 at a different server host that it will use to read from and write to FileMaker Server. This should be the Web Publishing Engine host.
Parameter name: "jdbc.ssl"
This parameter will instruct Zulu 2 to access the FileMaker Server Web Publishing Engine over port 443 with SSL enabled instead of standard insecure communication over port 80.
Zulu Sync Admin username and password
Parameter name: "zulu.adminUsername"/"zulu.adminPassword"/"zulu.adminPasswordHash"
This parameter can be used to set or override the admin credentials for accessing the Zulu Sync Admin page. If Zulu 2 is deployed manually, setting the credentials here is necessary. Otherwise, it is just used to override the existing credentials if they are forgotten. the zulu.adminPasswordHash parameter can be used if you do not want to store a plain text password in the context descriptor file.
Parameter name: "zulu.timezone"
This parameter can be used to set the desired timezone of the Zulu 2 server. This will cause Zulu to publish events in whichever timezone is specified. This can be useful if most of your users are using their calendars in a different timezone than where the server is physically running.
Enforcing Strict One Way Syncing
Parameter name: "zulu.enforceStrictWrites"
This parameter can be used to customize Zulu's one way syncing so that it will undo changes made in the write only side of the sync. This is useful if you do not want users to be able to make any persistent modifications to their calendars (Applies to Google and Exchange).