Product documentation

• Release information (this document)
• System requirements website
• Fix list (key defects fixes in this release)
• Financial Transaction Manager online product documentation
• Entitled documentation fix pack (download from Fix Central)
• Mapping Specs - these documents are provided in the entitled documentation fix pack
• Resources (support links for this and other releases of this offering)

General instructions

Installation

1. Start IBM Installation Manager.
2. Add the location of the repository that contains the installation package:
   1. Select File > Preferences.
   2. Click Add Repository.
   3. Browse to the directory that contains 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 pane, click Update.
   2. Select IBM Financial Transaction Manager for Digital Payments, IBM Financial Transaction Manager for Check Services, IBM Financial Transaction Manager for Corporate Payment Services, or IBM Financial Transaction Manager for High Value Payments, 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. Do the 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: The installation overlays the J2SE applications, so no special migration instructions are needed. Restarting those applications updates them with the fixes.
3. WebSphere Application Server components: You can use the Automated Deployment Utility (ADU), manually upgrade (refer to the update instructions in each WebSphere Application Server component doc folder), or, in a WebSphere Application Server Network Deployment configuration, use the Deployment Manager.
   Note: Refer to "WebSphere Application Server 9.0.x update issue" in "Common Across Releases" > "Known Issues".
   1. All WebSphere servers must be restarted after all the components were 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 WebSphere Application Server profile deployment. If you are using a new WebSphere Application Server profile and already installed the interim fix onto the prior installation, you must do two deployment passes. The first pass is to do the initial, full product deployment. The second pass is to do those components that are affected by the interim fix.
4. Update your Transaction Server Scheduler.xml file. Refer to the Transaction Server Scheduler XML section in this document. Note: Updating the scheduler file might not be required for your installation.
5. Refer to the release-specific section for any changes that might affect your installation.
6. Start your runtime components.
7. If you are 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.

1. Create your server with <liberty-install-directory>/bin/server create PFSServer.
2. Modify the server.xml.template file located in FTM installation path <installation directory>/shared/vxxx/pfs/WebServices/Liberty/PFS with config values for your install (refer to the following list of things that need to be modified).
3. Rename that file server.xml
4. Copy server.xml and jvm.options into <liberty-install-directory>/usr/servers/PFSServer.
5. Start your server with <liberty-install-directory>/bin/server start PFSServer --clean (--clean is optional).

• Db2 installation location, database name, and port.
• IBM MQ installation location, queue manager name, user, password, and port.
• The db2admin user and password.
• Set currentPackagePath, currentFunctionPath, and currentSchema to your schema name.
• Set the password for the FTM administrator ID, which is usually fxhadmin.
• You must ensure that you create a server or update an existing server to run the new version of the IBM WebSphere Liberty RESTful web services.  For more information, see https://www.ibm.com/docs/SSRH46_3.2.12/gpyiybrinstlibty.html

Perform Actions Dialog

Overview

The Perform Actions dialog renders the dynamic configured parameters for each defined action for the Base application. In addition, some existing menu actions such as Transmission Accept, Reject or Batch Accept, Reject are also now merged onto the new Perform Actions dialog. The merged actions will also render the necessary parameters based on the configuration.

This new Perform Actions dialog is applied to Inbound Transmission, Inbound/Processing Batches and Inbound Transactions screens.

The configurations are in Base application’s configuration DSU spreadsheet. For example, the Sample[ReferenceApp]Configuration.xlsx has a new Perform Action Configuration sheet that lists all the actions that require the parameters. If the actions are not defined in the sheet, that action does not require the parameters.

The configuration is an XML format that can be loaded by DSU at the time of initial deployment.

The new dialogs can be accessed from the Grid screen action icon for each UOW screen.

The following is a sample XML that can be configured.

Note that the key to retrieve the action parameters are the Base application name, action name, Base status and Base subtype.

The Base action parameter (ActionParameter element that is not associated with the group) will be displayed under the Perform Action dialog’s action name.

If any action parameters are associated with the group, they will be displayed under a separate tab.

ActionParameter attributes

Note the Summary Grid will differ for each UOW.
 

Following is the sample xml configuration for the Transaction Level Accept Action.

Note: this action might not apply to all the reference applications.

<?xml version="1.0" encoding="UTF-8"?>

