T24 Data Warehouse
T24 Data Warehouse

If T24 is your prime data source, then jBloader can be implemented as the key element of your T24 data warehouse solution. As long as source data from banking applications other than T24 can be provided in Comma Seperated Values (CSV), then jBloader has the abilty to merge and incorporate data from these applications with T24 data.

jBloader extracts, parses and loads T24 data to standard Relational Database Management Systems (RDBMS) like Oracle, DB2, POSTGRES, MS SQL Server, MS Access. These environments integrate seamlessly with reporting tools such as Crystal Reports, Business Objects and iReport.

Definition of T24 Data Source and Packages

jBloader can of course load T24 data to your existing T24 data warehouse. It provides sophisticated features for replicating, extracting and filtering T24 data before loading to your chosen repository.

jBloader reads the T24 standard selection file in order to identify T24 source data. It registers all related transactions and fields including data from history ($HIS) and unauthorised ($NAU) files as well as local reference and idescriptor fields declared in the standard selection as the data source. The data source can also be identified in a T24 multi company environment.

T24 data is grouped into packages where the jBloader administrator selects sets of T24 applications and fields from the data source to make up a certain package. An example of a data package might include the T24 customer and account application tables with fields related to EU withholding tax which will become the basis of this regulatory report requirement.Data packages are at the core of jBloader’s application features. The package, identifying the data that will be extracted, is further processed to apply a number of other parameters. These include the jBloader product features covered in the next section.

Data Extraction

jBLoader provides two types of data extraction. Differential extraction allows UPDATE of changed data or INSERT of new information but no historical data will be included. This may be used for data that might have changed. In the CUSTOMER application for example, a customer might have changed his address or a new customer might have been opened, in both cases historical information may not be necessary to produce related reports. The second type is incremental extraction where jBLoader will APPEND all extractions to existing tables in the target database. CATEG.ENTRY for example may be incrementally extracted on a daily basis in order to add movements of the last working day in accounting type reports.

Features

  • Uses any RDBMS for internal application data -  jBLoader stores all its internal application data; user information, email alerts, extraction package and scheduling information in any RDBMS such as Oracle, PostgreSQL, DB2, SQL Server or MySQL.
  • One click database connectivity test - Whether for its internal, extraction source or target database connectors, the jBLoader administrator can immediately test the connection by clicking on a convenient “Test connection” button.
  • Two possible connection routes to T24 data -  jBLoader can connect to T24 data through shared folders or FTP/S.
  • Email alerts - jBLoader provides an email alert function where messages can be automatically sent on 4 event triggers; start, warning, failed and complete.
  • Secure user management - jBLoader provides the ability to set administrator and end user account profiles. End users can be set to have access to specific T24 companies and data extraction packages. This improves security around sensitive data by limiting which users have access to which data.
  • Multiple target database connectors - jBLoader provides the ability to configure several target RDBMS connectors. This is useful where certain data packages extracted from T24 might be destined to one RDBMS while a particular data package might be destined to another RDBMS.
  • Access to all T24 data types - jBLoader provides access to all T24 application tables and data types available in the standard selection. This includes idescriptor, local reference and multi-value fields.
  • Advanced selection criteria - jBLoader provides the ability to select data from all or a specific T24 company. It is possible to include or exclude history ($HIS) or not authorized ($NAU) files. At the field level jBLoader provides a T24 selection criteria syntax type generator using logical (AND/OR) and comparison (LIKE, UNLIKE, GT, GE, LT, LE, EQ and NE) operators.
  • Advanced scheduling options - From immediate, to the minute or annual intervals between extraction tasks, jBLoader provides the ability to specify a broad variety of scheduling options.
  • Advanced extraction options - jBLoader provides incremental and differential extraction options. There is also a truncate function to ensure data in fields extracted from T24 respect field lengths in target databases. Both data star and denormalized model formats are delivered; one table containing all the normal values and another containing all the multi-values for a particular extraction package.
  • CSV support - jBLoader provides features generate CSV files and also to retrieve data from CSV files.
  • Minimal impact on T24 resources - jBLoader extracts data at high speed with minimal impact on T24 server performance. It fits within a workflow management solution like DTS from MS SQL Server™ or Datastage™.