setup JADE Application server

[ConvertFromOldNGs]

by tom >> Tue, 6 Jan 2004 17:00:38 GMT

I am new to JADE. I'm trying to install Jade Application server but it didn't work.I followed the intruction from Jade's documents and get error -104 Failed to establish network connection Database Open failed. Can anyone check for me?
This is my shortcut for Jade app server
C:\Jade60\bin\jadapp.exe appServerPort=7000 path=C:\Jade60\system server=multiuser host=LocalHost port=6015 localport=6099

- Does Jadapp and presentation client have to be run simultaneously?
- Does Jadapp and Jade .exe point to the same Jade ini file or do I have to seperate for each application?
This is my jade ini file:
[Jade]
Server=MultiUser
ShowUserInterrupt=true
UseSystemTrayIcon=true
OpeningForm=true
BitmapFile=<default>
AviFile=<default>
AviPos=<default>
StatusPos=<default>
StatusFontColor=<default>
ApplicationPos=<default>
ApplicationFontColors=<default>
SchemaPos=<default>
SchemaFontColors=<default>
ServerPos=<default>
ServerFontColors=<default>
PathPos=<default>
PathFontColors=<default>
VersionPos=<default>
VersionFontColors=<default>

[JadeClient]
ServerNodeSpecifications=TcpIp,LocalHost,7000
ThreadPriority=Normal
Language=eng
ObjectCacheSizeLimit=5000000
TransientCacheSizeLimit=5000000
InitializationHandlerLibrary=jomsupp
SamplingNode=false
ReadOnlySchema=false
ReadOnlySystemSchema=false
MaxWaitAppStart=0
NotifyQueueDepthWarningThreshold=10000
TransientDbPath=c:\jade60\system


[JadeServer]
NodeName=LocalHost
NetworkSpecification1=TcpIp,Enabled,6005
DoubleDeadlockException=false
RunAsService=true
DisableUserSignOn=false
ServerTimeout=10000
UseSystemTrayIcon=true
Window=160,160,380,250
ServerImageFile=JadeLogo.bmp
ThreadPriority=Normal
MgmtThreadIdleTimeout=300000 MgmtThreadNetwork=TcpIp,Disabled,61923,127.0.0.1
MinServerThreads=20
MaxServerThreads=100
ServerThreadIdleTimeout=300000
MaxNotifyThreads=5
ObjectCacheSizeLimit=5000000
TransientCacheSizeLimit=5000000
RemoteTransientCacheSizeLimit=5000000
ReadOnlySchema=false
ReadOnlySystemSchema=false
SamplingNode=false
AutomaticCacheCoherency=false
TransientDbPath=c:\jade60\system

[JadeEditor]
ForceMultiByteLocale=false
[PersistentDb]
ObjectCacheSizeLimit=4M
PercentOverlayGoal=5
ObjectTrace=false
SpaceReuseOption=true
PrintStatistics=false
SuppressDialogs=false
DefInitialFileSize=16K
DefFileGrowthIncrement=64K
IndexCompressionRatio=95
BackupStats=false
BackupBuffers=4
BackupBlockSize=64K
BackupThreadPriority=Normal
BackupCompressionLevel=Normal
JournalMaxSize=64M
EnableArchivalRecovery=false
JournalRootDirectory=<default>
JournalArchiveDirectory=<default>
JournalCloseAction=None
VerifyTransactionLog=false
JournalMinSize=0
JournalSwitchInterval=0
ReorgWorkDirectory=<default>
RecoveryTimeTarget=300
MaxWaitForQuietPoint=0
SystemFileDirectory=<default>
ActivityLogDirectory=<default>
StateOverflowDirectory=<default>
OpenAllFilesOnDbOpen=false
[TransientDb]
IndexCacheSizeLimit=128K
ObjectTrace=false
SpaceReuseOption=true
PrintStatistics=false
SuppressDialogs=false
DefInitialFileSize=16K
DefFileGrowthIncrement=64K
[JadeInterpreter]
MethodCache=Multiple
MethodCacheLimit=512K
[JadeSecurity]
DevelopmentSecurityLibrary=<none>
[JadeSound]
ConnectSoundFile=C:\Jade60\bin/jadnet1.wav FailedConnectSoundFile=C:\Jade60\bin/jadnet2.wav ConnectionAbortedSoundFile=C:\Jade60\bin/jadnet3.wav DisconnectSoundFile=C:\Jade60\bin/jadnet4.wav FailedRpcRequestSoundFile=C:\Jade60\bin/jadnet5.wav EnableSoundSupport=true
[JadeCompiler]
SuppressWarningDialogs=false
[JadeStatistics]
ServerStatisticsTimerValue=60
ServerStatisticsFileName=ServerStatistics
ServerStatisticsToFile=false
[SyncDbService]
AuditCauseEvents=false

[JadeAppServer]

KeepAliveTime=10
ConnectionTimeout=0
EnableAppRestrictions=false
AllowSchemaAndApp1=<schema, application>
WindowPos=72,20,500,100
NodeName=jadapp-7000
NodeNameDescription=Jade AppServer 7000 (C:\Jade60\system) AutomaticDownLoad=true
CacheEntryTimeout=30
RPCEncryptionEnabled=false
RPCEncryptionHookDLL=Internal
DownLoadVersion=
DownLoadDescription=
DownLoadDirectory=
DownLoadDirectory2=
PreDownLoadVersion=
PreDownLoadDescription=
PreDownLoadDirectory=
PreDownLoadDirectory2=
PostInstallExe=
DownLoadMaximum=0
RunAsService=false

[ConvertFromOldNGs]

