ITSS

Chemin du pont du centenaire, 109

CH-1228 Plan-les-Ouates, Switzerland
TEL +41 22 706 20 80 / WEB www.itssglobal.com

jBLoader V2 - User Manual

January 21, 2019

jBLoader V2 – User guide

REVISION HISTORY

Version Description Author Date

1.0 Initial Draft Anbarasan 2017.07.03

VALIDATION

Name Position Role Date

DISTRIBUTION LIST

Name Company Position

January 21, 2019 2/47

jBLoader V2 – User guide

Table of Content
1. GENERAL INFORMATION ........................................................................................................ 4
1.1. Requirement Specification...................................................................................................... 4
1.1.1. Hardware requirement.................................................................................................... 4
1.1.2. Software requirement ..................................................................................................... 4
1.2. jBLoader system files .............................................................................................................. 5
1.3. Loader_Logs ............................................................................................................................ 5
2. JBLOADER GUI ......................................................................................................................... 6
2.1. Home Screen ........................................................................................................................... 7
2.2. Administration ........................................................................................................................ 8
2.2.1. User Profile ...................................................................................................................... 9
2.2.2. Role Maintenance ......................................................................................................... 10
2.2.3. Change Password .......................................................................................................... 11
2.2.4. Parameter Configuration ............................................................................................... 11
2.3. Configuration ........................................................................................................................ 13
2.3.1. Source Configuration ..................................................................................................... 14
2.3.2. Target Configuration ..................................................................................................... 17
2.3.3. Email Configuration ....................................................................................................... 19
2.3.4. Exception Handling ........................................................................................................ 20
2.3.5. Reserved Keywords ....................................................................................................... 20
2.3.6. Email Templates ............................................................................................................ 21
2.4. Migration .............................................................................................................................. 21
2.4.1. Package Migration ......................................................................................................... 21
2.4.2. Scheduler Migration ...................................................................................................... 22
2.4.3. Exception Migration ...................................................................................................... 23
2.5. Metadata Selection ............................................................................................................... 23
2.5.1. Metadata Update .......................................................................................................... 24
2.5.2. Packages ........................................................................................................................ 25
2.5.3. Groups ........................................................................................................................... 30
2.6. Scheduler .............................................................................................................................. 31
2.6.1. Task scheduler ............................................................................................................... 31
2.6.2. Update Scheduler .......................................................................................................... 39
2.7. Reports & Statistics ............................................................................................................... 39
2.7.1. Reports .......................................................................................................................... 40
2.7.2. Logs and Statistics ......................................................................................................... 42
2.7.3. Audit information .......................................................................................................... 43
3. Technical Informations ......................................................................................................... 45
3.1. Starting and Stopping the service ......................................................................................... 45
3.2. Extraction process – multiple files at a time......................................................................... 46
3.3. Troubleshooting .................................................................................................................... 47

January 21, 2019 3/47

jBLoader V2 – User guide

1. GENERAL INFORMATION

jBLoader is a data extraction tool for Temenos T24 with any database. It connects seamlessly to
reporting tools such as, Crystal Reports, Business Objects. It has the ability to extract data directly
from the database server without having any impact on the application server if the source
database is Oracle. In case of other source databases, the extraction will be done at the
application server level.

1.1. REQUIREMENT SPECIFICATION

1.1.1.Hardware requirement

CPU Xeon - Quad core (Minimum 3Ghz)

Memory
32 GB
(RAM)

Hard disk 1 TB (recommended), (Raid 6, DUAL channel & minimum 10K

space RPM)

NIC Gigabit

1.1.2.Software requirement

OS & required components will be available in the jBLoader

OS
consolidated pack

IP IP address of the machine

FTP/SFTP ftp/sftp access between the jBLoader machine & T24 server

T24 database & application server credentials. T24 user will be

T24
required during installation

January 21, 2019 4/47

jBLoader V2 – User guide

1.2. JBLOADER SYSTEM FILES

The hierarchy of jBLoader home directory is composed as follows:

DB_PROPERTIES Database Configuration Files

FOLDER_TEMP jBLoader Temporary Folder

PropertiesFolder (*) jBLoader Package Details

BACKUP_CSV To hold the backup of the extracted csv files

Reports Necessary files to generate reports

PROPERTIESFOLDER

The properties folder contains all jBLoader extraction details. Along with the jBLoader Logs, this
gives a detailed insight of what is happening through an extraction process.

Task_Logs - Each jBLoader defined extraction task is linked to this folder that holds all the task
logs since the beginning

Loader_Logs – Logs updated during the loading process into the target database will be
available under this directory

1.3. LOADER_LOGS

table_name.ctl - The. ctl (control) file consists of the create table syntax and table definitions
which are to be created in the target database.
table_name.log - This file consists of the log content with the successful entries and the cause for
rejection if present.
table_name.bad.csv - This file contains the records that are rejected from the target database with
its corresponding error code and exception

January 21, 2019 5/47

jBLoader V2 – User guide

2. JBLOADER GUI
jBLoader application can be launched by accessing the configured URL.
User’s can login to the application using the provided credentials which was created based on their
usability

Forget Password --> The user can reset their password even before login to the application if they
forget their password. The password will be sent to their registered mail id

January 21, 2019 6/47

jBLoader V2 – User guide

2.1. HOME SCREEN

The landing page of jBLoader will have a list of menus and a dashboard that holds a summary of the
status for the tables being extracted and the list of configured schedulers along with the status.

The schedulers(task) status summary can be viewed for any date from the home page

The different status for a configured scheduler will be displayed as shown below

Scheduler status Description

Scheduler is configured but not activated. Hence the extraction will

not happen until it is activated

Scheduler is active and is ready to be started, the extraction process

will be triggerred shortly

Scheduler is active and the data is currently being extracted in csv

files & completes once the data is loaded in to the target database

Scheduler will complete with warning status if any data has been
rejected during loading process

January 21, 2019 7/47

jBLoader V2 – User guide

Scheduler will complete with Success status if the data extracted

was loaded successfully without any issue

Scheduler will complete with Success status but in a different colour

if the data in the source table is empty

Scheduler will complete with Failed status if the extraction/loading

terminate in an abnormal way

➢ License validity – The validity of the jBLoader application can be viewed from the option
available at the top right corner of the page(info icon)

2.2. ADMINISTRATION

The administration menu is used to have control over the jBLoader users i.e to restrict access to the
jBLoader application based on the user’s usability, and also to configure the basic details required
for the application.

Below are the sub-menus available,

❖ User profile

❖ Role Maintenance

January 21, 2019 8/47

jBLoader V2 – User guide

❖ Change Password

❖ Parameter Configuration

2.2.1.User Profile

A new user can be set up based on the role assigned for them to use the application. And a role can
be changed at this level any time if the admin would like to restrict the access to the application.

An email id need to be configured which will be used while resetting their password.

January 21, 2019 9/47

jBLoader V2 – User guide

2.2.2.Role Maintenance

The user access to the menu will be restricted at the role level. A role can be set up and the required
access to the menus will be assingned to it. So that the user can access only those menus and the
other menus will not be visible in their login.

January 21, 2019 10/47

jBLoader V2 – User guide

2.2.3.Change Password

The password for the currently logged in user can be changed at any time from the application.
Once the password is changed the user can login with their new password into jBLoader.

2.2.4.Parameter Configuration

It holds the default configuration based on various criteria that will be used for the extraction

❖ Basic Parameter

Batch size - Number of records that will be extracted per csv file (Default : 200000)

Thread size - Maximum number of threads used during extraction for a single table (Default : 7)

Write size - Defines the sizes to be written for the no. of column tags parsed (Default : 200)

January 21, 2019 11/47

jBLoader V2 – User guide

Scheduler interval time - Interval time for the scheduler to monitor any change in the
scheduler status inorder to trigger the extraction process(Time in secs)

Dates Table - The actual table name in the source database for DATES table. This is
used to have the current T24 date in all the extracted records in the
target database

Dates RECID - The default record id of the DATES table from the source database

Application home path - The home path of the jBLoader application available in the server. All
the necessary logs and the required license will be available here

Date format - The default date format that has to be used thoughout the application

❖ Additional Parameters

COB Check - To specify whether a COB completion check need to be performed

prior to extraction. Once enabled, the extraction process will be on
hold even during the scheduled time until a confirmation/flat file is
received for the corresponding COB event set at scheduler level

