Knowledge Base > Automation Engine and Target Systems > SAP > Executing Jobs in Java Stack (JXBP)

Executing Jobs in Java Stack (JXBP)

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 agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host. Subsequently, you can use a Job objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task 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.

Report for Java Statistics

A processed SAP Job object can also contain a reportA report provides more detailed information about a task's execution or a component. (SJJI) which includes information about the Java job. Activate this functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… by checking the relevant checkbox in the area Optional reports in the Job object's SAP tab.

Installation

Creating the external Schedulers in SAP:

  1. Use the WebInterfaceDeprecated Term. to log on to the SAP NetWeaver Administrator.
  2. Select the Job tab.
  3. Click the link "Java Scheduler" -> "External Scheduler".
  4. Insert a new entry in the listShows entities in a grid view of registeredThis is the status of a task that runs within a group and is waiting for its start. external Java Schedulers ("Add").
  5. Complete the fields. Specify "Automation EngineThis component drives an Automation Engine system and consists of different types of server processes." for the name and the description.
  6. Click on Add.

Creating a Connection object in AE:

  1. Log on to system clientA closed environment within an Automation Engine system where you can create and run objects. A client name consists of a 4-digit number that must be indicated when a user logs on to the Automation Engine system. Users and their rights are also defined in clients. A particular Automation Engine object type. 0000.
  2. Create a new Connection object for SAP.
  3. Open the Connection object and select the connection type "Internet" in the Attributes tab.
  4. Switch to the Internet tab and specify the connection data for the SAP Java Scheduler. Indicate the userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management. that was used to add AE as an external Scheduler.
  5. Store and close the Connection object.
  6. Switch to the folderTop level entities such as Environment, Deployment Target, Activity, … are stored in folders. The permissions a user has on an entity depend on the permissions that are set on the folder for the entities. HOST and open the SAP Agent's object.
  7. Select the Connection object in the Agent tab in the field Java Basis.
  8. Store and close the Agent object.
  9. Restart the SAP agent if it is currently running.

Special Cases

In an environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications. 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 statusThis represents the condition of a task (such as active, blocked, generating). "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 statisticsThis is a list of a task's previous runs.. 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 codeThe value that represents the result of tasks and script functions. 403.

Restarts are not possible. The complete job starts in the Java Scheduler because there is no AE JCL.

Return Codes

SAP status Job return code in AE
COMPLETED
HOLD
RUNNING
SCHEDULED
STARTING
UNKNOWN
0
ERROR 501
CANCELED 502

 

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH