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

© Copyright International Business Machines Corporation 2007, 2008. 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 is a cumulative fix which includes all the latest changes for the IBM® WebSphere® Telecom Web Services Server (TWSS), Version 6.2.0 This interim fix is recommended for all customers with a TWSS 6.2.0 installation.

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

Fix and update history

This interim fix includes the following APARs and fixes. This package includes all fixes for the Access Gateway, Service Policy Manager, Service Platform components, and TWSS Web service implementations.

Interim Fix 001

Interim Fix 002

Interim Fix 003

Interim Fix 004

Fix Pack 001

Interim Fix 005

Software compatibility

 

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.

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 6.2.0. Refer to the following information for details:

http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/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/v6r2m0/topic/com.ibm.twss.doc/com_prereqs.html

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

Installation instructions

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

Note: In this section, WAS_ROOT refers to the WebSphere home directory, for example /opt/IBM/WebSphere/AppServer.

To apply the fix pack, complete the following steps:

  1. Verify that the WebSphere Application Server (WAS) version is 6.1.0.11, and that the appropriate iFix or iFixes have been applied.
  2. Verify that the WebSphere Application Server Enterprise Service Bus (ESB) version is 6.0.2.2, and that the appropriate iFix or iFixes have been applied.
  3. If you have an earlier TWSS fix pack that was installed using the Update Installer, uninstall it. The TWSS Update Installer fix packs are cumulative.
  4. Download the WebSphere Update Installer version 6.1.0.13 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 6.0 and the Service Platform which is based on WAS 6.1
  5. Download the IMS UPDI Plugins package 6.2.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.
  6. 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 6.2.0.1 fixpack. For details see the IMS Update Installer Plugins installation page for fix pack 6.2.0.1: http://www.ibm.com/support/docview.wss?uid=swg24017457
  7. Download the TWSS Update Installer package 6.2.0-WS-WAS-TWSS-AG-IF000005.pak into the WAS_ROOT/updateInstaller/maintenance directory on the Access Gateway servers.
  8. Download the TWSS Update Installer package 6.2.0-WS-WAS-TWSS-SP-IF000005.pak into the WAS_ROOT/updateInstaller/maintenance directory on the Service Platform servers.
  9. Download the TWSS Update Installer package 6.2.0-WS-WAS-TWSS-Services-IF000005.pak into the WAS_ROOT/updateInstaller/maintenance directory on the Service Platform servers.
  10. Start the Update Installer as described in the WebSphere documentation, and select the TWSS fix pack(s) to be installed.
    The UPDI Plugins package should be installed first to each server.
    The 6.2.0-WS-WAS-TWSS-AG-IF000005.pak contains updates to the Access Gateway.
    The 6.2.0-WS-WAS-TWSS-SP-IF000005.pak contains updates to the Service Platform and should be installed before the services.
    The 6.2.0-WS-WAS-TWSS-Services-IF000005.pak contains updates to the TWSS Services.

    The Update Installer updates the WAS_ROOT/installableApps/TWSS-Base and WAS_ROOT/installableApps/TWSS-Services directory contents, but does not deploy the updates onto the application server.

  11. Update the component EARs that are deployed on the application server:
    1. Start WebSphere Application Server where the component is 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: http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.install.doc/intro_c.html
  12. Review iFix contents for updated database initialization (.ddl) files or policy initialization script (.py) files, and use them to initialize the database or policies according to the instructions in the InfoCenter.

 

Configuration instructions

The configuration for TWSS is the same as that described in the InfoCenter, except as specified in either the TWSS 6.2.0 Readme (WebSphereProductsForTelecomReadme.html) or this Readme.

Attachment Limit Configuration

This iFix defines a default SOAP attachment size limit of 1 MB, requiring that the size of any one attachment or the combination of all attachment parts passed on a Web service request not exceed this limit. This iFix also adds the ability to override the default attachment size limit through the use of name space bindings. There are two name space binding values that can be defined to set the size limit for attachments: one to set the individual size limit for attachment parts and the second to set the overall limit for all attachments.

To change the default SOAP attachment size limit, complete the following steps on the deployment manager and synchronize the changes with all nodes:

  1. Log in to the Integrated Solutions Console.
  2. In the navigation panel, click Environment > Naming > Name Space Bindings.
  3. Select cell_name for the Scope, and click Apply.
  4. To change the default maximum size of an attachment part that can be attached to an inbound message, create a name space binding for the SOAP attachment part maximum size:
    1. Click New.
    2. Click String for the binding type, and click Next.
    3. Type SOAP_attachment_part_max_size for the Binding Identifier.
    4. Type sca/attachments/MaxSizeAttachmentPart for the Name in Name Space.
    5. Type the maximum allowed size of an attachment part for a given message. This is an integer number measured in MBytes (when followed by 'M' or 'm'), or KBytes (when followed by 'K' or 'k'), or bytes (when followed by 'B' or 'b'). The default value used is '1M'.
    6. Click Finish, and click Save to save changes to the master configuration.
  5. To change the default maximum size of all attachment parts that can be attached to an inbound message, create a name space binding for the SOAP attachment maximum size:
    1. Click New.
    2. Click String for the binding type, and click Next.
    3. Type SOAP_attachment_max_size for the Binding Identifier.
    4. Type sca/attachments/MaxSizeAttachments for the Name in Name Space.
    5. Type the maximum allowed size of all attachment parts for a given message. This is an integer number measured in MBytes (when followed by 'M' or 'm'), or KBytes (when followed by 'K' or 'k'), or bytes (when followed by 'B' or 'b'). The default value used is '1M'.
    6. Click Finish, and click Save to save changes to the master configuration.

system_type configuration

In either the SMS or WAP applications for SMPP, use the TWSS Administration Console to locate the Network Mapper configuration page. That page contains an additional configuration setting for the value used in the system_type field of the SMPP Bind Transceiver operation.

reorgchk to optimize DB2 performance

DB2 relies upon calculated values for optimal performance. The database catalog statistics and the physical organization of the data in the tables are used to provide optimal database performance. Catalog statistics should be recomputed periodically as the data in the tables changes. This need is greatest after periods of heavy data modifications (inserts, updates, and deletes) such as during initial population or periodic purge activities. These calculations are CPU intensive and block access to the database while they run. We recommend this maintenance be performed during an appropriate service window.

The DB2 reorgchk command is the simplest way to count and record the statistical details about tables, indexes and columns. There are other more tightly focused techniques that may provide improved results. If you experience poor database performance after completing this command, consult the database administrator and inquire about using other techniques to improve the database performance.

db2 reorgchk update statistics on table all

No J2C activation specification for the MM7 Resource Adapter

When installing the MM7Connector.rar (MM7 Resource Adapter), there is no J2C activation specification associated with that adapter. Therefore, when you use the procedure titled "Installing the JCA adapter for SMPP and MM7-based Web service implementations" in the InfoCenter (http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/topic/com.ibm.twss.install.doc/jca_adapter_t.html), you should skip step 4 when deploying Parlay X Multimedia Messaging over MM7.

Disabling PMI improves performance

The TWSS 6.2.0.0 product readme recommends turning off PMI (Performance Monitoring Interface) in order to avoid a performance problem. There is a more specific method of disabling the specific PMI metrics that cause the performance problem, which allows PMI to be generally used.

  1. In the WAS Administration Console, on the left side, click Monitoring and Tuning > Performance Monitoring Infrastructure (PMI).
  2. Select the correct application server instance. This should be done for each application server instance when in a cluster.
  3. Ensure that Enable PMI is checked.
  4. Click Custom.
  5. On the left side of the customization area, select Web Applications.
  6. Select URIConcurrentRequests, URIServiceTime, and URIRequestCount.
  7. Select Disable.
  8. Save the changes and restart the server.

Performance improvement for DNS lookups