Scheduler Opertaion - To enable/diable all the configured schedules with weekday and
interval option

Selection Criteria Prefix - A variable that can be used in the selection criteria at the
package level, in which the request for the extraction will be sent to
T24 application server

COB Interval Time - Interval time to check the availabilty of the flat file in application
home path. It will be used once the COB Check option is Enabled

Log Notification - To set the various status for which notification need to be sent via
Email upon completion of the scheduler

January 21, 2019 12/47

jBLoader V2 – User guide

2.3. CONFIGURATION

All the major configurations regarding the extraction will be available under this menu. The
source database details(from where data will be extracted) and its corresponding application
server details if required, target database details(data will be stored), email setup, data
exception handling will be configured here.

❖ Source Configuration

❖ Target Configuration

❖ E-mail Configuration

❖ Exception Handling

❖ Reserved Keywords

❖ Email Templates

January 21, 2019 13/47

jBLoader V2 – User guide

2.3.1.Source Configuration

The source database from where data need to be extracted can be any database.

• Oracle : If the database is Oracle then the extraction will be done directly from the database
server and hence the applicaton server is not required. In case if the virtual fields like i-
descriptor / j-descriptor need to be extracted then the extraction will be done in the application
server via T24 service.

• Other databases : For all other databases, the extraction will be done at the application server
via T24 service.

Once the scheduler is executed, the request for extraction will be sent to the application server
with all the required fields to be extracted. And then the jBLoader_T24 service will do the data
extraction in csv files and transfer back the files to GUI for loading it into the target database.

T24 database configuration :

Below are the required details of the source database

✓ Database - Any database(ORACLE/jBase/MSSQL/DB2)

January 21, 2019 14/47

jBLoader V2 – User guide

✓ DB Host - IP address of the T24 database server

✓ DB Port - Accessible port number

✓ DB Conn Type - To be specified whether the connection to the database need to

established based on the service name or SID of the database

✓ Service Name / SID - The service name or the SID of the database

✓ DB UserName - Database username

✓ DB Password - Database password

T24 applicaton server configuration :

Below are the required details of the application server

✓ Communication type - Based on the application server (SHARE/FTP/SFTP)

✓ Host - IP address of the T24 application server

✓ Port - Accessible port number

✓ User name - Server login credential (user name)

✓ Password - Server login credential (password)

✓ IN path (F.ORA.IN) - Folder path in the application server where request will be
sent

January 21, 2019 15/47

jBLoader V2 – User guide

✓ OUT path (F.ORA.OUT) - Folder path in the application server where data will be
extracted

✓ LOG path (F.ORA.LOG) - Folder path in the application server where log will be
updated

✓ ZIP option - To specify whether to compress the extracted csv files in a

single file and then to ftp it to GUI

✓ FTP retry count - Time interval that the GUI will check on the T24 application
server, to verify whether extraction has been finished & the corresponding log is
updated as completed

January 21, 2019 16/47

jBLoader V2 – User guide

2.3.2.Target Configuration

It defines the target database for the extracted data. Multiple JDBC (or other connectors) may be
defined, as it may be desired to extract certain data to one database server and other to another
supported RDBMS.

Below are the required details of the target database

✓ Database - Any RDBMS(ORACLE/MSSQL/DB2)

✓ Host name - IP address of the target database server

✓ DB Port - Accessible port number

✓ DB Conn Type - To be specified whether the connection to the database need to

established based on the service name or SID of the database

✓ Service Name / SID - The service name or the SID of the database

✓ DB UserName - Database username

✓ DB Password - Database password

✓ File Type - If File Type option is enabled single & M1 tables are created in
single(one) table. The multi & Sub values are written in same row with different delimeters.
If this option is selected user needs to specify the multi & sub value marker.

January 21, 2019 17/47

jBLoader V2 – User guide

✓ Column delimiter - Specifies the character that need to be used as a column delimiter
in the data extracted in the csv files

✓ Enclosed delimiter - Specifies the character that need to be used as an enclosure for
the data extracted in the csv files

✓ Commit count - GUI will do a commit to a database once the specified number of
rows here are inserted into the database

