IBM WebSphere Telecom Web Services Server, Version 7.1 Interim Fix 3 Readme
© Copyright International Business Machines Corporation 2010. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
· Updates, limitations, and known problems
This interim fix is recommended for all customers with a TWSS 7.1 installation using MMS/MM7, SMS/SMPP, WAPPush/SMPP web service implementation on all supported platforms. This Interim fix can be installed using the WebSphere Update Installer and through manual updates.
This package cumulatively includes the following fixes:
Interim Fix 001
· Access Gateway - Issue related to SOAP messages with attachments in the PX21_MMS_FLOW (APAR LI75489): This addresses the problem of attachments that were not being propagated for the PX21_MM_FLOW. All customers using WsT 7.1 Access Gateway’s Multimedia Messaging flow must install this iFix.
Interim Fix 002
· Access Gateway - MMS Default Flow, Issue related to maximum size attachment validation (APAR LI75671): This fix addresses the problem by performing a check in the handler to validate the size of the attachment against the Namespace binding set as part of the environment variable.
·
Access Gateway – WebContainer threads hung during callback
notification (APAR LI75671): This fix addresses the problem by appropriately
unlocking a synchronized block in the PolicyRetrieval
mediation primitive. This is invoked as part of the request flow when an ESB
callback notification is triggered from the Service Platform.
·
CallHandling over SIP Service
Implementation Web Service (APAR LI75671
): Issue related to exceptions for higher TPS (> 80). This fix addresses the problem related to obtaining a Proxy object outside a dialog when there are a higher number of transactions per second (TPS).
· SMS over SMPP Service Implementation Web Service (APAR LI75671): This fix addresses the issue related to Multiple notifications on the same target with Null criteria. This problem is resolved by validating the criteria and not allowing multiple null values.
· First Steps (FS), Truncation string displayed on FS under WASND (APAR LI75671): This fix addresses the problem of displaying the test in FS for the fields related to Configuration Mode, Database Driver Path, JMS Queue Mode, JMS Queue Path, JMX Administrator User Name, TWSS Username, and password.
Interim Fix 003
·
MMS over MM7 Service Implementation Web Service (APAR LI75725):
The issue is seen when the MMSC is using a MM1/MM4 PLMN address format for the
· MMS over MM7 Service Implementation Web Service (APAR LI75829): This fix addresses the problem of the encoding of subject line used by the MMSC of MO Message according to the RFC 2047.
· SMS over SMPP Service Implementation Web Service (APAR LI75752): This fix addresses the problem by splitting a Thai message correctly and sending all the segments to the destination address without any loss of data
· SMS over SMPP Service Implementation Web Service (APAR LI75830): This fix addresses the problem caused by multiple SMS request in synchronous mode when connecting to the backend server. This is addressed by providing multiple JCA connections for multiple requests.
· WAPPush over SMPP Service Implementation Web Service (APAR LI75734): This fix addresses the problem by splitting a Thai message correctly and sending all the segments to the destination address without any loss of data.
Note: To limit the attachment
size, the Name space binding has to be configured in the WebSphere Application
Server administration console as described in the following step-wise procedure:
1. Go to Environment -> Naming -> Name Space Bindings.
2. Click New.
3. Click String for the binding
type, and then click Next.
4. In the Binding Identifier field, type (or paste) MaxSizeAttachments.
5. In the Name in Name Space field, type sca/attachments/MaxSizeAttachments.
6. In the String Value field, specify the maximum size, in bytes, of all
attachment parts . The value is an integer followed by
the suffix M, m, OK, OK, B, or b. The default value is 1M (1 megabyte).
7. Click Next.
8. Click Finish.
9. Click Save to save changes
to the master configuration.
Note: To limit the attachment
parts, the Name space binding has to be configured in the WebSphere Application
Server administration console as described in the following step-wise
procedure:
1. Go to Environment -> Naming -> Name Space Bindings.
2. Click New.
3. Click String for the binding
type, and then click Next.
4. In the Binding Identifier field, type (or paste) MaxSizeAttachmentPart.
5. In the Name in Name Space field, type sca/attachments/MaxSizeAttachmentPart.
6. In the String Value field, specify the maximum size, in bytes, for any
single attachment part . The value is an integer
followed by the suffix M, m, OK, OK, B, or b. The default value is 1M (1
megabyte).
7. Click Next.
8. Click Finish.
·
Red Hat
·
SuSE
Linux
· AIX® 5L 5.3 TL 10 SP1 or 6.1 TL 3 SP2
· Solaris 10 (5.10)
· WebSphere Application Server Network Deployment, version 7.0.0.7 or 6.1.0.29
· WebSphere Enterprise Service Bus version 7.0.0.1 or 6.2.0.2 (which includes the corresponding version of WebSphere Application Server Network Deployment above)
|
APAR |
File Name |
|
|
7.1.0-WS-WAS-TWSS-AG-IF000003.pak |
|
LI75725, LI75752, LI75734, LI75829, LI75830 |
7.1.0-WS-WAS-TWSS-Services-IF000003.pak |
|
|
7.1.0-WS-WAS-TWSS-SP-IF000003.pak |
|
|
7.1.0-WS-WAS-TWSS-WIDPlugins-IF000003.zip |
· IBM SDK, version 1.6 SR 6 (included with WebSphere Application Server Network Deployment, version 7.0.0.7)
· IBM SDK, version 1.5 SR 11 (included with WebSphere Application Server Network Deployment, version 6.1.0.29)
· IBM DB2® Enterprise Server Edition version 9.5.0.4 or 9.7.0.1
· Oracle Database version 11.1.0.7 or 11.2.0.1
Hardware requirements for TWSS are included in the information center. For details, refer to:
http://publib.boulder.ibm.com/infocenter/wtelecom/v7r1m0/topic/com.ibm.twss.doc/com_hw_prereqs.html
Software requirements for TWSS are included in the information center. For details, refer to the Software compatibility section of this Readme and to:
http://publib.boulder.ibm.com/infocenter/wtelecom/v7r1m0/topic/com.ibm.twss.doc/com_sw_prereqs.html
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\WID62 or C:\IBM\WID7
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. Download the WebSphere Update Installer version 7.0.0.7 on the Access Gateway application server.
4. 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.
5. Ensure 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 fix pack). You need to download and run a reset script available on the support download site which will then allow installation of TWSS 7.1 Interim fix 001. 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
6. Download the TWSS Update Installer package 7.1.0-WS-WAS-TWSS-AG-IF000003.pak to the WAS_ESB_ROOT/updateInstaller/maintenance directory on the Access Gateway servers.
7. Download the TWSS WID plugin iFix package 7.1.0-WS-WAS-TWSS-WIDPlugins-IF000003.zip to a temporary folder and unzip the contents into the folder <WID_HOME>/TWSS folder. It should have extracted the PX21_MM_FLOW.zip file which contains the WID flow.
8. Start the Update Installer as described in the WebSphere documentation, and select the TWSS fix pack(s) to be installed.
1. Install the UPDI Plugins package on each of the deployment managers of the WESB clusters.
2. Install the 7.1.0-WS-WAS-TWSS-AG-IF000003.pak which contains updates to the Access Gateway on the deployment manager and all nodes for the Access Gateway.
3. The Update Installer updates the WAS_ESB_ROOT/lib/ext directory and the WAS_ESB_ROOT/installableApps/TWSS-Base directory.
9.
Download the TWSS Service iFix
package 7.1.0-WS-WAS-TWSS-Services-IF000003.pak to the WAS_ROOT/updateInstaller/maintenance directory on the Service
Platform servers.
10. Update the component EARs that are deployed on the application server by running TWSS First Steps with 'Update' option.
The configuration for TWSS is the same as that described in the TWSS 7.1 information center.
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.
Technote related to this iFix for Telecom Web Services Server Version 7.1.0:
http://www-01.ibm.com/support/docview.wss?uid=swg21430449
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.