Please enable JavaScript.
Coggle requires JavaScript to display documents.
TAFJ Administration, ARCHIVE - Coggle Diagram
TAFJ Administration
T24 Upgrade
Pre upgrade
checks
-bankers are supposed to input all transactions before upgrade including all pending transactions
-file layout will be change taking place during upgrade
-No unauthorized records must exist
-All message queue must be cleared & T24 service must be shutdown because information/ advice will be lost, files could be locked, cleared and created during upgrade so it is best that no background process are running.
-No users must be logged in
-Take a backup of complete t24 environment
-Backup old temp.release directory before upgrade
-Set cache to maximum (500) in SPF because it less time required to upgrade and it has be set an IO error.
-Ensure enough space in database because database size increase after upgrade
TAFJ
download latest tafj
-before lunching the Patch_TAFJXXX.sh make sure environment variables $TAFJ_HOME, $JAVA_HOME, $ECLIPSE_HOME are set
-Now eclipse will be restart for loaded new jars
-Manually replace TAFJJ_EE_EAR.ear file to application server like jboss, weblogic or websphere
T24 Libraries
-The procedure to upgrade T24 libraries & data making use to TEMP.RELEASE provided by integration team
-Make sure the existing precompiled jars in a single folder and folder reference to tafj.properties temn.tafj.directory.precompile=new jar directory
-temp release file can downloaded from distribution
Setting TEMP.RELEASE
-untar the zip file a directory temp.release created automatically
-Open the configuration properties add new property JEDIFILENAME_SYSTEM=SYSTEM
-If the SYSTEM directory is not present create using following command DBTools JQL CREATE-FILE SYSTEM TYPE=J4
-Create a record name TEMP.RELEASE inside the SYSTEM
DBTools JQL JED SYSTEM TEMP.RELEASE
1 D
2 D:\TAFJWorkshop\temp.release
Upgrade command
DBTools -s -log tmprelease TEMP-RELEASE D:\TAFJWorkshop\temp.release D:\TAFJWorksho\T24\lib -bp D:\TAFJWorkshop\T24\LOCAL.BP
observe the tmprelease log
-deploying jar files
-deploying source code
-upgrading F.PGM.DATA.CONTROL
-upgrading F.RELEASE.DATA
-T24.UPGRADE terminated successfully
T24.PRE.RELEASE
-you will unable to login t24 after upgrade due to mission OS.TOKEN, OS.TOKEN.USE, OS.TOKEN.XML.CACHE
- To resolve those run a program T24.PRE.RELEASE which is available into temp.release t24bin folder
-this program has a list of hard coded files
-the program try to open those files ,failing which, it creates the file by calling EBS.CLEATE.FILES
-run the program tRun T24.PRE.RELEASE
-After executing the program you should able see a file in &SAVEDLISTS& as named T24.PRE.RELEASE
-
-
AUTO.AUTHORISE
tRun AUTO.AUTHORISE -S (to read from &SAVEDLISTS&
-the program prompts for username/password along with name of file from &SAVEDLISTS&
-
Module upgrade
Manual
-set in SPF (license code for new product) and EB.PRODUCT to enable to module upgrade
-set TEMP.RELEASE and run T24 build libraries for FA product
-on completion on t24 build libraries the corresponding product is updated in the "DATA" field of BNK/T24.UPGRADE
-Module upgrade field in SPF also updated
Auto upgrade
- AUTO.UPGRADE field yes to in SPF file
- untar the temp.release file for upgrade process
- T24.PRE.RELEASE routine will not promt for a user id.
- RUN.CONVERSION.PGMS records are released as live records
- F.RELEASED.RECORDS.LIST provides a key list for any user define enquiry or investigation reports
Pre upgrade
- change right access to temp.release directory
- set JEDIFILENAME_SYSTEM=SYSTEM in tafj.properties file
- if not present then create DBTools JQL CREATE-FILE SYSTEM TYPE=UD
D
temp.release path
- ensure precom
add new product
- add PRODUCTS field in SPF
- applications field in company
- run the service BNK/T24.UPGRADE with product code added in DATA field
4.make sure run directory path is in temp.release
-
SEAT
- turn on OP.CONSOLE in SPF
- for turn off make in <<null>
- results are store in SEAT.RESULTS
- at jbase level the results stored in log files
- possible values for OP.CONSOLE are ON,RECORD,TEST.PERFORMANCE
- log name jNNN.log here j followed by the port number
T24 Update
- create a system definition file using toolbox
- download T24Updates from tcsp
- place the T24Updates to T24_HOME/UD/updater/updates
- setting up updater.xml from /UD/updater/updates/config
- run updater.sh
- after install record can be viewed in T24.UPDTE.RELEASE application with data released filed N means still now not installed
- downloaded update jar is created /TAFJ/updates/<<release_product_component_version>>
- copying the jar from TAFJ/updates to respective place
- run BNK/T24.UPDATES
- run tRun START.TSM -DEBUG
- T24.UPDATE.RELEASE field is C in data field.
- Update install will be updated SPF field T24.UPDATES
- Post installation run the service BNK/T24.AUTHORISE to authorise the INAU record
browser update
- open updater.xml from UD/updater/config folder
- uncomment the service name=browser tag and comment other service tag
- unzip the content place the BrowserWeb.war to deployment folder
- login to browser-->click on help-->about t24 browser
-