This week's book giveaway is in the Agile and Other Processes forum. We're giving away four copies of Real-World Software Development: A Project-Driven Guide to Fundamentals in Java and have Dr. Raoul-Gabriel Urma & Richard Warburton on-line! See this thread for details.
We have an existing batch program application running on Unix which basically database transactions like reading input data from files and write to the database. We also have a web application using JDK 1.5, EJB 3.0, JPA, Hibernate, JBoss, JSF, JBPM, SOA, ESB, Seam framework, Oracle 10g etc.
Wondering what would be the best Java related technology to adapt to convert our old unix batch programs?
Currently we are just converting all the business rules into separate Java standalone application which we would execute from Unix shell scripts which are run through a job scheduler.
We have an existing batch program application running on Unix which basically database transactions like reading input data from files and write to the database
It depends. How big are the files? How often does this need to execute? Are the data files different from file to file? How time sensitive is the information getting into the database? How manual of a process is it now?
Writing some shell scripts to kick of some java code isn't a bad idea. You could also consider doing it with Groovy and removing shell scripts from the requirements. You could also look into a feed engine if you need something more robust and configurable. For example OSFE but that might be overkill for your needs.
Happiness is not a goal ... it's a by-product of a life well lived - Eleanor Roosevelt. Tiny ad: