Absent Member.. MisterT1968 Absent Member..
Absent Member..

QTP/(U)FT Support Tip: How to check, whether Siebel is configured for testing?

Hello all,


How are you? I hope you are fine


This should be a How-To guide related to the Siebel AddIn and testing Siebel applications.


1. Supported versions:




  • Any version not mentioned below, including subversions, have not being quality-assured, therefore not supported by HP.
  • QTP 9.2 and older use the QTP Siebel Add-in 8.0
  • Siebel Thick Client is not supported.
  • Siebel server 7.7.x or higher uses/requires Siebel Test Automation module (STA), for QTP to work against such environments



QuickTest Professional 9.5, 10.00, 11.00, 11.5x:


Built-in: Siebel 7.0.x, 7.5.x, 7.7.x, 7.8.x, 8.0.x,
Patch: None


QuickTest Professional QTP 9.2 and below


Built-in: Siebel 7.0.x, 7.5.x, 7.7.x
Patch: Siebel 7.8.x (QTPSiebel8P7107)


Please keep in mind, that the versions 9.x are already End-Of-Life and should therefore not be used anymore.


2. Check that the STA is installed and active in Siebel 7.7 or higher


In difference to the versions 7.0-7.5, the versions from 7.7. need some pre-requisites.


IMPORTANT: This checklist does not guarantee that the Siebel Test Automation module has been properly install and configured, but it is a very good indicator. If all the items on the list have being verified, and are still experiencing problems, please contact Siebel technical support.


  • Be sure of having installed the Siebel Test Automatio module package on the server, sold directly by Siebel (Oracle).
  • Make sure of having enabled automation on the Siebel server. For detailed information, refer to the Testing Siebel eBusiness Applications Guide, provided with your Siebel installation. The following is provided "AS-IS" considering each version of the Siebel server can be different, therefore we strongly recommend reviewing the mentioned documenation instead of using only the below feedback:


Server Side Configuration:


    • Add/Change the .CFG file for the Siebel server (have in mind there can be more than one application within, ergo multiple cfg files, so be sure of confirming with your Siebel administrator or support engineer to find the respective CFG file of the interface to automate). Add the following to the [SWE] section, for example:

         EnableAutomation = TRUE
         AllowAnonUsers = TRUE
         AutoToken = <SecretWord>


    • Restart the Siebel Server
    • (optional) Add Automation Token



  • Make sure the URL for the log-in page of the Siebel server includes the SWECmd=AutoOn token


Example: http://hostname/callcenter/start.swe?SWECmd=AutoOn.


If mentioned token isn't appended, the Siebel Web Engine (SWE) does not generate test automation information.


If the "Open the following application when a record or run session begins" option is selected in the Siebel tab of the "Record and Run Settings" dialog box, QuickTest Professional automatically appends the Siebel Test Automation information to the URL (you do

not need to specify it manually in the URL).


Note: If user logs out of Siebel, a log-in page is displayed whose URL does not contain this tag. If log back in to Siebel server from such page, the Siebel Test Automation module will not be loaded.


For more information about the Record and Run Settings dialog box options, see the QuickTest Professional Siebel Add-in Guide for version 8.0 or "QuikTest Professional Add-ins Guide" for QuickTest Professional 9.5 or higher


  • Verify that the HTML source of the log-in page of the Siebel server contains the RN='<xxx>', UN='<xxx>', and OT='<xxx>' tags.



Example: Your Siebel server log-in page may contain the following tags:


RN='_SweUserName' UN='_SweUserName' OT='SiebWebText'


To view the HTML source of the Siebel server log-in page in Internet Explorer, select View -> Source from the menu.


  • Check that the list of running processes in the Windows Task Manager includes a process named SiebelAx_Test_Automation_*.exe. This process will appear only after having logged into the Siebel application.


I hope these information helped.


Best regards,

Tino Pacholski

Functional Testing Support Engineer

[If this post solves or helps solve your issue, mark the thread as solved and give KUDOS to the author for their assistance.]
Labels (2)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.