WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server supports the Web Services for Remote Portlets
(WSRP) standard. Using this standard, portals can provide portlets, applications,
and content as WSRP services, and other portals can integrate the WSRP
services as remote portlets for their users. With WebSphere Application Server
you can provide WSRP services. A portlet container, like WebSphere Portal, can
consume these services as remote portlets.
Messaging, connectivity, and transaction management
WebSphere Application Server supports asynchronous messaging through the
use of a Java Message Service (JMS) provider and its related messaging
system. WebSphere Application Server includes a fully integrated JMS 1.1
provider called the default messaging provider. The default messaging provider
complements and extends WebSphere MQ and the application server. It is
suitable for messaging among application servers and for providing messaging
capability between WebSphere Application Server and an existing WebSphere
MQ backbone.
WebSphere Application Server also supports Java EE Connector Architecture
(JCA) 1.5 resource adapters, which provides connectivity between application
servers and Enterprise Information Systems (EIS). WebSphere Application
Server V7.0 comes with Java Transaction API (JTA) 1.1 specification support,
which provides standard Java interfaces for transaction management.
Authentication and authorization
WebSphere Application Server provides authentication and authorization
capabilities to secure administrative functions and applications. Your choice of
user registries include an operating system user registry, like the Resource
Access Control Facility (RACF®) on z/OS, an LDAP registry (for example, IBM
Tivoli Directory Server), custom registries, file-based registries, or federated
repositories. In addition to the default authentication and authorization
capabilities, WebSphere Application Server has support for Java Authorization
Contract for Containers (JACC) 1.1. This gives you the option of using an
external JACC-compliant authorization provider for application security. The IBM
Tivoli Access Manager client embedded in WebSphere Application Server is
JACC-compliant and can be used to secure your WebSphere Application
Server-managed resources.
Application client
With WebSphere Application Server you can run client applications that
communicate with a WebSphere Application Server by installing the application
client component on the system on which the client applications run. It provides a
stand-alone client run-time environment for your client applications and enables
your client to run applications in a Java EE environment that is compatible with
EJB.
10 WebSphere Application Server V7.0: Concepts, Planning, and Design