Hi,

I have migrated (very old) VaGen code to EGL. Programs have Text UI and all the logic, database access etc are inside a program.

I've generated EGL code into a Application Client project. And then built deployable file (according to IBM Java Web Start Deployment Sample), installed it into Websphere Application Server. And then run it with Java Web Start.

Am I on the right track here? Is there a better solution to deploy TUI based programs? Should I generate it to some other way?

I'm asking because my problem now is that the software is working only  if I use direct database access (jdbc). But that is not a good solution because JWS is loading the software into user's workstation and database access cannot be made from there. Ideally database traffic should go through WAS server where the software is actually installed. But I can't find a way to do it.

Any help would be appreciated, thanks

Petri

Hi Petri,

You are going the wrong way.

The TextUI program is a legacy green screen or terminal 3270 and this application do not run in Web Browser and do not need WAS Server.

You need create EGL Project  type General Project and if you want to generate Java the choose Target Runtime Platform is Java.

If you need more help, please call me inbox hsieh@dataexpressonline.com.br

Best regards,

Hsieh

Petri,

Hsieh is correct in that a TUI program does not run in a browser, but runs in its own JVM (per user).   This may be possible in an Application Client as I don't believe that it uses a browser but is more like a "batch" container.

That said, our TUI programs cannot utilize J2EE constructs which in this case means they cannot use datasources within WAS.  Each JVM will make its own connection.

If you don't want the individual user to connect directly to the DB, then I would think you would need to use something like DB2 connect on a server to channel the requests to the database server.  This means the clients (TUI programs) connect to the DB2 connect on the server and it then routes the request to the "host" database.

Mark

 Hi Mark and Hsieh,

Thank you for your answers!

I was afraid that I was going to dead end, thanks for comfirming it.
I'll have to check DB2 Connect option, it might be the solution to database traffic.

I think that I will still be using WAS server and Java Web Start to distribute our application to users.
If you know a better way to distribute standalone java to users please let me know.

Then I was wondering another approach:
What if I split TUI program into two programs: TUI (very thin client) and a called program that does all the work (logic, database access etc).
Is it then possible to generate them to "client/server" programs? I mean can I generate called programs into J2EE running on a WAS server and
TUI programs will use web services or EJB to call them?

Petri

That seems to me like the perfect way forward.

If you've split of your business logic and database access into services and a lightweight frontend, it could be easy to move to full web interface for the frontend (=RUI) in the future.

If we need to schedule applications with our job scheduler on as400, we create a small egl standalone application (generated into a java application), which only purpose is to access the web service where the business logic and database access is written.

I agree with Bram...using a service as the back end would enable the use of J2EE resources.    To complete the answer... a called program "can" run in an application client container, but it does not support access to J2EE if called directory (through a TCPIP listener).  So, the use of a Service in a web container to wrap the called program or to turn it into a service enables the J2EE resources.

Mark