WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Planning checklist for Web service implementations

Before you begin the installation, decide where you will install the WebSphere® Telecom Web Services Server components. Print this page and record information about your environment before you begin.

General coexistence considerations

The following Direct Connect services can coexist in any combination, for instance:
  • Parlay X SMS over SMPP
  • WAP Push over SMPP
  • Parlay X Terminal Location over MLP
  • Parlay X Multimedia Messaging over MM7
Multiple service implementations for any of the following Web services cannot be deployed together. For example Parlay X Call Notification over SIP/IMS cannot be deployed together with Parlay X Call Notification over Parlay.
  • Call Notification
  • Call Handling
  • Terminal Location
  • Terminal Status
  • Third Party Call
  • Short Message Service (SMS)
Note: TWSS supports address URIs that use the following schemes only: tel:, sip:, sips:, short:.

Database tables

Refer to the topic Database tables for Web service implementations for a list of the database table names that are required for each Web service implementation.

Parlay X Call Notification over SIP/IMS

If you plan to deploy Parlay X Call Notification over SIP/IMS, you will need the following in your network.
  • The WebSphere Application Server proxy, to handle requests to the Web service and to the IMS control plane.
  • An S-CSCF or SIP proxy to direct call establishment (optional).
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive
    • CallNotificationAddress table
  • A JMS queue (which requires a service integration bus, TWSSBus) for the PX Notification component Web service.
  • A shared file system space to store the JMS queue file or database data store.

Parlay X Call Handling over Parlay

If you plan to deploy Parlay X Call Handling over Parlay, you will need the following in your network.
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • JMS queue (which requires a service integration bus, TWSSBus), for the PX Notification component Web service.
  • Shared file system space to store the JMS queue file store
  • Database tables to store:
    • Transaction and network statistics data
    • Policy data
    • Notification data
    • TWSS Administration Console configuration data
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive
    • Data for Call Handling rules

Parlay X Presence over SIP/IMS

If you plan to deploy Parlay X Presence over SIP/IMS, you will need the following in your network.
  • IBM® WebSphere Presence Server Component or other IMS-compliant presence server
  • IBM WebSphere XML Document Management Server Component to resolve groups
  • The WebSphere Application Server proxy, to handle requests to the Web service and to the IMS control plane.
  • Billing mediator to process usage records or CEI events
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • A JMS queue (which requires a service integration bus, TWSSBus) for the PX Notification component Web service.
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service, if you plan to use it
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive

Parlay X Terminal Status over SIP/IMS

If you plan to deploy Parlay X Terminal Status over SIP/IMS, you will need the following in your network.
  • An S-CSCF or SIP proxy to direct call establishment (optional).
  • IBM WebSphere Presence Server Component or other IMS-compliant presence server
  • IBM WebSphere XML Document Management Server Component to resolve groups
  • The WebSphere Application Server proxy, to handle requests to the Web service and to the IMS control plane.
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • A JMS queue (which requires a service integration bus, TWSSBus) for the PX Notification component Web service.
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service, if you plan to use it
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive

Parlay X Call Handling over SIP/IMS

If you plan to deploy Parlay X Call Handling over SIP/IMS, you will need the following in your network.
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • JMS queue (which requires a service integration bus, TWSSBus), for the PX Notification component Web service.
  • Shared file system space to store the JMS queue file store
  • Database tables to store:
    • Transaction and network statistics data
    • Policy data
    • Notification data
    • TWSS Administration Console configuration data
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive
    • Data for Call Handling rules

Parlay X Third Party Call over SIP/IMS

If you plan to deploy Parlay X Third Party Call over SIP/IMS, you will need the following in your network.
  • The WebSphere Application Server proxy, to handle requests to the Web service and to the IMS control plane.
  • An S-CSCF or SIP proxy to direct call establishment (optional).
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive
    • Data for the third party call information
  • Optional: Consider the endpoints for UserAgent PBX numbers or SIP Software IP addresses.

