• No results found

communication options

Server communication libraries

Windows 95 communication options

Using the sqlwntm.dll or sqlwntw.dll SQLAPI library, a Graphical User Interface (GUI) or character-based Windows 95 client can connect to one or more local or remote database servers.

Similarly, a SQLBase for Windows 95 server can support multiple client connections. The General Communications Interface (GCI) library, sqlngci.dll, provides the communications interface between the client-side

SQL/API library (sqlwntm.dll or sqlwntw.dll) and the lower-level communication libraries (sqlntnbi.dll and sqlapipe.dll). It also interfaces between the SQLBase Server for Windows 95 and these same libraries.

Centura also offers a single-user Windows 95 database server, which supports the same communications protocols as the multi-user server.

Multi-user database servers

The load instructions below assume that SQLBase is installed on the c:\ drive. If your installation drive is different from c:\, substitute the appropriate letter drive.

dbntsrv.exe

This is an unlimited-user SQLBase for Windows 95 database server. To load the

dbntsrv.exe into memory, select one of these options:

Click the dbntsrv.exe icon (if one is installed on the desktop), orSelect Start, Run..., then type:

c:\centura\dbntsrv

dbnt1sv.exe

This is a 1-user SQLBase for Windows 95 database server. To load the dbnt1sv.exe into memory, select one of these options:

Click the dbnt1sv.exe icon (if one is installed on the desktop), orSelect Start, Run..., then type:

Windows 95 communication options

dbnt5sv.exe

This is a 5-user SQLBase for Windows 95 database server. To load the dbnt5sv.exe into memory, select one of these options:

Click the dbnt5sv.exe icon (if one is installed on the desktop), orSelect Start, Run..., then type:

c:\centura\dbnt5sv

dbnt10sv.exe

This is a 10-user SQLBase for Windows 95 database server. To load the dbnt10sv.exe into memory, select one of these options:

Click the dbnt10sv.exe icon (if one is installed on the desktop), orSelect Start, Run..., then type:

c:\centura\dbnt10sv

dbnt25sv.exe

This is a 25-user SQLBase for Windows 95 database server. To load the dbnt25sv.exe into memory, select one of these options:

Click the dbnt25sv.exe icon (if one is installed on the desktop), orSelect Start, Run..., then type:

c:\centura\dbnt25sv

dbnt50sv.exe

This is a 50-user SQLBase for Windows 95 database server. To load the dbnt50sv.exe into memory, select one of these options:

Click the dbnt50sv.exe icon (if one is installed on the desktop), orSelect Start, Run..., then type:

c:\centura\dbnt50sv

Server communication libraries

In addition to the database server executables listed in the previous section, SQLBase requires that protocol-specific server communication libraries be installed on the database server computer as well.

SQLBase Server for Windows 95 supports NetBIOS, Anonymous Pipes, and TCP/IP, allowing the server to connect to Netware, Windows NT, and Windows 95 clients.

sqlntnbi.dll

This communication library supports the NetBIOS protocol on a Windows 95 server. When you specify:

comdll=sqlntnbi

in the [dbntsrv.dll] section of a server’s configuration file (sql.ini) and start a server (for example, dbntsrv.exe), sqlntnbi.dll is loaded into memory.

These keywords are specific to Windows 95 NetBIOS communications and can be configured in the [dbntsrv.ntnbi] section of the server’s configuration file (sql.ini):

Read Chapter 3, Configuration (sql.ini) for a complete description of these keywords.

sqlapipe.dll

This communication library supports the Anonymous Pipes protocol on a Windows 95 server. When you specify:

comdll=sqlapipe

in the [dbntsrv.dll] section of a server’s configuration file (sql.ini) and start a server (for example, dbntsrv.exe), sqlapipe.dll is loaded into memory.

There are no keywords specific to Anonymous Pipes on the Windows 95 platform.

sqlws32.dll

This communication library supports the TCP/IP protocol on a Windows 95 server. When you specify:

comdll=sqlws32

