T24 Startup Manual for Access Banks v1 - SAM-V-IT€¦ · T24 Startup Admin Manual for Access Banks V. 1.5a (Berlin, 27.6.2011, Sven Hoehn) Page 2 / 241 T24 Startup Admin Manual for

T24 Startup Admin Manual for Access Banks V. 1.5a (Berlin, 27.6.2011, Sven Hoehn) Page 1 / 241

T24 Startup Admin Manual for Access Banks


T24 Startup Admin Manual for Access Banks


Table of Content:

T24 Startup Admin Manual for Access Banks..................................................................................................................................................................2

Table of Content: ...................................................................................................................................................................................................................3

1. Introduction.....................................................................................................................................................................................................................6

1.1 Summary and Scope................................................................................................................................................................................................6 1.2 Legal Notice..............................................................................................................................................................................................................6 1.3 Target Group of this Manual....................................................................................................................................................................................8 1.4 Reference to T24 Module Documentation..............................................................................................................................................................8 1.5 Key Contacts of LFS Berlin (IT Department)..........................................................................................................................................................8

2. Architectural Overview of T24 .....................................................................................................................................................................................9

2.1 Architecture Diagram................................................................................................................................................................................................9 2.2 T24 Hardware Requirements ................................................................................................................................................................................10 2.3 Description of Used Software Versions and Preferred Installation Paths ..........................................................................................................11 2.4 General....................................................................................................................................................................................................................13

2.4.1 For Telnet Session..........................................................................................................................................................................................14 2.4.2 For Web Interface Usage ...............................................................................................................................................................................14 2.4.3 For T24 Telnet User........................................................................................................................................................................................14

3. Installing T24 from Scratch in Head Office..............................................................................................................................................................15

3.1 Java .........................................................................................................................................................................................................................16 3.2 JBase.......................................................................................................................................................................................................................25 3.3 BNK Implementation ..............................................................................................................................................................................................34 3.4 Import SQL Database ............................................................................................................................................................................................35 3.5 Install and configure the XMLMSSQL driver ........................................................................................................................................................45 3.6 Mandatory Preparations in OS ..............................................................................................................................................................................61 3.7 TCServer Installation + Patch................................................................................................................................................................................69 3.8 Apache WebServer Install + Implementation of Browser Servlet.......................................................................................................................93 3.9 Implement the T24 Helpfiles................................................................................................................................................................................124 3.10 Client Based Software for Scanner/Camera Handling...................................................................................................................................124

3.10.1 Deal Slip Installation .....................................................................................................................................................................................124 3.10.2 Configuration .................................................................................................................................................................................................124 3.10.3 Image Capture ..............................................................................................................................................................................................126

3.11 Logout from T24 Classic Interface...................................................................................................................................................................132 3.12 Login to T24 Web Interface..............................................................................................................................................................................134


3.13 Logoff from T24 Web Interface........................................................................................................................................................................136

4. Installing T24 Branch Server....................................................................................................................................................................................138

5. Installing T24 Patches...............................................................................................................................................................................................157

5.1 Full Patch Delivery................................................................................................................................................................................................157 5.2 DL.DEFINE. ..........................................................................................................................................................................................................159 5.3 Cataloging objects................................................................................................................................................................................................162

6. Security Settings........................................................................................................................................................................................................164

6.1 SSL for Apache Tomcat.......................................................................................................................................................................................164 6.2 SSL for SQL..........................................................................................................................................................................................................164 6.3 SSH for Administrative Access to Classic Interface ..........................................................................................................................................164

7. Installing LFS Model Bank........................................................................................................................................................................................165

7.1 Full Installation......................................................................................................................................................................................................165 7.1.1 Prerequirements............................................................................................................................................................................................165 7.1.2 Overview........................................................................................................................................................................................................166 7.1.3 Parameter Record.........................................................................................................................................................................................167 7.1.4 Executing.......................................................................................................................................................................................................168 7.1.5 Logging ..........................................................................................................................................................................................................169 7.1.6 Installation and Configuration ......................................................................................................................................................................170 7.1.7 LMB Update ..................................................................................................................................................................................................171 7.1.8 Post Closing database creation ...................................................................................................................................................................173 7.1.9 LMB Restore .................................................................................................................................................................................................174

7.2 Supplementary Installation of Updates and Patches.........................................................................................................................................180

8. Creation of a new branch for T24............................................................................................................................................................................181

9. User Permissions.......................................................................................................................................................................................................188

9.1 General Administrative Users in T24 ..................................................................................................................................................................188 9.2 General Administrative Users in SQL .................................................................................................................................................................190 9.3 Specific LMB User Access Rights Structure and Administration ......................................................................................................................190 9.4 User Generation ...................................................................................................................................................................................................190 9.5 Printer Generation ................................................................................................................................................................................................191

10. Backup and Recovery ...........................................................................................................................................................................................193

10.1 IMPORTANT: DAILY BACKUP PROCEDURES............................................................................................................................................193 10.2 Alternate Manual Backup Procedure...............................................................................................................................................................196 10.3 Recovery Procedure.........................................................................................................................................................................................203 10.4 Alternate Manual Recovery Procedure ...........................................................................................................................................................204


11. Close of Business ..................................................................................................................................................................................................206

11.1 Tasks Before a COB.........................................................................................................................................................................................206 11.2 Run a Cob .........................................................................................................................................................................................................217 11.3 Tasks After a COB............................................................................................................................................................................................224 11.4 Troubleshooting COB.......................................................................................................................................................................................225

12. LOG File Control.....................................................................................................................................................................................................228

12.1 Basic Commands in Jshell...............................................................................................................................................................................228 12.2 HowTo: Use T24 Classic interface ..................................................................................................................................................................228

13. Example Documentation based on T24 Environments in AccessBank Tajikistan.....................................................................................238

13.1 Productive Environment: ..................................................................................................................................................................................238 13.2 Test Environment:.............................................................................................................................................................................................239


1. Introduction

This T24 Startup Admin Manual represents the guidelines for the new used banking software T24 from Temenos at Access Banks.

It is a group wide valid IT Startup manual with how-to´s to spread know-how within the Access IT community. It gives you a short

overview of the operational tasks you have to fulfill on your daily work with this software. You can find a short diagram of installed

components and how they interact with each other. This book is growing with the needs for new how to´s within the banks. You

can understand it as a quick reference guide for the daily tasks within the T24.

1.1 Summary and Scope

This T24 Startup Admin Manual is an essential source of information to support daily operations by clear description of all active and proactive tasks to keep the system running and to prevent unplanned outages by providing all information required.

1.2 Legal Notice

Please read this Legal Notice carefully before using this document:

Use

This document (“Manual”) is provided by LFS Financial Systems GmbH as a service to its customers and for general

information purposes for IT operations of Access network banks only (Permitted Use).

This Manual or any information contained herein may not, except where otherwise indicated, be reproduced, duplicated,

copied, transferred, distributed, stored or otherwise exploited for any commercial use without written permission by LFS

Financial Systems GmbH (Prohibited Use).

Copyright

The information contained in this Manual (such information, include, but is not limited to, software and hardware) is owned

by LFS Financial Systems GmbH, unless otherwise stated herein, and are protected by German and international

copyright laws, international treaties and other intellectual property laws.


Unauthorized or prohibited use or distribution of the Manual or any information contained herein may violate copyright,

trademark, and other laws and is subject to civil as well as criminal sanctions.

Disclaimer

LFS Financial Systems GmbH makes no warranties or representations of any kind as to the accuracy, suitability or

completeness of the information, references, links or other items that are contained in this Manual. This Manual is

available to all users "as is" without any representations or warranties of any kind, either express or implied, including

warranties as to merchantability or fitness for a particular purpose. This Manual may contain inaccuracies or typographical

errors.

LFS Financial Systems GmbH makes no warranties or representations whatsoever about any other reference or web site

which you may access through this Manual. Such are provided only as a convenience and does not mean that LFS

Financial Systems GmbH endorses or accepts any responsibilities for the contents or the use of such web sites.

Liability

IN NO EVENT WILL LFS FINANCIAL SYSTEMS GMBH OR ANY OF ITS EMPLOYEES BE LIABLE TO ANY PARTY

FOR ANY DIRECT, INDIRECT, INCIDENTAL, EXEMPLARY, SPECIAL OR OTHER CONSEQUENTIAL DAMAGES FOR

ANY USE OF THIS MANUAL, OR ANY WEBSITE REFERENCED TO OR ACCESSED THROUGH THIS MANUAL,

INCLUDING, WITHOUT LIMITATION, ANY LOST PROFITS, BUSINESS INTERRUPTION, LOSS OF PROGRAMS OR

OTHER DATA ON YOUR INFORMATION HANDLING SYSTEM OR OTHERWISE, EVEN IF LFS FINANCIAL SYSTEMS

IS EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

General

If any provision of this Legal Notice is held by any court or other competent authority to be void or unenforceable in whole

or part, the other provisions of this Legal Notice shall continue to be valid.

This legal notice shall be governed by and construed in accordance with laws of the Federal Republic of Germany.

Disputes arising in connection with this legal notice shall be subject to the exclusive jurisdiction of the German courts.


This agreement shall be governed and construed with German law. Place of fulfillment is Berlin, Germany. Place of

jurisdiction is Berlin, Germany.

1.3 Target Group of this Manual

This Manual is written for the IT Manager and IT Administrators of the operational environment of the LFS Model Bank

software based in T24forMCB R08.

1.4 Reference to T24 Module Documentation

1.5 Key Contacts of LFS Berlin (IT Department)

Head of IT Jürgen Rausch

[email protected]

Manager IT Operations Norman Kruner

[email protected]

Manager IT Development Stephan Hödtke

[email protected]

Members of Team IT Operations Sven Höhn (Specialist Hosting) Oliver Heinze (Specialist Hosting) Lutz Steinmetz (Specialist IT Security) Jörn Graul (Specialist Internal IT and Purchasing)

[email protected] [email protected] [email protected] [email protected]

Members of IT Development Andreas Baginski (Software Architect) Thibaut Dablemont (Software Developer) Fred Gröger (Specialist IT Development) Alfredo Soto (Specialist IT Development) Alin Stefaniu (Software Developer) Stephanie Zickert

[email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

Member of IT Tester Axel Siewert (Specialist Software Testing) Katrin Handke (Software Tester)

[email protected] [email protected]


2. Architectural Overview of T24

2.1 Architecture Diagram

Tier 1

Database Layer

Tier 2

Application Layer

Tier 3

Web Layer

Multi Tier Architecture

Installed Components

(64bit)


(64bit)


(64bit)

MS SQL

Server

2003/2008

SQL Client Java SDK Jbase

Windows

Server

2008 SDK

TC ServerT24 SQL

ConnectorT24 (bnk)

Java SDK

Apache

Web

Server


T24 Architecture Diagram


2.2 T24 Hardware Requirements


2.3 Description of Used Software Versions and Preferred Installation Paths1

1 Important: T24 is based on 64-bit architecture. Especially for 3rd party products you have to use 64bit editions (java, apache etc.)


When setting up the T24 environment we always use the same folder structure for the installed components. Here is an example: E:\T24\ E:\T24\3rd party E:\T24\3

rd party\java

E:\T24\3rd

party\Tomcat 5.5 E:\T24\BNK E:\T24\jbase E:\T24\R08_RC _Helptext E:\T24\tcserver E:\TEMP.RELEASE


2.4 General

This document defines the naming conventions for the T24 environments in the countries. These should be followed to ensure that the entire T24 application has a consistent look and feel all over Access Banks. The following abbreviations are proposed: - LMB (LFS Model Bank) – the generic part - LMBTJ (LFS Tajikistan) - LMBAZ (LFS Azerbaijan) - LMBZA (LFS Zambia) - Etc. If you want to install T24 environments for special purposes we defined some fixed naming conventions and a part of variable naming convention. We divide into four categories of environments (fixed): - Test - Dev - Live - Misc

The naming conventions are defined as followed (examples based on T24 environments for Tajikistan): LMBTJ-TEST LMBTJ-DEV LMBTJ-LIVE LMBTJ-MISC The variable part is based on a special functionality of the environments. When we implement T24 in Accessbanks we have a preoperational phase where a lot of tests will take place. E.g. we have an User Acceptance Test (UAT) or Trainings we define the T24 naming convention as followed (examples based on T24 environments for Tajikistan): LMBTJ-UAT LMBTJ-Training


2.4.1 For Telnet Session

To open a telnet session with T24 Applikation server you have to announce the application server where the jbase instance is installed and the so called „jBASE Telnetd Server“ is running. As described above this is always the Application server. To run a telnet session just click start�run� and type in the box „telnet %servername%“, where %servername% is the name of the application server. E.g. telnet sabtj005

2.4.2 For Web Interface Usage

To work with the T24 web interface you have to open the internet explorer or mozilla firefox on your local machine and type in the following URL: http://%servername%:8080/%env-name%/servlet/BrowserServlet %servername% = the name of the web server as described in one of the above chapters %env-name% = The name of the T24 environment which you want to connect with E.g. (based on T24 environment in Tajikistan) http://sabtj007b:8080/LMBTJ-TRAINING/servlet/BrowserServlet Important: The URL is case sensitive. So please check the right syntax if you are not able to connect to T24 via Web Interface!

2.4.3 For T24 Telnet User

For each T24 environment you need a local account with administrative rights to connect via telnet Interface to T24 Classic. The naming conventions for these users are based on the naming convention for the environments. Example: T24 environment: LMBTJ-TRAINING Username: LMBTJ-TRAINING The passwords for these users should be set with the password policies you defined and proposed by our Operations Manual.


3. Installing T24 from Scratch in Head Office

This installation procedure is based on a single machine installation with T24 R08_002 and Jbase 5.0.17 versions. Multi machine installations and usage of other software versions can differ from this scenario. System Requirements:

- All installation files are based on a 64bit system architecture (not possible to install the whole system on 32bit environments!)

- Ready installed Windows Server 2003 R2 incl all Service Packs o Drive C: System (20GB primary partition) o Drive D: Data (rest capacity extended partition) o Drive X: DVD/CD-Rom

- Ready installed MS SQL 2005 Enterprise Server incl SP3 and additional patches and hotfixes (change the installation folder to drive D:\) � follow Installation instructions from the document: sql_install.doc

- Ready installed Windows Server 2008 SDK (change the installation folder to drive D:\) � follow the installation instructions from the document: sdk.doc

General Considerations:

- When installing T24 usings this manual you have to use the same folder structure as mentioned in the document for each component. Otherwise you will get errors because the configuration files contain settings that are especially for the recommended folder structure. You will not be able to run the system with the given configuration files if you use a different folder structure! o Use this structure:

D:\T24\ 3rd party\ Java\ jre1.5.0_12 BNK jbase5\ 5.0 R08_RC _Helptext tcserver

- Check if all the needed installation files are present in the T24 installation folder:

o \T24_Install\3rd party\jre-1_5_0_12-windows-amd64.exe o \T24_Install\64bit_jbase5_5.0.17_windows.exe o \T24_Install\LFSF.R08.002.MSSQL.win64.jbc5017.T24MCB.production.20091204.zip


o \T24_Install\LFSF.R08.bak.zip o \T24_Install\XMLMSSQL_350_Win64.zip o \T24_Install\TC_1.5.2_8.zip o \T24_Install\3rd party\apache-tomcat-5.5.28.exe o \T24_Install\Browser_R08.002.08_ARC.zip o \T24_Install\T24_R08_RC12_UserGuide.zip o The folder \T24_Install\T24 Config Files

3.1 Java

To start the installation procedure run: jre-1_5_0_12-windows-amd64.exe from installation folder (\T24_Install\3rd party\)

click „Run“


Choose „Custom setup“ and click „Accept”


Change the installation path as in screenshot and click “Next” (Important drive D:\ !!!)


Click „Finish“ For using the java environment we have to set a new system variable in Operating System Open “System Properties”


Go to “Advanced” Tab and click „Environment Variables“


Click „New“ in section „System variables“


Set Name and Value see below

Click „Ok“


also edit the PATH variable and add the path to the binary folder from the java installation (D:\T24\3rd Party\Java\jre1.5.0_12\bin)


Select the PATH variable click edit and add in the end of the variable value line, devided by semicolon the following path: D:\T24\3rd Party\Java\jre1.5.0_12\bin see below


Click „Ok“ Now Reboot your System!

3.2 JBase

For the installation of jbase run “64bit_jbase5_5.0.17_windows.exe” from installation folder (\T24_Install\3rd

party\)

Click “Setup”


Click “Next”


Choose “Customised” and click “Next”


Accept the Agreement and click “Next”


Chance the Home and Installation Path as in screenshot

Click “Ja”


Click “Ja”

Click “Next”


Click “Finish” Now Reboot your System! Manual installation of telnetd service To install the telnetd service: open jshell as see below


Click “jsh”


Type “telnetd install start” and press ENTER Verify if installation was successful, so open “Services” in Windows OS.


jBASE Telnetd Server has to be started. Change Startup Type to “Automatic”

3.3 BNK Implementation To install the BNK directory unzipped the following folder:

LFSF.R08.002.MSSQL.win64.jbc5017.T24MCB.production.20091204.zip


To: D:\T24\ After doing this, copy and overwrite the remote.cmd and jprofile.bat with the following preconfigured files from installation package folder: T24 Config Files\remote.cmd to D:\T24\BNK\BNK.run T24 Config Files\jprofile.bat to D:\T24\BNK\BNK.run

3.4 Import SQL Database

For the SQL DataBase import unzip: LFSF.R08.bak.zip To: Temp or another temporary folder Start SQL Server Management Studio



Type in the name of the Server you install Temenos


Click “Databases” with a right click and than Restore Database..”



Click “Ok”

Click “Add”



Choose the file as in screenshot and click “Ok”

Click “Ok”



Select LFSF2 database and set a tick by “Restore” as seen in screenshot After this choose “Options” under “Select a page” on the left side

Choose the same settings as in screenshot and click “Ok”


Click “Ok”

3.5 Install and configure the XMLMSSQL driver

To install and configure the XMLMSSQL driver, check if the following driver path does exist: D:\T24\BNK\BNK.run\driver\bin check name: config-XMLMSSQL.exe if exist, execute this file if not, uncompress from installation folder to D:\T24\BNK\BNK.run\driver and execute After execute config-XMLMSSQL.exe the following window appears


Type: “1” and press ENTER (for Database settings)


Type “2” and press ENTER (for Set Server)


Enter the SQL Server name and press ENTER


Type “3” and press ENTER (for Set Database)


Enter the Database Name and press ENTER


Type “9” and press ENTER ( for Back to main menu)


Type “2” and press ENTER (for User settings)


Type “2” and press ENTER (for Set SQL user name)


Type “2” and press ENTER (for Set SQL user name) Enter SQL user name and press ENTER


Enter SQL user password and press ENTER


Type “9” and press ENTER (for Back to main menu)


Type “4” and press ENTER (for Test connection)


Press ENTER to continue


Type “6” and press ENTER (for Save and exit) (with executing this file, the following central config file will be created)


This two config files were created: (Check under D:\T24\jbase5\config)

Within a single environment this is no problem. In multiple dev environment this is a typical error source because, every environment uses this central file. But in a mutiple evironment each evironment should have his own config file. This individual config file has to be createt manually for each environment otherwise all environment will use the same database as configured in jedi_config


3.6 Mandatory Preparations in OS

To create a user for the telnetd session open “Computer Management”

Click „Start“ then right click on „My Computer“ and choose „Manage“


Choose „ Local Users and Groups“ and then „Users“


Right click in the right field and choose “New User..”


Type in and set the ticks as in screenshot (PW set by yourself)


Right click on temenos user and choose „Properties“


Choose „Profile“ and type in as in screenshot


Choose „Member of“ and click „Add…“


Enter „Administrators“ click „Check Names“ and than ok


Click “Apply” and than “OK” After this reboot your system.

3.7 TCServer Installation + Patch To run the TC Server properly you have to create an entry in OFS.SOURCE


Log on with “temenos” user


After typing in your PW , Choose “n” and press ENTER


Start T24 with “ETS” press ENTER and then type “EX”


Log in with INPUTT


Type in your password


Type in OFS.SOURCE, I as in screenshot The following view appears



Type in TCS and press ENTER


(Current view)


Change the settings as in screenshot


Check or change settings as in screenshot After this Type “V” for validate and press ENTER Unzip ZIP and TAR files (TC_1.5.2_8.zip) for TC SERVER from installation folder and run: Setup_TCServer.1.5.2_0.bat from unzipped TC_Server folder The following window appears


Press ENTER to continue Type the following path settings in


Type: “n” and press ENTER


Press ENTER to terminate After installation, install the patch (Patch_TCServer.1.5.2_8.bat) So run: Patch_TCServer.1.5.2_8.bat and the following window appears


Press ENTER to continue


Enter the path as in screenshot and press ENTER


Press ENTER to terminate. After the installation oft TCS and the TCS Patch, copy and overwrite tcserver.xml from installation folder to D:\T24\tcserver\conf\TCServer Open a telnet session (telnet localhost)


Click “Ok”

Log in with “temenos” user, choose “n” and press ENTER


Type in: “ -->set < c:\vars.txt “ and press ENTER With this command, you create the file “vars.txt” which contains a few very important paths and settings. Now copy the whole content from C:\vars.txt to D:\T24\tcserver\conf\TCServer\environment.vars into the section <win32> the content of the environment.vars should look like: <win32>


HOME=D:\T24\BNK\BNK.run PATH=D:\T24\jbase5\5.0\bin;D:\T24\BNK\BNK.run\bin;D:\T24\BNK\BNK.run\localbin;D:\T24\jbase5\5.0\bin;D:\T24\BNK\BNK.run\globusbin;D:\T24\BNK\BNK.run\radbin;D:\T24\BNK\BNK.run\driver;D:\Program Files\Microsoft SQL Server\90\Tools\binn;C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\Bin\amd64;C:\Program Files (x86)\Microsoft Visual Studio 9.0\vcpackages;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE;D:\Program Files\Microsoft SDKs\Windows\v6.1\Bin\x64;D:\Program Files\Microsoft SDKs\Windows\v6.1\Bin;C:\WINDOWS\Microsoft.NET\Framework64\v3.5;C:\WINDOWS\Microsoft.NET\Framework\v3.5;C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\WINDOWS\system32;D:\T24\BNK\BNK.run\driver\bin;D:\Program Files\Microsoft SQL Server\90\Tools\binn SHELL=D:\T24\jbase5\5.0\bin\jsh _=C:\WINDOWS\system32\cmd.exe "JBCLISTFILE=D:\T24\BNK\BNK.run\&SAVEDLISTS&" ALLUSERSPROFILE=C:\Documents and Settings\All Users CLIENT_TNID=1100007f01000c ClusterLog=C:\WINDOWS\Cluster\cluster.log CommonProgramFiles=C:\Program Files\Common Files CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files COMPUTERNAME=SLFSA006 ComSpec=C:\WINDOWS\system32\cmd.exe DRIVER_HOME=D:\T24\BNK\BNK.run\driver FP_NO_HOST_CHECK=NO HOMEDRIVE=D: HOMEPATH=\T24\BNK\BNK.run INCLUDE=C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\Include;D:\Program Files\Microsoft SDKs\Windows\v6.1\Include;D:\Program Files\Microsoft SDKs\Windows\v6.1\Include\gl;D:\T24\jbase5\5.0\include JAVA_HOME=D:\T24\3rd party\Java\jre1.5.0_12 JBASE_CODEPAGE=utf8 JBASE_CORE_DUMP=1 JBASE_I18N=1 JBASE_INHIBIT_ZERO_USED=1 JBASE_LOCALE=en_US JBASE_WARNLEVEL=29 JBCDEV_BIN=D:\T24\BNK\BNK.run\localbin JBCDEV_LIB=D:\T24\BNK\BNK.run\locallib JBCEMULATE=prime JBCGLOBALDIR=D:\T24\jbase5\5.0 JBCJREDIR=D:\T24\jbase5\5.0\java\jre JBCJRELIB=D:\T24\jbase5\5.0\java\jre\bin\client;D:\T24\jbase5\5.0\java\jre\lib JBCOBJECTLIST=D:\T24\BNK\BNK.run\lib;D:\T24\BNK\BNK.run\locallib;D:\T24\BNK\BNK.run\globuslib;D:\T24\BNK\BNK.run\GR0800004lib;D:\T24\BNK\BNK.run\radlib;D:\T24\BNK\BNK.run\driver\lib


JBCRELEASEDIR=D:\T24\jbase5\5.0 JBCSPOOLERDIR=D:\T24\jbase5\5.0\jspooler JBC_CLIENT_IP=127.0.0.1 JBC_CLIENT_PORT=1284 JBC_TELNET_FLAG=1 JEDIENABLEQ2Q=1 JEDIFILENAME_MD=D:\T24\BNK\BNK.run\VOC JEDIFILENAME_SYSTEM=D:\T24\jbase5\5.0\src\SYSTEM JEDIFILEPATH=D:\T24\BNK\BNK.run lib=C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\Lib\amd64;D:\Program Files\Microsoft SDKs\Windows\v6.1\Lib\x64 LIBPATH=C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\lib\amd64;D:\Program Files\Microsoft SDKs\Windows\v6.1\Lib\x64 NUMBER_OF_PROCESSORS=2 OFS_SOURCE=TCS OS=Windows_NT PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH PROCESSOR_ARCHITECTURE=AMD64 PROCESSOR_IDENTIFIER=EM64T Family 6 Model 23 Stepping 10, GenuineIntel PROCESSOR_LEVEL=6 PROCESSOR_REVISION=170a ProgramFiles=C:\Program Files ProgramFiles(x86)=C:\Program Files (x86) PROMPT=$P$G SQLSERVERDIR=D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn START.GLOBUS=n SystemDrive=C: SystemRoot=C:\WINDOWS TEMP=C:\WINDOWS\TEMP TERM=vt220 TMP=C:\WINDOWS\TEMP USERDOMAIN=SLFSA006 USERNAME=temenos USERPROFILE=C:\Documents and Settings\Default User VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 9.0 VSINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio 9.0 windir=C:\WINDOWS PWD=D:\T24\BNK\BNK.run JBCBASETMP=D:\T24\jbase5\5.0\tmp\jBASEWORK JBCLKFILE=D:\T24\jbase5\5.0\tmp\LOCKFILE


JBCPAUSEFILE=D:\T24\jbase5\5.0\tmp\PAUSEFILE JBCERRFILE=D:\T24\jbase5\5.0\jbcmessages_en_US JBASE_DATABASE=default </win32> Save the file and exit (Exit also the telnet session) Now reboot your system!


Now we want to setup the tcserver as a windows service. to do so just execute installService.bat from D:\T24\tcserver\bin folder


Finish!

3.8 Apache WebServer Install + Implementation of Browser Servlet To install the apache tomcat, run apache-tomcat-5.5.28.exe from installation folder package


Click “Run”


Click “Next”


Click “I Agree”


Select “Webapps” and click “Next”


Change the destination folder to D:\T24\3

rd Party\Tomcat 5.5 as in screenshot


Check the settings as in screenshot


Change the path as in screenshot (D:\T24\3

rd Party\Java\jre1.5.0_12\)


Click “Finish” Set startuptype from manual to automatic for the apache service in “Windows services” After this reboot your system!

Implement the T24 BrowserServlet

To host the browser servlet extract: Browser_R08.002.08_ARC.zip copy the extracted BrowserWeb.war to D:\T24\3rd Party\Tomcat 5.5\webapps After a few seconds a new folder should be createt under D:\T24\3rd Party\Tomcat 5.5\webapps named BrowserWeb (if necassary please restart apache service in “Windows services”) unzip T24_R08_RC12_UserGuide.zip from installations package to temp folder and copy the unpacked R08_RC


_Helptext folder to D:\T24 Copy and overwrite the browserParameters.xml from Installation folder to D:\T24\3rd Party\Tomcat 5.5\webapps\BrowserWeb Copy and overwrite the helpParameters.xml from Installation folder to D:\T24\3rd Party\Tomcat 5.5\webapps\BrowserWeb Copy and overwrite the browserConnection.xml from installation folder to D:\T24\3rd Party\Tomcat 5.5\webapps\BrowserWeb\WEB-INF\conf Copy and overwrite the channels.xml from installation folder to D:\T24\3rd Party\Tomcat 5.5\webapps\BrowserWeb\WEB-INF\conf As from the delivered installation package two files not exist, we have to create them manually before checking the browser login: Start telnet session

Click “Ok”


Log on wit “temenos” user type “n” and press ENTER


Type “CREATE.FILE F.BR.BRANCH 1 1” (as in screenshot) and press ENTER The following view appears:



Type: CREATE.FILE F.BR.PARAMETER 1 1 (as in screenshot) and press ENTER The following view appears:


Start T24:


Type “ETS” press ENTER and type “EX” and press also ENTER LOG IN to the T24 classic interface with “temenos” user as in other sessions before.


Type “FILE.CONTROL” and press ENTER


Type “I” and press ENTER


Type “BR.PARAMETER” and press ENTER


Change the settings as in screenshot To get an second SUFFIXES entry press " > " and ENTER


Change the settings as in screenshot and validate with “STRG V” and press ENTER Type: “STRG + U” and press ENTER Type: “STRG + U” and press ENTER Until “SELECT APPLICATION” appears on telnet screen


Type: “FILE.CONTROL I BR.BRANCH” (as in screenshot) and press ENTER


Change the settings as in screenshot and validate with “STRG V” and press ENTER Authorise the files which were created Log on with „AUTHOR“ user on T24


Type FILE.CONTROL E (as in screenshot) and press ENTER


Type " 1 " Enter and than: “A” press ENTER and in second line also “A” and than ENTER


Press: “STRG V” and press ENTER to validate this


Press: “STRG V” and press ENTER to validate this


blättern mit strg f bis alle seiten angezeigt wurden, bei anzeigen der letzten seite noch mal STRG V + enter


STRG V enter Scroll with „STRG F“ until all sites were shown, on the last site press “STRG V” and than ENTER Now reboot your system! To start and test the browser connection you have to start the apache tomcat service and tcserver service (it should be start automatically on startup but please check in “windows services”)


To check the installation, try to log in via the browser interface: open browser (for example internet explorer) and type: http:\\localhost:8080\BrowserWeb\servlet\BrowserServlet

Log on with “INPUTT” or “AUTHOR” user (as in classic interface)


The following screen should be appear:

Finish!


3.9 Implement the T24 Helpfiles

In construction

3.10 Client Based Software for Scanner/Camera Handling

3.10.1 Deal Slip Installation

• In order to print deal slips, style sheets must be copied into the following folder on the Web Server:

.\webapps\{WEB_APPLICATION}\transforms\custom\

e.g. \\sabtj005\d$\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-DEV\transforms\custom\

• Create a folder “logo” on the Web Server into the following folder

.\webapps\{WEB_APPLICATION}\plaf\images\

e.g \\slfsa005\d$\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-DEV\plaf\images\logo

• Copy the image “accessbank_tadjikistan.jpg” in the created folder “logo”

e.g. \\slfsa005\d$\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-DEV\plaf\images\logo\accessbank_tadjikistan.jpg

3.10.2 Configuration

T24 In order to print the deal slips locally the user needs to configure properly his T24 user in the browser preferences:

• Open the application BROWSER.PREFERENCES

• Enter your user id

• Select “Local” for “Print Location”


• Valid the record with an other user if it is necessary

• Relog with the user in T24

Internet Explorer In Internet Explorer, go to Page Setup, and set the Header and Footer as Empty


NOTE: Dealp slips have been implemented to support Internet Explorer 8.0. Don’t print them with

any other browsers.

3.10.3 Image Capture

3.10.3.1 Installation

The Javascript functions for acquiring images must be added to the custom.js file on the Web

server. That custom.js file is under:


\\{SERVER_NAME}\d$\T24\3rd Party\Tomcat 5.5\webapps\{WEB_APPLICATION}\scripts\custom.js

e.g. \\192.168.0.54\d$\T24\3rd Party\Tomcat 5.5\webapps\LMBTJ-TEST01\scripts\custom.js

Install on the computer the Twain ActiveX control from Ciansoft.

3.10.3.2 Configuration

In Internet Explorer the following settings has to be set:

• Tools > Internet Options > Security > Trusted Sites > Sites: As Web site add the address of your T24 server

(e.g. http://192.168.0.30)

• Tools > Internet Options > Security > Custom Level

Enabling or prompting "Initializing and Script Activex controls not marked as safe".

Note 1: ActiveX control is a Microsoft technology which only works on Internet Explorer. Any other browsers do not support the use of ActiveX controls.

Note 2: To ensure that you are using custom.js with the new JavaScript functions, refresh the cache of

your browser (CTRL + F5).

Login to T24 Classic Interface The T24 Classic Interface is only used for administrative purposes. Within this interface you run COB´s or install patches. The normal user should have no possibility to interact with the T24 system. To login to T24 Classic interface just do the following: Click Start � Run and type in telnet %servername% (where servername is the App server where T24 is installed):


After you press enter you will get the following welcome screen:

Here you have to type in your T24 login name (local account from App Server):


Now enter the password for this User and press enter. The following should appear:

Now yu are in T24 jshell environment. Type „ETS“ and confirm with enter:


Then type „EX“ and confirm with enter to get the login screen from T24 classic interface:

Here you just have to follow the instaructions on the bottom of the screen (PLEASE ENTER YOUR SIGN ON NAME) Please have in mind that any commands in T24 has to be typed in in upper case letters!


After you type in your logon name and confirm with enter you will be asked to enter your password:

After typing in the correct password you are successfully logged in to T24 Classic interface:


3.11 Logout from T24 Classic Interface

Dependend on which submenue you are actually on your T24 application press STRG+U and confirm with enter. Do this action so often until you are in the start screen of T24. You can see this on the top of the screen the coloured „SELECT APPLICATION“ headline. When you reach this side just type under action „BK“ and confirm with enter:

After confirming with enter the following screen appears:


Now just type „exit“ and press enter. The windows will close automatically or you get the information „connection to host lost“ and you are properly logged out from the system.


3.12 Login to T24 Web Interface

The T24 Web Interface is the only interface for the end user. All the stuff members of the banks have to work with this interface to fulfill their daily tasks. Open your Internet Explorer (or Mozilla Firefox) and type in the address of your T24 Web server and the appropiate environment (you get the right URL from your administrator). After pressing enter you will get the following login page:


Type in your T24 login credentials. After successfull login you will get the following page:


3.13 Logoff from T24 Web Interface

To logoff from T24 Web Interface you just have to click the cross symbol on your welcome.

Sometimes T24 opens an additional windows (internet explorer sessions). You have to close all the additional windows before logoff from T24 Web Interface. Just close the windows by clicking the cross on the upper right corner.


When you are logged out successfully you will receive the following screen:

Here you can go back to the login screen by clicking „T24 Sign On“ or just close the Internet Explorer.


4. Installing T24 Branch Server

- Download Apache Tomcat 5.5.32 32-bit edition from the following link:

o http://ftp.halifax.rwth-aachen.de/apache/tomcat/tomcat-5/v5.5.32/bin/apache-tomcat-5.5.32.exe

- Download Java Runtime Environment 5.0 Update 12 from the following link:

o http://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/VerifyItem-Start/jre-

1_5_0_12-windows-i586-

p.exe?BundledLineItemUUID=LKeJ_hCyQUcAAAEt9yZKPOYD&OrderID=db2J_hCyt88AAAEt2SZKPOYD&ProductI

D=QGnACUFBE3kAAAEY0f05AXuX&FileName=/jre-1_5_0_12-windows-i586-p.exe

- Install Java as shown in this setup example (please use the same folder structure as used in your environment, means

install on drive E:\T24\3rd party\java)

To start the installation procedure run: jre-1_5_0_12-windows-i586-p.exe from installation folder

click „Run“


Choose „Custom setup“ and click „Accept”


Change the installation path as in screenshot and click “Next” (Important drive E:\ !!!)


Click „Finish“ For using the java environment we have to set a new system variable in Operating System Open “System Properties”


Go to “Advanced” Tab and click „Environment Variables“


Click „New“ in section „System variables“

Set Name and Value see below


(Important drive E:\ !!!) Click „Ok“

also edit the PATH variable and add the path to the binary folder from the java installation (E:\T24\3rd Party\Java\jre1.5.0_12\bin)


Select the PATH variable click edit and add in the end of the variable value line, devided by semicolon the following path:E:\T24\3rd Party\Java\jre1.5.0_12\bin see below

(Important drive E:\ !!!) Click „Ok“ Now Reboot your System!


- Now install Apache Tomcat (to drive E:\T24\3

rd party\Tomcat 5.5)

To install the apache tomcat, run apache-tomcat-5.5.32.exe from installation folder package (please use the same folder structure as used in your environment, means install on drive E:\T24\3rd party\tomcat 5.5)

Click “Run”


Click “Next”


Click “I Agree”


Select “Webapps” and click “Next”


Change the destination folder to E:\T24\3

rd Party\Tomcat 5.5


Check the settings as in screenshot


Change the path as in screenshot (E:\T24\3

rd Party\Java\jre1.5.0_12\)


Click “Finish” Set startuptype from manual to automatic for the apache service in “Windows services” After this reboot your system! - Rename the browserweb.war to <instance_name>.war and copy it to the new created webapps folder of tomcat (E:\T24\3rd

party\Tomcat 5.5\webapps)

o E.g. LMBTJ-TRAINING.war

- Copy from the T24 Web server (headquarter) the following files/folder to the corresponding folders of your new installed

server

o E:\T24\ R08_RC _Helptext (the complete folder)

o When we want to connect e.g. to the LMBTJ-TRAINING environment copy:


� E:\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-TRAINING\ browserParameters.xml

� E:\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-TRAINING\ helpParameters.xml

� E:\T24\3rd party\Tomcat 5.5\webapps\LMBAZ-MISC\WEB-INF\conf\ browserConnection.xml

� E:\T24\3rd party\Tomcat 5.5\webapps\LMBAZ-MISC\WEB-INF\conf\ channels.xml

o Edit the channels.xml on the new server and change all entries concerning hostname (hostname is the name of the app

server you want to connect):

<?xml version="1.0" ?>    <CHANNELS> <CHANNEL> <NAME>browser.1</NAME> <TIMEOUT>120</TIMEOUT> <ADAPTER> <TYPE>tcp</TYPE> <PORT>7041</PORT> <SUPPLIER> <INITIATOR> <HOSTNAME>SABTJ006B</HOSTNAME> </INITIATOR> </SUPPLIER> <CONSUMER> <MAX_SESSION>5</MAX_SESSION> <ACCEPTOR> <BACKLOG>30</BACKLOG> </ACCEPTOR> </CONSUMER> </ADAPTER> </CHANNEL> <CHANNEL> <NAME>browser.2</NAME>


<TIMEOUT>120</TIMEOUT> <ADAPTER> <TYPE>tcp</TYPE> <PORT>7042</PORT> <SUPPLIER> <INITIATOR> <HOSTNAME> SABTJ006B </HOSTNAME> </INITIATOR> </SUPPLIER> <CONSUMER> <MAX_SESSION>5</MAX_SESSION> <ACCEPTOR> <BACKLOG>30</BACKLOG> </ACCEPTOR> </CONSUMER> </ADAPTER> </CHANNEL> <CHANNEL> <NAME>downloadChannel</NAME> <TIMEOUT>120</TIMEOUT> <ADAPTER> <TYPE>tcp</TYPE> <PORT>7043</PORT> <SUPPLIER> <INITIATOR> <HOSTNAME> SABTJ006B </HOSTNAME> </INITIATOR> </SUPPLIER> <CONSUMER> <MAX_SESSION>5</MAX_SESSION> <ACCEPTOR> <BACKLOG>30</BACKLOG> </ACCEPTOR> </CONSUMER> </ADAPTER> </CHANNEL> <CHANNEL>


<NAME> mq.sample </NAME> <TIMEOUT> 15 </TIMEOUT> <ADAPTER> <TYPE> mqseries </TYPE> <MQHOST>localhost(1414)</MQHOST> <MQMANAGER>qm.test</MQMANAGER> <MQQUEUE>test.in</MQQUEUE> <MQCHANNEL>ch.test</MQCHANNEL> <CONSUMER>    <REPLYQUEUEPARAMETERS>QUEUE</REPLYQUEUEPARAMETERS> <MQHOST>localhost(1414)</MQHOST> <MQMANAGER>qm.test</MQMANAGER> <MQQUEUE>test.out</MQQUEUE> <MQCHANNEL>ch.test</MQCHANNEL> </CONSUMER> </ADAPTER> </CHANNEL> </CHANNELS> - Test the connection from the branch by typing in the following link:

o http://%branch_server_name%:8080/LMBTJ-TRAINING/servlet/BrowserServlet

Where %branch_server_name% is the name of the new branch server


5. Installing T24 Patches

Patches can be provided in number of ways.

5.1 Full Patch Delivery

Usually T24 core system patches that are delivered by Temenos Help Desk are sent in a form of compressed file named R08XXXX.zip (where XXXX is a patch number and R08 is the main T24 release number). In order to restore this kind of patches one has to user core GLOBUS.RELEASE mechanism. There can be additional instructions sent on the e-mail that contains the patch. The additional instructions have to be strictly followed. The mechanism of GLOBUS.RELEASE should be used in the following way: • There should be a directory TEMP.RELEASE in the application server. It is common for all environments (in case

there is more than one in the server). Usually in LFS Model Bank architecture it is a subfolder of “T24” main folder (\T24\TEMP.RELEASE)

• The patch need to be uncompressed to the directory so that all the patch files are in the subfolder with the patch name:

• When the patch is already copied to the directory (as above) then GLOBUS.RELEASE utility should be started from

T24 command line in classic mode. Since the same utility is used for installing main releases, service packs and single patches then it searches thru TEMP.RELEASE folder and will display whatever it finds in there – it should at the end display our patch name.

• The patch has to be “Chosen” and installed:


• In case the patch contains I_ files then probably they will need to be copied manually to GLOBUS.BP directory

(subfolder of “bnk”) ; for this there should be additional instructions specified in the e-mail containing the patch • There can also be database records delivered within the patch that require manual authorization by the user; for this

there should be additional instructions specified in the e-mail containing the patch For more detailed description please refer to T24 User Guide (System Administration / Upgrades.pdf).

There can also be patches delivered by Temenos MCB Help Desk that are usually named HDXXXXXX (with XXXXXXX being a patch number). This type of patches very often uses DL.DEFINE utility and also can contain precompiled routine objects that may require cataloging (i.e. linking to libraries). In the compressed patch file there is also always a document describing the content of the file and full instructions that need to be followed for restoring of the patch.

The mechanisms used for patch restoring are described in the paragraphs below.


5.2 DL.DEFINE.

This document contains only brief instructions that need to be followed for patch restoring. For more detailed description please refer to T24 User Guide (system Administration / Data Library.pdf). In order to restore a Data Library (DL) package you need to uncompress and copy the folder containing the package to F.DL.RESTORE directory (in bnk directory):

Then from command line of T24 in classic mode you need to run: DL.PARAMETER V SYSTEM


In field No 4 you should put “..\F.DL.RESTORE” path and in field No 6.1 the name of the package, e.g. TMNS000-LFSF.PAT.101103.WIN64 and commit the record. After that the utility should create a record in DL.DEFINE with the ID of the package. Now you need to execute from command line: DL.DEFINE V TMNS000-LFSF.PAT.101103.WIN64 and commit the record.


At that moment the content of the package should be restored to $NAU files for all database records in the package. The user should now commit and authorize all the received records (e.g. ENQUIRY, VERSION or STANDARD.SELECTION). Each package sent should also be accompanied by detailed instructions saying what records in which applications need to be committed and authorized. Please note that due to cross dependencies the order of committing can be important.


5.3 Cataloging objects

Cataloging is required when a routine is sent as a compiled object. Usually there will be detailed instructions how the objects should be cataloged. In order to catalog a routine you have to • copy it to a directory (usually specified in the instructions) e.g. LOCAL.BP. • make sure to which libraries it should be copied: o T24 core routines are cataloged to libraries in ./globuslib o MCB patches (EMERGE) are in libraries in ./lib o LMB (local development) are in libraries in ./locallib • You can be check if and where the routine was cataloged before. In order to do so you need to run at jshell level a

command: jshow –c <routine.name>, e.g.:

jsh LMBTJ-PROD ~ -->jshow -c EBR.LMB.LIMIT.BRANCH Subroutine: E:\LMBTJ-PROD\bnk\bnk.run\locallib\lib0.dll

jBC EBR.LMB.LIMIT.BRANCH version 5.0 Thu Mar 31 20:18:51 2011

jBC EBR.LMB.LIMIT.BRANCH source file LMB.BP

jsh LMBTJ-PROD ~ --> from the above example you can see that the routine EBR.LMB.LIMIT.BRANCH has been cataloged from LMB.BP directory to libraries in ./locallib • The environment variable JBCDEV_LIB decides to which libraries the routine will be cataloged. The standard

setting is:

JBCDEV_LIB=E:\LMBTJ-PROD\bnk\bnk.run\locallib

• The environment variable that decides where the system searches for libraries and (VERY IMPORTANT!!!) in

which order is JBCOBJECTLIST: JBCOBJECTLIST=E:\LMBTJ-PROD\bnk\bnk.run\lib;

E:\LMBTJ-PROD\bnk\bnk.run\locallib;


E:\LMBTJ-PROD\bnk\bnk.run\globuslib;

E:\LMBTJ-PROD\bnk\bnk.run\GR0800004lib;

E:\LMBTJ-PROD\bnk\bnk.run\driver\lib

The above example shows that libraries in ./lib will have priority over libraries from ./locallib – so it can happen that if new routine by mistake is cataloged to ./locallib (according to standard settings) then still the old one residing in ./lib will be executed. • There have to be instructions (sent with the routine) that will tell how to set up the JBCDEV_LIB variable so that the

routine is cataloged correctly, e.g.:

jsh LMBTJ-PROD ~ -->

jsh LMBTJ-PROD ~ -->SET JBCDEV_LIB=$HOME\lib

jsh LMBTJ-PROD ~ -->

• After the environment variables are correctly setup then the routine should be cataloged: jsh LMBTJ-PROD ~ -->CATALOG LMB.BP EBR.LMB.LIMIT.BRANCH

EBR.LMB.LIMIT.BRANCH

Object EBR.LMB.LIMIT.BRANCH cataloged successfully

Library E:\LMBTJ-PROD\bnk\bnk.run\lib\lib5.dll rebuild okay jsh LMBTJ-PROD ~ -->

• Please check with jshow command (see above) if the routine is cataloged correctly, is not duplicated, etc.:

• After cataloging of the routine you always have to log out and log in again in order to run the new objects.


6. Security Settings

6.1 SSL for Apache Tomcat In construction

6.2 SSL for SQL In construction

6.3 SSH for Administrative Access to Classic Interface

In construction


7. Installing LFS Model Bank

7.1 Full Installation

7.1.1 Prerequirements

To operate correctly LMB.RESTORE.REVISION depends on the Subversion client 'SlikSVN' (32 bit edition) which

can be found at http://www.sliksvn.com/en/download . It should be installed to the standard path 'C:\Program

Files (x86)\SlikSvn'.

After that the working copy has to be created. This is the folder LMB.RESTORE.REVISION reads the files to be

restored from. You can either copy an existing one from another environment and rename it or you can do a

subversion checkout:

svn co --username=<username> --password=<password> <svn server path> <destination path>

e. g.:

svn co --username=temenos --password=temenos http://127.0.0.1:8080/t24envcopy D:\t24envcopyfiles

After that copy all files belonging to LMB.RESTORE.REVISION to the LMB.BP folder of the environment:

I_ LMB.RESTORE.REVISION.COMMON

I_F. LMB.RESTORE.REVISION

LMB.RESTORE.REVISION

LMB.RESTORE.REVISION.AUTHORISE

LMB.RESTORE.REVISION.FIELDS

LMB.RESTORE.REVISION.PROCESS

LMB.RESTORE.REVISION.VALIDATE

LMB.RESTORE.PREPROCESS

LMB.GET.AUDIT.FIELD.INDEXES

LMB.FS.DECODE

LMB.FS.ENCODE


Then adjust I_ LMB.RESTORE.REVISION.COMMON so that it fits your setup of SlikSVN and the working copy

directory:

Finally everything has to be compiled in the environment. Login to jshell and enter these two commands:

SELECT LMB.BP EQ LMB.RESTORE... OR LMB.GET.AUDIT.FIELD.INDEXES OR LMB.FS... EB.COMPILE LMB.BP

7.1.2 Overview

All developed elements (T24 applications, versions, routines, etc. ) of LFS Model Bank application are saved into a central repository (as source files). While LMB.SAVE.REVISION is used by the developers to save the items into this repository, LMB.RESTORE.REVISION tool is to be used to set up or replace certain parts of the LMB application within a certain (Test) environment. In each environment the tool works on a separate working copy of the repository. The user can switch between

� restoring up to the latest repository revision

� restoring a certain revision of the trunk

� restoring without updating the working copy

In the latter case the user will set up the files of the repository’s working copy manually. The LMB.RESTORE.REVISION is a T24 application that can only be used in Classic mode. The user will have to insert a Parameter record first and then (with another credential) authorize it.


Especially during authorization the tool will execute several tasks of checking relations between developed parts, sorting, compiling etc. There will be provided log files for both execution steps which the user can and should check for error messages.

7.1.3 Parameter Record

LMB.RESTORE.REVISION records contain 6 parameter fields:

Mandatory fields are

� 1_DESCRIPTION containing free text to describe the goal of this record and

� 4_PATH to select type of repository handling.

7_CNT is an auto-increment field which is increased by one each time the record is saved. After each execution (authorization) a timestamp is added to 8.1_RESTORED.ON. Repository Handling Possible values for 4_PATH are:

� “TRUNK” to update working copy to a certain revision of trunk before restoring

� “TAGS” to update working copy to a certain tag of repository


� “MANUAL” to omit automatic working copy update and just restore.

If TRUNK is selected, the 6_REVISION field may contain a certain revision number to be used for update. If 6_REVISION is empty the latest revision of the trunk is used. If TAGS is selected, the 5_TAGNAME field shall contain the name of the tag to be used for update. If MANUAL is selected, all files that should be restored have to be copied to the ‘manual’ subfolder in the SVN working copy dir of the environment first. You can find the folder name in the file I_LMB.RESTORE.REVISION.COMMON in the LMB.BP folder of the environment. The user may use several parameter records. Normally there’s used only one named TRUNK with an appropriate description and 4_PATH set to “TRUNK” and 6_REVISION set to the desired one. After several usages it may look like:

7.1.4 Executing

The tool LMB.RESTORE.REVISION can be executed only in Classic mode. You have to connect ( e.g. by Telnet) to the desired environment and run it in two steps:

� Open Classic mode as a SuperUser and insert a new version of Parameter record.


e.g. LMB.RESTORE.REVISION I MANUAL

Thanks to the auto-increment field you normally (i.e. when no revision number is needed) do not have to

amend the record but only commit.

� Open Classic mode as another SuperUser and authorize the record.

e.g. LMB.RESTORE.REVISION A MANUAL

7.1.5 Logging

Using the path “{environment}\bnk\bnk.run\LMB.RESTORE.REVISION.LOGS” you may find after each execution two log files named after scheme:

� “{timestamp}_RESTORE_{action}_{record_id}.log”

where {timestamp} is of “yymmddhhmm” format and {action} is “INPUT” or “AUTH” e.g:

After each restoring, especially checking the _AUTH_ log file for lines starting with “!” or containing the pattern “could not” shall be done by the user to check for any issues which may have occurred.


If you are, for instance, using Notepad++ you can doubleclick on any line discovered and thus easily put the editor there to get some more information:

7.1.6 Installation and Configuration

The tool has to be installed to each (Test) environment separately before any restoring of LMB application can take place. Even in case of copying an environment already in use as a new (named) one, the tool newly has to be configured and then recompiled. The file {environment}\bnk\bnk.run\LMB.BP\I_LMB.RESTORE.REVISION.COMMON is used for configuration of the tool, e.g. defining

� the application and credential to access the central SVN repository


� the path to the used SVN working copy or

� t

h

e

items of the black list

After the environment was installed (e. g. by Sven) there is an additional step needed to make the LMB.RESTORE.REVISION working: Please open I_LMB.RESTORE.REVISION.COMMON in LMB.BP and change the value of the variable FN.SVN.WORKING.COPY to the path of the subversion working copy (e. g. 'D:\t24envcopyrestoretest01'). After that please execute the following commands on jshell: SELECT LMB.BP EQ LMB.RESTORE... EB.COMPILE LMB.BP

7.1.7 LMB Update

For each environment there is a folder which has been created for a repository.

� For Development: \\192.168.0.29\e$\t24envcopyrestoredev

� For Training: \\192.168.0.29\e$\t24envcopyrestoretraining

� For UATII: \\192.168.0.29\e$\t24envcopyrestoretraining\uatII

� For UATIII: \\192.168.0.29\e$\t24envcopyrestoreuatIII

� For GoLive: \\192.168.0.29\e$\t24envcopyrestoregolive

In this folder there are 3 subfolders:

� manual

� tags

For all tasks regarding installation or configuration and recompiling of the tool in any environment the development is responsible.


� trunk

For any update LMB-Update on any T24 environments:

1. Do a backup of the bnk folder as well as a backup of the SQL Server Database.

2. If the subfolder “manual” is not empty, delete all the content

3. Extract the LMB archive in the subfolder “manual” of the environment you want to update.

e.g. \\Sabtj006b\e$\t24envcopyrestoretraining\manual.

4. In Classic mode, open in Input (with any @Id) the application LMB.RESTORE.REVISION.

5. Fill the field PATH with MANUAL as well as a DESCRIPTION in the proper field.

6. With another user, you have to valid the record.

7. Finally browse to the folder ..\bnk\bnk.run\LMB.RESTORE.REVISION.LOGS and check the log file.


7.1.8 Post Closing database creation

The Post Closing database is created by T24 COB. In order to create such a database a record needs to be defined in PC.PERIOD application. The below table describes fields in the table:

The following command should be invoked in order to create or amend the PC.PERIOD record: PC.PERIOD,LMB.AMEND Then as the ID of the record a date of reporting period end needs to be specified. The version doesn’t require authorization (0-authoriser).


7.1.9 LMB Restore

7.1.9.1 Overview

All developed elements (T24 applications, versions, routines, etc. ) of LFS Model Bank application are saved into a central repository (as source files). While LMB.SAVE.REVISION is used by the developers to save the items into this repository, LMB.RESTORE.REVISION tool is to be used to set up or replace certain parts of the LMB application within a certain (Test) environment. In each environment the tool works on a separate working copy of the repository. The user can switch between

� restoring up to the latest repository revision

� restoring a certain revision of the trunk

� restoring without updating the working copy

�

In the latter case the user will set up the files of the repository’s working copy manually. The LMB.RESTORE.REVISION is a T24 application that can only be used in Classic mode. The user will have to insert a Parameter record first and then (with another credential) authorize it.


Especially during authorization the tool will execute several tasks of checking relations between developed parts, sorting, compiling etc. There will be provided log files for both execution steps which the user can and should check for error messages.

7.1.9.2 Parameter Record

LMB.RESTORE.REVISION records contain 6 parameter fields:

Mandatory fields are

� 1_DESCRIPTION containing free text to describe the goal of this record and

� 4_PATH to select type of repository handling.

7_CNT is an auto-increment field which is increased by one each time the record is saved. After each execution (authorization) a timestamp is added to 8.1_RESTORED.ON. Repository Handling Possible values for 4_PATH are:

� “TRUNK” to update working copy to a certain revision of trunk before restoring

� “TAGS” to update working copy to a certain tag of repository


� “MANUAL” to omit automatic working copy update and just restore.

If TRUNK is selected, the 6_REVISION field may contain a certain revision number to be used for update. If 6_REVISION is empty the latest revision of the trunk is used. If TAGS is selected, the 5_TAGNAME field shall contain the name of the tag to be used for update. If MANUAL is selected, all files that should be restored have to be copied to the ‘manual’ subfolder in the SVN working copy dir of the environment first. You can find the folder name in the file I_LMB.RESTORE.REVISION.COMMON in the LMB.BP folder of the environment. The user may use several parameter records. Normally there’s used only one named TRUNK with an appropriate description and 4_PATH set to “TRUNK” and 6_REVISION set to the desired one. After several usages it may look like:

7.1.9.3 Executing

The tool LMB.RESTORE.REVISION can be executed only in Classic mode. You have to connect ( e.g. by Telnet) to the desired environment and run it in two steps:

� Open Classic mode as a SuperUser and insert a new version of Parameter record.


e.g. LMB.RESTORE.REVISION I MANUAL

Thanks to the auto-increment field you normally (i.e. when no revision number is needed) do not have to

amend the record but only commit.

� Open Classic mode as another SuperUser and authorize the record.

e.g. LMB.RESTORE.REVISION A MANUAL

7.1.9.4 Logging

Using the path “{environment}\bnk\bnk.run\LMB.RESTORE.REVISION.LOGS” you may find after each execution two log files named after scheme:

� “{timestamp}_RESTORE_{action}_{record_id}.log”

where {timestamp} is of “yymmddhhmm” format and {action} is “INPUT” or “AUTH” e.g:

After each restoring, especially checking the _AUTH_ log file for lines starting with “!” or containing the pattern “could not” shall be done by the user to check for any issues which may have occurred.


If you are, for instance, using Notepad++ you can doubleclick on any line discovered and thus easily put the editor there to get some more information:

7.1.9.5 Installation and Configuration

The tool has to be installed to each (Test) environment separately before any restoring of LMB application can take place. Even in case of copying an environment already in use as a new (named) one, the tool newly has to be configured and then recompiled. The file {environment}\bnk\bnk.run\LMB.BP\I_LMB.RESTORE.REVISION.COMMON is used for

configuration of the tool, e.g. defining

� the application and credential to access the central SVN repository


� the path to the used SVN working copy or

� the items of the black list

For all tasks regarding installation or configuration and recompiling of the tool in any environment the development is responsible.


7.2 Supplementary Installation of Updates and Patches

In construction (Andreas Baginski / Axel Siewert)


8. Creation of a new branch for T24

1. Install a Web Server for the new branch For details please refer to chapter “3.8 Apache WebServer Install + Implementation of Browser Servlet” of this document

2. From T24 system:

a. Create a new Company record by using T24 application COMPANY.CREATE in „V” mode (for more details please check T24 User Guide). Change Branch address is required


As a result there should be a COMPANY record created:


NOTICE: The COMPANY.CREATE utility very often crashes while creating files for the new branch. In such cases please

contact the LFS Competence Center in Berlin immediately.

b. Setup the hierarchy of Department Account Officer records for the new branch:


There should be records created for the new branch, branch departments or even particular users. In the example above a record is created for a user that works in Branch 2 Credit Department.


c. Setup USER records for the new branch (with VERSION USER,LMB.CREATE.USER):


d. Setup TELLER.PARAMETER for the new branch (copy from one of existing records). This action should be done by user

logged in the new Branch:

e. Open tills for all tellers, client advisers, operators and a branch manager (only the tills of cashiers are the proper tills – the others are dummy, usually for the purpose of local development) - this is a task of the Chief Cashier of the new branch,


f. Open all required internal accounts. Please ask for the list of internal accounts at accounting department; All internal accounts that are used by T24 for any background accounting (inter-branch, teller till accounts, etc.) should be opened at least in the local currency; other currency accounts should be opened automatically when required by a transaction, currently know list of internal accounts that have to be opened is following:

i. TJS-10300-0001-0006 (the last 4 digits are specific for the new branch) ii. TJS-11500-0001-0006 iii. TJS-16401-0001-0006

g. Setup Teller Exchange rates (LMB.DEAL.RATES) – this is a task of the Chief Cashier of the new branch.


9. User Permissions

9.1 General Administrative Users in T24 The administrative users should have access to a command line and full access to all programs. This is necessary for cases when a new command might need to be executed. Yet all the flags for logging in of his actions should be set to “Y”. For more details about USER profile setup please refer to T24 User Guide (Security / Security Management System.pdf) Please see below a sample administrative T24 user setup:

USER.ID........... BARIBINSD1

---------------------------------------------------------------------- 1 USER.NAME......... DMITRIJS BARIBINS 1

2 SIGN.ON.NAME...... BARIBINSD01

3 CLASSIFICATION.... INT

4 LANGUAGE.......... 1 English 5. 1 COMPANY.CODE... ALL ALL COMPANIES

6 DEPARTMENT.CODE... 1 Implementation

7 PASSWORD.VALIDITY. 01 AUG 2011 M0601 Every 6 months on day 1

8 START.DATE.PROFILE 01 JAN 1985

9 END.DATE.PROFILE.. 31 DEC 2012

10. 1 START.TIME..... 00:00

11. 1 END.TIME....... 24:00

12 TIME.OUT.MINUTES.. 999 13 ATTEMPTS.......... 9

14 INIT.APPLICATION..

15. 1 CUSTOMER.......

16. 1. 1 ACCOUNT..... 17. 1 COMPANY.RESTR.. ALL

18. 1 APPLICATION.... ALL.PG

19. 1 VERSION........

20. 1 FUNCTION....... A 2 B C D E F H I L P R S V 21. 1 FIEL

22. 1 DATA.COMPARISON

23. 1 DATA 24. 1 DATA


25 SIGN.ON.OFF.LOG... Y

26 SECURITY.MGMT.L... Y

27 APPLICATION.LOG... Y

28 FUNCTION.ID.LOG... Y

29 INPUT.DAY.MONTH... DDMM

30 ATTEMPTS.SINCE.... 31 DATE.LAST.SIGN.ON. 03 APR 2011 32 TIME.LAST.SIGN.ON. 22:35:19

33. 1 PASSWORD....... 34 PASSW.CHANGE.DATE. 17 FEB 2011

35 PASSW.END.DATE....

36 DEACTIVATION.DATE.

37 REACTIVATION.DATE. 38 CLEAR.SCREEN...... Y 39. 1 OVERRIDE.CLASS.

40. 1 AUTH.LEVEL.....

40. 2 CHQ.PRINTER....

40. 3 BRNCH.NO....... 40. 4 LMB.USER.GROUP.

40. 5 LMB.USER.NAME..

41 DEALER.DESK....... 01 TREASURY

42 PRINTER.FOR.RPTS..

43 PRINTER.FOR.P.FUNC

44. 1. 1 GB USER.ADDR

45. 1 RPT.TO.RECEIVE.

46. 1 RPT.COPIES.....

47. 1 LAST.SPOOL.DATE

48. 1 LAST.SPOOL.TIME 49 AMOUNT.FORMAT.....

50 CREATE.GI.USER....

51. 1 GI.USER.NAME...

52. 1 DATE.CREATED...

53 MAX.SESSIONS......

54. 1 ATTRIBUTES..... SUPER.USER 55 DISPO.OFFICER.....

56. 1 DISPO.RIGHTS...

57. 1 SIGN.ON.ITEM...

58 SIGN.OFF.ITEM..... 59. 1 PROCESS.DEPT...

60. 1 OTH.BOOK.ACCESS

61. 1 OTH.BOOK.BLOCK.


62. 1 ALLOWED.DAYS...

63. 1. 1 DAY.ST.TIME.

64. 1. 1 DAY.END.TIME

65 LDAP.ID...........

66 LDAP.DN

67 LEAD.PREF.........

68 DATE.FORMAT....... 1 <DD> <MONTH> <YEAR> 69 OFFLINE.SMS.PROFIL

70 RESERVED.2........

71 RESERVED.1........ 72 RECORD.STATUS.....

73 CURR.NO........... 3

74. 1 INPUTTER....... 6_ADAM.1_I_INAU

75. 1 DATE.TIME...... 19 APR 11 14:33

76 AUTHORISER........ 77 CO.CODE........... TJ-001-0001 BEFOREPROD

78 DEPT.CODE......... 1

79 AUDITOR.CODE...... 80 AUDIT.DATE.TIME...

9.2 General Administrative Users in SQL In construction (Sven Höhn / Stephan Hödtke)

9.3 Specific LMB User Access Rights Structure and Administration

In construction (Stephan Hödtke / Andreas Baginski)

9.4 User Generation In construction (Axel Siewert / Stephan Hödtke)


9.5 Printer Generation

The current architecture of the Access Bank in Tajikistan is only using local printers without any system printer. Thus all printouts are directed to printers that are installed as local to the workstations of the users. In order to redirect all printout to local printers there has to be a record created for each user in BROWSER.PREFERENCES application: USER.ID........... BARIBINSD1 DMITRIJS BARIBINS 1

---------------------------------------------------------------------

1 SKIN.NAME.........

2. 1 ATTRIBUTES..... 3 SAVE.WIN.POS......

4 PRINT.LOCATION.... LOCAL

5 MAIN.SCREEN.......

6 PACK..............

7 ENQ.WILDCARD......

There should however be a jbase spooler active for reports to be generated in T24 (during report creation the system tries to open spooler files and if not existing it may crash the system). The jbase spooler has to be initiated only once by running SP-NEWTAB utility in jshell:

jsh LMBTJ-DEV ~ -->SP-NEWTAB

This operation deletes ALL print jobs and print queues, and re-creates a new spooler with the following criteria:

1) Spooler directory = D:\T24\jbase5\5.0\jspooler

2) Default security of form queues = CREATOR 3) Default security of print jobs = CREATOR

