Configuring servers

EAServer provides property tabs and three wizards that step you through the process of configuring and tuning a server. You can use property tabs, the wizards, or both, to configure and tune a server. The wizards step you through the configuration process, and the property tabs allow you to select which properties you want to configure in the order you choose. The wizards and property tabs modify the same information. The Advanced tab displays all server settings.

Configuring a server using the Server Configuration wizard

The Server Configuration wizard steps you through the basic configuration required to establish a server.

1. From within EAServer Manager, display the list of installed servers by expanding the Servers folder.

2. Highlight the server you want to configure.

3. Select File | Server Configuration Wizard.

Tuning the server using the Performance Tuning wizard

The Performance Tuning wizard fine-tunes your server for optimum performance.

1. From within EAServer Manager, display the list of installed servers by expanding the Servers folder.

2. Highlight the server you want to configure.

3. Select File | Performance Tuning Wizard.

Configuring debug settings using the Server Debug Settings wizard

The Server Debug Settings wizard defines additional settings for debugging server and performance problems.

1. From within EAServer Manager, display the list of installed servers by expanding the Servers folder.

2. Highlight the server you want to configure.

3. Select File | Server Debug Settings Wizard.

Configuring or modifying server properties

Select each tab as required to define various aspects of server behavior.

1. From within EAServer Manager, display the list of installed servers by expanding the Servers folder.

2. Highlight the server you want to configure.

3. Select File | Properties. The Server Properties dialog box displays, which contains these tabs:

   • General – define general individual server properties.

   • Java VM – control the execution of Java in the server.

   • HTTP Config – determine browser accessibility.

   • Transactions – determine the transaction coordinator for components that participate in EAServer transactions.

   • Security – see “Administration password and OS authentication” for security options accessible from this tab.

   • Resources – define the maximum number of client connections.

   • Log/Trace – set logging and trace options.

   • Handlers – if hosting an Open Server application, allows you to specify Open Server event handler function names.

   • Naming Service – set the server’s naming service options. See Chapter 5, “Naming Services” for additional information.

   • Servlets – disable servlet execution in EAServer and configure additional properties to control the execution of servlets.

   • PowerDynamo – enable hosting of PowerDynamo Web sites in EAServer.

   • Hot Standby – enable hot standby and define the master and backup servers.

   • JAXP Support – configure Java API for XML parsing support.

   • Java Classes – specify classes to include in the server’s runtime JAR file.

   • Java Debug – specify the port number for remote debugger connections.

   • Static Page Caching – enable caching for static pages.

   • HTTP Custom Response Header – define custom headers for HTTP responses.

   • HTTP Directory Browsing – enable HTTP browsing for Web application and non-Web application directories.

   • Components – configure component execution.

   • Advanced – edit server property settings in their raw format, that is, as they are stored in the configuration repository.

If you modify any property, click OK in the Server Properties dialog box to save your changes, or click Cancel to discard the changes.

When you modify server properties, you must refresh the server for the changes to take effect. To refresh the server, highlight the server icon and select File | Refresh.

General

Table 3-1 describes the general properties that you can configure for individual servers.

Java VM

The settings on this tab control a variety of parameters that affect the execution of Java in the server. Table 3-2 lists the settings. If you change these settings, you must restart the server before the changes take effect.

HTTP Config

Clients can access EAServer and retrieve HTML pages using a Web browser. You can customize certain aspects of your server’s HTTP behavior by modifying the HTTP configuration properties listed in Table 3-3.

Configuring redirection addresses when using a proxy server

You may need to configure redirection addresses if clients connect to your server through a proxy or firewall, or if you want the domain name set in cookies that are returned to the client.

Some HTTP requests may cause EAServer to redirect the client to a different page. For example, when a client requests a page that has access constraints, the user may be redirected to the login page. The HTTP redirect response code contains a fully qualified HTTP or HTTPS URL, including the protocol, host, and port. When clients connect through a proxy server, the redirection URL must be modified to specify the proxy host address rather than the EAServer host address. Some proxies do not filter any packets in the base protocol. A hardware SSL engine is one such example. When using these proxies, you must configure the properties below to ensure that the proxy address and protocol appear in the redirection URL, rather than the address used for the connection from the proxy to EAServer:

