The FixPack note contains the following sections:
This FixPack contains the following revisions since the last maintenance release :
Available as of
Version |
APAR/CR Number |
Feature |
Description |
1.0.3.1TF |
CR 71299 |
Synchronous Request Processing Performance |
Performance has been improved during Synchronous Request Processing. Connection Pooling to connect to remote TCPIP server has been provided. |
1.0.3.1TF |
CR 70741 |
BO_Verb Support in Static MO |
Support for BO_Verb attribute has to be provided for the TCPIP Adapter during Request/Outbound Processing. |
1.0.3.1TF |
CR 48205 |
Base64 Encoding |
Support for Base64 Encoding of Incoming Data and Base64 Decoding of Outgoing Data. This can be done through configuration properties. |
1.0.3 |
CR 59860 |
Migration of Adapter to Adapter Framework v2.6.0 |
The Adapter has been migrated to AF 2.6.0. This also included making the Adapter jar compatible with JDK 1.4.x. |
1.0.3 |
CR 45571 |
Chabge to start scripts of Adapter. |
'Connector' has been removed from '-n${CONNAME}Connector' in start_TCPIP.sh and start_TCPIP.bat. |
1.0.2 |
CR 48040 |
Additional feautures in Request Processing |
The below feautures have been provided in Request Processing:
1. Async and Sync Request processing.
2. Code change so that Request Processing can bypass Message Handlers.
3. Change in Request Processing to handle Sync flow. The Response BO is set in the Adapter and not the Message Handler |
1.0.2 |
CR 61361 |
Namespace Conflict with ICS as Broker. |
BIA_ApplicationMessage Map invoked during Event and Request processing was same. Now they have been made different and added to Inbound and Outbound sections of the Map. |
1.0.2 |
CR 61633 |
Async Event Processing |
During Async Event processing Adapter was trying to write data to the Client. This has been rectified. |
1.0.1 |
CR 44170 |
Event Processing Bug |
TCPIP Adapter sends one byte data to the TCPIP client, to check if it is Alive, during Event processing. |
1.0.1 |
CR 44171 |
Globalization bug during Event Processing. |
The adapter hard codes US_ASCII to default encoding during Event Processing. |
1.0.1 |
CR 44204 |
Response handling during Request Processing. |
TCPIP adapter cannot handle Response, other than status, during Request processing. |
1.0.1 |
CR 60794 |
Request Processing Bug. |
TCPIP adaper fails to instantiate Data Handler properly, during Request Processing, in certain scenarios. |
Add, replace, or remove the following files and directories as indicated (Note that these are rolled up in the FixPack you downloaded):
For Connector Version |
Platform |
Add / Replace / Remove |
File (Starting from %CROSSWORLDS% / $CROSSWORLDS) |
1.0.3.1TF |
WIN & UNIX |
Replace the file | Replace the connector jar with the new jar file provided with the fix.Also create a new CFG file from the connector configuration template, BIA_TCPIPAdapterTemplate, provided. |
1.0.3 |
WIN & UNIX |
Replace the file | Replace the connector jar with the new jar file provided with the fix. Replace the old Adapter start scripts with the new start scripts. Ensure that you invoke the connector controller(affected due to CR 45571 above), with ICS as broker, appropriately. Ensure that AF 2.6.0 is installed and connector folder within 2.6.0 AF installation. |
1.0.2 |
WIN & UNIX |
Replace the file | Replace the connector jar with the new jar file provided with the fix. Replace the Map BO repository with the BO repository provided with the Build BIA_TCPIPAdapterRepository.zip. |
1.0.1 |
WIN & UNIX |
Replace the file | connectors\TCPIP\BIA_TCPIP.jar for Windows AND connectors/TCPIP/BIA_TCPIP.jar for Unix |
Configure the following for the FixPack to work:
Connector |
Platform |
Add / Remove |
Property/Legal values (Case-Sensitive) |
1.0.3.1TF |
WIN & UNIX |
Add |
Add EnableBase64Encoding to ServerConfiguration of CFG. Add EnableBase64Decoding to ClientConfiguration of CFG. Set both to false if Base 64 encoding and decoding is not required. Else set to true. Add ConnectionPoolSize to CFG. Set ConnectionPoolSize in Client Configuration of CFG to size of Connection Pool to contact the remote TCPIP Server. |