How To - Install WRS On Windows

*** Edit the information contained here is out of date. To find more up to date information please visit here: http://wavingtheshiny.collaborynth.com.au/books/fedone-book/fedone-book ***

Okay so I've worked out how to install the WRS on Linux (well Debian and Redhat based Distros anyway). So now I'm planning How Tos for the following Operating Systems:

  • Windows
  • OpenSolaris
  • FreeBSD

The main focus of this How To is going to be on actually getting and installing the various packages that you will need to complete the installation process under Windows.

Requirements:

Building the WRS under Windows is going to take a little bit more downloading and configuring than under Linux. Whereas Linux has tools such as Synaptic and Yum to manage software installation, Windows is sadly lacking in this. So this means lots of manual downloading.

Suns Java SDK

You will need Suns Java SDK to build the WRS on Windows. To get this visit the following page:

http://java.sun.com/javase/downloads/index.jsp

And select the most up to date version of the Java SE Development Kit. At the time of writing, this is JDK Update 14. Go through the process of downloading and installing the SDK.

Ant

While the SDK is vital it does not include a vital tool required in the building of the WRS, the Apache Ant Build Tool. There are a number of ways to get Ant for Windows, however I found the following project the easiest to use:

http://code.google.com/p/winant

OpenSSL For Windows

Windows, unlike most other Operating Systems does not come with a built in ability to generate SSL Certificates. In order for us to build the certificates required by the Wave Reference Server we need to do the following:

Download and install the following packages:

http://www.slproweb.com/download/Win32OpenSSL_Light-0_9_8k.exe

and

http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF

Mercurial

Now that you have the Java tools ready to go, you need to get the source for the WRS itself. This means that you will need mercurial. For Windows I recommend the TortoisHG project. It integrates with Explorer and is pretty easy to use. To get TortoisHG visit the following site:

http://bitbucket.org/tortoisehg/stable/wiki/Home

Openfire XMPP Server

The Openfire XMPP Server is available across Windows, Linux and Mac. To grab the Windows version go to the following page:

http://www.igniterealtime.org/downloads/index.jsp

WRS Source

Now that you have all the tools, you need to get the source for the WRS so you can build it.

Step 1:

Create a directory called Wave-Devel

Step 2:

In that directory right click on a piece of blank space, click on TortoisHG and then select "Clone a Repository".

Step 3:

In the screen that pops up fill out the following:

Source Path = https://wave-protocol.googlecode.com/hg/

Destination Path = [CURRENT_DIRECTORY]/wave-protocol

and then click on Clone. This will take a little while but once it's finished you should have a wave-protocol directory with a big green tick.

Building the WRS

So long as you've got all your tools setup correctly, building your copy of the WRS should be as simple opening up a command console and running the following as this:

set JAVA_HOME=c:\Program Files\Java\jdk1.6.0_14
set ANT=c:\Program Files\winant\bin\ant

cd [THE_FULL_PATH_TO]wave-protocol
ANT

That will present you with a fully built fedone client and server.

OpenSSL

We still need to generate the ssl certificates that the WRS requires. With the WinOpenSSL the commands are pretty much the same as in the original howto, with the exception being that you need the full path to the openssl binary. So in the wave-protocol directory run the following on the command line:

[PATH_TO]\openssl genrsa 1024 | [PATH_TO]\openssl pkcs8 -topk8 -nocrypt -out [NAME].key
folllowed by

[PATH_TO]\openssl req -new -x509 -nodes -sha1 -days 365 -key $NAME.key -out [NAME].cert

Where [NAME] is the name you want to give your key/cert files.

Openfire

You're almost ready to get started. All that remains is for you to modify your Openfire Server. I've included the instructions from the Linux Howto, as these shouldn't change from OS to OS.

Once the server has restarted, if you closed the browser open it up and login again the admin console on http://localhost:9090. Once you've logged in, do the following:

Server -> Server Settings -> External Components

In the External Components Management Page you need to make the following changes:

Service Enabled -> Switch to Enabled

                        -> Port should be 5275

                       -> Secret can be whatever you like

Allowed To Connect -> add a new subdomain called wave and a secret

Security:

Now go to Server -> Server Settings -> Security Settings.

Server Connection Security -> select "Custom"

Server Dialback ->  Select Available

Accept self-signed certificates -> Select the checkbox

Once that is done, browse to Server -> Server Settings -> Registration and Login and do the following:

