[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Architecture of Enterprise Service Portals

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


Figure 31: 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:

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.

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 36 describes the communication protocols that are used between elements in the enterprise service portal network.




Table 36: Communication Protocols for an Enterprise Service Portal 
Protocol
Used for Communication Between

HTML/HTTPS (HyperText Markup Language over Secure HyperText Transmission Protocol)

Enterprise manager's Web browser and the enterprise portal Web application running in the enterprise service portal

Enterprise Portal API

Enterprise Web application and the enterprise server

CORBA

Enterprise server and remote SAEs running in a different Web application server than the enterprise server

LDAP

Enterprise server and SRC directories


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]