Jade RAP and JadApp

[ConvertFromOldNGs]

by Scott Sheng >> Tue, 1 Nov 2005 8:28:10 GMT

Hi
We tried to start JadApp as singleUser then allow client to connect, it is done successfully, but we find that the server execution method will be run on client side,
is it right? any comment? I hope it can be still run on server side.


I'd appreciated if some one can explain or help me.

Thks
Scott

[ConvertFromOldNGs]

by dcooper@jade.co.nz >> Tue, 1 Nov 2005 8:38:19 GMT

If you are running a single user app server, then the app server is playing the role of (obviously) the app server (ie: the middle/business logic tier) and also the database server (ie: the database tier). In this configuration, a server execution method makes no difference because the app server and database server are basically the same thing (ie: one node is performing both roles). You say that the method is being run on the client side - do you mean the thin client? This is never the case (in any configuration, even when you have a database server) because the thin client does not execute JADE logic - that's what the app server does by default and what the database server does with server execution methods (if you're running a database server node).

Dean.

[ConvertFromOldNGs]

by Torrie >> Tue, 1 Nov 2005 21:58:14 GMT

Scott

If your logic is using files or active X from a serverExecution method then you will notice a difference when running a single user application server. Normally when running in a serverExecution method these will access items on the server (where JadeRap is running.) However when running Jade Application Server in single user mode, I presume that the file and active X object will by default access items on the presentation client unless you set the usePresentationClient property on the file or activeX object to false.

Torrie

[ConvertFromOldNGs]

by Scott Sheng >> Wed, 2 Nov 2005 8:01:52 GMT

Hi Torrie,
I tried to use "write" instruction in a serverExecution method to output some thing to Jade interpreter Output viewer, then found that the viewer will appear at presentation client when I am running JadApp as single user mode, but if you run JadApp as multiuser mode, you will see the viewer to appear at server side.

any comment?

Scott

[ConvertFromOldNGs]

by Torrie >> Wed, 2 Nov 2005 20:34:46 GMT

Yes

You can use the JadeLog class in Jade to write to a log file and specify whether the file is output to the server or to the client. I find that this is much better in live systems as you have a record of the output stored in a file and you don't have to be looking at the server to see the output. Take a look in the Jade help for the Jade Log class, there is an example in there as well.

If you do want the output appearing on the server then you could use a text view that will refresh when the file is updated. I've used TextPad for this in the past.

Torrie

[ConvertFromOldNGs]

by Jade Support >> Thu, 3 Nov 2005 1:32:32 GMT

Torrie's is correct. The implementation of Par 17762 in the 6.1 release addresses these issues to some extent.



Prior to JADE 6.1, serverExecution mode was effectively ignored for application servers running in singleUser mode. As a result, logic executed from server methods in a thin client application was treated exactly the same as non-server methods. As a result, calling those methods that are affected by the thin client running environment would always be associated with the presentation client. For example, files would be opened by default on the presentation client, date and times would return the presentation date/time, getComputerName returned the presentation client name etc.



In JADE 6.1, this has been changed such that methods executed in server methods will honour the server execution mode and by default will be associated with the application server environment. As a result, using server method's in singleUser thin client application execution should behave the same as multi-user server execution. Note that this will of course have no impact on calling clientExecution methods from server methods, they will continue to be executed in the client environment.



Jade Support