Fix Readme
Abstract
This document contains release information for Financial Transaction Manager for ACH / Check / CPS Services for Multiplatforms v3.0.2, and describes known issues and changes from previous releases.
Content
Financial Transaction Manager for ACH Services, Check Services, and Corporate Payment Services V3.0.2 Release Information
Table of Contents
Common Across Releases
...Known Issues
...Changes
...General Instructions
...Upgrade Procedure
...Prerequisites and Co-requisites
...Prior to Installation
...Installation
......Create a New Installation
......Update an Existing Installation
...Necessary Tasks after Installation
...Uninstalling if Necessary
3.0.2.1 Release
...3.0.2.1 iFix 1
...3.0.2.1 iFix 2
...3.0.2.1 iFix 3
...3.0.2.1 iFix 4
...3.0.2.1 iFix 5
...3.0.2.1 iFix 6
...3.0.2.1 iFix 7
...3.0.2.1 iFix 8
...3.0.2.1 iFix 9
...3.0.2.1 iFix 10
...3.0.2.1 iFix 11
...3.0.2.1 iFix 12
...3.0.2.1 iFix 13
...3.0.2.1 iFix 14
...3.0.2.1 iFix 15
...3.0.2.1 iFix 16
...3.0.2.1 iFix 17
...3.0.2.1 iFix 18
...3.0.2.1 iFix 19
...3.0.2.1 iFix 20
...3.0.2.1 iFix 21
...3.0.2.1 iFix 22
...3.0.2.1 iFix 23
3.0.2.0 Release
Known Issues
IBM Integration Bus and Linux ODBC driver
On Linux, we have observed incompatibilities between IBM Integration Bus v9 and generic ODBC Database Extender (IE02). Use the IE02 package that ships with the IBM Integration Bus to avoid the issue.
IBM Sterling Connect:Direct
On Linux, the 4.2.0.3-SterlingConnectDirectforUNIX-Linux-x86-iFix014 package has a defect that causes Connect:Direct to not work in the product. This problem will be corrected in a later release of the Connect:Direct package.
Database
If your database is on z and you have to perform a forced end of day, you will get a database exception. This is a known DB2 client driver issue that is being resolved in a future DB2 release level. The DB2 client that exhibits this issue is version 3.66.46, which ships with DB2 version 10.1 for z/OS. The fix will be in DB2 client 3.70.* versions of the db2jcc driver.
WebSphere Application Server 8.5.5.9 or later
WebSphere Application Server (WAS) v8.5.5.9 or later is not supported when running with Java SDK 6 earlier than version 6.0.1 Service Refresh 8 Fix Pack 30 due to WAS APAR IV84524. Either use WebSphere Application Server feature for Java SDK 7 or obtain Java SDK version 6.0.1 Service Refresh 8 Fix Pack 30 (PI66070: SHIP JAVA 6/26 SR8 FP30 FOR WSAS V8.5.0.X AND V8.5.5.X) or later.
Data Setup Utility
The following documents describe the changes for the data setup utility (DSU) and the import and export workbooks:
DSUmigration_v3.0.2.pdf
DSUMigrationBR_v30.2.pdf
Which can be downloaded from Fix Central at:
Check
3.0.2-FTM-Check-MP-Documents .
CPS
3.0.2-FTM-CPS-MP-Documents .
Database migration
For database migration instructions refer to the migration instructions in {Install location}\shared\vnnn\pfs\Database\{os}\doc
Transaction Server Scheduler XML
The following document describes the changes to the scheduler XML for the Transaction Server component:
TransactionServerSchedulerChanges_v3.0.2.pdf
Which can be downloaded from Fix Central at:
Check
3.0.2-FTM-Check-MP-Documents .
CPS
3.0.2-FTM-CPS-MP-Documents .
General Instructions
Migration
Migration by running two installations in parallel is described in the following document:
FTM_PFS_Parallel_migration.pdf
Which can be downloaded from Fix Central at:
Check
3.0.2-FTM-Check-MP-Documents .
CPS
3.0.2-FTM-CPS-MP-Documents .
WebSphere Application Server
All WebSphere Servers must be restarted after all components have been updated.
Internet Explorer (IE) in Compatibility mode
Some FTM Control Center pages will not render correctly in the Compatibility View of IE 11, because it emulates an older IE version.
Solution
The older IE versions are not supported but the following may work for you.
1. Navigate to Administration > System > Properties
2. Open the System Property "HTTP Response Headers". This has a default value and a custom value.
3. Edit
4. Add "X-UA-Compatible: IE=edge" to this list of headers.
-If there is a custom value defined for this property, add a pipe character to the end of the current value, and then add this new header.
-If there is no custom value defined for this property, we recommend the user to copy the default value into the custom value, and then add a pipe character, and then add this new header.
5. Restart server so that the new HTTP Response Headers are used when visiting pages.
Explanation
This new response header will force pages to display as IE11 when being viewed with Compatibility mode.
Upgrade procedure
To upgrade an existing installation for a fix pack the following tasks need to be performed:
Prerequisites and co-requisites
Prior to installation
Before installing a fix pack, perform the following steps:
Installation
Create a new installation
Mod Releases and Fix Packs can be used to create a new installation. Interim Fixes (iFixes) cannot be used to create a new installation and can only be used to update an existing installation.
Update an existing installation
Deployment
Necessary tasks after installation
Verify the correct build information. See 'Build Date' listed in the table below.
Uninstalling if necessary
To rollback to a previous version:
Before uninstalling, insure the applications in the install location are not running:
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
Feature Changes
The following SOAP Web Services have been removed:
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
No feature changes.
Note: This section contains changes from the 3.0.2.0 release.
Compatibility Matrix
Because the development of releases and interim fixes (iFixes) for maintenance are done in parallel, a later release might not contain every interim fix that was created for an earlier release. The following table shows you which releases and interim fix levels can be successfully upgraded to V3.0.2, Fix Pack 1.
In the following table, the "If you're on version" column shows you the releases that can be upgraded successfully. The highest release or interim fix level that can be upgraded for each release is shown in the "To successfully upgrade to V3.0.2, Fix Pack 1, you must be no higher than version" column. If the release that you are upgrading from is at an interim fix level that is higher than the release or fix level that is shown in the right column, you can't upgrade the release without losing some changes. The upgrade needs to occur at the next release.
For more information about the individual changes in a release or interim fix, see the fix list for this version.
Known Issues
[All] The "(Action) Pending work authorization" handles the refuse and release actions. Users with this permission will be able to refuse an accepted transmission. The work around: limit the number of users granted this permission and avoid refusing a non-pending transmission.
[All] In the migration to FTM4C version 3.0.1 or above, three UI properties were merged into a single property called HTTP Response Headers. An issue with the migration could cause this parameter to contain an invalid value if it was empty in the original 3 properties. To address this, navigate to Administration -> System -> Properties. If the Custom field of the HTTP Response Headers property is set with a valid value, no action is required. If the field is blank, edit the property to remove any white space or use the query UPDATE FTM.CORE_PROPERTIES SET VALUE = NULL WHERE KEY = 'framework.http.resp.hdr'.
Feature Changes
Control Total Verification Processing
[All] The purpose of the new functionality is to reduce the number of inbound file notifications to one. The notification will contain information regarding all validation errors found within the file and failures that occurred executing Control Total Verification (CTV) due to missing CTV files.
The inbound file will be ingested normally to complete both CTV and additional validation. When the ingestion process is completed, and no CTV has been received, the inbound physical transmission will be set to the “Processed” state and the inbound transmission will be placed in a “Pending” state. A single notification will then be sent back to the sender detailing that the CTV file has not yet been received along with any additional issues detected during file validation. To generate a single notification, the Control Total service will no longer default to sending a Control Total Alert. Instead, the Transmission Acknowledgement will include the error code configured in the missingControlTotalErrorCode property. When the CTV file is finally received, the CTV process will resume and, upon success, the inbound transmission will be released from the “Pending” state.
The following individual changes make up the overall change to Control Totals Verification:
Inbound Physical Transmissions:
[All] Removed action to restart "Inbound ignoring control total verification".
Inbound Transmissions:
[All] Added two new actions, "Release" and "Refuse" in the action type "Pending Work". These actions are not functional at the 3.0.3.x release level of FTM for Check, ACH, or CPS.
New columns added are Pending, Released, and Released By.
Pending transmissions are now marked with a yellow highlight.
Inbound Transmission Hierarchy:
[All] Pending and Released By values added to file attributes.
[All] Released value added to file states.
[All] Added messages to indicate release and refuse complete after approvals:
- IZGMB059K: Release Transmission.
- IZGMB060K: Refuse Transmission.
Inbound Services:
[All] Enabling the "Notification for Unresolved Missing Control Total" (by checking "Send") on a Control Total service overrides Gateway error code setting for missingControlTotalErrorCode. This will prevent an error code from being assigned to the transmission or being included in the Transmission Acknowledgment.
Gateway Server:
[All] Property missingControlTotalErrorCode added to Gateway Server configuration with default error code IMA0035.
Permissions:
[All] Permissions below added to support Release and Refuse actions and the associated Approvals permissions on the Transaction Server application:
- (Action) Pending work authorization
- (Action) Level 1 review of Release Transmissions
- (Action) Level 2 review of Release Transmissions
- (Action) Level 3 review of Release Transmissions
- (Action) Level 1 review of Refuse Transmissions
- (Action) Level 2 review of Refuse Transmissions
- (Action) Level 3 review of Refuse Transmissions
Approvals/Business Rules Configuration:
[All] Added two new actions for type "InboundTransmissions" that must be added before Approvals will enforce secondary approval on the Release and Refuse actions added to the Inbound Transmissions actions:
- releaseTransmission
- refuseTransmission
Transmission Acknowledgment Service:
[All] Added two new fields, "paymentStandard" and "hashTotal", to provide same information to the Transmission Acknowledgment as is available to the Control Total Alert Notification.
This is the end of the changes to Control Totals Verification.
Java 7 / Java 8 Support
[All] WAS Java 7 and Java 8 are now supported for FTM 3.0.2.1 and above, Multiplatforms for CPS, Check, and ACH.
Presentment Group table changes:
[All] Fields (and data) introduced to the PRESENTMENT _GROUP table during the 3.0.2.0 release now have been moved to the FILE table.
3.0.2.1 iFix 2 - Custom Attributes Permissions:
[All] New permissions were added for the purpose of the partner screen custom attributes.
The following file contains SQL that will need to be run by a DB2 DBA in order to update the database:
D64385.Migration.sql
Which can be downloaded from Fix Central at:
Check
3.0.2-FTM-Check-MP-Documents .
CPS
3.0.2-FTM-CPS-MP-Documents .
Note: This section contains changes from 3.0.1.0 and 3.0.0.15 releases
Known Issues
[All] If connecting to a z/OS database, a database accessor error will occur when selecting the action to clear filters on the Inbound Transmissions screen.. This is being corrected in an iFix that will be available soon. Corrected with v3.0.2.0 iFix 1 (APAR PI71000).
[All] Services that partners have assigned to them are unable to be edited at this time. Work around is to delete the service and then add the service again. This is being corrected in an iFix that will be available soon. Corrected with v3.0.2.0 iFix 1 (APAR PI70885).
Changes
Installation location
[All] The product will be installed in a v302 subdirectory. For example:
Automated Deployment Utility
[All] The Deployment Tokens Configuration file must be updates with the Distribution Batch queues. Use the Deployment Configuration utility to open your existing tokens file to configure the new values.
[All] The pfs_deploy.xml ftm_version needs to be changed to 302. Use the pfs_deploy_v302.xml.sample as an example.
Control Center
[All] Previously customers could use any URI starting with a context root of '/fxh' to access the Control Center.
Now the proper URL for accessing the UI is now {protocol}://{host}:{port}/fxh/app with a context root of fxh/app. For example: http://127.0.0.1:58080/fxh/app. Bookmarks pointing to the "admin" or "fxh" context root should be changed. To access the 'Web Service Browser', they use the URI '/fxh/svc'.
Encryption utility
[All] The encryption utility that is located in install_directory \shared\v302\pfs\utilities\Encryption has been enhanced to support additional encryption algorithms, such as AES, along with key length and pass phrase support. An additional pass phrase parameter has been added to the Business Rules Distribution Manager, Business Rules Process Server, Gateway and Transaction Server. Refer to the IBM Knowledge Center for details.
MQ Queues
[All] New Distribution queues, which were added for performance improvement.
FXH.DISTRIBUTION.BATCH.BACKOUT.QUEUE
FXH.DISTRIBUTION.BATCH.QUEUE
Refer to the Migration section for more details.
Business Rules Process Server
[All] Business Rules Process Server now supports SSL/TLS connections. The other components that use Business Rules Process Server have been updated with new configuration properties to support this new SSL/TLS connection capability.
Distribution
[All] Currency formatting for all of the currency was based on the system currency and calculated amounts were in system currency. Now outbound currency and calculated amounts will be based on the actual outbound currency. Formatting has been changed to reflect the actual currency.
[All] Outbound Transmissions, Batches, and Segments screens will show the totals for amount and count columns. Amounts are formatted only if all of the currency is the same type. Note that some columns already had totals and additional columns have been provided.
[All] Outbound Transmission Definitions
Added new "File Name Pattern" substitution tokens.
%PNAME% - Similar to %PID% except use partner name. Supports sub-string substitution, for example PNAME1-4.
%CLID% - Cash Letter ID. Substitutes the first batch ID of the file. No sub-string support.
Gateway
[All] Physical Transmissions (Inbound and Outbound) screens will show the totals for amount and count columns. Amounts are formatted only if all of the currency is the same type.
Transaction Server
[All] Currency formatting for all of the currency was based on the system currency and calculated amounts were in system currency. Now inbound currency and calculated amounts will be based on the actual currency of what came in. Formatting has been changed to reflect the actual currency.
[All] New "Column Totals" button will show the totals for amount and count columns. Amounts are formatted only if all of the currency is the same type. This change applies to the Inbound Transmissions, Batches, Segments, and Transactions screens. With this new functionality the Configuration property "Transaction Server User Interface Properties" > "“Use system currency for column totals” has been removed
[All] On an Inbound Transmissions or Batch screen you can now add a comment , for example as to why an action was taken.
[All] On an Inbound Transmissions or Batch screen you can now Reject either the Transmission or Batch as long as the transmission or batch has not already been accepted and is Overrideable.
Settlement
[All] Enhanced Settlements third party feed to support feeds for user defined work not known to the FTM system. The ThirdPartyFeed.xsd has been changed for this support.
Migration from release v3.0.0.15 to release v3.0.2.0
[All] The same migration requirements apply as from v3.0.0.14 to 3.0.1.0.
Refer to:
Financial Transaction Manager for ACH Services v3.0.1 release information.
Financial Transaction Manager for Check Services v3.0.1 release information.
Financial Transaction Manager for CPS Services v3.0.1 release information.
[Check] If you will be using Amount Keying then deploy this component. Refer to the IBM Knowledge Center in section Financial Transaction Manager for Multiplatforms V3.0.2 for the Amount Keying installation deployment.
All configuration changes that are in v3.0.0.15 are also in v3.0.2.0.
The configuration changes that are in v3.0.1.0 will apply.
Refer to the above sections for any new configuration changes.
Migration from release v3.0.1.0 to release v3.0.2.0
[Check] If you will be using Amount Keying then deploy this component. Refer to the IBM Knowledge Center in section Financial Transaction Manager for Multiplatforms V3.0.2 for the Amount Keying installation deployment.
[All] Create the new Distribution queues, which are used for performance improvement. Refer to the {installation Path}/shared/v302/pfs/utilities/MQ/{win or unix}/MQQueues-CreateReference.txt for details.
FXH.DISTRIBUTION.BATCH.BACKOUT.QUEUE
FXH.DISTRIBUTION.BATCH.QUEUE - For this queue in Distribution also define the JMS Queue resource with the JNDI name jms/presentment/BatchQ.
[All] If you are using the Automated Deployment Utility with an existing Deployment Tokens Configuration file you will need make some updates. Refer the Automated Deployment Utility section above for changes.
Refer to the above sections for any new configuration changes.
Contains release information for Financial Transaction Manager for ACH / Check / CPS Services for Multiplatforms v3.0.2. It describes known issues and changes from previous releases. Start with the section for the release version you are currently working with and review each subsequent release for the changes.
Note: 3.0.2.x ACH is no longer supported.
Table of Contents
Common Across Releases
...Known Issues
...Changes
...General Instructions
...Upgrade Procedure
...Prerequisites and Co-requisites
...Prior to Installation
...Installation
......Create a New Installation
......Update an Existing Installation
...Necessary Tasks after Installation
...Uninstalling if Necessary
3.0.2.1 Release
...3.0.2.1 iFix 1
...3.0.2.1 iFix 2
...3.0.2.1 iFix 3
...3.0.2.1 iFix 4
...3.0.2.1 iFix 5
...3.0.2.1 iFix 6
...3.0.2.1 iFix 7
...3.0.2.1 iFix 8
...3.0.2.1 iFix 9
...3.0.2.1 iFix 10
...3.0.2.1 iFix 11
...3.0.2.1 iFix 12
...3.0.2.1 iFix 13
...3.0.2.1 iFix 14
...3.0.2.1 iFix 15
...3.0.2.1 iFix 16
...3.0.2.1 iFix 17
...3.0.2.1 iFix 18
...3.0.2.1 iFix 19
...3.0.2.1 iFix 20
...3.0.2.1 iFix 21
...3.0.2.1 iFix 22
...3.0.2.1 iFix 23
3.0.2.0 Release
| Back to top |
Common Across Releases
|
Known Issues
IBM Integration Bus and Linux ODBC driver
On Linux, we have observed incompatibilities between IBM Integration Bus v9 and generic ODBC Database Extender (IE02). Use the IE02 package that ships with the IBM Integration Bus to avoid the issue.
IBM Sterling Connect:Direct
On Linux, the 4.2.0.3-SterlingConnectDirectforUNIX-Linux-x86-iFix014 package has a defect that causes Connect:Direct to not work in the product. This problem will be corrected in a later release of the Connect:Direct package.
Database
If your database is on z and you have to perform a forced end of day, you will get a database exception. This is a known DB2 client driver issue that is being resolved in a future DB2 release level. The DB2 client that exhibits this issue is version 3.66.46, which ships with DB2 version 10.1 for z/OS. The fix will be in DB2 client 3.70.* versions of the db2jcc driver.
WebSphere Application Server 8.5.5.9 or later
WebSphere Application Server (WAS) v8.5.5.9 or later is not supported when running with Java SDK 6 earlier than version 6.0.1 Service Refresh 8 Fix Pack 30 due to WAS APAR IV84524. Either use WebSphere Application Server feature for Java SDK 7 or obtain Java SDK version 6.0.1 Service Refresh 8 Fix Pack 30 (PI66070: SHIP JAVA 6/26 SR8 FP30 FOR WSAS V8.5.0.X AND V8.5.5.X) or later.
Fix list and new feature summary
For the list of fixes refer to Financial Transaction Manager for ACH Services, Check Services, and CPS Services V3.0.2 Fix List
Data Setup Utility
The following documents describe the changes for the data setup utility (DSU) and the import and export workbooks:
DSUmigration_v3.0.2.pdf
DSUMigrationBR_v30.2.pdf
Which can be downloaded from Fix Central at:
Check
3.0.2-FTM-Check-MP-Documents .
CPS
3.0.2-FTM-CPS-MP-Documents .
Database migration
For database migration instructions refer to the migration instructions in {Install location}\shared\vnnn\pfs\Database\{os}\doc
Transaction Server Scheduler XML
The following document describes the changes to the scheduler XML for the Transaction Server component:
TransactionServerSchedulerChanges_v3.0.2.pdf
Which can be downloaded from Fix Central at:
Check
3.0.2-FTM-Check-MP-Documents .
CPS
3.0.2-FTM-CPS-MP-Documents .
General Instructions
Migration
Migration by running two installations in parallel is described in the following document:
FTM_PFS_Parallel_migration.pdf
Which can be downloaded from Fix Central at:
Check
3.0.2-FTM-Check-MP-Documents .
CPS
3.0.2-FTM-CPS-MP-Documents .
WebSphere Application Server
All WebSphere Servers must be restarted after all components have been updated.
Internet Explorer (IE) in Compatibility mode
Some FTM Control Center pages will not render correctly in the Compatibility View of IE 11, because it emulates an older IE version.
Solution
The older IE versions are not supported but the following may work for you.
1. Navigate to Administration > System > Properties
2. Open the System Property "HTTP Response Headers". This has a default value and a custom value.
3. Edit
4. Add "X-UA-Compatible: IE=edge" to this list of headers.
-If there is a custom value defined for this property, add a pipe character to the end of the current value, and then add this new header.
-If there is no custom value defined for this property, we recommend the user to copy the default value into the custom value, and then add a pipe character, and then add this new header.
5. Restart server so that the new HTTP Response Headers are used when visiting pages.
Explanation
This new response header will force pages to display as IE11 when being viewed with Compatibility mode.
Upgrade procedure
To upgrade an existing installation for a fix pack the following tasks need to be performed:
- Perform database migration. Refer to the Database migration section in this document.
- Update the WebSphere Application Server (WAS) components. You may use the Automated Deployment Utility (ADU) or manually upgrade (refer to the update instructions in each WAS component doc folder).
- Update your Data Setup Utility worksheets. Refer to the Data Setup Utility section for documentation.
- Update your Transaction Server Scheduler.xml. Refer to the Transaction Server Scheduler XML section for documentation. Note: this may not be required for your installation.
- Refer to the release specific section for changes that may affect your installation.
Prerequisites and co-requisites
- Ensure that your system meets all of the system requirements: http://www.ibm.com/software/industry/financial-transaction-manager/requirements
This action prevents technical problems that might occur after the installation and configuration of the fix pack. - Review the Flashes and open Authorized Problem Analysis Reports (APARs) on the Financial Transaction Manager product support Web site: http://www-01.ibm.com/support/docview.wss?uid=swg27027034
Open APARs describe defects that are not yet addressed in a fix pack, and they might contain work-arounds for known problems. - Ensure that there is sufficient free space to install the fix pack. At least 2GB of free space is required to contain the uncompressed installation image.
- If an FTM product is already installed and there are special fixes applied, contact IBM support to determine whether you need an updated version of the fixes before you install the fix pack. This helps to ensure that your system is in a consistent state and that no special fixes are lost.
Prior to installation
Before installing a fix pack, perform the following steps:
- Download the fix pack tar file to an appropriate location.
- Uncompress the tar file.
- Insure the applications in the install location are not running:
- RMI Service, Business Rules Distribution Manager, Business Rules Process Server, Gateway, Transaction Server.
- Additional for Windows (Check only): Archive Server (IES), Image Server (IIS), Image Review and Rescan (IIR), and Image Capture Display (ICD).
- When installing a fix pack that includes a JRE upgrade, encrypted configuration files will need to be decrypted first. After installing the fix pack, then the configuration files can be encrypted again.
Installation
Create a new installation
Mod Releases and Fix Packs can be used to create a new installation. Interim Fixes (iFixes) cannot be used to create a new installation and can only be used to update an existing installation.
Update an existing installation
- Start IBM Installation Manager.
- Add the location of the repository containing the installation package:
- Select File->Preferences.
- Click Add Repository.
- Browse to the directory containing the repository and select the file repository.config (if you are using a directory) or diskTag.inf (if you are using the installation CD)
- Click Test Connections and click OK.
- Click OK.
- Transfer the FTM product installation files to your installation directory:
- On the main pane, click Update.
- Select IBM Financial Transaction Manager for ACH Services, IBM Financial Transaction Manager for Check Services, or IBM Financial Transaction Manager for Corporate Payment Services and click Next.
- Review the license agreements and click Next if appropriate.
- On the first Install Packages pane, specify the shared resources directory of the Installation Manager and click Next.
- On the second Install Packages pane, specify the installation directory (you must have write access to the directory) and click Next.
- On the third Install Packages pane, do not change the selected features and click Next.
- On the Install package summary information pane, click Install.
- After installation is complete, click Finish.
Deployment
- Perform database migration. Refer to the Database migration section in this document.
- Note: The run time components cannot be running during the database migration.
- Note: Files can continue to be delivered to the Gateway inbound source folder.
- J2SE components: Install will overlay the J2SE applications so no special migration instructions are needed. Restarting those applications will update them with the fixes.
- WebSphere Application Server (WAS) components: You may use the Automated Deployment Utility (ADU), manually upgrade (refer to the update instructions in each WAS component doc folder), or in a WAS Network Deployment configuration use the Deployment Manager.
- All WebSphere Servers must be restarted after all components have been updated.
- Update your Transaction Server Scheduler.xml. Refer to the Transaction Server Scheduler XML section in this document for documentation. Note: this may not be required for your installation.
- Refer to the release specific section for changes that may affect your installation.
- At this point you can start up your runtime components.
- If you are using the Data Setup Utility (DSU) worksheets capability for managing your data then update your worksheets. Refer to the Data Setup Utility section in this document for documentation.
Necessary tasks after installation
Verify the correct build information. See 'Build Date' listed in the table below.
Uninstalling if necessary
To rollback to a previous version:
Before uninstalling, insure the applications in the install location are not running:
- RMI Service, Business Rules Distribution Manager, Business Rules Process Server, Gateway, Transaction Server.
- Additional for Windows (Check only): Archive Server (IES), Image Server (IIS), Image Review and Rescan (IIR), and Image Capture Display (ICD).
- Start IBM Installation Manager.
- Click Uninstall.
- On the Uninstall Packages screen (Select packages to uninstall), select the FTM version that has the iFix to uninstall and click Next.
- On the Uninstall Packages (Review the summary information) screen, confirm the package you are uninstalling is correct and click the Uninstall button.
- The screen will now show a Green Check Mark icon (Packages are uninstalled) click the Finish button.
| Back to top |
3.0.2.1 iFix 23
|
| Back to top |
3.0.2.1 iFix 22
|
| Back to top |
3.0.2.1 iFix 21
|
| Back to top |
3.0.2.1 iFix 20
|
| Back to top |
3.0.2.1 iFix 19
|
| Back to top |
3.0.2.1 iFix 18
|
| Back to top |
3.0.2.1 iFix 17
|
| Back to top |
3.0.2.1 iFix 16
|
| Back to top |
3.0.2.1 iFix 15
|
The following SOAP Web Services have been removed:
- Physical Transmissions
- Inbound Transmissions
- Inbound Batches
- Inbound Transactions
| Back to top |
3.0.2.1 iFix 14
|
| Back to top |
3.0.2.1 iFix 13
|
| Back to top |
3.0.2.1 iFix 12
|
| Back to top |
3.0.2.1 iFix 11
|
| Back to top |
3.0.2.1 iFix 10
|
| Back to top |
3.0.2.1 iFix 9
|
| Back to top |
3.0.2.1 iFix 8
|
| Back to top |
3.0.2.1 iFix 7
|
| Back to top |
3.0.2.1 iFix 6
|
| Back to top |
3.0.2.1 iFix 5
|
| Back to top |
3.0.2.1 iFix 4
|
| Back to top |
3.0.2.1 iFix 3
|
| Back to top |
3.0.2.1 iFix 2
|
| Back to top |
3.0.2.1 iFix 1
|
| Back to top |
3.0.2.1 Release
|
Compatibility Matrix
Because the development of releases and interim fixes (iFixes) for maintenance are done in parallel, a later release might not contain every interim fix that was created for an earlier release. The following table shows you which releases and interim fix levels can be successfully upgraded to V3.0.2, Fix Pack 1.
In the following table, the "If you're on version" column shows you the releases that can be upgraded successfully. The highest release or interim fix level that can be upgraded for each release is shown in the "To successfully upgrade to V3.0.2, Fix Pack 1, you must be no higher than version" column. If the release that you are upgrading from is at an interim fix level that is higher than the release or fix level that is shown in the right column, you can't upgrade the release without losing some changes. The upgrade needs to occur at the next release.
For more information about the individual changes in a release or interim fix, see the fix list for this version.
| If you’re on version | To successfully upgrade to V3.0.2, Fix Pack 1, you must be no higher than version |
| 3.0.0.15 | 3.0.0.15 iFix 5 |
| 3.0.2.0 | 3.0.2.0 iFix 2 |
Known Issues
[All] The "(Action) Pending work authorization" handles the refuse and release actions. Users with this permission will be able to refuse an accepted transmission. The work around: limit the number of users granted this permission and avoid refusing a non-pending transmission.
[All] In the migration to FTM4C version 3.0.1 or above, three UI properties were merged into a single property called HTTP Response Headers. An issue with the migration could cause this parameter to contain an invalid value if it was empty in the original 3 properties. To address this, navigate to Administration -> System -> Properties. If the Custom field of the HTTP Response Headers property is set with a valid value, no action is required. If the field is blank, edit the property to remove any white space or use the query UPDATE FTM.CORE_PROPERTIES SET VALUE = NULL WHERE KEY = 'framework.http.resp.hdr'.
Feature Changes
Control Total Verification Processing
[All] The purpose of the new functionality is to reduce the number of inbound file notifications to one. The notification will contain information regarding all validation errors found within the file and failures that occurred executing Control Total Verification (CTV) due to missing CTV files.
The inbound file will be ingested normally to complete both CTV and additional validation. When the ingestion process is completed, and no CTV has been received, the inbound physical transmission will be set to the “Processed” state and the inbound transmission will be placed in a “Pending” state. A single notification will then be sent back to the sender detailing that the CTV file has not yet been received along with any additional issues detected during file validation. To generate a single notification, the Control Total service will no longer default to sending a Control Total Alert. Instead, the Transmission Acknowledgement will include the error code configured in the missingControlTotalErrorCode property. When the CTV file is finally received, the CTV process will resume and, upon success, the inbound transmission will be released from the “Pending” state.
The following individual changes make up the overall change to Control Totals Verification:
Inbound Physical Transmissions:
[All] Removed action to restart "Inbound ignoring control total verification".
Inbound Transmissions:
[All] Added two new actions, "Release" and "Refuse" in the action type "Pending Work". These actions are not functional at the 3.0.3.x release level of FTM for Check, ACH, or CPS.
New columns added are Pending, Released, and Released By.
Pending transmissions are now marked with a yellow highlight.
Inbound Transmission Hierarchy:
[All] Pending and Released By values added to file attributes.
[All] Released value added to file states.
[All] Added messages to indicate release and refuse complete after approvals:
- IZGMB059K: Release Transmission.
- IZGMB060K: Refuse Transmission.
Inbound Services:
[All] Enabling the "Notification for Unresolved Missing Control Total" (by checking "Send") on a Control Total service overrides Gateway error code setting for missingControlTotalErrorCode. This will prevent an error code from being assigned to the transmission or being included in the Transmission Acknowledgment.
Gateway Server:
[All] Property missingControlTotalErrorCode added to Gateway Server configuration with default error code IMA0035.
Permissions:
[All] Permissions below added to support Release and Refuse actions and the associated Approvals permissions on the Transaction Server application:
- (Action) Pending work authorization
- (Action) Level 1 review of Release Transmissions
- (Action) Level 2 review of Release Transmissions
- (Action) Level 3 review of Release Transmissions
- (Action) Level 1 review of Refuse Transmissions
- (Action) Level 2 review of Refuse Transmissions
- (Action) Level 3 review of Refuse Transmissions
Approvals/Business Rules Configuration:
[All] Added two new actions for type "InboundTransmissions" that must be added before Approvals will enforce secondary approval on the Release and Refuse actions added to the Inbound Transmissions actions:
- releaseTransmission
- refuseTransmission
Transmission Acknowledgment Service:
[All] Added two new fields, "paymentStandard" and "hashTotal", to provide same information to the Transmission Acknowledgment as is available to the Control Total Alert Notification.
This is the end of the changes to Control Totals Verification.
Java 7 / Java 8 Support
[All] WAS Java 7 and Java 8 are now supported for FTM 3.0.2.1 and above, Multiplatforms for CPS, Check, and ACH.
Presentment Group table changes:
[All] Fields (and data) introduced to the PRESENTMENT _GROUP table during the 3.0.2.0 release now have been moved to the FILE table.
3.0.2.1 iFix 2 - Custom Attributes Permissions:
[All] New permissions were added for the purpose of the partner screen custom attributes.
The following file contains SQL that will need to be run by a DB2 DBA in order to update the database:
D64385.Migration.sql
Which can be downloaded from Fix Central at:
Check
3.0.2-FTM-Check-MP-Documents .
CPS
3.0.2-FTM-CPS-MP-Documents .
| Back to top |
3.0.2.0 Release
|
Known Issues
[All] If connecting to a z/OS database, a database accessor error will occur when selecting the action to clear filters on the Inbound Transmissions screen.. This is being corrected in an iFix that will be available soon. Corrected with v3.0.2.0 iFix 1 (APAR PI71000).
[All] Services that partners have assigned to them are unable to be edited at this time. Work around is to delete the service and then add the service again. This is being corrected in an iFix that will be available soon. Corrected with v3.0.2.0 iFix 1 (APAR PI70885).
Changes
Installation location
[All] The product will be installed in a v302 subdirectory. For example:
- Instead of {install location}/xxx/v300 will be {install location}/xxx/v302 where xxx is ach, check or cps.
- Instead of {install location}/shared/v300/pfs will be {install location}/shared/v302/pfs.
Automated Deployment Utility
[All] The Deployment Tokens Configuration file must be updates with the Distribution Batch queues. Use the Deployment Configuration utility to open your existing tokens file to configure the new values.
[All] The pfs_deploy.xml ftm_version needs to be changed to 302. Use the pfs_deploy_v302.xml.sample as an example.
Control Center
[All] Previously customers could use any URI starting with a context root of '/fxh' to access the Control Center.
Now the proper URL for accessing the UI is now {protocol}://{host}:{port}/fxh/app with a context root of fxh/app. For example: http://127.0.0.1:58080/fxh/app. Bookmarks pointing to the "admin" or "fxh" context root should be changed. To access the 'Web Service Browser', they use the URI '/fxh/svc'.
Encryption utility
[All] The encryption utility that is located in install_directory \shared\v302\pfs\utilities\Encryption has been enhanced to support additional encryption algorithms, such as AES, along with key length and pass phrase support. An additional pass phrase parameter has been added to the Business Rules Distribution Manager, Business Rules Process Server, Gateway and Transaction Server. Refer to the IBM Knowledge Center for details.
MQ Queues
[All] New Distribution queues, which were added for performance improvement.
FXH.DISTRIBUTION.BATCH.BACKOUT.QUEUE
FXH.DISTRIBUTION.BATCH.QUEUE
Refer to the Migration section for more details.
Business Rules Process Server
[All] Business Rules Process Server now supports SSL/TLS connections. The other components that use Business Rules Process Server have been updated with new configuration properties to support this new SSL/TLS connection capability.
Distribution
[All] Currency formatting for all of the currency was based on the system currency and calculated amounts were in system currency. Now outbound currency and calculated amounts will be based on the actual outbound currency. Formatting has been changed to reflect the actual currency.
[All] Outbound Transmissions, Batches, and Segments screens will show the totals for amount and count columns. Amounts are formatted only if all of the currency is the same type. Note that some columns already had totals and additional columns have been provided.
[All] Outbound Transmission Definitions
Added new "File Name Pattern" substitution tokens.
%PNAME% - Similar to %PID% except use partner name. Supports sub-string substitution, for example PNAME1-4.
%CLID% - Cash Letter ID. Substitutes the first batch ID of the file. No sub-string support.
Gateway
[All] Physical Transmissions (Inbound and Outbound) screens will show the totals for amount and count columns. Amounts are formatted only if all of the currency is the same type.
Transaction Server
[All] Currency formatting for all of the currency was based on the system currency and calculated amounts were in system currency. Now inbound currency and calculated amounts will be based on the actual currency of what came in. Formatting has been changed to reflect the actual currency.
[All] New "Column Totals" button will show the totals for amount and count columns. Amounts are formatted only if all of the currency is the same type. This change applies to the Inbound Transmissions, Batches, Segments, and Transactions screens. With this new functionality the Configuration property "Transaction Server User Interface Properties" > "“Use system currency for column totals” has been removed
[All] On an Inbound Transmissions or Batch screen you can now add a comment , for example as to why an action was taken.
[All] On an Inbound Transmissions or Batch screen you can now Reject either the Transmission or Batch as long as the transmission or batch has not already been accepted and is Overrideable.
Settlement
[All] Enhanced Settlements third party feed to support feeds for user defined work not known to the FTM system. The ThirdPartyFeed.xsd has been changed for this support.
Migration from release v3.0.0.15 to release v3.0.2.0
[All] The same migration requirements apply as from v3.0.0.14 to 3.0.1.0.
Refer to:
Financial Transaction Manager for ACH Services v3.0.1 release information.
Financial Transaction Manager for Check Services v3.0.1 release information.
Financial Transaction Manager for CPS Services v3.0.1 release information.
[Check] If you will be using Amount Keying then deploy this component. Refer to the IBM Knowledge Center in section Financial Transaction Manager for Multiplatforms V3.0.2 for the Amount Keying installation deployment.
All configuration changes that are in v3.0.0.15 are also in v3.0.2.0.
The configuration changes that are in v3.0.1.0 will apply.
Refer to the above sections for any new configuration changes.
Migration from release v3.0.1.0 to release v3.0.2.0
[Check] If you will be using Amount Keying then deploy this component. Refer to the IBM Knowledge Center in section Financial Transaction Manager for Multiplatforms V3.0.2 for the Amount Keying installation deployment.
[All] Create the new Distribution queues, which are used for performance improvement. Refer to the {installation Path}/shared/v302/pfs/utilities/MQ/{win or unix}/MQQueues-CreateReference.txt for details.
FXH.DISTRIBUTION.BATCH.BACKOUT.QUEUE
FXH.DISTRIBUTION.BATCH.QUEUE - For this queue in Distribution also define the JMS Queue resource with the JNDI name jms/presentment/BatchQ.
[All] If you are using the Automated Deployment Utility with an existing Deployment Tokens Configuration file you will need make some updates. Refer the Automated Deployment Utility section above for changes.
Refer to the above sections for any new configuration changes.
[{"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"3.0.2.1;3.0.2.0;3.0.2;3.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"IBM Financial Transaction Manager for ACH Services","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"IBM Financial Transaction Manager for Check Services","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"IBM Financial Transaction Manager for Corporate Payment Services","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
14 April 2021
UID
swg22003609