For us at Amway Corp, a key part of creating batch processes, with Java, was using the LaunchClient command and
J2EE Client applications. We felt we were very close to being able to run our Java batch processes on the
application server. But more trials and tribulations were ahead of us.
We created a J2EE Client application\program that would call a "hello world" EJB.
After deploying the code to...
Our first Java application (10 years ago) was a migration of a legacy application.
The legacy application consisted of a number of screens and a number of batch processes.
Migrating the screens to Java technology seemed straight forward.
In theory, they would be a direct use of the MVC pattern (EJB, JSP, Servlet). Easy.
But what about the batch processes? They didn't seem to fit the MVC pattern....
Our Java application supports my company's (Amway Corp) Customer and Sales Compensation areas.
This is a very unique and complex part the Amway's business model.
The application requires a large database to store business-related data.
The database consists of dozens of tables and millions of rows.
It contains transactional data and summarized data.
The size of the database grows daily.
As our Java project progressed, we began to add new members to our development team.
This meant many resumes to review and many interviews to conduct.
It was to become quite a time consuming chore for the interviewers.
During a portion of the interview, a series of technical questions about Java are asked.
The goal behind these questions is to allow the interviewee to talk to us about Java.
During the initial architecture and analysis of our J2EE-based application,
one Java issue generated a lot of attention on our team : Enterprise Java Beans or EJBs.
Should we use EJBs?
What flavor of EJBs should we use?
At the time, we received no practical advice on EJB usage.
We got a lot of general advice. "Use what is best for you, etc."
Quite often, we were referred to a diagram with a lot...