The official Strolch blog with news, ideas, and thoughts on using Strolch.
Strolch can do reports!
A feature we haven't written about yet is the report API. Strolch has it's own API to generate
reports of data, and since we have a generic model, we use
Resource of type
Report to define them.
Go check out the documentation and then enjoy using this easy way to deliver the reports your peers require.
Strolch queries are deprecated!
Strolch has had once again many changes, and fixes etc. One important thing to note is that we have removed support for transactional mode and have rewritten how models are searched. Thus the search API was born.
Go check out the Strolch Search documentation and then go rewrite your searches =)).
Strolch tag 1.6.51 has all those juicy changes!
So many changes, and so long no update - not good!
Oh boy, have we forgotten to update you all on the latest awesome features in Strolch! There are over 123 commits since the last tag 1.3.0, so that alone merits a new blog post.
Currently the latest tag is 1.5.5, but this version is actually already quite old, as it was created on 31. January 2017 and there are 53 new commits ahead of the tag.
Enough of all the commits, lets get to the new features:
To summarize, execution and reporting are the two new features that make Strolch really awesome! We use execution to perform a number of actions on a remote device connected to a Strolch agent through WebSockets. This allows serial and parallel execution of actions and of course locking of concurrently used resources.
In an enterprise world reports can never be missed, so we needed an API to create reports. Of course that API was created in a way that all things are done in Strolch: generically. Thus a report is created as a Resource, defining the report object, columns and any relevant joins.
And one of the really cool things is that we have started with a UI for Strolch. There is now an Inspector with which the entire data model of a running agent can be seen. This inspector is built using Polymer and WebComponents and thus can be easily embedded in your application.
To simplify tasks in a web project, there is also a StrolchJs repository where certain Strolch specific things are handled e.g. querying the authenticated user's roles etc.
The release of the next Strolch version isn't defined yet, as we are internally building a project on all these changes and with the release 1.0.0 of that project (which will be soon), we shall perform the next release of Strolch.
Until then, happy coding!
Release Version 1.3.0 released and deployed to Maven Central
We have released a new version of Strolch so that you can now go and use the the latest features in Strolch.
Further we have now deployed Strolch to Maven Central, so it is easier than ever to use Strolch in your projects. No need to download first or use a special repository - just define the dependencies as you would any other dependency.
Some of the new features:
Strolch has also been moved to another organisation on GitHub, so if you're compiling Strolch from source, please update your GIT remote configurations.
Have fun using the latest and greatest version of Strolch!
Opt-In versioning of objects
A major new feature has landed in Strolch. Now, using opt-in, it is possible to have all changes to
the object model be versioned. This means that any change to
Activity is automatically versioned and one can then revert to
this version later on.
This will make it far easier to implement undo operations in applications since it is an inherent part of the lifecycle of objects in Strolch.
Since Strolch is supposed to be used also in small footprint hardware, this option is opt-in.
A side affect of this new feature is that we have for the time being not ported the XML persistence layer. If this is required, then someone drop us a note and we'll check on it.
So now go ahead and add
<enableVersioning>true</enableVersioning> to your
Realm so that versioning is enabled.
Release of Strolch 1.2.0
A few months ago we informed of the soon to be released version 1.1.0. Well, we decided to jump to 1.2.0 because we did some refactorings. All the eitchnet projects have been melted into Strolch and thus now it's all one nice package. This will result in simpler development and less constraints on APIs between the two projects.
Other than that, not much changed, but we are continually working on Strolch, so go grab your latest copy and have fun coding!
Long due update on Strolch development.
Although we have been rather quiet in the last couple of months, anyone viewing Strolch's commit log, will see that we certainly didn't halt Strolch development.
We have been hard at work, using Strolch in projects, which required many new features and fixes. The commit log shows as of today over 180 commits since the release tag 1.0.0.
Some of the most exciting changes are:
Further new features and changes are:
Commandto easily perform system user actions.
strolch_minimal_restprojects to easily get started.
Policyto all root elements.
So, although we've been rather quiet on the blog and on social media, we have not been quiet in Strolch's development. We are planning to release version 1.1.0 soon, so stay tuned!
The ground work of the Strolch planning engine has been laid.
One of the core ideas in building Strolch was to create a planning engine. The planning engine would
work in combination of
Order objects representing customer orders,
objects representing machines, human resources, etc., and
hierarchies defining a workflow.
With the latest couple of commits to Strolch we have now added Activities and a basic planning of
Actions onto Resources. Activities have an ordered list of
IActivityElement which allows
creating an arbitrary deep tree structure of Activity and Action elements.
Action objects have a list of
IValueChange objects which define the start, end and
further value changes over time on a referenced Resource. Thus planning an Activity is done by
iterating the Activity hierarchy and for every Action selecting a relevant Resource and then then
applying the changes of the Action on to the referenced
TimeState on the Resource.
This implementation is currently very simple as it ignores all constraints which a Resource might
have. In further development we shall implement a
Violation model so that UIs can be
built to visualize the over-use of Resources.
In even further steps we would then start implementing algorithms to not just apply the changes onto a Resource, but to actually search the Resource for time slots when the value changes would not violate any constraints applied to the resource.
We are very much looking forward to these new features. Stay tuned for your updates - even though they do take their time to arrive =).
Any good software has some decent documentation explaining concepts, best practices and gives examples.
So this post is to announce that there is now a new page on Strolch's website with a bit of documentation. This first documentation explains the Strolch runtime and some of the do and don't in Strolch code.
Bear with us, writing documentation takes time and can be outdated quickly, so we will make an effort to keep everything up to date and add more documentation, but this is a start.
Finally Version 1.0.0 of Strolch has been released and can be downloaded immediately.
Before 1.0.0 could be released, some major changes were decided, all driven by the first big project using Strolch as its underlying stack. Those changes were minor, and really major, but should make Strolch better and was important for the first release.
Here is a list of the most interesting changes:
Closeableso that they are closed using a try-with-resource block in Java7. The change that was required was to not auto commit. Now a TX is read-only and one has to set the auto commit as the last statement. See this commit for more information.
tx.flush()to allow an implementation to flush part of a transaction, this feature is vital to perform parts of a transaction before deciding if the TX should be committed.
TRANSACTIONALqueries, instead of staying in-memory.
StringMatchModeinstead of just
DateRangeinstead of just
MigrationsHandlerto use to perform code migrations of production data bases where data shouldn't go lost.
Strolch 1.1.0 is already in development and can also be downloaded from the download page. Here you can see the current change list on GitHub. For instance heavy work has been done to implement privilege management by adding a REST API. Looking forward to a wonderful next Strolch release.
DurationParameter and additional minor changes: Release of 1.0.0-RC4 which can be
downloaded on the download page.
While implementing a use case in a Strolch based application it was detected that an essential
parameter type was missing, the
DurationParameter. This parameter currently stores the
value as a long in memory and serializes to
ISO8601. As soon as we move Strolch to
Java8, we will change this to use the
Period class in the new Java8 date and time API.
In addition to the new parameter, a couple of other changes were made:
So, Strolch 1.0.0-RC4 is out the door, go ahead and try it out.
Important feature Database Initialization added: Release of 1.0.0-RC3 which can be downloaded on the download page.
When living continuous integration and continuous delivery, it is vital that things like database migrations and initialization are performed in a controlled, but automatic way.
A Strolch-based application is using the PostgreSQL persistence layer. The implementation understands the concepts of migration, and validating the database schema, but currently a mechanism to automatically initialize the database with a minimal set of data was missing.
Migrating a database for Strolch is mostly a one time thing. The object model in Strolch is quite
static, so there is seldom a need to migrate the database. Domain specific changes, i.e. new
Resources, or adding Parameters to Resources, is not a schema change. Thus, instead of going the way
other frameworks go, e.g. Ruby on Rails, we built the data initialization right into the
Now if the PostgreSQL
PersistenceHandler creates the schema, then it might also
initialize the minimal set of data. For this to work, the
PersistenceHandler checks if
If those flags are enabled, and the schema was created during initialization, then the database is
also initialized with the contents of the XML file configured under key
The database initialization is done as a system user action which must have the name
This is another fail-safe, so that on a production system, this user can simply be deleted.
So, Strolch 1.0.0-RC3 is out the door, go ahead and try it out.
Scratch that RC1, here is the brand new 1.0.0-RC2 which can be downloaded on the download page.
So, as expected there were a few bugs, for instance the Strolch tutorial apps didn't start, so now i fixed those and released an RC2. Go get it and give it a try!
With the Go-Live of a Strolch-based application around the corner, it is time to release Version 1.0.0 of Strolch. To this affect we have now released version 1.0.0-RC1 which can be downloaded on the download page.
Strolch as a component based software agent has been two years in the making. The concepts in Strolch have been taken from a proprietary planning, scheduling and controlling software agent, which was, and is been, used in industrial automation, logistics and production. Strolch was created to bring the concepts, which were working well for small teams to go-live with large projects in short to medium time-frames to the open source world.
Strolch was completely rewritten using the key concepts of a parameterized object model and a component based agent but remembering which clutches the original implementation had, thus trying to eradicate those without bringing in new ones. It might not be perfect in version 1.0.0, but it is a starting point form which to carry on from.
Strolch isn't feature complete by a long shot, but it sure has got many features which make it useable in a concrete project, thus making sure it is not vaporware =)
The following is a list of key features, many of which were driven by concrete project requirements:
With the light weight implementation, where there are basically no third party libraries required for the normal runtime, Strolch has a minimal foot print which allows it to run on small devices for instance a BeagleBone Black. Using the in-memory mode, it is an easy feat to set up test environments with little to no further requirements than the JVM.
So what is planned for the future? Although Strolch has quite a few interesting features, it is by no way feature complete. The greatest wish is for Strolch to become a community driven platform, so many new features will arise in the future, but at least one major future feature which will be tackled in the near future and will certainly drive the next major release is a planning and scheduling engine using a Gantt chart to visualize the schedule.
The planning engine will use the timed values on Resources extensively to create a planning engine on which Workflows can be placed and allowing to detect violations and bottlenecks.
An extension of the planning of the scheduling engine will allow more than just placing Workflows on Resources, but actually searching groups of Resources for a time slot of when to place tasks. This will allow to use capacity constraints to plan and schedule workflows using different algorithms, and respecting calendars etc.
Further time will be spent on giving Strolch it's own UI. Currently the idea is to use Google's Polymer to implement the UI, thus creating reusable widgets that can be used in projects.
So, now the important part is for new users to start using Strolch for their own projects. Go ahead, check out the Downloads page for the latest release and then checkout the two tutorial applications to get yourself up to speed!
Don't hesitate to send us feedback or questions, we will be delighted to help you get your Strolch-based application up and running, or provide feedback to your concerns!
Robert von Burg
Dr. Martin Smock
* Currently Transactional mode is missing concrete implementation for querying for the XML persistence