✓ Error count - Specifies the maximum number of errors allowed during the
loading process. Once the no. of records that are rejected during the loading process
exceeds this value, the process will be terminated

January 21, 2019 18/47

jBLoader V2 – User guide

2.3.3.Email Configuration

The default email settings for sending notification has to be configured. i.e., smtp host, port are
required along with the mailing address. Multiple mail ids can be configured in To & CC Mail id.
Once the scheduler process completes, an email notification will be sent to the registered mail ids
based on the log notification set.

January 21, 2019 19/47

jBLoader V2 – User guide

2.3.4.Exception Handling

To create the target DB structure jBLoader use the declared structure of the T24 DB and not the
actual data content. Therefore, because of the lack of check in T24 some values could exceed the
declared capacity i.e. an address of 35 characters in a column which has a declared size of 30 or the
declared type is DATE and the actual content is a string. Such discrepancies could be discovered
during the extraction. Nevertheless, there is a methodology to avoid having to perform a complete
extraction to validate the changes.

A record defined in “Exception handling” will be considered while creating the table structure in the
target database. Hence the actual data in source database can be loaded in target db even if there is
a discrepancy in the actual data and the defined structure from T24.

2.3.5.Reserved Keywords

There are cases where the actual column name in T24 is a reserved keyword in SQL. Eg., FUNCTION
in F.USER table. In such case, there will be an error during table creation in target database.

The keywords can be defined under this section, so that the corresponding column will be renamed
while creating it in target database. Ie., For the above mentioned example, the field FUNCTION will
be created as K_FUNCTION in the target database.

January 21, 2019 20/47

jBLoader V2 – User guide

2.3.6.Email Templates

jBLoader have some default email templates that are used to send notifications. i.e., for License
expiry alert and for scheduler completion status. Based on the default language set,the
corresponding template will be used.

2.4. MIGRATION

For the clients already using jBLoader older version either service version or the direct version, it is
easy to migrate them to jBLoader web based version. The necessary components to be migrated
from older version are the packages, tasks & exceptions.

2.4.1.Package Migration

It is necessary to migrate the packages since the client might have created number of packages
based on their requirement. So it is very important to migrate all the packages availabe in the
existing version into new version.

There is an option in previous version of jBLoader to export the configured packages in an xml
format. All those packages can be migrated by uploading those xml files from a single folder.

January 21, 2019 21/47

jBLoader V2 – User guide

Once the update is done, it will display the number of packages migrated successfully out of the
available packages. In case of any issue during migration, the corresponding log will be updated in
‘catelina.out’ available in tomcat folder.

2.4.2.Scheduler Migration

It is also necessary to migrate the schedulers since the task in the older version holds all the
configured tables with scheduled date & time and other detials like full table
extract/incremental,etc... In order to use the same sequence and timing for scheduler with the same
configuration, it is necessary to migrate the tasks.

As like packages, the tasks also can be exported from older version of jBLoader and the same can be
imported into new version. In addition to the xml files, it is mandatory to select the available source
connector during migration process since it is required to store in internal database in new version.

January 21, 2019 22/47

jBLoader V2 – User guide

2.4.3.Exception Migration

Due to data discrepencies there could be lot of exceptions occurred during the extraction process in
older version of jBLoader. All those exceptions might be handled in older version either service or
direct version via JBL.APPL.FLD.EXCEPTIONS table in T24 or Exceptions.xml file respectively, which
need to be migrated to new version in order to handle the same.

The migration process uses exactly the same xml format used in direct version of jBLoader. i.e.,
Exception.xml file can be directly uploaded to update the same in local database in new version.

For the exceptions available in the service version(JBL.APPL.FLD.EXCEPTIONS), a mainline routine

will be provided along with the new pack which need to be deployed in the application server.
Executing the mainline routine will create a file ‘Exception.xml’ in &SAVEDLISTS& folder with all the
available exceptions in the table. This file will be in a required format which will be then used to
upload the exceptions in new version.

2.5. METADATA SELECTION

This is the major section to extract the table structure of all available tables in T24 and to update the
same in local database. And also to setup the required tables to be extracted and its correspoding
fields.

January 21, 2019 23/47

jBLoader V2 – User guide

2.5.1.Metadata Update

