Running servers as Windows services The procedure that describes how to install EAServer as a Windows service incorrectly states that you set the Java runtime version on the Server Properties | Java VM tab. This tab no longer exists. You set the Java version on the command line, as correctly described in the last step of this procedure.
Server Properties: Handlers In the Server Properties dialog box, the Handlers tab allows you to specify event handlers that support the Open Server™ event-based programming model. These handlers are called only for events triggered by clients that connect to an Open Server listener. For more information, see Appendix B, “Migrating Open Server Applications to EAServer,” in the EAServer Programmer’s Guide.
Server Properties: HTTP Config The properties below should be set to control the URL that is returned when clients connect to EAServer through a proxy server that does not filter and modify the location header in HTTP redirect response packets. A fully qualified URL must be returned in HTTP redirect responses, including the protocol, host, and port. When a client connects to EAServer through a proxy server and requests a page that requires redirection, the redirection URL must include the proxy server address and not the EAServer address. Some proxies, such as the EAServer redirector plug-in, automatically filter and modify the redirection URL. Some proxies do not; for example, hardware SSL engines often do not filter any packets in the base protocol. In these cases, you must configure the following properties 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 to specify a domain name, the host name
in redirection URLs will be “www” rather than
the host name set in the EAServer listener. For example, if the
Domain Name is specified as .foo.com and
EAServer runs on host abc, the redirection host would be www.foo.com
rather than abc.foo.com. If specifying a domain name, include the
leading dot, for example .foo.com rather
than foo.com. If using jagtool,
set this property as com.sybase.jaguar.server.http.domainname.
When a domain name is specified, the address used in the location header for redirect response packets is composed as follows:
protocol://wwwdomain: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.
domain – is the value of the Domain Name setting.
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.
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. If using jagtool, set this property as com.sybase.jaguar.server.http.proxyprotocol.
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. If using jagtool, set this property as com.sybase.jaguar.server.http.httpport.
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. If using jagtool, set this property as com.sybase.jaguar.server.http.httpsport.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
