Exploring Engines

Objective

After completing this lesson, you will be able to acquire a comprehensive understanding of engine details.

Engines

Interface development flow diagram with con for each stage, the engine icon is highlighted to indicate that we are covering this step.

The Application Engine determines how the received messages should be handled in monitoring and error handling. There are four engines. Watch this video to learn more:

Key Takeaways

  • Application Engine: Manages message handling, restarts, cancellations, and external monitor navigation based on the technology processing data messages.
  • Persistence Engine: Reads and updates data from an interface's persistence layer, preventing simultaneous editing by locking messages.
  • Selection Engine: Determines data display in Monitoring and Error Handling by evaluating data and preparing header data for the interface messages.
  • Logging Engine: Writes the log messages during data message processing which are later displayed in monitoring and error handling.

How to Set Engines for an Interface

Watch this demo to see how, for the example interface developed in this training, we leverage SAP Application Interface Framework's XML runtime and persistence. We need to use the XML engines for seamless interface operations.

SAP Application Interface Framework's XML Persistence and Runtime

For interfaces that use the XML runtime and persistence, the application and persistence engines have to be set to XML. We'll use the runtime and persistence for the interface that we create during the first exercises.

Flow diagram showing an XML runtime and persistency process with functions such as reading, updating, locking messages, and logging changes.

SAP Application Interface Framework provides its own runtime and persistence layer to process XML messages. SAP Application Interface Framework can handle the following functions on its own:

  • Storing the data
  • Inserting/updating message content
  • Locking/unlocking messages during processing

Recipients

Before you start to set up recipients, you should think about who should be responsible for which interface, who needs to be informed in case an error occurs, and who needs to do something to correct the error. For example, users from an FI department are not responsible for interfaces related to HR and, therefore, the FI users should not see any interface belonging to HR in the Interface Monitor.

Flow diagram representing what recipients enable and showing the details on how to assign the recipients to the interface.

Recipients enable the following:

  • Defining for which interfaces the (business) users are responsible
  • Defining which interfaces a user should see in the Interface Monitor
  • Defining the user that has to be assigned to a recipient

Instead of assigning single users, you can assign roles to the recipients. You can assign different interfaces to one recipient. You can also assign a user to multiple recipients.

These are the steps required to set up recipients:

  1. Define the recipient itself. You can do this in SAP Application Interface Framework Customizing Error HandlingNamespaceSpecific FeatureDefine Recipients Give the recipient a meaningful name and description.
  2. You have to assign the recipient to the interfaces that should be monitored with it. You can either assign the recipient to specific interfaces, you can assign the recipient to a complete namespace, or you can assign the recipient as key-field dependent.
  3. If you assign the recipient to the complete namespace, you can monitor all interfaces of the namespace.
  4. If you want to assign the recipient to specific interfaces, you can do this via the Interface-Specific Features in SAP Application Interface Framework Customizing in Error HandlingInterface-Specific FeaturesInterface-Specific FeaturesAssign Recipients without Key Fields
  5. If you want to assign a key-field dependent recipient, you add the recipient name to the recipient assignment table.

With recipients, you can also notify the users in the case of errors. SAP Application Interface Framework uses SAP Alert Management. Therefore, the users can receive emails or see the alerts in their alert inbox. An email is only sent for the first erroneous message of an interface. A new alert is only sent out if the old alert was confirmed or has expired.

How to Create and Use a Recipient

Watch this demo to learn how to create recipients for all interfaces within your namespace, such as the ALL_INTERFACES recipient, which allows you to display messages processed in the Interface Monitor and assigns your user as the receiver for all interfaces.

Log in to track your progress & complete quizzes