Installing EAServer takes 10 – 20 minutes, depending on the speed of your computer and features you are installing.
What the installer does 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:
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 Sybase Central 4.3 is installed, the installer configures the new EAServer installation to use the existing Sybase Central installation. Otherwise, the installer creates a new Sybase Central 4.3 installation.You cannot modify this location.
Sets the JAGUAR_CLIENT_ROOT environment variable to represent the EAServer installation directory.
If you install the PowerBuilder virtual machine (PBVM), adds required entries to the system CLASSPATH environment variable.
Creates (or updates if it already exists) the vpd.properties configuration file in your %SystemRoot% directory. vpd.properties is used internally by InstallShield. Do not delete or modify this file as it may affect the ability to reinstall or uninstall any software that uses an InstallShield installer (including non-Sybase products).
Registers the EAServer client ActiveX automation controllers for the JaguarORB, CtsSecurity, and SessionManager ActiveX client interfaces (if the ActiveX client runtime is installed).
Adds the appropriate paths to the following Registry path:
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\APP PATHS
Creates or updates Registry subkeys, including ODBC.INI and ODBCINST.INI.
Creates or updates the SYBASE key in HKEY_CURRENT_USER\Software.
Updates system and user paths in HKEY_CURRENT_USER\Environment.
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.
If you have downloaded EAServer, expand the installation software to a temporary location. Otherwise, insert the software CD into your CD drive.
Select Start | Run, and enter:
path\setup.exe [-is:tempdir temp_directory]
where path is the location of the installation software. If you have less than 170MB in your temp directory, add the -is:tempdir temp_directory option, replacing temp_directory with the full path to a temporary directory that has at least 170MB of available disk space. For example:
f:\setup.exe -is:tempdir d:\temp
The installer starts, and the EAServer 5.2 Install window appears.
The installer may not run correctly some machines with
older versions of the Microsoft DirectDraw display software and
drivers. If setup.exe does not run correctly,
run jsetup.bat, located in the SupportNT directory
of the CD, which launches the installer with Java DirectDraw support
disabled. The installer may run more slowly with DirectDraw disabled.
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 dropdown 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 any EAServer applications, including EAServer, and EAServer as an Windows service. Click Next.
Enter the full path to which EAServer is to be installed. If this is an upgrade, enter the full path to the directory in which EAServer 5.x 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, then 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 choose 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.
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 and select to install any of the JDKs, you can either install the selected JDK, or use a JDK that may already be 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 where to install it to. 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 in the specified location.
Click Next to continue.
If you creating a new installation and have chosen to install EAServer as a Windows service, specify the server and service names. For a new install, accept the default values unless you plan to create a different server after completing the install. For new installs, the installer creates one server named Jaguar. If you specify another server name, the service will not run unless you create the server after the install completes. Chapter 3, “Creating and Configuring Servers,” in the EAServer System Administration Guide describes how to create servers.
If you are upgrading, you can specify the name of an existing server other than the default, Jaguar. In this case, specify a service name that does not conflict with other services running on your machine.
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 install completes, you can modify or remove preconfigured listeners as described in Chapter 3, “Creating and Configuring Servers,” in the EAServer System Administration Guide.
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 display the readme file. Click Next.
Click Finish to exit the installer.
For each of the following products you choose to install, see the corresponding section for additional installation and configuration instructions:
ASA support – “Installing ASA”.
Any of the Web server redirector plug-ins (Apache, Netscape, iPlanet, or Microsoft IIS) – Chapter 4, “Installing and Configuring a Web Server Redirector Plug-In.”
ODBC and Open Client – Chapter 5, “Configuring Open Client and ODBC.”
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.
Installing EAServer