AE provides the following opportunities for the handling of jobs in the SAP Java Scheduler:
First, the Java job definition must be deployed in the Java Schedule to make it visible to the SAP agent. Subsequently, you can use a Job object to create an instance from an existing job definition.
A SAP Job object always belongs to exactly one Java job definition.
Create a SAP Job object for Java Scheduler jobs and select a SAP agent plus a Login object. Use the Form tab to select the job definitions to be applied. The lower part of the tab automatically displays the corresponding parameters.
The Job log tab contains the following options:
The job log is always deleted together with the job instance.
A processed SAP Job object can also contain a report (SJJI) which includes information about the Java job. Activate this function by checking the relevant checkbox in the area Optional reports in the Job object's SAP tab.
Creating the external Schedulers in SAP:
Creating a Connection object in AE:
In an environment of several nodes, the Java Scheduler jobs are processed on the node on which the Scheduler Service is active. If this node is deactivated or fails, job processing continues on a different node.
The agent periodically attempts to re-establish the connection to the Java Scheduler if it has been lost during job execution. The job remains active in the AE system and obtains the status "Waiting for remote system".
The job aborts if calling the Java Scheduler results in an error. In this case, there is no report about the Java job's statistics. The error is logged in the Job object's report "Agent Log" and in the SAP agent's log file. The job aborts with return code 403.
Restarts are not possible. The complete job starts in the Java Scheduler because there is no AE JCL.
SAP status | Job return code in AE |
---|---|
COMPLETED HOLD RUNNING SCHEDULED STARTING UNKNOWN |
0 |
ERROR | 501 |
CANCELED | 502 |