web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Microsoft Internet Information Services (IIS) web server By default, all configuration.xml files are located in the following directory: /var/domains//configurations// To add web container ENV variables for a Partition Managed Object, use the env-vars element and env-var sub-element and the following syntax: ...> ... where is the ENV variable name and is the value you want to set for the named ENV variable. For example: ...> ... For more information about the element, go to BDOC Reference. Microsoft Internet Information Services (IIS) web server The Microsoft Internet Information Services (IIS) web server is not included with any BES product offerings. However, BES does include the IIOP redirector which provides connectivity from the Borland Tomcat-based web container to the IIS web server, and from the IIS web server to a CORBA server. The IIOP redirector is supported for the following IIS versions: ■ Microsoft Windows 2000/IIS version 5.0 ■ Microsoft Windows XP/IIS version 5.1 ■ Microsoft Windows 2003/IIS version 6.0 For more information, go to Chapter 5, “Web server to web container connectivity.” IIS/IIOP redirector directory structure After installing any of the BES products, by default, the following IIS/IIOP redirectorspecific directory structure appears in: /etc/iisredir2/ Table 4.4 IIS/IIOP redirector directories IIS/IIOP redirector-specific directory name conf logs Description Contains all configuration files. Contains all log files. Chapter 4: Web components 37
Smart Agent implementation Smart Agent implementation The Smart Agent is a service that helps in locating and mapping client programs and object implementation. The Smart Agent is automatically started with default properties. For information on configuring the Smart Agent, go to the VisiBroker for Java Developer's Guide. The Smart Agent is a dynamic, distributed directory service that provides facilities for both the client programs and object implementation. The Smart Agent maps client programs to the appropriate object implementation by correlating the object or service name used by the client program to bind to an object implementation. The object implementation is an object reference provided by a server, such as the Borland web container. The Smart Agent must be started on at least one host within your local network. When your client program invokes an object (using the bind method), the Smart Agent is automatically consulted. The Smart Agent locates the specified object implementation so that a connection can be established between the client and the object implementation. The communication with the Smart Agent is transparent to the client program. The following are examples of how the Smart Agent is used by the BES web components: ■ “Connecting an Apache web server to a Borland web container” on page 38. ■ “Connecting Borland web containers to Java Session Service” on page 39. Connecting an Apache web server to a Borland web container As a distributed directory service, the Smart Agent registers an active ID of an object reference for the client programs to use. The following diagram shows the interaction between the client program binding to an object through the Smart Agent. In this example, the Apache web server is acting as a client and the Borland web container is acting as a server (and provides the object reference). 38 BES Developer’s Guide
- Page 1 and 2: Developer’s Guide Enterprise Serv
- Page 3 and 4: Contents Chapter 1 Introduction to
- Page 5 and 6: Entity beans . . . . . . . . . . .
- Page 7 and 8: Chapter 23 Using JMS 209 Configurin
- Page 9 and 10: Entity Bean Properties (applicable
- Page 11 and 12: Figures 0.1 Borland Enterprise Serv
- Page 13 and 14: BES Products and Editions overview
- Page 15 and 16: Documentation conventions Important
- Page 17 and 18: Contacting Borland support World Wi
- Page 19 and 20: BES services overview Figure 0.1 Bo
- Page 21 and 22: The Partition and its services ■
- Page 23 and 24: Borland Enterprise Server and J2EE
- Page 25 and 26: 14 BES Developer’s Guide
- Page 27 and 28: Creating Partitions Creating Partit
- Page 29 and 30: Running Partitions Table 3.1 Option
- Page 31 and 32: Configuring Partitions You can also
- Page 33 and 34: JMX support in Partitions ■ ■ A
- Page 35 and 36: JMX support in Partitions Figure 3.
- Page 37 and 38: Thread pools Partition properties r
- Page 39 and 40: 28 BES Developer’s Guide
- Page 41 and 42: Apache web server implementation Fo
- Page 43 and 44: Borland web container implementatio
- Page 45 and 46: Borland web container implementatio
- Page 47: Borland web container implementatio
- Page 51 and 52: 40 BES Developer’s Guide
- Page 53 and 54: Apache web server to Borland web co
- Page 55 and 56: Apache web server to Borland web co
- Page 57 and 58: Apache web server to Borland web co
- Page 59 and 60: Large data transfer Downloading lar
- Page 61 and 62: Large data transfer Uploading large
- Page 63 and 64: IIS web server to Borland web conta
- Page 65 and 66: IIS web server to Borland web conta
- Page 67 and 68: IIS web server to Borland web conta
- Page 69 and 70: Session management with JSS If an i
- Page 71 and 72: Managing and configuring the JSS Co
- Page 73 and 74: The Borland IIOP connector BES supp
- Page 75 and 76: Setting up your web container with
- Page 77 and 78: 66 BES Developer’s Guide
- Page 79 and 80: Web-enabling your CORBA server Impo
- Page 81 and 82: Configuring your Apache web server
- Page 83 and 84: Configuring your Apache web server
- Page 85 and 86: Web Services and Partitions ■ ■
- Page 87 and 88: Web Service providers Java:RPC prov
- Page 89 and 90: How Borland Web Services work
- Page 91 and 92: Packaging Web Service Application A
- Page 93 and 94: Tools Overview Java2WSDL tool Note
- Page 95 and 96: 84 BES Developer’s Guide
- Page 97 and 98: Client view of an enterprise bean L
Smart Agent implementation<br />
Smart Agent implementation<br />
The Smart Agent is a service that helps in locating and mapping client programs and<br />
object implementation. The Smart Agent is automatically started with default<br />
properties. For information on configuring the Smart Agent, go to the VisiBroker for<br />
Java Developer's Guide.<br />
The Smart Agent is a dynamic, distributed directory service that provides facilities for<br />
both the client programs and object implementation. The Smart Agent maps client<br />
programs to the appropriate object implementation by correlating the object or service<br />
name used by the client program to bind to an object implementation. The object<br />
implementation is an object reference provided by a <strong>server</strong>, such as the <strong>Borland</strong> <strong>web</strong><br />
container.<br />
The Smart Agent must be started on at least one host within your local network. When<br />
your client program invokes an object (using the bind method), the Smart Agent is<br />
automatically consulted. The Smart Agent locates the specified object implementation<br />
so that a connection can be established between the client and the object<br />
implementation. The communication with the Smart Agent is transparent to the client<br />
program.<br />
The following are examples of how the Smart Agent is used by the BES <strong>web</strong><br />
components:<br />
■<br />
“Connecting an Apache <strong>web</strong> <strong>server</strong> to a <strong>Borland</strong> <strong>web</strong> container” on page 38.<br />
■<br />
“Connecting <strong>Borland</strong> <strong>web</strong> containers to Java Session Service” on page 39.<br />
Connecting an Apache <strong>web</strong> <strong>server</strong> to a <strong>Borland</strong> <strong>web</strong> container<br />
As a distributed directory service, the Smart Agent registers an active ID of an object<br />
reference for the client programs to use. The following diagram shows the interaction<br />
between the client program binding to an object through the Smart Agent. In this<br />
example, the Apache <strong>web</strong> <strong>server</strong> is acting as a client and the <strong>Borland</strong> <strong>web</strong> container is<br />
acting as a <strong>server</strong> (and provides the object reference).<br />
38 BES Developer’s Guide
Change language