I've recently started to get into Camunda (version 7). I have already develoiped a few workflows, and everything is running smoothly, including the basic Cockpit, which I find highly useful.
Now I want to put my workflows into production. What are the limitations of doing so, using only the Community edition, instead of the Enterprise one? Am I losing out on something important by not going for the full commercial service?
Will I encounter any limitations down the road that will block my workflows?
You can find a comparison of Camunda 7 CE and EE here:
https://camunda.com/enterprise/
There is no (e.g. volume) limitation on engine level you will be surprised by later on. Apart from commercial support, the additional Cockpit features are very useful and Optimize to add business analytics to your environment may also be of interest.
Shortly before Open Text acquired Actuate I stood up an iHub F-Type server on Amazon so that people in my little company could have access to reports and information. Now that the acquision is completed Open Text has discontinued support and availability for F-Type and is directing users like me to full blown iHub which they make available free for 45 days (which they will, so they say, extend to 90 days) and afterwards it is a paid service and not affordable for me.
My question is...how are others providing for cloud based reporting for users in a way that is affordable? I am aware of this project that appears to offer something like what F-Type used to. Has anyone tried this ReportServer? Any thoughts or experiences you could share?
I am also open to other reporting platforms (Jasper, etc.) if they offer what I am after. This would be my least preferable option but my users wouldn't really know or care so I could do it if I needed to?
Download the latest BIRT Runtime Release Build (4.5.0), put the engine in a server, add scripts to run the reports you want.
http://download.eclipse.org/birt/downloads/build.php?build=R-R1-4_5_0-201506092134
I am trying to find the best way to maintain a bug tracker and feature/upgrade requests for clients on web development projects. Ideally it would be an open source system we can have installed on a sub domain of our site.
This will then allow each client to login and add bugs/features/upgrade which we can hopefully keep track of.
I have been trying to use and implement trac but it just feels too "techy" and a little too complex for setup.
Any ideas?
Thanks in advance,
Shadi
UPDATE
Just to clarify, we do want a system to install on our servers, the trouble with trac is the install process in relation to what you get and how clients feel about it is a little poor. But if something is awesome but has a complex setup, that isn't a problem...
Mantis is another. Simple UI.
http://www.mantisbt.org/
If you have Linux boxes, trac is much easier to install. Config takes a bit, but wasn't a problem in my experience.
I've heard good things about FogBugz. :)
If you don't want to install it yourself they have a hosted solution also.
Have you taken a look a Bugzilla? Not sure if it meets all your needs but it is free but you can get paid support. It's an open source project AFAIK.
I started exploring CouchDB and I am interested in following:
Is there or will there be a Windows install?
If there is, is there a shared hosting provider that offers CouchDB?
Not knowing much about it, can it be somehow embedded in my application or bin deployed (don't laugh).
The most reliable source is the CouchDB download page
There are several places offering CouchDb hosting. Besides Cloudant, you can use most Infrastructure-as-a-Service parties like Google, AWS, etc.
This question was asked (and answered) elsewhere on StackOverflow here and here.
There's a Windows version now, available on CouchIO (http://www.couch.io/get) blog.
Download & Unzip
Double-Click bin\couchdb
Relax!
Visit http://127.0.0.1:5984/_utils
There's been a fully compatible Windows build of CouchDB shortly after every source release, since the initial 1.0.0 release over 18 months ago. You can get this directly from the Apache CouchDB mirrors http://couchdb.apache.org/ now.
NB the embedded test suite is actually for developer testing; due to subtle timing constraints not all tests will pass first time round on every machine. In the next release of CouchDB, the tests will be done outside the browser which will be both simpler and more robust.
Please up-vote this so we have the right information to hand.
Since this question was posted, there is a Windows download available at https://couchdb.apache.org/ .
I need to build a simple, single user database application for Windows. Main requirements are independence from windows version and installed software. What technologies (language/framework) would you recommend? My preference for language is the Visual Basic.
EDIT: What about VB.Net and SQL Server Compact Edition?
I would recommend Sqlite. It's completely self-contained, and public domain so there are no license issues at all.
Single user or multi user?
For single user, the answer would be SQLite
For multi user (or multithread), try MySQL or PostgreSQL.
Since your requirement is a windows based application i would suggest that you go with sql server 2005 express edition which is a free tool, but with certain small limitations. you can upgrade to a bigger version when you go with a paid version.
There are other DB engines like SQL Lite or FireBird, choose them if the support and growth options they provide are good enough for you
Additionally, Visual Basic is eof lifed. VB.NET might be a better windows based platform currently. It would give a better platform / features to start with and when you want to expand the talent you have working on the project, i assume .NET talent might be more available than programmers who want to work with a dead language.
duplicate of What options are there for a quick embedded DB in .NET?
I'll repeat my answer from there:
"Or theres Esent, the built in database that exists in every copy of windows. Read about it here: http://ayende.com/Blog/archive/2008/12/23/hidden-windows-gems-extensible-storage-engine.aspx" and http://www.codeplex.com/ManagedEsent
SQLite will work for a local desktop application. If you want several users, a few gigas of data, and multiple connections I would use mysql or Firebird.
http://www.mysql.com/
http://www.firebirdsql.org/
FireBird SQL server will be thing of choice. It can be used in both embedded and multiuser mode like traditional databases. It implements many of the SQL standards and has strong community base. It is available for Windows, Linux, Solaris, OS X, HP-UX
As mentioned, SQLite is a great single-user database. This page has VB/SQLite examples. Once concerns is that SQLite parses foreign key constraints, but does not enforce them. You can use this code to generate "foreign key triggers" for SQLite, thus gaining an easy to use database with FK constraints.
Depending on how demanding your database needs are, though, you might want to consider MS Access.
I used SQL Server Compact Edition. It's like sqllite. A single SDF file accessed using ADO.NET.
You can develop your application using Visual Basic .NET and manage you database (add tables, columns, constraints, etc...) using Visual Studio.
SQLite may be what you are looking for. http://www.sqlite.org/
Depending on your needs for the application.
You could use SQLLite which is a very nice database with no installation required.
You could also use Microsoft SQL Server: SQL Server Compact 3.5.
Both are free!
It's not quite clear from your post whether you want a web application or not.
For a web application, MySQL works effectively on the Windows platform. You also have nearly limitless options for development environment including, PHP, Ruby on Rails, Django, and .Net.
If you are looking at a desktop application, MS Access might be suitable ... incredible easy for simple applications.
Well, assuming you don't have any prior experience...
You need some kind of persistence storage (for example a database) and a client.
For the storage you could use almost anything. For example you could create your DB in MS Access and just ship it as a file, using ADO to access it.
Other options are MS SQL Express edition (comes pre-installed on some machines or could be installed for free) and plenty of open source databases like SQLite
For the client side you could not go wrong with VBScript and ADO (using OLE DB drivers). They come with every Windows installation since Dark Ages, you will have plenty of references/tutorials/answers online.
A drawback: no UI to speak of, so you'll have to build a command line interface (which was for a 'simple' application).
If you want to build a UI I would suggest using .NET WinForms. The overhead will be substantially bigger but .NET is now installed on all XP/Vista machines and even if it is not you could always install the framework with you application.
If you want to build application that can move to other pc easily,I prefer Microsoft Access it is small database easy to use and no need to install.It suites for application like Addressbook,mini crud system.
But if you want to develop enterprise database system you should use MySQL instead.
I do not understand what you mean with "independence form [...] installed software". You ever need at least the DBMS installed as well as one client or user interface.
I recommend using MS Access. It is easy and cheap for simple, single user tasks and rapid prototyping development. Only development version have to be bought ("normal" Access) to create DBs. Runtime version of Access 2007 can be downloaded free of cost from Microsoft Homepage - for using only the database you created.
Also it combines DBMS and GUI frontend in same tool.
Dare I mention MS Access...?
If you are looking for small footprint (up to a few MB) and easy deployment (end-user should only install your application to get it working), then your options are SQLite and Firebird embedded.
Of those two, I'd pick Firebird any time, because of it's full support for SQL (you can't, for example, drop a column in SQLite), ACID compliance, and ability to go client/server without any changes (just change the connection string from embedded to server) to the code if you ever decide to let multiple users work on the same database.
Not to mention that you can use full server to develop (which means your application and database administration tool can be connected to database at the same time).
I'm successfully using Turbo Delphi (free for commercial and no commercial use) + ZeosLib (zeos.firmos.at).
The only things you need to distribute with your .exe are the database client dlls (no need to install the client, just put the dlls in the same directory).
Would Kexi work?
I can recommend from personal experience "My Visual database"
free, no code, no sql, just drag and drop.
http://myvisualdatabase.com/
Best Option would be to create a Win32 native application using Delphi and use SQLLite as the database.
Reason being Delphi can produce native win32 applications without any other product being installed on the machine.