by dr >> Tue, 6 Jan 2004 21:39:07 GMT

Tom,

Your command line specifies server=multiUser, so you must have a database server process (jadrap.exe) running - your ini file specifies this runs as a service. In the [JadeServer] section, NetworkSpecification1 specifies the port number as 6005, but the command line asks the jadapp to connect on port 6015 - change one of these so they are the same.

With regards to ini files, each process (jadrap.exe, jadapp.exe, jade.exe) can run against their own ini files, or they may use a common ini file. It's easier to manage a single ini file, but the facility is there to specify individual (and conflicting) settings in separate ini files if your installation requires it. In a distributed installation, it may be that the processes do not have network (file) access to a common ini file, in which case they would have to have their own individual files ... this is common for thin clients that may be separated from the database and/or appServer by a firewall.

Hope this helps ... Rob

[ConvertFromOldNGs]

by Patwos >> Tue, 6 Jan 2004 22:10:08 GMT

Typical, in the time I was typing my long response and rereading it, someone else also answered the same posting.

Note that as of 6.0 you can also do more work in a single ini file using the new name= option on the command line to create sections such as:

[AppServer1.JadeAppServer]
AppServerPort=40000

[AppServer2.JadeAppServer]
AppServerPort=40001

In this way, you can keep your command lines simple, still share a single ini file but run two AppServers on different ports etc. Makes it much easier when you have a larger system with multiple AppServers and means you can change more things via the ini file without needing to get access to the shortcut command line - particularly useful if you've configured these as services.

Hope that helps,
Pat.

[ConvertFromOldNGs]

by Patwos >> Tue, 6 Jan 2004 21:54:21 GMT

With server=multiUser on your shortcut, you're indicating that this AppServer is going to connect to a DbServer (either jadrap or jadsrv). The -104 exception indicates that you either do not have jadrap or jadsrv running or that the host name is incorrectly specified or that the jadrap/jadsrv are listening on a different port number. Given that your host is local host, and that you do have some conflicts with respect to the tcp port numbers you have utilised your current setup will get the -104 even if you have the DbServer running.

From your shortcut:
* appServerPort=7000 - this is the port that your thin clients will eventually connect to. There is a potential conflict with your serverNodeSpecification

* host=LocalHost - no problems there

* port=6015 - overrides the ini file definition below

* localport=6099 - not entirely necessary. You can just let windows pick your next available local port number.


From your ini file:
[JadeClient]
ServerNodeSpecifications=TcpIp,LocalHost,7000 - if not overridden by the command line port= parameter, this would not succeed in connecting to your jadrap/jarsrv as the port number does not match your network specifications in the JadeServer section below.

[JadeServer]
NetworkSpecification1=TcpIp,Enabled,6005 - no problems here except that this port number does not match that specified on the ServerNodeSpecifications in the JadeClient section above, nor does it match the value you have specified using port=6015 on your command line.

To summarise, your port= parameter on the shortcut does not match up with your NetworkSpecification1 and neither does the port number in your ServerNodeSpecifications in your JadeClient section. Unless you have a good reason to "override" the host/port details on your command line, I would suggest making the following adjustments:

Change your shortcut details to the following. Note that I have removed the "unnecessary" command line overrides and deliberately added the ini file specification:

C:\Jade60\bin\jadapp.exe appServerPort=7000 path=C:\Jade60\system server=multiuser ini=c:\Jade60\system\jade.ini

Change your ini details as follows:

[JadeClient]
ServerNodeSpecifications=TcpIp,LocalHost,6005

[JadeServer]
NetworkSpecification1=TcpIp,Enabled,6005

Note that I changed the JadeClient section so that the port number matched the JadeServer sections port number. You could have changed either so long as you ensure that they match, are utilising a port that no other software on your server already utilises and is different to the port number that you use for your AppServerPort specification.


This of course all assumes you actually want to connect to a DbServer in multiUser mode. If you only want to run an AppServer without running the DbServer, then change server=multiUser to server=singleUser on your shortcut.

Hope that helps,
Pat.

[ConvertFromOldNGs]

by Tom >> Wed, 7 Jan 2004 7:14:16 GMT

Thanks a lot Pat, It works after I change follow your instruction. I first run Jadrap and then Jadapp and I heard the sound "Connection Established" and finally I run Jade presentation client. It works fine.
But these processes were done in one machine,when I tried to run Jade thin client from another machine in same network. I got error 14140 Thin Client Tcp connection failed .I could be the error at Appserv=xxxxxx.

This is my shortcut commandline for Thin client:
C:\Jade60\bin\jade.exe appServer=10.0.0.7 appServerPort=7000 app=SayHello schema=SayHello ini=C:\Jade60\bin\jade.ini

note:10.0.0.7 ip of the machine that runs Jadrap and Jadapp
Is it possible to run Thin client in same network? Thanks
regards,

TOM

[ConvertFromOldNGs]

by allistar >> Wed, 7 Jan 2004 8:50:29 GMT

A few things to check:
- that the app servrr is in fact running on 10.0.0.7:7000
- that the client machine can "see" 10.0.0.7 (try to ping it - should work if ping packets aren't dropped).
- is there a firewall preventing access to port 7000 on 10.0.0.7?

Regards,
Allistar.

------------------------------------------------------------------
Allistar Melville
Software Developer, Analyst allistar@silvermoon.co.nz
Auckland, NEW ZEALAND

Silvermoon Software
Specialising in JADE development and consulting
Visit us at: http://www.silvermoon.co.nz
*NEW* Simple web access to Jade at: www.silvermoon.co.nz/jhp.html ------------------------------------------------------------------