After creating the necessary datastores and flat file formats for your project, you can begin building jobs.
A project is a single-use object used to group related jobs. It represents the highest organizational level in SAP Data Services. When you open a project, the associated group of jobs becomes accessible in the user interface. Projects are stored in the Local Object Library, and only one project can be active at a time.
Projects serve organizational purposes, such as grouping jobs with interdependent schedules or jobs that require collective monitoring.
A job is the only executable object in Data Services. During development, you can manually execute and test jobs directly. In a production environment, you can schedule batch jobs or configure real-time jobs as services that process incoming message requests.
Job Execution
- Jobs are schedulable objects.
- When executed in SAP Data Services Designer, a job runs immediately.
- You can schedule execution using the Data Services Management Console or a third-party scheduler.
- All steps within a job are executed as a single unit.
A job consists of multiple steps. Each step is represented by an object icon in the workspace. By connecting two or more objects, you create a job diagram that defines the execution logic.
Process Orchestration
Connecting objects determines the sequence of operations. A subsequent step only starts if the previous step completes successfully. For example, a data flow will only execute if the preceding script finishes without errors.
To run objects in parallel, place them in the workspace without connecting them.
For complex logic, organize content into individual workflows and create a single job to call these workflows.
Objects within a workflow behave the same as those in a job:
- Connected objects execute sequentially upon success.
- Unconnected objects execute in parallel.
Hint
Summary
In this lesson, you learned about SAP Data Services jobs.
- Jobs are the only executable objects, running immediately in Designer or scheduled via Management Console or third-party schedulers.
- Job steps execute sequentially when connected, with subsequent steps starting only after successful completion of previous steps.
- Parallel execution occurs when objects are unconnected, allowing multiple operations to run simultaneously within a job.
- Workflows organize complex logic into reusable components, with objects behaving identically to those in jobs regarding sequential and parallel execution.