• Domain Name If this property is set, EAServer composes redirection URLs using the specified host or domain name rather than the host name set in the EAServer listener. The domain name is also set for cookies that are returned to the client. This allows sharing of cookie information across multiple servers in your domain. If the domain name is not set for the cookie, the information is available only to applications running on the server where it was created.

  There are two ways to set the property:

  • If you specify a domain name beginning with a dot, the redirection host is “www” at the specified domain. For example, if you enter .foo.com and EAServer runs on host abc, the redirection host is www.foo.com, rather than abc.foo.com. Use this format if your proxy or firewall server runs with host name “www.”

  • If you specify a value that does not begin with a dot, the redirection host is the supplied value, with no domain name appended. In this case, enter either an IP address, or the entire address, including the domain name. For example, search.foo.com or 10.22.241.101. Use the full name if clients do not connect through a proxy, or connect through a proxy with a host name other than “www.”

  When a domain name is specified, the address used in the location header for redirect response packets is composed as follows:

  protocol://address:port
  

  where:

  • protocol is the value of the Proxy Protocol setting, or if not set, the protocol of the original request from the proxy to EAServer, which may not match the protocol used by the base client’s connection to the proxy.

  • address is the value of the Domain Name setting if the setting does not begin with a dot; otherwise, address is the Domain Name setting with “www” inserted at the beginning.

  • port, for HTTP URLs, is the value of the Proxy HTTP Port setting, or 80 if not set. For HTTPS URLs, port is the value of the Proxy HTTPS Port setting, or 443 if not set.

  To override the Domain Name for Web applications, you can set the com.sybase.jaguar.webapplication.httpdomain.override property to true. See Web application properties for a description of this property.

• Proxy Protocol When a domain name is specified, the protocol for redirection URLs. Specify HTTP or HTTPS. If not set, the protocol matches that of the request sent from the proxy to EAServer. This may not match the original protocol. For example, the client may use HTTPS to connect to the proxy, which uses HTTP to connect to EAServer. In this case, you must set the Proxy Protocol to HTTPS. Otherwise, the client Web browser may refuse to connect to the redirected URL because of the switch from HTTPS to HTTP.

• Proxy HTTP Port When a domain name is specified, this setting specifies the port to embed in HTTP redirection URLs. The default is 80. When a domain name is not specified, this setting is ignored.

• Proxy HTTPS Port When a domain name is specified, this setting specifies the port to embed in HTTPS redirection URLs. The default is 443. When a domain name is not specified, this setting is ignored.

HTTP logging and statistics

EAServer maintains three HTTP log files and a statistics data file that allow you to monitor HTTP events. The file names are prepended with the server name. For example, if you create a server named Test_server, error messages for that server are directed to the Test_serverhttperror.log file. By default, the log files are located in the EAServer bin subdirectory (or devbin if you are running the debug server version).

• <server_name>httprequest.log – records HTTP request log information about each HTTP request.

• <server_name>httperror.log – logs HTTP errors, such as a request for an HTML file that does not exist.

• <server_name>httpservlet.log – logs HTTP servlet requests.

• <server_name>httpstat.dat – records HTTP statistics.

For information on viewing these files, see “Using the File Viewer”.

Transactions

This section describes the transaction coordinator models that are available. All components installed in one instance of EAServer share the same transaction coordinator.

EAServer transaction coordinator models are:

• Java Transaction Service (JTS) For UNIX or Windows users, this option complies with the JTS and the Object Transaction Service (OTS) and X/Open Architecture (XA) standards. The JTS transaction coordinator integrates the functionality of the shared connection, OTS/XA, and JTS/JTA transaction modes. The JTS transaction coordinator uses two-phase commit to coordinate transactions among multiple databases.

