Configuring Your Network Protocol

TCP/IP is required for multiuser configurations. TCP/IP must be installed on each workstation that is to participate as a node in the JADE environment. Your network manufacturer supplies TCP/IP and your network administrator supplies the TCP/IP address.

JADE also provides fast transport mechanisms for JADE modules on the same machine (for example, one that has multiple CPUs). For details, see "Hybrid Pipe Shared Memory (HPSM) Transport" and "JadeLocal Transport", later in this chapter.

Use the:

• NetworkSpecification parameter in the [JadeServer] section of the JADE initialization file to specify the transport types used by a JADE server.

• ServerNodeSpecifications parameter in the [JadeClient] section of the JADE initialization file to specify the transport type used by a JADE client to connect to the server.

• Server URI string in the server argument of a command line, to specify the target database and the client-server transport. For details, see "Format of the Server URI String", later in this chapter.

As JADE database servers and JADE application servers can often reside on the same machine, you can use a local intra-machine transport to significantly improve performance. You can also use these transport mechanisms to communicate from standard (fat) clients and JADE application servers to JADE servers if these processes run on the same physical machine, to significantly improve overall performance. Intra-machine local transport uses shared memory.

To detect whether a connection has been lost, a polling mechanism ensures that some minor communication is taking place regularly. See also "TransportIdlePollInterval" under "JADE Object Manager Server Section [JadeServer]", in the JADE Initialization File Reference.

If your database is running as a service but not with the Local System account, your Windows administrator must configure the user logon to add the following Windows privilege Create global objects (SeCreateGlobalPrivilege at the programming API level), which can be done directly to the user logon or to a group of which that user is a member. On a machine that is not part of a Windows domain, this can be done by accessing the Local Security Policy in the Administrative tools directory and adding the Create global objects policy under Local Policies / User Rights Assignment to the desired group or user. This allows JADE programs that need to connect via the JadeLocal or HPSM intra-machine transport to work across multiple Windows sessions or user logons.

With the HPSM transport, a database running with a standard account requires the extra privilege. Client nodes do not require the extra privilege.

With the JadeLocal and HPSM transports, if a standard user attempts to create a Global\basename value in either of these initialization file parameters, it fails because of insufficient privileges.