Running a Jade Application

You can run Jade applications in the following ways.

Single user mode via the Jade executable (jade.exe), as shown in the following command line example.
```
c:\jade\bin\jade.exe path=c:\jade\system server=singleUser app=Accounts ini=c:\jade\system\jade.ini schema=AccountsSchema
```
For details, see "Single User Configuration" under "Jade Configurations", in Chapter 1 of the Installation and Configuration Guide.
Multiuser mode via the Jade executable (jade.exe). The following is an example of the command line required to run an Accounts application in the default multiuser mode.
```
c:\jade.exe path=s:\jade\system schema=AccountsApp app=Accounts ini=c:\jade\system\jade.ini
```
For details, see "Multiuser Configuration" under "Jade Configurations", in Chapter 1 of the Installation and Configuration Guide.
Thin client mode, via the Jade executable (jade.exe), as shown in the following command line example.
```
jade.exe app=Accounts ini=c:\jade\system\jade.ini schema=AccountsSchema appServer=MyAppServer appServerPort=1234
```
For details, see "Invoking a Jade Presentation Client", in Chapter 2 of the Thin Client Guide.
From the Jade Platform development environment. For details, see "Running an Application from the Jade Platform Development Environment".
A non-GUI client application using the jadclient executable. For details, see "Running a Non-GUI Client using jadclient".
A non-GUI server application using the ServerApplication parameter in the [JadeServer], [JadeAppServer], or [NonGuiClient] section of the Jade initialization file. (For details, see the Jade Initialization File Reference.)
From Jade code in an application, by using the Application class startApplication, startApplicationWithParameter, startAppMethodWithString, or startAppMethod method. (For details, see Chapter 1 of the Encyclopaedia of Classes.)

The shutdown behavior of an application server and database server differs in that when either of these nodes is shut down, all applications running on that node are closed.

If one application is terminated (when all forms of that application are closed), the database remains open, as each application uses the same open instance of that database; that is, if another application is started by an application that is already running, the node is not closed until both applications are terminated (jade.exe continues to run until all applications are terminated). For example, if jade.exe is used to initiate the Jade Platform development environment in single user or multiuser mode and another application is run from within Jade (for example, AppEg1), closing the Jade application does not close the database if the other application is still running. If the other application (AppEg1) starts another application (for example, AppEg2), both AppEg1 and AppEg2 must be shut down for the database to be closed.

A user application developed using an Enterprise or Free restricted licence that is invoked from outside of the Jade Platform development environment displays a splash screen stating that it is a test environment. (A test environment is not for production use.) The only action that the user can perform is to click anywhere on the splash screen or to press any key to remove the splash screen.

The type of licence is displayed at the bottom of the Jade Platform development environment sign-on screen (that is, an unrestricted primary (Production) licence or an Enterprise or Free restricted licence).

Operating system command line arguments are delimited by white space, which is either a space or a tab. A command line argument is the information that follows the program's name on the command line of the operating system. Command line arguments are used to pass information to the program. A command is split into an array of strings named arguments. Argument 0 is (normally) the command name, argument 1, the first element following the command, and so on.