IBM® WebSphere® Telecom
Web Services Server (TWSS)
version 7.1 includes
functionality and support for new Web service implementations.
Custom JCA adapter
TWSS version 7.1 provides
a JCA adapter architecture with which you can achieve a pluggable
component architecture for managing connections with a network entity
(or with an SMSC when you are using the SMPP protocol). TWSS version 7.1 also
provides a JCA adapter that is based on version 3.4 of the SMPP protocol.
Enhancements to the Access Gateway
- Two options for SLA enforcement
- There are now two methods for controlling the type of traffic
admitted into the network for individual requesters using Service
Level Agreement (SLA) mediation primitives:
- Using SLA Cluster Enforcement, hierarchical limits in the SLA
mediation primitive are enforced using a sliding window, rate limiting
bucket algorithm.
- Using SLA Local Enforcement, hierarchical limits in the SLA mediation
primitive are enforced using a fixed window algorithm.
- REST-style access using HTTP
- TWSS version 7.1 provides
an open network enablers OneAPI–a
single API that can be used across multiple operators. Through version
7.0, the TWSS Access Gateway supported
only Web service invocations to access the telecom services provided
by the service platform. The purpose of the OneAPI is
to extend the channel support for the Access Gateway to
include HTTP.
- Subflows
- With the use of subflows, you can more easily customize the default
Access Gateway flows and apply your customizations across multiple
flows.
Enhancements to the Service Platform components
- Notification Management user interface
- A new user interface has been implemented as an add-on to the
existing notification management component, providing an easy way
for administrators to perform any administrative tasks through a user
interface. It is available as a control found in the TWSS Administration Console.
- Notification retry
- A retry mechanism has been added to the notification delivery
of several Parlay X services that retries the endpoint for a configurable
number of times before a failure is logged. The endpoint could be
the ESB endpoint or the requester's endpoint. The retry is done at
the PXNotification component scope and is done as long as the endpoint
URI is not accessible and the retry count is not exhausted. A retry
delay is also configurable for the pause time between the retries.
New Web service implementation: Parlay X Call Handling over SIP/IMS
Telecom Web Services Server version
7.1 includes
support for a new Web service implementation.
Parlay X Call Handling over SIP/IMS provides
access to the features of the Parlay X 2.1-based Web service, which
accepts requests for call handling services and controls various checks
that are done to ensure the requests are valid. This feature provides
operations to set rules for a network terminal or a group and allows
it to accept, block, or route calls to another terminal. It also provides
the functionality to view or clear a pre-existing rule. The following
operations are supported:
- setRules
- setRulesForGroup
- getRules
- clearRules
Enhancements to existing Web service implementations
In
TWSS 7.1,
the attachment handling functionality, as part of the sendMessage
operation in MMS, has been enhanced to include a feature where the
attachments can now be stored in-memory and not persisted into the
database. Opting for in-memory attachment handling also means that
the sendMessage operation now occurs synchronously, as opposed to
the asynchronous mode of operation in previous releases. You now have
an option, provided by the Integrated Solutions Console,
to choose between Synchronous mode, with in-memory attachment handling,
or Asynchronous mode, for the sendMessage operation.