jBLoader uses the same data structure of all the tables available in T24 and creates the table with
the same structure in the target database. This helps not only to maintain the same structure and
also to identify the data discrepencies in source database which can be analyzed & rectified. So
during the intial configuration, it is mandatory to do this update with an available option of Upload
type ‘Full’ - in order to fetch all the table structure from source database.

It is also possible to update only specific table’s structure without doing a full upload. Eg., New
applications could have been developed or few fields(local ref) may be introduced in specific
appliciations locally, and only those particular table structure need to be updated in jBLoader local
database. This can be achieved with an option ‘Partial’ update.

There are three different cases that need to be handled based on the actual setup in the source
database. Based on the setup the table structure will be extracted accordingly.

➢ Oracle – If the source database is oracle then there are two possibilities.

1. All tables will be maintained in oracle including VOC file. So the table structure will
be extracted completely from the database server.

2. VOC file alone will be maintained in jBase and all other tables in oracle. The
extraction of VOC file alone will be done at the application server level via mainline
routine and then the update need to be performed from GUI which will then extract
all the other required details regarding table structure from database server.

➢ Other databases – The table structure will be extracted via mainline routine and the extracted
files will be available in the application server in a required format. Once the required files are
available, the update need to be performed from GUI which will update the jBLoader local
database

January 21, 2019 24/47

jBLoader V2 – User guide

2.5.2.Packages

All tables that need to be extracted via jBLoader has to be configured as a package.

Based on the application selected, following columns will be populated automatically with the
possible values available in T24

• File type

List of available file types for the selected application will be populated. Required files to be
extacted can be selected from the option.

Eg., NAU – Unauthorised (FBNK.ACCOUNT$NAU) ; HIS – History (FBNK.ACCOUNT$HIS) ; LIVE

– LIVE file (FBNK.ACCOUNT)

• Company list

All available companies for the selected application will be populated and required company
can be selected from the option. Eg., BNK, EU1,… (FBNK.ACCOUNT, FEU1.ACCOUNT)

And for the installation files which doesn’t have company mnemonic will be displayed as
‘INT’ in the company list. Eg., INT – Installation files (F.COMPANY,F.USER)

January 21, 2019 25/47

jBLoader V2 – User guide

• Fields

All the available fields in the selected application will be populated including Core fields,
Local fields and I & J descriptor fields. It is advised not to extract the I-Descriptor or J-
Descriptor fields since these are virual fields that will have performance impact. If I of j-Desc
fields are included in the package then by default the request will be sent to application
server and the extraction will be done by T24 service.

The tree structure will be like as shown below,

DB table name : It is possible to change the table name that will be created in the target
database. There are some cases where the tabe name exceeds 30 characters which is not allowed
while creating the table & results in error. For such case, it is easier to change the table name at
this level.

Selection Criteria : The selection criteria can be applied either at the database level or
application server level

➢ Database level - The filter will be applied directly at the database level. Ie., the selection of
records will be performed by parsing the xml files available in the db based on the criteria
specified. It is applicable only for single value fields. T24 field name along with the Sql operators
are allowed.

January 21, 2019 26/47

jBLoader V2 – User guide

➢ App. Server level - If the selection has to be done based on multivalue fields then it can be
done at the application server level. In this case the request will be sent to application server and
the jBLoader service will do the extract based on the selection critera provided. Once the
extraction completes the files will be sent back to GUI for loading. This can be done by adding a
prefix in the selection criteria.

The prefix to be used is the variable configured under Administration > Parameter
Configuration menu

Sample processing : It is also possible to extract only a sample of records(may be for testing
purpose)

KEY LIST : we can extract the list of IDs that are available in a record in &SAVEDLISTS&
directory. The record/file name should starts with ‘LIST.’ and in the selection criteria it should
be prefixed with ‘@’

January 21, 2019 27/47

jBLoader V2 – User guide

Routine based selection : You may use a specific subroutine to get the Key List to be processed.
You may build your own subroutine or might use the existing one “JBL.SPECIAL.SELECTION”

The routine must be a subroutine with four parameters & the syntax of the calling routine is
like below. You may change the use of first two parameters, but the purpose of the last two
parameters is fixed.

ROUTINE.NAME(EXACT.FILE.NAME, SELECTION CRITERIA, RETURN.KEY.LIST,ERROR)