<ActionParameters xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ActionParameters.xsd">

  <ActionParameter

            name="InterBankSettlementDate"

            type="date"

            displayOrder="1"

            required="true"

            regEx="\d{4}-\d{2}-\d{2}"/>

  <Group name="Charge">

              <ActionParameter

                                    name="ChargesAmount"

                                    type="decimal"

                                    length="18"

                                    displayOrder="1"

                                    required="true"

                                    regEx="^[0-9]{1,15}(?:\.[0-9]{1,2})?$"/>

              <ActionParameter

                                    name="ChargesCurrency"

                                    type="string"

                                    length="3"

                                    displayOrder="2"

                                    required="true"

                                    default="SEK"

                                    choices="SEK,DKK"

                                    regEx="[A-Z]{3,3}"/>  

              <ActionParameter

                                    name="ChargesAgent"

                                    type="string"

                                    length="11"

                                    displayOrder="3"

                                    required="true"

                                    regEx="[A-Z0-9]{4,4}[A-Z]{2,2}[A-Z0-9]{2,2}([A-Z0-9]{3,3}){0,1}"/> 

              <ActionParameter

                                    name="ChargesAccount"

                                    type="string"

                                    length="30"

                                    displayOrder="4"

                                    required="true"

                                    regEx="[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}"/>                   

  </Group>

  <Group name="Compensation">

              <ActionParameter

                                    name="CompensationAmount"

                                    type="decimal"

                                    length="18"

                                    displayOrder="1"

                                    required="true"

                                    regEx="^[0-9]{1,15}(?:\.[0-9]{1,2})?$"/>

              <ActionParameter

                                    name="CompensationCurrency"

                                    type="string"

                                    length="3"

                                    displayOrder="2"

                                    required="true"

                                    default="SEK"

                                    choices="SEK,DKK"

                                    regEx="[A-Z]{3,3}"/>

              <ActionParameter

                                    name="CompensationDebtorAgent"

                                    type="string"

                                    length="11"

                                    displayOrder="3"

                                    required="true"

                                    regEx="[A-Z0-9]{4,4}[A-Z]{2,2}[A-Z0-9]{2,2}([A-Z0-9]{3,3}){0,1}"/> 

              <ActionParameter

                                    name="CompensationCreditorAgent"

                                    type="string"

                                    length="11"

                                    displayOrder="4"

                                    required="true"

                                    regEx="[A-Z0-9]{4,4}[A-Z]{2,2}[A-Z0-9]{2,2}([A-Z0-9]{3,3}){0,1}"/> 

              <ActionParameter

                                    name="CompensationCreditorAccount"

                                    type="string"

                                    length="30"

                                    displayOrder="5"

                                    required="true"

                                    regEx="[A-Z]{2,2}[0-9]{2,2}[a-zA-Z0-9]{1,30}"/>       

  </Group>

</ActionParameters>

NLS support rule:

For Name:

The system will search the actionParameter.[parameter name].name key first. If found, the translated label will be used.

However, if the key is not defined, it will check if the XML configuration contains the displayName. If found, it will be used.

If none of key or displayName are used, the parameter name will be used to display the name.

For Help:

The system will search the actionParameter.[parameter name].description key first. If found, the translated label will be used.

However, if the key is not defined, it will check if the XML configuration contains the description. If found, it will be used.

If none of key or description are used, the parameter name will be used to display the help.

For Tab Name:

The system will search the actionParameter.[group name].group key first. If found, the translated label will be used.

If the key is not defined for the group, the group name will be used to display the help.

Permissions Generation Process

For FTM Base applications such as SEPA, HVP and CPS will have new permissions generated when the applications are initially installed.

            The process will follow the following steps.

1. When installed, the FSM_RESOLUTION_ACTION table will contain a list of actions for each application depending on its UOW levels (e.g. Transmission, Batch, Transaction).
2. The system will generate the permission code for each action name.
3. For Transmission, Inbound/Processing Batches and Transactions screen, the permissions will be assigned based on each Base Application.
4. The client will have to assign such permissions separately. Once the permissions are created base on FSM_RESOLUTION_ACTION, they will not be deleted assuming the future release will continue reusing them.

The Check, NACHA and Zelle applications do not have a corresponding Base application. Their default permission will reuse the existing permissions. They will be located under the None Base Application.

Note that some of the Transaction actions are TCH specific permissions, such as Accept Transactions, Accept And Return Transactions and Reject Transactions. Those will not be used anymore. The corresponding permissions are created under FTM IP TCH Application separately.

These old permissions, though no longer used, will remain in the system to support smooth migration. That is because the DB migration precedes the application migration. There may be a window that the old application may be used with the upgraded database and DSU.

Back to contents