“easy-to-release” change manager to reduce risk and cost. · pdf filet24-cm is a...

“Easy-to-release” change manager to reduce Risk and Cost.

T24-CM System Architecture

Process Workflow & Functional Overview

2

3

4

Business Challenge & Solution

Agenda

T24 System Change Process 1

T24 System Change Process

Production Environment

Testing Environment

Dev Environment Packages

Package the data records and routines

Install and test the packages

Release to Production

Packaging and releasing is manual operation

Package installation is mostly manual operation

Package installation is mostly manual operation

For T24 system bug fix or parameters update, data and routines need to be packaged, released and installed across multiple environments of the bank, the following is the normal T24 system change process:


There are many challenges in the standard T24 system change process, T24-CM is designed to provide solutions to these challenges.

Challenge Solution

Chanllenge-1: Package installation operation is mostly manual.

Human mistake cannot be avoided in the manual operations like data record input, authorization, routine catalog, etc…

Automation

Deploy packages automatically, minimize the manual operation

Chanllenge-2: Lack of package dependency management mechanism.

Issue occurs when packages are installed in a wrong sequence.

Dependency Management

Analyze and manage dependency in the repository

Verify dependency during package installation

Chanllenge-3: No result and history tracking

Operation procedure and result are not tracked and cannot be audited

History Tracking

Record history of every operation, the installation result and procedure can be reviewed and actions can be taken for any issue.

Continuing …


Challenge Solution

Chanllenge-4: No recovery mechanism

The installed package cannot be uninstalled in case of deployment failure or issue found

Package Uninstall

Backup is taken before any change, it is easy to restore to pre-installation status by “one-click” operation

Chanllenge-5: Difficult to manage the changes in multiple environments

Difference between environments are managed manually

The synchronization between environments are manual operation

Multi-Environment Management

Environment wise information are managed in the repository.

The difference between environments can be found easily, and the difference can be synchronized automatically

Chanllenge-6: Packaging and delivering changes from development environment is a time consuming manual work

Packaging Facility

Changes can be automatically packaged from dev environment and registered into the repository automatically.

T24

T24-CM System Architecture

T24 Servers

T24-CM Business Logic

Web Server

Repository

OFS HTTP

Browser

T24-CM Plug-in

T24-CM System Components

OFS Listener

T24-CM is a web-based application, all the user operations are done through web browser. The business logic and repository are running in the web server. FTP is used to transfer data files between web server and T24 server. Web server send requests to T24 through standard OFS interface. A new application is developed as a plug-in running in T24 to assist the process.

FTP

Functional Overview – Process Workflow

Packaging (optional)

Package Management

Package Installation

History View

Environment Management

Repository

- Environment Info - Packages - Dependency Info - Installation History - Pre-install backup

1. Create new records for all the environments that need to be managed

2. Package the changes from the dev environment (This operation is not required if the package are delivered from vendor)

3. Register the package into repository.

4. Choose the packages to be installed and click the install button, then the packages are installed into target environment automatically.

5. View the package installation history and actions can be taken from the history view

6. Package can be uninstalled if user choose to do so

The following is the T24-CM main Operation Workflow

Package Uninstall (optional)

Functional Overview – Environment Management


Packaging Package management


History View

Package Uninstall

The T24-CM can mange multiple environments. The following information are maintained in repository for each environments:

- T24 server access information - Package installation status and history. The package installation difference between environments can be found out easily through enquiry.

Features of Environment Management function

Functional Overview – Environment Management

The list of environments that are managed in the T24-CM

Functional Overview – Packaging

Packaging Package

management Package

Installation History

View Package

Uninstall

Packaging the data records and routines from development environment is a manual operation and time consuming. The T24-CM packaging function is to automate the whole process and improve the productivity.

The packaging realize the automation by - Auto packaging the data records in T24 - Auto Zipping and downloading the package from T24 - Auto registering the package into repository The packaging step is optional in the flow. Package can be delivered from Temenos or packaged manually without using T24-CM.


Features of the Packaging function

Functional Overview – Packaging

Packaging Input Screen

Input the new package name and source environment information

Input the data records or routines to be packaged

Functional Overview – Package Management

Package Management


History View

Package Uninstall

The packages need to be registered into the repository before installing. The packages could be either packaged from Dev environment using packaging function, or delivered by Temenos. T24-CM support the following 3 types of packages: -DL.DEFINE -BUILD.CONTROL -Core Patch

The package register process is fully automated. User just need to choose the package file and click the register package button, system automatically analyze the package and update repository with the following information: - The detail of all the components inside the package - The dependency between the new package and all other packages in the repository User can assign the packages to different groups, which can be used for batch installation.

Environment Management Packaging

Features of the Package Management function


Packages List Screen


Details of the package and the package file

List of components in the package

The installation status and history of the package in different environment

Package Detail Screen

Functional Overview – Package Installation


Package management

History View

Package Uninstall

The package installation function improve productivity by automating the installation process, reduce the system risk by automating the dependency validation and result verification.

User can choose to install single package, or install multiple packages by choosing multiple packages or groups.

Before installing, system validate the target environment status to make sure all the depended packages are installed.

System can decide the installation order if multiple packages are to be installed

System take backup of all the components before installing. In case of any failure, the backup can be used for the restoration.

System automatically validate all the components to make sure the routines are cataloged properly and data records are inputted and authorized properly.

All the process steps and results are logged in the repository for user action and audit purpose.


Features of the Package Installation function


1. Dependency Check

2. Decide Installation Order

Check the dependency to make sure all prerequisite packages are installed in the target environment already

Decide the installation order if multiple packages are to be installed

3. Upload Packages

4. File Decompression

5. Preinstallation Backup

7. Record Input/Authorize

8.Result Verification

6. Install Packages

Upload packages to be installed to the target environment

Decompress the package file before installation

Take backup of all the components before installing

Install packages using the T24 standard installation tool

Automatically input and authorize the IHLD and INAU records

Validate all the components after installation

The detail steps of the auto package installation


Brief information and component details of the package to be installed

Process log is displayed in real time while installing

Package Installation Screen

Functional Overview – History View

Package management

Package Uninstall

The installation steps and result of packages and their components can be viewed by using the history view function.

From the history view, system provide facility for user to take various actions: - View all the installation log - View the installation result of packages and components - Reinstall the failed package - For the failed data record, find out the reason by comparing both expected and actual records using the data comparison function - For the failed packages and components, user can choose to ignore the errors or redo the result verification after user manually corrects the errors. - Uninstall the package in case of failure that cannot be fixed or wrong installation


History View


Features of the History View function


Installation History View Screen

Action could be taken to the task

List of all the installation tasks and the status


Installation History Action Screen

The status of packages and components of the installation task

The packages could be uninstalled using this button

If the component is data record, the record detail can be viewed

The process log could be viewed

Functional Overview – Package Uninstall

Package management

History View

In case the package installation failure cannot be fixed, or wrong package is installed, the package uninstall function can be used to restore the backup data or routines.

System validate the environment status before uninstall to make sure there is no newer version of component is installed. System raise error message if the dependency validation fails.

If the dependency validation passed, system automatically install the backup components. The backup installing process is basically same as the package installing process

Environment Management Packaging Package

Uninstall Package

Installation

Features of the Package Uninstall function

Functional Overview – Package Uninstall

Package Uninstall

The package could be uninstalled by clicking this button in the history action screen

Process log is displayed in real time while uninstalling

“easy-to-release” change manager to reduce risk and cost. · pdf filet24-cm is a...

Documents