Disable "Inband Account Registration".

Disable "Change Password".

Disable "Anonymous Login"

Enable server-server compression in "Compression Settings"

Disable file proxy transfer in "File Transfer Settings"

Disabling Group Chat and Pubsub

Through a bit of debugging I and Mark Achee discovered that the OpenFire XMPP server tends to be a little random in how it lists the services that it has on offer. By default it offers the Pubsub and Group Chat facilities as well as the Wave service that we've just setup. This can result in Federation issues as the chatter will be delivered to the wrong service. To ensure that this doesn't happen, it's best to disable Group Chat and Pubsub.

Disablilng Pubsub:

To disable the Pubsub service do the following:

Browse to Server Manager->System Properties. Scroll down to the bottom and enter the following information:

Property Name: xmpp.pubsub.enabled

Property Value: false

Disabling Group Chat:

Browse to Group Chat->Group Chat Settings.

Delete the conference domain.

Now, the run-server.sh and run-client.sh files included in the source, won't actually run in Windows (shocking I know). So I've attached a couple of quick and nasty .bat files to this post for you to use. Download these into your wave-protocol server, modify them to reflect your criteria and away you go.

So that's windows out of the way. It's probably a little rough, but I'll keep improving it as people use it.

AttachmentSize
run-client.256 bytes
run-server.746 bytes

Comments

PBDybKOPbrTo

