Free tier software for linux

ControlTier application aims to be a complete enterprise-ready automation solution. It is our goal to provide the tools needed to automate the build, release, deployment, configuration, and control of distributed, multi-tier applications. When it comes to ease of use and out of the box functionality, we havent met all of our goals yet but we are working hard to do so. Any comments, questions, or criticisms are always welcome.
ControlTier coordinates and automates the chain of events that take place when you build and deploy a collection of integrated applications (what we call a "site").
Youll use ControlTier to:
- Coordinate your build processes (interfaces with build tools like Ant)
- Manage your build artifacts and other deployable resources in a structured repository
- Coordinate the distribution, configuration, and control of the various applications that makeup a site
Unlike most automation solutions that are focused exclusively on hardware and OS provisioning in production environments, ControlTier was built to focus on the application build and deployment processes that run all the way from Development, through QA, and into Production.
Main features:
- Framework for sequencing and coordinating automation
- Configuration management database
- Logical remote management (manage lots of things as one logical unit, no matter where they physically reside)
- GUI based development and operations tools
- Improved reuse and componentization of your existing scripts and configurations
- Change detection and configuration validation
- Application status discovery and detection
- Fine-grain access control
- Release migration tools
- Logging (with environment context built-in)
- Reporting and correlation tools
- Cross-platform support (Linux, Solaris, Windows, Mac OS X, etc.)
Enhancements:
- This is a major upgrade of both the ControlTier automation framework as well as the pre-built automation modules and workflows that come with the framework.

GPS Tracker project allows someone to track a GPS enabled cell phone using Google maps. For this project I used a Motorola i355 cell phone on the Sprint/Nextel network.
You need to have a data plan so that you can make updates to your website from the cellphone. Please read the ReadMe.txt file in the download for installation instructions. I hope you enjoy the project. If you have any questions, feel free ask them in the forum.
There are two projects available. The first project is built with .NET and Microsoft SQL Server. The second project is built with PHP and MySQL. If you have any suggestions, please feel free to let me know. Both projects use java (J2ME) on the phone.
How It Works:
None of the code for this project is very difficult, but it does span a number of tiers and languages which may be unfamiliar to some. Figure 1 shows the data flow from phone to Google map.
Phone
Lets start with the code on the phone. This app is written in java using Java 2 Micro Edition (J2ME). Java is very similar to C#. As you look through the code, the only thing that might confuse a C# coder is the vector. A java vector is pretty much a C# ArrayList, a dynamic array. There are 2 classes in the app, LBSMidlet7 and Qworker. A midlet is an app that runs on cell phones. Take a look at the class definition. It extends the MIDlet class and implements a LocationListener interface. That means that we need to put all the method definitions of that interface into our class. Well get to that in a bit, right now lets look at the constructor.
We do 2 things in the constructor. We create a QWorker object and pass it "this" and the website that we will be uploading to. The getAppProperty method gets attributes out of the JAD file. Open the JAD file in your favorite text editor and there youll see the webpage that youll be sending GPS data to. Notice how were passing "this" to the GWorker object? Thats the LBSMidlet7 object. Take a quick look at the QWorker class, it extends the Thread class. Thats why we call worker.start() in the LBSMidlet7 constructor. We want to start our worker thread.
When you start a thread, what you are doing is creating an object and then running that objects run() method. Take a look at the run method. It has an endless loop and in the loop the first thing it does is call queue.wait(). Look at the definition of the queue. The queue is an abstract data type (ADT), it just like a queue at a bank, enter the queue at the back of the line and leave the queue when you get to the front of the line. Look at the definition of the queue, its our vector (dynamic array). When you call wait() on an object within a class that extends the Thread class, it puts that object to sleep. Think about that a little. When we hit that line, our QWorker object is now waiting... Whats it waiting for? Well get to that in a minute. Before we do that, take a look at the synchronized keyword. Notice that its wrapping the queue. What that does is it puts a lock on the queue and tells all other processes not to touch the queue until that little block of code is done with it.
Ok, so now weve started a worker thread and put it to sleep. Lets now go back to the LBSMidlet7 class and take a look at the startApp() method. In the lifecycle of a midlet, the constructor is called once and then the startApp() method is called next. In fact it can be called several times, like for instance when you close a flip phone and then open it again. What happens is that the app is suspended and when you flip the phone open again, startApp() is called again. In startApp(), we get our display and then we create a LocationProvider if one hasnt already been created and we create another thread... Why are we creating all these threads? Good question. When a midlet (app) is suspended, the backgroud threads that are created keep running. That allows us to get our GPS data and send it to our webserver while we do other important stuff, like make phone calls.
The LocationProvider is what gets our GPS data. First we create a criteria, were using the default, but you can set stuff like accuracy, response time etc. Next we create our Location Listener. Its pretty much just what it sounds like. Here you can set the interval for how often you want to get GPS data. Its currently set to 60 which is in seconds. When data comes in, the locationUpdated() method is called. This is another one of the required methods in the LocationListener interface. Here we create yet another thread and call getLocation(). The getLocation() method gets the GPS coordinates, creates a queryString which we will send to the web server a little later and then calls worker.addToQueue in the QWorker class.
Lets go back over to the QWorker class and see what happens in that method. It add the queryString to the queue and then calls queue.notify(). Guess what queue.notify() does? It wakes up our sleeping QWorker thread and tells it to get to work! Notice that our calls to the queue are once again wrapped in a synchronized block. Please practice safe threading... When notify() is called on a thread, what it does is go back to the run() method and execute the next line of code right after where we told the queue to wait(). So now we are just about ready to send the GPS data to the web server. We have a couple of interesting lines of code there. First we call peekInQueue() which gets the queryString out of the queue but leaves it there for now. Then it sends the queryString to the getUrl method which attempts to send the queryString to our web server. If its successful, we can remove the queryString from the queue. If not, we leave the queryString in the queue and try to send it to the webserver again later.
Why in the world do we have this complicated queue here? Im glad you asked. There may be times when you are receiving GPS data but are not actually in an area that has a cell phone connection. If we dont have a cell phone connection, we cant send our GPS data to our web server. So we stick our queryString in our queue and wait until we get back into an area with cell phone connectability. Can you hear me now?
Well, weve spent a pretty fair bit of time explaining the phone code. Its a little complicated but its important to know whats going on if you want to take the code and make modifications to it to suit your needs. Heres a good article on the Sun website to let you know about more capabilities of the Location Based Services API. Right about now, our queryString should be arriving at our website, lets catch up to it and see what happens.
Enhancements:
- Added comments to code

