Difference between revisions of "Information Systems:com.unipharm.uwd (Java integrations project)"
Jump to navigation
Jump to search
m |
|||
| Line 16: | Line 16: | ||
===Concerns to address=== |
===Concerns to address=== |
||
| − | * How to instruct a non-developer or general outsider to run these programs manually, especially considering the huge classpath (which makes infeasible |
+ | * How to instruct a non-developer or general outsider to run these programs manually, especially considering the huge classpath (which makes infeasible typing them all out <code>java -c</code>). |
* Best practice with package-splitting. |
* Best practice with package-splitting. |
||
* How to manage growing project dependencies (both Maven libs and jars from the Integrator environment). |
* How to manage growing project dependencies (both Maven libs and jars from the Integrator environment). |
||
Revision as of 12:26, 27 May 2021
Note: In hindsight, the name of this package kind of sucks. Plan to rename when -norwizzle (talk)
uwd is the name of a Java pilot project that currently houses various integrations (utility scripts, business reports etc.). The root package is com.unipharm. The source code for Integrator programs currently reside here.
Packages
This is better documented in the javadocs, but they are summarized here nonetheless:
- com.unipharm.uwd.integrations.bizreports - Periodic reports e.g. sales reports, activity reports (HC MAR).
- com.unipharm.uwd.integrations.carriers - Carrier Interface batch programs e.g. data import, freight-to-sales updater etc.
- com.unipharm.uwd.integrations.healthcanada - Maintenance programs for the Health Canada reference DB (DPD and LHNPD)
- com.unipharm.uwd.ittools - Tools for IT e.g. DMARC processor, QBATCH watchdog
- com.unipharm.uwd.utils - Utility classes and other helpers
Javadoc
The javadoc site for this package will be hosted on owl.
Concerns to address
- How to instruct a non-developer or general outsider to run these programs manually, especially considering the huge classpath (which makes infeasible typing them all out
java -c). - Best practice with package-splitting.
- How to manage growing project dependencies (both Maven libs and jars from the Integrator environment).