Step-by-step tutorial

It is not practical trying to implement everything in one go. We recommend building the integration in small, easily testable steps, like the following:

  1. Install Collabora Online on a dedicated server or in a VM, and make sure you can access the discovery service by pointing your browser to

    https://<WOPI client URL>:<port>/hosting/discovery
  2. Add WOPI REST endpoints to your web service, for the moment returning only a “Hello World” message upon a GET request, that you can evaluate via a web browser. If you need, you can for example use Apache’s mod_rewrite so that the REST endpoints are redirected to URL of your choice. At this moment, test that

    https://<WOPI host URL>/<...>/wopi/files/<id>/contents
  3. Implement the CheckFileInfo endpoint – make sure that

    https://<WOPI host URL>/<...>/wopi/files/<id>
  4. At this moment, you will be able to see a constructed document in Collabora Online: Create a URL by concatenating URL from the discovery XML (see the point 1), and add WOPISrc=https://<WOPI host URL>/<...>/wopi/files/<id> at the end, resulting in URL like

    https://<WOPI client URL>:<port>/loleaflet/<hash>/loleaflet.html?WOPISrc=https://<WOPI host URL>/<...>/wopi/files/<id>

    Create a small test.html file containing:

  <form action="...URL you constructed..." enctype="multipart/form-data" method="post">
    <input name="access_token" value="test" type="hidden"/>
    <input type="submit" value="Load Collabora Online"/>

When you load it in the browser and click the Load Collabora Online button, it will open a text document that shows “Hello World” provided by the WOPI endpoints. If your WOPI host is on a different machine than Collabora’s, make sure to add that host along with the port in the configuration file loolwsd.xml under <storage><wopi> tag.

  1. From this point, you have the basics working, and you have to extend the JavaScript pieces: Create an iframe that will contain the Collabora Online, and provide that with a real access token. From the Collabora Online point of view, the access token can be any random text or number that contains just numbers, characters, and underlines.

  2. Update your REST endpoints so that they provide real data instead of a synthesized “Hello World” and hard-coded document length.

  3. Implement the PutFile end point, so that the results of editing can appear in your file storage too. To do this, implement the POST request to

    https://<WOPI host URL>/<...>/wopi/files/<id>/contents
  4. Either implement the PutRelativeFile endpoint, so that the option to Save As appears in the UI, or change CheckFileInfo to return UserCanNotWriteRelative with value true if you don’t want to do that yet.