IBM WsT Telecom Web Services Server Component, Version 7.0.0.1

© 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 fix pack

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

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

Fix and update history

This fix pack 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 

  • 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. Refer to the Configuration Instructions section for more details.
  • Access Gateway - WAPush 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 the Additional Information section 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 Sevice Implementation Web Service, Issue related to higher latency (APAR LI74722): Corrects the problem related to the higher latency on database interactions when there is a higher number of transactions per second (TPS).
  • SMS over SMPP Sevice Implementation Web Service, Issue related to concatination 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: Refer to the Configuration Instructions section for details.
  • 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 the Additional Information section for details on the FS related issues and changes.
  • 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.

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
  • 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
  • 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 

Viewing the Changed File.list in the Update Installer .pak file

Update installer .pak files are delivered in .zip format. To view the contents of a .pak file, use any archiving tool that can read .zip files. The Java jar tool can also extract the files.list file from the .pak file.

7.0.0-WS-WAS-TWSS-SP-FP000001.pak\repository\twss.sp\files.list

7.0.0-WS-WAS-TWSS-AG-FP000001.pak\repository\twss.esb\files.list

7.0.0-WS-WAS-TWSS-Services-FP000001.pak\repository\twss.svc\files.list

To view the contents, type jar -tf fixpack_name.pak

To extract the files.list, type jar -xf fixpack_name.pak repository/twss.svc/files.list

Next, you can use an editor to view the files.list, which lists all of the files to be changed for the .pak file.

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 information:

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

Installation instructions

Before you begin, ensure that the following service has been applied to the application server for the Access Gateway the and Service Platform.

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.

To apply the fix pack, complete the following steps:

  1. Verify that the WebSphere Application Server (WAS) ND version is 6.1.0.23, and that the appropriate iFix or iFixes have been applied.
  2. Verify that the WebSphere Application Server Enterprise Service Bus (ESB) version is 6.1.0.2.
  3. 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
  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 and the Service Platform Application servers.
  5. 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 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.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
  6. Download the TWSS Update Installer package 7.0.0-WS-WAS-TWSS-AG-FP000001.pak to the WAS_ROOT/updateInstaller/maintenance directory on the Access Gateway servers.
  7. Download the TWSS Update Installer package 7.0.0-WS-WAS-TWSS-SP-FP000001.pak to the WAS_ROOT/updateInstaller/maintenance directory on the Service Platform servers.
  8. Download the TWSS Update Installer package 7.0.0-WS-WAS-TWSS-Services-FP000001.pak to the WAS_ROOT/updateInstaller/maintenance directory on the Service Platform servers.
  9. 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-FP000001.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-FP000001.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-FP000001.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.
  10. Update the component EARs that are deployed on the application server:

Follow the instructions in the information center to update the Application EARs included in the fix pack. Refer to the following instructions:

    1. WAS 6.1.x:   http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/trun_app_upgrade_console.html
    2. WAS 7.x:    http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/trun_app_upgrade_console.html  

Configuration instructions

The configuration for TWSS is the same as that described in the InfoCenter, 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 due to duplicate entries of TWSS admin console links in the navigation.xml file of 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>
  5. ·  Save and close the navigation.xml file
  6. ·  Start the deployment manager, node agents, and servers.

Call Handling Default Flow Rewiring

In the Request part of Call Handling default flow the Message Interceptor (MI) Mediation Primitive's Fail terminal being connected to the input terminal of 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 the PX21_CH_FLOW.zip as a Project Interchage 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 which are required for your environment and delete the rest so that FS configures only those services that are required. Contact your IBM Support represeentative 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 the 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 support team for building the EAR file.

 

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.