Home

	Expand Search

Installation Guide Adaptive Server Enterprise for Linux/Intel

Chapter 6 Installing Sybase PC-Client Products

Configuring network connections for client products

Configuring network connections for client products

Adaptive Server communicates with other Adaptive Servers, Open Server applications (such as Backup Server), and client software on your network. Clients can talk to one or more servers, and servers can communicate with other servers by remote procedure calls.

For Sybase products to interact with one another, each product needs to know where the others reside on the network. This information is stored in an interfaces file (sql.ini on Windows NT), or in the libtcl.cfg file.

Adding a server entry to the libtcl.cfg file

You use the libtcl.cfg files to specify an LDAP (Lightweight Directory Access Protocol) server name, port number, DIT base, user name, and password to connection to an LDAP server.

The default libtcl.cfg file is located in:

%SYBASE%\%SYBASE_OCS%\ini

In its simplest form, the libtcl.cfg file is in this format:

[DIRECTORY]

ldap=libdldap.dll ldapurl

where the ldapurl is defined as:

ldap://host:port/ditbase

When an LDAP server is specified in the libtcl.cfg file, the server information is accessible only from the LDAP server. Adaptive Server ignores the interfaces file. Open Client/Open Server applications that use the -I option at start-up override the libtcl.cfg file and use the interfaces file.

To use a directory service, you must:

1. Add the location of the LDAP libraries to the path environment variable for your platform.

2. Configure the libtcl.cfg file to use directory services.

   Use any standard ASCII text editor to:

   • Remove the semicolon (;) comment markers from the beginning of the LDAP URL lines in the libtcl.cfg file under the [DIRECTORY] entry.

   • Add the LDAP URL under the [DIRECTORY] entry. See Configuring Adaptive Server Enterprise for supported LDAP URL values.

   Warning!

   The LDAP URL must be on a single line.

   ldap=libdldap.dll ldap://host:port/ditbase??scope??
        bindname=username password

   For example:

   [DIRECTORY] 

   ldap=libdldap.dll ldap://huey:11389/dc=sybase,dc=com??
        one??bindname=cn=Manager,dc=sybase,dc=com secret

3. Verify that the appropriate environment variable points to the required third-party libraries. The Netscape LDAP SDK libraries are located in %SYBASE%\%SYBASE_OCS\lib3p. The Windows PATH environment variable must point to this directory.

4. Once you have edited the libtcl.cfg file, use dsedit to add a server to the directory service:

   1. From the Windows task bar, select Start | Programs | Sybase | dsedit.

   2. Select LDAP from the list of servers, and click OK.

   3. Click Add New Server Entry.

   4. Enter:

      • The server name - this is required.

      • Security mechanism - optional. A list of security mechanism OIDs are located in %SYBASE%\%SYBASE_OCS%\ini\objectid.dat.

      • HA server name - optional. This is the name of the high-availability failover server, if you have one.

   5. Click Add New Network Transport.

      • Select the transport type from the drop-down list.

      • Enter the host name.

      • Enter the port number.

   6. Click OK two times to exit the dsedit utility.

For more information, Configuring Adaptive Server Enterprise for your platform.

Adding a server to the sql.ini file

During installation, the srvbuild process adds entries to the interfaces file for your new Adaptive Server, Backup Server, Monitor Server, and XP Server.

To access a Sybase server through the interfaces file, each server must be included in the interfaces file on the client computer.

To add a server entry to the sql.ini file on your PC-client computer:

1. Using the Microsoft Windows task bar, click Start | Programs | Sybase | dsedit.

2. Click OK on the first screen to open the InterfacesDriver screen.

3. Select ServerObject from the menu, and click Add.

4. In the Input Server Name box, enter the name of the server for which you are creating an entry.

   Click OK.

5. In the Attributes column, double-click on the server address row you just added.

6. In the ProtocolNetwork Address, click Add.

7. From the drop-down list in the Protocol box, select TCP, NAMEPIPE, SPX, or VINESIP.

8. In the Network Address box, you can enter either the server name or the IP address, along with the server port number. For example:

   machine_name, 4100

   or,

   machine_name 4100

   where machine_name is the name of the computer, and 4100 is the port number the server is using to "listen" for clients.

   The Windows platform now accepts TCP-style connection information.

   [SERVER]
   MASTER=NLWNSCK,heuy,2222 
   QUERY=NLWNSCK,heuy,2222

   or, the preferred format:

   [SERVER] 
   MASTER=TCP heuy 2222 
   QUERY=TCP heuy 2222

   or

   [SERVER] 
   MASTER=TCP,heuy,2222 
   QUERY=TCP,heuy,2222

   The preferred format is to use TCP and a space between the host_name and port_number, because it is supported across all platforms. You can edit the sql.ini with any standard ASCII text editor.

9. To find the IP address for a machine, use ypmatch. For example:

   ypmatch 'hostname' hosts

   where hostname is the name of the machine.

   To find a server's listener server port number:

   • If the server is on another PC, check the %SYBASE%\ini\sql.ini file

   • If the server is on a UNIX machine, check the interfaces file in $SYBASE

   To connect to a UNIX server, the entries you add to sql.ini must match the entries in the interfaces file on the UNIX system.

For instructions on using dsedit or dscp to modify interfaces file entries or to create new interfaces file entries for existing servers, see the Utility Guide.

For additional information on using dsedit on the client computer, see the Open Client/Server Configuration Guide for Desktop Platforms and the Open Client/Server Supplement.

For specific information about entries for connections to Monitor Server and Historical Server, see:

• Adaptive Server Enterprise Monitor Server User's Guide

• Adaptive Server Enterprise Monitor Historical Server User's Guide

Enabling TCP connections

To connect through TCP instead of Named Pipes and Winsock network protocols, you must enable the TCP connections.

To enable TCP connections:

1. From the Windows task bar, click Start | Programs | Sybase | OC OS Config.

2. Click the NetLibrary tab.

3. Select Windows NT or 98 as the platform and TCP as the protocol.

4. Click OK.

This process maps NLWNSCK to TCP in your Sybase network configuration file (libtcl.cfg).

You have completed installing Adaptive Server client plug-ins. To find out more information about setting up network communications, or to add optional functionality to Adaptive Server, see Configuring Adaptive Server Enterprise.

After you have installed the Sybase products on your system, see their accompanying documentation for configuration and administration issues.

Testing the Sybase Central installation

After you install Adaptive Server, Sybase Central, and the Java Runtime Environment, it is a good idea to test the installation and network connections.

To test installation and network connections:

1. Select Start | Programs | Sybase Central Java Edition from the Windows task bar to start Sybase Central.

2. Select Tools | Connect from the Sybase Central menu bar to activate a Sybase Adaptive Server login screen.

3. Log in using the default user ID, "sa", without a password. If you changed the password for Adaptive Server according to the post-installation instructions, you need to use the new password.

4. From the drop-down menu, select the Adaptive Server that you want to connect to.

   If Sybase Central is installed on the same computer as the server, click the icon for the server.

   If prompted to start Adaptive Server, click OK. When the traffic light icon representing the server is green, the server is running.

   Warning!

   Do not start XP Server from Sybase Central. Adaptive Server starts XP Server automatically when Adaptive Server receives the first request for an extended stored procedure.

5. To disconnect from a server, choose Disconnect from the Tools menu.

   If a server is running on the same computer as Sybase Central, disconnecting does not stop it.

6. Exit Sybase Central.

If Adaptive Server fails any of these tests, see Chapter 9, "Troubleshooting" Before retrying the installation, follow the instructions in Chapter 5, "Post-Installation Tasks."