• Microsoft Distributed Transaction Coordinator (DTC) DTC uses two-phase commit to coordinate transactions among multiple databases. DTC is available on Windows platforms as part of Microsoft SQL Server 6.5 or later.

To set the transaction coordinator for your server, select the transaction model from the server’s Transactions tab in the Server Properties dialog box.

For detailed information about components and transactions, see Chapter 2, “Understanding Transactions and Component Lifecycles,” in the EAServer Programmer’s Guide.

Resources

The Resources tab allows you to limit the number of concurrent client sessions and contains configurable properties used by Open Server applications. Table 3-4 describes the server resource properties.

Log/Trace

Tracing provides information about activities carried out by your application. Trace output is sent to the server’s log file. To establish the level of detail for logging and tracing, select the Log/Trace tab. Table 3-5 describes the logging and trace properties.

For information on viewing the log file, see “Using the File Viewer”.

Handlers

This tab allows you to specify Open Server event handlers when you have configured EAServer to support Open Server client connections. This feature allows you to run legacy Sybase Open Server applications in EAServer. For more information, see Appendix B, “Migrating Open Server Applications to EAServer,” in the EAServer Programmer’s Guide. These handlers are called only for events that are generated by clients that connect to a listener that is configured to accept Open Server requests.

Specifying an event handler

1. Select the Handlers tab.

2. Enter the DLL or shared library name and the function name of the specific event handler being called, separated by a colon.

   The following example illustrates an entry for a connect event handler:

   Platform	Entry
   Solaris, AIX, Digital UNIX, and LINUX	libsamp.so:debug_connect
   HP-UX	libsamp.sl:debug_connect
   Windows	libsamp.dll:debug_connect

   where libsamp is the DLL or shared library name and debug_connect is the function called whenever a connect event handler is called.

   Table 3-6 summarizes the types of event handlers that you can install. For information on coding event handlers, see Appendix B, “Migrating Open Server Applications to EAServer,” in the EAServer Programmer’s Guide.

   Table 3-6: Individual server event handlers

   Event handler	Called
   Connect	Each time a client connects to EAServer.
   Disconnect	When the client disconnects from EAServer.
   Error	When a server processing error occurs.
   CS Error	When a CS-Library error occurs
   CT Error	When a Client-Library error occurs
   Open Server Error	When a Open Server error occurs.
   Initialization	Before starting a server.
   Start	When a request to start the server is made.
   Stop	When a request to stop the server is made.
   Language	When a client sends a language request, such as a SQL statement.
   RPC	When a client issues a remote procedure call.
   Attention	When an attention has been received. An attention is an immediate event; EAServer services the attention as soon as it occurs, rather than adding it to the client’s event queue.
   Cursor	When a client sends a cursor request.
   Dynamic	When a client sends a dynamic SQL request.
   Message	When the client sends a message.
   Option	When a client sends an option command.
   Bulk	When a client issues a bulk copy request.

Naming Service

Select the Naming Service tab in the Server Properties dialog box to set the server’s naming service options. You can use this property sheet to configure a server to be a name server, or to point to another server as its name server.

For general information about naming services, see Chapter 5, “Naming Services.”

Initial Context – enter the server’s default name context. The name server binds any object implementations on the server to the server’s initial name context.

If you use an EAServer as a name server, the name context can be a compound name with each organization level separated with a forward slash (“/”); for example, /us/sybase/finance.

If you use an external LDAP server to provide persistent storage, the initial context must match the schema used by the LDAP server. For example, c=us,o=sybase,ou=finance.

Naming server options

Use these options to specify whether the EAServer instance is also a name server, or whether it uses another EAServer instance as its name server.

• Click Enable as a Name Server to configure the server as a name server. If you select this option, you can then also set the Name Server Strategy options described below.

• If EAServer uses another EAServer instance as its name server, unselect Enable as a Name Server. Enter the URL for the EAServer instance acting as the name server; for example, iiop://myhost:9000.

