Installation Guide Adaptive Server Enterprise for Linux/Intel

Chapter 6 Installing Sybase PC-Client Products

Chapter 6

Installing Sybase PC-Client Products

Your UNIX-based Adaptive Server also includes PC-client products that you install on a PC and connect, via the interfaces file, with your Adaptive Server.

This chapter describes how to install client products on Windows 98 and Windows NT 4.0.

Overview

Client plug-ins enable clients, such as Sybase Central and Open Client, to access Adaptive Server.

Sybase Central plug-In

The Sybase Central plug-in allows you to connect to of Adaptive Server via client connections. You can use Sybase Central to connect to remote servers, local servers (installed on the same machine), and multiple servers. See "Configuring network connections for client products". Before you use the plug-in, restart your computer to implement changes made to the PATH and CLASSPATH environment variables during installation.

Open Client runtime

The Sybase PC-client CD includes Open Client software for Windows NT and Windows 98. Several products, such as the Adaptive Server plug-in and SQL Advantage require Open Client runtime. Monitor Client Library requires Open Client/C with the SDK option.

Open database connectivity

Some applications do not connect to Adaptive Server directly through the Open Client software but through the Open Database Connectivity (ODBC) driver, or the jConnect driver instead. For example, PowerDynamo connects through the ODBC driver.

See the Adaptive Server Configuration Guide for more information.

ODBC and OLE DB require the Microsoft Data Access Component (MDAC). You can download it directly from Microsoft's Web site .

Installing PC-Client products

Before starting the installation process for PC-client products, be sure that you have at least an extra 2.4MB of disk space, a \temp directory and TEMP environment variable.

The installation program uses the extra space and directory to write files temporarily during the installation. The installation program frees this space after installation is complete.

Special instructions for Windows 98 platforms:

Environment Space is an area of memory set aside for each process in which environment variables can be defined. By default, there is a fixed amount of memory set aside to hold environment variables. This space contains the name of the variable (for example, TEMP) and its value (for example, C:\Windows\temp). Windows 98 by default provides for 256 bytes of environment space. Each environment variable defined takes up a specific amount of space depending upon the number of characters in the name and value. If you define an environment variable and there is not enough space to hold the variable and its definition, Windows will return an error indicating that you are "out of environment space."

If you are installing PC-client products on the Windows 98 platform, follow these steps to increase your environment space.

Bring up a DOS window
Right click on the MSDOS icon on the left end of the top window bar to bring up the properties window
Select Memory
Select Initial Environment and enter: 4096
Click OK

To install client products on Windows 98 and Windows NT:

Verify that your computer has sufficient RAM for each product. See Chapter 2, "Installation Requirements".
Log in using an account with Windows NT administrator privileges.
Close any open applications or utilities to free memory and system resources.
Insert the PC-client CD in to the drive. The Studio Installer should start automatically.
Alternatively, you can start the Studio Installer from the Windows Start menu, select Start | Run, and enter:
```
X:\setup.exe
```
where X is your CD-ROM drive.
Click OK.
When the Studio Installer starts, it prompts you for an installation directory. Click Next.
Select the type of installation to be performed.
- Standard Install - installs the default components a user needs.
- Full Install - installs every component on the CD.
- Customized Install - allows you to select which components to install. Certain components will automatically be installed if they are required to run other selected components.
  If you select Customized Install, the next window is the Component Selection screen, which allows you to specify which components to install.
  Components that would be installed in a standard installation appear with a check in the check box to the left of the product name. You may select or deselect components from this list. Components with subcomponents have a More... button enabled. Clicking this button allows you to select or deselect subcomponents.
Click Next.
The Summary screen displays every component to be installed by the Studio Installer, the required disk space, and the available disk space.
If the target directory does not have enough free space, the available space appears in red. Clicking Next without sufficient hard disk space results in an error and stops the installation.
Click Next.
Optionally, you can select Save on the Summary screen to save all the installation information into a cmdfile to proceed with the installation in a noninteractive, silent install. See Appendix A, "Alternative Installation Methods".
If the target directory does not exist, Studio Installer prompts: "OK to create directory?" Click Yes.
The Studio Installer installs the components and displays a progress indicator.
Warning!
If you are prompted to overwrite any DLLs, select Yes only if the version of the new DLLs is later (the version number is larger) than the one it is attempting to overwrite.
The Studio Installer generates an error message and stops the installation if you do not select any components for installation.
Click Back to select components, or Cancel to cancel the installation procedure.
If any components selected to be installed require a license, the Sybase Software Asset Management (SySAM) screen displays and prompts you for certificate information at this time.
When prompted to reboot the computer, leave the CD in the CD-ROM drive and select Yes. Restarting the PC updates the environment variables and registry keys.
If you are installing client products on the Windows 98 platform, you must manually restart the computer before proceeding with the configuration of client products. The Studio Installer does not automatically reboot the Windows 98 operating system.

