The WebSphere® Application
Server Feature Pack for Communications Enabled Applications (CEA)
V1.0 helps simplify development of innovative applications by offering
an SOA-based programming model to add multi-modal communications capabilities
such as Click to call, Cobrowsing and Two-way Synchronized Forms,
to existing and new applications using existing Java skills.
New feature: The new features that are
described in this topic are current as of the original release of
the product version. Changes in this documentation that are related
to service releases are marked with fix pack icons.
newfeat
Benefits of the Feature Pack for CEA Version 1.0
WebSphere Application Server
Feature Pack for Communications Enabled Applications V1.0 is a product
extension available to WebSphere Application
Server V7.0 customers that:
- Delivers an innovative programming model that simplifies the addition
of communications capabilities into existing and new applications
by leveraging existing Java skills
- Provides Web services and REST services-based APIs which enable
a richer user experience and increases user interaction effectiveness
- Delivers customizable and extensible multi-modal communications
widgets: Click to call, Contact Center Cobrowsing, peer-to-peer Cobrowsing
and Two-way Synchronized Forms
- Provides a unit test environment to prototype and test applications
without the need to access the corporate Telephony/Unified Communications
network
- Provides third party Telephony/Unified Communications support
and an on-ramp to CEBP (communications enabled business process) solutions
- Supports the latest Session Initiation Protocol (SIP) Servlet
1.1 standard (JSR 289)
New and changed features in
Feature Pack for CEA Version 1.0.0.1
Notable changes to
Feature Pack for CEA Version 1.0 provided by Version 1.0.0.1 include
support for the following features:
- Clustering and failover support for CEA services on distributed
platforms (Web Collaboration and Telephony services)
- iWidget support
- Making Web collaboration URIs more secure with a nonce to prevent
session snooping
- New Dojo level supported by the widgets
New and changed features in
Feature Pack for CEA Version 1.0.0.3
Notable changes to
Feature Pack for CEA Version 1.0.0.1 provided by Version 1.0.0.3 include
support for the following features:
- Clustering and failover support of the communications services
on z/OS®
New and changed features in
Feature Pack for CEA Version 1.0.0.5
Notable changes to
Feature Pack for CEA Version 1.0.0.1 provided by Version 1.0.0.5 include
support for the following features:
- Mobile widgets can be included in Web applications that enable:
- Users to enter their mobile phone number and request an immediate
callback from your company
- Users to enter their mobile phone number and receive notifications
of incoming calls
- A mobile phone number to be used for collaborating and cobrowsing
- SIP servlet requests can include proprietary header fields. SIP
proprietary header fields enable certain SIP settings to be implemented
on a per message basis. SIP settings set at the SIP container level
apply to all SIP messages handled by that SIP container.
Restrictions
The following restrictions
are changed based on various service levels of the product:
- Features related to communications services (widgets, REST interface,
Web Service interface) are limited to single server environments.
Features related to communications
services (widgets, REST interface, Web Service interface) are no longer
limited to single server environments.
Features related to communications
services (widgets, REST interface, Web Service interface) are no longer
limited to single server environments.
- Clustering is only supported for the JSR 289 feature.
Clustering is no longer
restricted to just the JSR 289 feature.
The Web collaboration feature of the Feature Pack
for CEA does not work with multiple servant regions. If multiple servant
regions for a server are active, a user might not be able to communicate
with another user. Configure your application server to use one servant
region only.
The Web collaboration feature
of the Feature Pack for CEA works with multiple servant regions.
When you start WebSphere Application Server
Version 7.0 Fix Pack 9 with Feature Pack for CEA Version 1.0.0.3 enabled
in a stressed environment, then up to 10% of incoming Web collaboration
calls might fail to establish. The failure only affects incoming calls;
no established sessions are affected. When failures do happen, they
occur within one second or less, while the application servers are
starting. After the application servers display an Open for
e-business message, no other call failures occur because
all incoming calls are established.
Feature Pack for CEA Version 1.0.0.3 is
not compatible with Application Enablement Services Version 5.2.0.98.
To fix this problem, install Application Enablement Services Version
4.2.1.20.5.0, which is compatible with Feature Pack for CEA Version
1.0.0.3. For more details, read the following information. Currently,
Feature Pack for CEA Version 1.0.0.3 does not implement RFC 4028,
which requires the use of the following header fields on INVITE requests:
- Session-Expires
- Conveys the lifetime of the session.
- Min-SE
- Conveys the minimum allowed value for the session timer.
Because Application Enablement Services Version
5.2.0.98 does not allow an administrator to disable the use of RFC
4028 in its core message processing, users of Feature Pack for CEA
Version 1.0.0.3 and Application Enablement Services Version 5.2.0.98
cannot deploy a TR/87 solution in their environments. This problem
occurs after you attempt to initiate a TR/87 request through Application
Enablement Services Version 5.2.0.98. The following error response
is returned in the application server trace logs. This same error
message is also readable in Application Enablement Services Version
5.2.0.98 system logs:
SIP/2.0 488 Not Acceptable here: Session could not be
established - Supported: timer header is required.
To
diagnose this problem, complete the following steps:
- In the administrative console, click .
Enable the following application server trace:
*=info: com.ibm.ws.commsvc.*=all: com.ibm.ws.cti.*=all
- Find the following message in the application server SystemOut.log
and trace.log:
SIP/2.0 488 Not Acceptable here: Session could not be established - Supported: timer header is required.
If the preceding message is displayed, an incompatibility problem
exists.