Installation Guide EAServer 5.
DOCUMENT ID: DC32146-01-0550-01 LAST REVISED: December 2006 Copyright © 1997-2006 by Sybase, Inc. All rights reserved. This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. To order additional documents, U.S.
Contents About This Book ............................................................................................................................ v CHAPTER 1 Before You Install EAServer .......................................................... What EAServer contains .................................................................. EAServer documentation ................................................................. HTML documentation ..............................................................
Contents CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In .... 37 Overview ........................................................................................ 37 How the plug-in works ............................................................. 38 Load balancing ........................................................................ 39 Failover and detecting unavailable application servers........... 40 Binding to a specific application server ...................................
About This Book This book describes how to install EAServer, an application server, which includes an integrated set of development tools that you use to deploy Web applications that support high-volume traffic, dynamic content, and intensive online transaction processing (OLTP). Audience This book is for anyone responsible for configuring the EAServer runtime environment, or for creating and deploying packages and components on EAServer.
The EAServer Feature Guide explains application server concepts and architecture, such as supported component models, network protocols, servermanaged transactions, and Web applications.
About This Book • Implement custom security services for authentication, authorization, and role membership evaluation • Implement secure HTTP and IIOP client applications • Deploy client applications that connect through Internet proxies and firewalls The EAServer Performance and Tuning Guide describes how to tune your server and application settings for best performance.
Formatting example To indicate File | Save Menu names and menu items are displayed in plain text. The vertical bar shows you how to navigate menu selections. For example, File | Save indicates “select Save from the File menu.
About This Book ❖ ❖ ❖ Finding the latest information on product certifications 1 Point your Web browser to Technical Documents at http://www.sybase.com/support/techdocs/. 2 Click Certification Report. 3 In the Certification Report filter select a product, platform, and timeframe and then click Go. 4 Click a Certification Report title to display the report.
Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.
About This Book If you need help Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you cannot resolve a problem using the manuals or online help, please have the designated person contact Sybase Technical Support or the Sybase subsidiary in your area.
xii EAServer
CH A PTE R 1 Before You Install EAServer This chapter contains information you need to know before you install or upgrade EAServer. Topic What EAServer contains Page 1 EAServer documentation System requirements 2 2 What to install 4 What EAServer contains Besides the EAServer software, the installation includes: Installation Guide • Adaptive Server Anywhere 9.0.2 database server runtime files • jConnect™ for JDBC™ 5.5 and 6.0 • PowerBuilder 10.2.
EAServer documentation EAServer documentation See the release bulletin for late-breaking installation information. HTML documentation Online HTML documentation is installed with EAServer in the docs subdirectory within the html subdirectory. To view the documentation after installation, use your Web browser to load html/docs/index.html. You can also view the documentation by connecting to EAServer as described in “Starting EAServer, ASA, and EAServer Manager” on page 16.
CHAPTER 1 Before You Install EAServer Installation type Minimum hard disk space Full Client Runtime Only 881MB 453MB Typical Custom 834MB Depends on features selected Note The hard disk space size may vary for different Linux distributions. JDK versions EAServer requires version 1.3.1 of the Java Development Kit (JDK) from Sun Microsystems. You can optionally run servers with JDK 1.4.2 instead. By default, JDK 1.3.1 and the optional JDK versions that you select are installed with EAServer.
What to install What to install When you install EAServer, features are installed by default depending on the type of installation you select. The types of installations are: • 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.
CHAPTER 1 Feature Core server files Locales Before You Install EAServer Description Installs files required by the server. Installation type Typical Allows you to install locale files in addition to English. Optional Charsets EAServer Manager JDKs Allows you to install additional character sets. 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.
What to install Feature Samples Web Services support Description Installs the EAServer samples and the Adaptive Server Anywhere database server and runtime files required by some of the samples, and the tutorials. Installs Web Services Toolkit. You can choose which components are installed: Installation type Typical Typical • 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.
CH A PTE R 2 Installing EAServer This chapter explains how to install, upgrade, and uninstall EAServer, which includes the EAServer application server, its various features, and Adaptive Server Anywhere (ASA).
Installing EAServer • Upgrading your license, for example, from the Developer to the Advanced Edition • Reinstalling EAServer 5.5 or adding components or features to your installation 4 Verify that you have enough space to install the software. See “System requirements” on page 2. 5 The installer requires a valid X-Windows configuration. Make sure you can run the xterm command at the command prompt where you start the installer.
CHAPTER 2 ❖ Installing EAServer Installing EAServer 1 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. 2 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.
Installing EAServer If you have already installed EAServer 5.5, you can select one of the other options to upgrade your license, add components, or reinstall. For details, see “Upgrading, reinstalling or adding components” on page 13. Note 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.
CHAPTER 2 Installing EAServer 10 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” on page 3. Click Next to continue. 11 If you are installing the Web services toolkit Eclipse plug-in, you must have an Eclipse installation.
Installing EAServer 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 https1 8080 8081 For HTTP (Web client connections). HTTP with SSL security.
CHAPTER 2 Network installation Installing EAServer • ASA support – “Installing ASA” on page 16. To run the sample applications and tutorials, you must install ASA. • Any of the Web server redirector plug-ins (Apache or iPlanet) – 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.
Upgrading, reinstalling or adding components Each of these procedures is described below. Installation directory You must select the EAServer installation directory, and not the upper-level Sybase location to properly upgrade, add components, or reinstall EAServer. For example, if you selected /work/sybase as your original installation directory, the default EAServer installation directory is /work/sybase/EAServer.
CHAPTER 2 Installing EAServer 2 The installer prompts you for the type of reinstallation: Typical, Client Runtime Only, Full, or Custom. If you select Typical or Full installation type, a default set of features is reinstalled. Custom and Client Runtime Only allow you to modify your selections. Click Next. 3 For Custom and Client Runtime Only reinstallations, place a check mark next to the components to reinstall.
Installing ASA • Instance pools • Servers • SSL certificates To take advantage of new functionality, you may need to modify settings. For example, for listeners you can use {$JAGUAR_HOST_NAME} to specify the host value. This is the default value for new installs, but for upgrades, the existing values are preserved. Systems Management options Systems Management version 5.5 is described in Chapter 13, “Using Systems Management,” in the EAServer System Administration Guide.
CHAPTER 2 ❖ Installing EAServer Starting the server • Change to the EAServer bin directory, and run serverstart; for example: cd /work/Sybase/EAServer/bin serverstart.sh The server starts and runs as a foreground process in the current console window. To start the server in a separate window, use the -xterm option; for example: cd /work/Sybase/EAServer/bin serverstart.
Connecting to EAServer through a Web browser You need not provide a password for jagadmin unless one has been established. See “Administration password and OS authentication” in the EAServer Security Administration and Programming Guide for information on establishing a jagadmin password. • Host Name: your machine name or the name of the proxy host if you have selected the Use Proxy check box. • Port Number: your IIOP port number; the default is 9000.
CHAPTER 2 Installing EAServer • host – is the name of your machine. • http-port – is the port number at which EAServer accepts HTTP connections (the default is 8080). After you connect to EAServer, you can view user documentation and run the EAServer samples. ASA must be installed to run the samples. Installing the CocoBase Enterprise O/R evaluation software EAServer 5.5 includes an evaluation version of CocoBase® Enterprise Object/Relational mapping software from Thought Inc.
Uninstalling EAServer 4 To view the features you are uninstalling, select View the Uninstall Summary Panel. Review your selections and click Next. 5 If the installation process created a new installation of Sybase Central 4.3, you can remove it. Do not remove Sybase Central if it is used by other EAServer 5.x installations or other Sybase products. To remove Sybase Central, select this option. Click Next.
CH A PTE R Creating Embedded EAServer Installations 3 You can silently run the EAServer installer. If you are packaging EAServer with your own software, you may want to create a scripted EAServer installer that runs as a subinstall of your own installation procedure, so your end users install EAServer without any installer interaction.
Configuring and running the silent installer • libjinstaller.so. • The JRE_1_4 subdirectory and its contents. Sybase recommends that you use this JRE to run the install. Other JRE versions may not work as well. • If you have the Developer or Workgroup Edition, copy SYBASE_EAS.lic from the root directory of the EAServer CD to the root directory of your install image.
CHAPTER 3 c Creating Embedded EAServer Installations For all upgrades, stop EAServer applications such as “Jaguar CTS” terminal windows, EAServer Manager, and server processes that you have started in the background. You can shut down servers that are running in the background using EAServer Manager or jagtool (after connecting to the server to be shut down), or by killing the process ID that is running the serverstart.sh or jagsrv command.
Configuring and running the silent installer Parameter Specifies -W EASInstallLog.logOutput The directory and file name for the log file. The default is: $D(temp)/EAS550Install.log -W EASInstallLog.isLogAllEvents This specifies eas550install.log in the /tmp directory. Whether to log all messages or only errors and warnings. Specify True to log all messages, and False to log only warnings and errors. Installation types Set the -W SilentInstallType.
CHAPTER 3 Creating Embedded EAServer Installations For upgrade installations (installation type is InstallUpgrade), specify the location of the previous installation, as specified by the JAGUAR environment variable for the installation. The default value is $D(install)/sybase, which specifies the directory /opt/sybase. License agreement For the silent installation to run, change the value of -W SybaseLicense.
Configuring and running the silent installer Table 3-3: Silent installer listener port parameters Parameter -W InstallLogFilename.value -W PortScan.silentResolvePortConflict Specifies The name and path of a log file where the listener port numbers are recorded. If you specify automatic detection of free ports, you can read the port numbers from this file after the installation. Whether to scan for unused ports if a specified port is in use.
CHAPTER 3 Creating Embedded EAServer Installations Parameter Specifies -W SilentEASJDK14installed.value Whether to use an existing JDK 1.4 installation to run servers with. To use an existing installation, set this parameter to Yes and specify the location as the value of the next parameter. Also, set the value of EASJDK14_server.active to False in the feature selection section. If you are using an existing JDK 1.4 installation, the location where it is installed.
Configuring and running the silent installer Parameter Set the value to -W LicenseAuthorizationNumber.value License authorization code Sybase Central installation parameters 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 Sybase Adaptive Server Anywhere installations on the same machine. Configure the options in Table 3-7 to specify whether to install a new copy of Sybase Central 4.
CHAPTER 3 Creating Embedded EAServer Installations Some features have a parent-child relationship (shown by indentation in the sample installation script). To install child features, you must enable both the parent feature and the child feature. Some features require additional files to be added to your installation image, as listed in Table 3-8. If you enable these features, add the required files to your image by copying them from the EAServer installation CD.
Configuring and running the silent installer Parameter Feature Additional requirements -P EASODBC.active Installs ODBC driver manager and driver files. Required to run servers (even if you do not use ODBC connections). Requires parent feature -P EASServer.active. Required for server installs Requires file SupportLinux/EAS_jars/ EAS_unixodbc.jar. Requires parent feature -P EASServer.active. -P EASWebServerPlugins.active Parent feature for Web server plug-in files.
CHAPTER 3 Creating Embedded EAServer Installations Parameter Feature Additional requirements -P EASSystemManagement. active Installs the EAServer systems management components that allow remote management using JDMK-, JMX-, and SNMP-based tools. Requires directory SupportLinux/SystemManagement (entire directory). -P EASToolsSupport.active Parent option for the tools support option. If set to False, the tools support options are ignored. Installs the PowerBuilder version 10.2.
Configuring and running the silent installer SilentInstall.sh -W "SilentInstallLocation.value=/opt/Sybase/EAServer" You must also remove the equivalent settings from the silent install configuration file. Silent uninstaller files You can configure the silent installer to support silent uninstallation, which creates a script your users can run to silently remove the installation from their system. The silent uninstaller requires: • The EASuninstall.jar and EASuninstall.
CHAPTER 3 Creating Embedded EAServer Installations SilentUninstall_Unix.sh Users of your installation run this file to remove the installation from their system. A sample of this file is on the EAServer installation CD. Place a copy in your install image, and verify the following, keeping in mind that the file is run from the EAServer _uninstall directory: • The CLASSPATH includes EASuninstall.jar (located in the same directory).
Post-installation configuration Test any other features that you are installing, such as EAServer Manager, Web Services, and so forth. Cleaning up the machine Before re-running the silent installation, uninstall the previous installation using the graphical or silent uninstaller. For graphical uninstaller instructions, see “Uninstalling EAServer” on page 19. For silent uninstaller instructions, see “Silent uninstaller files” on page 32.
CHAPTER 3 Creating Embedded EAServer Installations You can call these tools and APIs from your installation script or install program to configure the server and install application components. For example, you might install your own components by importing them as Jaguar JAR files with the jagtool or jagant deploy command, then use the install command to install the components to the preconfigured Jaguar server. You might also use the create command to define connection caches.
Post-installation configuration 36 EAServer
CH A PTE R 4 Installing and Configuring a Web Server Redirector Plug-In The Web server redirector plug-in allows communication between the Web server and the EAServer HTTP and HTTPS protocol listeners.
Overview iPlanet 6.0 requires Red Hat 4.0 To use the redirector plug-in for either the iPlanet 6.0, you must be running on Red Hat Advanced server 4.0. These Web servers do not support either Red Hat Advanced server 3.0 or the SUSE Linux Enterprise server. Commonly used terms Table 4-1 lists terms, which are used throughout this chapter.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In Figure 4-1: HTTP request flow through the redirector Load balancing Load balancing is transparent to the client. The redirector detects and directs requests from existing sessions to EAServer using either the J2EE cookie or the J2EE session identifier that is part of the HTTP request.
Overview In Figure 4-2, the Web server redirector has an entry in the redirector configuration file that directs requests for the “examples” Web application to three application servers: Jag1, Jag2, and Jag3. Requests for the Web application are distributed evenly across all three servers. Figure 4-2: redirector configuration file entry Failover and detecting unavailable application servers The redirector provides failover for Web applications.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In When a request arrives from a client, the Web server redirector sends it to an EAServer application server. The redirector selects the server based on a round-robin scheme where each new request from a client is directed to the next available application server that can service the request.
Overview Debugging If you are using the Apache or iPlanet redirector plug-in, you can trace requests by setting this directive in the redirector configuration file: Connector.SessionId When this directive is set, the value of ConnectorSessionId is appended to the URL that is forwarded to EAServer. EAServer writes the URL to the server’s HTTP request log, which may be helpful for debugging. For example, if you add this to the redirector configuration file: Connector.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In Configuring the data source for HTTPServletRequest methods When using a Web server redirector, you can configure the source for information returned by the HTTPServletRequest methods getScheme, getServerPort, and getServerName by setting the Web application property com.sybase.jaguar.webapplication.get-serverinfo-from.
Installing and configuring an iPlanet Web server plug-in • Context paths that inform the Web server which client requests to forward to the redirector. See “Defining context paths” on page 45. • An EASProxy object that specifies which HTTP methods are forwarded to the redirector. See “Adding the EASProxy object” on page 45. Adding location information The redirector plug-in is a Netscape Application Programming Interface (NSAPI) extension.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In Defining context paths Context paths inform the Web server which requests are directed to the redirector. In the obj.conf file, search for this line:
Installing and configuring an iPlanet Web server plug-in Edit the redirector configuration file This section describes how to set the redirector configuration file directives that: • Map Web server requests to EAServer listeners • Set the redirector logging level Mapping Web server requests to EAServer listeners Create and edit the redirector configuration file to add the Connector.WebApp directive, which maps requests sent to the redirector by the Web server to EAServer HTTP listeners.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In The redirector configuration file must contain the following mapping rule for each EAServer that you want to handle requests: Connector.WebApp /* = http://jaguar_host:jaguar_listener Where jaguar_host is the EAServer host machine and jaguar_listener is the EAServer HTTP listener.
Installing and configuring an iPlanet Web server plug-in Logging level Description error Adding Connector.LogLevel error to the redirector configuration file is appropriate when you want to log error messages to the Web server log file. Error messages provide additional information, such as the Web server disconnecting from EAServer or not connecting to an EAServer. verbose Adding Connector.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In Table 4-4: Libraries required by Web server EAServer files Web server destination directories • libjcc.so iPlanet: • libjctssecct.so WEB_SERVER_HOME/bin/https/lib • libjctssecct_f140.so • libjeas_httpd40.so (iPlanet) – this is the redirector plug-in file that must be identified in obj.conf. See “Edit the Web server configuration files” on page 43 for more information. • libjeas_httpd40_f140.
Installing and configuring an Apache Web server plug-in 3 Copy libraries from EAServer to your Web server. 4 Make an entry for the Web host in the /etc/hosts file. For information about the Apache Web server, see Apache Core Features at http://httpd.apache.org/docs/mod/core.html. Edit the httpd.conf configuration file The httpd.conf file: Sample httpd.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In determine the server's fully qualified domain name, using 1.2.3.4 for ServerName". However the following is fatal and the redirector will not load. "Unable to determine host name" • conn_config represents the redirector configuration file. The redirector configuration file can be any name and location you choose, but it must be identified by EASConfigFile. In this example, conn_config is the name of the redirector configuration file.
Installing and configuring an Apache Web server plug-in Figure 4-4 illustrates how a client request for examples/test.jsp and examples/images/welcome.gif to the Web server and port Web1:8020 is redirected to jag1:8080.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In For example, if “neptune” is the name of your Web server, and WEB_SERVER_HOME/conf/conn_config is the name and location of the redirector configuration file that you create, edit conn_config to set the Connector.WebApp directive: Connector.WebApp /testapp = http://jaghost1:8080 Connector.WebApp /estore1, /estore2, /estore3 = http://neptune:8080 Connector.WebApp /* = http://foobar:8080, http://neptune:8080 Connector.
Installing and configuring an Apache Web server plug-in Connector.WebApp /*=http://rainforest:8080 Connector.WebApp /*=http://neptune:8080 In addition, the server hosts specified for the WebApp directive (in this case, “rainforest” and “neptune”) must match the host names you define for your EAServer HTTP listeners.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In • libjeas_mod.so • libjeaseapi_mod.so • libjeasproxy_mod.so • libjeasproxyeapi_mod.so • libjinsck_r.so • libjintl_r.so • libjjnirt.so • libjlog.so • libjsybscl_r.so • libjtli_r.so • libjutils.so Make an entry for the Web host in the /etc/hosts file The Web server may not start if you do not have the fully qualified path name to your Web server host in the /etc/hosts file.
Configuring EAServer to accept Web server requests 3 Verify that the Connector.WebApp directive is set correctly in the conn_config file. For example: Connector.WebApp /* = http://hostname:8080 hostname is the machine name where EAServer is installed, and 8080 is the EAServer HTTP port number, and “/*” appears immediately after Connector.WebApp.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In Set the EAServer HTTP listener properties The HTTP listener properties that are related to the Web server redirector plugin are defined in the listener properties file for each EAServer HTTP listener that receives Web server requests: • com.sybase.jaguar.listener.http.connector_events – this is a required property and must be set to true so that the listener can properly process requests from the Web server.
Configuring HTTPS support for Web server plug-ins Connector.WebApp /*=http://jaghost1:8080 Note jaghost1 is not equivalent to jaghost.domain, where domain is the domain in which EAServer is hosted. Configuring HTTPS support for Web server plug-ins You can establish HTTPS connections between your Web server redirector and EAServer. You should be familiar with SSL and Security Manager before establishing HTTPS connections.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In Table 4-5: Subdirectories and files to copy from EAServer to Web server host Root directory $JAGUAR Subdirectories and files to copy • db/* • bin/setenv.sh • bin/sasecmgr • easmgr/* • java/lib/easclient.jar • java/lib/easj2ee.jar • java/classes/easri.jar $JAGUAR/lib or $JAGUAR/devlib • jdk/jdk1.3 • libjcc.so • libjctssecct.so • libjeas_mod.so • libjeaseapi_mod.so • libjeasproxy_mod.so • libjeasproxyeapi_mod.so • libjinsck_r.
Configuring HTTPS support for Web server plug-ins libjeasproxyeapi_mod.so • Files required for non-EAPI versions of the Apache Web server: libjeas_mod.so (for Apache version 1.3.26) or libjeas2_mod.so (for Apache version 2.0) libjeasproxy_mod.so In addition, for EAPI versions of Apache, modify the LoadModule directive in the httpd.conf file as follows: LoadModule easredirector_module libexec/libjeaseapi_mod.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In Table 4-6: HTTPS directives Default or valid value Directive name Connector.Https.pin Connector.Https.cacheSize <100> Connector.Https.SessLingerTime <28800> (8 hours) Connector.Https.SessShareCount <10> Connector.Https.
Configuring HTTPS support for Web server plug-ins Testing your HTTPS connections Once you have installed the required files and configured the Web server redirector plug-in to use HTTPS, you can test your connection to EAServer by sending HTTPS requests to a default HTTPS listener (for example, port 8081). Port 8081 is an HTTPS port that uses the Sample1 user certificate, which is signed by the Jaguar User Test CA.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In e From the Export Certificate wizard, select the format type for the exported certificate. Select Binary Encode X509 Certificate. Click Next. f Select Save to File and enter the full path name to a file that will contain the CA certificate. Do not add any extension to the file name. A .crt extension is automatically added to the exported certificate by Security Manager.
Adding FIPS and TLS support to the Web server redirector plug-ins 4 Mark the certificate trusted: a Select the CA folder b Select the certificate you just installed. c Select File | Certificate Info. The Certificate Information dialog appears. Use the scroll bar to view all of the information. d The Certificate dialog includes a Trusted Certificate check box. Mark the certificate as trusted. The certificate now appears in the Trusted folder. e Restart the Web server if it was running.
CHAPTER 4 • Installing and Configuring a Web Server Redirector Plug-In iPlanet 4.x Note This procedure updates existing Web server redirector plug-ins that were installed with an EAServer 5.x installation program. For new EAServer 5.5 installations, skip step 1 below and install all required files from the new EAServer 5.5 installation.
Adding FIPS and TLS support to the Web server redirector plug-ins 5 To start the installer from the command line, change to the location of the installation software 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 Install window appears. 6 Click Next in the Install window.
CHAPTER 4 Installing and Configuring a Web Server Redirector Plug-In where Plug-in name is the plug-in for which you are adding FIPS and TLS support. 11 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.
Adding FIPS and TLS support to the Web server redirector plug-ins Enabling FIPS and TLS for an Apache plug-in This section explains how to copy required files and configure the FIPSsupported redirector plug-in for Apache. It assumes you have already installed and configured the plug-in for non-FIPS use and updated this installation by following the instructions described in “Adding FIPS and TLS support to the Web server redirector plug-ins” on page 64. 1 Edit the httpd.
CHAPTER 4 • 3 Installing and Configuring a Web Server Redirector Plug-In libjutils.so To support FIPS and TLS, you must copy the following libraries from the EAServer/lib subdirectory that was created when you ran the EAServer 5.5 installation program into the WEB_SERVER_HOME/libexec directory: • libjctssecct_f140.so • libjsbgpks_r.so • libjeas2_mod_f140.so (Apache version 2.0 FIPS-supported library) • libsbgse2.so 4 Verify that the Web redirector plug-in still works for your HTTP connections.
Adding FIPS and TLS support to the Web server redirector plug-ins 2 Copy the required libraries. When you initially installed the non-FIPSsupported iPlanet Web server plug-ins, and used WEB_SERVER_HOME as the location of the Web server software, you copied the libraries listed in Table 4-4 on page 49 from your $JAGUAR/lib directory to the appropriate subdirectory. To support FIPS, you must also copy the following files to the same directory: • libjctssecct_f140.so • libjsbgpks_r.
CH A PTE R 5 Configuring Open Client and ODBC for EAServer This chapter describes how to set up Open Client and unixODBC driver to work with EAServer. Topic Overview Installing FreeTDS Page 71 72 Configuring ODBC Configuring Open Client 72 75 Overview The EAServer installation includes an option to install Open Client version 11.1.1 but it no longer includes the Merant (formerly Intersolv) DataDirect Connect ODBC Driver For Sybase Databases, Version 3.60.
Installing FreeTDS Installing FreeTDS Before you begin your installation, verify that unixODBC is not already installed on your machine. If it is, uninstall the existing version of unixODBC. ❖ Installing and configuring FreeTDS 1 Obtain FreeTDS at http://www.freetds.org, download and unzip the source code. Sybase recommends that you use the latest version of FreeTDS, which is fully compatible with ODBC 3.0. 2 Go to the FreeTDS source code directory; for example, /usr/tmp, and execute: .
CHAPTER 5 Configuring Open Client and ODBC for EAServer Creating a unixODBC connection cache When you create a unixODBC connection cache, you must define the “Server Name” with the ODBC data source name. You can obtain the data source name from the odbc.ini file, which is located in $JAGUAR/unixodbc. Using ODBC to connect to ASA Adaptive Server Anywhere is installed as part of both a typical and a full installation. The installation includes the ODBC driver to connect to ASA databases.
Configuring ODBC If isql shows a command prompt and not an error message, the connection is successful. Using ODBC to connect to ASE If you are using ASE as a data source, and FreeTDS as the database driver, you must configure the EAServer. 1 Add the data source information to $JAGUAR/freetds/etc/freetds.conf file. For example, to connect to the MySybase sample database, enter: [MySybase] host = ASE hostname port = 5000 tds version = 5.0 where: • host – is the server machine’s host name or IP address.
CHAPTER 5 Configuring Open Client and ODBC for EAServer Driver = SybaseASE Trace = yes Servername = ASE hostname Port = 5000 Database = tempdb uid = dba The name of the driver must be the same as that defined in odbcinst.ini. The server name is the database name without the extension. To verify whether the connection is correct, go to $JAGUAR/unixodbc/bin, and use the isql command-line tool to execute: .
Configuring Open Client Set required environment variables To set the environment variables, edit the user_setenv.sh setup script located in EAServer/bin. Create this file if it does not exist. Settings in this file are added to the server environment when it starts. After you run the setup script, set the SYBASE and LD_LIBRARY_PATH environment variables manually. 1 Set the SYBASE environment variable to the full path of the EAServer openclient subdirectory.
CHAPTER 5 Configuring Open Client and ODBC for EAServer • server_name – is the server you defined in the interfaces file. • user – is a valid user name for EAServer or the database server. • password – is the password that accompanies the user name. If isql shows a command prompt rather than an error message, the connection is successful.
Configuring Open Client 78 EAServer
Index Symbols C .odbc.ini file CLASSPATH environment variable 19 client runtime installation, defined 4 installing files 4 Java 5 CocoBase Enterprise software, installing 19 components, adding to EAServer 13 configuration files obj.conf 43 setenv.
Index DSQUERY environment variable adding support for 64 configuring support for Apache 68 configuring support for iPlanet 69 full installation, defined 4 72 E EAServer before you install 1 configuring Open Client for 71 connecting through a Web browser 18 documentation 2 features 4 installing 8 JDK, supported versions 3 listeners, default settings 12 products 1 reinstalling or adding components to 13 starting 16 system requirements 2 uninstalling 19 upgrading a license 13 what to install 4 EAServer Man
Index J jagadmin, default user name jagmgr command 17 O 17 JAGUAR environment variable 8 Jaguar Manager.
Index U listener ports 25 logging parameters 23 parameters, specifying on the command line 31 SilentInstall_Unix.sh script 23 SilentUninstall_Unix.sh script 33 SilentUninstall_Unix.txt configuration file 32 Sybase Central installation parameters 28 testing and running 22 testing the installation 33 troubleshooting and cleanup 33 uninstaller files 32 vpd.properties file, preserving 22 SilentInstall_Unix.sh script 23 SilentInstall_Unix.
Index FIPS, configuring for iPlanet 69 how it works 38 httpd.conf Apache sample configuration file 50 httpd.conf, Apache configuration file 50 HTTPS support 37 HttpSession object and failover 40 installing on your Web server 43, 49 iPlanet configuration file, editing 46 library names 44 load balancing 39 logging level, setting for Apache 54 logging level, setting for iPlanet 47 mapping iPlanet requests to EAServer 46 mapping requests to EAServer 52 obj.conf configuration file requirements 44 obj.
Index 84 EAServer