With this feature, you may define your own method to build the key list for the main file. The
jBLoader service will call the routine based on the parameters you specify on the SELECTION
criterion for the table as below.

Input the routine name prefixed with the “@” followed by the parameters for the first &
second locations of the routine.

@<Routine name>, <File Name>, <selection>

Dynamic selection : we have an option to do the selection based on dynamic values. Below are
the common variable that can be used in the selection criteria

!Today_YYYYDDD
!Today_YYDDD
!Today_YYYYMMDD
!Today_YYMMDD
!Lworkday_YYYYDDD
!Lworkday_YYDDD
!Lworkday_YYYYMMDD
!Lworkday_YYMMDD
Eg., If we need to select the DE.O.HEADER records generated during last working day then it
can be achieved by having the selection criteria as like below

January 21, 2019 28/47

jBLoader V2 – User guide

This selection criteria will be changed to @ID like ‘D20170101%’ during the runtime; where
20170101 is the last working day in T24.

Sample package

When multiple files types / companies are selected with required fields it will create multiple
packages with the same configuration .ie., If file types - HIS & NAU and company - BNK & EU1 are
selected then upon saving the package will create four different packages like FBNK.ACCOUNT,
FBNK.ACCOUNT.HIS, FEU1.ACCOUNT, FEU1.ACCOUNT.HIS accordingly.

January 21, 2019 29/47

jBLoader V2 – User guide

2.5.3.Groups

Once the package is created it has to be added to a group which will be scheduled for extraction.
Multiple packages can be clubbed under a single group, so that all the corresponding packages in a
group can be scheduled at a same time with the same configuration.

January 21, 2019 30/47

jBLoader V2 – User guide

2.6. SCHEDULER

Below are the menus available to schedule the extraction and to update the scheduler timing for all
weekday jobs if required.

2.6.1.Task scheduler

The scheduler is configured for the group already defined and can schedule it for extraction.

Scheduler Info :

January 21, 2019 31/47

jBLoader V2 – User guide

A scheduler can be setup to execute with the frequency either as one-time or as a recurring one.

➢ If the frequency type is set to ‘One-time Job’ then the scheduler can be started immediately or
at specified time

The below column will be visible only if start frequency is set to ‘At a specific time’ so that the
scheduler start date & time can be specified

➢ If the frequency type is set to ‘Recurring Job’ then the scheduler can be executed in an interval
with the below possible options in the drop down menu

January 21, 2019 32/47

jBLoader V2 – User guide

If the scheduler need to be executed during specific days of the week or month, then the option will
be available as like below

At the scheduler level it is possible to select the source connector and the target connector from the
drop down since multiple connectors can be available and is easier to switch over to another at any
time at scheduler level.

January 21, 2019 33/47

jBLoader V2 – User guide

The scheduler can be disabled/enabled with the option ‘Task Activation’

Extraction properties :

The next step in scheduler configuration is the extraction properties tab.

We can define a scheduler whether the table need to be extracted as Incrementally or a full extract
of a table, which is available in the Advanced option.

For incremental type - the options available are Today, Last Working day and Jbl Table

Today / Last Working day – Extract data for current/previous day accordingly, and its applicable for
stmt.entry,categ.entry & re.consol.spec.entry tables

Jbl table – Extract data incrementally based on the local jbloader table maintained. The extracted
data will be maintained in jbloader table and only the new data will be extracted in subsequent run

There is an option (Data upload mode) to specifiy whether a table in the target database need to be
dropped and recreated during the data upload process or only the data alone need to be truncated

January 21, 2019 34/47

jBLoader V2 – User guide

inorder to maintain the already existing structure or just to load the data without deleting the
records in it which is used for incremental upload.

We can define whether we need to load the extracted data in the target database or just we need
the extracted .csv files without loading it into the target database. When the option ‘Enable
connector’ is set to ‘YES’ the data will be extracted and it will be loaded in to the target database
which is default process used. In case if need to verify the extracted data without loading then this
option should be set to ‘NO’ and the extracted csv files will reside under /FOLDER_TEMP/ in
jBLoader home directory.

