Installation types

When you install EAServer, features are installed by default depending on the type of installation you select. The types of installations include:

Typical – installs the typical files required to develop EAServer applications.

Custom – you define which features to install. By default, features that are installed in a typical installation are selected for installation in a custom installation, but you can add or remove features.

Client Runtime – installs only the client runtime files, and Web server plug-ins. Select this option to run Java or C++ client applications or to use SSL connectivity from PowerBuilder clients, but not install the entire product set.

You are not required to install the client runtime if you are developing clients on a machine where the application server is installed. The server installation includes the core server files.

See Chapter 4, “Installing and Configuring a Web Server Redirector Plug-In,” for more information about the Web server plug-ins.
Full – installs all features.
Upgrade – upgrades EAServer from version 6.0.0, 6.0.1, 6.0.2, or 6.1.
Add Components – adds components to an existing 6.2 installation.

Table 1-2 describes EAServer features and lists the features that are installed for each type of installation. A Full installation installs everything.

**Table 1-2: EAServer features**
Feature	Description	Installation type
Server	Includes the application server and files required to manage the server and develop clients and components.	Typical
Core server files	Installs files required by the server.	Typical
Runtime libraries	Installs the required runtime libraries and includes these options: Standard – compatible with JDK 1.5 and JDK 1.6. JDK 1.5 is the default. Optimized – compatible with JDK 1.6 only.	Typical
Client Runtime	Installs the client runtime files. Includes these options: Standard – compatible with JDK 1.5 and JDK 1.6. JDK 1.5 is the default. Optimized – compatible with JDK 1.6 only.	Client Runtime and Typical
Servlet Runtime	Installs the servlet runtime files.	Typical
Windows Service	Allows you to install EAServer as a Windows service. Restart your machine if you install EAServer as a Windows service.
Program Menu Items	Creates Start menus to run EAServer, start EAServer Manager, and so on. This option does not support multiple EAServer installations on a single machine. See “Multiple EAServer installations on a single machine”.	Typical
Registry Update	Updates the Registry with required EAServer entries. When you install or reinstall EAServer, the installer checks the Registry for an existing EAServer installation if this feature is selected, and uses that location as the default installation location. This option does not support multiple EAServer installations on a single machine. See “Multiple EAServer installations on a single machine”.	Typical
Apache, IIS, and Sun Java System Web Server plug-ins	Installs Web server plug-ins to integrate EAServer Web applications with Web sites hosted on popular Web servers.See Chapter 4, “Installing and Configuring a Web Server Redirector Plug-In,” for more information.	Client Runtime
Administration	Installs: J2EE Web Administration Console – a web-based console that allows you to configure servers, packages, and components. Web File Server – a Web application that provides FTP services on remote servers. Web Shell – allows you to issue server and cluster commands through the shell command line. Web Load Balancer – a Web application that balances server loads by redirecting HTTP requests from Web applications to application servers within a cluster.	Typical
Documentation	Installs online HTML documentation and tutorial files in the EAServer html or docs subdirectory.	Typical
Extras	Installs these options: jConnect 6.05 – JDBC (Java Database Connectivity) allows Java applications to access multiple database management systems using Structured Query Language (SQL). (Typical) JUDDI server – installs the files required to run a private Java implementation of the Uniform Description, Discovery, and Integration (UDDI) server. Eclipse Development tool – installs an Eclipse plug-in to create and administer Web services, and optionally installs Eclipse.	Typical
JDKs	Options for installing both JDK 1.5 and 1.6.	JDK 1.5 is included in a Typical install
Open Client	Installs the Open Client software. See Chapter 5, “Configuring Open Client and ODBC for EAServer” for more information.	Typical
Optional Charsets	Allows you to install additional character sets.
Samples	Installs the EAServer samples.	Typical
Sybase Asset Management System (SySAM)	(Optional) Installs SySAM to perform license administration and asset management tasks. If you select this option, you can then select: Network License Server – installs the network license server used to manage resource licenses. License Utilities – installs SySAM license utilities. See the Sybase Software Asset Management Users Guide on the Sybase Product Manuals Web site.	Typical
Tools Support	Installs: PowerBuilder 10.5.1 – support for running PowerBuilder 10.5.1 components in EAServer. PowerBuilder 11.2 – support for running PowerBuilder 11.2 components in EAServer.