SAP Desktop Agent: Installation and Setup Guide

This article provides a comprehensive guide to installing and setting up SAP Desktop Agent 3 for SAP Build Process Automation. The guide includes step-by-step instructions for accessing the RBSC Portal, adding new users, and installing the Desktop Agent. It also covers troubleshooting and error resolution, and highlights the importance of installing the Desktop Agent as a service for unattended mode in production or quality VMs. The guide includes relevant images to support the steps and encourages users to share any additional error scenarios they encounter.

SAP Desktop Agent 3 is a crucial component of SAP Build Process Automation, enabling the execution of automation projects on user desktops. This article provides a detailed guide to installing and setting up the SAP Desktop Agent 3, including troubleshooting common errors and best practices for unattended mode in production or quality VMs.

Accessing the RBSC Portal and Adding New Users

To begin, users need access to a SAP BTP tenant with SAP Build Process Automation. The Desktop Agent 3 can be installed locally on user desktops. The installation process starts by accessing the RBSC Portal, where users need to log in with S-user credentials. After logging in, users can add new users and assign the ProcessAutomationAdmin role, which is essential for adding users to the system [1].

Installing the Desktop Agent

Once the user is added, the installation of the Desktop Agent can commence. Users should download the Desktop Agent from the SAP Development Tools page and install it with administrator rights, especially if running automation in unattended mode in production or quality VMs [1].

Troubleshooting Common Errors

Several errors can occur during the installation and registration of the Desktop Agent with the tenant. One common error is "Registration failed because we couldn't get the access token from the tenant." This error can be resolved by adding `"websocketChoice": "wsProxy"` in the configuration file for Desktop Agent versions 3.19.56 or higher [1].

Another error is the "Health check is Not Successful Error." This error requires referring to the relevant SAP Note for a solution. Users should reach out to their VM infrastructure team to implement the necessary changes in the VM [1].

Maintaining Active User Sessions

In some cases, the Desktop Agent may get disconnected after a user session is logged out. This behavior can be modified by configuring Group Policy settings to ensure the user session remains active even after disconnecting from the VM [1]. This is crucial as the SAP Desktop Agent relies on an active user session to continue functioning.

Alerts and Precautionary Measures

To ensure quick resolution of disconnections, users can configure an Alert Handler in the SAP Build Process Automation Lobby. This setup allows for email notifications to be sent within 5 minutes of a disconnection, enabling prompt manual checks and resolution [1].

Conclusion

Installing and setting up the SAP Desktop Agent 3 for SAP Build Process Automation involves a series of steps that include accessing the RBSC Portal, adding new users, and installing the Desktop Agent. Troubleshooting common errors and maintaining active user sessions are essential for smooth operation, especially in production or quality VMs. By following the outlined guide and best practices, users can ensure the efficient and reliable execution of automation projects.

References

[1] https://community.sap.com/t5/technology-blog-posts-by-members/complete-guide-to-sap-desktop-agent-installation-errors-and-resolutions/ba-p/14157455