Knowledge Base > Automation Engine and Target Systems > SAP > Checking Errors

Checking Errors

This document contains information that will support you in recognizing the source of errors which  cause the 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 to functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… improperly or individual tasks to be executed incorrectly.

Job Report

The first source to be checked is the activation log of the AE jobAn Automation Engine object type for a process that runs on a target system. for SAP. It provides information about the actions the agent has taken in connection with the SAP system and how the particular actions ended.

Attributes of Executable Objects

Sometimes the error cause is easily found in the attributes of an executable objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task (such as a wrong 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. or 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.). Check the attributes of the particular object.

CPIC User

An SAP user (client, name or passport) must be defined in a Login object to be able to establish a connection to the SAP System. This user must also be available with the same passwordA secret combination of characters for a Automation Engine user. in all an SAP system's clients in which tasks are executed. Check the Login object and the users in the SAP system.

Within the SAP system, the agent is represented by the CPIC user. This user requires the appropriate rights such as operator rights for background processing, for example. Check the rights of the SAP system's CPIC user.

Helpful Transactions

Through job logs and spool lists, the transaction "SM37" provides information about job executions. The XMI log which can be called using "RZ15" also supplies helpful records.

Log Files

Agent and Server log files provide exact information about the relevant point in time when the error occurred. These files' contents are also provided in the System Overview. The initial section shows the complete INI file including the parameters which have been specified for the agent and server. This section is followed by a chronological listShows entities in a grid view of all executed actions.

SAP's System Log

Error situations occurring in the SAP system are logged in SAP's system log. Use the SAP transaction "SM21" to view the system log. In particular cases (such as when the agent fails to schedule a job step), the SAP system log is automatically copied to an own tab in the AE report.

Traces

Traces provide even more detailed information than log files. They contain all messages which were sent from and to agent and server or agent and SAP system (RFC trace). Traces can be activated in the agent's INI file or the System OverviewThe UserInterface window that contains information about the Automation Engine system.. Trace contents are stored in files in the agent's working directory or an individually defined directory.

Traces are required for the support or development team's analysis process. Always include this information in your support message.

An activated RFC trace create files on agent side but also on SAP's applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity. server computer. Automic recommends activating traces only for a short period of time in order to reduce the hard disk's memory consumption. Set gw/accept_remote_trace_level to 0 if no trace files should be created in the SAP system.

Further information about RFC trace is available in the SAP note number 532918.

 

 


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

Copyright © 2016 Automic Software GmbH