If you experience very slow response from the TWSS Administration Console or Parlay Administration Console, particularly on AIX, this can be due to poor or unpredictable response times from the DNS server. The Java JVM provides a system property com.ibm.cacheLocalHost that can be set to true. This will improve lookups of the localhost IP address. This Java JVM system property should be set in the Process Definition for the Deployment Manager and all Application Server instances.

Additional Configuration for MMS/MM7 service

Additional configuration settings for MM7 optional parameters has been introduced to the MMS Administration Console configuration that enables these MM7 protocol fields to be set appropriately to interoperate with various MMS-C servers. Most notably are the additional settings for VASPID, VASID, Distribution Indicator. See the help provided for these settings in the Administration Console after installing the updated EAR file.

Additional Configuration for Access Gateway and PX Notification when security is disabled at Access Gateway

Using PX Notification when security is disabled at the Access Gateway requires additional configurations such as User Name for PX Notification and the requesterExceptionList in Access Gateway.

To configure the PX Notification properties like User Name:

  1. Log in to the Administration Console that contains the TWSS Service Platform common components.
  2. In the left pane, expand TWSS Administration Console -> Web Services - > Clusters.
  3. Click the cluster name.
  4. In the Web Service Platform pane, click PXNotification.ear.
  5. In the Component Configuration pane, click PXNotification Delivery Web Service.
  6. In the Runtime properties pane enter a User Name and optionally a Password.
  7. Click OK and save the changes.

To configure the requesterExceptionList:

  1. Log in to the Administration Console that contains the TWSS Access Gateway default flow(s).
  2. In the left pane, expand Applications.
  3. Click SCA modules.
  4. In the SCA Modules pane, click one of the installed TWSS Access Gateway default flows.
  5. In the Configuration pane under Additional properties, click Module properties.
  6. Locate the MsgElementRemover.request.requesterExceptionList property. This property is a comma-delimited list of requesters for which the configured message element will not be removed.
  7. Set or add the user name you used to configure the PX Notification Delivery Web Service User Name property.
  8. Click OK and save the changes.

Both changes will become effective after the save is completed. No server restart is needed.

Additional Configuration for ALM over XDMS when security is disabled for Access Gateway

A new service policy, service.config.UserName, is added to the Address List Management over XDMS Web service implementation. The new policy accepts the user name value and needs to be configured at the Service Policy Manager. This configuration enables the Access Gateway and Address List Management systems to run with security off while using the user name (for basic authentication or asserted identity) and passing it to XDMS when security is on at XDMS. When the requester ID is specified, it will take precedence over the user name.

The precedence is Requester ID -> User Name from Service Policy -> UNAUTHENTICATED.

The following topic in the IBM WebSphere XDMS information center provides the required information on creating proper access rights when the value for the service.config.UserName service policy is different from the actual owner of the document.

http://publib.boulder.ibm.com/infocenter/wtelecom/v6r2m0/index.jsp?topic=/com.ibm.xdms.doc/grantingmanyidentitiesreadaccesstoalldocumentsinadirectory.html

Example: User Name service policy value is sip:bob@ibm.com and the actual owner for the document is sip:john@ibm.com. Access rights need to be created for sip:bob@ibm.com to read, write, update, or administer the documents owned by sip:john@ibm.com.

Additional configuration for Message Logger mediation primitive in TWSS Access Gateway

The following technote (IC53621) from WebSphere Application Server ESB provides a workaround when you require triggers or stored procedures with the Message Logger mediation primitive database table on Oracle.

http://www.ibm.com/support/docview.wss?uid=swg1IC53621

Functionality improvement to TWSS common components

This fix addresses the issue related to the XA exception when a TWSS common component (Usage Records, Notification Management or PxNotification ) interacts with the JMS queue or with database tables.

Functionality improvement to SMS over SMPP Failover

New functionality to enable the SMS over SMPP service to recreate binding with the SMSC after the TWSS system restarts.

Functionality improvement to Parlay Connector

New functionality in the Parlay Connector to maintain a unique assignment ID across the cluster even if the assignmentID changes between the managed service manager objects at the Parlay gateway. This functionality requires the PARLAYDB to be recreated. See the TWSS 6.2 information center for details about creating the database.