Also it is possible to have a backup of the extracted csv files ( both cases - data is loaded or not).
Once the option ‘Backup CSV’ is set to ‘YES’ then the extracted csv files will be copied under the
folder ‘BACKUP_CSV’ available in jBLoader home directory

Once we have the csv files extracted via jBLoader or from any other internal process but in the same
format, then it is possible to load the available .csv files in to target database via jBLoader. We can
enable the CSV upload option and specify the file name & it’s corresponding path of the csv files.

January 21, 2019 35/47

jBLoader V2 – User guide

Event based : The scheduler can even be triggered based on the events instead of time driven. The
possible options are Pre Cob, Post Cob and Cob.

Based on the selected event, the scheduler will wait for the corresponding confirmation file and
once received the extraction will be triggered.

Also it is possible to extract data during COB at any stage

Below options are available and need to be set at T24 batch level based on the requirement

• Halt the batch job at any stage to extract the data via jBLoader and then resume COB once all
the configured scheduler for that particular stage is completed

• The batch job will trigger the extraction via jBLoader at required stage and will continue to
resume the COB, so the extraction will happen in parallel with COB

January 21, 2019 36/47

jBLoader V2 – User guide

Once the required batch job is set, update the metadata info in jBLoader (explained in section 2.5.1
Metadata update) which will update the internal database of jBLoader accordingly. Hence the COB
stage in jBLoader will display only the list of batch jobs to which the routines used for above said
process is attached.

Pre-Job Path/Post-Job Path: The scheduler can trigger a script either as a Pre-Job or Post-Job or
both depending on user requirements. To use this option user needs to upload all the script
file(.SQL) to the jBLoader server using any FTP tool (One-time process).

Once the script files are uploaded to the jBLoader server, user can configure the script on the
required scheduler. As provided in the below screenshot user needs to provide the script name
along with the path for the execution.

jBLoader will execute the script and write the log file(if any) to the directory where the script file
resides.

January 21, 2019 37/47

jBLoader V2 – User guide

Sample screen of a scheduler :

January 21, 2019 38/47

jBLoader V2 – User guide

2.6.2.Update Scheduler

In some cases it is necessary to reschedule all the existing schedules. Eg., If there is an unexpected
delay in COB or any technical activities planned over the scheduled time then the extraction process
should be put on hold and should be restarted at specific time. This can be achieved by updating all
the schedulers by specifying the execution time so that the first job scheduled earlier will be
updated with the new date & time specified and all other subsequent jobs will be updated
accordingly by maintaining the same interval between the tasks.

2.7. REPORTS & STATISTICS

Once we have configured and scheduled for extraction, we have an additional feature to have some
basic reports with the extracted data and it is possible to view user log summary & scheduler
statistics. Also logs are maintained at menu level which will be useful for audit purpose. Audit
information is available for all menus that has all information regarding the data created / updated /
deleted for all the columns available in the corresponding menu.

January 21, 2019 39/47

jBLoader V2 – User guide

2.7.1.Reports

There are two type of report available i.e,. Static & Graphical.

➢ Static report - By default, we have four static reports based on scheduler status and log
summary for user activity & scheduler. It is also possible to do a filter for the report by applying
selection criteria with the available fields in the corresponding table used for reports. Also user can
select the Report format like PDF, CSV and HTML.

Below is the sample screenshot for Scheduler log summary report,

January 21, 2019 40/47

jBLoader V2 – User guide

➢ Graphical report – A scheduler trend report is available in graphical view, in which the number
of records loaded, rejected for a particular table can be viewed in a graph for the given range of
dates.

January 21, 2019 41/47

jBLoader V2 – User guide

2.7.2.Logs and Statistics

The Logs and Statistics menu provides the summary for the scheduler and the user activities.

➢ Scheduler Statistics - All detailed logs regarding the scheduler ie, the number of records loaded
for single value & multivalue table, extraction time, source count and the status of the scheduler
are available from this menu

January 21, 2019 42/47

jBLoader V2 – User guide

➢ User log summary - All the user activities are captured and details regarding the same are
available ie., user activity(list,update,etc..) on the respective record at the menu level are available

2.7.3.Audit information

The logs captured at menu level are used for audit purpose. All the activities are logged and the
values updated for all the available columns in the corresponding menu are displayed as an audit
information.