Naming server strategy

If you enabled the EAServer instance to be a name server, indicate whether the server provides transient or persistent object name storage. By itself, an EAServer name server provides transient storage. However, you can add persistent storage capabilities to EAServer by using an external naming service, such as an LDAP name server.

If you enable persistent storage, enter the following information:

• The URL of the LDAP name server

• A manager DN (distinguished name) for the LDAP server

• The manager DN password

The manager DN provides exclusive access to all objects in the LDAP server database in order to bind and update the objects on the name server. The manager DN and its password are part of the LDAP server configuration properties, set by the server administrator. See your LDAP server documentation for complete information.

Servlets

On the Servlet tab in the Server Properties window, you can disable servlet execution in EAServer and configure additional properties to control the execution of servlets.

See Chapter 22, “Creating Java Servlets,” in the EAServer Programmer’s Guide for complete information about developing and configuring servlets.

PowerDynamo

This section discusses how to configure EAServer to host your PowerDynamo Web sites and provide access to those sites from a browser. Access to PowerDynamo Web sites is disabled by default.

Hosting PowerDynamo Web sites in EAServer

1. Install PowerDynamo version 3.6.1 on your Windows or UNIX machine where EAServer is installed.

2. Update your EAServer’s environment to include the PowerDynamo DLL and class files. Depending on your platform, perform the following:

   On UNIX, make the following modifications to your $JAGUAR/bin/setenv.sh file, then source the file:

   • Define a PDYNAMO environment variable and set it to the root of your PowerDynamo installation. This environment variable is required on UNIX machines.

   • Define a JAGUARCLASSES environment variable and set it to your client JAR file, $JAGUAR/client/easclient.jar.

   • Add $PDYNAMO/lib to your LD_LIBRARY_PATH.

   • Add $PDYNAMO/class03 to your CLASSPATH.

   On Windows, depending on the virtual machine you are using, modify the %JAGUAR%\bin\user_setenv.bat file, or create this file if it does not exist. Make the following edits:

   • Add %PDYNAMO%\win32 to your PATH.

   • Add %PDYNAMO%\class03 to your CLASSPATH, where %PDYNAMO% is the root of your PowerDynamo installation. You do not need to define a PDYNAMO environment variable.

3. Start EAServer and connect to it from EAServer Manager. To enable PowerDynamo support:

   1. From EAServer Manager, open the Servers folder.

   2. Highlight the server you want to configure.

   3. Select File | Properties.

   4. Select the PowerDynamo tab.

   5. Click Enable PowerDynamo Execution.

   6. If you have both a PowerDynamo mapping and a servlet alias with the same URL, select Dynamo or Servlets from the Priority of EAServer HTTP Services list. This determines whether the PowerDynamo Web site or servlet is served to the client.

   7. Click OK.

4. Configure your machine so that your Web sites can connect to and retrieve information from databases that they use. For example, on Windows, if you load a Web site that accesses data from a SQL Anywhere database, you must include the SQL Anywhere DLLs in your PATH and set up the ODBC data source properly. See your database software instructions and the PowerDynamo User’s Guide for detailed information.

You can now access a PowerDynamo Web site by entering into your browser, the EAServer HTTP address followed by a PowerDynamo Web site. For example:

http://EAServer_server_host:8080/mapped_url_name/file_name

This example connects your browser to:

• EAServer’s HTTP port 8080 on the host machine identified by EAServer_server_host.

• The mapped_url_name is the mapping you supply for a PowerDynamo Web site in the PowerDynamo | Utilities | Configuration | Mappings folder.

• file_name is the file you are accessing from the mapped PowerDynamo Web site.

Hot Standby

If you have two EAServer installations, you can enable hot standby, which allows you to designate one of the servers as a backup server that accepts client connection requests in case the master server fails. The master server processes client requests. The backup server starts in “Admin” mode and does not accept client requests. If the master server fails or is unreachable, the backup server sets itself to “Ready” mode and accepts client requests. Once the master server is up and accepting requests, the backup server enters “Admin” mode, refusing connections from clients.