4) Other owners of spooler =

Enter options 1) to 4) to modify, C to continue or Q to quit :

There also should always be two records created in T24 PRINTER.ID application: with ID of HOLD and SYSTEM. They can both be pointing to HOLD (which will only copy the reports to %HOLD% directory (under bnk/bnk.data/eb/ ).


PRINTER.NAME...... HOLD ---------------------------------------------------------------------

1 PRIME.PRINTER.ID.. HOLD

2 DESCRIPTION....... Hold Output - Do Not Print

12 CURR.NO........... 2 13. 1 INPUTTER....... 1_G10.1.02m

14. 1 DATE.TIME...... 29 OCT 99 14:21

15 AUTHORISER........ 16_INPUTTER 16 CO.CODE........... DE-001-0001 LMBTJ-DEV

17 DEPT.CODE......... 200

For more details about report printing please refer to T24 User Guide (System Administration / Report Control.pdf).


10. Backup and Recovery

10.1 IMPORTANT: DAILY BACKUP PROCEDURES

It is of major importance that you do make backups both of the file directory and the database EVERY TIME before you

- Run a COB

- Update the environment (both T24 core, LMB or SQL Reporting Services)!

This is to enable you as local IT Administrators to always return to the last known working environment on your own in case of problems caused by batch jobs (COB,…) or updates (T24, LMB, SQL Reporting).

COB’s or updates are only to be performed after the banks business ended and never in a live working environment via usual business hours! If problems occur while users are still working in the system, then user data will be lost!!!

So it is important to perform the sequence of Backup’s, COB’s and updates in the following sequence:

1. Be sure that the business performance in the branches and in the head office has ended

2. Detach user connections (see chapter “10.1 Tasks before a COB)

3. Make a FIRST BACKUP of the file folder and the database:

run “E:\Tools\ReportsUpdate\ReportsUpdater.exe” on the application server to backup

- the BNK folder, - the T24 database - and also the two SQL Reporting databases


Details for execution please see chapter “10.1 Tasks Before a COB”

This is to allow you to get back to a useful environment in case of COB problems!

4. Perform the COB

5. Make a SECOND BACKUP with “ReportsUpdater.exe “ in a different place (don’t overwrite the first backup!). This is to allow you to get back to a working environment in case of update problems!

6. If T24 updates are available that

a. have been proposed to be implemented by LFS IT

b. have been tested by you (and if related to changes on functionalities also by responsible key business persons) thoroughly on the PRE-PROD environment


c. are fine with the responsible key business persons to be introduced as of today (please coordinate with the key persons beforehand)

you can install them now

Then make a THIRD BACKUP.

7. If LMB updates are available that


b. have been tested by you and the responsible key business persons thoroughly on the PRE-PRO environment


you can install them now.

Then make a FORTH BACKUP.

8. If SQL Reporting Services updates are available that


b. have been tested by you and the responsible key business persons thoroughly on the PRE-PROD environment


you can install them now.

Then make a FITH BACKUP.

9. Restart the environment (see chapter “10.3 Tasks after a COB)

All these backups are needed to enable you to return to the latest trustful working environment on your own and allow time for in-depth analysis of problems in batch or update procedures by LFS IT and/or Temenos Helpdesk.

On the long run you only need to store permanently the backups from before and directly after COB, so that historic analysis is possible. Please also save them to tapes.

Although all changes to a PROD environment have to be tested by you thoroughly on the Pre-PROD environment, problems while performing such actions on PROD environment can appear. The analysis and problem resolution can not be predicted, so only by performing all actions in above sequence including all the backups allows you to realize a start of bank operations on the next day on your own within the banks business hours!


10.2 Alternate Manual Backup Procedure

When backing up a T24 environment it is important that you backup the database and the corresponding BNK folder at the same, otherwise the data are not consistent! T24 spreads some system information across database and file folder.

a) The backup of the T24 folder is really simple. You find the necessary BNK folder under T24 folder on your application server. Just zi the whole folder and copy it to a different location (DVD, tape or external hard drive).