An audit details are available for the list of below menus,

January 21, 2019 43/47

jBLoader V2 – User guide

Below is the sample screenshot for Audit log for Scheduler configuration

January 21, 2019 44/47

jBLoader V2 – User guide

3. TECHNICAL INFORMATIONS

There are few technical details that need to be noted if the extraction happens at the application server
level. i.e., for T24 source database as other than oracle or virual fields(I-DESC & J-DESC) need to be
extracted or special selection criteria to be applied at application server level.

jBLoader relies on T24 Server Side Objects for extraction purposes and uses the T24 SERVICES for
processing. The service that need to be active is ‘JBL.RUN.SERVICE’. ie., SERVICE.CONTROL for this
service to be set to AUTO.

Also make sure you have a valid license in JBLOADER.PARAMETER-SYSTEM record, in the respective
fields LICENSE.CODE & MAINTENANCE.DATE

3.1. STARTING AND STOPPING THE SERVICE

If you have stopped all the services including TSM, before starting the services clear the file
TSA.STATUS by below command.
Jsh -> CLEAR.FILE F.TSA.STATUS

To start the SERVICE, Input the below records in TSA.SERVICE in Globus/T24

Set “SERVICE.CONTROL” field to “AUTO” in JBL.RUN.SERVICE record to run in background.
Set “SERVICE.CONTROL” field to “START” in TSM record.

Then AUTHORISE the records.

On jBase prompt, run the below command to start the service.

Jsh->START.TSM

To stop the SERVICE, input from Globus/T24

TSA.SERVICE I JBL.RUN.SERVICE
TSA.SERVICE I TSM
Then go to field “SERVICE.CONTROL” and input “STOP”. And authorise the record.

January 21, 2019 45/47

jBLoader V2 – User guide

3.2. EXTRACTION PROCESS – MULTIPLE FILES AT A TIME

The service ‘JBL.RUN.SERVICE’ is a standard T24 Service which will trigger the services
JBL.EXTRACTOR.X (where X is the service number) only if there is any request from jBLoader GUI to
initiate the extraction. The maximum number of service that will be triggered by the
JBL.RUN.SERVICE is 6 which needs to be defined in JBLOADER.PARAMETER.
The actual data extraction will be done by the services JBL.EXTRACTOR.X. Once the extraction
completes, the csv files available in out path will be transferred back to GUI for loading.

TSA.SERVICE, SEE

SERVICE........... JBL.RUN.SERVICE
------------------------------------------------------------------------------
1. 1 DESCRIPTION.... JBL.RUN.SERVICE
3. 1 WORK.PROFILE... TSM for TSM
5 USER.............. ANBU02 ANBU
6 SERVICE.CONTROL... AUTO
7 REVIEW.TIME....... 5

TSA.SERVICE, SEE

SERVICE........... JBL.EXTRACTOR.1
------------------------------------------------------------------------------
1. 1 DESCRIPTION.... JBL.EXTRACTOR
3. 1 WORK.PROFILE... JBL.SERVICE for JBLOADER
5 USER.............. ANBU02 ANBU
6 SERVICE.CONTROL... STOP
7 REVIEW.TIME....... 5

The number of agents is been defined in “TSA.WORKLOAD.PROFILE” table as in below screenshot.

TSA.WORKLOAD.PROFILE SEE
WORKLOAD.PROFILE.. JBL.SERVICE
------------------------------------------------------------------------------
1 DESCRIPTION....... for JBLOADER
3. 1 AGENTS.REQUIRED 6
15 CURR.NO........... 2

January 21, 2019 46/47

jBLoader V2 – User guide

Input the SYSTEM record in JBLOADER.PARAMETER file. In the field MAX.SERVICE.NUMBER, enter
the maximum service number to be used ( Maximum 6 ).

3.3. TROUBLESHOOTING

If there is an issue from the T24 side, please take necessary actions to check the service
JBL.EXTRACTOR.X.

The service has two sections for one table.

1. Extraction
2. Cleanup (Including creating zip file if requested)

Please note, if you clear the In path folder where request files are placed (F.ORA.IN) while the
services are running, make sure to stop the service by clearing the JOB.LIST files too; otherwise the
service will run until the end of the assigned file.

January 21, 2019 47/47