MQTT.fx 0.0.4 released

Just released new version of MQTT.fx.
Download latest binaries HERE.

MQTT.fx - v0.0.4

New:
– revisited UI (return of “real” buttons)
– extended support for $SYS-topics: subscription for mosquitto or Hive MQ can be choosen (in respect to @dobermai).
– publish and subcrive/receive are now different tabs
– experimental support for http-proxy (in respect to @dimaki123).
– last choosen broker & port is restored at next app start
– updated 3rd party libs (e.g. now using features of ControlsFX 8.0.6)
MQTT.fx - v0.0.4 - broker status
MQTT.fx - v0.0.4 - subscribe
MQTT.fx - v0.0.4 - connection options
MQTT.fx - v0.0.4 - validation

Fixed:
– publish to topics even if not subscribed before (in respect to @_efwe_)

Hint:
Configuration-format has changed, v0.0.4 might conflict with former versions.
In this case just delete (or rename) the mqttfx-config.xml.
Windows: [USER_HOME]\MQTT-FX\mqttfx-config.xml
OS X: [USER_HOME]/Library/Application Support/MQTT-FX/mqttfx-config.xml
The new configration is automatically created on next app start.

MQTT.fx 0.0.3 released

Download latest binaries HERE.

Most significant change: I have added a pane to show some status values of the broker:

mqtt-0.0.3

In v0.0.3 these $SYS topics are recognised (Tooltips are showing the descriptions):

Version: $SYS/broker/version
Build: $SYS/broker/timestamp
Uptime: $SYS/broker/uptime
Subscriptions Count: $SYS/broker/subscriptions/count
Changeset: $SYS/broker/changeset
Clients Connected: $SYS/broker/clients/active
Clients Expired: $SYS/broker/clients/expired
Clients Disconnected: $SYS/broker/clients/inactive
Clients Maximum: $SYS/broker/clients/maximum
Clients Total: $SYS/broker/clients/total
Connection: $SYS/broker/connection/#
Messages Inflight: $SYS/broker/messages/inflight
Messages Received: $SYS/broker/messages/received
Messages Sent: $SYS/broker/messages/sent
Messages Stored: $SYS/broker/messages/stored
Messages Publish Dropped: $SYS/broker/publish/messages/dropped
Messages Publish Received: $SYS/broker/publish/messages/received
Messages Publish Sent: $SYS/broker/publish/messages/sent
Messages Retained Count: $SYS/broker/retained/messages/count
Bytes Received: $SYS/broker/bytes/received
Bytes Sent: $SYS/broker/bytes/sent
Load Connections: $SYS/broker/load/connections/+
Load Bytes Received: $SYS/broker/load/bytes/received/+
Load Bytes Sent: $SYS/broker/load/bytes/sent/+
Load Messages Received: $SYS/broker/load/messages/received/+
Load Messages Sent: $SYS/broker/load/messages/sent/+
Load Publish Dropped: $SYS/broker/load/publish/dropped/+
Load Publish Received: $SYS/broker/load/publish/received/+
Load Publish Sent: $SYS/broker/load/publish/sent/+
Load Sockets Count: $SYS/broker/load/sockets/+

JavaFX based MQTT Testing Utility

Download latest binaries HERE.

Now that MQTT is on its way to become THE industry-standard protocol for IoT and M2M communication the IoT community might have to review current message strategies.

Isn’t it a very good way to start with a JavaFX-Client to get into MQTT ;-)?
So, currently I am working on JavaFX based frontend based on Eclipse Paho.

Featured so far:

  • connect to an MQTT broker (tested with mosquitto yet)
  • modify some connection options
  • subscribe to topics
  • publish to topics
  • continuous logging of arrived messages
  • load and save settings (working directory: [user.home]/mqttfx)
  • an ugly application icon

Like to give it a try?
Download executable JAR (with dependencies) (requires an installed Java8-JRE)
Download Mac OSX DMG
Download Windows (x86) Installer

Main Screen
mqtt-fx-1

Logging Arrived-Messages
mqtt-fx-2

Editing Connection Options
mqtt-fx-3

Stored Configuration and UI-Settings
mqtt-fx-4

Introducing ‘adm4EE’: Manage Java EE Application Servers

Today I would like to announce a new project I have started at bitbucketadm4EE

I want to create a JavaFX  based management tool to ease the daily business of Java EE Application Server admins.

“A tool to manage App Servers? What about the already existing admin consoles?”

The aim is to keep the UI as simple as possible and hide complexity, even if the backend functions are very powerful and to provide easy access to:  monitoring the state of domains and applications and basic configurations like JDBC-pools, service ports, change admin password, etc.:

MainView

Currently implemented features:

Domain

  • Setup new domain according to domain template folder with support for JavaScript based setup script (Nashorn) via command line
  • Configure the domain
  • Start the domain
  • Stop the domain
  • Check if a domain is up and running
  • Restart the domain automatically in case of failure

EE Applications

  • Check application version against remote update server
  • Update application with new version from remote update server (support for update script)

JDBC Pool

  • Reconfigure JDBC Pool settings: Username, Password, URL, Ping JDBC Pools

Misc

  • Configure Service Ports (e.g. for HTTP listener, admin listener,…) with PortBase/PortOffset support
  • Command Line Interface for usage during scripted installation procedure
  • Settings are stored in a config-File (e.g. URL for Online-Updates, preferred Ports, …)
  • Change admin password
  • Show and save server log file
  • By now only GlassFish is supported, but prepared for other JavaEE-Servers (e.g. WildFly)

Some :

ConfigurationViewJDBCPoolViewLogViewServicePortsViewChangeAdminPasswordView

Have I already mentioned how much  I like the native packaging target? 

OSXdmg

 

Download: adm4ee_1_0_0.dmg