Home

	Expand Search

DirectConnect for Oracle Installation/Reference for Windows NT

Chapter 2: Installation

Chapter 2

This chapter provides instructions for installing DirectConnect for Oracle for Windows NT.

Notes About New Installation

1. Read the instructions in this chapter before you begin your installation.

2. Perform the preparation tasks in this chapter.

3. Load the Sybase files from media, as explained in this chapter.

4. Follow the instructions in this chapter to configure DirectConnect for Oracle.

Pre-Installation Checklist

Before beginning your installation, complete the tasks in the following checklist:

• Read the DirectConnect for Oracle Release Bulletin for essential
  information.
• Verify that your system meets the minimum software and
  hardware requirements (see Chapter 1).

Installation Instructions

The distribution disks come with a utility called setup. This utility creates the appropriate directories on your hard disk, decompresses the files on disk, and copies them to your system.

Follow the instructions below to install DirectConnect for Oracle:

1. Insert the Installation disk into the appropriate disk drive. Start the installation program by selecting the setup.exe file in the File Manager Window or executing setup at a command prompt.

2. When prompted, enter an installation directory or accept the default by clicking NEXT.

   WARNING! Sybase recommends installing DirectConnect for Oracle in a separate directory from other products.

   setup copies the software to the specified directory on your hard disk, prompts you to insert new disks as required, and notifies you when the installation is successful.

3. Users have the option to display a readme file. Click YES to read the file or NO to exit the installation program.

Configuring DirectConnect for Oracle

After completing setup, configure DirectConnect for Oracle by performing the following steps:

• Create or modify the sql.ini file.
• Modify the libtcl.cfg file.
• Set the SYBASE environment variable.
• Set environment variables for DirectConnect.
• Set environment variables for Oracle.

Create or Modify the sql.ini File Entry

The sql.ini configuration file contains network connection information for the servers to which you wish to connect. This file is read by client applications to determine how to connect to a specified server, and by server applications to determine which address to listen for connection requests from clients. After installation, a sql.ini file must be created or an existing sql.ini file modified using sqledit (see Appendix A, "Using sqledit").

You may use one of two methods if you wish the server entries located in the sql.ini file to be accessed by more than one client or server application:

1. Copy the sql.ini file to other machines with applications that must access its server entries, or

2. Place the sql.ini file in a common location (for example, on a file server) accessible on the network. (Note that if you use isql to connect to and query a server, you must execute isql using the -i interfaces file parameter to specify the name and location of the sql.ini file.)

The Elements of a sql.ini File Entry

The following list describes each element in a sql.ini file entry:

• Server name

  Specifies the name of the server application to which a client application connects. Server names must be no more than 11 characters long. The initial character of a server name should be a letter (ASCII a-z, A-Z). The characters that follow may be letters, numbers, or the underscore character ("_").

• Driver

  Specifies which gateway driver DLL should be used for the connection.

• Service type

  Specifies the type of connection for the entry. Two values are possible:

  • query - Represents connection information used by a client to log in to the server. "query" lines may refer to a network address on any machine.
  • master - Represents connection information used by a server, specifying where the server should listen for connection requests from clients. "master" lines must always refer to a network address on the local machine. Only servers use the information provided by this line. "master" lines are not necessary in a sql.ini file for a machine running only clients.
• Connection information

  Specifies network address-related information for the specified server. The format of the server connection information will vary depending upon the driver used in the connection.

Network Support

Your DirectConnect can communicate with OmniConnect, Open Server applications, and client software on your network. Clients can talk to one or more servers.

DirectConnect for Oracle for Microsoft Windows NT supports network connections using the Named Pipes, Windows Sockets (TCP/IP), and SPX/IPX protocols.

To add network protocol support to a server, configure connection information for that network protocol using the sqledit program (see Appendix A, "Using sqledit"). Follow the instructions below to select the correct connection information for the Named Pipes, Windows Sockets, or SPX/IPX protocols.

WARNING! Network addresses must be unique for all servers running on the network.

Named Pipes Information

For the Named Pipes protocol, the connection information consists of the unique pipe name for the server. Valid pipe names begin with \pipe and follow the same naming restrictions as MS-DOS file names.

To avoid conflicts, always use unique pipe names of the same length for all Sybase products on your PC. Here is an example pipe name for DirectConnect for Oracle: \pipe\dco\query

If you are adding a network entry to access a server on a remote, networked machine (not the local machine), preface the pipe name with \\machine_name, where machine_name is the name of the PC running the server. Do not add the \\machine_name prefix if you are configuring a network entry for a server on the local PC.

