Re: Using a single JVM

We have used the REST API methodology for several years now, even before
it had an acronym.

We do this with Java/JSP applications as well as .Net/ASPX.

This is a great way to be calling simple Java services and ASPX from an
RPG program or wrapped in a CL command. Talk about new life for CL
commands !!

I would actually recommend this method before using data queues
personally because your application gets direct response from the
service instead of needing to go through data queue plumbing.

And only 1 JVM instance !!

Just my two cents....

Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT


-----Original Message-----

message: 5
date: Thu, 20 Nov 2008 09:22:17 -0600
from: David Gibbs <david@xxxxxxxxxxxx>
subject: Re: Using a single JVM

Joe Pluta wrote:

Another option that's really powerful is to use a web application
server to expose business logic as web services, either via SOAP or
REST (I prefer the latter for intracompany work). Let the application
server handle all of the session management issues. You also get the
benefit of being able to share logic with other business units if
needed.

In general, I agree with Joe on this.

As with all implementations, you need to take the context into account.

If the application is highly focused and not likely to be shared with
applications on other systems, I think the data queue method is probably
easier.

A web service approach is much more flexible and reusable ... but
probably more difficult to implement and use in RPG. It's _much_ easier
to use in other languages though (java, php, .net, etc).

The key thing to consider is: think about where and how your application
is going to be used down the road and choose the best solution with that
target in mind.

david