Extension:BlueSpice/BlueSpice fully featured

This document describes the installation steps for the first beta version of BlueSpice for MediaWiki (Fully Featured) under Linux.

About this manual
If you installed MediaWiki directly into  then   and   are identical.
 * The manual should be read completely and followed step-by-step.
 * When editing configuration files in a text editor be sure to save them as UTF-8 without BOM (Byte Order Mark).
 * The string  represents the URL of your Mediawiki installation, e.g..
 * The string  represents the file system path to your Mediawiki installation, e.g..
 * The string  represents the file system path to the web server root, e. g..

MediaWiki
For the installation of BlueSpice we assume that MediaWiki (version 1.15x or 1.16x) is installed and configured. It can be accessed via browser at.

Languages
Currently only the languages,   and   are supported.

Browser
For the usage of BlueSpice Firefox from version 3.0 is recommended. Other browsers (especially IE 7 and 8) may work, but have not been tested properly so far.

Server
These login credentials to the database server should be known: (probably created during the installation of MediaWiki) With an installation on Xampp the username "root" with empty password is preset.
 * Web server (Apache 2)
 * PHP versions 5.2.0, 5.2.6, 5.2.9, 5.3.0 and 5.3.2 were successfully tested.
 * PHP version 5.3.1 has a bug Bug due to which MediaWiki does not work. This affects e. g. Xampp 1.7.3.
 * MySQL from version 5.x
 * Host/IP address and port
 * Username and password for the root user (Create/Drop-Statements) and the Wiki-User
 * Name of the used database
 * The table prefix of the used database

Components of BlueSpice
If the above mentioned requirements are met and the readily configured MediaWiki 1.15.x or 1.16.x is accessible via browser, download the file bluespice_fully_featured_beta1.zip. It contains the following directories and files:


 * bluespice-core
 * bluespice-mw
 * skins
 * webservices
 * installcheck.php

Copy the contents of this file directly into the directory. Note: This will overwrite some files in your  folder.

From now on we assume that you installed Mediawiki to.

The following directories have to be writable by the web server:

(e. g. )

Checking the requirements
To check further requirements for the installation, access  via browser. The page shows additional information about the installation as well as occurring errors (e.&#x202f;g. concerning missing rights).



If everything is OK (green "OK") you can proceed to the setup of BlueSpice:

Setup of BlueSpice
Open the file  in a text editor and add the following lines at the very end:

 $wgUseAjax = true; $wgDefaultSkin = 'bluespice'; require_once( dirname(__FILE__).'/bluespice-core/index.php' ); BsCore::getInstance('MW')->setup;

// MediaWiki extensions require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/Lockdown/Lockdown.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/Quiz/Quiz.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/Poem/Poem.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/CategoryTree/CategoryTree.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/ImageMap/ImageMap.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/ParserFunctions/ParserFunctions.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/InputBox/InputBox.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/Nuke/Nuke.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/DynamicPageList/DynamicPageList.php' ); require_once( BsConfig::get('MW::AdapterPath').DS.'ext-dist/Cite/Cite.php' );

Configuration of BlueSpice
Point your browser at the URL.

Click "Start configuration" and fill in the necessary parameters (cf. screenshot).



User: Provide a database user who has the right to create tables in the database. The database user who is created via a standard MediaWiki installation does not necessarily have these rights! For testing (only!) you can use the MySQL-root-user.

Database: Fill in the database name and the prefix used when MediaWiki was installed.

Socket: Leave this field empty.

Core::BlueSpiceScriptPath: Fill in the path of the  installation starting at the   directory. (Example:  was installed in  . Therefore the correct input for Core::BlueSpiceScriptPath is:.

Core::UseMinify: Leave this unchecked.

If the submission of the configuration was successful, the message Configuration successfully finished. is shown in the browser.

WARNING: For security reasons we recommend to delete the file  as soon as BlueSpice is up and running.

Executing update.php
This step automatically creates additional database tables required by BlueSpice. Use the user/password combination from above.  $wgDBadminuser = 'wikiuser'; $wgDBadminpassword = 'your-password';
 * For MediaWiki 1.15.x make sure the file  exists. If it doesn't, copy the file   to.
 * For MediaWiki 1.16.x the according variables can be found in !
 * Open the respective file in a text editor and adjust the user name and password in the following lines:
 * In a command shell execute  TWICE:

user@linux:$ cd  user@linux:$ php /maintenance/update.php user@linux:$ php /maintenance/update.php The tables are now being created. Make sure the output looks something like this: Creating whoisonline table...ok Creating shoutbox table...ok

BlueSpice for MediaWiki can now be reached by browser at. Search and PDF-Export require the following extra steps:

Webservices
The BlueSpice extensions "ExtendedSearch" and "PDF-Export" are implemented as Java web services. These must be deployed in an Application Server such as Tomcat, Glassfish, Jboss or Jetty. For this manual we assume a running Tomcat installation.

Extended Search
This requires the PHP curl extension (php5-curl).

The Tomcat connector must be configured with. Example (Debian Lenny):

File : <Connector port="8180" maxHttpHeaderSize="8192" URIEncoding="UTF-8" ...

The path to the Solr configuration (solrconfig.xml) must be configured in Tomcat via the variable. Example (Debian Lenny):

File JAVA_OPTS="-Dsolr.solr.home=/opt/bluespice_data/solr"

Create the directory for the search index:

mkdir -p /opt/bluespice_data/solr/ chown -R tomcat55 /opt/bluespice_data/solr/

Copy the folder  to

Now deploy solr1.4.war. Example (Debian Lenny):

cp solr1.4.war /var/lib/tomcat5.5/webapps/

Make sure the file  contains the line

BsExtensionManager::registerExtension('ExtendedSearchMW',     RUNLEVEL::FULL|RUNLEVEL::REMOTE, ACTION::ALL);

Now activate Extended Search in your browser and configure the new web service:

BlueSpice (navigation on the left) -> Admin -> Preferences -> Section Search
 * Check the box "EnableExtendedSearch"
 * SolrHost (default: 127.0.0.1)
 * SolrPath "/solr1.4"
 * SolrPort (cf. the connector port in your server.xml)

PDF-Export
Deploy bn2pdf-light.war. Example (Debian Lenny):

cp bn2pdf-light.war /var/lib/tomcat5.5/webapps/

Finish
Your BlueSpice installation should be working now.

Support
Unterstützung finden Sie hier:


 * Support, Bug reports
 * Forums