IBM Support

Financial Transaction Manager for Corporate Payment Services and Digital Payments V3.2.1 Release Information

Fix Readme


Abstract

This document contains V3.2.1 release information for Financial Transaction Manager for Corporate Payment Services and Financial Transaction Manager for Digital Payments for Multiplatforms. Included are known issues and changes from previous releases.

Content

Financial Transaction Manager for Corporate Payment Services and Financial Transaction Manager for Digital Payments V3.2.1 Release Information

Contains release information for:

  • Financial Transaction Manager for Corporate Payment Services for Multiplatforms V3.2.1
  • Financial Transaction Manager for Digital Payments for Multiplatforms V3.2.1


Described are known issues and changes from previous releases. Start with the section for the release version you’re currently working with and review each subsequent release for the changes.

 
 

Contents
Common Across Releases
3.2.1.0 Release
...3.2.1.0 iFix 1
...3.2.1.0 iFix 2
...3.2.1.0 iFix 3
...3.2.1.0 iFix 4
 

 
  

Back to top
Common Across Releases
 
 

Known Issues

Control Center
The Control Center Online help search function will not work due to Java 8 incompatibility. The WAS SystemOut.log will show something similar to the following:
Excerpt from SystemOut.log :
[2/20/17 17:52:19:097 UTC] 00000190 webapp        E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[equinoxbridgeservlet]: java.lang.ClassNotFoundException: org.apache.jsp.advanced.searchView_jsp
        at java.net.URLClassLoader.findClass(URLClassLoader.java:607)
        at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:133)

 

WebSphere Application Server 9.0.x update issue (Windows Only)
 
In WebSphere Application Server v9.0.x, there is a known problem updating components for an interim fix. This appears to only apply to Windows Operating System.
 
Automated Deployment Utility workaround:
 
The interim fix components to update need to be first uninstalled.  The tokens file, for example pfs_deploy.xml, contains those interim ifix components to update.  These will appear in the <install> </install> section.  You will also need to add these same components in the <uninstall> </uninstall> section.
 
Manual update workaround:
 
Before updating the Console WAR modules stop the FrameworkUI_EAR application, then proceed as normal.  The Engine modules can be updated as normal.

Feature Changes

Fix list and new feature summary

For the list of fixes refer to Financial Transaction Manager for Corporate Payment Services and Financial Transaction Manager for Digital Payments V3.2.1 Fix list.


Data Setup Utility
The following documentation describes the changes for the data setup utility (DSU) and the import and export workbooks (CPS):


DSUmigration_v3.2.1.pdf
DSUMigrationBR_v3.2.1.pdf

Which can be downloaded from Fix Central at 3.2.1-FTM-CPS-MP-Documents .

 

Database migration
For database migration instructions, refer to the migration instructions in {Install location}\shared\vnnn\pfs\Database\db2\{os}\doc

Transaction Server Scheduler XML
The following documentation describes the changes to the scheduler XML for the Transaction Server component (CPS):

TransactionServerSchedulerChanges_v3.2.1.pdf

Which can be downloaded from Fix Central at 3.2.1-FTM-CPS-MP-Documents .
 


General Instructions

Migration

Upgrade procedure

To upgrade an existing installation for a fix pack or interim fix (iFix) the following tasks need to be performed:

Pre-installation
Note: Installation Manager won’t update a file that has been modified after Installation Manager originally installed that file.

  1. Ensure that the following components in the install location aren’t running: RMI Service, Business Rules Distribution Manager, Business Rules Server, Gateway, Transaction Server.
  2. Ensure that your installation doesn’t have any updated files from test fixes or modifications that you may have made. Known directories or files that may have test fixes are:
    1. Install location\shared\v321\pfs\BusinessRules\manager\lib\pdrmgrfx.jar
    2. Install location\shared\v321\pfs\BusinessRules\server\lib\pdrsvrfx.jar
    3. Install location\shared\v321\pfs\Gateway\lib\izxfix.jar
    4. Install location\shared\v321\pfs\ITS\lib\txfix.jar


