Pics from the Victor Wooten Concert Saturday Night.

It was great night. I drove down with a couple friends (one which happens to be my old bass instructor). I also ran into an old friend down at the show. Good times!

It’s been two months since I have taken the time to write anything on my blog. But the work is still going on. Friday we met to discuss the next steps in the development of whatever it is we are developing. I decided that the next step for me would be to get a server up and running to make it feel more tangable. Since I already had plans for Saturday that involved setting up a Fedora 5 server, I decided that would be the day. So after getting done with the Fedora setup in the morning I drove off to go to the local computer store. After messing around with the Sata drive for several hours I finally gave up and went to bed. With a clear head the next morning I install a simple 10 Gig IDE that I already had laying around. Everything else runs smooth and we now have our server ready to go.

Saturday morining 8:00 am I wake up roll out of bed, try and make myself presentable as quickly as possible and jump in the car to drive 30 miles south of my house. Today is the day we finish setting up our first Linux Fedora 5 server. On the agenda today is getting Apache 2.2.2 to talk with Tomcat 5.5.something Subversion up and running with our source code imported, Subversion working with Apache 2.2.2 and finally if we have time get Maven 2 loaded and the CruiseControl application installed. Since some of this stuff I have only done one time prior it was a full schedule to say the least.

9:00 am
Luckily Tom has already set up the server minus the XWindows libraries but including Tomcat 5, Subversion, and Apache 2.2.

Now we need to get the Apache server to communicate with the Tomcat server. This is not as easy as it sounds since the documentation on the Tomcat site has seemingly been abanden long ago. We copied down the .so file that we suppose would work for the Intel based x86 architecture and go about setting up the httpd.conf file to include the new shared library, add a workers.properties file to the httpd/conf directory and modify the server.xml file under the Tomcat installation to enable AJP13. Once completed we get repeated errors from the http server (Apache) exclaiming that the mod_jk.so file is bad. We go through several girations of this before, including investigating moving to another server Jetty or Resin.

For the Impatient (What works):
1.) Get Fedora 5 installled minus xWindows.
2.) Type “service httpd status” to get the status of Apache.
3.) If apache is not installed then install it using “yum install httpd”
4.) Try starting Tomcat “service tomcat5 start”
5.) If Tomcat is missing then type “yum install tomcat5”
6.) Test the installation “telnet localhost 80”

Now to get Tomcat working with Apache use the Proxy approach
1.) finish…. later. collecting our details.

I know, I know, I know… I have already been hassled for choosing the Sempron chip. I am not a hardware guy and the goal for this stage of the game is to get a server in the sky for less then $500. It turns out that this one will cost me less then $390 by the time I take the 200Gg. Sata drive back that I don’t need. 10 Gigs. will work for now.

The server:
Case: Antec NSK1300
Processor: AMD Sempron Processor 3000+
Motherboard: MSI - K9VGM - V
RAM: 1 GB DDR2
Harddrive: 10 GB IDE hardrive

We have decided on the name Open-Enterprise since we feel that this describes what we are doing. The meeting yesterday morning went very well with Marc and myself slating out the first bit of work to be done. The list falls roughly into Marc working on the HR interface while  I am working on the core data access, service layer, and util classes.  We hope to build very light weight modules that can be modified and maintened easily. Part of or discussion centered on whether or not the service layer would be required since what we see happening mostly in the module is CRUD database activity. We decided on a mixed approach using the ServiceLocator pattern attaching our DAO’s to the ServiceLocator. If we need a further seperation between view and data access layer we can simply place a service in between the two layers and redirect the calls from view layer, using the ServiceLocator, to a newly created Service component.

Another part of the dicussion centered around how SOA, Mule, BPEL, and the OE modules in general would remain generic but yet be able to leverage the information from other modules without braking with our highly decoupled model.  It is my opinion that WS Interface specifications will need to be generated for each module in the OE suite.  The combination of these specifications will form what I term the Eco system that will sit on top a generic service bus (Mule).

While researching Mule last night I ran into a couple of terms that I had heard used but was unfamiliar with their meanings.

The Terms: Staged Event-Driven Architecture SEDA and Representational State Transfer REST or REST(ful) systems.

These links helped me to understand the terms a little better. 

 http://www.eecs.harvard.edu/~mdw/proj/seda/

http://www.xfront.com/REST-Web-Services.html

We hope to have some architectual drawings a general road map and some sample code soon. 

I haven't had a lot of time to post on this site since getting back from vacation. But some great things have happened since then. Marc Johnson a senior level consultant in Cincinatti has decided to start helping with the project. He has been researching all the available open source ERP systems on the market today. His research covers OpenMfg, OfBiz, … (i will finish this list later).  We have also started the brain storming process determining what work will need to be done first and what we will include in our full version of the software.

Below is an initial list:

1. Finance
2. HR
3. Order Management
4. Inventory Management
5. Purchasing
6. Customer
7. E-commerce
8. Point of Sale

Our next step will be to put together a rough object model focusing on a single module for the application, like Human Resources. We would like to develop a web based solution that is self contained and "Simple".  Not simple in missing functionality but simple in that we will try to cover this domain area adding major functions and leaving out all the minor directions that can turn a project into an ocean boiling machine.

Sorry if my post is not coherent. Its late and I am sitting at Panera. : )

Just getting started today. My idea for starting this blog is to journal my experiences as I develop Enterprise Applications using Open Source Java. My current interest are around using SOA to combine web based ERP applications to evolve into an Open Source framework for delivering value to mid-size and small companies with little or no risk.

Open Source Top Level Frameworks:
- Spring
- Wicket
- Hibernate
- Mule