b) The backup of the T24 database should be performed with the „SQL Server Management Studio“ tool. You can find this tool on the T24 Database server. Click start � All Programs � Microsoft SQL Server 2005 � SQL Server Management Studio

Start this tool and you will come the welcome screen where you have to enter your login credentials to the database server:

Connect with the correct credentials to your database server and you will get the following window:


Open on the left pane the Databases section and right click on the database you want to backup.


Choose Tasks � Backup...


On the Destination section choose add and navigate to a folder where you want to write the backup file to. Type in a name for the backup file (include name of database+date.bak)


Confirm twice with ok. Check the other parameter and type once more ok to backup the database


Now the backup process to backup the database is started. You can see the execution status in the bottom left corner of the active window.

The backup process is completed when the following message appears:


Now go via the explorer to the appropriate backup folder and save the file to a different location (where the BNK folder resides � DVD, tape or external hard drive).

Now you are able to restore a T24 environment. Please have in mind that these are only the necessary data to restore an environment. Wit this backup you are not able to install a whole server after a crash. Therefore you need the full backup of the system to be able to make a disaster recovery. This is described in our Operations Manual (note: actually we examining a new backup software and write a new concept for backup scenarios in Accessbanks)

c) In addition this has to be done for the two SQL Reporting services databases (Alin to add).


