Challenge Overview
The Trading Partner Registry and Repository (TPRR) is an existing GUI sub-application within a larger custom IBM J2EE 5.0 web application called ARMS (Administrative Reporting and Measurement System). The primary responsibilities of the TPRR are to enable the creation and management of trading partner profiles and business process subscriptions. The data defined within the TPRR is used by an Enterprise Service Bus (ESB) to look-up trading partner profile data, subscription data, routing data, and data needed to support data mapping and data enrichment. The TPRR is also used to manage ESB process scheduling.
Trading partner profile data is stored in an IBM DB2 V9.7 database.
The TPRR sub-application has already been implemented, using a pre-existing custom application framework and patterns from the parent ARMS application. The primary persistence technologies currently used by the TPRR sub-application (and parent ARMS application) are:
- Spring 2.5.6 (Bean Configuration, Hibernate Integration)
- Hibernate 3.2 (for database persistence and object /relational mapping; database transaction management)
IBM’s Open Source Policy prefers the use of Apache openJPA over Hibernate, and encourages that Hibernate applications be migrated to JPA when possible.
It has been determined that the easiest way to start to perform the Hibernate to JPA migration for the TPRR sub-application is to entirely redesign the DAO entity components for JPA.
This component design event is to design a ScheduleDAO component that handles persistence-related operations for theTPRR’s SHEDULE database entity, using JPA 1.0 (implemented using Apache openJPA 1.2.x). Currently, the SCHEDULE entity supports an ESB process that requests a product Catalog from a back-end ERP system, and then distributes the received Catalog response from the back-end ERP system to a Gateway system, which then forwards the Catalog to an external Trading Partner. There are two types of Catalog requests: full (entire) and delta (incremental).
Appendices A - C contain a diagram of the physical SCHEDULE table entity, a data dictionary, and the table’s DDL.
Final Submission Guidelines
N/A