Installing EAServer

Installing EAServer takes 10 – 20 minutes, depending on the speed of your computer.

The setup program installs software in default drives and directories unless you specify otherwise. If a directory you specify does not exist, the setup program creates it. The setup program:

Creates a release directory in a location you specify.
Sets the JAGUAR environment variable to represent the EAServer installation directory.
Checks whether Sybase Central 4.3 has been installed with Sybase Adaptive Server Enterprise 12.5.1 or by an existing EAServer 5.2 installation. If the installer finds a Sybase Central 4.3 installation, it configures the new EAServer installation to use the existing Sybase Central installation. You cannot modify this location.

Installing EAServer

Exit any programs that are running. If you do not, the Sybase installer may not be able to copy some files to the appropriate directories.

Insert the EAServer CD in your CD drive. On most machines, the installer starts automatically. If you suspect that you do not have the required 150MB in your temp space, cancel the installation, and specify an alternate temporary directory as described in the next step.

To start the installer from the command line, change to the CD drive and enter:

./setup [-is:tempdir work_directory]

Specify the -is:tempdir option if you have less than 150MB in your temp space. work_directory is the full path to a temporary directory to be used by the installer.

The installer starts, and the Sybase EAServer 5.2 Install window appears.

Click Next in the Install window.

Use Back and Next to step backward and forward through the installation process to modify specifications as necessary.

Select Cancel to halt the installation process.

Select your country or region from the drop-down list to display the license agreement. You must read and accept the terms of the license agreement for your country before you can install any Sybase products. Click Next.

The installer checks whether any EAServer processes are running on the machine. If prompted, shut down EAServer and any EAServer applications. Click Next.

Enter the full path to the directory in which to install EAServer. If this is an upgrade, enter the full path to the directory in which EAServer 5.0 is installed. Select Upgrade Install to upgrade your installation to 5.2.

If you have already installed EAServer 5.2, you can select one of the other options to upgrade your license, add components, or reinstall. For details, see “Reinstalling or adding components”.

The installer searches for a directory identified by the $JAGUAR environment variable. If located, this is the default directory for upgrading your installation or adding components.
Select the type of installation you want and click Next:
- Typical – installs EAServer using the most common installation options.
- Client Runtime Only – installs the files required to run standalone EAServer clients.
- Full – installs everything.
- Custom – allows you to select specific installation options for EAServer. After choosing this option, select the server options to install (for example, debug libraries and the files required to support SSL clients).
  
  Select the EAServer features to install by placing a check mark next to the feature.
You must install ODBC, or the server will not run.

See “What to install” for a list of features that are installed for each installation type.
If you are installing the Advanced Edition, provide the product license information:
- Order Number
- Feature Name
- Authorization Code
The product license information is provided in your EAServer package on a printed Sybase certificate. Click Next.
If you select a custom installation, you can either select a JDK to install or use a JDK that is already installed on your system. If the installer detects an existing JDK of the appropriate version, it is displayed as the default location. Existing JDKs must be of the correct version and patch level, as described in “JDK versions”.

Click Next to continue.
If you are installing the Web Services Toolkit Eclipse plug-in, you must have an Eclipse installation. Choose one of the following options:
- Select Install New Eclipse and enter the path in which to install it. The installer places Eclipse version 2.1.1 in an eclipse subdirectory in this location.
- Select Use Existing Eclipse to configure your EAServer installation to use an existing Eclipse installation. Enter the path to the existing installation, which must be Eclipse version 2.1, 2.1.0, or 2.1.1, installed in an eclipse subdirectory of the specified location.
Click Next to continue.
EAServer Manager and Security Manager require a Sybase Central 4.3 installation. You can share a single Sybase Central 4.3 installation between multiple EAServer and Adaptive Server Anywhere installations on the same machine. Choose one of the following options:
- Select Install New sybcentral43, and enter the path in which to install it. The installer places Sybase Central version 4.3 in a sybcentral43 subdirectory of this location.
- Select Use Existing sybcentral43, and enter the path to the existing installation, which must be Sybase Central version 4.3, installed in a sybcentral43 subdirectory of the specified location.
Click Next to continue.

If you are creating a new installation, the installer displays port numbers for the preconfigured EAServer network listeners, as displayed in Table 2-1. You can edit the ports or accept the default settings. Choose port numbers that are not used by other servers running on your machine.

You can click “Suggest ports” to test whether any of the specified ports are in use. The installer tests each port to see if it is used by a running process or in known EAServer installations on the machine. If a port is in use, the number is incremented by 100 and tried again.

When you click Next, the installer also tests whether ports are in use. After the installation completes, you can modify or remove preconfigured listeners as described in Chapter 3, “Creating and Configuring Servers,” in the EAServer System Administration Guide.

**Table 2-1: Default listener settings**
Listener name	Default port	Description
http	8080	For HTTP (Web client connections).
https1	8081	HTTP with SSL security.
https2	8082	HTTP with SSL security requiring client certificates to connect.
iiop	9000	For IIOP connections. EAServer Manager, PowerBuilder®, and other standalone client applications use this protocol.
iiops1	9001	IIOP with SSL security.
iiops2	9002	IIOP with SSL security requiring client certificates to connect.
tds	7878	Used by clients that use the Methods as Stored Procedures (MASP) interface.
OpenServer	7979	Used by clients that connect to legacy Sybase Open Server™ applications that have been adapted to run in EAServer.

The installer displays a summary of the features to be installed and the installation directory. Review these entries and click Next to continue or Back to modify your entries.

The installer begins copying files and informs you when the installation is complete. Select Start Server to start EAServer or View Readme to view the readme file. Click Next.

Click Finish to exit the installer.

If you started the installer by allowing it to launch automatically after inserting the CD, or by clicking the setup icon in your graphical file manager, close the terminal window labeled Run after exiting the installation.

For each of the following products you choose to install, see the corresponding section for additional installation and configuration instructions:

ASA support – “Installing ASA”. To run the sample applications and tutorials, you must install ASA.

Any of the Web server redirector plug-ins (Apache, iPlanet, or Sun Java System) – Chapter 4, “Installing and Configuring a Web Server Redirector Plug-In.”

ODBC and Open Client – Chapter 5, “Configuring Open Client and ODBC for EAServer.”

Web Services Toolkit – Web Services Toolkit is automatically installed when the feature is selected.

Network installation

If you are a system administrator, you may want to allow users to install EAServer from a network drive rather than from the CD. To do this, copy the files from each CD to a separate directory on a network drive and note the location. During installation, the user is prompted to specify the directory location for each CD.