Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
pallab_haldar
Active Participant
0 Kudos
3,037

In This blog, I will discuss the steps to schedule a job using the Data Services Management Console.

A. Steps are given below for batch Job scheduling -

1.  Log In to the Data Services Management Console.

pallab_haldar_0-1707067762958.png

2.  Now we need to 'Administrator' and expand the 'Batch' menu –

      

pallab_haldar_1-1707067762965.png

3. Select the repository where the job you want to schedule has been developed.

pallab_haldar_2-1707067762971.png

 

4. Please Go to the 'Batch job Configuration' Tab. Select the project of your job. Click on the right hand side 'Schedules' which is under the other information column of the job for which we want to create a schedule –

pallab_haldar_3-1707067762981.png

5. Then click on the 'Add' button. Give a name for your schedule. We need to select Date-Day for our schedule. There is an option of 'recurring' if want to schedule the job in recurring. In our case, we will schedule it once a day at 11.23 PM. Need to click on the 'apply' button and a schedule for your job is created.

pallab_haldar_4-1707067762992.png

7. If we want to check, activate, and deactivate the created job then go to the 'Repository Schedules' tab and there we can see the scheduled job.

 

pallab_haldar_5-1707067762997.png

B. Real-Time job scheduling:

 Real-time jobs do not need to wait for an internal trigger or a scheduling like a batch job. It is waiting for a message from the access server, once it is it starts automatically.          

Realtime Jobs are suitable for XML Messages. The basic architecture is like below –

pallab_haldar_6-1707067762999.png

Before we need to start development, we need to configure the access server.             

pallab_haldar_7-1707067762999.png

Real-time jobs start with a message and end with a message.  The input message must be the first step in the job and the end message the last one. After the real-time job is published, DS checks the job inside for tables, syntax, and all objects and if everything is OK, the job starts and can accept requests.

Hope it will help. In the next blog I will discuss about the different fine tuning techniques/performance tuning techniques in SAP data services. 

Labels in this area