Chapter 1: Before You Install EAServer

What to install

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 for developing EAServer applications. If you choose this option, the client runtime files are installed on your machine in the easclient.jar file.
Client Runtime Only – installs only the client runtime files. 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.
Full – installs all features.
Custom – you define which features to install. By default, features that are installed as part of a typical installation are installed as part of a custom installation, but you can add or remove features.

If you customize your installation, be aware of the following:
- JDK 1.3 – EAServer Manager, jagtool, jagant, JAAS, and the J2EE Application Client require JDK 1.3 which is installed automatically. If you select this option you have the choice of installing it, or using an existing JDK1.3 installation.
- C++ runtime files – SSL support requires C++ runtime libraries.
- Client runtime files – to run Java and C++ client applications, or to use SSL connectivity from PowerBuilder clients, you must install the EAServer client runtime files.
- When you select to install the server, you must also install the C++, Java, and SSL runtime files.

Table 1-2 describes EAServer features and lists the features that are installed for each type of installation. Any feature can be optionally installed if you select the Custom installation type, and 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
Locales	Allows you to install locale files in addition to English.
Optional Charsets	Allows you to install additional character sets.
ActiveX runtime	Includes the files required to run standalone EAServer ActiveX client applications on machines that lack a server installation. For example, use this when a Web DataWindow application uses Microsoft Active Server Pages to connect to EAServer.
C++ runtime	Includes the files required to run standalone EAServer C++ client applications on machines that lack a server installation; for example, header files, link libraries, and DLLs.	Typical, Client Runtime
Java runtime	Includes the files required to either run standalone EAServer Java client applications on machines without a server installation, or to develop and run Java applications that use EAServer components.	Typical, Client Runtime
SSL runtime	Installs the SSL runtime to manage SSL certificates on client installations including files required to open SSL connections from C++ or PowerBuilder clients, including the standalone client Security Manager.	Typical, Client Runtime
System Management	Installs the EAServer systems management components to support remote management using JDMK, JMX, and SNMP. See the EAServer System Administration Guide for more information on this feature.
Windows Service	For Windows platforms. This option allows you to install EAServer as a Windows service. Reboot your machine if you install EAServer as a Windows service.
ODBC	Installs the ODBC drivers. See Chapter 5, “Configuring Open Client and ODBC” for more information.	Typical, Client Runtime
Program Menu Items	For Windows platforms. 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	For Windows platforms. 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, iPlanet, IIS, and Netscape 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.
Debug server	Includes the debug version of the application server and files required to manage the server and develop clients and components.	Typical
Documentation	Installs online HTML documentation and tutorial files in the EAServer html\docs subdirectory.	Typical
EAServer Manager	Allows you to configure servers, packages, and components.	Typical, Client Runtime
Message Bridge	Sybase Message Bridge for Java generates Java classes that simplify parsing and construction of XML documents used in your EAServer applications. Installs the runtime files required by Message Bridge and the GUI that aids in building Message Bridge applications.
Open Client	Installs the Open Client™ software. See Chapter 5, “Configuring Open Client and ODBC” for more information.	Typical
Samples	Installs the EAServer samples and the Adaptive Server Anywhere database server files required to run databases used by the samples and tutorials.	Typical
PowerBuilder version 8.0.4	Provides support for running PowerBuilder 8.0 components in EAServer.
PowerBuilder version 9.0.1	Provides support for running PowerBuilder 9.0 components in EAServer.
PowerBuilder version 10.0.0	Provides support for running PowerBuilder 10.0.0 components in EAServer.
PowerDynamo to JSP conversion utility	Installs a tool to convert PowerDynamo Web sites to JSP-based J2EE Web applications	Custom
Web services support	Installs Web Services Toolkit. You can choose which components are installed: WST runtime installs the files required to run Web services in EAServer. WST client runtime installs only the files that are required to run Web services clients. These files are also included with the WST runtime option. Administration console installs the Web-based Web services administration tool. Eclipse based development tool installs an Eclipse plug-in to create and administer Web services, and optionally installs Eclipse. Private UDDI server installs the files required to run a private Uniform Description, Discovery, and Integration (UDDI) server.	Typical install includes the WST runtime, administration console, Eclipse plug-in, and private UDDI server. Run a custom install to install only the client runtime files.

Multiple EAServer installations on a single machine

View this book as PDF