10.3 Recovery Procedure If there is the necessity to turn back

- A COB because of a chrash

- An update because of a problem in installation (the correctness of the functionality has to be tested BEFOREHAND on the PRE-PROD environment together with the responsible business key users!)

Then again use the tool “E:\Tools\ReportsUpdate\ReportsUpdater.exe”, this time with the button “Restore Selected Backup” after marking the last as working know data set:


Now restart the T24 environment. If the reason for the recovery was a COB crash, please see chapter 10.4 Troubleshooting COB.

10.4 Alternate Manual Recovery Procedure To restore an environment you have to take the backup files you need to restore.

a) First of all delete the BNK folder from the app server. Delete also the database from the db server. Then copy the BNK folder from the backup to your T24 app server in the T24 folder (E:\T24\).

b) To restore the database, log on to the database server and login to your SQL server via SQL Server Management Studio as describe in the backup section.

Right click on the left pane on Databases and choose Restore databases:

Choose „from device“and navigate to your backup folder from where you want to restore the database.


In the section „To database“type in the name of the database you want to restore (pay attention to use the right name. It has to be the same name as from the backup).

Select the check field in the section „select the backup sets to restore“and click ok to restore the database.

Wait until the message appears that the restore was successful.

c) In addition this has to be done for the two SQL Reporting services databases (Alin to add).

