Application Mashup - Wirecloud - Installation and Administration Guide

From FIWARE Forge Wiki

Jump to: navigation, search
IMPORTANT NOTE: this page contains outdated WireCloud's documentation. New versions of this documentation are published at Read the Docs.



This Installation and Administration Guide covers WireCloud version 0.7 (starting from FIWARE release 4.2). Any feedback on this document is highly welcomed, including bugs, typos or things you think should be included but are not. Please send it to the “Contact Person” email that appears in the Catalogue page for this GEi.


This page contains the Installation and Administration Guide for the WireCloud Mashup Platform, a reference implementation of the Application Mashup Generic Enabler, based on the WireCloud Open Source project. The corresponding online documentation is continuously updated and improved, and provides the most appropriate source to get the most up-to-date information on installation and administration. Both WireCloud users and developers have the option to create tickets though the github’s issue tracker of the project.


This section describes all the requirements of a basic WireCloud installation. However, these dependencies are not meant to be installed manually in this step, as they will be installed throughout the documentation:

  • A Database Manager (MySQL, PostgreSQL, SQLite3...)
  • Python 2.6 or 2.7. Python 3 and other versions are currently not supported. Also the following python packages must be installed:
    • Django 1.5+
    • South 0.7.4+
    • lxml 2.3.0+
    • django-compressor 1.4+
    • rdflib 3.2.0+
    • requests 2.1.0+
    • gevent 1.0.0+
    • selenium 2.41+
    • pytz
    • django_relatives
    • user-agents
    • regex
    • markdown
    • whoosh 2.5.6+
    • pycrypto
    • pyScss 1.3.4+
    • Pygments

All these dependencies are available for Linux, Mac OS and Windows, so WireCloud should work on any of these operating systems. However, it is better to use Debian Wheezy+, CentOS 6.3+, Ubuntu 12.04+ or Mac OS X as these operating systems are actively tested. Specifically, this installation guide was tested in the following systems:

  • Ubuntu 14.04
  • Ubuntu 12.04
  • CentOS 6.3
  • CentOS 6.5
  • Debian Wheezy
  • Debian Jessie
  • Mac OS 10.9