Installation

  1. Start IBM Installation Manager.
  2. Add the location of the repository containing the installation package:
    1. Select File > Preferences.
    2. Click Add Repository.
    3. Browse to the directory containing the repository .zip file and select the file. Click Open and then OK.
    4. Click Test Connections and then OK.
    5. Click OK.
  3. Install the FTM product installation files to your installation directory:
    1. On the main panel, click Update.
    2. Select IBM Financial Transaction Manager for Digital Payments, IBM Financial Transaction Manager for Check Services, or IBM Financial Transaction Manager for Corporate Payment Services and then click Next.
    3. Select the fix pack or interim fix and then click Next.
    4. Follow the rest of the prompts.
    5. Confirm that the "Update packages" page shows success.


Deployment

  1. Perform database migration. Refer to the Database migration section in this document.
    1. Note: The runtime components can’t be running during the database migration.
    2. Note: Files can continue to be delivered to the Gateway inbound source folder.
  2. J2SE components: Install will overlay the J2SE applications so no special migration instructions are needed. Restarting those applications will update them with the fixes.
  3. WebSphere Application Server (WAS) components: You can 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.
    Note: Refer to "WebSphere Application Server 9.0.x update issue (Windows Only)" in "Common Across Releases" > "Known Issues".
    1. All WebSphere Servers must be restarted after all of the components have been updated.
    2. For an interim fix, refer to the fix list for the modules to deploy. Note: Interim fixes are meant to be deployed on an existing WAS profile deployment. If this is a new WAS profile, and you have already installed the interim fix onto the prior installation, you must perform two deployment passes. The first pass is to do the initial, full product deployment and the second pass is to do those components that are affected by the interim fix.
  4. Update your Transaction Server Scheduler.xml. Refer to the Transaction Server Scheduler XML section in this document. Note: this might not be required for your installation.
  5. Refer to the release specific section for any changes that might affect your installation.
  6. At this point, you can start your runtime components.
  7. If you’re using the Data Setup Utility (DSU) worksheets capability for managing your data, update your worksheets. For more information, see the Data Setup Utility section in this document.
 
Back to top
3.2.1.0 iFix 4
Known Issues

None.
Feature Changes

None.
Migration

None.
Back to top
3.2.1.0 iFix 3
Known Issues

105506 (CPS - fixed at 3.2.1.0 iFix 3 with the information provided below)
NameNotFoundException Error during Task Registry

