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

Contents

• About this fix pack
  • Fix and update history
  • Software compatibility
• Installation requirements
  • Hardware requirements
  • Software requirements
• Installation instructions
• Uninstall instructions
• Updates, limitations, and known problems
• Trademarks

About this fix pack

This fix pack contains fixes and minor improvements for the IBM® WebSphere® Telecom Web Services Server (TWSS), Version 6.1.1 release. This fix pack is recommended for all customers with a TWSS 6.1.1 installation.

This fixpack is installed using the WebSphere UpdateInstaller and well as some manual updates.

Fix and update history

This fix pack includes the following APARs and fixes:

• Third Party Call Failover: (APAR LI71831) Corrects a problem with session attributes containing underscore characters and conflicting with SIP Container processing during failover.
  
• Configurable maximum message size for SendSms: (APAR LI71967) Provides configurable maximum message size in Admin console. This allows the user to choose maximum message size as more than 254 in order support the payload functionality.
  
• Message payload has been implemented: (APAR LI71967) The message payload was not previously used. By using the payload, the user can send a message up to 64K in size.
  
• Support for WAS 6.1.0.3: This fixpack adds additional support for WAS 6.1.0.3. This required a minor change to a number of EAR files. The following files have been updated:
  • admission.ear
  • faultalarm.ear
  • networkresources.ear
  • pxnotification.ear
  • traffic.ear
  • usage.ear
  • thirdparty.ear
  • callnotify.ear
  • payment.ear
  • presence.ear
  • termstatus.ear
  • parlayear.ear
  • smppear.ear
  
  
• Compatibility Issues with Lucent Parlay Gateway: (APAR LI71967) Parlay SMS service is unable to send messages or receive mobile originated messages. TWSS Parlay SMS service has been updated to allow for implementation differences with the ISG Multi-Media Messaging service.
  

Software compatibility

• Operating Systems:
  • Red Hat Enterprise Linux ® AS 4.0 Update 4
  • SUSE Linux Enterprise Server 9 SP 3
  • AIX ® 5.3 SP 5300-04-01
• Application Server
  • WebSphere Application Server Network Deployment, Version 6.1.0.3
  • iFix PK31203
  • iFix PK35193
• Java™
  • JDK, Version 1.5 (included with WebSphere Application Server Network Deployment, Version 6.1.0.3)
• Databases
  • IBM DB2 Universal Database™ Version 8.2 FixPak 4
  • Oracle Database Version 10.2.0

Installation requirements

Hardware requirements

Hardware requirements for TWSS are included in the information center and have not changed since version 6.1.1. Refer to the following information for details:

http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/index.jsp?topic=/com.ibm.twss.doc/com_prereqs.html

Software requirements

Software requirements for TWSS are included in the information center. Refer to the following information for details: http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/index.jsp?topic=/com.ibm.twss.doc/com_prereqs.html

In addition to the prerequisites listed in the information center, the following maintenance fixes are required:

WebSphere Application Server Version 6.1.0.3 must be applied to the base WebSphere Application Server for the Service Implementations. The fix pack can be retrieved from the following link: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24013772

Additionally, the WebSphere Application Server iFix PK31203 is also required, and provides a fix to the SIP Proxy. The fix is located at http://www-1.ibm.com/support/docview.wss?uid=swg24014163

The WebSphere Application Server iFix PK35193 is also required, and provides a fix to a memory leak. The fix is located at http://www-1.ibm.com/support/docview.wss?uid=swg24014591

Installation instructions

Before you begin, ensure that the following steps have been completed:

• Fix Pack 3 (WebSphere Application Server Version 6.1.0.3) has been applied to the application server where the Service Implementations are installed
• iFix IFPK31203 has been applied to the application server where the Service Implementations are installed
• iFix IFPK35193 has been applied to the application server where the Service Implementations are installed

To apply the fix pack, complete the following steps:

1. Verify WebSphere Application Server version is 6.1.0.3, and the iFix or iFixes are applied.
   
2. If you have an earlier TWSS fixpack installed through Update Installer, it should be uninstalled. These TWSS Update Installer fixpacks are cumulative.
3. Download the TWSS Update Installer package 6.1.1-WS-WAS-TWSS-SP-FP000001.pak into the WAS_HOME\updateInstaller\maintenance directory.
4. Download the TWSS Update Installer package 6.1.1-WS-WAS-TWSS-IMSServices-FP000001.pak into the WAS_HOME\updateInstaller\maintenance directory.
5. Start the Update Installer as described by WebSphere, and select the TWSS fixpack(s) to be installed. The 6.1.1-WS-WAS-TWSS-SP-FP000001.pak should be installed first, followed by the 6.1.1-WS-WAS-TWSS-IMSServices-FP000001.pak. The updateInstaller will update the WAS_HOME\installableApps\TWSS-Base and WAS_HOME\installableApps\TWSS-IMS directory contents, but not deploy them onto the application server.
6. Update the component EARs that are deployed on the application server:
   
   1. Start the WebSphere Application Server 6.1 where the common components and service implementations are installed.
   2. Open the Integrated Solutions Console and log in.
   3. Click Applications->Enterprise Applications and select the appropriate Application EAR.
   4. Click Uninstall.
   5. Follow the instructions in the information center to install the new EARs included in the fix pack. Refer to the following instructions:
      • Installing Common Components: http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/topic/com.ibm.twss.install.doc/deploy_cc_t.html
      • Installing SIP Services: http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/topic/com.ibm.twss.install.doc/deploy_services_c.html
   
   
7. Download the TWSS Parlay Services update IBM_WebSphere_Telecom_WebServices_Server_ParlayServices_6.1.1.1.tar.gz.
8. Follow these instructions to install the Telecom Web Services Server Parlay Services fixpack.
   1. Extract the fixpack tar file, IBM_WebSphere_Telecom_WebServices_Server_ParlayServices_6.1.1.1.tar. The extract will have smppEAR.ear and SMPPConnector.rar file.
   2. Find the SMPP EAR at the location: IBM_WebSphere_Telecom_WebServices_Server_ParlayServices_6.1.1.1.tar/ears/smpp/SmppEAR.ear
   3. Find the Connector RAR at the location: IBM_WebSphere_Telecom_WebServices_Server_ParlayServices_6.1.1.1.tar/rar SMPPConnector.rar
   4. Before installing, check whether smppEAR.ear, SMPPConnector.rar are already installed in WebSphere Application Server. If so, uninstall both.
   5. Install the smppEAR and SMPPConnector RAR from the fixpack package extracted above. To install the smppEAR, refer to the following installation instructions: http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/index.jsp?topic=/com.ibm.twss.install.doc/deploy_smpp_ear_t.html
   6. To install SMPPConnector RAR, refer to the following installation instructions: http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/topic/com.ibm.twss.install.doc/jca_adapter_t.html
   7. After completing EAR and RAR installations, restart the WebSphere Application Server.
   
   

Uninstall instructions

The TWSS product InstallShield installers provide an uninstaller. The uninstaller will not uninstall Update Installer .pak files. If you need to uninstall the TWSS components, uninstall any Update Installer packages first. Then use the product InstallShield uninstallers.

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-306.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. Each of the following links 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 6.1.1.1:
http://www-1.ibm.com/support/search.wss?word=aw&wfield=&nw=&apar=include&tc=SS2PVA&atrn=SWVersion&atrv=6.1.1.1&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

WebSphere HTTP Proxy does not route Web Service Requests

The WebSphere Proxy Server does not route Web Services requests in a cluster. A HTTP 500 internal error may result along with a NullPointerException when this problem occurs. There are two possible workarounds for this problem:

• Add an empty SOAP header in this manner: <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header /> <soapenv:Body> <p756:makeCallResponse xmlns:p756="http://www.csapi.org/schema/parlayx/third_party_call/v2_3/local"> <p756:result>wsaixlab56.1171559563921.3_1</p756:result> </p756:makeCallResponse> </soapenv:Body> </soapenv:Envelope>
• Use the HTTP Web Server Plugin instead of the WebSphere Proxy Server.

Trademarks

The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM, WebSphere, DB2 Universal Database, 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.