You will need to have the following redirection enabled on the F5 side:
https://evolve.domain -> https://evolve.domain/en
http://evolve.domain
-> https://evolve.domain/en
Note: We recommend that you do notbrowse the http URL.
Evolve/Studio Manager Cloud configurations
Below will be our recommendation for Automate Evolve Server & Automate Evolve Worker VMs/Cloud database (Azure SQL Managed Instance/AWS RDS) configurations:
- Automate Evolve Server VM and Automate Evolve worker VM should be in the same data center as of Azure SQL ManagedInstance or AWS RDS. Both VMs and database instance should be as close as possible.
- Network latency among Evolve/Worker Server VMs and Cloud database instances should be minimal.
Skip SAPUI Check
Launch GUI issue 'sapgui start failed' troubleshooting steps:
Reason of “sapgui start failed” The following sequence diagram shows how an SAP GUI connection is opened from Automate Client.
Possible Reason 2
As of SAP GUI 7.20, 7.30 and 7.40, there is a security check before starting the SAP GUI. If you click on 'Deny' or if in the SAP GUI security settings, the option is set to 'Deny', you will get the same dump.
Whenthe sapgui.exe delegates, it always starts SAP Logon, no matter whether SAP Logon Pad is already running or not.
When the service worker logon account is SAP user and that user has enabled setting->“Activate guixt” , it always starts SAP Logon, no matter whether SAP Logon Pad is already running or not.
Possible Reason 3
RFC connection fails in NAT environment.
Possible Reason 4
No SAP GUI resources available any more on frontend PC.
Lot of parallel threads in ECTR can call SAPGui transactions example, when opening the structure tab of a document.
[15:06:55.113] FJ-08 Calling: /DSCSAG/DOC_GET_LATEST_STR4.[apilog @ stateless.txt#115] (using SAPGui)... [15:06:55.113] FJ-03 Calling: /DSCSAG/DOC_GET_LATEST_STR4.[apilog @ stateless.txt#114] (using SAPGui)... [15:06:55.113] FJ-05 Calling: /DSCSAG/FOL3_CLASS_READ.[apilog @ stateless.txt#113] (using SAPGui)... [15:06:55.113] FJ-02 Calling: /DSCSAG/DOC_WHEREUSED_ALLVERS2.[apilog @ stateless.txt#112] (using SAPGui)... [15:06:55.113] FJ-04 Calling: /DSCSAG/OBJ_GET_MULTIDETAIL2.[apilog @ stateless.txt#1
Possible reason 5
The "Log On" user of "Service Worker" should not be SAP user as recommended. In case, if "Log On" user is SAP user then "Activate GuiXT" must be unchecked for that user. The user should logon on SAP GUI on service worker machine and uncheck "Settings->Activate GuiXT" option.
Steps to Download SAP NW RFC SDK files in case files are not present in System32
Refer the Support portal article link for the steps when the dlls are not present in c:\windows\system32\ path.
Steps to Download SAP NW RFC SDK files
Note: To connect Automate Evolve, Studio Manager (Server and Worker) and Studio with SAP, customers need SAP NetWeaver RFC Library. If the library will not be already present on the system, then user will get an error when these products try to make a connection to SAP. This library can be downloaded from SAP market place, following the steps here Steps to Download SAP NW RFC SDK files to get this library and place it at the required location. (Applicable from 20.2.9 onwards)