Installing your own Google Wave Federation Prototype Server

November 3, 2009 § 1 Comment

Ok, first of all, you’re all pretty anxious to get onto google wave. Here are some steps to get your own (albeit a console version) of your own FedOne Server. This process will use OpenFire as the XMPP server, others can be used such as Prosody.

Examples and screenshots have been created on a Mac, but this procedure allows for both OSX and Debian/Ubuntu installations.

Installation of Components

Java 6 –
OpenFire  –
Mercurial -

Openfire is a collaborative server based on XMPP which we will load the Prototype Server (FedOne) as an extension. Just choose your platform and follow the instructions.
For OSX: Just download the dmg and install the package.
For Ubuntu/Debian:
sudo dpkg -i openfire_3.6.4_all.deb
sudo /etc/init.d/openfire restart


Add these paths to your .profile located in /Users/<you>/.profile (For OSX)

export JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
export PATH=$JAVA_HOME/bin:$PATH

Navigate to  http://localhost:9090 to setup Openfire which you just installed.
OpenFire Settings:

You will now need to restart OpenFire (hint, it is located in System Preferences)
Linux users:
sudo /etc/init.d/openfire/restart
After you have restarted OpenFire you need to configure it a little more, allowing FedOne to interact with it.
Navigate to http://localhost:9090 once more.
Login with Username: admin Password: whatever you set in the admin setup.
Go to Server ->  Server Settings -> External Components.

Go to Server -> Server  Settings -> Security Settings

Now pull the latest repo to a folder with the mercurial command:

hg clone wave-protocol
cd wave-protocol

After you receive BUILD SUCCESSFUL, rename to and edit your settings in this file.

# Domain name of the wave server

# Host name and port the wave server's client frontend listens on

# The version of FedOne, extracted from the file
FEDONE_VERSION=`grep ^fedone.version= | cut -f2 -d=`

### Server-specific variables
# These will probably need to be changed

# These should be okay to leave alone

# Set XMPP_SERVER_IP to localhost if the XMPP and FedOne servers are
# running on the same host

# Set true to disable the verification of signed deltas

# Set true to disable the verification of signers (certificates)


We’re almost there.

Now you need a certificate:
Run this in terminal, so it exports in the same wave-protocol folder.
openssl genrsa 1024 | openssl pkcs8 -topk8 -nocrypt -out localhost.key
openssl req -new -x509 -nodes -sha1 -days 365 -key localhost.key -out localhost.cert
Replace localhost if you need for the filenames.

Now run the config:

Now to run the server:

And run our client:
./ <username>


Here are a couple of client commands to mess around with:
/open 0
/add <email>


About these ads

Tagged: , ,

§ One Response to Installing your own Google Wave Federation Prototype Server

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

What’s this?

You are currently reading Installing your own Google Wave Federation Prototype Server at dekz.



Get every new post delivered to your Inbox.

%d bloggers like this: