RequestHeader set "x-webobjects-server-port" "80" RequestHeader set "x-webobjects-server-name" "localhost" RequestHeader set "x-webobjects-server-url" "http://localhost"
Then, restart Apache and SOGo:
% /etc/init.d/apache2 restart % /etc/init.d/sogo restart
If you want to use an IP address or a real DNS name to access SOGo, you must adjust this accordingly. The "x-webobjects-server-url" value will become the official URL to access your SOGo system. Now, from the same machine on which you performed the above steps, open your favorite Web browser and access http://localhost/SOGo. You should be able to log in with any of the three users created above.
Through the standard CalDAV and CardDAV protocols, SOGo supports desktop clients, such as Mozilla Thunderbird, Apple iCal and Apple Address Book, very well.
Mozilla Thunderbird, combined with the Lightning calendar extension, is the preferred client to use with SOGo. Version 2 and 3.1 of Thunderbird are supported. Thunderbird is the preferred desktop client as SOGo's Web interface shares most of its look and feel and functionality with Thunderbird. Moreover, two extensions can be installed together with Lightning to perfect the integration: the SOGo Connector and SOGo Integrator extensions. The former adds more capabilities to Thunderbird (such as CardDAV support, CalDAV ACL and so on), and the latter adds features that are vertical to SOGo (such as calendars, address-book sharing capabilities and automatic discovery, preferences synchronization and more).
Using the SOGo Integrator extension requires editing one file in the extension file subtree to specify where the SOGo server is located. This is done by hand. In an enterprise environment, this step is required only once per release, because the updates are expected to propagate automatically. Uncompress (using a ZIP or jar tool) the SOGo Integrator XPI, and locate the extensions.rdf file. This file is used for locating the extension update server and the SOGo server (let's consider those to be the same for the moment). There is a line starting with a Seq tag and with an attribute named isi:updateURL. Replace the host part of that URL with the SOGo server to which you want to connect, which again should be identical to the x-webobjects-server-url. For example, one would replace the following:
<Seq about="http://inverse.ca/sogo-integrator/extensions" ↪isi:updateURL="http://sogo-demo.inverse.ca/plugins/ ↪updates.php?plugin=%ITEM_ID%&version=%ITEM_VERSION%& ↪platform=%PLATFORM%">
<Seq about="http://inverse.ca/sogo-integrator/extensions" ↪isi:updateURL="https://sogo.acme.com/plugins/ ↪updates.php?plugin=%ITEM_ID%&version=%ITEM_VERSION%& ↪platform=%PLATFORM%">
if the SOGo server is accessible from https://sogo.acme.com/SOGo. Once you are done modifying the configuration file, save your changes and reconstruct the XPI. As for the extension update server, it can be configured to install or uninstall Mozilla Thunderbird extensions automatically. You also can push Thunderbird settings to all your user base. Installation and configuration is documented in the “Mozilla Thunderbird—Installation and Configuration Guide”.
On Mac OS X, if you prefer Apple's closed-source applications, you easily can use Apple iCal 3 and iCal 4 with SOGo. All features will be available, including calendar sharing and delegation, due to SOGo's excellent compatibility with the CalDAV protocol and its implementation of some Apple-specific extensions. Since Mac OS X 10.6, it's also possible to use Address Book with SOGo through the CardDAV protocol in order to access your contacts. When you combine those two applications with Apple Mail, a cohesive environment is created with collaboration possibilities with other users on other platforms.
The popularity gained by the CalDAV and CardDAV quickly exposed fundamental flaws in both protocols, and the Collection Synchronization for WebDAV and CalDAV Scheduling Extensions to WebDAV were created to eliminate those. The former introduces a token-based approach to DAV resources synchronization. So, instead of letting the DAV client ask for the ETag of every single item in a collection to see what has changed on the server, the client actually sends a sync token and gets in return the references of changed items from a collection. This makes the whole synchronization process of large calendars or address books very fast.
The second extension actually moves all the scheduling logic required in calendaring applications (inviting attendees, checking availabilities and so on) to the server. This avoids client-side implementation bugs and reduces client-to-server communications, which can be slow on high-latency connections.
SOGo implements those two extensions quite nicely, and Mozilla Lightning supports both while Apple iCal limits itself to CalDAV Scheduling Extensions to WebDAV.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide