| Oracle® Retail Integration Bus Oracle® Universal Service Mapper User Guide Release 19.0 F25772-01 |
|
 Previous |
 Next |
| Oracle® Retail Integration Bus Oracle® Universal Service Mapper User Guide Release 19.0 F25772-01 |
|
Previous |
Next |
Universal Service Mapper has 3 major components:
Event Listener [Abstract Service Mapper, Service Def JSON]
Service Mapper Orchestration [Orchestrator, Template and DVM]
External Service Invocation and Service Provider
The event listener is a service hosted by the USM application which is open to receiving data from any application that is connected to it. The application here is either RIB-LGF or WMS Cloud. The applications have the following URL pattern set in their target for USM.
http://<host>:<port>
When application sends data, the event listener internally calls the abstract service mapper which determines family, message type and the operation(s) from the message received by referring to the Service Def JSON file.
The abstract service mapper now calls the service mapper orchestrator, which decides what data populates the mapper templates. The orchestrator does the field-by-field mapping from the source application to the destination application. Certain key-value pairs in the DVM maintain context between the applications.
The Service Mapper Orchestrator calls the services hosted by the service providers after the mapping operations are completed. The service providers here are either RIB-LGF or WMS Cloud, which consume these services through USM. The calls are REST calls. USM holds the information necessary for it to call these services in a file with the prefix external_env_json for the respective application. These are stored as key-value pairs in a JSON file.
