Starting WaveMaker

WaveMaker can be started from the WaveMaker launcher on all platforms. WM does not install as a service or daemon.

On linux systems, in /opt/wavemaker/bin can be used to start WaveMaker from script or console. WaveMaker does not need to be run as root.

On Windows and OSX, the WaveMaker launcher must remain open if it is used. Tomcat is a child process of the launcher, closing the launcher will terminate the WaveMaker Server process.

Stopping WaveMaker

Use the stop button if using the launcher.
Terminate the process if not.

Platform specific installation


See Mac OSX Installation Instructions

Debian - Ubuntu

Debian packages are available in 32bit and 64bit packages.
Packages are installed using dpkg, e.g:

sudo dpkg -i wavemaker-6.0.6amd64.deb \\

Where wavemaker-6.0.6amd64.deb is the file similar to wavemaker-.X.X.Xyyyy.deb

Wavemaker installs to /opt

AMD64 Specific

Required Packages

For *64bit systems installed AMD64 packages ia-3libs is required for java
To install:

sudo apt-get install ia32-libs
Suggested Packages

lib32nss-mdns is suggested for name resolution
To install:

sudo apt-get install lib32nss-mdns

Note: On Ubuntu 11 the package manager reports "The package is of bad quality" due to default permissions. It is safe to ignore this warning.


You can use dpkg to remove the wavemaker installation

sudo dpkg -r wavemaker

Note: Packages must be installed using dpkg or synaptic package manager. Attempting to run them as binaries will result in errors such as:

line 1: syntax error near unexpected token `newline' \\
 line 1: `!<arch>' \\

Start at boot

Script: wavemaker

  1. Save the above script in init.d with executable permissions
  2. Edit the WAVEMAKER_HOME, JAVA_HOME and STUDIO_USER variables
  3. Install with "chkconfig --add wavemaker"

RedHat - CentOS

Downloaded RPM packages can be installed using rpm. e.g.:

sudo rpm -i wavemaker-.6.0.0.i386.rpm

Where rpm -i wavemaker-.6.0.0.i386.rpm is the file similar to wavemaker-.X.X.X.i386.rpm

Or using yum. Here we use nogpgcheck to prevent the 'is not signed' error

yum install wavemaker-.6.0.0.i386.rpm --nogpgcheck

Where wavemaker-community.6.0.0.i386.rpm is the file similar to wavemaker-.X.X.X.i386.rpm

These both require you to download the package from as the rpm is not in the repository.

Installs to /opt

Packages are not signed. Please use rpm or edit /etc/yum.conf to replace gpgcheck=1 with gpgcheck=0


To uninstall an older version, verify the correct package name:

yum list installed | grep wave
And remove the package using yum
sudo yum remove wavemaker-community.i386

Accessing Remotely

The WaveMaker server can accessed remotely by pointing a browser to the server url. Such as:


In order to access a remote Linux host, you may need to open the WaveMaker port in iptables.
Example: Accept port 8094 (default WM port).

-A RH-Firewall-1-INPUT -m state \--state NEW -m tcp -p tcp -- dport 8094 -j ACCEPT
to /etc/sysconfig/iptables before possible REJECT rules
and restart iptables
> sudo /sbin/service iptables restart

IPTables HowTo at

Startup Problems

See: startup issues

Running as a Service on Windows

How to create a windows service from java app.
A discussion of available options.

Apache Procrun Procrun is a set of applications that allow Windows users to wrap (mostly) Java applications (e.g. Tomcat) as a Windows service.
Part of apache commons

Tanuki Software Java Service Wrapper Please note their licensing options
Java Service Wrapper

Microsoft's Sc.exe
To remotely create and start a service from the command line, you can use the SC tool (Sc.exe) included in the Resource Kit.
How to create a Windows service by using Sc.exe

OW2 Forge
JavaService allows server-type Java programs to be run in the background as a Windows NT/2000/XP system service (aka Unix daemon process).

Running Java Applications as a Windows Service
An example of how to turn a Java class into a Windows service using the open source Java Service Wrapper project.
Embarcadero Developer Network

Related Information

Accessing Studio via SSH Tunnel

How to configure Studio to require a password to access

© 2004-  WaveMaker, Inc