Table 12-1 describes the client properties that configure connections that must be opened through a Web proxy. You must set these properties in addition to any properties that you would set to connect directly to EAServer.
C++/ActiveX/ PowerBuilder property |
CORBA property |
EJB property |
Specifies |
---|---|---|---|
|
|
|
Specifies the host name or IP address of the Web proxy server. Does not apply to Java applets running in a Web browser, which use the proxy address specified by the browser’s proxy configuration. There is no default for this property, and you must specify both the host name and port number properties. |
|
|
|
Specifies the port number at which the Web proxy server accepts connections. Does not apply to Java applets running in a Web browser, which use the proxy address specified by the browser’s proxy configuration. There is no default for this property, and you must specify both the host name and port properties. |
|
|
|
By default, the client ORB attempts to open IIOP connections, then attempts an HTTP-tunnelled connection if plain IIOP fails. Since Web proxy connections require HTTP tunnelling, set this to true to eliminate the performance overhead of trying plain IIOP connections before trying HTTP-tunnelled IIOP. |
|
|
|
An optional setting to specify what extra information is appended to the header of each HTTP packet sent to the Web proxy server. There is no need to set this property unless your HTTP proxy server has special protocol requirements. By default, the following line is appended to each packet: User-agent: Jaguar/major.minor where major and minor are the major and minor version numbers of your EAServer client software, respectively. You can set this property to specify text to be included at the end of each HTTP header. If multiple lines are included in the setting, they must be separated by carriage return and line feed characters. If the setting does not include a “User-agent: ” line, then the default setting above is included in the HTTP header. |
N/A. |
|
|
Use the Java Secure Sockets Extension (JSSE) classes for secure HTTP tunnelled (HTTPS protocol) connections. JSSE provides an alternative to the built-in SSL implementations when secure connections are needed from an applet running in a Web browser. Additional configuration may be required to use this option. See “Using Java Secure Socket Extension classes” for more information. |
Copyright © 2005. Sybase Inc. All rights reserved. |