Recently Wakanda released the 2.6.0 version of their Wakanda Enterprise solution. Along with this upgrade, the was a few surprises.
- This version now requires Ubuntu 18.0.4. Ubuntu 16.04 LTS is no longer supported and in order to perform this upgrade, you will need to upgrade your running distribution.
- Ubuntu 17 was never supported. Likely will not be added.
- Versions of Wakanda 2.0.0 - 2.5.0 require Ubuntu 16.04 LTS ONLY.
- Wakanda only is supported running under Ubuntu. So if you want to play with it you had better get used to working with Ubuntu and the Debian package system.
- The new version of Wakanda 2.6.0 and later now starts and runs as a service. The /etc/init.d files are now gone and have left the package. You will need to manage the service as a systemd.
The ironic part is that this is a big surprise. There nothing in the README file about this upgrade causing this kind of changes. It may be a minor upgrade but having to upgrade your Linux Distro to accommodate the minor version change by Two full releases is a big shock.
Originally Wakanda for Linux only ran under Ubuntu 16.04 LTS.
The new installer will install all you need to get started but make sure you have your license file in the right place. The following flags will allow you to configure the startup of your new Wakanda configuration. There is a note in the README file about the proper placement for the default license file.
Usage: wakanda-enterprise-server [OPTION]... [FILE]...
http://www.wakanda.org
-s, --solution=VALUE Solution or JS file
-d, --daemon Go daemon and run in the background
Administration options:
--admin-password=VALUE Administrator login password (default: <empty>)
--admin-port=VALUE Force the Administration panel port number
--admin-ssl-port=VALUE Force Administration panel ssl port number
--admin-publish=VALUE Force Administration panel publishing mode
'https': accept only HTTPS connections
'http': accept only HTTP connections
'both': accept both HTTPS and HTTP connections
'both-but-http-local-only': accept HTTPS
connections and HTTP connections only from localhost
Service discovery options:
--no-discovery Do not start Bonjour services
--allow-data-conversion
Allow converting the database to a higher Wakanda version
Debugger settings:
-g, --debugger=VALUE Debugger to launch at startup (ignored if
--debug-off is specified) ['remote': activate the
remote web debugger, 'none': disabled] (default: none)
--debug-off Disable the Debugger features.The debugging
interface will not be launched on the server
side, which can be useful when the solution is
used in a production environment
Jobs:
--job-id=VALUE Specify the server job id
System workers:
--system-workers=VALUE Configuration file for system workers
Logging facility:
--syslog Forward Wakanda Server's log messages to the
Syslog daemon
--verbose Verbose mode
--pid=VALUE PID file containing Wakanda Server's process id
-l, --license=VALUE Path of the license file
Help:
--version Display the version and exit
-t, --test Launch backend tests
-h, --help Display the help and exit
Instead of using the old configuration file in the /etc/defaults folder you will instead update the file in
/lib/systemd/system/wakanda.service Be prepared to make a few changes. Here is an example my one of my .service files. This configuration is running on my development server hence the --debugger = 'remote'.
[Unit]
Description=Wakanda Enterprise Server
After=network-online.target
[Service]
Type=notify
User=wakanda
Group=wakanda
ExecStart=/usr/local/bin/wakanda-enterprise-server --daemon --syslog --solution="/opt/mySolution/app.waSolution" --debugger='remote' --license="/opt/mySolution/license/license.key"
Restart=always
[Install]
WantedBy=multi-user.target
Hopefully, this helps you and prepares you for the change you will get in the new Wakanda 2.6.0 release.