dtoGe project is a java source generation tool that can ease the development of multi-tier systems by offering a reliable solution to obtain the data transfer objects out of the domain model objects without hand-writting additional code.

Using a simple set of javadoc tags, dtoGen™ provides the possibility to define the whole set of data transfer objects used by your system.

AirFart is a wireless tool created to detect wireless devices, calculate their signal strengths, and present them to the user in an easy-to-understand fashion. It is written in C/C++ with a GTK front end. Airfart supports all wireless network cards supported by the linux-wlan-ng Prism2 driver that provide hardware signal strength information in the "raw signal" format (ssi_type 3). Airfart has a modular n-tier architecture with the data collection at the bottom tier and a graphical user interface at the top.
Following suit with the major players in the wireless arena, we decided the air prefix best categorizes airfart. Further, re-arrange the letters in traf and you can get fart. So, our mission is to sniff out wireless devices who broadcast a scent.
We hope our name isnt offensive. 99% of the people we have come in contact with have thought the name is clever and funny. Remember, no one is forcing you to use it...
Enhancements:
- Updated interface.c and Makefile, now graphics are located in /usr/share/pixmaps/airfart
- Updated vendor.c, now manuf file is located in /usr/share/airfart;
- need to do make install before running airfart
- Added initial Gentoo ebuild file; still needs work
- Number of packets received per ethernet address is now stored
- Tweaked Makefile to not bail out if directories already exist
- Added the star to the about entry in help
- Added GUI support for Packet Count
- Added a column for numerical (percentage) strength
- Added support for a config file and a basic preferences box
- Changes do not yet affect behaviour of the program

