Canadian Model Bank Installer

The purpose of the installation guide is to explain the process and technical workflow of the CMB installer tool for DS package deployments. FIs can use this CMB installer tool as a handy process to install the DS packages that are delivered by Canadian Model Bank. This process is only applicable for Cpack developments which will process the DS packaging mechanism in a sequential order.

The intended audience for this document is the bank IT staff and IT administrators deploying the package delivered to them.

The CMB Installer tools is used to install the packages delivered as part of Canadian Model Bank. This tool will allow the FIs to install the new modules, fixes and reinstall of existing packages in a handy way by minimising the time. This tool is used for packages that are under Cpack delivery mechanism process. The CMB installer tool will install the packages in a sequential order for easy tracking.

Below are the list of item the package does.

  • Installation of the package in a sequential order.
  • Auto installation of an old package while installing the latest package.
  • Auto authorisation of data records.
  • Produce a log report upon the installation of the packages.
IMPORTANT: This process is same for all the releases from R17 onwards.
NOTE: There are no functional configuration required for this process as it comprises of package deployment and installation process.

First Time Installation

FIs using the CMB installer tool for the first time have to perform the below steps to install the packages in a smoother way.

ClosedStep 1: Download the Packages from the FTP Server
  1. Login to the FTP server.
  2. Select all the packages available.
  3. While transferring the pack via FTP, the transport method must be set to binary.
ClosedStep 2: Download the CMB.PRODUCTS File
  1. Download the CMB.PRODUCTS file from the Common_RoutinesAndLt stream under the FTP folder.
  2. Place it under the &SAVEDLISTS& folder in the environment.
  3. A sample screen shot is provided below.

ClosedStep 3: Place the ‘ScopeList.txt’ under &SAVEDLISTS&
  1. Place the ‘ScopeList.txt’ under &SAVEDLISTS&.
  2. A sample screen shot is provided below.

  3. A sample ScopeList.txt file is provided below.

ClosedStep 4: Configure the Temenos Transact Home Path in the Temenos Transact Environment
  1. Set T24_HOME=D:\CAMB\R17\Temenos\T24\Data\UD.
ClosedStep 5: Create a Folder for Processing the DS Packages
  1. Create a folder under t24 home called DSPackageUpdates as shown below.

ClosedStep 6: Process the DS Package

Below are the steps for installation of the CMB installer tool.

NOTE: The CMB Temenos Transact data installer tool is released as part of Common_RoutinesAndLt DS package, hence it needs to be first released and then other packages can be released.
  1. Create folder called packages under the UD directory and place the DS pack as shown below.

  2. Manually place the jar file under the camnjars folder as shown below.

  3. Once the DS pack and jars are placed in the respective paths, execute the tRun T24PackageInstaller (copy and past the highlighted command) from tafj_shell as shown below.

  4. Upon executing the above command, the system will display the process successful message as shown below.

ClosedStep 7: Release the Data Record
  1. Execute the command tRun packageDataInstaller (copy and past the highlighted command) from tafj_shell to release data records.

  2. Upon executing the above command, the system will release the data records as shown below.

  3. Once executed, the data records will be placed in INAU.
  4. Authorise the below record manually to proceed with the CMB installer tools.
    • OFS.SOURCE>CMB.UPDATES.
    • STANDARD.SELECTION>CMB.SPF.
    • STANDARD.SELECTION>CMB.UPDATES.
    • STANDARD.SELECTION>CMB.PRODUCT.
    NOTE: This is one time setup and hence it needs to be manually authorised for the tool implementation.
  5. A sample screen shot for OFS.SOURCE>CMB.UPDATES is provided below.

  6. A sample screen shot for STANDARD.SELECTION>CMB.UPDATES is provided below.

  7. A sample screen shot for STANDARD.SELECTION>CMB.SPF is provided below.

  8. A sample screen shot for STANDARD.SELECTION>CMB.PRODUCT is provided below.