See Chapter 7, “Load Balancing, Failover, and Component Availability” for information about component failover.

Enabling hot standby in EAServer

1. You must first enable the two hot standby servers as name servers. Select the Naming Service tab and click Enable as a Name Server to configure EAServer as a name server.

2. Select the Hot Standby tab and click the Enable Hot Standby check box.

3. Enter the Master Server URL using the format iiop://hostname:port. For example, iiop://EAServer_master:9095.

4. Enter the Backup Server URL using the format iiop://hostname:port. For example, iiop://EAServer_backup:10000.

   The master and backup servers must be valid IIOP or IIOPS URLs. You can have only one master and one backup server defined and one of them, but not both, must be defined on the local server.

5. Synchronize the servers using the master as the primary server—see “Synchronization”.

You can verify the settings of hot standby by checking these properties on the Advanced tab:

• com.sybase.jaguar.server.CosNaming.nameserver must be set to true for both the master and backup servers.

• com.sybase.jaguar.server.hotstandby is set to true if hot standby is enabled.

• com.sybase.jaguar.server.hotstandby.master is the URL of the hot standby master server.

• com.sybase.jaguar.server.hotstandby.backup is the URL of the hot standby backup server.

JAXP Support

The JAXP Support tab allows you to configure the default Java XML parsers for components and Web applications running on the server. See Chapter 36, “Configuring Java XML Parser Support,” in the EAServer Programmer’s Guide for more information.

Java Classes

The Java Classes tab allows you to configure the set of classes to be custom-loaded at the server level. For more information, see “Custom class lists for packages, applications, or servers” in Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide

Java Debug

This tab configures the server’s remote debugging interface with the settings listed in Table 3-7. Use the interface that your remote debugging tools support.

After changing these settings, restart the server in debug mode for the change to take effect. For information on debugging Java components, see the EAServer Programmer’s Guide.

Static Page Caching

You can configure EAServer to cache HTML and other static pages, which improves the speed at which the page contents are served. When a client requests an HTML page, EAServer checks the cache for a suitable entry. If the cache entry exists, the cached page is sent to the client. If the cache entry is not found, EAServer loads the page from disk, sends it to the client, then saves the page contents in the cache. Table 3-8 describes the static page caching options.

To cache dynamic content such as JSP or servlet responses, use one of the other caching options described in Chapter 5, “Web Application Tuning,” in the EAServer Performance and Tuning Guide.

(<WebAppName>[/<dir>], 
[<file_type>], [<file_type>], ...),
(<WebAppName>[/dir>], ...), ...

(Vacation/images, 
 *.gif, *.jpg),
(Vacation/archives, *.*)

(Vacation)

(<dir>, [<file_type>], [<file_type>],
...), (<dir>, [<file_type>], ...), ...

(images, *.*)

(images)

When you modify static page cache properties, you must refresh the cache for the changes to take effect. To refresh the cache, highlight the server icon and select File | Refresh Static Cache.

HTTP Custom Response Header

The HTTP Custom Response Header tab allows you to define custom response header filters for HTTP responses at the server level. You can customize header information such as the server name or the expiration date of the response. By default, a server-level custom response header filter applies to all server resources. You can apply the filter to specific resources by setting the value of the com.sybase.jaguar.server.filter-mapping property to the resource URLs.

You can also define custom headers at the Web application level by installing the default filter com.sybase.jaguar.servlet.AddHeadersFilter in a Web application. Chapter 23, “Using Filters and Event Listeners,” in the EAServer Programmer’s Guide describes how to do this. When both server and Web application custom headers exist, the Web application custom header takes precedence.

Defining custom headers

Enter a custom header as property name/value pairs.

1. Click Add to display the New Property dialog box.

2. Enter a property name, property value, and (optionally) a description.

3. Select the property type, either String or Date. If you select Date, specify when the header expires. Enter a period of time, and select either From Now or Ago. For example, if you want the header to expire a month from now, enter 1 in the Months field, and select From Now.