After you restore the BNK folder and the appropriate databases you are now able to login to T24 again.


11. Close of Business

COB is the process to close and init the day in T24. There is no open day in T24 because it is done with COB. This process must be run when all tellers have been closed and users logged off.

After the bank’s working day is over and all branches are closed, we need to perform the ‘Close of business (COB)’ procedure. During this, all

calculations for day changing are executed and the data for reporting is copied to the SQL reporting server.

11.1 Tasks Before a COB

BE SURE THAT NO ONE IS LOGGED IN TO THE SYSTEM BEFORE YOU CONTINUE!

This HowTo document was created on LMBTJ-UATII environment, so screen shots may show that name instead of the name of the

productive environment LMBTJ-PROD.

Make sure data export to reporting is working

To ensure this data export will work when COB is in reporting stage, you have to check by executing

LMB.EOD.DATA.EXPORT.TEST from T24 Classic interface:


The result of it should look similar to this:


Disable Internet Explorer access to be sure that nobody else will be logged in to the system

To disable the web interface go to jshell and type cmd. Now you have a windows command prompt and enter net stop “TCS

Service LMBTJ-PROD” to stop the connection service for the web interface. Users will not be able to log in to the system using

Internet Explorer anymore:


To leave windows command prompt type exit and you will be back to jshell.

