Why Should You Use a Job Scheduling Service ?
Maybe we start thinking about a Cloud Foundry application. This application, with its different duties (e.g. persisting hierarchy models-, generating reports on a regular basis-, informing send out by signaling if thresholds are passed on the datamodel) has a variety of business processes to service. A certain degree of these processes might be routines that have to be executed either synchronously or asynchronously on a regular basis. Wouldn't it be good to have these results without the necessity to execute the actions that create them ? At this point the great SAP Business Technology Platform Job Scheduling Service comes into play.
Some words and explanations of the terms we are using in Job Scheduling Service try to clear up things and make it easier to get speed up when you start working with the documentation:
- Job Scheduling Service
This service has to be created as an instance as the basis for your jobs. You can select this Cloud Service from the Service Marketplace within your BTP Trial account.
A job is a logical structure that manages one ore more schedules and finally executes the defined action endpoints. It is implemented as an URL. Jobs run according to a schedule synchronously or asynchronously. Jobs can also be configured with a Cloud Foundry task.
An action is the atom of work what it is all about. An action works on your data so as to execute processes according to its schedule assigned to jobs.
The Job Scheduling Service Dashboard lets you define jobs and the assigned actions belonging to them. Moreover it allows to create schedules and execute other administrative work.
- REST endpoint
The REST endpoint of your SAP BTP application is used by your Job Scheduling Service invoking HTTPS Calls.
An Instance of Job Scheduling Service and additionally XSUAA Service has to be created. The binding with the App(s) has to follow the correct sequence. First you are to bind XSUAA Service.
The XSUAA Service brings security aspects into the Job Scheduling Service. XSUAA means Authorization and Trust Management. The correct privileges have to be in place to set up the Job Scheduling Service.
- Service Plan
A service plan is a particular type of service. Next to lite, there are plans like: Standard, Default, Securestore, hdi-shared, lite, space, application, s3-standard and apiaccess. Service is deprecated.
The service plan lite guarantees basic authentication (username and password) for REST API calls.
What are the prerequisites for using the Job Scheduling Service ?
Having talked about the terminology we can approach now the practical integration of the SAP Job Scheduling Service.
Let us point out the prerequisites in detail. You can take it as a kind of checklist.
- BTP Account
BTP access, global account- and subaccount has to be set up appropriately.
For this kind of Service the Global Account Administrator role is necessary.
The contract with SAP has to allow the usage of this service.
The location of the Job Scheduling Service with all applications is the level Space.
- Space Role
For binding the service instance to your applications you need to have the Space Developer or alternatively-the Space Manager Role.
The SAP Job Scheduling Service does not take care of applications. This has to be set up before it is possible to use this service.
Accordingly to applications also its endpoints have to be configured and tested positively before using the Scheduling Service.
It is compulsory to have Applications and the Job Scheduling Service Instance in the same space.