on 09-03-2013 3:27 AM
what is the difference between b/w Batch Job and Real Time job in DS???
And how to create a real time job and configure with Access Server???
Hi Sabat
The main difference between batch jobs and real-time jobs is that a real-time job (when configured as a real-time service) is running constantly. It waits for input messages, executes, and returns a result - which can contain many elements. An example might be a validation engine, it would accept many (potentially parallel) input messages and reply (hopefully) in a very short time. It can support a high level of throughput (if designed correctly).
When batch jobs are executed, they start processes to perform transformation and cannot return a complex reply back to the initiator.
Calling both types via the web service are valid and realistic scenarios, a real-time job would be used for fast processing of small input messages and consumable replies, a batch job could be triggered by an enterprise scheduler once a week to export a large volume of data to a 3rd party.
The following white paper gives how to construct a real-time job,
Hope the above information Answers the query...
Regards
Srinivas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
If you are going to cut and paste my posts, please put a reference to the original post next time - https://scn.sap.com/thread/2149180
Michael
Hi Sabat,
Real Time job vs Batch job:
The main difference between batch jobs and real-time jobs is that a real-time job (when configured as a real-time service) is running constantly. It waits for input messages, executes, and returns a result - which can contain many elements. An example might be a validation engine, it would accept many (potentially parallel) input messages and reply (hopefully) in a very short time. It can support a high level of throughput (if designed correctly).
When batch jobs are executed, they start processes to perform transformation and cannot return a complex reply back to the initiator.
Calling both types via the web service are valid and realistic scenarios, a real-time job would be used for fast processing of small input messages and consumable replies, a batch job could be triggered by an enterprise scheduler once a week to export a large volume of data to a 3rd party.
and regarding building real-time jobs please refer below documents.
Building Data Integrator Real-time Jobs and Calling Web Services:This white paper shows how to construct a real-time job, expose it via a web service, and invoke a web service using Data Integrator (DI). It follows on from a previous white paper – Manipulating XML using Data Integrator.
Links:
http://scn.sap.com/docs/DOC-19789
Or also refer below links
Real Time Jobs in Data Services:
http://www.dwbiconcepts.com/etl/23-etl-bods/178-real-time-jobs-in-data-services.html
Thanks,
Daya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello
If you are going to cut and paste my posts, please put a reference to the original post next time - https://scn.sap.com/thread/2149180
Michael
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.