HTML ThinClient setup on Linux with Apache

[ConvertFromOldNGs]

by Rich >> Sat, 15 Nov 2003 6:13:32 GMT

Hi folks,

I'm having some difficulty getting Jade to serve an application through the Apache module. My setup is SuSE with Jade Dev Release 6.17.011 (the IDE itself runs fine). Where I'm at is I've created a 1-screen app to play with, and this works just fine on as a regular GUI Thin Client, but doesn't want to work as WebEnabled. I've installed the module into Apache and can view jade-info, and get a reasonable error screen when it's trying to connect to wrong port on the app-server. However, when mod_jadehttp is told to connect to the port that Jade app server is listening on, all I can seem to achieve are 500 Server Errors in my browser.

I'm sure I'm missing something obvious here, as there are only about 4 files that need to be played with. Most of the doco seems to reference IIS, so does anyone have a minimal (but complete) example that "just works" with Apache on a Linux server?

Thanks,
Rich.

[ConvertFromOldNGs]

by Patwos >> Mon, 17 Nov 2003 9:18:33 GMT

Rich,

I'm not familiar with the Linux version of Jade, but in the Windows world you connect your web browser via IIS to a web enabled application running via jade.exe not to an AppServer. I would imagine that a similar approach would need to be taken on a Linux server with your web browser connecting via Apache to a Non_GUI_Web application running via jadclient. Perhaps someone more familiar with the Linux version of Jade could confirm this.

Hope that helps,
Pat.

[ConvertFromOldNGs]

by Rich >> Tue, 18 Nov 2003 22:24:03 GMT

Thanks for that Pat. Back to a RedHat system, running 6.016.11... (if it makes a difference)

If I tell mod_jadehttp to use 127.0.0.1:6017 (for example) and set my WebTest app to listen on 127.0.0.1:6017, things should be working when I launch the app from the shell.

But, when running the app from the jade command line, I get the following errors:
WebTest.log says
SystemException: 1090 (not continuable, resumable)
* Attempted access via null object reference
Caused By:
Method: RootSchemaApp::_webInitialize(2551) -- source position: 2551

And jommsg2.log says
2003/11/19 11:17:17 04e86-40bc0b30 TcpIp: TcpConnection::postedResponse: connection was closed from 127.0.0.1
2003/11/19 11:17:17 0652e-40ab2b30 server: (jadclient) Version 6.0.16 - ANSI, OS Version: Linux 2.4.20-20.9
2003/11/19 11:17:17 0652e-40ab2b30 server: Invocation: jadclient ini=/home/jade/jade.ini path=/home/jade/system app=WebTest schema=WebTest path=/home/jade/system
2003/11/19 11:17:17 0652e-40ab2b30 SvcMgr: Service initialize logic returned 1001
2003/11/19 11:17:18 0652e-406d0860 server: (jadclient) Finished: exit code 1001 remapped to 105

I'm a bit confused about what else I need to set up. It looks like something somewhere is confused about directories, or the app needs something more than a simple startup form?

FWIW, I tried the demo system, and had no joy there either - although I did end up with lots of Windows style paths being written to my Linux system.

Any help would be appreciated...

[ConvertFromOldNGs]

by Rich >> Wed, 19 Nov 2003 6:29:57 GMT

Well, back on to SuSE with 6.017.11, and I no longer get the mis-matched client/app-server error that finally ended the RedHat 6.016 efforts.

Anyway, what I've got is an 1239 exception and a note about msgBox(553) in the log , when I connect via mod_jadhttp to a WebTest application running on the Linux box under jadclient.sh.

I just want to make sure I'm doing this right...
Jade is on 50001, Jade-app is on 50002, Apache is on port 80 while mod_jadhttp is set to use 6071. WebTest app has its connection configured as 127.0.0.1:6071, so that means it's listening on 6071 for connections from mod_jadhttp. Seems simple enough...

If that's all it needs, then why does my empty Main webform not work? Instead I get nested exceptions and message box errors in the log... which presumably shouldn't be there because it's a server app anyway, and I've not written any code in the form to generate them (doco says they should be ignored ignored anyway, so this must be system generated?). Also, it runs fine as a regular GUI thin client app.

[ConvertFromOldNGs]

by Jade Plant >> Thu, 20 Nov 2003 21:09:17 GMT

Rich,

HTML thin clients that use the HTML dynamic generation feature cannot be run on a non-Windows environment because this implementation still requires the use of Windows GUI. If you wish to run HTML thni clients in a non-Windows environment you will need to use the HTML thin clients that use HTML documents.

[ConvertFromOldNGs]

by Rich >> Fri, 21 Nov 2003 0:22:48 GMT

Thanks for the info.