NOTE: WireCloud can make use of the Marketplace, Store and Repository GEs. If you want to exploit this support, you can choose between installing these GEs or using any of the instances publicly available, for example, on FIWARE Lab (see the "Instances" tab of the corresponding entries at

Installing basic dependencies

Before installing WireCloud, you will need to have some basic dependencies installed: python and pip.

NOTE: Although virtualenv is not required, you should install it before installing WireCloud if you intend to use it. It is highly recommended to use virtualenv (see the using virtualenv section for more info) when installing WireCloud in CentOS/RedHat as those systems usually raise problems when installing python packages using their official repositories and pip (a common case, as some packages should be updated for being compatible with WireCloud). Anyway, it is possible to install WireCloud in those systems without using virtual environments.


This guide assumes you system's package list is up to date. Otherwise, run the following command:

 $ apt-get update

before installing software in Debian/Ubuntu.

Python and pip can be installed by executing the following command:

$ apt-get install python python-pip


Python itself can be found in the official CentOS/RedHat repositories:

$ yum install python

Whereas pip and other packages should be installed from 3rd party repositories. The most common one is the EPEL repository (see for instructions about how to add it). If you has such a repository, you will be able to install pip using the following command:

$ yum install python-pip

Mac OS

Python comes installed by default in Mac OS, so you don't need to install it. pip can be installed using the following command:

$ sudo easy_install pip

However, we recommend you to upgrade your python installation using the Homebrew tools for Mac:

$ brew install python

This command will install, as bonus, the pip command tool.

Using virtualenv

virtualenv is a tool to create isolated Python environments. Those Virtual Environments, are an isolated working copy of Python which allows you to work on a specific project without worry of affecting other projects.

virtualenv can be installed using pip:

$ pip install virtualenv

Once installed virtualenv, you will be able to create virtual environments using the following command:

$ virtualenv venv

This will create an venv folder for storing all the resources related to the virtual environment. To begin using the virtual environment, it needs to be activated:

$ source venv/bin/activate

You can then begin installing any new modules without affecting the system default Python or other virtual environments. If you are done working in the virtual environment for the moment, you can deactivate it:

$ deactivate

This puts you back to the system’s default Python interpreter with all its installed libraries.

To delete a virtual environment, just delete its folder.

Installing WireCloud using pip

WireCloud can be easily installed using pip. To install WireCloud from a FIWARE release, download the desired version from the FIWARE PPP Public Files area.

Once downloaded, you can install it using the following command (assuming you downloaded APPS-Application-Mashup-Wirecloud-4.2.3.tar.gz):

 $ sudo pip install APPS-Application-Mashup-Wirecloud-4.2.3.tar.gz

You can always install the latest version of WireCloud from PyPI using the following command:

 $ sudo pip install wirecloud

Installing WireCloud from sources

The WireCloud source code is available from the GitHub WireCloud repository.

To get the latest development version of the code, you can choose between two options:

  • Go to the WireCloud repository on GitHub, switch to the 0.7.x branch (or select a specific 0.7.x tag) and click on the ZIP button to download the repository as a zip file, or just click on this link. Unzip it.
  • Or use a GIT client to get the latest development version via Git:

    $ git clone git://
    $ cd wirecloud
    $ git checkout 0.7.x

Once downloaded the source code, you can install WireCloud using the script:

$ cd <path/to/source/code>/src
$ python sdist
$ sudo pip install dist/wirecloud-<version>.tar.gz

Where <version> is the version of WireCloud to install.

Creating a new instance of WireCloud

Once installed WireCloud, you will have access to the wirecloud-admin script. This script is, among other things, used for deploy new instances of WireCloud. Before creating the instance, we recommend you to create a special user for managing and running WireCloud. For example, in Debian/Ubuntu:

$ adduser --system --group --shell /bin/bash wirecloud

Then, create a new instance directory using the startproject command. This will create a new directory containing the script, the configuration files, ... related to the new instance. Moreover, you can add new python modules into this directory to customise your instance.

$ cd /opt
$ wirecloud-admin startproject wirecloud_instance

After creating the new instance, you have to configure it choosing a database, populating it and performing final DJango configurations. These steps can be skipped using the --quick-start option. This will configure the instance to use SQLite3 with a default admin user (password:admin). This method is very useful for creating a WireCloud instance for testing:

$ cd /opt
$ wirecloud-admin startproject wirecloud_instance --quick-start

If you make use of the "--quick-start" option, you should be able to go directly to the Running WireCloud section.

Database installation and configuration

To set up the database engine, it is necessary to modify the DATABASE configuration setting in the instance file (e.g. /opt/wirecloud_instance/wirecloud_instance/ You can use any of the database engines supported by Django.

The following examples show you how to configure SQLite and PostgreSQL databases.


Setting up a SQLite database can be just accomplished within seconds by using the following parameters into the file:

      'default': {
             'ENGINE': 'django.db.backends.sqlite3',
             'NAME': '<dbfile>',
             'USER': '',
             'PASSWORD': '',
             'HOST': '',
             'PORT': '',

where <dbfile> is the path to the database file.

Python directly comes with support for SQLite, but we recommend you to install the pysqlite2 module as it provides a more updated driver:

$ sudo pip install pysqlite

Finally, please take into account that SQLite database is not recommended for production purposes. It is only useful for evaluation purposes.


For production purposes, PostgreSQL database is a much better choice. To do so, the following parameters must be set in

      'default': {
             'ENGINE': 'django.db.backends.postgresql_psycopg2',
             'NAME': '<dbname>',
             'USER': '<dbuser>',
             'PASSWORD': '<dbpassword>',
             'HOST': '<dbhost>',
             'PORT': '<dbport>',

where <dbname> represents the name of the database, <dbuser> is the name of the user with privileges on the database and <dbpassword> is the password to use for authenticating the user. <dbhost> and <dbport> are the host and the port of the database server to use (leave these settings empty if the server is running on the same machine as WireCloud).

The only thing that remains is installing the python bindings for PostgreSQL:

$ sudo pip install psycopg2

Or alternatively, for Debian/Ubuntu:

$ sudo apt-get install python-psycopg2

Installing PostgresSQL on Debian/Ubuntu

First install the object-relational database system.

$ sudo apt-get install postgresql

Afterwards you have to create the project Database. We assume that your user has super administrator permissions in PostgreSQL. This usually means that you have to login as the postgres user (i.e. $ sudo su postgres).

Both the PostgreSQL database and its user can be created with the following commands:

$ createuser <dbuser> [-P]
$ createdb --owner=<dbuser> <dbname>

If you want to create a password protected user you must use the -P option.

If you want to create a database called 'wirecloud' and a user called 'wc_user' with privileges on this database, you should write the following:

$ createuser wc_user [-P]
$ createdb --owner=wc_user wirecloud

Finally, it is also needed to allow local connections to the database, i.e. from the computer you are installing WireCloud. To do so, add the following rules to the beginning of the /etc/postgresql/X.X/main/pg_hba.conf file. In other words, the following two rules MUST be the first two rules of the file:

# TYPE  DATABASE           USER            CIDR-ADDRESS          METHOD
local   wirecloud          wc_user                               trust
local   test_wirecloud     wc_user                               trust # only necessary for testing WireCloud

Reload pg_hba.conf in PostgreSQL server with the following command:

$ sudo service postgresql reload

And finally, restart PostgreSQL and check if your user has access using this command:

$ psql wirecloud -U wc_user

Installing PostgresSQL on other platforms

Please, follow the oficial PostgresSQL installation guide

Database population

Before running WireCloud, it is necessary to populate the database. This can be achieved by using this command:

# python syncdb --migrate

This command creates some tables and asks you if you want to create a Django superuser. This user is required to login into WireCloud and to be able to perform administrative tasks; please respond yes. An example of the command output, where user/password are admin/admin, is the following:


You just installed Django's auth system, which means you don't have any superusers defined.
Would you like to create one now? (yes/no): yes
Username (leave blank to use 'wirecloud'): admin
E-mail address:
Password: ***** (admin)
Password (again): ***** (admin) 

Finally, whenever the WireCloud code is updated, the database must be migrated (and this is one of those times):

# python migrate

Note: It is strongly recommended to perform a full database backup before starting to migrate WireCloud to a new version.

Extra options

Here’s a list of general settings available in WireCloud and their default values. These settings are configured in the file. Also, take into account that most of these settings are based on settings provided by Django (see Django documentation for more info).


(Tuple, default: () [Empty tuple])

A tuple that lists people who get code error notifications. When DEBUG=False and a view raises an exception, WireCloud will email these people with the full exception information. Each member of the tuple should be a tuple of (Full name, email address). Example:

(('John', ''), ('Mary', ''))

Note that Django will email all of these people whenever an error happens.


(Boolean; default: True)

A boolean that turns on/off anonymous user access. Take into account that disabling anonymous access will reduce the usefulness of embedded and public workspaces as they will require users to be logged in.


(Boolean; default: False)

A boolean that turns on/off debug mode.

Never deploy a site into production with DEBUG turned on.

One of the main features of debug mode is the display of detailed error pages. If your app raises an exception when DEBUG is True, Django will display a detailed traceback, including a lot of metadata about your environment, such as all the currently defined Django settings (from


(String; default: "browser")

Language code to use by default (e.g. "en"). This setting also support other values: "browser", meaning "use the language detected from browser" and "default" for using the value of the LANGUAGE_CODE setting.


(String, default: None)

Set FORCE_DOMAIN using an string if you want to force WireCloud to use a concrete domain name when building internal URLs. If this setting is None (the default), WireCloud will use the domain info coming with the requests or from the django's sites framework if configured and used.

This setting is mainly useful when WireCloud is behind a web server acting as proxy.


(String, default: None)

Set FORCE_PROTO to "http" or to "https" if you want to force WireCloud to use one of those schemes when building internal URLs.

If this setting is None (the default), WireCloud will check if the request comes from a secure connection and, in that case, it will use https as the scheme for building the internal URLs. In any other case, WireCloud will use http as the scheme for the internal URLs.

This setting is mainly useful when WireCloud is behind a web server acting as proxy.


(String; default: "en-us")

A string representing the language code to use as fallback when no translation exist for a given literal to the user’s preferred language. For example, U.S. English is "en-us".


(String; default: 'root@localhost')

The email address that error messages come from, such as those sent to ADMINS.


(String, default: "wirecloud.defaulttheme")

A string representing the module that will be use for theming WireCloud. Current themes shipped with WireCloud are "wirecloud.defaulttheme", "wirecloud.fiwaretheme" and "wirecloud.oiltheme".


(Dictionary; default: A middleware configuration dictionary)

A data structure containing the middleware configuration per URL group where the URL group name are the keys of the dictionary and the value should be a tuple of middleware classes to use for that group.

You should use this setting as replacement of the Django's MIDDLEWARE_CLASSES setting (See Django's middleware documentation)

Currently available groups are "default", "api" and "proxy". For example, if you want to add a middleware class to the "api" group, you can use the following code:

URL_MIDDLEWARE_CLASSES['api'] += ('my.middleware.module.MyMiddlware',)


new in WireCloud 0.7.0

(Boolean or String, default: True)

Set WIRECLOUD_HTTPS_VERIFY to False if you want WireCloud not validate HTTPS certificates. If this setting is True (the default), WireCloud will verify https certificates using the CA certificates bundled with python requests or using the certificates provided by the system (this depends on the procedure followed for installing the python requests module). You can also provide a path to a CA bundle file to use instead (e.g. WIRECLOUD_HTTPS_VERIFY = "/etc/ssl/certs/ca-certificates.crt").

Django configuration

The file allows you to set several options in WireCloud. If DEBUG is False you will need to collect WireCloud static files using the following command and answering 'yes' when asked:

$ python collectstatic

In addition, you should serve the static files with a fast performance http server like Nginx or Apache. Django has documentation for this topic.

Finally, you can compress css and javascript code files for better performance using the following command:

$ python compress

Note: Don't forget to rerun the collectstatic and compress commands each time the WireCloud code is updated, this include each time an add-on is added or remove or the default theme is changed.

Advanced configurations

Installing the WireCloud Pub Sub add-on

The development of the Pub Sub add-on is carried out at []. You can always find the latest information about how to install and use it on the main page of the repository.

Newer versions of the Pub Sub add-on can be installed directly using pip:

$ pip install wirecloud-pubsub

Since wirecloud_pubsub uses django.contrib.static functionalities, you should add it to your INSTALLED_APPS in


As last step, add a DEFAULT_SILBOPS_BROKER setting with the URL of the broker to use:


Don't forget to run the collectstatic and compress commands on your WireCloud installation:

$ ./ collectstatic
$ ./ compress

NGSI proxy

WireCloud comes with a javascript library that allows widgets and operators to connect to NGSI-9/10 servers. This support works out of the box when installing WireCloud except for receiving notification directly to widgets and operators. To enable it WireCloud requires what is called NGSI proxy, this proxy is a facade that receives NGSI notifications and passes them to Widgets or Operators.

This NGSI proxy doesn't need to be installed in the same machine as WireCloud and can be shared with other WireCloud instances. WireCloud will use the NGSI proxy passed to the ngsi_proxy_url option of the NGSI.Connection object. This URL can be obtained from Widget/Operator preference defined in its config.xml.

You can install a NGSI proxy following those steps:

$ apt-get install nodejs npm
$ ln -s /usr/bin/nodejs /usr/bin/node
$ git clone git://
$ cd ngsijs/ngsi-proxy
$ npm install

After this, you can run the NGSI proxy issuing the following command:

$ npm run start

Integration with the IdM GE

  1. Create a new Application using the IdM server to use (for example:
    • Redirect URI must be: http(s)://<wirecloud_server>/complete/fiware/
  2. Install the social-auth django module (e.g. pip install django-social-auth)
  3. Edit
    • Remove wirecloud.oauth2provider from INSTALLED_APPS and add social_auth to it. For example, if your file currently contains the following content:
      The new value should be:
    • Add 'wirecloud.fiware.social_auth_backend.FiwareBackend' to AUTHENTICATION_BACKENDS. example:
    • Add a FIWARE_IDM_SERVER setting pointing to the IdM server to use (e.g. FIWARE_IDM_SERVER = "")
    • Add FIWARE_APP_ID and FIWARE_APP_SECRET settings using the id and secret values provided by the IdM. You should end having something like this:
      FIWARE_APP_ID = "43"
      FIWARE_APP_SECRET = "a6ded8771f7438ce430dd93067a328fd282c6df8c6c793fc8225e2cf940f746e6b229158b5e3828e2716b915d2c4762a34219e1792b85e4d3cdf66d70d72840b"
  4. Edit
    • Replace the login endpoint:
      • Remove: url(r'^login/?$', 'django.contrib.auth.views.login', name="login"),
      • Add: url(r'^login/?$', 'wirecloud.fiware.views.login', name="login"),
    • Add social-auth url endpoints at the end of the pattern list: url(r'', include('social_auth.urls')),
  5. Run "python syncdb --migrate; python collectstatic --noinput; python compress --force"

Running WireCloud

We recommend running WireCloud based on an Apache Web Server. However, it is also possible to run it using the Django internal web server, just for testing purposes. In any case, WireCloud should be configured for being served over HTTPS, this can be accomplished in severals ways as you can use another server as frontend and configure the encryption on that server. We recommend you to visit the Security/Server Side TLS page from mozilla for more information about how to configure efficiently your https security parameters.

Running WireCloud using the Django internal web server

Note: Be aware that this way of running WireCloud should be used for evaluation/testing purposes. Do not use it in a production environment.

To start WireCloud, type the following command:

$ python runserver --insecure

Then, go to http://computer_name_or_IP_address:8080/ where computer_name_or_IP_address is the name or IP address of the computer on which WireCloud is installed, and use the username and password you provided when populating the database to sign in on the platform.

Running WireCloud using Apache 2

If you choose to deploy WireCloud in Apache, the mod_wsgi module must be installed (and so does Apache!).

Installing Apache 2 on Debian/Ubuntu

To do so, type the following command on Debian/Ubuntu:

$ sudo apt-get install apache2 libapache2-mod-wsgi

Once you have installed Apache and mod_wsgi you have to enable the latest:

$ a2enmod wsgi

The next step is the creation of a VirtualHost for WireCloud using the Apache’s configuration files. On Debian and Ubuntu the configuration files for the VirtualHosts are stored at /etc/apache2/sites-available and enabled and disabled using a2enmod and a2dissite. The syntax of the VirtualHost definition depends on the version of Apache 2 of your system, so they are going to be described in different sections.

Installing Apache 2 on CentOS/RedHat

$ yum install httpd mod_wsgi

Apache 2.2

You can use this template as starting point:

<VirtualHost *:80>
        ### Wirecloud ###
        WSGIPassAuthorization On

        WSGIDaemonProcess wirecloud python-path=<path_to_wirecloud>
        WSGIScriptAlias / <>
        <Location />
                WSGIProcessGroup wirecloud

        Alias /static <path_to_wirecloud>/static
        <Location "/static">
                SetHandler None
                <IfModule mod_expires.c>
                        ExpiresActive On
                        ExpiresDefault "access plus 1 week"
                <IfModule mod_headers.c>
                        Header append Cache-Control "public"
        <Location "/static/cache">
                <IfModule mod_expires.c>
                        ExpiresDefault "access plus 3 years"

Assuming that your wirecloud instance is available at /opt/wirecloud_instance, you should have something similar to:

<VirtualHost *:80>
        ### Wirecloud ###
        WSGIPassAuthorization On

        WSGIDaemonProcess wirecloud python-path=/opt/wirecloud_instance
        WSGIScriptAlias / /opt/wirecloud_instance/wirecloud_instance/
        <Location />
                WSGIProcessGroup wirecloud

        Alias /static /opt/wirecloud_instance/static
        <Location "/static">
                SetHandler None
                <IfModule mod_expires.c>
                        ExpiresActive On
                        ExpiresDefault "access plus 1 week"
                <IfModule mod_headers.c>
                        Header append Cache-Control "public"
        <Location "/static/cache">
                <IfModule mod_expires.c>
                        ExpiresDefault "access plus 3 years"

Once you have the site enabled, restart Apache

# apache2ctl graceful

and go to http://computer_name_or_IP_address/ to get into WireCloud.

See the Apache 2.2 documentation about how to configure the TLS encryption and the Security/Server Side TLS page from mozilla for more information about how to configure efficiently your https security parameters.

Apache 2.4

You can use this template as starting point:

<VirtualHost *:80>

        <Directory <path_to_wirecloud>/<instance_name>
                <Files "">
                        Require all granted
                        Order allow,deny
                        Allow from all
        ### Wirecloud ###
        WSGIPassAuthorization On

        WSGIDaemonProcess wirecloud python-path=<path_to_wirecloud>
        WSGIScriptAlias / <>
        <Location />
                WSGIProcessGroup wirecloud

        Alias /static <path_to_wirecloud>/static
        <Location "/static">
                SetHandler None
                <IfModule mod_expires.c>
                        ExpiresActive On
                        ExpiresDefault "access plus 1 week"
                <IfModule mod_headers.c>
                        Header append Cache-Control "public"
        <Location "/static/cache">
                <IfModule mod_expires.c>
                        ExpiresDefault "access plus 3 years"

Assuming that your wirecloud instance is available at /opt/wirecloud_instance, you should have something similar to:

<VirtualHost *:80>

        <Directory /opt/wirecloud_instance/wirecloud_instance>
                <Files "">
                        Require all granted
                        Order allow,deny
                        Allow from all

        ### Wirecloud ###
        WSGIPassAuthorization On

        WSGIDaemonProcess wirecloud python-path=/opt/wirecloud_instance
        WSGIScriptAlias / /opt/wirecloud_instance/wirecloud_instance/
        <Location />
                WSGIProcessGroup wirecloud

        Alias /static /opt/wirecloud_instance/static
        <Location "/static">
                SetHandler None
                <IfModule mod_expires.c>
                        ExpiresActive On
                        ExpiresDefault "access plus 1 week"
                <IfModule mod_headers.c>
                        Header append Cache-Control "public"
        <Location "/static/cache">
                <IfModule mod_expires.c>
                        ExpiresDefault "access plus 3 years"

Once you have the site enabled, restart Apache

# apache2ctl graceful

and go to http://computer_name_or_IP_address/ to get into WireCloud.

See the Apache 2.4 documentation about how to configure the TLS encryption and the Security/Server Side TLS page from mozilla for more information about how to configure efficiently your https security parameters.


pip has problems installing lxml. What do I have to do?

See for more detailed info.

For instance, in Debian and Ubuntu you probably have to install the python-dev, libxml2-dev, libxslt1-dev and "zlib1g-dev" packages:

    $ sudo apt-get install python-dev libxml2-dev libxslt1-dev zlib1g-dev

In Mac OS, remember to install XCode and its Command Line Tools. If this doesn't work and you're using the Homebrew tools for Mac, you can try the following commands:

   $ brew install libxml2
   $ pip install lxml

I'm getting strange errors. Is there any way to get better info about the problem?

You can set the DEBUG setting to True

I don't remember the admin credentials. How can I recover it?

You have two options:

  • change the password of your admin user: see python changepassword
  • create a new admin user: see python createsuperuser

I get errors while running the script or when running the startproject command

If the error is similar to the following one:

   Traceback (most recent call last):
     File "./", line 8 in <module>
       from import execute_from_command_line
   ImportError: No module named

check that you python installation is correctly configured (using the python interpreter used for running WireCloud):

   $ python 
   Python 2.7.6 (default, Nov 13 2013, 20:19:29)
   [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.2.79)] on darwin
   Type "help", "copyright", "credits" or "license" for more information.
   >>> import django
   >>> django.VERSION
   (1, 5, 5, 'final', 0)

WireCloud server is giving 503 error responses

If you see messages in the apache log file like:

(13)Permission denied: mod_wsgi (pid=26962): Unable to connect to WSGI \
daemon process '<process-name>' on '/etc/httpd/logs/wsgi.26957.0.1.sock' \
after multiple attempts. 

edit /etc/httpd/conf.d/wsgi.conf and add the following line:

WSGISocketPrefix /var/run/wsgi

See the following link for more information about this problem.

I get the following error

Error processing proxy request: 'HTTPResponse' object has no attribute 'stream'

Check your python requests module version.

AttributeError: This StreamingHttpResponse instance has no `content` attribute. Use `streaming_content` instead.

Remove MIDDLEWARE configuration from your file.

Administration procedures

Administration commands

WireCloud provides a set of command line tools that can be used from the command line (manually or by scripts) on the folder of the WireCloud instance.


Adds one or more packaged mashable application components into the catalogue. At least one of the following flags:

  • redeploy Replace mashable application components files with the new ones.
  • users=USERS Comma separated list of users that will obtain access to the uploaded mashable application components
  • groups=GROUPS Comma separated list of groups that will obtain access rights to the uploaded mashable application components
  • public Allow any user to access the mashable application components.

Example usage:

$ python addtocatalogue --users=admin,ringo file1.wgt file2.wgt


Allows changing a user’s password. It prompts you to enter twice the password of the user given as parameter. If they both match, the new password will be changed immediately. If you do not supply a user, the command will attempt to change the password whose username matches the current user.

Example usage:

$ python changepassword ringo


Creates a superuser account (a user who has all permissions). This is useful if you need to create an initial superuser account or if you need to programmatically generate superuser accounts for your site(s).

When run interactively, this command will prompt for a password for the new superuser account. When run non-interactively, no password will be set, and the superuser account will not be able to log in until a password has been manually set for it.

  • –noinput Tells Django to NOT prompt the user for input of any kind. You must use –username with –noinput, along with an option for any other required field. Superusers created with –noinput will not be able to sign in until they’re given a valid password.
  • –username Specifies the login for the superuser.
  • –email Specifies the email for the superuser.

The username and email address for the new account can be supplied by using the –username and –email arguments on the command line. If either of those is not supplied, createsuperuser will prompt for it when running interactively.

Example usage:

$ python createsuperuser


Rebuilds whoosh indexes used by the search engine of WireCloud. Some commonly used options are:

  • noinput Do NOT prompt the user for input of any kind.
  • indexes=INDEXES Comma separated list of indexes to reset. Current available indexes: user, group and resource. All by default.

Example usage:

$ python resetsearchindexes --noinput --indexes=user,group

Sanity check procedures

The Sanity Check Procedures are the steps that a System Administrator will take to verify that an installation is ready to be tested. This is therefore a preliminary set of tests to ensure that obvious or basic malfunctioning is fixed before proceeding to unit tests, integration tests and user validation.

End to End testing

Please note that the following information is required before carrying out this procedure:

To quickly check if the application is running, follow these steps:

  1. Open a browser and type http://computer_name_or_IP_address/login in the address bar.
  2. The following user login form should appear:
  3. Enter the credentials and click on the "log in" button.
  4. Click on the Marketplace tab.
  5. Open the local catalogue uploader view using the path selector as depicted in the following figure:
  6. Upload CoNWeT_weather-example_1.0.3.wgt file using the "Adding widgets from packages" form.
  7. The new widget should be now available on the local catalogue.
  8. Repeat steps 6 and 7 using the CoNWeT_wms-viewer-geowidget_0.5.2.2.wgt and CoNWeT_weather-mashup-example_2.0.wgt files.
  9. All the widgets and mashups should be now available on the local catalogue.
  10. Click on the "Add to Workspace" button of the "Weather Example Mashup".
  11. Click on the "New workspace" button.
  12. The view should automatically change to the "Weather Example Mashup" view and widgets should appear in it.
  13. Select the pin tool in the "Web Map Service" widget clicking the appropriated button as shown in the image.
  14. And click the desired location. The "Weather Widget Example" should update the forecast info.

By performing this sequence of steps, you will check that the WireCloud Mashup platform is running and correctly deployed, and its database has been properly set up and populated.

List of Running Processes

We need to check that the Apache web server and the Postgres database are running. WireCloud uses a python interpreter, but it will not be listed as it runs embedded into apache2. If we execute the following command:

ps -ewF | grep 'apache2\|postgres' | grep -v grep

It should show something similar to the following:

$ ps -ewF | grep 'apache2\|postgres' | grep -v grep
postgres  1631     1  0 25212  9452   0 Jul03 ?        00:00:19 /usr/lib/postgresql/9.1/bin/postgres -D /var/lib/postgresql/9.1/main -c config_file=/etc/postgresql/9.1/main/postgresql.conf
postgres  1702  1631  0 25208  3784   0 Jul03 ?        00:00:47 postgres: writer process                                                                                                    
postgres  1703  1631  0 25208  1452   0 Jul03 ?        00:00:39 postgres: wal writer process                                                                                                
postgres  1704  1631  0 25462  2964   0 Jul03 ?        00:00:16 postgres: autovacuum launcher process                                                                                       
postgres  1705  1631  0 17370  1660   0 Jul03 ?        00:00:18 postgres: stats collector process                                                                                           
root      3811     1  0 50067 10848   0 13:13 ?        00:00:00 /usr/sbin/apache2 -k start
www-data  3818  3811  0 68663 39820   0 13:13 ?        00:00:00 /usr/sbin/apache2 -k start
www-data  3819  3811  0 68687 39448   0 13:13 ?        00:00:00 /usr/sbin/apache2 -k start
www-data  3822  3811  0 68901 40160   0 13:13 ?        00:00:00 /usr/sbin/apache2 -k start

Network interfaces Up & Open

To check the ports in use and listening, execute the command:

$ sudo netstat -ltp

The expected results must be something similar to the following:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 localhost:postgresql    *:*                     LISTEN      1631/postgres   
tcp        0      0 *:http                  *:*                     LISTEN      3811/apache2    

or these ones in case the machine is configured to use IPv6:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 localhost:postgresql    *:*                     LISTEN      1631/postgres   
tcp6       0      0 [::]:http               [::]:*                  LISTEN      3811/apache2    


The last step in the sanity check, once that we have identified the processes and ports, is to check the different databases that have to be up and accepting queries. If we execute the following command:

$ psql -U wc_user wirecloud

It should show a message text similar to the following:

psql (9.1.4)
Type "help" for help.


Diagnosis Procedures

The Diagnosis Procedures are the first steps that a System Administrator will take to locate the source of an error in a GE. Once the nature of the error is identified with these tests, the system admin will very often have to resort to more concrete and specific testing to pinpoint the exact point of error and a possible solution. Such specific testing is out of the scope of this section.

Resource availability

WireCloud runs fine with a minimun of 512 MB of available RAM (1024 MB recommended) and 10 GB of hard disk space. Nevertheless memory usage strongly depends on the number of concurrent users. According to normal usage patterns taken from the log history, memory usage exceeding 256 MB per user are to be considered abnormally high. WireCloud is not CPU-intensive and thus CPU usages over 5% per user is considered abnormal. WireCloud is i/o-intensive and performances below 12 http requests per second are considered abnormal.

The results from monitoring the testbed instance usage shows that the aforementioned ranges remains valid.

Remote Service Access


Resource consumption

Resource consumption strongly depends on the load, especially on the number of concurrent users logged in.

  • The main memory consumption of the Apache Web server should be between 64 MB and 1024 MB.
  • Postgresql should consume a small amount of memory, not more than 64 MB.

I/O flows

The only expected I/O flow is of type HTTP or HTTPS, on port defined in Apache Web Server configuration files.

Personal tools
Create a book