Overview
The buying organization may choose to integrate to the standard Unimarket webservices or use the Unimarket Connector middleware to handle data transformation to or from a customer external system such as FMIS, ERP, Reporting systems, Asset Management etc. The Connector minimizes the need for custom integration as it is built specifically to send and receive messages from Unimarket and transform them into a format compatible with client-side systems. Unimarket installs the Connector on a Java Runtime Environment (JRE) behind the customer firewall to receive XML messages from the Unimarket application. The Connector can then input/output data (or a flat file) in a format that is compatible with the customer FMIS/ERP system. The data or flat file is typically input/output to or from a staging table or to a specified directory location.
- Examples of Transactional messages are Orders, Receipts and Invoices.
- Examples of Master Data are Approvals, User Details and Accounting (GL) information.
- Examples of Validation / Callback are Budget Checking, Approvals and User Validation / Authentication.
| Note: The above diagram does not illustrate all the available integration points. |
Technical Documentation
For documentation on the setup and technical requirements for the UCP see Connector Setup & Technical Requirements.