FZKDRx iibptltbjnbh, [url=http://zbztkdpncxye.com/]zbztkdpncxye[/url], [link=http://iwgqbcoxyywv.com/]iwgqbcoxyywv[/link], http://bgdtbkratfok.com/

lFOsNwWJNCVWHze

taiQnl vsojqgnoqjbf, [url=http://aswheumnacqw.com/]aswheumnacqw[/url], [link=http://zbqirnjhqkzk.com/]zbqirnjhqkzk[/link], http://xagddxsdzbhn.com/

ZjAbTBcEMeZpzUZ

21VwKi mgxwseddbycv, [url=http://tvdsflqclofb.com/]tvdsflqclofb[/url], [link=http://uflrjdbslbfm.com/]uflrjdbslbfm[/link], http://obiccayqzpdv.com/

QJZnudFJSLXgWoJFe

Kbu0Z5 cufeymaxaunn, [url=http://ocjkxzgqehbp.com/]ocjkxzgqehbp[/url], [link=http://woadzxgjabvs.com/]woadzxgjabvs[/link], http://xbwbedxxcijp.com/

luVXhLwauYPpHOsmy

fHICAG oximgyuwcqia, [url=http://ebarlledkhdh.com/]ebarlledkhdh[/url], [link=http://spoehschrawg.com/]spoehschrawg[/link], http://dhwoeynhjcxu.com/

Error while running the fedone-server-0.2.jar

Hi I am run the fed one server using following run-server.bat file:

set PRIVATE_KEY_FILENAME=waveTest.key
set CERTIFICATE_FILENAME_LIST=waveTest.cert
set CERTIFICATE_DOMAIN_NAME=%CERTIFICATE_DOMAIN_NAME%

set XMPP_SERVER_HOSTNAME=localhost
set XMPP_SERVER_IP=127.0.0.1
set XMPP_SERVER_SECRET=password123

java -jar dist/fedone-server-0.2.jar
--client_frontend_hostname=127.0.0.1
--client_frontend_port=5222
--xmpp_component_name=wave
--xmpp_server_hostname=%XMPP_SERVER_HOSTNAME%
--xmpp_server_ip=%XMPP_SERVER_IP%
--xmpp_server_port=5275
--xmpp_server_secret=%XMPP_SERVER_SECRET%
--xmpp_server_ping="acmewave.com"
--certificate_private_key=%PRIVATE_KEY_FILENAME%
--certificate_files=%CERTIFICATE_FILENAME_LIST%
--certificate_domain=%CERTIFICATE_DOMAIN_NAME%
--waveserver_disable_verification=false
--waveserver_disable_signer_verification=true

 

But I am getting following error message:

usage: must supply xmpp_server_description
    --certificate_domain <CERTIFICATE_DOMAIN>

    --certificate_files <CERTIFICATE_FILES>
 comma separated WITH NO SPACES.
    --certificate_private_key <CERTIFICATE_PRIVATE_KEY>

    --client_frontend_hostname <CLIENT_FRONTEND_HOSTNAME>

    --client_frontend_port <CLIENT_FRONTEND_PORT>

    --waveserver_disable_signer_verification
 <WAVESERVER_DISABLE_SIGNER_VERIFICATION>
    --waveserver_disable_verification <WAVESERVER_DISABLE_VERIFICATION>

    --xmpp_component_name <XMPP_COMPONENT_NAME>

    --xmpp_jid <XMPP_JID>

    --xmpp_server_description <XMPP_SERVER_DESCRIPTION>

    --xmpp_server_hostname <XMPP_SERVER_HOSTNAME>

    --xmpp_server_ip <XMPP_SERVER_IP>

    --xmpp_server_ping <XMPP_SERVER_PING>

    --xmpp_server_port <XMPP_SERVER_PORT>

    --xmpp_server_secret <XMPP_SERVER_SECRET>

 

 

Please suggest...

 

Thanks 10x, all inclusive tutorial !

thanks a lot for a great thread,

i got all up running on windows 7 within 2 hours on a virgin machine just following that single thread (people who know me know i am impatient and an amateur...).

THX

Hey,

big thx from Germany! The server & client are now both running on Windows 7 here!

BTW: I had some trouble to run your batch files as I just compiled a new jars from the Mercurial repo. The names of the jars are slightly different to the ones given in your files. Additionally I had to add a new parameter for the server namely :--waveserver_disable_signer_verification=true

Nice work!

 Regards,

 Jan

OpenSSL not needed.

Windows server has multiple ways of self issuing a certificate.  They aren't obvious to a typical non-enterprise user because you almost never use a self-signed cert in Windows except for lab use.

For server 2003:

Use the Self-SSL tool from the Server 2003 Resource Kit (Free)

Or add the Certificate Authority role to your server and self issue.

 

For server 2008:

Both of the above apply, but there is an easier way if you have IIS installed.

In IIS Manager, go to server certificates, and choose  "Create self-signed certificate."

WRS On Windows

Thank you, for the jump-start !

Cannot create new wave.

 I followed this guide and it seems to work fine. Except i cannot create new waves...

Anyone know how to fix this ?

 My startup config:

Client:

set WAVE_SERVER_DOMAIN_NAME=server
set WAVE_SERVER_HOSTNAME=localhost
set WAVE_SERVER_PORT=9222
set
USERNAME=%1@%WAVE_SERVER_DOMAIN_NAME%

java -jar dist/fedone-client-console-0.2.jar %USERNAME% %WAVE_SERVER_HOSTNAME% %WAVE_SERVER_PORT%

Server:

set PRIVATE_KEY_FILENAME=imperox.key
set CERTIFICATE_FILENAME_LIST=imperox.cert
set CERTIFICATE_DOMAIN_NAME=localhost

set XMPP_SERVER_HOSTNAME=%CERTIFICATE_DOMAIN_NAME%
set XMPP_SERVER_IP=localhost
set XMPP_SERVER_SECRET=letmein

java -jar dist/fedone-server-0.2.jar --client_frontend_hostname=127.0.0.1 --client_frontend_port=9222 --xmpp_component_name=wave --xmpp_server_hostname=%XMPP_SERVER_HOSTNAME% --xmpp_server_ip=%XMPP_SERVER_IP% --xmpp_server_port=5275 --xmpp_server_secret=%XMPP_SERVER_SECRET% --xmpp_server_ping="acmewave.com" --certificate_private_key=%PRIVATE_KEY_FILENAME% --certificate_files=%CERTIFICATE_FILENAME_LIST% --certificate_domain=%CERTIFICATE_DOMAIN_NAME% --waveserver_disable_verification=true --waveserver_disable_signer_verification=true

The Client:

←[31m@server> ←[0m/new
←[31m@server> ←[0m/new

←[31m@server> ←[0m/open 1
Error: entry is out of range, there are no available waves (try "/new")

 

The Server:

Oct 14, 2009 9:25:04 AM org.waveprotocol.wave.examples.fedone.waveserver.WaveSer
verImpl isLocalWavelet
INFO: ### WS is local? [WaveId:server!w+B3pE5eYguZls]/[WaveletId:server!conv+roo
t] = false
Oct 14, 2009 9:25:04 AM org.waveprotocol.wave.examples.fedone.waveserver.WaveSer
verImpl postSignerInfoAsync
INFO: Broadcasting 1 signatures
Oct 14, 2009 9:25:04 AM org.waveprotocol.wave.examples.fedone.federation.xmpp.Xm
ppDisco sendDiscoItemsGet
INFO: Trying to discover remote server: server
Oct 14, 2009 9:25:04 AM org.waveprotocol.wave.examples.fedone.federation.xmpp.Wa
veXmppComponent sendPacket
INFO: sent XMPP packet:
<iq type="get" id="791-12" to="server" from="wave.localhost">
  <query xmlns="http://jabber.org/protocol/disco#items"/>
</iq>

 

 

wrong [to]

<iq type="get" id="791-12" to="server" from="wave.localhost">
  <query xmlns="
http://jabber.org/protocol/disco#items"/>
</iq>

all server should use your own ip address, as 'server' cannot be found on the intranet.

did you ever figure this out?

did you ever figure this out?  I'm stuck in the same place.

Try changing the DOMAIN_NAME

Try changing the DOMAIN_NAME setting from 'server', ie.

set WAVE_SERVER_DOMAIN_NAME=localhost

I cant get the OpenSSL setup...

I get the following error in the second command.

OpenSSL> req -new -x509 -nodes -sha1 -days 365 -key $NAME.key -out Wave.key

Error opening Private Key $NAME.key

5380:error:02001002:system library:fopen:No such file or directory:.\crypto\bio\bss_file.c:356:fopen('$NAME.

key','rb')

5380:error:20074002:BIO routines:FILE_CTRL:system lib:.\crypto\bio\bss_file.c:358:

unable to load Private Key

error in req

Thanks

replace "$NAME.key" with

replace "$NAME.key" with "wave.key" or something similar, remember to REMOVE THE $ SIGN

$NAME should be a file name

 $NAME should be replaced by a file name like wave,

and there are wave.key and wave.cert in your wave-protocol folder.

Greets, thanks for the great

Greets, thanks for the great tutorial, seems i almost got it working, but there's minor problem

 

Oct 5, 2009 12:06:25 PM org.waveprotocol.wave.examples.fedone.crypto.WaveSignatureVerifier <init>

WARNING: ** SIGNER VERIFICATION DISABLED ** see flag "waveserver_disable_signer_verification"

Oct 5, 2009 12:06:25 PM org.waveprotocol.wave.examples.fedone.waveserver.CertificateManagerImpl <init>

WARNING: ** SIGNATURE VERIFICATION DISABLED ** see flag "waveserver_disable_verification"

Oct 5, 2009 12:06:25 PM org.waveprotocol.wave.examples.fedone.waveserver.WaveServerImpl <init>

INFO: Wave Server configured to host local domains: [example.com]

Oct 5, 2009 12:06:25 PM org.waveprotocol.wave.examples.fedone.ServerMain$RpcInetSocketAddressFactory <init>

INFO: Starting client frontend on host: 127.0.0.1 port: 9876

couldn't connect to XMPP server:org.xmpp.component.ComponentException: host-unknown

Oct 5, 2009 12:06:25 PM org.waveprotocol.wave.examples.fedone.ServerMain run

INFO: Starting server

 

>>couldn't connect to XMPP server:org.xmpp.component.ComponentException: host-unknown

any insight on how to fix that please ? 

thank you

WRS setup

Hey James/all -

Thanks for the detailed information here. I am having a problem however, the WRS sourcelink that you put in here doesnt seem to work, I wasnt able to locate the source code any other place through searches.

Is there an updated location ?

thanks

Hrmm I just checked the

Hrmm I just checked the source and it seems to be fine.

You blog on this subject got

You blog on this subject got me started.  Thank you.

Pitfall:

On Windows Server 2003, I'm having problems with the DOS not behaving like a Linux terminal.  Ther result is a window that has control garbage.

Additional resources:

http://code.google.com/p/wave-protocol/wiki/Installation
http://code.google.com/p/wave-protocol/wiki/ConsoleClient
http://code.google.com/p/wave-protocol/wiki/Federation
 

 

Not Just Windows 2003

Unfortunately it's not just limited to windows 2003. The Console for everything from windows 2000 and above is pretty dodgy.

WRS and Client running on Windows Vista...

BIG UPS to James for taking the time to create these instructions! I'd be at this for days without them.

Couple of tips from my experience with it:

- Make sure the Java version you compile the WRS Server with is the same as the one your Java Runtime environment is using. I already had JRE installed before installing the SDK and after building the Server JARs using ANT, I tried to start the server again and got a version error. Only after completely unistalling and removing all Java program files and then downloading and reinstalling the JAVA SDK (the regular one not the fancy EE SDK with Glassfire like I did initially) was I able to properly build the WRS Server and move on...

The "WAVESERVER_DISABLE_SIGNER_VERIFICATION" command line parameter is missing from the run-server.bat file provided above. When trying to start the server I was getting an error that the "WAVESERVER_DISABLE_SIGNER_VERIFICATION" need a value. Adding "--WAVESERVER_DISABLE_SIGNER_VERIFICATION=true," to the end of the run-server.bat fike enabled me to move on.

- One thing that may be totally obvious to everyone except me is that: The "Client to Server Port" in the Server Ports section of the Server Information page of OpenFire Admin, the "WAVE_SERVER_PORT" in run-client.bat, and the "client_frontend_port" in run-server.bat MUST ALL MATCH. Mine defaulted to 5222 in OpenFire, once I set the others to the same value, the client and the server started working perfectly.

That's about it. Again, Kudos to James for putting this tutorial together.

Penthos

WRS in Windows Vista

Hello,

Thanks so much for your thorough instruction. I've been banging on this for several days now and I'm really not sure where to go with it. Everything seemed to install and compile correctly, but I can't get the server to actually start. As you can see below, I run the "run-server" bat file and below is what happens:

----------------------------------------------------------------------------------------------------------------------------------------

C:\Users\Penthos\DOCUME~1\WAVE-D~1\WAVE-P~1>run-server

C:\Users\Penthos\DOCUME~1\WAVE-D~1\WAVE-P~1>set PRIVATE_KEY_FILENAME=PWS01.key

C:\Users\Penthos\DOCUME~1\WAVE-D~1\WAVE-P~1>set CERTIFICATE_FILENAME_LIST=PWS01.cert

C:\Users\Penthos\DOCUME~1\WAVE-D~1\WAVE-P~1>set CERTIFICATE_DOMAIN_NAME=PWS01

C:\Users\Penthos\DOCUME~1\WAVE-D~1\WAVE-P~1>set XMPP_SERVER_HOSTNAME=PWS01

C:\Users\Penthos\DOCUME~1\WAVE-D~1\WAVE-P~1>set XMPP_SERVER_IP=$XMPP_SERVER_HOSTNAME

C:\Users\Penthos\DOCUME~1\WAVE-D~1\WAVE-P~1>set XMPP_SERVER_SECRET=serenity

C:\Users\Penthos\DOCUME~1\WAVE-D~1\WAVE-P~1>java -jar dist/fedone-server-0.2.jar --client_frontend_hostname=127.0.0.1 --client_frontend_port=5275 --xmpp_component_name=wave --xmpp_server_hostname=PWS01 --xmpp_server_ip=$XMPP_SERVER_HOSTNAME --xmpp_server_port=5275 --xmpp_server_secret=serenity --xmpp_server_ping="google.com" --certificate_private_key=PWS01.key --certificate_files=PWS01.cert --certificate_domain=PWS01 --waveserver_disable_verification=true

usage: must supply waveserver_disable_signer_verification

    --certificate_domain <CERTIFICATE_DOMAIN>

    --certificate_files <CERTIFICATE_FILES>

 comma separated WITH NO SPACES.

    --certificate_private_key <CERTIFICATE_PRIVATE_KEY>

    --client_frontend_hostname <CLIENT_FRONTEND_HOSTNAME>

    --client_frontend_port <CLIENT_FRONTEND_PORT>

    --waveserver_disable_signer_verification

 <WAVESERVER_DISABLE_SIGNER_VERIFICATION>

    --waveserver_disable_verification <WAVESERVER_DISABLE_VERIFICATION>

    --xmpp_component_name <XMPP_COMPONENT_NAME>

    --xmpp_server_hostname <XMPP_SERVER_HOSTNAME>

    --xmpp_server_ip <XMPP_SERVER_IP>

    --xmpp_server_ping <XMPP_SERVER_PING>

    --xmpp_server_port <XMPP_SERVER_PORT>

    --xmpp_server_secret <XMPP_SERVER_SECRET>

------------------------------------------------------------------------------------------------------------

 In the end, the server never starts and I don't understand what it's trying to tell me.

ANY help would be much appreciated!

Thanks in advance,

Penthos

Exception whenever I run the run-client or run-server

Hello,

I get the following error when i try to start the client or serverusing the provided bat files, any help would be appreciated:

Exception in thread "main" java.lang.UnsupportedClassVersionError: org/waveproto

col/wave/examples/fedone/ServerMain (Unsupported major.minor version 49.0)

        at java.lang.ClassLoader.defineClass0(Native Method)

        at java.lang.ClassLoader.defineClass(Unknown Source)

        at java.security.SecureClassLoader.defineClass(Unknown Source)

        at java.net.URLClassLoader.defineClass(Unknown Source)

        at java.net.URLClassLoader.access$100(Unknown Source)

        at java.net.URLClassLoader$1.run(Unknown Source)

        at java.security.AccessController.doPrivileged(Native Method)

        at java.net.URLClassLoader.findClass(Unknown Source)

        at java.lang.ClassLoader.loadClass(Unknown Source)

        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)

        at java.lang.ClassLoader.loadClass(Unknown Source)

        at java.lang.ClassLoader.loadClassInternal(Unknown Source)

java.lang.UnsupportedClassVersionError

java.lang.UnsupportedClassVersionError

means you are using an java version that is to old. Try the latest JDK 1.6

WRS on Windows XP

I thought I had it working.  I've got one issue and I don't know which property on the openfire server to set to fix it.  I'm getting the couldn't connect to XMPP server:org.xmpp.component.ComponentException: java.net.ConnectException: Connection refused: connect error.  I assume this means wave can't connect to Openfire.  Here are the settings:

The machine is named oldpierce.  I first had allow to connect as subdomain wave and port 5269 but changed it to anyone with no success.  Here is the command that I am using to start the server:

 

C:\wave-devel\wave-protocol>java -jar dist/fedone-server-0.2.jar

--client_frontend_hostname=127.0.0.1

--client_frontend_port=9876

--xmpp_component_name=wave

--xmpp_server_hostname=oldpierce

--xmpp_server_ip=oldpierce

--xmpp_server_port=5275

--xmpp_server_secret=secret

--xmpp_server_ping="oldpierce.intermark.local"

--certificate_private_key=wrscert.key

--certificate_files=wrscert.cert

--certificate_domain=oldpierce  

--waveserver_disable_signer_verification=true

--waveserver_disable_verification=true

Please you email me at brianj at intgroup dot com if you have an idea of the problem.  I tried 192.168.0.31 instead of oldpierce for the hostname and IP.  I also setup oldpierce in the host file as 192.168.0.31 but no dice.  I also don't see port 5275 set in the openfire server so this must be a default.  Thanks.

 

Thanks! Few remarks though ...

Hi James

Firstly, thanks for your great explanation. I can confirm that it works indeed - in less than two hours I got things up and running. Maybe a few hints though, the at least occurred to me:

On Windows 2003 Server, port 5269 seems to in use and OpenFire hat trouble to bind to it, so I used 5275 instead (means to change the OpenFire Config @ External Components and the start_wave_server.bat file so it connects to OpenFire's correct component port.

Also, instead of building the server and client from their respective sources, I downloaded the already compiled jars (http://code.google.com/p/wave-protocols/downloads/list. The only thing was, that I needed to obtain and insert/copy /META-INF/services/org.xmlpull.v1.XmlPullParserFactory into fedone-server-0.2.jar (I actually obtained it from OpenFire.jar). This is propably first class hacking, but it worked anyway and helped me overcome the "resource missing" error that the wave server was showing in the first place when trying to start it.

Also, I found it a bit painful to finally understand that the wave server is using the certificate domain name whilst OpenFire uses the name you've entered upon setting up the OpenFire server and which can be anything (I used example.com). However, when you're computer is not a domain controller and is called server1 then it's likely that this name is used to generate the certificates and that means that users of the wave are to log on as user@server1 and not as user@example.com (which, from the wave server's perspective is in fact a remote user).

Anyway - now it works and not in the last place because of the great HOW TO you offered!

PS: When using the already compiled jars, it is also important to update the .bat files, as the jars are slightly differently named!

Marco

Anyone seen this issue

 Unable to access jarfile fedone-0.2.jar when running run-server.bat

the path is correct, i've even tried removing /dist and running the bat file directly from the dist folder.

Java and the JDK are both 1.6

unable to access fedone-0.2.jar

To this last question, your jar files should be named fedone-server-0.2.jar and fedone-client-console-0.2.jar  the .bat files need to be changed.  heh.