eZ calendar provides a calendar extension for the eZ publish CMS.
eZ calendar is an eZ publish 2 module that provides an advanced Web based calendar application.
It supports recurring events, comments, groups, types, categories, priorities, status, comments, files, links, sorting, month, week, day, and year views, tooltips, JSCalendar date selection, and new design templates.
It features very flexible security and supports permissions on the groups that can view, add, edit, and delete events.
Main features:
- With eZ calendar you can filter the events based on the event type and for which group of people the event concerns. The eZ calendar features very flexible security and permissions on calendar administration depending on user groups specified in the admin which can view, add, edit, delete events. The public user in the prerequisite group can view either by day, month or year.
- It also supports a new dhtml, css user interphase, advanced repeat event, file/image/map attachments, directions link, html descriptions, multi-tier event groupings and many more features .
- eZ calendar is a powerful component to add into any existing eZ publish installation, especially used for collaborative and informative sites.
- eZ calendar provides calendar features which match most handheld and computer desktop datebook / calendar applications.
- eZ calendar has been extended to support every possible kind of reoccurring event type you can imagine.
- eZ calendar is a standalone module, which depends on the eZ publish framework, modules and classes.
- A special thanks goes out to everyone in the eZ publish user community who contributed to eZ calendars design, development, motivation, funding, testing, extension, feedback and so much more .

HSE (Hibernate, Spring, Echo2) is a three-tier base application for Echo2. It is designed to be a starting point for writing robust AJAX applications in Java, Spring, and Hibernate.
Main features:
Hibernate, Spring, Echo2 integration:
- All three technologies are matched cohesively together to provide a robust base for your AJAX applications.
3-Tier Architecture:
- Follows the established pattern of separating the application into data, business, and user-interface tiers.
Security:
- Allows username/password logon, logoff, and permission checking.
- Permissions can be queried using hasPermission(), or enforced using requirePermission().
- Enforcement is done in the business tier.
- Group-based Permission System:
- Permissions are group based, which means that users gain permissions based on their group membership (A user can be a member of only one group).
- Groups can have multiple permissions, and associate levels for each permission.
- The base application uses two methods for interpreting permission levels.
Input Validation:
- A simple and flexible validation system that can handle most common input field validations.
- The custom screen and requestor components can display validation error alerts, and can automatically set focus to the offending input field.
User Editor:
- Example on-screen CRUD editor allowing modification of user properties, as well as group membership.
Group Editor:
- Example on-screen CRUD editor allowing modification of group properties, as well as assigning permission levels.

OpenSubsystemss goal is to provide consistent set of business components that solve particular area of interest such as inventory management, order processing, shopping, email and fax communication, document management, imaging and others.
There are many frameworks and libraries attempting to make life of developers easier. Most of them focus on improving certain technology (EJB) or technical problem such as persistence in Java (Hibernate) or view tier for web applications (Struts).
There are very few that actually give developers fully functional business components that are immediately available to be integrated into their application and solve specific business needs. OpenSubsystems is one of them.
OpenSubsystems is dedicated to providing highest quality products by paying attention to innovative design, carefull implementation and thorough testing while staying true to the spirit of open source.
All our development processes and products are extensively documented and available for review and use to wide audience of business analysts, developers and testers.
Enhancements:
Feature requests
Core
- 1674491Generalize DataFactory interfaces by requiring domain id
- 1674470Simplify DatabaseOperation classes by removing redundant arguments
- 1674438Simplify DatabaseSchema interface/impl for read-only schemas
- 1674289Change license to GPL v2 only for Core
Bugs
Core
- 1674498IOException thrown by FileUtils when directory exists
- 1674495NullPointerException in StringUtils.concat method
- 1674483Servlet preservice method not called when login is required
- 1674420NullPointerException in DatabaseConnectionFactoryImpl class
- 1630270NoSuchElement exception when using XAPool

Caravan Business Server is an extremely easy to use comprehensive development and deployment framework which has been used to build Enterprise wide, mission critical Web-based applications.
It includes, as a seamless integrated package, an easy to use Scripting Language, Search Engine, Database Engine, a Web Server and a Communication Server, which makes it a 1-Tier Architecture.
Caravan Business Server is currently available on Linux. Once an application is developed on any OS, the same can be simply redeployed on any other OS without making any changes.