Unblu 4.1

Internal Documentation

This document may change at any time without prior notice.
Changes may break backwards compatibility.
Do not rely on it!

Cloud Setup Multi-Node Simulation With One Unblu Server

1. Purpose

This document describes, how to configure unblu to start the "universe" product from within an ide (eclipse) which - for the browser - behaves as if multiple (separate) cloud nodes would have been deployed.
This greatly helps to test a cloud setup on the developers machine with little effort.

2. Howto configure

2.1. DNS / host file settings

The following DNS (or alternatively /etc/host file) settings are required:

# use this, if you want to avoid snippet adaptations to

Of course other IPs (instead of can be used as well.

2.2. unblu server configuration

The base configuration enables cluster setup, which is what cloud is configured with:

# configure server as if it was a cloud node

# a "default" server base url must be present, which is used internally for everything not handled during a http request

# currently, restrictedServerBaseUrl is always static


Two configuration settings are required in addition to the cloud setup to simulate the cluster with one instance. These are available as of unblu version 3.5:

# let server evaluate serverBaseUrl during requests dynamically by using the submitted "Host" or "X-Forwarded-*" headers of the request

# assign a fixed worker url - we can only simulate one worker instance for now
# this is always returned, when a worker is asked for its origin

3. Howto Test

In order to start testing, go to (co-visitor / agent).

Don't forget to adapt the snippets to or alternatively re-direct to as well.

4. Etest

Etest also supports this kind of setup.

Use as your property overlay when starting cloud universe and then start testing using:

5. Limitations

Due to the fact, that it is only one server instance, it is currently not possible to simulate certain server side functionalities (i.e. dispatcher connecting to workers to retrieve token informations). Instead of what would happen on real cloud node instances, where remote procedure calls over http are executed, the ide currently does not go over network to communicate between different origin parts.