Application Platform decision
The application we are about to design is for a health care industry.
A very high level view of the application would be that it
is a way to gather a prospective client information as a RFP which
when we win will get converted into an actual contract after collection
information from various departments that involves a work rule engine
kind of scenario. So there are bunch of approvals that have to heppen
to move the partial contract from one department to another and there are
lots of approvals. The sales people will also have the ability to
take the application to the prospective client and should be able to take
information offline and then we able synch up with the database (this will
involve only a portion of the application). I would like to get input from
all of you about how I can convince management to go with Java as our application platform.
Below are some of the requirements of the application
1) It need to interact with another application that is written in Powerbuilder,
C, with oracle as the database.
2) It has to operate in an OFFLINE mode (atleast a portion of application)
3) about 300 users are expected to work on it concurrently
4) A work flow engine needs to be there to facilitate some pretty complex
work flow rules ( any suggestions)
[1396 byte] By [
kris727] at [2007-9-30 19:12:56]
> I would
> like to get input from
> all of you about how I can convince management to go
> with Java as our application platform.
Maybe you could start by telling us why you think it should be Java. If nothing else, it would be good practice for how to frame your argument. And if you realize you don't have any good reason for Java, then you can go do some more research.
> Below are some of the requirements of the application
>
> 1) It need to interact with another application that
> is written in Powerbuilder,
> C, with oracle as the database.
Don't know about C. But my previous company has a PowerBuilder app that interacts with Java. This is done with a Jaguar app server. The server hosts the PB module, which interacts with the Java via CORBA. I think PB now has a simpler way to interface with Java, but I don't remember the details. Something about importing a Java file and automatically generating a stub. It's a bit fuzzy since I haven't actually used that technique.
> 2) It has to operate in an OFFLINE mode (atleast a
> portion of application)
>
> 3) about 300 users are expected to work on it
> concurrently
>
> 4) A work flow engine needs to be there to facilitate
> some pretty complex
> work flow rules ( any suggestions)
Obviously none of these present any problem for Java, but I don't see them as particularly suitable for Java over some other language, either.
