Enabling Automation for Developer Web Client

Automation is available only for Developer Web Clients. Automation is not supported in Mobile Web clients. While installing, you must select the developer web client option only if automation is needed.

After installing the Developer Web Client, Tomcat will automatically be deployed in the following directory: <webclient_install_location>\applicationcontainer_external. The CONTAINERURL for AutomationSubSys section gets updated with the HTTP port provided during the Developer Web Client installation.

1. Enable the system preference by navigating to Administration - Application screen, then the System Preference.

   Name	Value
   Enable UPT	TRUE
   Enable UPT Context	TRUE
   UPT Max Record Cache	100

2. Make the following changes to the Developer Web Client's cfg files:

   • Update the [AutomationSubSys] section by setting the following:

     Set ContainerURL as follows: CONTAINERURL = http://localhost:<Connector Port>/siebel/jbs

     Set the #Port number according to the port specified in the following: C:\Siebel\Client\applicationcontainer_external\conf\server.xml <Connector port="9001" protocol="HTTP/1.1".

   • Update the [InfraUIFramework] section by setting EnableAutomation to TRUE:

     EnableAutomation=TRUE

   Playing the script through Developer Web Client is supported. Use the Siebel Thin Client URL to play back the script.

   • Multiple users using the same User ID is not supported, since it brings in ambiguity during conversion.

   • A case where recording is started and is not stopped, the session is logged out. Stop Recording is injected and considered for conversion.

   • Sticky sessions are not supported.

   • A functional flow is considered for conversion only with the confines of Start and Stop Recording.

   • Single users spanned across sessions are supported.

Approach for generating the Script involving switching of users on Portal and consumer applications

• Start the UPT-KWD recording of new user registration as an anonymous user. Proceed with the recording till a registration followed by login as a newly registered user and if there are any further scenarios for a newly registered user.

  Note: At this point, since there is a user switch (due to new user login), an anonymous user UPT csv file will be generated in an <anonymous_username> folder under the <SiebelServerBuild>\ses\siebesrvr\UPT folder. Copy this anonymous UPT csv based on timestamp.

• Stop the UPT-KWD recording as a new user and log out of the application.

  Note: Since the new user has logged out of the application, the new user UPT csv file will be generated in a <NewUsername> folder under the <SiebelServerBuild>\ses\siebesrvr\UPT folder.

• Now paste the anonymous UPT csv copied in Step 1 into the SiebelServerBuild>\ses\siebesrvr\UPT\<NewUsername> folder. The <NewUsername> folder will now have the following: 'anonymous user UPT csv' and 'new user UPT csv file'.

• Log in to the Siebel application as a new user and generate the KWD Script. This script will have both steps involving anonymous user followed by the new user registration or login and further steps as applicable.