Which technologies are involved in the development of Mindquarry?

Mindquarry is based on Java technologies. We use Apache Jackrabbit as a JCR-conformant content repository, Apache Cocoon as the Web Framework, for the frontend we use the Dojo Toolkit in the Web and SWT for the desktop client user interface.

What do I need for installing Mindquarry Collaboration Server?

Since Mindquarry Collaboration Server is written in Java, it can be installed on every server platform that is capable of running Java 1.5 applications, i.e. Linux, Windows or Mac. The only thing you need is a pre-installed Java runtime environment.

For full document management support you need an Apache Web server with mod_perl and mod_svn. By the way, we offer a complete installation package for the Windows platform that includes Apache with all needed extensions. At the moment you need to install these by yourself on every other platform. How to do this is described in the installation guide.

What is the overall architecture?

The Mindquarry architecture guide is open to and published at the developer pages.

Is Mindquarry available as virtual image for VMWare?

We provide VMWare images only for stable releases of Mindquarry. Find them on the download pages.

How do I upload files?

Mindquarry file sharing uses the Mindquarry Desktop Client to synchronize files on your computer with the Mindquarry repository (this means up- and download). You can start the Mindquarry Desktop Client via Java Web Start by following the "Client" link in the footer of your Mindquarry Web interface.

The client will ask you for your credentials and a workspace folder on your computer where it will maintain a local copy of the shared files. After startup of the client you can hit the synchronize button and a new directory will be created for your team in the local workspace. Put files into your local workspace and hit "synchronize" again: the file will be uploaded and available to all team members.

What is the strategy for integration and API's?

Mindquarry uses XML in the data store, XML for internal processing and XML for the output (XHTML, ATOM, OPML). For integration, we currently offer an REST API that is used for instance in our desktop client, but we are keen on using standardized APIs for Wiki, Task Management and Document Management as well.

Do you have some considerations according data migration?

We have nothing concrete in place here yet, but we are able to migrate data from version control systems to our document repository (we are using Subversion internally, so we can rely on their migration scripts). For Wiki and tasks it is mainly a matter of extracting content from the existing system and publishing it using our REST API.

What is the default login name and password after installation?

Log in with user "admin" and password "admin".

My question is not answered in this FAQ?

Try to get an answer in the Forum.