The JadeLocal transport between the JADE database and standard clients is implemented by the use of shared memory, global events, and semaphores.
The JadeLocal transport should be used when a node has one or two processes only.
The following JADE initialization file parameters are required to use the JadeLocal transport.
[JadeServer] NetworkSpecification<n>=JadeLocal,enabled|disabled,[Global\]base-name [JadeClient] ServerNodeSpecifications=JadeLocal,[Global\]base-name
The base-name value can have an optional Local\ or Global\ prefix, as described for the HPSM transport, earlier in this chapter.
If the prefix is absent, it defaults to Local\, which is consistent with running with the least‑privileges mode. When running as a standard user, the value of the base-name variable is created in the Local\ or session namespace, which means that all JADE programs must be running as the same user logon and also in the same Windows session, to be able to connect to this RPC transport. For example, if the database is installed as a service, all application servers and standard clients wanting to connect to this database via JadeLocal transport must also be running as services and under the same user logon.
Local intra-machine transport is used only when the transport type is defined as JadeLocal or HPSM on both the server and client and the network state on the server is defined as Enabled.
Alternatively, use the server argument in a command line to specify the server Universal Resource Identifier (URI) target database and the client-server transport, instead of the server and path arguments in a command line and the