Stop background services

To be sure that there is no open file handle or database connections we also need to stop all T24 activities running background. This

is done by stopping TSM service. Login using T24 Classic interface and run TSA.SERVICE, I TSM to open the TSM record:


Navigate to field 5 and set it to STOP and commit the record. After that you should wait a few minutes to give the running services

time to terminate.

To check if there are running services you can execute TSA.STATUS L from T24 Classic interface.

Release of left over user logins

It could be that not all users logged off correctly, so that you should close these open sessions. To do this, go to T24 Classic interface

and run ENQ LMB.USERS.STATUS and press “F5” at the next screen. This will give you a list if logged users (remember that there

might be more than one page).

Copy the result list to a text file (e. g. MS Word) and run SIGN.ON.RESET, I 1 IN t24 Classic Interface. Enter all user IDs from

the list (except the user you are logged in with currently). When you finished press “F5” and all open user sessions will be closed.


Backup of the environment This step is most important! If anything goes wrong during COB we can rollback to the current state of the system by restoring the

backup we will create now. Please read entire chapter 9 for further details!

Logoff from the system (all kind of sessions, also T24 Classic interface, jshell etc).

Login to the Application server using Remote Desktop. Run E:\Tools\ReportsUpdater\ReportsUpdater.exe which will guide you

through backup procedure. When asked for a config file select the one in the E:\Tools\ReportsUpdater folder. Then go to the “Full

Environment Backup” tab and choose the environment to backup.

The tool will zip the BNK folder on the application server and trigger a backup of the database files on the database server.

At the end of the backup procedure you should have 4 files.

On application server (in E:\Backup\LMBTJ-PROD):

LMBTJ-PROD_bnk_<date>_<comment>.7z

On the database server (in E:\Backups):

LMBTJ-RPTVWS-PROD_<date>_<comment>.bak

LMBTJ-PROD_<date>_<comment>.bak

On the reporting database server (which is currently the same, but can be different)

LMBTJ-RPT-PROD_<date>_<comment>..bak

You should copy them to a safe place as soon as backup is done.


Click the “Create Environment Backup Now” button and enter a comment, e. g. before COB or something else that helps you to

identify the backup later.


It may happen that you get the following error:


This is caused by open files handles. Make sure that all connections to T24 are closed. It could also be that some background tasks

did not terminate yet. Open a task manager and search for processes that are owned by user LMBTJ-PROD and kill them. After that

click the “Create Environment Backup Now” button to try again.

As soon as the BNK folder was backup up you get the following dialog:


To continue with the backup click the “Close” button.

After all necessary files have been backup up you will be informed if everything went fine:


Click “OK” and click the “Search for existing backups” button. The backup that was just created should show up in the list now.


You can now logoff from the application server and close Remote Desktop.

Copy the backup to a safe place now!

11.2 Run a Cob

Prepare T24 services

Login to T24 via Classic interface and execute TSA.SERVICE, I TSM to open the TSM record. There set field 5 to START:


Commit the record and do the same for the COB record.

You can now run COB.MONITOR in the Classic interface to bring up a screen, the will later show the progress of the COB:


Run the COB

Open three new jshell sessions to LMBTJ-PROD. The first will start the master process, the other two will run the jobs.

