Known Problems, Limitations and Workarounds in Oracle Open Script

Spread the love
  • 1



Oracle Open Script
Known Problems, Limitations and Workarounds in Oracle Open Script

Known Problems, Limitations and Workarounds

This (Oracle Open Script) section lists known issues and workaround solutions for the components in the Oracle Application Testing Suite.

Oracle Open Script Load Testing

The following are know issues and workaround solutions for Oracle Load Testing.

  • If your script fails to playback successfully in Oracle Load Testing due to Windows authentication or other user permissions related issues with your application, this may be due to the login authentication of the Oracle Load Testing Agent Service. The Oracle Load Testing Agent Service which runs all the Virtual Users on a given Agent system will by default be installed to run under the Local System account. This may cause issues for certain applications if they block access to this account. To address this, open the Oracle Load Testing Agent Service in the Services panel and change the login to run under a specific user with appropriate application permissions.
  • In order to use the Oracle Load Testing Java Client “User Mode” option, users must first save a Java version of their test script saved in Oracle Functional Testing. There is an option available in Oracle Functional Testing that enables it to compile and save the test script in Java for use by the Java Agent. In the Oracle Functional Testing Advanced Options dialog under JavaAgent, check Create a Java Agent script after saving a script. The next time you save your script, Oracle Functional Testing will save the standard script files plus the Java Agent files. This script can then be run in Oracle Load Testing using the Java Client option.
  • When using the SNMP data source, new SNMP MIBs that users specify are uploaded to the Oracle Load Testing Server by default and can be accessed only through the Local Oracle Load Testing Data Collector running on that Server. Remote Oracle Load Testing Data Collectors cannot access these MIBs and users need to copy those over manually.
  • To use the JMX Data Source, you may need to manually copy the server-specific class files to the <installdir>DataCollectorclasses directory on the Data Collector machine. These class files are required for each J2EE Application supported server. The jar files should be same version as the J2EE Application Server. You should get the class files from your Application Server installation. The list of required jar files is contained in the Oracle Load Testing “” file located in <installdir>DataCollectorproperties.
    To do JMX Discovery on WebLogic 10.3.1, doing the following:

    1. Copy <installdir>libwlfullclient.jar to <installdir>DataCollectorclassesweblogic9.1
    2. Open <installdir> and modify it so Agents.JMX.Server.weblogic91.ClassPath = classes/weblogic9.1/wlfullclient.jar and save the file.
    3. Log in to Oracle Load Testing.
    4. Select Metrics from the ServerStats menu then select New.
    5. Also select the JMX Data Source then click Discover Counters.
    6. Select the local system and click Edit.
    7. Select Oracle WebLogic 9.1 as the server (port 8088), username oats and the password (the password specified when installing the Oracle Application Testing Suite product).
    8. Click OK.
    9. Click OK and the discovery process begins. After a few moments, you will see a full list of the MBeans on the server.
    The ServerStats JMX discovery caches counter information. The side effect is that it also caches error messages. For example, failure to copy the correct jar files to data collector’s classes directory prior to attempting the discovery would result in an error. When the discovery is attempted after copying the jar files, the discovery still may not work because of the cache. The recommended workaround is to re-start the Oracle Load Testing Server and retry the discovery.

Oracle Open Script Test Manager

The following are known issues and workaround solutions for Oracle Test Manager.

  • When creating an Oracle Functional Testing type Test Case, the script file must be saved as a package file (.otmpkg) in Oracle Functional Testing in order to attach it to the Oracle Functional Testing Test Case in Oracle Test Manager.
  • The icons in the Tree View for Requirements, Tests and Issues are automatically assigned and cannot currently be configured by the Administrator.
  • After configuring a new database in the Oracle Test Manager Database Configuration dialog, users must restart the Oracle Application Testing Suite Application Service in order for that database to appear in the Database dropdown list on the Oracle Test Manager login page.
  • Troubleshooting OpenScript Script Execution in Oracle Test Manager
    The following additional steps are required in order to run the following types of OpenScript scripts from Oracle Test Manager:

    • Siebel Functional
    • Oracle Forms Functional
    • Web Functional scripts that rely on system input events, such as key press or mouse click
    It is necessary to run these scripts using an interactive desktop of a named Windows user account that is always logged in.
    1. For Siebel and Oracle Forms, the named user’s account must have visited the Siebel or Oracle Forms site at least once to ensure that all necessary ActiveX controls and plug-ins are installed in the named user’s browser.
    2. On the Oracle Test Manager agent machine that will run the scripts, stop the “Oracle Application Testing Suite Agent Service” and configure it to start manually.
    3. On the Oracle Test Manager agent machine, login as the named Windows user account that will run the scripts. From a command prompt, run the following all as one command. The .conf file is an argument for the .exe.
      C:OracleATSagentmanagerbinAgentManagerService.exe -c

      where C:OracleATS is the OATS installed folder.

    4. The named user account must remain logged into the system at all times that scripts will be run.

Oracle Open Script Database 10g Express Edition

The following are known issues and workaround solutions for Oracle Database 10g Express Edition.

  • In some cases, the Oracle Database 10g Express Edition service does not start completely. If you receive a 404 Not Found error when starting Oracle Load Testing or Oracle Test Manager, restart the Oracle database service and the Oracle Application testing service, as follows:
    1. Open the Control panel and the Administrative Tools.
    2. Open Services.
    3. Select the Oracle Application Testing Suite Application Service and click Stop the service.
    4. Select the OracleServiceXE service and click Restart the service.
    5. Wait for the OracleServiceXE service Status to indicate “Started”.
    6. Select the Oracle Application Testing Suite Application Service and click Start the service.
    7. Wait for the Oracle Application Testing Suite Application Service Status to indicate “Started”.
    8. Restart Oracle Load Testing or Oracle Test Manager.
Don't miss out!
Subscribe To Newsletter

Receive top technical news, lesson ideas, travel tips and more!

Invalid email address
Give it a try. You can unsubscribe at any time.

Spread the love
  • 1


  1. Hello, I have just started to use OATS – Openscript. I have been creating scripts to record both Oracle form and eBusiness web. Recording Form has been pretty smooth.

    However, I am kind of stuck now trying to record this web page where I need to click an icon and it will bring up the list of values in a new popup small window (radio button style), then I need to select one and click ok. However, when I playback the script, it does not record this popup window.

    This drives me crazy!! any thoughts?


  2. the applet holding ebs data,which launches before forms are launched,crashes and closes the forms and then restarts.but when it crashes,openscript stops recording.m unable to move forward bcz of this..#

    openscript sucks bigf time


Please enter your comment!
Please enter your name here