Parlay X Payment (PostPaid)

If you plan to deploy Parlay X Payment (PostPaid), you will need the following in your network.
  • Billing mediator to process usage records or CEI events
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive

Parlay X Address List Manager over XCAP

If you plan to deploy Parlay X Address List Manager over XCAP, you will need the following in your network.
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • IBM WebSphere XML Document Management Server Component (IBM XDMS), or equivalent XCAP server, deployed and configured in the TWSS Administration Console
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive

The Web service implementation needs to be aware of the security settings for the XCAP server: either the Trust Association Interceptor, basic authentication, or unauthenticated.

WAP Push over SMPP

If you plan to deploy WAP Push over SMPP, you will need the following in your network:
  • Short Message Service Center (SMSC)
  • SMPP connector
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • JMS queues (which require a service integration bus, TWSSBus) for the Web service
  • A shared file system space to store the JMS queue file store.
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • WAP Push data
    • TWSS Administration Console configuration data
    • Notification data
    • Data for the Usage Record component Web service, if you plan to use it
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive

Parlay X SMS over SMPP

If you plan to deploy Parlay X SMS over SMPP, you will need the following in your network.
  • Short Message Service Center (SMSC)
  • SMPP connector
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • JMS queues (which require a service integration bus, TWSSBus) for the PX Notification component Web service and for the Web service itself
    Note: This is not required for synchronous messaging.
  • A shared file system space to store the JMS queue file or database data store.
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • Notification data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive
    • SMS data

Parlay X Terminal Location over MLP

If you plan to deploy Parlay X Terminal Location over MLP, you will need the following in your network.
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • A JMS queue (which requires a service integration bus, TWSSBus) for the PX Notification component Web service.
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • Notification data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive
    • Terminal location data

Parlay X Multimedia Messaging over MM7

If you plan to deploy Parlay X Multimedia Messaging over MM7, you will need the following in your network.
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • JMS queues (which require a service integration bus, TWSSBus) for the PX Notification component Web service and for the Web service itself
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • MMS data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive

Parlay X Terminal Status over Parlay

If you plan to deploy Parlay X Terminal Status over Parlay, you will need the following in your network.
  • Parlay Connector, to communicate with a Parlay gateway
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • Parlay Administration Console
  • A JMS queue (which requires a service integration bus, TWSSBus) for the PX Notification component Web service.
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • Notification data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service, if you plan to use it
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive

Parlay X Terminal Location over Parlay

If you plan to deploy Parlay X Terminal Location over Parlay you will need the following in your network.
  • Parlay Connector, to communicate with a Parlay gateway
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • Parlay Administration Console
  • A JMS queue (which requires a service integration bus, TWSSBus) for the PX Notification component Web service.
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service, if you plan to use it
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive
    • Notification data

Parlay X SMS over Parlay

If you plan to deploy Parlay X SMS over Parlay, you will need the following in your network.
  • Parlay Connector, to communicate with a Parlay gateway
  • Access Gateway
  • Service Policy Manager
  • Service Platform components (see the topic Required components for the Web service implementations).
  • TWSS Administration Console
  • JMS queues (which require a service integration bus, TWSSBus) for the PX Notification component Web service and for the Web service itself
  • Parlay Administration Console
  • Database tables to store
    • Transaction and network statistics data
    • Policy data
    • Notification data
    • TWSS Administration Console configuration data
    • Data for the Usage Record component Web service
    • Traffic data for use by the SLA Enforcement mediation primitive
    • Information about messages, used by the Message Interceptor mediation primitive
    • SMS data

Parlay X Call Notification over Parlay

If you plan to deploy the Parlay X Call Notification over Parlay, you will need the following in your network.

Parlay X Third Party Call over Parlay

If you plan to deploy the Parlay X Third Party Call over Parlay, you will need the following in your network.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.