Forums

by Mike >> Fri, 13 Feb 2004 17:19:51 GMT

Because I'm using a Jetted application, I have to start a number of server apps using ServerApplicationN=<schema>,<app> in the [JadeServer] section of my .ini file. These apps are fat client and thus jade.exe needs to read a ...ini file in order to get the relevant comms settings from NetworkSpecifications to talk to the RNA. Jade's not opening my lovingly crafted .ini file because it's called:

"E:\JadeControl\system\Jade CONTROL.ini"

Instead, it's opening:

"E:\JadeControl\bin\JadeCONTROL.ini"

(yes, there's no space - I found this out from the JOM log.) Having copied the former to the latter, it worked sweet as a nut.

Now, I don't want to maintain two .ini files for the same DB, so how can I make the fat client server apps use the former instead of the latter? And just how did it decide on the particular name for the .ini file it was reading, anyway? Does it simply assume that it's named after the install folder?

by Dr J. >> Sun, 15 Feb 2004 21:50:59 GMT

Given that the ServerApplicationN=<schema>,<app> in the [JadeServer] section of your .ini file can't directly launch jade.exe applications, I presume this means that the applications started by way of the ServerApplicationN= parameters are in turn doing their own createExternalProcess, or similar, to launch the jade.exe apps?

If so, perhaps the specification to createExternalProcess has the ini file defined without the missing space character?

by cnwjhp1 >> Mon, 16 Feb 2004 1:53:01 GMT

You guessed it - Jetted systems are normally run under the JADECare Toolset, so the fat client initialise method defaults to JADECare's convention of assuming the .ini file is named after the environment id (aka the install folder).

Cheers,
John P

by Mike >> Mon, 16 Feb 2004 10:37:31 GMT

Oookay - having studiously read the IAG last summer I originally settled on putting my .ini files in the /system folders. As we're still in the early deployment phases for Jade and out Jetted apps, I don't mind renaming and moving the .ini files and updating all my shortcuts - provided I'm not storing up trouble for later. Am I?