Service oriented architecture

A Service Oriented Architecture (SOA) represents the current pinnacle of interoperability, in

which resources on a network are available as individual, loosely-coupled and independent

services (Freudenstein et al., 2006; Murray, 2003; Bunge et al., 2008; Lewis et al., 2007). As

Service-oriented Architecture (SOA) matures, an efficient approach for the integration of

web services in portals is required. SOA is a desirable and inevitable solution.

In summary, a successful portal includes determining factors: 1) architecture built on layers

of services and component modules; 2) providing the ability to inter-mingled data and

content from multiple sources stored in multiple formats; 3) a framework that is extensible

by employing open standards in the development of portal services (Mary, 2002; Brakel,

2003; Azar et al., 2008).

Single sign-on approach

Single sign-on is a simple means of managing passwords and authenticating users to

various applications. It allows users to access all authorized services and resources

seamlessly (Adabala et al., 2004; Heckle et al., 2008; Volchkov, 2001; Heckle, 2007; Mauro,

2008). However, its implementation has tremendous complexities that involve overall

security policies, user profiles, natures of business, integration of legacy, web applications

portfolios, cost structures of Information Technology operations, as well as future

application development strategies (Heckle et al., 2008; Volchkov, 2001).

In general, pragmatic approaches adopt the following criteria: 1) modifying existing

applications and building new ones, synchronizing passwords to share recourses and

30 Web Intelligence and Intelligent Agents

services; 2) establishing external tools or an authentication middleware, layer to support

authentication methods or servers; 3) configuring legacy applications with their existing

directories and synchronizing with the enterprise directory, central administration promptly;

4) delegating or mapping user credentials or capabilities on resources; 5) developing trust

channels to deliver, share user credentials information (Adabala et al., 2004; Heckle et al.,

2008; Volchkov, 2001; Heckle, 2007). In addition, the single sign-on technology can mitigate

the shortcomings of id/password approaches.