Show TOC

Background documentationMigrating User Data to CBTA SUT Management

 

Since CBTA 3.0 SP02, the user credential tool is no longer available. It is replaced with the system under test (SUT) management for CBTA.

With the SUT management migration program, you can migrate user data from the user credential tool of SP00 or SP01 to the new SUT management in two steps:

  1. Migrate user credentials.

  2. Enhance the SDC with technical destinations, automatically

With the SUT management you can manually enhance existing eCATT system data containers (SDCs) and target components with technical destinations. So CBTA can access systems, start a business or technical session, and Web-based target systems can be tested.

For more information about enhancing SDCs, see Creating a Test Profile With Logon Data for SUTs.

The SUT management migration program enhances SDCs automatically. For each SDC, an enhancement of the target system is created. The process uses the following data:

  • To provide system data and business user information, the business RFC destination or the RFC of the logical component that is assigned to a target system is used.

  • To find the corresponding technical RFC destination (TST_[SID]_CLNT[client]) used by CBTA for underlying internal service processes, the host and client of the target system’s business RFC destination is used, which is directly assigned or derived from the logical component.

  • To create a test profile of an enhancement, the business user of the business RFC destination is used. This test profile defines the business user and password that are used to open a recording or execution session against the SUT. If there was an entry in the old user credential tool for the business user of the business RFC, a DEFAULT test profile (with an empty test profile name) is created in the enhancement. This ensures that existing CBTA tests to which no test profiles are assigned can still run; the system uses the default test profile to determine the business user.

Note Note

If the RFC destination user is set to Current User (transaction SM59, Logon & Security tab), the system assumes that all business users from the old user credential tool, which are migrated, can be used to create a test profile. So the migration program creates test profiles in the SUT management tool for all users. In this process, the first user is assigned to the default test user whose test profile name is empty. The names of other created test profiles match the corresponding business user names.

End of the note.

Restrictions:

  • Releases prior to CBTA 3.0 SP02 only supported the SAP ABAP backend UI technology, so no data for URI-based SUTs is provided.

  • Only SDCs used by CBTA tests are enhanced.

Procedure

1. Migrating the User Credentials

Perform the following steps on each system (such as development system, quality system, production system) on which CBTA is used:

  1. Start transaction SE38 and run the program AGS_TST_MIGRATE_USER_CRED.

  2. SUT management is started, showing the screen for user credentials migration.

  3. Under Migration of user credentials to new SUT management framework, choose productive run. (Only if you have migrated the user credentials already, choose do not execute. You will need this option for the SDC enhancement.)

    Caution Caution

    The productive run overwrites existing data in the SUT management. If you have, for example, updated the password of a user in the SUT management, the old password is restored. If you are not sure whether you have performed this step already, perform step 6.

    End of the caution.

    Recommended: To perform the user credential migration only and exclude the automatic enhancement step, select do not execute under Creation of SDC enhancement for migrated user credentials.

  4. Choose Execute.

  5. To ensure that the migration was successful or if you are not sure whether you have performed this step already, start transaction SE16 and display table AGS_TAO_SETTING. In the CONFIG_UUID field, enter 00505694393A1ED388A25F25907457E7, and choose Execute. If the migration was performed successfully, X is displayed in the Value field.

    If the migration failed, create an incident.

2. Enhancing SDCs

When the migration was successful and if you have not created the enhancements (do not execute was selected), you can now simulate the creation of enhanced SDCs:

  1. In SE38, start program AGS_TST_MIGRATE_USER_CRED, choose Test mode under Creation of SDC enhancement for migrated user credentials.

    Under Migration of user credentials to new SUT management framework, select Do not execute.

  2. Choose Execute.

  3. Errors are reported. To save the result and messages, choose Start of the navigation path System Next navigation step List Next navigation step Save End of the navigation path and store them, locally.

    Resolve the issues. For more information, see the Troubleshooting section.

  4. Repeat the previous steps until no more issues are reported.

    If enhancing an SDC fails (in parts or totally), do the following:

    1. To migrate the other SDCs, proceed with the next step.

    2. In the SUT management, create or complete the failed enhancement manually.

  5. To create the enhanced SDCs and commit them, choose Productive run under Creation of SDC enhancement for migrated user credentials.

  6. Choose Execute.

  7. In the SUT management, choose Check for the RFC destination and for the test profiles and ensure that the status is OK (green icon).

Optional: Updating SDC Enhancements

If a new target system has been assigned to an SDC since the last migration, synchronize the enhanced SDCs with the Enhancing SDCs procedure. Existing enhanced target systems are not overwritten.

Troubleshooting

  • Message: The target component &1 is not fully defined: no RFC or logical component set.

    Reason: The target system of the SDC has no assignment (RFC or logical component).

    Action: If the target system needs to be used, review the definition of your SDC and target system and set an RFC or logical component. Otherwise you can ignore the warning.

  • Message: No enhancement of target &1 and system role &2: No technical RFC TST_SID_CLNT found for host &3 client &4.

    Reason: There are three possibilities:

    • The system has extracted system information from the business RFC destination (host, client) but has not found the technical RFC destination with the same host and client.

    • The system did not get a business RFC destination from the logical component, so it could not determine a technical RFC destination dedicated to CBTA.

    • The business RFC destination assigned directly to the SDC and target system or through the logical component is not properly defined (missing technical data, for example the host), so the RFC destination cannot be resolved.

    Action: If the target system needs to be used, create a test RFC destination for the system in the SAP Solution Manager configuration, under Component-Based Test Automation.

    If a test RFC destination already exists, check if the host information matches.

    Check the configuration of your logical component: An RFC destination must be assigned for the system role that is specified in the error message.

    Check the definitions of the business RFC and technical RFC destinations.

  • Message: No enhancement of target &1 and system role &2: No user credentials found for host &3 client &4.

    Reason: The system cannot get the login information of the business user (defined in the business RFC destination of the current SDC and target system) from the old user credentials tool, to access the SUT.

    Action: The old user credentials are no longer available, so you cannot fix this issue.

    Use the SUT management to define the enhancement.

  • Message: The settings made for the user of the business RFC &1 are not supported. Specific user or current user settings only handled.

    Reason: The logon procedure in the business RFC is not properly defined. Without a specific user or current user settings, the program cannot define a test profile.

    Action: Check whether the user settings of your business RFC destination are empty.

  • Message: SR 010 host unknown in the status bar.

    Reason: A host that is defined in a business RFC destination does not exist anymore or is down. The application also displays a message.

    Action: If the host does not exist anymore, (the SDC and target system that used it probably are not used anymore), ignore this message.

    If the system is down, run the program again or use the SUT management.