Architecture of Enterprise Service Portals

Figure 16 shows the basic elements and communication protocols of an enterprise service portal.

Figure 16: Elements and Communication Protocols for an Enterprise Service Portal

Elements for an Enterprise Service Portal

An enterprise service portal consists of a server cluster that communicates with the following network elements:

• Directory system—A distributed set of directories with information shadowing and chaining agreements between master and slave servers
• (Optional) Network information collector

  For SRC implementations that use more than five SAEs, an enterprise service portal requires a NIC to identify which SAE is managing a subscriber. This NIC takes the distinguished name (DN) of an access as the key and returns the corresponding SAE as the value. For SRC implementations that use five or fewer SAEs, you can use directory eventing to identify the SAEs.

• Remote SAE
• Manager PC—A client PC on which a person managing an enterprise runs a Web browser to communicate with an enterprise service portal

Internally, an enterprise service portal consists of a J2EE application server cluster that implements an Enterprise API or Enterprise Tags Library, an enterprise Web application that uses one of these interfaces, and an enterprise server. The enterprise server requires persistent sessions in the cluster. That is, the cluster member that receives the first manager session request must receive all subsequent requests for the same session.

Communication Protocols

Table 18 describes the communication protocols that are used between elements in the enterprise service portal network.

Table 18: Communication Protocols for an Enterprise Service Portal

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.