ClosedStep 8: Authorise the Data Record
  1. Execute the tRun CmbDataInstaller command (copy and paste the highlighted command) in the tafj_shell as shown below.

  2. Upon executing the above command the record will be auto authorised as shown below.

    NOTE: After completing this process all the records will be auto authorised. Please check the logs for any exceptions raised during authorisation.
  3. Once the data installer is completed, the system will generate a logfile in the &SAVEDLIST& folder as shown below.
    NOTE: The log report will be named with the package name along with the release date and time.

    NOTE: In case, if any dependency pack missing error is shown in the report, then take the dependent pack from the FTP server provided and follow the deployment steps mentioned above.
ClosedStep 9: Final Processing of the CMB Installer
  1. Login into Temenos Transactand input the CMB.SPF>SYSTEM record and commit the same
    NOTE: This is an one time process and it has to be done only during the tool installation process.
  2. Once the above steps are completed, validate the CMB.SPF record to make sure the latest version has been updated (Common_RoutinesAndLt – Version 146) in the Camb Updates field.
  3. Once the common package is successfully installed, download all the other packages (except common) and do the installation process by following the above procedure.

Package Deployment Regular Process

FI require an ability to deploy the package in a sequential order. Below are the steps involved in deployment the DS package.

Before deploying the package, the package version needs to be verified:

  • Package deployment of R17_Card_Management_1_Java.jar.
NOTE: This process is same for all the release from R17 onwards.
ClosedStep 1: tRun T24PackageInstaller (Existing Process)
  1. Place the DS pack and the jar file in the respective paths and execute the below command. The below command is used to extract the DS pack in the environment for installation.

  2. Once the above command is executed, the system will copy the libraries and binaries in to the respective folders.

ClosedStep 2: tRun packageDataInstaller (Existing Process)
  1. Execute the below command to release the data records to the system. This process will fetch the data records from the DB pack and release them in the environment.

  2. Once the above command is executed the data records will be released as shown below.

    NOTE: The data records will be release in INAU status.
ClosedStep 3: tRun CmbDataInstaller (New Process)
  1. The below command is used to auto authorise the data record released in the above step.

  2. Upon executing the above command, the system will authorise the data record into the environment as shown below.

ClosedStep 4: Log Report and Dependencies Report
  1. Once the data records are authorised, a log file will be captured for the Cmb.DataInstaller as shown below.

  2. Upon successful completion of the installation, the respective jar file will be updated with the latest version number as shown below.

    • Initial package: Package deployment of R17_Card_Management_1_Java.jar
    • Latest package: Package deployment of R17_Card_Management_3_Java.jar
  3. Initially, the environment has only version 1 installed, now the latest version 3 is being installed (version 2 will be auto installed).
ClosedStep 5 Update Applications
  1. Once the installation process is complete, the system will update the CMB.UPDATES application as shown below with the version details and data record information.

  2. The CMB.SPF application is updated with the latest version number and development reference as shown below.

Dependency Report

FI have the flexibility to produce a dependency report even when no packages are installed. The system will report the error in the log file, and the package will not be installed.

Users can execute the tRun CmbDataInstaller command directly and check the dependency report generated.

When packages are not installed, the system will scan the dependency report so see whether there are installed packages already without any dependency.

In the below example, the system scans and produces the given four packages and lets us whether all the latest updates are installed.

A sample screenshot for the dependency report (ScopeList) is provided below.

NOTE: The scope list is a one-time setup and hence it is not required to be placed every time while executing the installer tool.
  1. Execute the tRun CmbDataInstaller command as shown below.

  2. Upon executing the above command, the dependency report is generated as shown below.
  3. The dependency report will display the missing stream with the latest version of it and suggestions will be provided as shown below.

ClosedManual Instructions