To edit a header property, highlight the property and click Modify. Edit the property name or value, and click OK.

To delete a header property, highlight the property and click Delete.

For more information on filters and programming customized responses, see the Java Web page.

HTTP Directory Browsing

The HTTP Directory Browsing tab allows you to enable HTTP directory browsing and define which directories can be browsed; these directories can be inside or outside Web applications.

You cannot enable directory browsing for the special Web application directories WEB-INF and META-INF. Also, if you enable browsing for a directory that contains welcome files, anyone browsing the directory will see only the welcome files.

Enabling directory browsing

1. Click Enable Directory Browsing. This enables browsing for the directories you have added to your list.

2. Click Add. An entry is added to the list with default settings. Modify the entry to define the directory that can be browsed:

   • Web Application Name – click the Web application name. A drop-down list displays a list of installed Web applications from which to choose. Or use Default to define non-Web application directories.

   • Directory Name – enter the directory name that can be browsed.

     Use forward slashes when defining a directory name.

   • Grant Access to Subdirectories – either true or false. If true, grants access to all subdirectories of the directories that you specify.

3. To allow browsing of multiple top-level directories in the same Web application, repeat the previous steps to create an entry for each directory. To delete a directory from the list, highlight the directory and click Delete.

4. Restart the server for the changes to take effect.

You can verify the settings of HTTP directory browsing by checking these properties on the Advanced tab:

• com.sybase.jaguar.server.http.dirbrowseenable must be set to true to enable directory browsing. If false, the following two properties are ignored.

• com.sybase.jaguar.server.http.dirbrowseinclude defines the list of non-Web application browsable directories.

• com.sybase.jaguar.server.http.dirbrowsewebappinclude defines the list of Web application browsable directories.

Components

Properties on this tab configure component execution and include:

• LWC Enables the EAServer lightweight container (LWC) for intercomponent EJB invocations or calls to EJBs from servlets and JSPs hosted in the same server. For more information, see “Lightweight container” in the EAServer Performance and Tuning Guide.

• Skeleton Support If LWC is enabled, the Skeleton Support option enables LWC calls to EJB components from servlets and JSPs hosted in the same server. Such calls are not supported unless this option is set.

• External Server Request Timeout For components that run in an external server, specifies the default external request timeout. That is, how long, in seconds, to wait for a response from the external server before returning an error to the client. If not set, the default is 60 seconds.

• External Server Start Timeout For components that run in an external server, specifies the default server start timeout. That is, how long, in seconds, to wait for the external server to start if it is not already running. EAServer returns an error to the client if the external server does not start in the specified time. If not set, the default is 60 seconds.

Advanced

For advanced users only. Select this tab to edit server property settings in the EAServer configuration repository. Properties are listed in Appendix B, “Repository Properties Reference.” You can use this tab to edit any property prefixed with “com.sybase.jaguar.server.” Most server properties can be configured on other tabs in the Server Properties dialog box, except the following:

• com.sybase.jaguar.server.authservice

• com.sybase.jaguar.server.authorization.service

• com.sybase.jaguar.server.authorization.permcachetimeout

• com.sybase.jaguar.server.bindrefresh

• com.sybase.jaguar.server.filter-mapping

• com.sybase.jaguar.server.http.disablechunkedtransfer

• com.sybase.jaguar.server.http.force.close

• com.sybase.jaguar.server.jvm.nojit

• com.sybase.jaguar.server.jvm.options

• com.sybase.jaguar.server.jvm.verbose

• com.sybase.jaguar.server.jvm.verboseGC

• com.sybase.jaguar.server.masp.zero-success

• com.sybase.jaguar.server.roleservice

• com.sybase.jaguar.server.servlet.error-page

• com.sybase.jaguar.server.timeout

• com.sybase.jaguar.server.tx_timeout

• Environment variable properties

Copyright © 2005. Sybase Inc. All rights reserved.