IBM WebSphere Diameter Enabler Component, Version 6.1.0.2 Readme

© Copyright International Business Machines Corporation 2006, 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

This fix pack addresses three issues that have been discovered in Diameter Enabler Version 6.1. It includes a fix for the method getMSISDN of the Sh Web service interface, a fix for the default discrimination weight for SSL, and a fix for the Mobile Subscriber ISDN Number (MSISDN) Attribute Value Pair (AVP) encoding and decoding.

Fix and update history

This fix pack includes APAR LI71409 and APAR LI71859.

APAR LI71409 includes the following fixes:

  • The method getMSISDN has been deprecated and replaced with the method getMSISDNList in order to properly support the Sh specification. See the Javadoc ™ for more details. As of this update, the method getMSISDNList should be used instead of getMSISDN.
  • The default discrimination weight value for SSL has been changed to 1, and the unsecured channel has been changed to 10, so that SSL works properly in a default installation.

APAR LI71859 includes the following fixes:

  • The MSISDN AVP is encoded in Telephony Binary Coded Decimal (TBCD) format in the Sh request packet. If an MSISDN AVP is received in a request or answer packet, it is expected to be in TBCD format and is decoded to UTF-8.
  • Prior to this fix, a grouped AVP was omitted if all of the enclosed, optional AVPs were not present. The lack of an optional AVP should not effect the transmittal of other AVPs in the same group. As part of this fix, a grouped AVP is included in the ACR packet if at least one of the enclosed AVP values is present as a web service parameter. For example, the Inter-Operator-Identifier (IOI) grouped AVP is included in the ACR as long as either the Originating-IOI or the Terminating-IOI value is present in the web service request.
  • A ClassNotFoundException was introduced in WAS 6.1.0.3 during server startup. Packaging of the Eclipse Modeling Framework jars changed in Fix Pack 3. References to org.eclipse.emf.common.util.EList became invalid and were changed to java.util.List.

Software compatibility

  • Operating Systems
    • Red Hat Enterprise Linux® AS 4.0 Update 4
    • SUSE Linux Enterprise Server 9 SP 3
  • Application Server
    • WebSphere® Application Server Network Deployment, Version 6.1.0.1
    • WebSphere Application Server Fix Pack 6.1.0.3 and iFix PK31203
  • Java ™
    • JDK ™, Version 1.5 (included with WebSphere Application Server Network Deployment, Version 6.1.0.1)
  • Databases
    • IBM DB2 Universal Database™ Version 8.2 FixPak 4
    • Oracle Database Version 10.2.0.1

 

Installation requirements

Hardware requirements

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

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

Software requirements

Software requirements for Diameter Enabler are included in the information center, and they have not changed since version 6.1.0. Refer to the following information for details:

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

 

Installation instructions

Before you begin:

  • Fix Pack 2 or Fix Pack 3 (WebSphere Application Server 6.1.0.2 or 6.1.0.3) has been applied to the server where the IP Multimedia Subsystem (IMS) Connector has been installed.
  • IMS Connector 6.1.0.0 or 6.1.0.1 has been installed.
  • Update Installer 6.1 must already be installed on the application server.
  • You must log in to the operating system as the actual root user in a UNIX® environment.
  • You must log in with the same root user authority level when unpacking a fix, fix pack or refresh pack.

To apply the fix pack, complete the following steps:

  1. Download the IMS Connector update installer package 6.1.0-WS-WAS-IMSConnector-FP000002.pak into the was_root/updateInstaller/maintenance directory.
  2. Start the update installer as described by WebSphere and select the IMS Connector fix pack to be installed. The update installer will update the was_root/installableApps directory with the DHADiameterShWebServiceEAR.ear. It will also update the was_root/diameter/Configuration directory with the DiameterChannelInstall.py and DiameterChannelUninstall.py scripts.
  3. If upgrading from 6.1.0.0, update the default discrimination weights for SSL via the admin console:
    1. Start the WebSphere Application Server 6.1 where the IMS Connector is installed.
    2. Open the Integrated Solutions Console and log in.
    3. Click Application servers->server1.
    4. Click Ports.
    5. Click the View associated transports link in the DiameterNamedEndPoint row.
    6. Click DiameterChain.
    7. Click Generic inbound channel.
    8. Change the discrimination weight to 10 and click OK.
    9. Return to the Transport Chain page and click SecureDiameterChain.
    10. Click Generic inbound channel.
    11. Change the discrimination weight to 1 and click OK.
    12. Save the changes.
  4. Update the Sh Web Service implementation:
    1. Start the WebSphere Application Server 6.1 where the IMS Connector is installed.
    2. Open the Integrated Solutions Console and log in.
    3. Click Applications->Enterprise Applications.
    4. Select the checkbox for the DHADiameterShWebServiceEAR application and click Update.
    5. Click Browse to find the EAR on the local file system.
    6. Select the file was_root/installableApps/DHADiameterShWebServiceEAR.ear.
    7. Click Next on the following screens, and click Finish in the summary screen.
    8. Save the changes.
  5. Update the Rf Web Service implementation:
    1. Start the WebSphere Application Server 6.1 where the IMS Connector is installed.
    2. Open the Integrated Solutions Console and log in.
    3. Click Applications->Enterprise Applications.
    4. Select the checkbox for the DHADiameterRfWebServiceEAR application and click Update.
    5. Click Browse to find the EAR on the local file system.
    6. Select the file was_root/installableApps/DHADiameterRfWebServiceEAR.ear.
    7. Click Next on the following screens, and click Finish in the summary screen.
    8. Save the changes.

Updates, limitations, and known problems

Updates, limitations, and known problems about Diameter Enabler are documented in technotes on the IBM Software Support Web site: http://www-306.ibm.com/software/pervasive/multisubcon/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 Diameter Enabler Version 6.1.0.2:
http://www1.ibm.com/support/search.wss?word=aw&wfield=&nw=&apar=include&tc=SS2P3U&tc1=SSC2P38&atrn=SWVersion&atrv=6.1.0.2&atrn1=&atrv1=&atrwcs=on&lang=all&dr=all&r=10&cc=us&from=advs&loc=en_US&rs=3073&cs=utf-8&Submit.x=45&Submit.y=17

Trademarks

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

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.

UNIX is a registered trademark of The Open Group in the United States and other countries.

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