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 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 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)
The TPRR application stores Partners and their capability information into a database named, TPRRDB (TPRR.ddl). This Database contains various partner related and Configuration tables. TPRR application will be used to populate the values into these tables.
This component design event is to create a TPRRPurge java application that runs periodically and purges records according to the specified parameter. Upon start up TPPPPurge will look up TPRRPurge.properties file which will contain database connection and schedule related information. Once the job starts, the application will go through TPRRDB. PURGE_CONFIG table and execute active jobs
Final Submission Guidelines
N/A