Web Connector CommunicationThe Web Connector is initially tied to the NAS whose IP address is specified during the Web Connector installation. The Web Connector quickly learns load-balancing information and is no longer dependent on any particular NAS.
Reads the RegistryWhen the Web server starts, it reads the registry information for NAS. The Web Connector knows of all the Application Components (GUIDs) listed in the registry and any load-balancing information for those Application Components. UpdatesInitially, the Web Connector sends requests to the primary Netscape Application Server. When the Netscape Application Server receives the request, it evaluates the request against its own load- balancing table. If the request was not routed to the current best choice the NAS sends the request back to the Web server with the current information. Reroutes Requests to the Next NASThe Web Connector retains information in memory about which NAS is the best choice for each Application Component. It also retains the information of other past choices of NAS. If a Netscape Application Server becomes unavailable, the Web Connector determines this and sends the request to the next choice on its list. Default NASAn unidentified request is a request for a GUID that the Web Connector is unfamiliar with. If the Web Connector receives an unidentified request for an Application Component (GUID), it sends the request to the primary Netscape Application Server. That server updates the Web Connector with the correct server if it needs to move the request to another Netscape Application Server. For first-time execution of an Application Component, the Web Connector always uses the primary NAS. The term primary refers to the default NAS IP address given during installation. This is not the primary used by the cluster nor is a cluster install needed to use the Web Connector.
|