MBE, Mongo Back End.

First MBE version out

MBE is a backend written in Python 3 that provides database access, authentication, access control and other features on top of the MongoDB document database.

It is basically a blatant attempt of having the cake and eating it, to explore the possibilities given when combining the absolute freedom of a document database with the fine-grained control of a JSON Schema.

It doesn't hurt, of course that the same JSON-schema can be used to validate data directly in the web client interface, for example using angular-schema-form.

Conceptual documentation can be found at http://www.optimalbpm.se/wiki/index.php/MBE .

API documentation can be found at http://www.optimalbpm.se/api/mbe/index.html .

The source as well as a very simple example is found at https://github.com/OptimalBPM/mbe .

Good times!

More WiX articles on Python problems and blogging location

First:

I felt it was time to clear up some more of the WiX-situation with regards to pip on windows.
As, for example, both pyodbc and lxml simply won't install without vcvarsall.bat, several packages aren't installable via pip on Windows.

The most elegant solution to this is not installing Visual Studio on all machines you want to run your application, but to build .msi-installers that are easily included in your installation.

So don't wait, but go and see the article on the Optimal BPM wiki: How to make .msi packages from Pythonlib .exe-files.

I can answer some questions in the comments here if needed.


Second:

This blog will move to optimalbpm.se soon.

Bye!

MongoDB,BPM, QAL 0.4.0, Optimal Sync 0.9.0 and improved WiX article

Releases

Recently, QAL and Optimal Sync(Optimal BPM Tools) was released in new versions(QAL, Optimal Sync). Many a new features are included and especially Optimal Sync is shaping up to become a pretty useful tool. Especially, the Windows installation of Optimal BPM Tools(Optimal Sync) is much improved.

MongoDB

I am currently investigating using MongoDB as a database backend for the system. There is currently a backend written that uses a EAV structure that works in all backends(DB2, Oracle, Postgres, MySQL, SQL server).

However, since Optimal BPM is geared towards simplicity, it is pointless to make the users learn installing and maintaining a complex relational database backend, when possibly, there are better options.

The document-oriented approach of MongoDB seems, at least so far, be a perfect fit for a BPM system. All possible possible issues, like data integrity, schema upgrade issues and similar concerns, are under investigation and hopefully resolved this week.

This means a couple of things for Optimal BPM:

1. It will be even easier to install.
2. It can have a far simpler data layer.
3. The system only needs to support one database backend for installations.
4. QAL doesn't need to support more DDL functionality, and can evolve further into the data mining and transformation direction in a more clean manner.
5. The UBE project, and its upgrader functionality, can be discontinued.

A surprising way of using Optimal Sync, if I choose to develop that functionality, is to make it able to transform from an old MongoDB logical schema to a new, using a old JSON-schema and a new JSON-schema and map the differences. This way one can handle database structure upgrades without having to write scary upgrade scripts.

WiX

The bane of many a developer, WiX, has now been honored by an improved write-up at the wiki. The script/custom action section has been moved to its own article:  http://www.optimalbpm.se/wiki/index.php/Wix_and_scripting_languages .
The old article is now more as it is supposed to be, a pre-tutorial introduction.

QAL API documentation

The QAL API documentation is now online for your browsing pleasure!

Python3-Sphinx was used, a small article on that subject may develop over time as well.


Cheers!

Windows installer done at last!

Phew. That was actually pretty hard. The WiX and MSI documentation is both lacking and confusing.

Anyway, the installer is now available for download at the files section at source forge.

It is burn-based, and downloads dependency packages and installs them.

As I mentioned before, I made a WiX primer, I have now updated that with some information on how to install pip packages:
http://www.optimalbpm.se/wiki/index.php/WiX.


Cheers!

WiX, .msi and a setuptools(easy install) and pip bundle

Hi,

I am forging ahead with the making of the .msi-files for the windows installation of Optimal BPM tools (or rather Optimal Sync, to be fair).

During the process of making the installation bundle(I want to include everything) i have been forced to create som  .msi:s that I would think could be pretty useful outside this project, namely a setuptools and pip windows installation bundle. Please download and if you encounter any problem, just create a ticket at the Sourceforge project page.

If course, for a Python application, these programs are very important. So now there is a way to easily include easy install and pip in an Python 3.3 windows deployment for those who want that. The installation checks for a Python 3.3 installation and installs the files in its /Scripts-folder.

By the way, WiX is one of the least well documented tools i have ever encountered. At the same time it is pretty complicated. And strange. So it hasn't been easy. Far from it.

However, in the end, I have managed to create a pretty flexible setup using WiX preprocessor variables. Which actually works in a predictable manner as opposed to WiX Properties and normal WiXVariable constructs which might or might not be available at "bind" time.

My current recommendation is to use preprocessor variables instead of the other stuff as they don't resolve in an equally predictable manner.
I will elaborate on that further on my writeup later on.



Until then, have a nice time.

Windows, MSI and fixes

Hi everybody,

The seriously bug fixed Optimal Sync(as of now at 0.8.3)  is about to be installable on Windows as well soon. I have started building an .msi-package, which turned out to be a bit more problematic than expected. However, I think I have overcome most of the problems.

So much, actually, that I have felt compelled to poste a guide on how WiX works and its caveats. The guide is thought of as a primer before you get into the official tutorial, which is a bit wordy and difficult to get.

I consider the problems I encountered quite typical of what most that develop an .msi-package encounters and that my example file is more useful. Especially, I use the paraffin.exe-utility instead of the quite insufficient heat.exe . I would imagine that most does, maybe the article can save them some time.

Anyway, the guide is at the wiki, here, and I hope it will help you understand WiX and its somewhat maddening quirks a bit better.

Cheers!