IBM WebSphere Telecom Web Services Server Component, Version
6.2.0 Interim Fix 1 Readme
© 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
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 fix pack 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.
- ArrayOutOfBoundsException occurs on notifymgmt.ear: (APAR LI72617)
Corrects a problem in which the notifymgmt.ear gets an
ArrayOutOfBoundsException during the registerNotification method.
- Add configuration for the SMPP system_type PDU field: (APAR
LI72618) Corrects a problem in the SMS and WAP services for SMPP by adding a
configuration setting in the network mapper Administration Console page. The
administrator can use this setting to specify the value of the system_type
field that is used during the Bind Transceiver operation.
- Memory leak in SMS, WAP, and MMS services: (APAR LI72622) Corrects
a problem in the SMS, WAP and MMS service EARs and the SMPPConnector.rar that
results in a memory leak.
- Service Policy Manager Console hangs: (APAR LI72628) Corrects a
problem in the Service Policy Manager Console that may result in the browser
looping or hanging and requiring the user to exit the browser.
- Missing SMS Resources cause stack dump in trace log: (APAR LI72628)
Corrects a problem in the SMS service where a few resources were missing from
a resource file causing exceptions to be dumped into the trace log. This was
harmless but appeared to be a problem.
- Added Attachment Size limit policy to Access Gateway: (APAR
LI72628) Corrects a problem in the Access Gateway by enforcing limits on the
size of attachments sent to the system.
Software compatibility
- Operating systems:
- Red Hat Enterprise Linux ® AS 4.0 Update 5
- SUSE Linux Enterprise Server 9 SP 3
- AIX ® 5L 5.3 TL 05 SP 6
- Application server
- WebSphere Application Server Network Deployment, Version 6.1.0.11
- iFix PK49611
- iFix PK52139
- iFix PK53626 (part of the the 6.1.0.11-WS-WAS-IFSIP_101707 cumulative
package)
- iFix PK53885
- iFix PK54131 (part of the the 6.1.0.11-WS-WAS-IFSIP_101707 cumulative
package)
- WebSphere Application Server Enterprise Service Bus, Version 6.0.2.2
- iFix IC53828
- iFix JR27493
- WebSphere Integration Developer, Version 6.0.2.2
- Java™
- JDK, Version 1.5 (included with WebSphere Application Server Network
Deployment)
- Databases
- IBM DB2 Universal Database™ Version 9.1 FixPak 2
- Oracle Database Version 10.2.0.2
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:
To apply the fix pack, complete the following steps:
- Verify that WebSphere Application Server (WAS) version is 6.1.0.11, and
that the appropriate iFix or iFixes have been applied.
- 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.
- Download the Websphere Update Installer version 6.1.0.11 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
- Download the IMS UPDI Plugins package 6.2.0.0-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.
- Download the TWSS Update Installer package
6.2.0-WS-WAS-TWSS-AG-IF000001.pak into the
WAS_ROOT/updateInstaller/maintenance directory on the Access Gateway servers.
- Download the TWSS Update Installer package
6.2.0-WS-WAS-TWSS-SP-IF000001.pak into the
WAS_ROOT/updateInstaller/maintenance directory on the Service Platform
servers.
- Download the TWSS Update Installer package
6.2.0-WS-WAS-TWSS-Services-IF000001.pak into the
WAS_ROOT/updateInstaller/maintenance directory on the Service Platform
servers.
- 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-IF000001.pak contains updates to the Access Gateway.
The 6.2.0-WS-WAS-TWSS-SP-IF000001.pak contains updates to the Service
Platform and should be installed before the services.
The
6.2.0-WS-WAS-TWSS-Services-IF000001.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.
- Update the component EARs that are deployed on the application server:
- Start WebSphere Application Server where the component is installed.
- Open the Integrated Solutions Console and log in.
- Click Applications > Enterprise Applications and select the
appropriate Application EAR.
- Click Uninstall.
- 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
Configuration instructions
The configuration for TWSS is the same as that describes in the InfoCenter,
except where described 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:
- Log in to the Integrated Solutions Console.
- In the navigation panel, click Environment > Naming > Name Space
Bindings.
- Select cell_name for the Scope, and click Apply.
- 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:
- Click New.
- Click String for the binding type, and click Next.
- Type SOAP_attachment_part_max_size for the Binding Identifier.
- Type sca/attachments/MaxSizeAttachmentPart for the Name in Name
Space.
- 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'.
- Click Finish, and click Save to save changes to the master
configuration.
- 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:
- Click New.
- Click String for the binding type, and click Next.
- Type SOAP_attachment_max_size for the Binding Identifier.
- Type sca/attachments/MaxSizeAttachments for the Name in Name
Space.
- 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'.
- 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 focussed techniques that may provide improved results. If you experience
poor database perforamnce after completing this command please consult the
database administrator and inquire about using other techniques to improve the
database performance.
db2 reorgchk update statistics on table all
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.