Windows Sockets Information

For the Windows Sockets protocol, the connection information consists of the TCP/IP host name of the Windows NT machine and a unique socket for the Adaptive Server, separated by a comma. No default will appear in the window. The following entry is an example of a TCP/IP host named "centaur": "CENTAUR, 5000".

Note: The TCP/IP host name is case-sensitive.

Valid socket numbers for DirectConnect for Oracle range from 1025 to 65535. Do not choose a socket number that is in use by any other application on your PC.

SPX/IPX Information

For the NWLink SPX/IPX protocol, the connection information consists of one of the formats shown in the following table. Any of the three formats is acceptable for the MASTER entry, but only Format 1 and Format 3 are acceptable for QUERY entries.

With Format 3, the server cannot reside on the same machine as its client, and it cannot use either Format 2 or Format 3 for addressing. If you want to connect to a local server, use the Named Pipes protocol.

Table 2-1: Formats for NWLink SPX/IPX protocol

Format	Connection Information Syntax	Example
1	net_number,node_number,socket_number	16,1,83BD
2	computer_name,socket_number	groucho,83BD
3	computer_name	groucho

The libtcl.cfg Configuration File

The libtcl.cfg configuration file is created at the time you install DirectConnect for Oracle, and contains information for each installed Net-Library driver. The client application uses the information in the sql.ini file entry, along with the information in the libtcl.cfg entry, to make a connection to a server using the correct gateway DLL. If the libtcl.cfg file must be modified, use sqledit (see Appendix A, "Using sqledit").

The Elements of a libtcl.cfg File Entry

The following list describes each element in a libtcl.cfg entry:

• Driver DLL filename

  Specifies the file name (but not the file extension) of the Net-Library driver DLL.

• Driver description

  Describes, briefly, the Net-Library driver. Driver descriptions are likely to be as brief as "Named Pipes Drivers" or "NWLINK SPX/IPX Drivers." You must specify a description, and the first word of the description must be different from the first word of other Net-Library driver descriptions.

Set Environment Variables

To run DirectConnect for Oracle, you must first define the proper environment variables.

Set the SYBASE environment variable to point to your Sybase installation directory.

Update the PATH environment variable to include the SYBASE\bin and SYBASE\dll directories. The PATH environment variable must also include the Oracle NT directory, orant\bin.

If you are using SQL*Net V2, update the ORACLE_HOME environment variable to point to your Oracle client installation directory, for example: d:\orant.

These environment variables can be set from the System menu in the Windows NT Control Panel. If DirectConnect for Oracle is running as a service, set them as System Environment Variables.

Installing and Removing DirectConnect for Oracle As a Service

If you want DirectConnect for Oracle to continue running after you log out of Windows NT, you must install DirectConnect for Oracle as an NT service. This will also allow you to start and stop DirectConnect for Oracle from the Services menu in the Windows NT Control Panel.

instdco

There is a program called instdco in the SYBASE\bin directory.

This program allows a Windows NT administrator to install or remove DirectConnect for Oracle as an NT service.

Installing DirectConnect for Oracle as a Service

The syntax to install DirectConnect for Oracle as a service is:

instdco service_name exe_location "-Sservice_name"

service_name is the name of the DirectConnect for Oracle. This should also match an entry created in the sql.ini file using sqledit (see Appendix A, "Using sqledit").

exe_location is the location of the DirectConnect for Oracle executable. DirectConnect for Oracle executables are installed in the SYBASE\bin directory. For example, if you are using V 7.1 of the Oracle client software, c:\dco\bin\dco71.exe or c:\dco\bin\dco73.exe if you are using V 7.3 of the Oracle client software.

For example, to create a DirectConnect for Oracle service named dcosrv1, type this command:

instdco dcosrv1 c:\dco\bin\dco73.exe "-Sdcosrv1"

You can now start dcosrv1 from the Services menu in the Control Panel.

Installing DirectConnect for Oracle for Windows NT as a service creates entries in the NT Registry. When instdco is run, an entry in HKEY_LOCAL_MACHINE\SOFTWARE\SYBASE\DCO\Server\ server_name is made, containing start-up parameters for that server.

Removing a DirectConnect for Oracle Service

The syntax to remove DirectConnect for Oracle as a service is:

instdco service_name remove 

What's Next?

Go to the next chapter for instructions on running DirectConnect for Oracle.