Browse Tag by manual
nikkus team bluespice mediawiki wiki
View Post

“The wiki is part of our corporate culture”

At the time of its expansion, the Berlin based event management company “NIKKUS” introduced a BlueSpice MediaWiki in 2012. Among other things the central knowledge repository features central questions about the company, process flows and tips and tricks for new staff members. The wiki enjoys a high level of acceptance among employees and saves a lot of precious time.

Continue Reading

Knowledge management and handbooks in the financial sector: A wiki with blog for the Saalfeld-Rudolstadt district savings bank

“Finally, more time for business thanks to the Web 2.0 – The Saalfeld district savings bank cracks open its knowledge silos and finds a new way to deal with rules” by Christian Sauer (summary of the progress report by Nathalie Köpff).

It is well-known that many things in Germany are over-regulated. Instead of supporting creativity and entrepreneurial thinking and action, too much regulation blocks the big picture and leads to redundancy, or in extreme cases to contradiction. The introduction of the Web 2.0 breaks open knowledge silos, helps colleagues share newly-acquired knowledge, in a central place accessible by all, for example in the intranet. Members of staff should have an information platform available which motivates their active cooperation, adding discernible value.

Online organisation handbook and open documentation

The Saalfeld-Rudolstadt district savings bank wiki meets both requirements. One part of the wiki satisfies the statutory and supervisory editorial requirements. This area fixes the procedural rules for business operations. Amongst other things, there is an open area in which the staff can freely document their knowledge. A blog provides support for the system, giving a non-binding form of transmitting information.

The main page of S-Pedia links to important innovations
The main page of S-Pedia links to important innovations

The backing of the management was indispensable to guarantee a wide enough basis for support and initiative. Furthermore, users were needed who really see the need, and last but not least a suitable provider. To get the project of the ground, one has to concentrate on the users, as they will be working with the system later on. For this reason, members of staff from the most diverse divisions of the company were integrated into the planning process right from the start. Taking the requirements of the users into account early on, avoids acceptance problems later on and developments missing the users’ requirements. In the case of the district savings bank, the first job was to determine the central activities clearly and specify a name for the platform: S-Pedia. Continue Reading

Install MediaWiki – Step by step instructions

In this article I want to answer the most frequently asked questions relating to installing MediaWiki. But first, a question in return: what is the purpose of the wiki? Is it just a test installation or is it to be used productively?

Installing a local test system

For testing, I recommend installing MediaWiki locally on your own computer. The installation process of a wiki is always the same. Firstly you need to set up and adapt the environment in which the wiki will run, this is primarily the webserver and the database as the case may be. Then you copy the wiki software files to the right place and set up the configuration data, either by hand or automatically, on the system environment. The most important things here are entering the right paths, language and connection to the database.

You can use the environment XAMPP for your local installation. Installation instructions can be found on the site I know small companies which run their wikis just with XAMPP and make them available on the intranet.

Installation as a productive system

To use a wiki productively in your business and organisation, however, I advise you to install it in a professional environment. XAMPP is not designed for professional use. Here, you need to decide whether the wiki will be made available on the web, or for internal use within the business. In any case, you need storage space available on the network. The system requirements can be found, for example, here at BlueForge (German website), or again in the official requirements list on, where, of course, one can also find the official installation instructions.

On the net, there are also useful video instructions, like this one:

Sometimes, it is also worth getting webspace with MediaWiki already fully installed from a webhost. Almost all the larger providers offer such services. And of course, cloud providers are preparing to include MediaWiki in their portfolios too. One is, however, not so flexible with these pre-packaged offers when it comes to updating and extending the software. Service providers like Hallo Welt! – Medienwerkstatt organise webspace, installation, extensions and maintenance of the software.

Here are a few tips to help decide where the software should be:

  • Migration: The files from your test wiki can be migrated to a productive system at any time. Generally, the effort needed to relocate a MediaWiki’s data is manageable.
  • Data saving: It is, however, very important to back up the files from a productive wiki regularly. Internal IT departments or webhosts regularly mirror the server so that it is possible to reset it to an earlier date. Generally, the more often the data is backed up and the longer the back ups are kept, the higher the hosting costs.
  • Test system: When making an installation with a lot of special adaptations and extensions, we recommend setting up a test system which will be synchronised with the productive system. New developments can be brought on to and taken off the test system before one puts them into practice on the productive system. In addition, one has a redundant system which can be used if the productive system goes offline.
  • Connectivity: If the wiki is to be connected to a central authentication system or other internal software, the system is generally installed on the intranet, as, for example, connecting to the LDAP server over the web is not possible or only with difficulty. If the whole infrastructure is on a cloud, it is different. One can, of course, combine the wiki with all the applications available on the cloud.
  • Compatibility and upgrades: There are innumerable extensions for MediaWiki, but not all extensions work with every version. For this reason, it is not always a good idea to use the newest version of MediaWiki. MediaWiki has a very short publishing cycle of only three months. For this reason, I recommend making an annual or biennial upgrade, in between introducing the newest safety patches. It gets problematic when an in-house developer changes the MediaWiki core. These changes are overwritten when upgrading and this can lead to undesirable side effects requiring significant support work. In order to guarantee reliability when upgrading, our developers for the BlueSpice for MediaWiki distribution, for example, avoid any core-hacks.

Extending with BlueSpice

Last but not least: For those who want to extend their MediaWiki with BlueSpice free there are installation instructions here for the freely downloadable software. Generally, MediaWiki is first installed and updated and then the newest version of BlueSpice is put over the top. Please make sure here too that you use the BlueSpice version compatible with the MediaWiki release you are using.


Further MediaWiki articles