Your SlideShare is downloading. ×

How we have build File Jockey Cloud

99

Published on

A few years ago we started building WebDAV on Domino server because Connections was small and Quickr was bigger... Now WebDAV runs smoothly on Tomcat so I could launch my WebDAV Cloud SaaS service. …

A few years ago we started building WebDAV on Domino server because Connections was small and Quickr was bigger... Now WebDAV runs smoothly on Tomcat so I could launch my WebDAV Cloud SaaS service.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
99
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. How we have build File Jockey Cloud Marten Vosmer posted this on July, 2013 Introduction A few years ago we started building WebDAV on Domino server because Connections was small and Quickr was bigger. WebDAV is coded in Java thanks to Domino, so it’s relatively easy to get the Java program to run on a Java server like Tomcat. We needed to replace the Domino features like logging and settings (which used Notes databases) with XML files because a Tomcat server does not understand a Notes database. I could never deliver a WebDAV cloud SaaS when WebDAV runs on Domino because of the licensing costs of the Domino server. Now WebDAV runs smoothly on Tomcat so I could launch my WebDAV Cloud SaaS service. The first clients are signing up which is extremely exciting for me. Setting up these clients is easy, a few XML files to setup on the WebDAV Cloud server and the client is up and running in 10 minutes. Nothing needs to be installed on the Clients Quickr or Connections server (expect that these servers are connected to the internet). Lialis runs the WebDAV servers on Amazon EC2 cloud systems. These servers are located in Ireland for WebDAV clients across in Europe. The clients mobile device connects to the central apache proxy server based on a client specifick URL, for example https://tyrellcorp@lialis.com. The the traffic is send to the Actual WebDAV server which does the WebDAV job with the clients Connections or Quickr server. Security All communication is enforced over HTTPS, this is also the case between the WebDAV Proxy and WebDAV servers. The function of the WebDAV proxy server is to balance the load between the two WebDAV servers. The WebDAV proxy server acts as an pass thru between the WebDAV clients and the WebDAV servers. The WebDAV servers translate the WebDAV client requests to IBM Quickr or Connections language. The WebDAV proxy server does not store any client related information besides general server logging. On the WebDAV servers we cache the clients documents send to or received from the Quickr or Connections servers to improve the speed of the WebDAV server. These files are stored encrypted on the WebDAV server and are removed after 60 minutes from the WebDAV server when the files are not used by the users. The client's credentials, set on the mobile device, are given to the WebDAV server which passes these credential to the clients Connections or Quickr server. Lialis does not log the client's credentials passwords, only the user names are logged on the WebDAV server. The WebDAV server does not check if the user's credentials are valid. It will allow any user (who knows the WebDAV URL (for example tyrellcorp@lialis.com) to pass thru to the clients Quickr or Connections server. At the clients Quickr or Connections server the user credentials checked. If the credentials are reported as invalid by the clients Quickr or Connections server the File Jockey server will give a not authorized error to the mobile device. The File Jockey server setup is used by users of Marten Vosmer: +31 622 473 076 | marten.vosmer@lialis.com | http://www.file-jockey.com
  • 2. multiple clients. The File Jockey server also used for free demonstration purposes of File Jockey with IBM Greenhouse. The WebDAV proxy server runs on Linux and the WebDAV servers run on Windows 2008. These servers are EC2 instances located at Amazon Ireland. Access to these servers is protected by an Amazon security group in which the ports are set to allow communication via. These ports are 22 (Linux server access), 443 (HTTPS) and 3389 (RDP Windows). On the Windows server running WebDAV a firewall is enabled where the ports 443 and 3389 are open. Licensing Lialis is billed by Amazon for running costs of the EC2 servers. These costs include the hire of the Windows and Linux operating systems. Lialis runs WebDAV Cloud on Apache Tomcat (not on Lotus Domino server). All licenses that must to be paid to third parties are paid by Lialis. Fail over The WebDAV servers running at Amazon Ireland are also running at Amazon N. Virginia. Suppose Amazon Ireland goes down then Lialis can switch to Amazon N. Virginia by changing the IP address of the WebDAV URL (for example tyrellcorp@lialis.com). Then this DNS change must replicate over the world which will take minutes till hours. Amazon EC2 servers File Jockey Cloud servers run on Amazon EC2 systems. The great advantage of EC2 is that Lialis can increase or lower the performance of the system within 1 minute. Setting up instructions For setting up WebDAV cloud Lialis needs the following information from the client. 1. The URL of the Connections or Quickr server (for example https://quickr@tyrellcorp.com) 2. Optional: a File Jockey account to one Quickr place of Connections Community dedicated to Lialis so we can test the setup and monitor the availability of the complete WebDAV system. Monitoring Lialis has a WebDAV monitoring system in place that downloads a particular file from the Quickr place or Connections community every 5 minutes. When this download fails Lialis and the client will be notified by email. For this monitoring system the File Jockey account and access to one Quickr place of Connections Community of the client must be in place. Information Marten Vosmer: marten.vosmer@lialis.com Phone: (+31) 622 473 076 Marten Vosmer: +31 622 473 076 | marten.vosmer@lialis.com | http://www.file-jockey.com
  • 3. File Jockey is the missing link between mobile device and IBM. We have written several other manuals in using apps combined with File Jockey and IBM Connections and Quickr. More details about the File Jockey software can be found on http://www.file-jockey.com Marten Vosmer: +31 622 473 076 | marten.vosmer@lialis.com | http://www.file-jockey.com
  • 4. Manuals Collaboration Quickr / Connections Make paper a memory with Notability, IBM Connections and File Jockey iPad iPhone Paperless meetings with iPad Goodreader and IBM Connections community files and Android Working with Office documents on your iPad and saving them directly in IBM Connections with File Jockey Lotus Notes databases Upload photo's from mobile device directly into Notes mail file folder Releasing files in any Notes database to mobile devices with File Jockey Manage your documents in IBM Connections with File Jockey and Readdle Documents Signing and storing of legal documents in IBM Connections Paperless meetings with Android FolderSync, IBM Connections and File Jockey Notability for iPhone How To Increase Lotus Notes & Quickr Mobile User Adoption Read, annotate, sign, … PDF’s from IBM environments, with PDF Expert and File Jockey Windows Archive your Quickr places or Connections communities Sync files between IBM Connections, file server, Quickr, Dropbox and many more cloud file storage solutions Network drive directly to the files in IBM Connections WebDAV clients for Windows 7 Automatic sync of your IBM Connections files to a folder on your computer (for Windows, Mac and Linux) Windows WebDAV client Total Commander Mac Working with WebDAV on a Mac Marten Vosmer: +31 622 473 076 | marten.vosmer@lialis.com | http://www.file-jockey.com

×