IBM WebSphere Telecom Web Services Server, Version 7.0.0 Interim Fix 2 Readme

© Copyright International Business Machines Corporation 2009. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

About this interim fix

This interim fix is a cumulative fix which includes all of the latest changes for IBM® WebSphere® Telecom Web Services Server (TWSS), Version 7.0.0. This interim fix is recommended for all customers with a TWSS 7.0.0 or 7.0.0.1 installation on all supported platforms.

This interim fix is installed using the WebSphere Update Installer as well as some manual updates.

Fix and update history

This interim fix includes the following APARs and fixes. This package includes all fixes for the Access Gateway, Service Platform components, and TWSS Web service implementations.

Fix Pack 001 

Note: If you are on a Solaris platform, the base version of TWSS is 7.0.0.1 and the system already contains the fixes noted in this Fix Pack 001 section.

  • Access Gateway - Transaction Recorder (TR) and Network Statistics (NS) Mediation Primitive (MP), Null Pointer Exception (NPE) during Database interaction (APAR LI74722): Corrects the problem of NPE related to database writes, when multiple instances of Network Statistics mediation primitives are included in a given Mediation Flow application.
  • Access Gateway - SLA Cluster Enforcement (SLA) Mediation Primitive, Problem related to not issuing appropriate error code during database interaction (APAR LI74722): Corrects the problem related to not issuing an appropriate error-code during the fault scenarios of database interactions in the SLA Cluster mediation primitive.
  • Access Gateway - SLA Cluster Enforcement (SLA) Mediation Primitive, Issue related to NPE during the absence of SLAImplementation.properties in sla-impl.jar (APAR LI74722): Corrects the problem related SLAImplementation.properties file missing scenario by issuing the error-code SOAC4030.
  • Access Gateway - Address Masking (AM) Mediation Primitive, Issue related to resolving the nested XPath elements (APAR LI74722): Corrects the problem related to resolving the XPath statements for addresses with nested elements.
  • Access Gateway - Call Handling Default Flow, Issue related to incorrect wiring (APAR LI74722): Corrects the problem related to the incorrect wiring of Message Interceptor (MI) Mediation Primitive's Fail terminal being connected to the input terminal of the SLA Cluster Enforcement (SLA) Mediation Primitive. For details refer to Call Handling default flow rewiring in the configuration instructions.
  • Access Gateway - WAP Push Default Flow, Removal of SmsNotification interface from default flow (APAR LI74722): Removed the redundant SmsNotification interface from the WAP10_FLOW.ear. The corresponding mediation flow has also been removed.
  • Access Gateway Third Party Call over SIP, issue related to JSESSIONID being returned along with Call Identifier (APAR LI74225): Corrects the problem by appending the JSESSIONID to the CallIdentifier as a response to a makeCall operation. Those who prefer to use the Third Party Call default flow do not need to make any changes. For those who need to customize the Third Party Call default flow, refer to Customizing Third Party Call default flow for instructions on how to build the Third Party Call flow after customizing it.
  • Address Masking Service Platform Web Service, Issue related to inserting data into Oracle database (APAR LI74722): Corrects the problem related to the insertion of data to Oracle Database by updating the insert statement.
  • Address Masking Service Platform Web Service, Issue related to the hardcoded datasource name reference to JDBC/TWSSDB (APAR LI74722): Corrects the problem related to the data source by removing the hardcoded reference and referring the configured value.
  • Parlay Connector, Inclusion of trace option related to Application Manager Classloading (APAR LI74722): Trace options related to the Class loader have been included to help easier diagnosis of any possible Classloader issues.
  • Parlay Connector, Round robin of the Primary callback (APAR LI74493): On the click of the Refresh button in the Parlay Administration console, the callbacks on the Primary Node can be shifted to a different node on a round robin basis. The SELF_TEST in the Parlay Administration console includes Callback statistics.
  • SMS over SMPP Service Implementation Web Service, Issue related to higher latency (APAR LI74722): Corrects the problem related to the higher latency on database interactions when there are a higher number of transactions per second (TPS).
  • SMS over SMPP Service Implementation Web Service, Issue related to concatenation of multisegmented messages at the SMSC end (APAR LI74722): Corrects the problem related to the SAR reference number for handling multisegmented messages.
  • WAPPush over SMPP, Issue related to database records being created for status less messaging (APAR LI74722): Corrects the problem related to the records being created in the WAPPUSHSENDDATA database table while handling status less messages.
  • WAPPush over SMPP, Issue related to Mobile Terminated (MT) messages being allowed on Receiver (Rx) channel (APAR LI74722): Corrects the problem by restricting the user from sending MT messages on Rx channel.
  • WAPPush over SMPP, Issue related to MT messages with confirm delivery and receipt request being allowed on Transmitter (Tx) channel (APAR LI74722): Corrects the problem by restricting the user from sending MT messages with confirm delivery and receipt request on Transmitter (Tx) channel.
  • WAPPush over SMPP, Null Pointer Exception (NPE) in WAPPush during the server start-up (APAR LI74722): Corrects the problem of NPE related to WAPPush during server startup in a combined deployment of the TWSS Direct Connect Services.
  • Terminal Location over MLP, ClassNotFoundException in FFDC (APAR LI74722): Corrects the problem of ClassNotFoundException for ParlayConnector classes in the FFDC during the server startup in a combined deployment of the TWSS Direct Connect Services.
  • Terminal Location over MLP, issue related to the conversion of MLP CircularArcArea shape to Parlay X LocationInfo (APAR LI74722): Corrects the problem related to the accuracy calculation for MLP CircularArcArea shape support.
  • Call Notification over SIP, Notifications are lost (APAR LI74722): Corrects the problem of report notifications are not being processed after the system recovers from Out Of Memory (OOM).
  • Third Party Call over SIP and Call Notification over SIP, Issue related to Usage Record entry not populated during error scenarios (APAR LI74722): Corrects the problem by writing the Usage Record entries during error scenarios.
  • SMS over Parlay, issue related to the conversion of MLP CircrularArcArea shape to Parlay X LocationInfo (APAR LI74722): Corrects the problem of callback references stack up in SERVERPROPETIES table, by removing the callback references once the callback is received by the service.
  • TWSS Parlay Web Services, ClassNotFoundException while starting the parlay services (APAR LI74722): Corrects the problem of ClassNotFoundException in the FFDC during the startup of TWSS Parlay Web Services.
  • Call Handling over Parlay, Issue related to SystemOut.log file contains trace strings (APAR LI74722): Corrects the problem by not logging the trace strings to the SystemOut.log file.
  • Administration Console, issue related to TWSS and Parlay Admin console links being displayed twice in the WAS Navigation pane: For details refer to TWSS Administration Console links appear more than once in the WAS Integrated Console navigation pane in the configuration instructions.
  • First Steps (FS), Issue related to transfer of runtime files to all the nodes in a cluster (APAR LI74722): Corrects the profiles selection during the configuration and deployment process to perform transfer of runtime files to all the nodes in a cluster. Refer to First Steps changes for details on the issues and changes related to First Steps.
  • First Steps, Insufficient description of configuration modes (APAR LI74722): Added details to each of the configuration modes.
  • First Steps, Issue related to “line too long” warning message in FS logs (APAR LI74722): Corrects the problem by limiting the size of the message text in the FS log file.

Interim Fix 001

  • Access Gateway - Issue related to FileNotFound exception being noticed while performing flowearpostproc operation (APAR LI74624): Corrects the problem of FileNotFound exception while performing flowearpostproc. The WIDPlugins iFix zip file contains files "esb_add_app_nspref.xsl" & "esb_add_web_nspref.xsl" that will help in resolving the issue.
  • Service Platform – platform.ear file missing in the TWSS Base installer (APAR LI74623): Corrects the problem by adding the platform.ear file to the TWSS service platform (SP) pak file.
  • Terminal Location over MLP, Issue related to Service ID and Request Mode are not sent to MLP Location Server (APAR LI74724): Corrects the problem by adding 3 new MBean attributes (Service ID, Request Mode and Requestor Required) to MLP Connector MBean. For more details refer to Additional attributes for MLP Connector MBean.
  • MMS over MM7, issue related to RFC2822 email address support for MMS/MM7 SI (APAR LI74709 & LI74710): Provides support to the RFC2822 email address. The RFC2822 email address support is provided to both MO and MT messages of MMS/MM7 SI. For more information, refer to MMS/MM7 service RFC2822 support.
  • MMS over MM7, issue related to the “authorization” header not being passed to the MMSC (APAR LI74699): Corrects the problem of MMSC reporting the StatusCode 2002 with StatusText “Address error” and Details “2819:Corrupt VAS address”.
  • MMS over MM7, issue related to MMS MO messages where sender field is being used as recipients in case if recipients field being missing (APAR LI74799): Corrects the problem of sender field being used as “recipients to” in case of MO messages missing the recipient field. If the recipients to field is missing then an error message stating that the recipients field is missing will be sent back to MMSC as a response instead of using the sender field as a recipients
  • Parlay Connector - Redesign of the Application Manager's Classloading mechanism (APAR LI74799): This fix is related to the change in the Application Manager's class loading mechanism, to use the JDK URLClassLoader API instead of the WebSphere CompoundClassLoader API (Deprecated). This class loading capability is required to understand the Application classes to dispatch Management events to them.
  • Removing ^M characters from .ddl and firststeps scripts (APAR LI74799): In this issue ^M characters which are seen in some of the scripts have been removed. The installer will replace the files in the appropriate location. This does not affect any of the functionality, hence you do not need to re-run any of these scripts.
  • CallHandling over Parlay, issue related to the Mismatch of the NetworkResource name in the Call Handling Web Service (APAR LI74722): Corrects the problem related to the mismatch of the NetworkResource name by maintaining consistency between the name in the Network Resource MBean and Call Handling Web Service MBean.
  • PX21_TL_MLP Service Implementation: Request XML validation failure in MLP Location Server (GMLC) related to the element "svc_init" version (APAR LI74799): Refer to Configuring the DTD Type and Location for MLP Protocol version 3.1.
  • PX21_TL_Parlay Service Implementation: Admission Control reports exceptions during the invocation of startPeriodicNotification operation (APAR LI74799): Refer to Adding startPeriodicNotification for PX21_TL_Parlay SI.

Interim Fix 002   

  • First Steps (FS), Issue related to FS not having the selection option for choosing the installed components for heterogeneous cluster deployment (APAR LI74924): Corrects the issue by providing a component deployment selection option. Users can choose the required components and deploy them to the required target cluster. For details refer to Additional Configuration related to First Steps in the configuration instructions.
  • Terminal Location over MLP, Issue related to the insertion of NULL records in TLMLPNOTIFYDATA data table while starting notifications (APAR LI74924): Corrects the problem by updating the MLP response message handling, when MLP Location Server invalidates the requests related to notification operations.
  • Terminal Location over MLP, Issue related to creating MLP Header elements while ending notifications (APAR LI74924): Corrects the problem by updating the MLP request message creation for the end notification operation.
  • Third Party Call over SIP/IMS - Issue related to small percentage of memory leak being noticed during long run on WAS v7.0.0.3 and v6.1.0.23 (APAR LI74924): Corrects the problem of memory leak overhead while performing long hour/stress run. For more information, refer to Configuration for Third Party Call over SIP/IMS in the configuration instructions.
  • Third Party Call over SIP/IMS - Issue related to No Audio Problem being noticed while performing makeCall between tel URIs . (APAR LI74917): Corrects the problem of No Audio Problem [or Early Media Session] with the new SIP Third Party Call flow. This new call flow is defined in Section 8 of RFC 3725.
  • Usage Record DB table migration (APAR LI74924): Corrects an issue related to the Non-Atomic Batch Failure error message in DB2, while creating usage record entries in the Usage Record database table. Refer to Migrating the Usage Record database table from TWSS 6.2.x to TWSS 7.0.x in the "Additional Information" section below.

Software compatibility

  • Operating systems:
    • Red Hat Enterprise Linux ® AS 5.0 Update 2 or later
    • SUSE Linux Enterprise Server 10 SP 1 or later
    • AIX ® 5L 5.3 TL 07 04-0818 or later
    • Sun Solaris 10 (5.10 version) 32bit and 64bit on Sparc
  • Application servers
    • One of the following application server offerings is required:
      • WebSphere Application Server Network Deployment (WAS ND), Version 7.0.0.3
      • WebSphere Application Server Network Deployment, Version 6.1.0.23
      • In addition, if the WAS ND version is 7.0.0.3, following iFixes must be applied:

