Either make it a data queue server NEP-style app or possibly turn it into a REST style API with JSP, but that's probably a lot more work than you want to do.
SAP experience isn't a bad thing to gain.
Regards,
Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
----------------------------------------------------------------------
message: 1
date: Fri, 3 Apr 2015 17:41:59 -0500
from: "Steve Landess" <sjl_abc@xxxxxxxxxxx>
subject: Best practice for a server program using Java
All -
My client is in the process of converting from JDE to SAP. ;-(
I have written a "server" RPG program which calls a Java program which calls an ABAP RFC which retrieves inventory availability information from the SAP system in order to provide visibility of inventory on the JDE side.
The server can return one or more rows of information from SAP:
Item, Lot number, lot date, Qty
It was a challenge, and now I know much more about SAP NetWeaver
(Eclipse-based) RPG/JNI/Java, and could almost call myself a Java programmer.
However, the start-up time for the JVM is bugging me, and in doing some research I don't think I want 100 different users calling this server and having to start up a JVM in each of their interactive jobs.
What is the best way to have a single instance of this "server" running on the IBM i system and having the users' jobs sending requests to this server and getting back results?
Regards,
Steve
------------------------------
message: 2
date: Fri, 3 Apr 2015 15:47:26 -0700
from: Alan Campin <alan0307d@xxxxxxxxx>
subject: Re: Best practice for a server program using Java
Assumption. Everything is on i. Use a data queue server. Simple and perfect for what you want to do.
On Fri, Apr 3, 2015 at 3:41 PM, Steve Landess <sjl_abc@xxxxxxxxxxx> wrote:
Confidentiality Notice: This email, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this email is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this email is prohibited. If you have received this email in error, please notify the sender by replying to this message and delete this email immediately.
midrange.com
