IBM WebSphere Telecom Web Services Server, Version 7.2 Interim Fix 5 Readme

© Copyright International Business Machines Corporation 2014. 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 applies to IBM® WebSphere® Telecom Web Services Server (TWSS) - Base, Services and WIDPlugin Version 7.2 installation using Firststeps on all supported platforms. This interim fix is installed using IBM Installation Manager.

Fix and update history

Interim Fix 001:

• APAR LI76433 - Firststeps - Issue related to configuration parameters in Firststeps console: This fix removes the necessity of providing JMXAdminUsername and JMXAdminPassword when security is disabled. JMXAdminUserName and JMXAdminPassword is required only if security is enabled.

• TWSSVersionInfo and TWSSFeatureInfo - These two scripts are available when iFix001 is installed using IBM Installation Manager.
  • TWSSVersionInfo.sh lists the version of IBM WebSphere Telecom Web Services Server Base (TWSS-Base), IBM WebSphere Telecom Web Services Server Service (TWSS-Services), along with any installed Interim Fix.
  • TWSSFeatureInfo.sh lists the installed features of IBM WebSphere Telecom Web Services Server Base and IBM WebSphere Telecom Web Services Server Services.
    • To list TWSS Base features, "-b" is passed as an argument; that is, "TWSSFeatureInfo.sh -b".
    • To list TWSS Services features, "-s" is passed as an argument; that is, "TWSSFeatureInfo.sh -s".

Note: IBM Installation Manager should be stopped while executing these two scripts.

Note: TWSSFeatureInfo script is supported in IBM Installation Manager, Version 1.4.4 and above.

Interim Fix 002:

• APAR LI76861 - This fix resolves the following problem: X-3GPP-Asserted-Identity is not propagated to the MMS Web Service Implementation as TAI does not allow the request to pass through when security is enabled.
• APAR LI76872 - This fix resolves the MMS Mobile Originated(MO) message Validation fails at the Service Implementation
• APAR LI76938 - This fix resolves the NullPointerException thrown by the TL/MLP Web Service Implementation when other than the default back-end alias is specified

Note: Run the dos2Unix command against the following scripts TWSSVersinInfo.sh and TWSSFeatureInfo.sh to eliminate the ^M character.

Interim Fix 003:

• APAR LI77213

  This fix resolves the following problems: Validation of appropriate backend server aliases based on the SPM policies for range and target aliases , The target addresses are validated based on fifteen-digit numbering space, TL/MLP service implement will allow empty string for MBean property Service ID.

This fix resolves the issue of TWSS interim fix packaging, now it displays same fix version for all TWSS offering (i.e Base , Services and WIDPlugins).

This fix resolves the Control M or ^M issue while executing TWSSVersionInfo.sh TWSSFeatureInfo.sh shell scripts.

Interim Fix 004:

• APAR LI77593 - This fix adds the 'TARGET' attribute to usage record service data column on performing MMS sendMessage operation.
• APAR LI77729 - This fix resolves the issue of updating the wrong deliverystatus i.e 'DeliveredToTerminal' when SMSC returns a status as REJECTD in SMPP Deliver_SM (Customer was sending senderAddress with more than 11 characters and SMSC rejected)
• APAR LI77730 - This fix resolves the issue of SAR message segmentation when encoding is set to 'UCS2 GSM 23.038' and message sent using sendSms operation is longer than configured backend property MaxMessageSize. The issue reported was that TWSS SMS/SMPP Service Implementation was not sending correct segment message length and there were no SAR optional parameters in SUBMIT_SM PDU.
• APAR LI77732 - This fix resolves the issue of not able to notify to the third party application when SMSC was sending Concatenated SMS messages having extra User Data Header(UDH) information as part of Mobile Originated(MO) messages, now the TWSS SMS/SMPP Service Implementation takes care of the User Data Header Information.

Note: Run the dos2Unix command against the following scripts TWSSVersinInfo.sh and TWSSFeatureInfo.sh to eliminate the ^M character.

Interim Fix 005:

• APAR LI777817 - This fix resolves the issue of SMS purge on ORACLE database. The issue reported was that when the SMS purge was enabled, and purge interval and purge block were set, instead of purging the records from tables SMSSENDDATA, SMSNOTIFICATIONDATA, SMSRECEIVEDATA and SMSOBJECTDATA, an SQL exception was being thrown.
• APAR LI77819 - This fix resolves the issue of MMS purge on ORACLE database. The issue reported was that when the MMS purge was enabled, and purge interval and purge block were set, instead of purging the records from tables MMSSENDDATA, MMSNOTIFICATIONDATA and MMSRECEIVEDATA, an SQL exception was being thrown.
• APAR LI77897 - This fix resolves the issue of MMS MO/MT attachment purge. The issue reported was that when the MMS purge was enabled, and purge interval and purge block were set, the records from the associated MMS tables, MMSATTACHCONTENT and MMSATTACHMETADATA were not purged during purge cycle. Another issue was after executing getMessage(), records were getting purged only from MMSRECEIVEDATA table and not the attachment tables. Now these issue are fixed, all related records from attachment tables are purged in the order of expiretime and block size

Note: Run the dos2Unix command against the following scripts TWSSVersinInfo.sh and TWSSFeatureInfo.sh to eliminate the ^M character.

Software compatibility

Operating Systems:

• Red Hat Enterprise Linux® AS 5.5
• SuSE Linux Enterprise Server 11
• AIX® 5.3 TL 12 or 6.1 TL 5 SP2 or 7.1
• Sun Solaris 10 (64-bit on Intel; or 32-bit and 64-bit on Sparc)

Application Server:

• WebSphere Application Server Network Deployment, Version 7.0.0.15
• WebSphere Enterprise Service Bus, Version 7.0.0.3 (which includes the corresponding version of WebSphere Application Server Network Deployment as mentioned above)
• IBM SDK, Version 1.6.0 SR 9 (included with WebSphere Application Server Network Deployment, Version 7.0.0.15)

Database

• IBM DB2® Enterprise Server Edition, Version 9.5 or 9.7
• Oracle Database, Version 11.2

Installation Manager

• Installation Manager 1.4.4

Installation requirements

Hardware requirements

Hardware requirements for TWSS are included in the information center. For more information, see Hardware requirements.

Software requirements

Software requirements for TWSS are included in the information center. For more information, see Software requirements and the Software compatibility section of this Readme file. 

Installation instructions

Note: In this section:

• IM_ROOT refers to the Installation Manager home directory. For example: /opt/IBM/InstallationManager/.
• WAS_ROOT refers to the WebSphere Application Server (WAS) home directory. For example: /opt/IBM/WebSphere/AppServer/.

To install TWSS Base and Service platform Interim Fix complete the following steps:

Note: To install the TWSS-Service iFix005 on the Service Implementation environment, first select TWSS Bases iFix005 and then the TWSS Service iFix005 to install using the Installation Manager.

To install TWSS WIDPlugin Interim Fix in the developement enviroment, complete the following steps:

Post Installation instructions for Interim Fix 005

Once the 7.2.0.0-WebSphere-TWSS-Services-IF005 is installed using the Installation Manager, the PX21_MM_MM7 & PX21_SMS_SMPP application EAR's will need to be manually deployed on the Service Platform environment using the WAS Administration console.

Note: If Interim Fix 001 is being installed: Consider the scenario where you have installed the TWSS-Base GM build without the Firststeps feature, and you have installed iFix002 on top of this. Later, you install Firststeps using the Modify option available in IBM Installation Manager. In such a scenario, if you attempt to uninstall iFix001, IBM Installation Manager gives a "Failed to find all Installation Files" error. Hence, before uninstalling iFix002, set the repositiry.config file of TWSS-Base GM build in IBM Installation Manager at File > Preferences > Add Repository.

Note: If iFix001 is uninstalled, TWSS-Base reverts to the GM version and the FirstStepsInfo.properties file (WAS_ROOT/installableApps/TWSS-Base/firststeps) gets modified. There are two methods to revert to the original values in the properties file:

• Edit the following fields in the FirstStepsInfo.properties file:
                          locale = %LOCALE%
                     locale_display_name = %LOCALE_DISPLAY_NAME%
                     locale_display_name_in_English = %LOCALE_DISPLAY_NAME_IN_ENGLISH%
  And change the values to:
                          locale = en_US
                     locale_display_name = English (United States)
                     locale_display_name_in_English = English (United States)
• Using the Modify option of IBM Installation Manager, uninstall Firststeps and install it again.
  

Configuration instructions

The configuration for TWSS is the same as that described in the TWSS 7.2 information center.

Updates, limitations, and known problems

Other updates, limitations, and known problems about Telecom Web Services Server are documented in technotes on the IBM Software Support website.

The technote related to this iFix for Telecom Web Services Server, Version 7.2.0 is available here.

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.

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.