Once a real-time service is configured ans started it is waiting for XML messages from the Access Server. External clients invoke the real-time service by creating an XML request and passing it to the Access Server, this is done using the functions in the Message Client API, see the Integrator's Guide for full details.
Publishing the real-time service via the Web Service also makes the service invokable via SOAP.
Thanks for the reply. I went through some of the integrators guide and some of the code samples and it is starting to make more sense to me now.
Does SAP also use the same types of calls for the real time jobs or are they done via an RFC connection? My company has implemented SAP BAS and I'm trying to figure out how the connection works between BAS and DQM, so far I believe it is calling one of these jobs
These look like jobs provided to us by DQM, is there any way I can determine which one BAS is calling?
The Jobs you describe here for DQM are called by the DQM for SAP RFC server that you run as a separate installer that is downloaded from the SAP Service Marketplace when you purchase that product. This RFC server is not setup in the management console (as the traditional DS rfc server does) but runs as a windows service (if you are on windows). This RFC server makes the calls to those jobs and to understand what jobs get called through the DQM for SAP BAdI's that are installed on the SAP CRM or ECC system (that is a separate install that is downloaded as well for the DQM for SAP product and applied to the CRM or ECC system, these jobs are all listed in the DQM for SAP RFC Servers config file - flrfcsrv.xml. This file can be found in the DQM for SAP RFC server install area on the file system under the config folder.
The DQM for SAP Data Services jobs need to be setup as real-time services as described in the DQM for SAP User's guide and then added to the WSDL as a webservices. This way they are exposed to the webservice and then able to be called by the RFC server.
Hope this helps.
I have a quick follow up question for you.
I've been reviewing the the jobs:
and I see that they are providing many fields as output, including the county name. However, in SAP our county/district field is not being populated. Do you know if there are any additional configurations necessary in the BADI or DQM to have the county populate?