- SAP Managed Tags:
Since the partnership between Tricentis and SAP has been announced in 2019 the topic of the integration between Tosca and SAP Solution Manager 7.2 has become more and more important. Tosca is a tool for automating test scripts, created by Tricentis, the world's leading provider of continuous testing platforms.
As ALM Consultants we saw the need to integrate the SAP Solution Manager 7.2 (SolMan) with Tricentis Tosca to build the base for the future Test Automation Capabilities with regards to new technologies such as SAP Concur, SAP Ariba and SAP SuccessFactors for example. My colleague aman91 and me invested some time to get into Tricentis and the integration with SolMan 7.2 and are happy to share our two contiguous blog articles guiding you through all the steps you need to get started with Tricentis Tosca and Solution Manager. This article focuses on the integration of Tricentis Tosca and SAP Solution Manager 7.2 followed by an article by aman91 where we discuss the creation and benefits of the integration by showing how Tricentis test cases can be created and executed after a successful integration.
Before we get into the technical integration let's have a look on the supported UI's and the different offerings dependent on the customers’ level of support. First, we have to differentiate between Tricentis Test Automation (TTA) and SAP Enterprise Continuous Testing by Tricentis (ECT). The TTA version supports all SAP UI's for on-premise (on prem) and cloud and is part of the SAP Enterprise Support. In comparison to that, the ECT version supports, in addition to the UI's that are already supported in TTA, 160+ UI technologies, mobile apps and many more as you can see in the following figure:
As mentioned in this blog post, we focus on the integration of Tricentis Tosca with SAP Solution Manager 7.2.
In a nutshell the process of the integration can be divided into 5 steps:
All the steps for the integration (for the current Tosca version 14.3 STS) can be reviewed in more detail in the official manual of Tricentis. We recommend that you always check the official manual if you are facing any errors in certain areas or whether there are any updates on this rapidly evolving topic.
In this step we first have to download and install the SAP .NET Connector 3.0 (for 32-bit and 64-bit system types) from the SAP Service Marketplace.
After the successful download and installation, we need to copy the sapnco.dll and sapnco_utils.dll file from the installation directory of SAP .NET Connector 3.0. The 32-bit version has to be copied to the %COMMANDER_HOME%\x86 directory and the 64-bit version to the %COMMANDER_HOME%\x64 directory. As a result of it there should be two dll-files in both directories.
To complete step 1 of the integration we have to create a multi-user workspace in Tosca. This is required to check in and check out objects from Tosca, so that all SAP Solution Manager users can access and work with them. To do this we have to click on Create new on the start screen of the Tosca Commander.
This will open a pop up where we have to enter the details for our new workspace. First, we have to select a type of repository (Oracle, MS SQL Server, DB2 or SQLite). In our case we selected SQLite:
Here you can enter also more specific details for the workspace, all necessary and further information regarding that can be found in the official manual of Tricentis.
After the successful creation of the workspace step 1 of 5 is completed and we can continue with step 2 of the integration process.
This step has to be done in Tricentis Tosca. First, we have to checkout the project by clicking on the project root element (in the project tab) and select the menu option Checkout Tree. After we have successfully checked-out the project tree we can run the SAP Solution Manager wizard. To do so, right-click on the project root element and select SAP Solution Manager -> Configure SAP Solution Manager Integration on the bottom. This will start the wizard with five steps.
In first part of the wizard both prerequisites should be fulfilled already if you have done everything correctly in step 1 and you just have to click the Next button. Otherwise, you have to go back to step 1 of the integration and check again what is missing.
In part two of the wizard, we have to enter a username and password for the workspace in Tosca. If you are not using a password, you can leave this input field empty and click on Next.
After that we have to enter the connection details to the SAP Solution Manager system. Most of this information can be found in the SAP Logon where you can copy SAP Host, SAP Client and SAP Instance Number. For SAP Username you have to enter your SAP GUI user which you use to login in to the system (not the ECATT-User!). Also, you have the possibility to enter a path where all log files should be stored and then click on Next.
Part 4 of the wizard is optional to secure the communication between Tosca and SAP Solution Manager with a Secure Network Connection (SNC). In our example we kept the settings as in our Development SAP Solution Manager 7.2 and clicked on Next.
In part 5 of the wizard, we have the possibility to override the RFC credentials for interface user that communicates between Tricentis Tosca and SAP Solution Manager. If you want to override the default SAP password, you can tick the checkbox Override RFC credentials to enter username and password.
Last but not least you can click on Finish to complete the integration wizard whereby we have also completed step 2 of the integration process.
In step 3 of the integration process we have to go back to the file explorer on our machine. Here we go to the %COMMANDER_HOME% directory and run the unregisterSapSolManAddin.bat file as Administrator. After the successful execution we run the registerSapSolManAddin.bat file as Administrator as well.
And with that, we have already completed step 3 of the integration process and can continue with step 4.
To enable the automation with Tricentis Tosca we need to perform some settings in SAP GUI options.
First, open the Options in the SAP Logon.
After that, select the menu entry Security and click on the underlying entry Security Settings. In the Security Module section click on the Button Open Security Configuration.
This will open a list with Security Rules. Here we have to enter a new entry for Tosca. To do so, scroll down to the first empty line, select the empty line and click on Insert. This will open a pop up where we have to enter the properties for the rule. Enter the details from screenshot below and click on OK to save new rule.
After we have created the new security rule we need to open the SAP GUI Configuration (by searching for “SAP GUI Configuration” in the windows search box). Be careful that you use the SAP GUI Configuration for the next step and not the SAP GUI options via SAP Logon as before.
Here we have to select first Visual Design and second the underlying entry Applications.
In the Expert Option section click on the Add button to open a pop up.
Navigate to the %TBOX_HOME% directory in the dialog box and execute the file Tricentis.Automation.SapServer.exe.
As a result sapguiserver and Tricenits.Automation.SapServer should appear in the Expert Option section as you can see here:
At the end, click on OK to save the changes and finish step 4 of the integration process.
Finally, we come to the last step of the integration between Tricentis Tosca and SAP Solution Manager. In this part we have to perform and check some settings in the SAP Solution Manager system. Therefore, log in to the system with your user (administrator rights are mandatory to fulfill this part of the integration).
First start transaction SE16 and open the database table ECCUST_ET. If there is not entry for Tricentis Tosca already you have to create a new entry by clicking on the Create button. Enter the following details and save your entry:
Secondly, we have to generate the standard eCATT-User in SAP Solution Manager. This has to be done only once per system, so if the eCatt-User already exists in your SAP Solution Manager system you can skip and continue with the check of the authorizations.
If the user does not already exist open transaction SE38 and execute the report ECATT_GENERATE_ET_USER.
After successful execution of the report, you have to activate the created role in transaction PFCG by entering the role SAP_ECET and selecting Change. Here you have to switch to the Authorizations tab and select Change Authorization Data. Place your cursor on the root element of the tree and click on Authorizations and then on Generate. Last but not least save your changes.
After the successful creation of the user we can check in transaction SU01 if the user has the necessary authorizations. Therefore, open the authorizations of the role SAP_ECET. It should contain at least the two entries ECATT_EXTERNAL_TOOL and SYST (with Activity Execute or 16 and Type of RFC object Function group) as you can see here:
Also, Tricentis recommends to disable scripting in the SAP Solution Manager system. You can disable it in transaction RZ11 by entering the parameter name sapgui/user_scripting. Here you have to set all three values to FALSE as you can see in the following screenshot:
Another setting we need to check is if the RFC service of the SAP system is activated. To do so, open transaction SICF and click on Execute. Here you have to find the rfc entry by navigating through the tree beginning with sap -> bc -> soap -> rfc or otherwise by filtering for rfc. After you have found the RFC service that is underneath soap you have to perform a right-click on it and select Activate Service (if Activate Service is already grayed out everything is fine and you can continue with the next step).
Last but not least we have to activate eCATT in our SAP Solution Manager system. Therefore, we call transaction SCC4. There we have to select our client and perform a double-click on it. On the next screen that opens we need to check the entry in the section CATT and eCATT Restrictions. If the entry is not set to eCATT and CATT Allowed or to eCATT and CATT Only Allowed for ‘Trusted RFC’ we have to change it by clicking on Edit, selecting the appropriate entry and saving the changes.
After that there is just one final step left to complete the integration process in which we have to disable the SAP Logon dialog. Therefore we have to open the Options in the SAP Logon window once again (by clicking on the icon in the upper left corner in SAP Logon). This time we click on Accessibility and Scripting and select Scripting. In the User Settings section, we have to disable the two checkboxes Notify when a script attaches to SAP GUI and Notify when a script opens a connection.
And with that we have successfully completed the integration process between Tricentis Tosca and SAP Solution Manager and can benefit from the advantages of both tools, like starting the Test Case execution from SAP Solution Manager (both attended and unattended) via a Test Plan.
If you are now curious about how you can take advantage of the integration, check out our second blog post where we will get into more detail regarding this topic.
As you can see the integration is pretty straight forward – so have fun and try it out yourself.
Link to our second blog post: https://blogs.sap.com/2022/02/01/how-to-create-a-tricentis-tosca-test-configuration-in-sap-solution-...
As ALM Consultants we saw the need to integrate the SAP Solution Manager 7.2 (SolMan) with Tricentis Tosca to build the base for the future Test Automation Capabilities with regards to new technologies such as SAP Concur, SAP Ariba and SAP SuccessFactors for example. My colleague aman91 and me invested some time to get into Tricentis and the integration with SolMan 7.2 and are happy to share our two contiguous blog articles guiding you through all the steps you need to get started with Tricentis Tosca and Solution Manager. This article focuses on the integration of Tricentis Tosca and SAP Solution Manager 7.2 followed by an article by aman91 where we discuss the creation and benefits of the integration by showing how Tricentis test cases can be created and executed after a successful integration.
Before we get into the technical integration let's have a look on the supported UI's and the different offerings dependent on the customers’ level of support. First, we have to differentiate between Tricentis Test Automation (TTA) and SAP Enterprise Continuous Testing by Tricentis (ECT). The TTA version supports all SAP UI's for on-premise (on prem) and cloud and is part of the SAP Enterprise Support. In comparison to that, the ECT version supports, in addition to the UI's that are already supported in TTA, 160+ UI technologies, mobile apps and many more as you can see in the following figure:
Figure 1: Overview of supported UI-Technologies
As mentioned in this blog post, we focus on the integration of Tricentis Tosca with SAP Solution Manager 7.2.
In a nutshell the process of the integration can be divided into 5 steps:
Figure 2: Process steps for the integration
All the steps for the integration (for the current Tosca version 14.3 STS) can be reviewed in more detail in the official manual of Tricentis. We recommend that you always check the official manual if you are facing any errors in certain areas or whether there are any updates on this rapidly evolving topic.
Step 1: Get Started with SAP Solution Manager integration
In this step we first have to download and install the SAP .NET Connector 3.0 (for 32-bit and 64-bit system types) from the SAP Service Marketplace.
After the successful download and installation, we need to copy the sapnco.dll and sapnco_utils.dll file from the installation directory of SAP .NET Connector 3.0. The 32-bit version has to be copied to the %COMMANDER_HOME%\x86 directory and the 64-bit version to the %COMMANDER_HOME%\x64 directory. As a result of it there should be two dll-files in both directories.
Figure 3: Adding *.dll files to respective Tricentis folder
To complete step 1 of the integration we have to create a multi-user workspace in Tosca. This is required to check in and check out objects from Tosca, so that all SAP Solution Manager users can access and work with them. To do this we have to click on Create new on the start screen of the Tosca Commander.
This will open a pop up where we have to enter the details for our new workspace. First, we have to select a type of repository (Oracle, MS SQL Server, DB2 or SQLite). In our case we selected SQLite:
Figure 4: Pop-up - Create new workspace Tosca
Here you can enter also more specific details for the workspace, all necessary and further information regarding that can be found in the official manual of Tricentis.
After the successful creation of the workspace step 1 of 5 is completed and we can continue with step 2 of the integration process.
Step 2: Run the SAP Solution Manager Wizard
This step has to be done in Tricentis Tosca. First, we have to checkout the project by clicking on the project root element (in the project tab) and select the menu option Checkout Tree. After we have successfully checked-out the project tree we can run the SAP Solution Manager wizard. To do so, right-click on the project root element and select SAP Solution Manager -> Configure SAP Solution Manager Integration on the bottom. This will start the wizard with five steps.
Figure 5: Configure SAP Solution Manager Integration
In first part of the wizard both prerequisites should be fulfilled already if you have done everything correctly in step 1 and you just have to click the Next button. Otherwise, you have to go back to step 1 of the integration and check again what is missing.
Figure 6: Step 1 - Verify prerequisites
In part two of the wizard, we have to enter a username and password for the workspace in Tosca. If you are not using a password, you can leave this input field empty and click on Next.
Figure 7: Step 2 - Workspace details
After that we have to enter the connection details to the SAP Solution Manager system. Most of this information can be found in the SAP Logon where you can copy SAP Host, SAP Client and SAP Instance Number. For SAP Username you have to enter your SAP GUI user which you use to login in to the system (not the ECATT-User!). Also, you have the possibility to enter a path where all log files should be stored and then click on Next.
Figure 8: Step 3 - SAP Solution Manager details
Part 4 of the wizard is optional to secure the communication between Tosca and SAP Solution Manager with a Secure Network Connection (SNC). In our example we kept the settings as in our Development SAP Solution Manager 7.2 and clicked on Next.
Figure 9: Step 4 - SNC settings
In part 5 of the wizard, we have the possibility to override the RFC credentials for interface user that communicates between Tricentis Tosca and SAP Solution Manager. If you want to override the default SAP password, you can tick the checkbox Override RFC credentials to enter username and password.
Figure 10: Step 5 - Override RFC credentials
Last but not least you can click on Finish to complete the integration wizard whereby we have also completed step 2 of the integration process.
Step 3: Register SAP Solution Manager service on your machine
In step 3 of the integration process we have to go back to the file explorer on our machine. Here we go to the %COMMANDER_HOME% directory and run the unregisterSapSolManAddin.bat file as Administrator. After the successful execution we run the registerSapSolManAddin.bat file as Administrator as well.
Figure 11: Register SAP Solution Manager service on your machine
And with that, we have already completed step 3 of the integration process and can continue with step 4.
Step 4: Configure SAP GUI options and settings
To enable the automation with Tricentis Tosca we need to perform some settings in SAP GUI options.
First, open the Options in the SAP Logon.
Figure 12: Open SAP GUI Options
After that, select the menu entry Security and click on the underlying entry Security Settings. In the Security Module section click on the Button Open Security Configuration.
Figure 13: Open Security Configuration
This will open a list with Security Rules. Here we have to enter a new entry for Tosca. To do so, scroll down to the first empty line, select the empty line and click on Insert. This will open a pop up where we have to enter the properties for the rule. Enter the details from screenshot below and click on OK to save new rule.
Figure 14: Security Configuration - Insert security rule
After we have created the new security rule we need to open the SAP GUI Configuration (by searching for “SAP GUI Configuration” in the windows search box). Be careful that you use the SAP GUI Configuration for the next step and not the SAP GUI options via SAP Logon as before.
Figure 15: Search for SAP GUI Configuration
Here we have to select first Visual Design and second the underlying entry Applications.
In the Expert Option section click on the Add button to open a pop up.
Navigate to the %TBOX_HOME% directory in the dialog box and execute the file Tricentis.Automation.SapServer.exe.
As a result sapguiserver and Tricenits.Automation.SapServer should appear in the Expert Option section as you can see here:
Figure 16: Visual Design - Applications - Expert Option
At the end, click on OK to save the changes and finish step 4 of the integration process.
Step 5: Prepare SAP Solution Manager
Finally, we come to the last step of the integration between Tricentis Tosca and SAP Solution Manager. In this part we have to perform and check some settings in the SAP Solution Manager system. Therefore, log in to the system with your user (administrator rights are mandatory to fulfill this part of the integration).
First start transaction SE16 and open the database table ECCUST_ET. If there is not entry for Tricentis Tosca already you have to create a new entry by clicking on the Create button. Enter the following details and save your entry:
Figure 17: Entry in database table ECCUST_ET
Secondly, we have to generate the standard eCATT-User in SAP Solution Manager. This has to be done only once per system, so if the eCatt-User already exists in your SAP Solution Manager system you can skip and continue with the check of the authorizations.
If the user does not already exist open transaction SE38 and execute the report ECATT_GENERATE_ET_USER.
Figure 18: Execute report ECATT_GENERATE_ET_USER in SE38
After successful execution of the report, you have to activate the created role in transaction PFCG by entering the role SAP_ECET and selecting Change. Here you have to switch to the Authorizations tab and select Change Authorization Data. Place your cursor on the root element of the tree and click on Authorizations and then on Generate. Last but not least save your changes.
Figure 19: Generate authorization role via PFCG
After the successful creation of the user we can check in transaction SU01 if the user has the necessary authorizations. Therefore, open the authorizations of the role SAP_ECET. It should contain at least the two entries ECATT_EXTERNAL_TOOL and SYST (with Activity Execute or 16 and Type of RFC object Function group) as you can see here:
Figure 20: Necessary authorizations for user ECATT_ET_USR in SU01
Also, Tricentis recommends to disable scripting in the SAP Solution Manager system. You can disable it in transaction RZ11 by entering the parameter name sapgui/user_scripting. Here you have to set all three values to FALSE as you can see in the following screenshot:
Figure 21: Set parameter value to FALSE in RZ11
Another setting we need to check is if the RFC service of the SAP system is activated. To do so, open transaction SICF and click on Execute. Here you have to find the rfc entry by navigating through the tree beginning with sap -> bc -> soap -> rfc or otherwise by filtering for rfc. After you have found the RFC service that is underneath soap you have to perform a right-click on it and select Activate Service (if Activate Service is already grayed out everything is fine and you can continue with the next step).
Figure 22: Check RFC services in SICF
Last but not least we have to activate eCATT in our SAP Solution Manager system. Therefore, we call transaction SCC4. There we have to select our client and perform a double-click on it. On the next screen that opens we need to check the entry in the section CATT and eCATT Restrictions. If the entry is not set to eCATT and CATT Allowed or to eCATT and CATT Only Allowed for ‘Trusted RFC’ we have to change it by clicking on Edit, selecting the appropriate entry and saving the changes.
Figure 23: Allow eCATT and CATT in SCC4
After that there is just one final step left to complete the integration process in which we have to disable the SAP Logon dialog. Therefore we have to open the Options in the SAP Logon window once again (by clicking on the icon in the upper left corner in SAP Logon). This time we click on Accessibility and Scripting and select Scripting. In the User Settings section, we have to disable the two checkboxes Notify when a script attaches to SAP GUI and Notify when a script opens a connection.
Figure 24: Disable notifications in SAP GUI Options
And with that we have successfully completed the integration process between Tricentis Tosca and SAP Solution Manager and can benefit from the advantages of both tools, like starting the Test Case execution from SAP Solution Manager (both attended and unattended) via a Test Plan.
If you are now curious about how you can take advantage of the integration, check out our second blog post where we will get into more detail regarding this topic.
As you can see the integration is pretty straight forward – so have fun and try it out yourself.
Link to our second blog post: https://blogs.sap.com/2022/02/01/how-to-create-a-tricentis-tosca-test-configuration-in-sap-solution-...
7 Comments