During the package installation if there are any dependencies, the system will update the manual instruction in the dependency report while installing the DSPackages. To validate the manual instruction in the dependency report, the Manual Instruction field from the CMB.UPDATES application must be configured.

  1. A sample screenshot for the validation of the manual instruction is provided below.
  2. View the current version of the package as per below.

  3. Place the DSPackage in the path as per below.

  4. Execute the tRun T24PackageInstaller command as per below.

  5. Libraries and binaries are released successfully as per below.

  6. Execute the tRun packageDataInstaller command as per below.

  7. Packages are deployed successfully as per below.

  8. Execute the tRun CmbDataInstaller command to install the data record.

  9. Data records are installer and authorised successfully as per below.

  10. View the CMB.UPDATES application after installing the DSPakage.
    • Old version = 123.
    • New version = 124.
    • Manual instruction = Yes.

  11. View the log file generated with manual instruction as per below.

    NOTE: If the Manual Instruction field from the CMB.UPDATES aplication is not defined, then the system will not update the manual instruction in the log file.

Install a New Module

FI have the flexibility to install new modules when the CMB installer tool is present in the system.

  1. Place the DS package in the below path.

  2. The ScopeList.txt is placed in the &SAVEDLISTS& folder as per below.

  3. A new product is not present in the scope list as per below.

  4. A new product will not be available in the below applications as well.
  5. The details of the CMB.SPF > SYSTEM are provided below.

  6. The details of the CMB.PRODUCT are provided below.

  7. Execute the tRun T24PackageInstaller.
  8. The system will release the new modules binaries successfully.

  9. Execute the tRun packageDataInstaller.

  10. The package is installed with exception in the CMB.UPDATES application as per below.

  11. Execute the tRun CmbDataInstaller.

  12. The system displays the dependency exception for the new module as highlighted above.
  13. Once the packages are installed, view the log file to check that the data records are authorised.

  14. View the log file.
  15. Data records are authorised.

  16. View the ScopeList.txt upon installing the new module.
  17. The new module is updated to the scope list as highlighted below.

  18. View the manual instruction details as per below.

  19. View the SPF > SYSTEM record as per below. The new modules installed are updated.

  20. View the CMB.PRODUCT application after installing the new module.

  21. Upon installing the new module, the system automatically updates the details in the system.

No Authorisation

During the package installation, FI can decide whether the data record needs to be authorised or not. To achieve this, the No Authorization field from the CMB.SPF application needs to be configured as per below.

The purpose of the No Authorization field is to decide whether data records need to be authorised or not. Allowed values are Yes, No or Blank.

  • Yes: Data records will not be authorised and placed in INAU status.
  • No or Blank: Data records will be authorised.
  1. View the CMB.SPF application as per below.

  2. Place the package in the updates folder and execute the below commands
    • tRun T24PackageInstaller (existing Process).
    • tRun packageDataInstaller (existing process).
    • tRun CmbDataInstaller (existing process).
  3. Upon successful processing of the CmbDataInstaller the data record were placed in INAU as per below.

Install the Package with the Same Version

The installation of the DS package with the same version will allow to install the package and will overwrite the same details.

  1. View the CMB.UPDATES application as per below.

  2. View the fix provided in version 3 of the Navision packages.

  3. View the CMB.SPF application as per below.

  4. Place the same version DS package in the path below.

  5. Execute the commands below:
    • tRun T24PackageInstaller (existing Process).
    • tRun packageDataInstaller (existing process).
    • tRun CmbDataInstaller (existing process).
  6. Upon installing the same version, view the CMB.SPF record as per below.

  7. View the fix below. No change, only the audit field changes are updated as per below.

Download Packages

FI must download the package from the below TCSP portal, where the DS package will be available in the respective streamwise.

  1. Login to the portal.

  2. Navigate to CAMB Updates.

  3. Download the required package.

  4. Click on the download zip file as per below.

Expand/Collapse
Share
Print

In this topic

Copyright © 2020- Temenos Headquarters SA

Published on :
Thursday, October 13, 2022 2:40:38 PM IST

Feedback
x