in the [dbntsrv.dll] section of a server’s configuration file (sql.ini) and start a server (for example, dbntsrv.exe), sqlws32.dll is loaded into memory.

The listenport keyword is specific to Windows 95 NetBIOS communications and can be configured in the [dbntsrv.ntnbi] section of the server’s configuration file (sql.ini): Read Chapter 3, Configuration (sql.ini) for a complete description of this keyword.

adapter commands

Windows 95 communication options

Client communication libraries

SQLBase Windows 95 client software supports SPX, NetBIOS, Anonymous Pipes, and TCP/IP.

• With SPX, clients can access SQLBase for NetWare database servers. • With NetBIOS, clients can access SQLBase for Windows NT and Windows

95 database servers.

• With Anonymous Pipes, clients can access SQLBase for Windows 95 database servers.

• With TCP/IP, clients can access SQLBase for NetWare, Windows NT, and Windows 95 database servers.

sqlntnbi.dll

This communication library supports the NetBIOS protocol on a Windows 95 client. When you specify:

comdll=sqlntnbi

in the [win32client.dll] section of a client’s configuration file (sql.ini) and access a remote database via a Windows 95 application (for example, dbntsrv.exe), sqlntnbi.dll is loaded into memory.

These keywords are specific to Windows 95 NetBIOS communications and can be configured in the [win32client.ntnbi] section of the client’s configuration file (sql.ini):

Read Chapter 3, Configuration (sql.ini) for complete descriptions of these keywords.

sqlapipe.dll

This communication library supports the Anonymous Pipes protocol on a Windows 95 client. When you specify:

comdll=sqlapipe

in the [win32client.dll] section of a client’s configuration file (sql.ini) and access a remote database via a Windows NT application (for example, dbntsrv.exe),

sqlapipe.dll is loaded into memory.

There are no keywords specific to Windows 95 Anonymous Pipes communications.

sqlws32.dll

This communication library supports the TCP/IP protocol (using Windows Sockets) on a Windows 95 client. When you specify:

in the [win32client.dll] section of a client’s configuration file (sql.ini) and access a remote database via a Windows NT application, sqlws32.dll is loaded into memory. The serverpath, searchcontext, and preferrednameservice keywords are specific to TCP/IP communication and can be configured in the [win32client.ws32] section of the client’s configuration file (sql.ini):

Read Chapter 3, Configuration (sql.ini) for a complete description of this keyword.

sqlwsspx.dll

This communication library supports the SPX 32-bit Microsoft Netware protocol on a Windows 95 client. When you specify:

comdll=sqlwsspx

in the [win32client.dll] section of a client’s configuration file (sql.ini) and access a remote database via a Windows NT application (for example, dbntsrv.exe),

sqlwsspx.dll is loaded into memory.

The searchcontext and preferrednameservice keywords are specific to SPX communication and can be configured in the [win32client.ws32] section of the client’s configuration file (sql.ini):

Read Chapter 3, Configuration (sql.ini) for a complete description of this keyword.

Note: 32-bit SPX support for Windows 95 requires that Novell’s Client32 for Netware be

installed on the Windows 95 client (Currently, Novell’s Client32 for Netware operates on Windows 95 only, and not Windows NT).

sqlws32.dll

This communication library supports the SPX 32-bit Novell Netware protocol on a Windows 95 client. When you specify:

comdll=sqlws32

in the [win32client.dll] section of a client’s configuration file (sql.ini) and access a remote database via a Windows NT application (for example, dbntsrv.exe),

sqlws32.dll is loaded into memory.

The searchcontext and preferrednameservice keywords are specific to SPX communication and can be configured in the [win32client.ws32] section of the client’s configuration file (sql.ini):

Chapter 3

Configuration (sql.ini)

This chapter describes the structure and organization of Centura’s configuration file (sql.ini) as well as the software configuration keywords for which you can specify values.

As a DBA, you need to be knowledgeable about configuration in order to tune the performance of SQLBase.

Related documents