Return to Start Page
iiThis section describes the ILS process flow. Here you can see how the hardware and software components work together. The section includes an overview of the process, detailed flow descriptions, and a preview of how you administer the ILS processes.
ILS acts as the server in a client-server network system. As a server, it responds to client requests for information. The requests are typically carried by either HTTP or LDAP protocol. When a client application requests information using HTTP, ILS use the Active Server Pages framework to respond with HTML pages that can be viewed with a standard Web browser. When a client application makes an ILS LDAP request, ILS generates LDAP responses that contain directory information or error codes. ILS can also provide directory information to ULP-based clients.
Queries from the LDAP interface are passed through the ILS directory DLL to the ILSDB DLL. Queries from the HTTP interface, on the other hand, are handled by an ActiveX server component that reformulates the query for the ILS directory DLL. For HTTP queries, an ASP script on the server composes the query results into an HTML page, which is then returned to the user.
iThe ILS Server has the following key processes:
Note The ULP interface is provided as a migration strategy for NetMeeting clients and will be phased out in the future. Dynamic directory clients are strongly encouraged to use the LDAP interface.
The following diagram illustrates how ILS handles a query from a client. Note that ILS/HTTP and ILS/LDAP are both running within the same instance of IIS.
In the following section, the identifiers (H1, H2, L1, L2, U1, U2, and so on) correspond to process steps in the preceding diagram.
When a directory request is received from a Web browser client, the following process takes place:
When a directory request comes from an Internet client application, such as Microsoft NetMeeting or Intel Internet Phone, the following process takes place:
The ILS implementation of the LDAP protocol is based on RFC 1777. The following restrictions are made for performance and scaling reasons:
When a directory request comes from a third-party Internet client application, such as the Microsoft NetMeeting client, the following process takes place:
ILS includes an administrative framework for operations. This framework describes how to set up, monitor, and administer the system. This section summarizes the operations strategy.
If Microsoft Membership System will be used for authentication, then each server must have the Membership Broker component installed on it. Also, a Membership Agent that is used by the Broker must be installed at the Membership System Backend site. For information about setting up Microsoft Membership System, see the Membership System documentation.
For more information about setting up ILS, see Chapter 3, "Setting Up ILS."
ILS can be administered from the command prompt, through Internet Service Manager dialog boxes, or remotely through a Web page.
For more information about managing ILS, see Chapter 4, "Operating ILS."
ILS uses Windows NT Performance Monitor counters to give feedback on the current operating status of the system.
For more information about counters, see Chapter 5 in the Internet Locator Server Operations Reference.
ILS also makes use of Windows NT events by writing to the Windows NT event log.
For descriptions of Windows NT events, see Chapter 2 in the Internet Locator Server Operations Reference.
Return to Start Page
© 1996-1997 Microsoft Corporation. All rights reserved.