APAR

File Name

PK74054

7.0.0.0-WS-WAS-IFPK74054.pak

PK78434, PK80305

7.0.0.3-WS-WAS-IFPK80305.pak

PK80775

7.0.0.0-WS-WAS-IFPK80775.pak

PK81028

7.0.0.3-WS-WAS-IFPK81028.pak

PK81897

7.0.0.3-WS-WAS-IFPK81897.pak

PK82137, PK84684

7.0.0.3-WS-WAS-IFPK84684.pak

PK83245

7.0.0.3-WS-WAS-IFPK83245.pak

PK83447

7.0.0.3-WS-WAS-IFPK83447.pak

PK83467

7.0.0.1-WS-WAS-IFPK83467.pak

PK89010

7.0.0.3-WS-WAS-IFPK89010.pak

PK89010

6.1.0.23-WS-WAS-IFPK89010.pak
  • WebSphere Enterprise Service Bus
    • WebSphere Application Server Enterprise Service Bus, Version 6.1.0.2
  • WebSphere Integration Developer
    • WebSphere Integration Developer, Version 6.1.0.102
  • Java
    • JDK, Version 1.6.0 SRX (included with WebSphere Application Server Network Deployment Version 7.0.0.3)
    • JDK, Version 1.5.0 SRX (included with WebSphere Application Server Network Deployment Version 6.1.0.23)
  • Databases
    Each component has different database needs. Refer to the Planning section of the information center for each component to understand the database needs for that component. WebSphere Telecom Web Services Server requires multiple database tables. Scripts are provided to assist in the database table creation; however, these scripts are provided for AIX and Linux only.
    • IBM DB2™ Enterprise Server Edition Version 9.5 FixPak 1
    • Oracle Database Version 10.2.0.4, 10.2.0.6, or 11.1.0.7 

Installation requirements

Hardware requirements

Hardware requirements for TWSS are included in the information center and have not changed since version 7.0.0. For details, refer to the following information:

http://publib.boulder.ibm.com/infocenter/wtelecom/v7r0m0/topic/com.ibm.twss.doc/com_hw_prereqs.html

Software requirements

Software requirements for TWSS are included in the information center. For details, refer to the Software compatibility section of this Readme and to the following topic in the information center:

http://publib.boulder.ibm.com/infocenter/wtelecom/v7r0m0/topic/com.ibm.twss.doc/com_sw_prereqs.html

Installation instructions

Note: In this section, WAS_ROOT refers to the WebSphere home directory, for example /opt/IBM/WebSphere/AppServer. WAS_ESB_ROOT refers to the WebSphere ESB home directory, for example /opt/IBM/WebSphere/ESB. WID_HOME refers to WebSphere Integration Developer home directory, for example C:\IBM\WID61

To apply the interim fix, complete the following steps:

  1. Verify that the WebSphere Application Server (WAS) ND version is at supported level as listed in Software Compatibility section, and all appropriate iFix or iFixes have been applied.
  2. Verify that the WebSphere Application Server Enterprise Service Bus (ESB) version is at supported level as listed in Software Compatibility section.
  3. If you have an earlier TWSS fix pack that was installed using the Update Installer, uninstall it. The TWSS Update Installer fix packs are cumulative.
  4. Download the WebSphere Update Installer version 7.0.0.3 on both the Access Gateway application servers and the Service Platform application servers. You will use this version of the update installer for both the Access Gateway which is based on WAS ND 6.1.0.x and the Service Platform which is based either WAS 6.1.0.x or WAS 7.0.0.x
  5. Download the IMS UPDI Plugins package 7.0.0.1-WS-WAS-IMS-UPDIPlugins.pak into the WAS_ROOT/updateInstaller/maintenance directory on both the Access Gateway Application servers and the Service Platform Application servers.
  6. If the IMS UPDI Plugin is already installed on the WAS Update Installer (Note: After applying the IMS Update Installer Plugin, if you have upgraded or installed a new version of the WAS Update Installer (UPDI) itself, then you won’t be able to apply this interim fix). You need to download and run a reset script available on the support download site which will then allow installation of TWSS 7.0.0.1 fixpack. For details see the IMS Update Installer Plugins installation page for fix pack 7.0.0.1: http://www.ibm.com/support/docview.wss?uid=swg24017457
  7. Download the TWSS Update Installer package 7.0.0-WS-WAS-TWSS-AG-IF000002.pak to the WAS_ROOT/updateInstaller/maintenance directory on the Access Gateway servers.
  8. Download the TWSS Update Installer package 7.0.0-WS-WAS-TWSS-SP-IF000002.pak to the WAS_ROOT/updateInstaller/maintenance directory on the Service Platform servers.
    Note: If you have only the Access Gateway installed, install this .pak file on the Access Gateway server.
  9. Download the TWSS Update Installer package 7.0.0-WS-WAS-TWSS-Services-IF000002.pak to the WAS_ROOT/updateInstaller/maintenance directory on the Service Platform servers.
  10. Download the TWSS Update Installer package 7.0.0-WS-WAS-TWSS-SPM-IF000002.pak to the WAS_ROOT/updateInstaller/maintenance directory on the Service Platform servers.
  11. Download the TWSS WID plugin iFix package 7.0.0-WS-WAS-TWSS-WIDPlugins-IF000002.zip to a temporary folder and unzip the contents into the folder <WID_HOME>/TWSS folder. It should have extracted the files esb_add_app_nspref.xsl & esb_add_web_nspref.xsl
  12. Start the Update Installer as described in the WebSphere documentation, and select the TWSS fix pack(s) to be installed.
    First, install the UPDI Plugins package on each of the deployment managers of WAS ND and/or the WESB clusters.
    The 7.0.0-WS-WAS-TWSS-AG-IF000002.pak contains updates to the Access Gateway. Apply the UPDI plug-in and the fix pack on all of the nodes and on the deployment manager for the Access Gateway. The Update Installer updates the WAS_ESB_ROOT/lib/ext directory and the WAS_ESB_ROOT/installableApps/TWSS-Base directory.
    The 7.0.0-WS-WAS-TWSS-SP-IF000002.pak contains updates to the Service Platform and should be installed before the TWSS services pak file. The Update Installer updates the WAS_ROOT/installableApps/TWSS-Base directory.
    The 7.0.0-WS-WAS-TWSS-Services-IF000002.pak contains updates to the TWSS Services.
    The Update Installer updates the WAS_ROOT/installableApps/TWSS-Services directory contents. For all of the TWSS components, the Update Installer does not deploy the updates onto the application server.
  13. Update the component EARs that are deployed on the application server. You can do this either by using the First Steps wizard or by following the instructions in the following information center topics:

Configuration instructions

The configuration for TWSS is the same as that described in the information center, except as specified in either the TWSS 7.0.0 Readme (WebSphereProductsForTelecomReadme.html) or this Readme.

TWSS Administration Console links appear more than once in the WAS Integrated Console navigation pane

This issue may be noticed after applying WAS fixes on an existing TWSS system. This is caused by duplicate entries of TWSS Admin Console links in the navigation.xml file of the isclite.ear file. To resolve the problem, follow these steps:

  1. Stop the node agents, servers, and deployment manager.
  2. Keep a backup of the navigation.xml file located at WAS_ROOT/systemApps/isclite.ear/config on the deployment manager server.
  3. Open the navigation.xml file in a text editor
  4. Delete the following lines: 
 
&ltnavigation:nav-element uniqueName="consoles" moduleID="com.ibm.soa.console" nodeType="label" isWscNode="true">
  &ltnavigation:title>
         &ltbase:nls-ref key="soa.root" locationName="com/ibm/ws/console/core/resources/ConsoleAppResources"/>
  </navigation:title>
  &ltnavigation:parentTree parentTreeRef="root" ordinal="210"/>
 
  &ltnavigation:nav-element url="/ibm/console/secure/com.ibm.soa.adminconsole/SelectSOAConsoleSettings.jsp?roottype=SOAConsoleNetworkResources" uniqueName="soa.consoles.nr" moduleID="com.ibm.soa.console" nodeType="url" isWscNode="true">
         &ltnavigation:title>
                 &ltbase:nls-ref key="soa.consoles.nr" locationName="com/ibm/ws/console/core/resources/ConsoleAppResources"/>
         </navigation:title>
         &ltnavigation:parentTree parentTreeRef="consoles" ordinal="210"/>
  </navigation:nav-element>
         
  &ltnavigation:nav-element url="/ibm/console/secure/com.ibm.soa.adminconsole/SelectSOAConsoleSettings.jsp?roottype=SOAConsoleServicePlatform" uniqueName="soa.consoles.p" moduleID="com.ibm.soa.console" nodeType="url" isWscNode="true">
         &ltnavigation:title>
                 &ltbase:nls-ref key="soa.consoles.p" locationName="com/ibm/ws/console/core/resources/ConsoleAppResources"/>
         </navigation:title>            
         &ltnavigation:parentTree parentTreeRef="consoles" ordinal="210"/>    
  </navigation:nav-element>
         
  &ltnavigation:nav-element url="/ibm/console/secure/com.ibm.soa.adminconsole/SelectSOAConsoleSettings.jsp?roottype=SOAConsoleWebServices" uniqueName="soa.consoles.ws" moduleID="com.ibm.soa.console" nodeType="url" isWscNode="true">
         &ltnavigation:title>
                 &ltbase:nls-ref key="soa.consoles.ws" locationName="com/ibm/ws/console/core/resources/ConsoleAppResources"/>
         </navigation:title>
         &ltnavigation:parentTree parentTreeRef="consoles" ordinal="210"/>
  </navigation:nav-element>
</navigation:nav-element>
  1. Save and close the navigation.xml file.
  2. Start the deployment manager, node agents, and servers.

Additional configuration related to First Steps

TWSS First Steps requires all of its files under the directory WAS_ROOT/installableApps/TWSS-Base/firststeps to have full file permission. Follow these steps to provide full permission to the files:

  1. Log in as a user with super administrative privileges.
  2. Before launching First Steps, navigate to the directory WAS_ROOT/installableApps/TWSS-Base/firststeps.
  3. To provide full permissions to the file, execute the command chmod 777 *.

The First Steps configuration mode determines how existing configuration resources and properties are updated. Valid values are "Migrate", "Update", and "Initial."

  • Initial - Initial values are provided for all configuration resources and properties. Existing values are overwritten, if necessary, to create an initial clean installation. This option should only be used during the first time deployment of any TWSS components. For the subsequent add-ons of any new components, the update option should be used. The Initial option completely drops all of the tables in the database and recreates them.
  • Migrate - Initial values are provided for missing configuration information. Existing configuration resources and properties are used, if possible, to enable migrating between release levels. This option is supported only for the consolidated database setup of TWSS.
  • Update - Initial values are provided for missing configuration resources and properties. Existing configuration resources and properties are used, if possible, to enable an update after applying an iFix or fixpack, if instructed by the readme file. This option should be used when deploying service add-ons to the existing setup and for making an update after applying an iFix or fixpack. The Update option does not drop the existing tables but creates the new required tables in the database.

Configuration Mode Application Deployment Database Table Drop Database Tables Creation Existing WebSphere Application Server resources
Initial Removes the existing EARs and redeploys with the new installation Drops all the db tables Creates the required tables Any matching resources are reused. Otherwise, new resources are created.
Migrate Removes the existing EARs and redeploys with the new installation Does not drop any existing tables Migrates the existing table schema of the older version to the newer version Any matching resources are reused. Otherwise, new resources are created.
Update Removes the existing EARs and redeploys with the new installation Does not drop any existing tables Creates the required tables, if any are needed. Any matching resources are reused. Otherwise, new resources are created.

Configuration for Third Party Call over SIP/IMS

Configure the following custom properties on WebSphere Application Server (WAS) version 7.0.0.3:

  1. Open the WAS Integrated Solutions Console and navigate to Servers > WebSphere Application Servers > server_name > SIP container > Custom properties.
  2. Add a new custom property: immediate.replication = true.
  3. Add a new custom property end.of.service.replication = false.
  4. Save the changes to the master configuration and restart the application servers.

Call Handling default flow rewiring

In the Request part of the Call Handling default flow, the Message Interceptor (MI) mediation primitive's Fail terminal is connected to the input terminal of the SLA Cluster Enforcement (SLA) mediation primitive. The PX21_CH_Flow.ear file has the modified/updated version of the flow. It is available as part of the Access Gateway plug-in.

Those who prefer to use the default flow do not need to make any changes. For those who need to customize the Call Handling default flow apart from the custom changes, perform the following steps:

  1. Import PX21_CH_FLOW.zip as a Project Interchange on WID 6.1.0.102.
  2. Open the "ClearRules" operation in the Mediation Flow Editor.
  3. Delete the connection between the MI mediation primitive's Fail terminal and the SLA mediation primitive's input terminal.
  4. Connect the MI mediation primitive's Output terminal to the SLA mediation primitive's input terminal.

Additional information

First Steps changes

First Steps (FS) fails to run to completion when the server profile is created using a custom profile option. First Steps does not provide an option to select any specific service implementation while configuring the services; it automatically detects all installed services and configures them.  If you experience these issues and need to run the FS script again, retain the services/components that are required for your environment and delete the rest so that FS configures only those services that are required. Contact your IBM Support representative to get more help.

Customizing Third Party Call default flow

Those who prefer to use the Third Party Call default flow do not need to make any changes. For those who need to customize the Third Party Call default flow, perform the following steps:

  1. Import PX21_TPC_FLOW.zip as a Project Interchange on WID 6.1.0.102.
  2. Make the required changes.
  3. Export the project interchange and send it to the support team for building the EAR file.

Additional attributes for MLP Connector MBean

Three new attributes -- Service ID, Request Mode, and Requestor Required -- are added to the MLP Connector MBean.

Service ID:

Description: A unique ID assigned to the TWSS TL MLP SI by the MLP Location Server

Default value: Empty String

When the value for Service ID is a non-empty string, it is mapped to the element “client/serviceid” in the MLP Request XML. Otherwise “client/serviceid” will not be added to MLP Request XML.

 

Requestor Required:

Description - Determines whether to add a requestor element to the MLP Request XML.

Default value – true.

Possible options: true / false.

When true, the WAS User Principle is mapped to the element “requestor/id” in the MLP Request XML.

When false, the “requestor/id” will not be included in the MLP Request XML.

 

Request Mode:

Description – Type of the request to be sent to MLP Location Server.

Default value – NONE

Possible options: NONE/ACTIVE/PASSIVE

When it is NONE, the “client/requestmode@type” element will not be included in the MLP Request XML.

When it is ACTIVE/PASSIVE, the “client/requestmode@type” will be mapped to ACTIVE/PASSIVE.

 

MMS/MM7 service RFC2822 support

MT operations for RFC2822 email address can be performed using one of the following formats:

·                sip:+E.164/TYPE=PLMN@recipient-mmse

·                sip:+E.164@recipient-mmse

·                E.164@recipient-mmse

where “sip” is the schema part which identifies the email address format, “E.164” is the actual MSISDN number and “@recipient-mmse” is the email address domain.

Example:

sip:9886061490@in.ibm.com

sip:+9886061490@in.ibm.com

sip:+9886061490/TYPE=PLMN@in.ibm.com

 

Per the MM7 specification, the incoming MO's RFC2822 address should adhere to the following format:

+E.164/TYPE=PLMN@recipient-mmse

Example:
+358401234567/TYPE=PLMN@mmse.sonera.net

Configuring the DTD type and location for MLP protocol version 3.1

When you are using version 3.1 of the MLP protocol, check the availability of the DTD file MLP_SVC_INIT_310.DTD and other dependent DTD files on the Internet, for example http://www.openmobilealliance.org. If the DTD file is not available publicly, do not select "PUBLIC" for the "MLP DTD Type" MBean attribute and perform the following steps:

  1. Generate the required DTD files by extracting the content from the MLP 3.1 specification document.
  2. Place the DTD files in the local file system on the MLP Location Server (GMLC).
  3. To find the MBean attributes related to MLP Connector, navigate from the WebSphere Application Server Integrated Solutions Console to the TWSS Administration Console and select PX21_TL_MLP > MLP Connector.
  4. Select SYSTEM as the DTD Type using the MBean attribute MLP DTD Type.
  5. Specify the correct DTD location (in the local file system) using the MBean attribute MLP DTD Location.

When you are using version 3.2 of the MLP protocol, the MLP_SVC_INIT_320.DTD is available at the Open Mobile Alliance Web site.

Adding startPeriodicNotification for PX21_TL_Parlay SI

To add the startPeriodicNotification operation to PX21_TL_Parlay SI in the Admission Control operations list, perform the following steps:

  1. Open the WebSphere Application Server Integrated Solutions Console and navigate to TWSS Administration Console > Web Services Platform.
  2. Click Admission Control.
  3. Click Service/Operation Limits.
  4. Click PX21_TL_Parlay.
  5. Under Additional Properties, click Operations.
  6. Click New.
  7. Enter startPeriodicNotification in the Name field.
  8. Enter TL startPeriodicNotification in the Value field.
  9. Click Add.
  10. Click the operation startPeriodicNotification.
  11. Enter 1 in the Weight field.
  12. Enter 5000 in the Cluster Rate Limit field.
  13. Enter 1000 in the Server Rate Limit field.
  14. Click OK.
  15. Save changes to the master configuration.

Migrating the Usage Record database table from TWSS 6.2.x to TWSS 7.0.x

Before migrating the usage record data in DB2, perform the following:

  1. Create a buffer pool using the command: CREATE BUFFERPOOL USAGEDB32KBP all nodes SIZE 10000 AUTOMATIC PAGESIZE 32K;
  2. Create a table space using the command: CREATE TABLESPACE USAGEDB32KTS PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 256 PREFETCHSIZE 64 BUFFERPOOL USAGEDB32KBP NO FILE SYSTEM CACHING;
  3. Export the usage record data from the TWSS 6.2 table.
  4. Import the usage record data exported from the TWSS 6.2 table into the tablespace created in step 2.

Migrating the database for the Parlay connector

Before migrating the Parlay Connector data, perform the following steps:

  1. Tablespaces corresponding to Parlay Web services/Connector are created initially. This step is required only for systems that use a DB2 database.
    • CREATE BUFFERPOOL PARLAYPOOL SIZE 250 PAGESIZE 16K
    • CREATE REGULAR TABLESPACE PARLAYSPACE PAGESIZE 16 K MANAGED BY SYSTEM USING ('soatmp1') EXTENTSIZE 32 OVERHEAD 24.1 PREFETCHSIZE 16 TRANSFERRATE 0.9 BUFFERPOOL PARLAYPOOL
  2. Do not transfer the SERVERPROPERTIES table contents from the TWSS 6.2 database to the TWSS 7.0 database.
  3. Using Export and Import commands, transfer the contents of the CFGPROPERTIES table from the TWSS 6.2 database to the TWSS 7.0 database. The row entries in the CFGPROPERTIES table that start with PX21_Parlay. must be renamed to ParlayConnector. This must be done manually on the TWSS 7.0 database system.

Migrating Parlay applications

While migrating Parlay applications written for TWSS 6.2 to 7.0, note that callbacks using plain Java objects are not supported in v7.0. So any application using plain Java objects for callbacks need to be modified to implement the callbacks using stateless session EJBs. Also, the WebDial sample shipped with the Parlay Toolkit, which uses a Java object as a callback, will be removed.

In TWSS 7.0, all the scheduler classes and EJBs (com.ibm.wast.parlay.scheduler.*) are deprecated and will be totally removed. The scheduler was originally written to support event scheduling that could be used by the Parlay applications and the Parlay connector. From 7.0, it will be the responsibility of the Parlay applications to manage their events within their implementation.

Note: Because of this, notifications that were already created by applications (Terminal Location, Terminal Status, and SMS) using TWSS v6.2 cannot be used after migration.

Updates, limitations, and known problems

Updates, limitations, and known problems about Telecom Web Services Server are documented in technotes on the IBM Software Support Web site: http://www.ibm.com/software/pervasive/serviceserver/support/

As limitations and problems are discovered and resolved, the IBM Software Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems that you experience. The following link launches a customized query of the live Support knowledge base. To create your own query, go to the Advanced search page.

All technotes for Telecom Web Services Server Version 7.0.0:
http://www.ibm.com/support/search.wss?word=aw&wfield=&nw=&apar=include&tc=SS2PVA&atrn=SWVersion&atrv=7.0.0&atrn1=&atrv1=&atrwcs=on&lang=all&dr=all&r=10&cc=us&from=advs&loc=en_US&rs=3075&cs=utf-8&Submit.x=39&Submit.y=16

Trademarks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM, WebSphere, DB2, and AIX

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.