Public interface for TWSS Service Platform API

New interface for TWSS Service Platform to ease the creation of custom Web Services using TWSS.

Additional configuration for SMS/SMPP service

A new configuration parameter, Connection re-try interval, has been introduced to the SMS SMPP ENQUIRELINK MBean in TWSS SMS Administration Console configuration. It provides an option to configure the time interval used to trigger the connection bind. It is used for establishing the connection with the SMSC when it has valid notifications at the time of TWSS server start. The default value is 3 minutes. The valid range is 3-60 minutes. See the help provided for these settings in the Administration Console after installing the updated EAR file.

Additional information

The SMS over SMPP and WAP Push over SMPP Web services cannot coexist on the same application server.

Additional Configuration for MMS/MM7 service

Run MmsDataDb2.ddl or MmsDataOra.ddl to update the table MMSSENDDATA with the column MESSAGEID. Verify that a new column with name MESSAGEID is created.

To configure the Destination Element:

  1. Log in to the Administration Console that contains the TWSS Service configuration.
  2. In the left pane, expand TWSS Administration Console -> Web Services - > Clusters.
  3. Click the cluster name.
  4. In the Web Service pane, click IMS Multimedia Messaging.
  5. In the Component Configuration pane, click Multimedia Messaging Web Service.
  6. Under the Destination Element attribute, select the appropriate destination element depending on the DeliveryReportReq from the gateway. This field defines the element to be used to get the destination number. This configuration option is used to switch between the Sender and Recipient element of DeliveryReportReq depending on the MMSC's interpretation of the MM7 spec.
  7. Click OK and save the changes.

Additional Configuration related to callback endpoint for TL/MLP service

The callback endpoint is being used in the StartPeriodicNotification & StartGeographicalNotification operations. The configurable Callback Endpoint provides an option to configure the endpoint to receive MO/notification messages. It is mandatory to configure a callback endpoint before attempting to start the notification operations. Otherwise the system would give a MalformedURLException.

To configure the Callback Endpoint address:

  1. Log in to the Administration Console that contains the TWSS Service configuration.
  2. In the left pane, expand TWSS Administration Console -> Web Services - > Clusters.
  3. Click the cluster name.
  4. In the Web Service pane, click PX21_TL_MLP.
  5. In the Component Configuration pane, click Terminal Location Notification Web Service.
  6. In the Runtime properties pane enter a Callback Endpoint:

    This is the callback endpoint URL where the callback server is listening for MO-Notification messages from an MLP location server. Example value: http://HostName:PortNumber/TWSS/ParlayX21/TerminalLocation/MLPCallback/services/MLPCallBack. When a firewall is in place, replace the HostName and PortNumber values with the firewall router's IP address & Portnumber and map the WebSphere Application Server (WAS) deployment manager's IP address and PortNumber with those of the firewall, as routing point. When there is no firewall, replace HostName & PortNumber with the WAS Deployment Manager's IP address and PortNumber.

  7. Click OK and save the changes.

Additional Configuration related to DataCoding for WAPPush/SMPP service

To configure the DataCoding in WAPPushSMPPNetworkAttributeMBean

  1. Log in to the Administration Console that contains the TWSS Service configuration.
  2. In the left pane, expand TWSS Administration Console -> Web Services - > Clusters.
  3. Click the cluster name.
  4. In the Web Service pane, click WAP10_PUSH_SMPP.
  5. In the Component Configuration pane, click WAPPush Backends.
  6. Click on the backend that is configured. On the backend configuration panel, select 8_bit_binary_GSM_23_038_a as the DataCoding value
  7. Click OK and save the changes.

Uninstall instructions

The TWSS product InstallShield installers provide an uninstaller. However, the uninstaller does not uninstall Update Installer .pak files. To uninstall 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.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 6.2.0:
http://www.ibm.com/support/search.wss?word=aw&wfield=&nw=&apar=include&tc=SS2PVA&atrn=SWVersion&atrv=6.2.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 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.