For the system data container (SDC) giving access to a SUT, define
the RFC or HTTP destinations with which to access the system under test (managed system)
the user and password to be used when recording or executing a test script
In the Test Configuration Environment, the test profile associates a test with the configuration. It allows you to reuse combinations of destinations/users under different system roles. When changing the system role, depending on the type of definition, the credentials can be role-dependent or role-independent (see the Available system roles
table below).
Using test profiles makes the system role concept available also for HTTP Destinations and URLs. You do not have to define a separate RFC destination for each business user of your test.
As of SAP Solution Manager 7.1 SP10, the SUT Management for Test Automation
view, in which you create test profiles, replaces the Automated Test User Credentials
view for maintaining credentials in CBTA.
For more information about the process described below, see “CBTA 3.0 SP02 - SUT Management” (http://service.sap.com/~sapidb/012002523100008891912014E.PDF) on SAP Service Marketplace at .
You have configured the CBTA back end components on your systems. For more information, see Configuring the SAP Solution Manager CBTA Back End.
You have defined the system data containers providing access to your SUT systems. For more information, see Creating a System Data Container in the Test Automation Framework.
In the Test Management work center, choose
.To prepare to import your system data container, in the System Data Container Hierarchy
view, enter the name of your SDC
Note
Once you have imported a system data container (SDC) into the SUT Management for Test Automation, for the technical communication between the SAP Solution Manager and the system under test, CBTA uses only the RFC destination defined in SUT Management (test profiles).
Choose Import
.
The SDCs and target components (target systems) are imported and listed.
Navigate to the target component.
The available system roles are listed when relevant, depending on the type of objects in the target components:
System Role | Description |
---|---|
RFC Destination | The default system role is available. It is used regardless of the current system role. |
HTTP Destination | The default system role is available. It is used regardless of the current system role. |
‘NONE’ HTTP Destination | All system roles are available. You can define the SUT to be used, depending on the current system role. This allows you to define a logical set of SUTs, such as “development”, “test”, “pre-production” and “production systems”. |
Logical Component | This is the preferred approach when the SUT is an SAP ABAP system. A logical component contains a list of RFC destinations to be used depending on the system role. You cannot use logical components for URLs. |
Select the system role.
The existing configuration is displayed.
Choose Edit
.
Create a test profile, depending on the SUT type:
The test profile is used in the test composition environment (TCE) test editor to associate a test with the configuration. For more information, see Maintaining SAP Attributes on the Attributes Tab Page and Executable Types.
SAP ABAP system
Note
Always configure test profiles for SAP ABAP systems under SAP ABAP system
even if URI-based access would be possible. Otherwise no back end access is possible and so only a subset of scenarios and features is supported.
Choose the RFC-Based SUT Access
tab page.
Enter the name of the technical RFC destination. The name typically follows the following schema: TST_<SID>_CLNT<CLIENT>
.
For more information, see SAP note 1763697.
Press Enter.
The SID and client data is retrieved by the system and displayed in the table.
Under Business Destination Enhancement Details
, choose Add
.
The system adds a row to the table.
Enter a test profile name.
The test profile name is a free text to identify the current row.
Example
In SAP CRM you can define job profiles such as services and so on, so it makes sense to define one user per job profile and to name the test profile associated with this user to reflect the job of this person, TP_SALES or TP_SERVICES, for example.
Enter the name (business user ID) and password of the business user.
Choose Check to verify your entries
.
SAP JAVA system or an HTML-based third-party system
Select the URI-based SUT Access
tab page.
Choose Add
.
The system adds a row to the table.
Select the connection type:
To enter the URL manually, select BASE_URL
.
To select an existing HTTP destination (similar to an RFC destination) containing the URL to be used, select HTTP_DESTINATION
.
Enter the connection URI
:
BASE_URL
: Enter the URL of your server, including the protocol (http:// or https://), the server name and optionally a port and query string prefix
Example
To record http://wiki.sdn.sap.com/wiki/display/SM/CBTA?param1=value1
, enter http://wiki.sdn.sap.com/wiki/display as the base URL.
Specify the end of the URL (SM/CBTA?param1=value1
) as the executable object.
HTTP_DESTINATION
: Enter the name of the HTTP destination, for example HTTP_DEST_TO_SAP_SMP
Do one of the following:
Enter a test profile name.
To be able to create test scripts in the Test Composition Environment without selecting a test profile name, leave the Test Profile Name
field empty.
This defines a default test profile, to allow you to continue to use test scripts created in previous CBTA releases.
Enter the name (business user ID) and password of the business user. If no user is required, select the Anonymous
checkbox.
To verify your entries, choose Check
.
Save your entries.
The Related Test Scripts
tab page lists test scripts that use the current SDC, target component and the test profiles used by test scripts. For more information, see Maintaining SAP Attributes on the Attributes Tab Page.