To resolve the problem refer to adding txaccessors.jar in the IBM Knowledge Center at ( https://www.ibm.com/support/knowledgecenter/en/SSRH46_3.2.1/gpyizgjaddsftskaixedi824.html ).


90870 (DP - fixed at 3.2.1.0 iFix 3 with the information provided below)

The change documented in the "DSUmigration_v3.2.1.pdf" document for this interim fix (iFix) requires you to run the DSU for the AchImport.properties file.
Feature Changes

None.
Migration

None.
Back to top
3.2.1.0 iFix 2

Known Issues

88956 (fixed at 3.2.1.0 iFix 2 with the information provided below)
Note: the following issue applies to only Digital Payments (not CPS).

Non-payment transactions amounts are incorrect

Use the two files below to fix a problem with one of the database views.

ReadMe-DropAndCreatePayAndNonPayTxnView_2.txt
DropAndCreatePayAndNonPayTxnViewV2.sql.txt

Which can be downloaded from Fix Central at 3.2.1-FTM-CPS-MP-Documents .

Feature Changes

85755
Cognos Report - Outgoing Transactions at the client level

Cognos  "Outgoing Transactions by Client" report displays successful outgoing transactions/amounts sorted by message type and by channel for a specified time period.

Migration

None.

Back to top
3.2.1.0 iFix 1
 
 

Known Issues

89638 (fixed at 3.2.1.0 iFix 3)
Note: the following issue applies to only Digital Payments (not CPS).

User interface displays an incorrect value for non-payment transactions

Use the two files below as a guide to drop and create one of the database views.

ReadMe-DropAndCreatePayAndNonPayTxnView.txt
DropAndCreatePayAndNonPayTxnViewV1.sql.txt

Which can be downloaded from Fix Central at 3.2.1-FTM-CPS-MP-Documents .

 

Migration

The following document contains the instructions needed to migrate from V3.2.1.0 to V3.2.1.0 iFix 1:

FTM_DigitalPayments_v3.2.1.0_iFix1_Installation.pdf

Which can be downloaded from Fix Central at 3.2.1-FTM-CPS-MP-Documents .
 

Back to top
3.2.1.0 Release
 
 

Note: This section contains changes since the V3.2.0.0 release.

 

Known Issues

88473
Immediate tactical activation not working from the participant directory user interface

83965
Add using WebSphere Application Server data source custom variables called currentSchema and currentFunctionPath

Changes were made to WebSphere enterprise applications so that they use a database schema name that is configured using the currentSchema and currentFunctionPath custom properties of the related JDBC data source. The Automated Deployment Utility (ADU) was updated to add these variables for all applications at the time of deployment. Also, the deployment configurations for all of the WebSphere based applications (*see below) was updated so that the ADU no longer creates the WAS environment variables that define the database schema name.

*Business Rules and Duplicate Detect still require a WebSphere variable to define the database schema name.

For performance reasons, it is preferable to configure the database schema name using the JDBC data source. This change is backward compatible because the applications can use either a WebSphere variable or the JDBC data source custom variable to specify the database schema name.

The FrameworkUI_EAR, PartnerProfileUI_EJBEAR, and Gateway_EJBEAR enterprise applications are intended to fully support database schema names defined by the JDBC properties as described above. However, these three applications are not yet fully functional with this configuration. As a workaround, you must define WebSphere variables for the schema name values for these applications.

The following instructions explain how to set the values in a single server environment and how to restart the applications for the variables to be recognized.

  1. Log in to WebSphere Administrative Console
  2. Environment > WebSphere variables
  3. New
  4. Enter 'izh.console.dbschemaname' (without quotes) into the Name field
  5. Enter the primary database schema name into the Value field (for example, 'FTM' (without quotes))
  6. OK
  7. New
  8. Enter 'partnerprofile.env.ui.dbschemaname' (without quotes) into the Name field
  9. Enter the primary database schema name into the Value field (for example, 'FTM' (without quotes))
  10. OK
  11. New
  12. Enter 'izx.gateway.engine.dbschemaname' (without quotes) into the Name field
  13. Enter the primary database schema name into the Value field (for example, 'FTM' (without quotes))
  14. OK
  15. Save
  16. Applications > Application Types > WebSphere enterprise applications
  17. Select check box for applications: FrameworkUI_EAR, PartnerProfileUI_EJBEAR, and Gateway_EJBEAR.
  18. Stop
  19. Select check box for applications: FrameworkUI_EAR, PartnerProfileUI_EJBEAR, and Gateway_EJBEAR.
  20. Start
 

Blocking Filter

For installations using IBM Integration Bus (IB) V9.0, the optional Blocking Filter flow will not work. IBM IB V9.0 is incompatible with the new Java based, optional, Blocking Filter flow.  This is a  Java V7/IB V9 versus V8/IB V10 restriction.

 

88886 (fixed in 3.2.1.0 iFix 1)
FI Transaction report

In the FI Transaction report, the total transaction count is not matching the sum of Credit Transfers + RFI+RFP+RORF.  This is fixed in the next interim fix.

 


 

Feature Changes

84853
Enhancements to Message Standard page
Message standard Add/Edit/Delete now has an additional FSM Application Name field.

Back end enhancements in choosing an Application ID
Inbound now chooses an application ID by first looking at the FSM Application ID that is configured for the message standard. If this is null, the default application ID is used instead.
Distribution now chooses an application ID by first looking at the Application ID that is configured for the channel. If this is null, the FSM Application ID that is configured for the message standard is used. If this is null, the default application ID is used.

 

77307
Enhancements to the banks and transmission definitions page
To support Canadian processing, the 10 digit identifiers for data destination center can be added to the routing number sections in the banks and transmission definitions pages.

Token enhancements for ADU
The CPS Reference BAR file has had two new tokens added to it, and these two new tokens can be overridden. To ensure these new tokens are added to the BAR file, run the PFSTools batch file, and then go to the PFS Tools web page on local host. Insert the tokens file that has been used to deploy previously when prompted to in step 1. Progress through the wizard as done previously, until step 8. In step 8, there should be one new field in step 8.2 called ASCII CPA Input Directory and a new one in step 8.3 called WMQ CPA Input Queue Name. The field originally called CPA Input Directory has also been renamed EBCDIC CPA Input Directory for clarity, but no other changes have been made to it. To override the new tokens, simply change the fields in the wizard to the desired value, otherwise leaving the default value is acceptable. Afterwards, complete the wizard and download the token file generated by the wizard at the end, and replace the original token file with the new one. To have the changes be added to the broker, the Reference_CPS_WAS_MB_deployment_script batch file must be run with the new token file. If overriding the default value of the file locations (C:\FTMChan\*) or queue name (FXH.GPY.CPA.IN), the channels defined by the FSM would need to match the overriding values in the .bar file.

 

52763
Risk Management > Account Rules Support (blocking filters only)

Phase 1 of participant account rules configuration for risk management has been implemented in this release.  Payment blocking filters may now be defined from the Participant Details page of the Control Center user interface.

For customers migrating from V3.0.6 to V3.2.1.0 directly:
No action needed. The account rules permissions are part of same groups as they were in V3.0.6

For customers migrating to V3.2.1.0 from a V3.2.0 migrated database (previously migrated from V3.0.6):
-Account rules permissions are assigned to 'Administrators' group by default.
-If the group 'Configuration Administrators' was not renamed, Account rules permissions are removed from this group.

 

52765
Risk Management > Account Rules > Blocking Filters Support

The Blocking Filters page manages the blocking filters for an account.  Blocking filters are used to block the defined transaction type from being accepted into the system. Incoming transactions that match a blocking filter are rejected by the system and are not eligible for review.

Permissions for Blocking filters for customers who have migrated:
In V3.2.1 the Blocking Filters page has been split from the Account rules page (available in V3.0.6), which means the Blocking filters page has its own permissions.

For customers migrating from V3.0.6 to V3.2.1.0 directly:
No action needed. Blocking filters permissions are part of same groups the Account rules were part of.

For customers migrating to V3.2.1.0 from a V3.2.0 migrated database (previously migrated from V3.0.6):
The Blocking filters permissions are assigned to 'Administrators' group by default. Any other groups the Account rules was a part of in V3.0.6, need to be manually added.

 

77330
Blocking rules

This change allows a bank to build blocking rules in Risk Management to prevent a customer from requesting payments in TCH.   This change requires the use of an optional node in FTM for Immediate Payments to interrogate the blocking rules.

 

77331
Blocking rules

This change allows a bank to build blocking rules in Risk Management to prevent a customer from receiving payments in TCH.   This change requires the use of an optional node in FTM for Immediate Payments to interrogate the blocking rules.

52765
Blocking filters - user interface support

The following page manages blocking filters for an account.  Blocking filters are used to block the defined transaction type from being accepted into the system. Incoming transactions that match a blocking filter are rejected by the system and are not eligible for review.

Permissions for Blocking filters for customers who have migrated:
In V3.2.1 this page has been split from Account rules (available in V3.0.6), which means the blocking filters page has its own permissions.

For customers migrating from V3.0.6 to V3.2.1.0 directly:
No action needed. Blocking filters permissions are part of the same groups that the Account rules were a part of.

For customers migrating to V3.2.1.0 from a V3.2.0 migrated database (previously migrated from V3.0.6):
The Blocking filters permissions are assigned to 'Administrators' group by default. Any other groups the Account rules were a part of in V3.0.6, need to be manually added.

 

52732
New user interface page - Participant directory: Originator Support

A new page that contains the basic attributes for a participant that is assigned the role of an originator has been created. Fields on this page appeared on the Originator Attributes page in prior versions of FTM.
Note:  This page is available only when the selected participant has been assigned the role of Originator under General > Roles.

 

84013
Participant directory Web Service - query by RTN and account number

This change allows a bank's operator to filter the Read Participant Detail web services based on the participant account number, account type, and bank code. These will be a new additional attributes in the optional filtering.

The operator should also be able to retrieve the participant account detail upon specifying the extension ACCOUNT to view all participant account details with participant ID specified in the web service.

 

82108
Participant directory - Add High risk customer flag

A new attribute has been added to the Participant Directory General tab called High risk customer.  It can have a value of Yes or No and by default it will be set to no.  This field will be passed to the Business Rules engine and can be used to drive business rule decisions for a participant. It is also available in Risk Processing to drive account rules decisions. 

 

82111
Reporting and Analytics database to use IBM InfoSphere Data Replication CDC

Instructions and configuration to use IBM InfoSphere Data Replication - CDC Replication to create a replicated database for the tables used for reports and dashboards.

 

85751
TCH Report - Transaction by FI

A new Cognos “Transaction by FI Report” displays successful incoming and outgoing transactions and amounts, sorted by message type and by channel.

 

84657
Handle Messages that come in "Pending" State

This change builds on the new capability in FTM for Immediate Payments where a payment can go to fraud review and not be determined good or bad immediately.  The payment goes into a pending state until fraud review determines whether the payment is good or bad. This change enables the payments that are in a pending state to be displayed in the Pending state and then the state will change when FTM for Immediate Payments completes.

 

85750
TCH Report - Network Transactions

Cognos Network Transactions Report displays successful incoming and outgoing transactions and amounts.

 

84659
TCH - Identify possible outgoing duplicate payments

This change will display transactions that were marked as duplicate payments in FTM for Immediate Payments on the Digital Payment Transaction user interface.

 

77321
TCH - Cancel a payment from Digital Payments user interface

This change enables a bank’s Customer Service Representative (CSR) to cancel a TCH credit transfer if it has not yet been sent to The Clearing House. The cancel request is available from the Control Center.

 

84655
TCH - Initiate a Request for Information from the Digital Payments user interface

This change enables a bank’s Customer Service Representative (CSR) to initiate a Request for Information (camt.026) on behalf of a creditor from the Control Center, and to allow the operator initiating the request to enter details of the information requested. This will likely be done when the creditor needs additional information to apply a payment.

 

77329
TCH - Match incoming payment to previous request for payment and report differences

This change builds on the new capability in FTM for Immediate Payments to associate multiple payments with a request for payment and to indicate whether the request for payment is Complete, Partial Payed, or Over Paid.  The user can view requests for payment on the Digital Payments user interface and see their status.  If a request for payment is in one of these statuses  the user can use the detail page to see the related payments to the request.

 
 

Migration

For migration from V3.2.0.1 to V3.2.1.0, note that you must run the migration DDLs for V3.2.0.2 and V3.2.1.0.

The following document contains the instructions for migrating from V3.2.0.1 to V3.2.1.0.

FTM_DigitalPayments_v3.2.1.0_Migration.pdf

Which can be downloaded from Fix Central at 3.2.1-FTM-CPS-MP-Documents .

 
 
 

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"Component":"IBM Financial Transaction Manager for Digital Payments","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"3.2.1;3.2.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
07 August 2020

UID

ibm10788411

Page Feedback