Issues while Scheduling CBTA test scripts in Foreground

[Former Member]

Hi,

System details:

Solution Manager: 7.1 SP12

Managed system (SUT): ECC Quality

Test Script: Recorded using CBTA

Currently we have setup CBTA and have recorded few Test Scripts, the setup is fine and we are able to execute CBTA test scripts from tester worklist.

Here we are trying to schedule the CBTA Test Script from the same desktop where were have SolMan and Managed system connectivity as well as the complete setup with CBTA Frontend installed in the same machine

CBTA Functionality of Recording and Execution is working fine. We have also created composite Test Scripts which includes CBTA test scripts for E2E Testing.

Below steps are followed:

1. SolMan User is registered in STPFE- eCATT Foreground Scheduler and activated testing for this user
2. CBTA Test Scripts are scheduled from the Tester worklist using the same user for which the foreground scheduling is activated. We tried scheduling Composite Test Scripts also but still the issue remains the same !
3. Below is the job RSTWB_BATCH_EXECUTE that gets released and immediately gets finished.
4. Job log shows below error The SolMan Login RFC SM_<Solman SID>CLNT<Client number>_LOGIN shows name and password as incorrect
5. We have checked the SolMan Login RFC and found that it is working fine, just that it asks for a password when we tried Remote Logon

RSTWB_BATCH_EXECUTE Job log details

SolMan Login RFC details:

Kindly help us to resolve the issue since it is very critical.

Best Regards,

Kavita Meswani

[Former Member]

Hi Kavita,

you have this error, because you entered a source system of your test configurations in your SOLAR project in Solution Manager.

The source system for this test configuration tells the scheduler to call the system via RFC connection SM_XXXCLNT012_LOGIN.

This will not work, because you can not specify logon data (as user and password) if you are in a batch job.

2 options you have:

• change the RFC connection for the test source system to a TRUSTED rfc like SM_XXXCLNT012_TRUSTED
• specify no source system in your solar project for that test case

Kind regards,

Christoph

[Former Member]

Hello Christoph sorry for asking this but it is related to the change of the RFC, in my System Data Container if I choose the Trusted RFC, It got not selected, so I had to use the Login one, is any parameter that disallowed the use of Trusted RFCs? or the System is not seeing as Trusting system?

Regards,

Paul

[Former Member]

Hi Paul,

typically you connect your SUT in Solution Manager in transaction "SOLMAN_SETUP" via menu point "Managed Systems". With doing this, your standard rfc connections  SM_<SID>CLNT<Client>_READ, SM_<SID>CLNT<Client>_LOGIN and SM_<SID>CLNT<Client>_TRUSTED will be created for you.

Pleas check, if you see these 3 connections for your SUT SID and CLIENT. If yes, Solution Manager and SUT are trusting each other.

It may be, that you User ID has no authorization in SUT to logon via trusted rfc connection!

Please check this, by logon with User ID to Solution Manager, goto SM59, select your fitting SM_<SID>CLNT<Client>_TRUSTED for display and push "Remote Logon" Button. SAPGUI in SUT should be come up.

Kind regards,

Christoph

[Former Member]

Hi Paul,

typically you connect your SUT in Solution Manager in transaction "SOLMAN_SETUP" via menu point "Managed Systems". With doing this, your standard rfc connections  SM_<SID>CLNT<Client>_READ, SM_<SID>CLNT<Client>_LOGIN and SM_<SID>CLNT<Client>_TRUSTED will be created for you.

Pleas check, if you see these 3 connections for your SUT SID and CLIENT. If yes, Solution Manager and SUT are trusting each other.

It may be, that you User ID has no authorization in SUT to logon via trusted rfc connection!

Please check this, by logon with User ID to Solution Manager, goto SM59, select your fitting SM_<SID>CLNT<Client>_TRUSTED for display and push "Remote Logon" Button. SAPGUI in SUT should be come up.

Kind regards,

Christoph