Develop an Apache JMeter Performance Test Plan for Oracle Analytics Cloud

1. Start the JMeter application. Change the default name and save the plan.
2. Add components to the plan.
   • A Config Element > User Defined Variables.
   • A Config Element >CSV Data Set Config.
   • A Config Element > HTTP Cookie Manager.
   • A Config Element > HTTP Request Defaults.
   • A Non-Test Element > HTTPs Test Script Recorder.
   • A Thread (Users) > Thread Group.
3. Configure the plan components.
   • User Defined Variables
     • Add the following variables.
       • host – The OAC hostname ending in .com
       • idcs – The IDCS hostname ending in .com
       • pauseMinTime – Used in “think” times. Use a low value, such as 1000, as the default.
       • pauseMaxTime – Use a low value, e.g., 2000, as a default.
       • analyzeMinTime – Used in “analysis” times. Use a low value, such as 1000, as the default.
       • analyzeMinTime – Use a low value, e.g., 2000, as a default.
   • CSV Data Set Config
     • In a text editor, create a .csv file in the same directory as the test plan, e.g., testUserPw.csv.
       • Add a line for the username and password delimited by a comma, e.g., testuser,testpassword.
     • In JMeter:
       • Browse for and enter the Filename.
       • Enter the comma-delimited Variable Names, e.g., user,pw.
   • HTTP Cookie Manager
     • Ensure the box is checked for Clear cookies each iteration.
   • HTTP Request Defaults
     • Enter https for the Protocol.
     • Enter the variable ${host} for the Server name or IP.
     • Enter 443 for the Port Number.
   • Thread Group
     • Add a Listener > View Results Tree.
     • Add four Logic Controller > Recording Controllers.
       • Login
       • Workbook
       • Refresh
       • Logout
     • Add two Sampler > Flow Control Actions.
       • One after Login and one after Workbook.
         • Enter Think Time for the Name of each.
     • Add one Sampler > Flow Control Action after Refresh.
       • Enter Analyze Time for the Name.
     • For each Flow Control Action, add a Timer > Uniform Random Timer.
       • For the Think Timers:
         • Enter ${pauseMaxTime} for the Random Delay Maximum.
           Enter ${pauseMinTime} for the Constant Delay Offset.
       • For the Analyze Timer:
         • Enter ${analyzeMaxTime} for the Random Delay Maximum.
           Enter ${analyzeMinTime} for the Constant Delay Offset.
   • HTTPs Test Script Recorder
     • Click the Test Script Recorder.
       • On the Test Plan Creation tab:
         • Change the Target Controller to <TestPlan>Thread Group>Login.
         • Note the Default Settings Port is 8888.
         • Click Start to generate an HTTPs certificate named ApacheJMeterTemporaryRootCA.crt in the $JMETER_HOME/bin directory.
         • Click Stop.
       • On the Requests Filtering tab:
         • Below is a starter list of patterns to exclude from the recording. Modify it as needed.

           .*png.*
           .*css.*
           .*svg.*
           .*js.*
           *.gif.*
           *.woff2.*
           *.public.*
           *.submit.*
           *.wallpaper.*
           *.static.*
           incoming\.telemetry\.mozilla\.org
           *.ico.*

           • Select the final list and copy it to the clipboard.
         • Click Add from Clipboard to add the URL Patterns to Exclude.
4. Click the Save icon to save the test plan.

Firefox is used because it is the simplest to configure. However, any browser can be used.

1. Start the browser and navigate to Settings.
   • Search for proxy and click the result.
     • Check the button for Manual proxy configuration.
       • Enter localhost for the HTTP Proxy.
       • Enter 8888 for the Port.
       • Check the box for Also use this proxy for HTTPS.
       • Click OK.
   • Search for certificate and click View Certificates.
     • Select Authorities.
     • Click Import.
       • Browse to the JMeter home/bin directory.
         • Select the ApacheJMeterTemporaryRootCA.crt certificate.
         • Click Open.
         • Check the box for Trust this CA to identify websites.
         • Click OK.
2. Close the browser.

Review and remove unnecessary requests under each of the recording controllers.

The username and password used to log into OAC were recorded. Hide the password and add flexibility to the plan.

• Search for the request under the Login controller starting with sso/v1/user/secure/login.
• Click the request to open it.
  • Replace the username with ${user}, the variable specified in the CSV element.
  • Replace the password with ${pw}, the variable specified in the CSV element.
• The portion of the body data should now look like this:

  {“op”:”cred_submit”,”credentials”:{“username”:”${user}”,”password”:”${pw}”,”device” …

The recorded tokens expire. Extract tokens and place them in variables.

• Navigate to the Login > /ui/dv HTTP request.
  • Add three Post Processors > Regular Expression Extractors. Name them:
    • loginCtx
    • signature
    • state
  • Edit the three extractors.
    • Set the Name of created variable to the extractor name, e.g., loginCtx.
    • Set the Regular Expression to: name=”<extractor name>” value=”(.+?)”/> e.g., name=”loginCtx” value=”(.+?)”/>
    • Enter $1$ for the Template.
    • Enter 1 for the Match No.
    • Set the Default Value to: NULL_<extractor name> e.g., NULL_loginCtx.
  • Navigate to the /ui/v1/signin HTTP request.
    • Add a Post Processors > Regular Expression Extractor. Name it accessToken.
    • Edit the extractor.
      • Set the Regular Expression to: accessToken: ‘(.+?)’
      • Set the Name of created variable, Template, Match No. and Default Value as performed for the first three.
  • Navigate to the /ui/dv/ui/api/v1/sessioninfo/ext HTTP request.
    • Add a Post Processors > Regular Expression Extractor. Name it csrfToken.
    • Edit the extractor.
      • Set the Regular Expression to: name=”csrfToken” value=”(.+?)”/>
      • Set the Name of created variable, Template, Match No. and Default Value as performed for the first three.

Pass the variables to subsequent HTTP requests.

Evaluate and add variables for HTTP Request parameters HTTP Header Managers. Below are some examples.

• The /ui/v1/signin request requires variables for the following parameters:
  • loginCtx
  • signature
  • state
• The /sso/v1/user/secure/login HTTP Header Manager requires:
  • The accessToken variable for the Authorization header.
• The /ui/dv/ui/api/v1/homepage and many other requests require:
  • The csrfToken variable for the X-CSRF-Token header.