The OFS Bulk Loader soluton easily allows generate and post bulk OFS messages into Temenos Transact™/T24™, hereinafter Transact. All OFS settings and details are defined in XLSX file of specific format. Once XLSX file is defined OFS messages can be posted to Transact by running one and only command in the command prompt.
Make OFS and other settings:
Prepare the data:
Run the command: java -jar ./OfsBulkLoader.jar ./source/test.xlsx
- Compliant with Transact OFS module
- Ready for use
- Easy to install
- Easy to maintain.
It can be effectively used for Transact data migration projects and for massive postings to Transact by means of OFS.
Please leave your comments, bug reports and cooperation proposals on alexsave@gmail.com.
You can also follow the author on https://www.linkedin.com/in/alexander-savelyev-b8875111/
I'd like to gratitude everybody who made the input into my project! Special thanks to:
- Peter Vengher (https://www.linkedin.com/in/peter-vengher-41b07a10/), for his ideas and support in testing.
- Rafiq Qarakishiyev (https://www.linkedin.com/in/rafiq-qarakishiyev-337a98110/), for support in testing.
- My son Aleksei Savelyev (https://www.linkedin.com/in/aleksei-savelyev-941165192/), for technical support.
The solution has one jar file OfsBulkLoader.jar which has to be run from the command prompt by the user. The jar file has been compiled on Java version 1.8.0_301. The solution has been tested on following environments:
- Transact R21, Windows 10, H2 database
- Transact R23, openSUSE Leap 15.5, MSSQL database
- Transact R23, openSUSE Leap 15.5, PostgreSQL database in JSON mode
The solution is compatible with Temenos Transact TAFJ environments on H2, MSSQL and PostgreSQL databases.
Prerequisite. Both Transact TSA.SERVICE's TSM and OFS.MESSAGE.SERVICE in any company have to be up and running to allow OFS messages to be posted into Transact.
Create the file F.OFS.BULK.LOADER.IDS by following command in DBTools in JQL mode:
CREATE-FILE F.OFS.BULK.LOADER.IDS 3 4
Find the required release here: https://github.com/alexsave-dev/OfsBulkLoader/releases. The current Readme file stands for the most up-to-date release. Previous Readme files are put inside relevant release packs. Unzip the file OfsBulkLoader.zip into the directory UD. You should get the picture like this:
Important. The file OfsBulkLoader.properties has to be always placed in the same directory with OfsBulkLoader.jar. The file keeps settings for OfsBulkLoader.jar execution. The current directory is the directory where the OfsBulkLoader.jar is located if you define relative paths for files and directories.
Modify OfsBulkLoader.properties to setup the path to TAFJ directory in TAFJ.HOME:
Open the excel file in the directory OfsBulkLoader/source/test.xlsx. The file is given in GIT as an example. Please feel free to copy and modify it according to your requirements. The spreadsheet "OFS" contains OFS message details (highlighted in green) and other user level settings (highlighted in orange) to control the solution. Mandatory fields are highlighted in red. You'll find explanations and hints in comments to fields on the spreadsheet.
Go to the the spreadsheet "DATA" to prepare ID values as well as field values to be posted as a part of OFS messages.
After you are done with xlsx, go to the command prompt in the directory OfsBulkLoader and run the following command to process the specific xlsx file (the name of the xlsx file should be provided as a parameter): java -jar ./OfsBulkLoader.jar ./source/your_file_name.xlsx.
After the execution is over you can check the directory OfsBulkLoader/log for a log file.
The OFS file will be in the directory OfsBulkLoader/ofs.
Important note: You don't need to change settings if you followed all instructions above and you are happy with existing structure of folders and other settings. If you decide to allocate the pack in another location then please change relevant paths.
The file OfsBulkLoader.properties has to be always placed in the same directory with OfsBulkLoader.jar. The file keeps settings for OfsBulkLoader.jar execution. The current directory is the directory where the OfsBulkLoader.jar is located if you define relative paths for files and directories.
| Setting | Default Value | Description |
|---|---|---|
| OFS.FILE.NAME | ./ofs/ofs | The name of the ofs file |
| LOG.FILE.NAME | ./log/log | The name of the log file |
| OFS.ARCHIVE.DIR | ./ofs/archive | The path to the archive directory for ofs files |
| LOG.ARCHIVE.DIR | ./log/archive | The path to the archive directory for log files |
| TAFJ.HOME | ../../TAFJ | The path to TAFJ directory. Important: please change it to the location of TAFJ folder on your server before first run |
| CHECK.AGENT.SECONDS.DEFAULT | 10 | The interval in seconds to check the number of OFS messages to be posted into Transact. It can be overriden by user interval defined in the spreadsheet. |
| DEBUG | FALSE | Please set the parameter to TRUE in case if extra details have to be provided for technical support |
| JDBC.URL.OVERRIDE | By default JDBC Url is taken from the relevant properties file in TAFJ/conf directory. If this setting is assigned then it overrides the default JDBC Url value. Usually this value is changed if additional connections options have to be given together with JDBC Url from TAFJ properties | |
| FM.DELIMITER | \uF8FE | Please keep this value unchanged unless you get other instructions from technical support |