To configure client network connections to Adaptive Server, see "Configuring network connections for client products".

If you installed jConnect 4.5 or 5.5 from the PC-Client CD, see "Installing Stored Procedures for jConnect" in Chapter 5, "Post-Installation Tasks".

Installing a Java Runtime Environment

Before you can use the Sybase Central monitoring features, you need to install the Java Runtime Environment (JRE):

To install the JRE:

Go to: %SYBASE%\ASEP_win32.
Double-click the file jdk1_1_8-win.exe and follow the installation instructions.
Restart your computer after you install the JRE.

Installing the Java Development Kit

Optionally, you can install the entire Java Development Kit (JDK) instead of the JRE. The JDK requires more disk space and includes files and features that support development of Java applets and applications. Sybase does not provide the JDK (see step 1 in the following instructions).

To install the JDK:

Download the JDK for your operating system from the Java Software Web site .
Double-click the file you downloaded.
Follow the installation instructions.
Add the following path to your CLASSPATH environment variable:
```
x:\install_path\lib\CLASSES.ZIP
```
where x:\install_path is the location (drive and directory) where you installed the JDK; for example, c:\javasoft.
Add x:\install_path\bin to your PATH environment variable, where x:\install_path is the location (drive and directory) in which you installed the JDK; for example, c:\javasoft.

Installing InfoMaker

InfoMaker is distributed as part of the PC-Client package. If you want to use the InfoMaker Demo Database, you must download and install Adaptive Server Anywhere.

To install InfoMaker:

Use the Studio Installer to install the software from the CD as described in "Installing PC-Client products".
Run the InfoMaker setup utility located in %SYBASE%\INFO-7_0_2\install.
From a DOS prompt, enter:
```
setup.exe "-EAS3"
```
or, from the Windows task bar, select Start | Run, and enter the full path to the executable, including the
```
 -EAS3
```
argument.
```
X:\sybase\INFO-7_0_2\install\setup.exe "-EAS3"
```
where X:\sybase is the installation directory for the PC-client components.
When prompted for an installation directory, accept the default.
When prompted to reboot the computer, leave the CD in the CD-ROM drive and select Yes. Restarting the PC updates environment variables and registry keys.
See the Powersoft documentation for instructions on using InfoMaker.

If you cannot launch the Demo Database through your shortcut, please change the properties in it by setting the path to your SQL Anywhere win32 directory.

Installing PowerDynamo

PowerDynamo is distributed as part of the PC-Client package.

To install PowerDynamo:

Use the Studio Installer to install the software from the CD as described in "Installing PC-Client products".
Run the PowerDynamo setup utility located in X:\sybase\PowerDynamo\install\setup.exe
where X:\sybase is the installation directory for the PC-client components.
When prompted for an installation directory, accept the default.
When prompted to reboot the computer, leave the CD in the CD-ROM drive and select Yes. Restarting the PC updates environment variables and registry keys.

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:

Add the location of the LDAP libraries to the path environment variable for your platform.
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
```
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.
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:

Using the Microsoft Windows task bar, click Start | Programs | Sybase | dsedit.
Click OK on the first screen to open the InterfacesDriver screen.
Select ServerObject from the menu, and click Add.
In the Input Server Name box, enter the name of the server for which you are creating an entry.
Click OK.
In the Attributes column, double-click on the server address row you just added.
In the ProtocolNetwork Address, click Add.
From the drop-down list in the Protocol box, select TCP, NAMEPIPE, SPX, or VINESIP.
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.
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:

From the Windows task bar, click Start | Programs | Sybase | OC OS Config.
Click the NetLibrary tab.
Select Windows NT or 98 as the platform and TCP as the protocol.
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:

Select Start | Programs | Sybase Central Java Edition from the Windows task bar to start Sybase Central.
Select Tools | Connect from the Sybase Central menu bar to activate a Sybase Adaptive Server login screen.
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.
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.
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.
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."


	Expand Search