Here is a summary of the TWSS components, database tables, and other network elements that are required when you deploy Parlay X Presence over SIP/IMS.
This topic provides information about what is needed in the network in order to deploy the Web service implementation. The order in which the information is presented does not represent the order in which the elements should be installed.
The Access Gateway must be installed in the network and is typically in a different cluster than the Web service implementation. All incoming calls are routed through message processing flows, which are deployed on the Access Gateway. A default Presence message processing flow is provided and should be deployed, unless you are using a custom message processing flow.
The optional group resolution mediation primitive in the default flow is used when group information is included with the message. The group resolution mediation primitive is required and it resolves group URIs. If you are using a custom message processing flow that does not include the group resolution mediation primitive, incoming URIs are processed like a single presentity URI.
The Service Policy Manager must be installed in the network, either in the Service Platform cluster or in its own cluster. The Service Policy Manager manages policies associated with the Web service implementation. When the database tables are created, they are populated with default policies. For information about default policies, see the Reference section of this information center.
The console must be installed on the deployment manager node for the cluster where the Web service is deployed.The console is used to configure the Web service implementations and the Service Platform components and to specify how they should be invoked. It is also used to administer MBeans that are included in the EAR files for the Web service implementations. It is managed through JMX.
The console plug-in acts as an extension to the WebSphere Integrated Solutions Console.
The Service Platform components must be installed on the same cluster node as the Web service implementation. If the cluster is configured to synchronize, you can deploy the Service Platform components on the network deployment manager node. Some Service Platform components may be optional and, if so, are noted as optional in the following list. Interactions with other Service Platform components are also noted.
Service Platform component | Required? | Remarks |
---|---|---|
Admission Control | No | When the Admission Control component Web service is available, the Web service implementation issues a VerifyAdmittableRequest to the Admission Control component to determine if the service request can be processed. |
Traffic Shaping | No | Recommended in an integrated environment–that is, in a full setup where all of the TWSS components (Access Gateway, Service Policy Manager, and so forth) coexist. |
Network Resources | No | Recommended in an integrated environment. |
Notification Management | Yes | Used by the startPresenceNotification and endPresenceNotification operations. |
PX Notification | Yes | The Web service implementation sends notification messages asynchronously to applications through this component. A retry mechanism has been added to the notification delivery of Parlay X services. |
Address Masking | No | When deployed, the Address Masking component Web service works in conjunction with the Address Masking mediation primitive (part of the processing flow for the Access Gateway). |
Fault and Alarm | No | Recommended. When the Fault and Alarm component Web service is
available, the Web service implementation issues a RecordFaultRequest request
to the Fault and Alarm component to generate a fault or an alarm when
the following conditions occur:
|
Usage Record | No | Recommended. When the Usage Record component Web service is available, the Web service implementation uses it to record information about services rendered for status and billing purposes. |
When installing Parlay X Presence over SIP/IMS, a JMS queue is required for the PX Notification component Web service.
Database tables must be created to store configuration and policy data. You can use a single database to store this data, or you can create a unique database for each type of data. When you use the First Steps script, the required tables are created for a single database configuration.
If you choose to use multiple unique databases, or if you prefer to configure the database tables manually, you can find additional information in the topic Planning for the database.