The Electronic Journal (EJ) is used to record the transaction information. You can add the EJ records with EJ APIs during transaction. And the EJ record will be stored in the repository which can be considered as database. The EJ provides JDBC DAO (database access object) to access the database as the left part of the above figure shows. If you choose database as the ultimate storage for EJ records, all the transactions will share the same EJ table, which means the record of transfer and deposit will be in the same table in the database.

The EJ can be configured through UNICOM^® Digital Transformation Toolkit (UDTT™) Element Factory like other components in UDTT. As demonstrated in the above figure, you can configure EJ Implementation, UserDefinedFields and JDBC DAO. As for UserDefinedFields, you can decide the table structure, except five fixed fields, three of them are the table keys and other two are for recurrence. Moreover EJ provides some customization that the you can implement your own handling logic.

The Electronic Journal provides a convenient tool to retrieve the EJ record. You can use the Electronic Journal Viewer (EJV) to query EJ records and present the results through GUI, and it also supports recurrence of transaction by EJ record. On the EJV GUI, you can input the query conditions, then get the query results and trigger the recurrence of the transaction GUI.

Like EJ, EJV can also be configured with UDTT Element Factory. So you can decide the query condition, and which part of the result is displayed on the GUI, and whether it needs recurrence.

The following figure is the overview of Electronic Journal and Electronic Journal Viewer.