Go to the first jshell session and run START.TSM –DEBUG, the DEBUG parameter is needed so that you see the output of the

single COB jobs and can find errors easier:


You now see a list with agents (agents are processes that execute the jobs) and their job. In this example the agents “tSA 5” and “tSA

6” are responsible for the execution of the COB. Remember that these numbers can be different on next COB, so check carefully. Do

not execute any other agent! They are used to run system background tasks which we do not want during COB.

Go to the other two jshell sessions you opened previously and run tSA 5 in one and tSA 6 in the other. This starts the COB and

you see the output of the jobs in the jshell sessions and the overall progress in the COB.MONITOR in the T24 Classis interface:



You can now sit back and wait for the COB to finish. As soon as it finishes, the COB.MONITOR will show again empty progress bars

and in the jshell sessions will be written “Agent stopped”:


Press Q in the COB.MONITOR to close it. Then run TSA.SERVICE, I TSM and set field 5 to STOP. Wait until the jshell session

where the master process is executed also shows the message “Agent stopped” (now all jshell sessions should show this message):


Congratulations, COB is finished!!!

11.3 Tasks After a COB

Finalising steps

Now it is time for another backup of the environment!

Remember to close all open sessions (T24 Classic interface, jshell …).

After the backup is finished and copied to a safe place, open a T24 Classic interface and enter TSA.SERVICE, I TSM and set field

5 to AUTO. Then logout from the system by typing SO and run START.TSM (this time without the –DEBUG parameter because we

want it to run in background):


Now it is time to enable the access for Internet Explorer again. Run cmd to get a windows command prompt and there run net

start “TCS Service LMBTJ-PROD”. After that you can close all sessions.

As a final test, try to login to T24 using Internet Explorer, to be sure that the system is up and ready again.

That’s it, COB procedure is completed!

11.4 Troubleshooting COB

Troubleshooting COB is a very complex topic. T24 is a system that in theory doesn’t need the restore after any error.


Having said that I need to write that during COB the most important is to always have a backup of the database before the COB ☺ In case an error occurs the operator should find out as much information about the error as possible. The information should be visible on the screen where the COB session was running. In case it’s not available any more then the same information can be seen in &COMO& (bnk/bnk.run folder). The log files in there are named with the agent number, date and time. There should also be the error information in T24 files EB.EOD.ERROR and corresponding record in EB.EOD.ERROR.DETAIL. After checking the above the operator should call LFS office in Berlin or if not available then to send a mail to [email protected] titled “COB crash – Urgent”. In case when there is no immediate response the operator should contact Temenos HelpDesk in India / Chennai under the following phone numbers: Tel: +(91) (44) 6551 7701/2/3/4/5 Fax : +(91) (44) 2822 2099 Or send a mail to [email protected] titled “COB crash – Urgent” There are a number of COB jobs that are locally developed. In case when an error appears during the local job then it is up to LFS team to find the reason and resolve the problem. At the moment there are the following COB batch records that are locally developed: • BNK/LMB.COB.CUST.CONTRACT.UPDATE • BNK/LMB.EOD.DATA.EXPORT.FOR.RPT • BNK/LMB.LD.CALC.PROV.CLS • BNK/LMB.PD.EOD.HOLIDAY.ADJ Usually the local jobs have names prefixed with “LMB”. In practice the 2 jobs from the above list can crash by raising a fatal error: • BNK/LMB.EOD.DATA.EXPORT.FOR.RPT – this is a job responsible for data export based on which the SQL

reports are generated later on next day. It may crash when the exported data format is wrong – in order to amend this error the LFS office needs to be contacted urgently.


• BNK/LMB.LD.CALC.PROV.CLS – provision calculations: the job processes all loans in the system. It can crash for the following reasons:

o CUSTOMER record is missing for the contract (not very probably…) o SECTOR is missing for an existing CUSTOMER record of the contract o GIC.LOAN.APPLICATION record is missing for the contract o LMB.RISK.INDUSTRY record is missing for the GIC.LOAN.APPLICATION record

In case when the missing items can be identified then the error can be fixed locally be the operator (probably with help of business bank user). For this the database from before the COB needs to be restored, the missing item amended (restored or added) and the COB can be repeated. Nevertheless the operator before trying to amend the above should first attempt to contact LFS office.


12. LOG File Control

12.1 Basic Commands in Jshell Please refer to sections "SELECT", "LIST", "DELETE" in jBASE Query Language to get an overview how to access jBase database records in jshell.

To edit files in jshell you can use 'jed'. WARNING: If you do anything wrong here the shole system can be currupted and might stop working!!! So if you want to open the record '12345' in 'FBNK.ACCOUNT' type: jed FBNK.ACCOUNT 12345 On the top line you can enter commands like: EX: quit without saving changes FI: quit with saving changes On the lower pane you have the file opened and can edit it. To change between upper and lower part, press 'Esc'.

12.2 HowTo: Use T24 Classic interface

The T24 Classic interface is an additional interface to the web interface for Internet Explorer. It should be preferred for some tasks (e.

g. Close of business) of the IT department. To access the T24 Classic interface we use the terminal software “PuTTY”. It is deployed

together with some additional files that make life easier for the IT team:

The “putty on 32 bit bit OS.reg” should be executed before first use. It imports profiles with correct settings to also be able Cyrillic

letters correctly.


To open a session with T24 Classic interface simply run “start putty.vbs”. The VBS script will also run “Putty_Desktop.exe” which

enables special hotkeys in PuTTY that are useful in T24 Classic interface.

Select the application server you want to connect to (for the environment “LMBTJ-PROD” it is sabtj006). You will be prompted for

“Account Name” and “Password”. For account name please enter the environments name you want to connect to, e. g. “LMBTJ-

PROD”.


Now you are in jshell and start the session from there. First run ETS and then EX which will take you to the T24 login screen where

you can use your T24 credentials:


If the credentials were input correctly you will the command line now:


In the lower left corner you can see at which level you are currently. If it says “AWAITING APPLICATION” you can enter the

application’s name, e. g. PASSWORD.RESET or TSA.SERVICE. For applications there can also be versions like the

“LMB.CREATE.USER” version for application “USER”. If you want to call a version directly simply enter the full name as application, e.

g. USER,LMB.CREATE.USER.

For “TSA.SERVICE” exists the version “TSA.SERVICE,” which does not need authorisation. Let’s now open the record “COB” in input

mode in application “TSA.SERVICE”. First run TSA.SERVICE,:


On top of the terminal window you see the application’s name you are currently in. The prompt now says “AWAITING FUNCTION”.

There are the following functions available:

Function abbreviation Function

I Input (input or amend a

record)

D Delete (remove a non-

authorised record)

A Authorise

R Revert (remove an

authorised record)

L List (lists all authorised

records)

E Exception (lists all

unauthorised records)


So to get to input mode we run I:

Now the prompt says “AWAITING ID” to show that you now can enter the id of the record you want to input. To input the record

“COB” we simply type COB:


Now you see the record’s content. If the record is not existing an empty one will be created. On the right lower corner of the

terminal window you see the page you are currently on. To go the next page press the “F3” button of your keyboard. By pressing the

“F2” button you go one page back. When you press the “F4” button you are taken to the last page.

As you see in the screen shot the fields are numbered. If you want to go to a specific field, enter the number and press “Enter”.


Then you can input new data and press “Enter” again. The numbers of changed fields are marked.


You will be taken to the next field. To skip fields you can again use “F3” and “F2”. If you want to leave the fields area, press “F4”.

When you finished your input you can commit the record by pressing “F5”. To discard the changes press “F1”.

“F1” is also used to go up in the levels so that you can go to another application.

To logout from the system enter SO when the system says “AWAITING APPLICATION”.

You can always see, at which level you are currently, by checking what is written in the left lower corner of the terminal window.


13. Example Documentation based on T24 Environments in AccessBank Tajikistan

13.1 Productive Environment:

Database Server: SABTJ005 All Databases are on Drive E:\default\data All Transaction Logfiles are on drive F:\default\log The Database Name for the production environment is LMBTJ-PROD Login credentials for telnet sessions: Name: LMBTJ-PROD PW: !T24ever2010 Login credentials for T24: http://SABTJ007:8080/LMBTJ-PROD/servlet/BrowserServlet Name: AUTHOR or INPUTT PW: 123456 AppServer: SABTJ006 Folder structure: E:\T24\BNK E:\T24\tcserver E:\T24\3rd party\Java\jre1.5.0_12 E:\T24\jbase5\5.0 Installed services: jBASE Telnetd Server TCS Service LMBTJ-PROD WebServer: SABTJ007 Folder structure:


E:\T24\3rd party\Java\jre1.5.0_12 E:\T24\3rd party\Tomcat 5.5 E:\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-PROD E:\T24\R08_RC _Helptext Installed service: Apache Tomcat

13.2 Test Environment:

Database Server: SABTJ005B All Databases are on Drive E:\default\data All Transaction Logfiles are on drive F:\default\log The Database Names for the test environment are: LMBTJ-DEV LMBTJ-TRAINING LMBTJ-UATII LMBTJ-UATIII LMBTJ-GOLIVE Login credentials for telnet according to the environment are: Name: LMBTJ-DEV LMBTJ-TRAINING LMBTJ-UATII LMBTJ-UATIII LMBTJ-GOLIVE PW: !T24ever2010 Login credentials for T24: http://SABTJ007B:8080/LMBTJ-DEV/servlet/BrowserServlet http://SABTJ007B:8080/LMBTJ-TRAINING/servlet/BrowserServlet http://SABTJ007B:8080/LMBTJ-UATII/servlet/BrowserServlet


http://SABTJ007B:8080/LMBTJ-UATIII/servlet/BrowserServlet http://SABTJ007B:8080/LMBTJ-GOLIVE/servlet/BrowserServlet Name: AUTHOR or INPUTT PW: 123456 AppServer: SABTJ006B Folder structure: E:\T24\BNK E:\T24\tcserver E:\T24\3rd party\Java\jre1.5.0_12 E:\T24\jbase5\5.0 According to the environments: E:\LMBTJ-DEV\BNK E:\LMBTJ-DEV\tcserver E:\LMBTJ-TRAINING\BNK E:\LMBTJ-TRAINING\tcserver E:\LMBTJ-UATII\BNK E:\LMBTJ-UATII\tcserver E:\LMBTJ-UATIII\BNK E:\LMBTJ-UATIII\tcserver E:\LMBTJ-GOLIVE\BNK E:\LMBTJ-GOLIVE\tcserver Installed services: jBASE Telnetd Server TCS Service LMBTJ-DEV TCS Service LMBTJ-TRAINING TCS Service LMBTJ-UATII TCS Service LMBTJ-UATIII TCS Service LMBTJ-GOLIVE


WebServer: SABTJ007B Folder structure: E:\T24\3rd party\Java\jre1.5.0_12 E:\T24\3rd party\Tomcat 5.5 E:\T24\R08_RC _Helptext E:\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-DEV E:\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-TRAINING E:\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-UATII E:\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-UATIII E:\T24\3rd party\Tomcat 5.5\webapps\LMBTJ-GOLIVE Installed service: Apache Tomcat