Handling Multiple Copies of the JADE Program

Use the newcopy command line argument to force a new copy of the jade.exe JADE program to exist; for example, for testing in a multiuser environment. When this argument is set to true (the default) and the JADE icon is clicked to launch JADE, a new copy of JADE is launched if the database is already open.

Specify a value of false to indicate that when the JADE icon is clicked and JADE is running, another application is started but another copy of the JADE program is not started; that is, execution is transferred to the copy of JADE that is currently running.

When initiating a thin client-based jade.exe executable with the newcopy command line argument set to false, execution is transferred to an existing jade.exe copy if that copy is running in thin client mode and it is connected to the same application server (the TCP address and TCP/IP port number must match), so that only one copy of jade.exe runs multiple applications connected to the same application server.

If no other matching copy of jade.exe is running, execution continues as normal.

If you create a shortcut that has the newcopy argument set to false and you specify a different JADE initialization file from the one with which the node was started, the active JADE initialization file is the one that was specified when the node started up and not the one specified in the newcopy=false shortcut. (You can call the Application class getIniFileName method in the new application to get the name of the initialization file that was used when the node started up.)