IBM WebSphere Telecom
Web Services Server Component, Version 6.1.1 Interim Fix 6
© 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.
This Interim fix contains fixes for the SMS over SMPP Web service implementation associated with IBM® WebSphere® Telecom Web Services Server (TWSS), Version 6.1.1. This Interim fix is recommended for all customers with a TWSS 6.1.1 installation.
The following SMS over SMPP Web
service fixes are included:
1) SMS SMPP throws WorkCompletedException.
APAR LI72529
A resource adapter was not able to create new endpoints.
2) SMS SMPP throws ArrayIndexOutofBound Exception while
processing empty PDU or MO message with empty commandlength.
APAR LI72535
3) SMS SMPP throws XAException
APAR LI72534
4) SMS SMPP throws TransactionRolledbackException.
APAR LI72480
A NullPointerException while processing
sendEnquireLinkResponse resulted in transactions being rolled back.
5) SMS SMPP throws TransactionRolledback Exception while
processing GenericNack PDU.
APAR LI72562
A problem occurred while processing a GenericNack PDU
response: SMS for SMPP received a GenericNack PDU from a particular backend,
but it sent back response PDUs to all connected backends. This resulted in a
TransactionRolledbackException.
6) NullPointerException for SMPP Interaction set to null.
APAR LI72559
7) Charging info made configurable
APAR LI72537
Charging information is made configurable and policy
driven. You can establish a policy to send charging information in all segments
of a large message or in only one segment.
APAR LI72537
A new policy, service.config.ChargeForFirstSegmentOnly,
supports sending charging information in message segments. The policy accepts
Boolean values, which result in the following settings:
For multi-segmented messages, True means that TWSS
includes charging information in the first segment only. False means
that TWSS includes charging information in all segments.
For single-segmented messages, TWSS includes the charging
information in the segment, regardless of what value you specify for
service.config.ChargeForFirstSegmentOnly.
If the policy is not set, the default value is true.
8) SMS SMPP throws workRejected exception under load
conditions.
APAR LI72536
9) Work timeout error in load environment.
APAR LI72560
A database operation to fetch the target scheme for a
destination number returned all records of the destination number. This
resulted in increased execution time and later caused a work timeout error. The
database operation is tuned to return a single correct record.
10) sms/smpp- avoid race condition and retries in db updates.
APAR LI72561
A race condition resulted in retries for database updates
for message status, resulting in increased execution time.
11) SMS SMPP throws Policy exception if priorityEnabled is
not set.
APAR LI72554
If the policy priorityEnabled was not set in the request,
SMS for SMPP returned the following error: "POL0010: A policy error
occurred. Error code is SOAM1567. Policy is
service.custom.priorityEnabled".
In this fix, if priorityEnabled is not set, it is assumed
to be false.
12) Tuning trace output of byte data in PeerConnection for
efficient execution.
APAR LI72578
Trace statements for outputting byte data were inefficient
and executed even when tracing was disabled.
13) SMS SMPP throws TransactionRolledbackLocalException
APAR LI72579
Starting and stopping of the enquire link and purge timers
has been introduced in cluster start/stop events. This prevents the cluster env
timer from receiving null input, which resulted in
TransactionRolledbackLocalException exceptions.
14) Increase WorkManager's start time to handle high load.
APAR LI72580
15) Memory leak in SMPP connector
APAR LI72622
During long runs of
16) Multiple binds happening while sending multi segmented
message.
APAR LI72624
17) SMS/SMPP throws SocketException in cluster environment
APAR LI72595
18) Add indexing to SMS data table.
APAR LI72625
19) Mismatch b/w the NID in submit_sm_resp,deliver_sm.
APAR LI72594
20) Add message id format property in the ESMC.properites
file.
APAR LI72626
For compatibility with SMSCs that support Hexadecimal/Decimal
in submit_sm_resp for Message ID, a new property, esmc.message.id.format,
is added in esmc.properties. It is an opaque value and will be set according to
the SMSC implementations. It is is set by default to HEXADECIMAL.
Formatting example: esmc.message.id.format = HEXADECIMAL
When set to HEXADECIMAL, TWSS will convert the message_id value in the
deliver_sm PDU from decimal to hexadecimal. When set to DECIMAL, TWSS
does not convert the message_id value in the deliver_sm PDU.
21) Add configuration for the SMPP system_type PDU field.
APAR LI72618
Corrects a problem in the SMS for SMPP Web service implementation 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.
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:
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:
Before you begin, ensure that the following steps have been completed:
Following are the steps to install this
Interim fix.
IBM_WebSphere_Telecom_WebServices_Server_ParlayServices_6.1.1_1_IF000006.tar.gz
The fix
contains SmppEAR.ear , SMPPConnector.rar files and ddl files for creating SMS
data tables. The ddl files are present for both DB2 and Oracle databases.
When the fix
file is extracted, following files can be found under the extract folder:
The ddl files are now added with
indexing. Depending on the database used (DB2 or Oracle), run the appropriate
ddl file to create the SMS data tables.
Refer the infocenter to get exact steps
on how to create the SMS data tables using the new ddl file given in the fix.
You can set this as JVM custom property for the appserver.
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
Check the infocenter documents for any
setup changes.
Also, refer to the TWSS 6.1.1 fixpack 1
readme for more information on base TWSS and IMS service updates.
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.1.1.1:
http://www.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
The following terms are trademarks of International
Business Machines Corporation in the United States, other countries, or both:
IBM, WebSphere, AIX, DB2, and DB2 Universal Database
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.