IBM WebSphere Telecom Web Services Server Component, Version 6.1.0.1 Readme
© Copyright International Business Machines Corporation 2006.
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 contains fixes and minor improvements for the IBM® WebSphere® Telecom Web Services Server (TWSS), Version 6.1.0
release, including a fix for session propagation
across the Telecom Web Services Access Gateway and several minor fixes to the service
implementations. This fix pack is recommended for all customers with a TWSS 6.1.0
installation.
Fix and update history
This fix pack includes the following APARs and fixes:
- ESB session propagation fix: (APAR LI71390) Corrects a problem in which previous sessions
are erroneously propagated when sending a mix of Web service stateful and non-stateful traffic. This caused subsequent requests to include HTTP cookies from previous
requests during Web service calls through the WebSphere Enterprise Service Bus (ESB). After applying this fix, cookies are
correctly propagated for any mix of stateful and stateless traffic.
- Removal of warning logging messages from SystemOut.log for the Third Party Call
Service Implementation: (APAR LI71400) Changes several warning messages into trace
messages. The messages are produced during normal operation of the service and do not
need to appear in the SystemOut.log. The messages can be viewed when
tracing is enabled.
- Fix to Terminal Status DDL: (APAR LI71400) Provides a default definition for the
Terminal Status getStatusForGroup() Web service operation within the Admission Control
common component during database initialization. This results in the following message
appearing in the SystemOut.log:
[7/26/06 10:19:59:930 EDT] 00000053 PivotHandlerW W com.ibm.ws.webservices.engine.PivotHandlerWrapper invoke WSWS3734W: Warning: Exception caught from invocation to com.ibm.ws.webservices.engine.dispatchers.java.JavaBeanDispatcher:
WebServicesFault
faultCode: {http://www.ibm.com/schema/soa/admctl/v1_0/local}NoAdmissionControlDefinedFault
faultString: com.ibm.soa.sp.admctl.NoAdmissionControlDefinedFault
faultActor: null
faultDetail:
com.ibm.soa.sp.admctl.NoAdmissionControlDefinedFault
Prior to this fix, the operation could still be defined manually in the Admission Control
section of the Telecom Web Services Server administration console. This automates defining this
operation with a default value during database initialization.
- Removal of non-existent JAX-RPC log handler from PX Notification: (APAR LI71400) This fix removes
a reference to a non-existent JAX-RPC handler within the PX Notification deployment descriptors.
This defect fixes the behavior where a ClassNotFoundException would be printed to the logs
when sending an outbound Call Notification service implementation notification request.
Software compatibility
- Operating Systems:
- Red Hat Enterprise Linux ® AS 4.0 Update 3
- SUSE Linux Enterprise Server 9 SP 3
- Application Server
- WebSphere Application Server Network Deployment, Version 6.1.0.2
- 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
Installation requirements
Hardware requirements
Hardware requirements for TWSS 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.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/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:
WebSphere Application Server Version 6.0.2.13 must be applied to the base WebSphere Application Server for the
WebSphere Enterprise Service Bus. This fix pack contains a fix for a memory leak within the Web Service client
engine. The fix pack can be retrieved from the following link:
http://www-1.ibm.com/support/docview.wss?uid=swg27004980#ver60
Additionally, the WebSphere Application Server iFix 6.0.2.10-WS-WAS-TFPK29364.pak is also required. This iFix
can be applied either before or after the 6.0.2.13 fixpack is applied. The fix is located at
http://www-1.ibm.com/support/docview.wss?uid=swg1PK29364
Installation instructions
Before you begin, ensure that the following steps have been completed:
- Fix Pack 13 (WebSphere Application Server Version 6.0.2.13) has been applied to the application server where the Telecom Web Service Gateway is installed
- iFix TFPK29364 has been applied to the application server where the Telecom Web Service Gateway is installed
- The WESB_HOME environment variable is defined as the directory where WebSphere ESB is installed
To apply the fix pack, complete the following steps:
- Verify WebSphere ESB base WebSphere Application Server version is 6.0.2.13.
- Create a directory to unzip the 6.1.0.1 updates. For example:
mkdir /tmp/twss-6.1.0.1
- Unzip IBM_WebSphere_Telecom_WebServices_Server_Base_6.1.0.1.tar.gz and IBM_WebSphere_Telecom_WebServices_Server_IMS_6.1.0.1.tar.gz in the temporary
directory.
- To install the ESB session propagation fix:
- Make a backup copy of the esb-handlers.jar file:
mv WESB_HOME/lib/ext/esb-handlers.jar
$WESB_HOME/lib/ext/esb_handlers_6.1.0.bak
- Copy the updated JAR file to the extensions directory:
mv /tmp/twss-6.1.0.1/esb-handlers.jar $WESB_HOME/lib/ext/esb-handlers.jar
- Update the PX Notify component:
- Start the WebSphere Application Server 6.1 where the common components and service implementations are installed.
- Open the Integrated Solutions Console and log in.
- Click Applications->Enterprise Applications and select PX Notification.
- Click Uninstall.
- Follow the instructions in the information center to install the new pxnotification.ear included in the fix pack. Refer to the following instructions: http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/topic/com.ibm.twss.install.doc/deploy_sp_pxnotification_t.html
- Update the Third Party Call service implementation:
- Start the WebSphere Application Server 6.1 where the common components and service implementations are installed.
- Open the Integrated Solutions Console and log in.
- Click Applications->Enterprise Applications and select Third Party Call.
- Click Uninstall.
- Follow the instructions in the information center to install the new thirdparty.ear included in the fix pack. Refer to the following instructions: http://publib.boulder.ibm.com/infocenter/wtelecom/v6r1/topic/com.ibm.twss.install.doc/deploy_service_thirdparty_t.html
- The AdminTs*.ddl files contain database initialization scripts for the Terminal Status service
implementation. These DDL files define the getStatusForGroup() Web service operation. You can define this operation
manually within the TWSS Administration Console; there is no need to reinitialize the database
if it is already initialized. For new installations, these DDL files should be overwritten with the
new DDL files prior to database initialization. The following describes the manual steps for adding
the operation definitions in the administration console in order to avoid database reinitialization:
- Start the WebSphere Application Server 6.1 where the common components and service implementations are installed.
- Open the Integrated Solutions Console and log in.
- Click TWSS Administration Console->Web Services Platform.
- Click the configuration you are administering:Cluster or a Single server. If you selected a cluster, click the appropriate cluster
name.
- Click the Admission Control.ear common component.
- Click Service/Operation Limits->TerminalStatus_IMS->Operations.
- Click New, and type the following as the operation name: getStatusForGroup
- Provide appropriate defaults. Suggested defaults are:
- Weight: 1
- Cluster Rate Limit: 5000
- Server Rate Limit: 1000
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-306.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.
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 Telecom Web Services Server Version 6.1.0.1:
http://www-1.ibm.com/support/search.wss?word=aw&wfield=&nw=&apar=include&tc=SS2PVA&atrn=SWVersion&atrv=6.1.0.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
Trademarks
The following terms are trademarks of International Business Machines Corporation
in the United States, other countries, or both: IBM, WebSphere, and DB2
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.