5.5 Specifying Scenario-Specific Attributes

In the Create Scenario dialog box, in the HTTP(S) tab, click the New Step icon. The Create Step dialog box opens.

Type a step name in the Name text box.

Select the Type drop-down list and select a step type:

<a href="http://www.netiq.com"><b>NetIQ</b></a>

The reference must include all syntax between the <a> and </a> tags.

<FRAME src="overview-frame.html" name="packageListFrame">

<meta http-equiv="refresh" content="180;URL=mlb_scoreboard.jsp?ymd=20030812">

For form-get and form-post, specify the reference as the name of the Submit button of the corresponding input type=submit tag. For example, the reference is Google Search and the URL is the search from the form action, if the HTML code is:

<form action="/search" name=f>
<input type=submit value="Google Search" name=btnG>
</form>

Define the form_field values in the parameter definitions. See Section 5.5.4, HTTP(S) Parameters.

Create parameters by clicking the New Parameter icon to open the Create Parameter dialog box.

Select the Type drop-down list and select a parameter type:

To save the parameter, click the Create button.

The Create Parameter dialog box closes and the new parameter displays in the Parameter list.

In the Create Step dialog box, click the Validation tab to display the Validation tab:

Click the New Rule icon to open the Create Rule dialog box.

Select the Rule Type drop-down list, then click Response Time.

Response time is the default for all scenarios except HTTP and HTTPS.

Select the Response Type drop-down list and select one of the following:

If the Response Type is Lower or Upper Threshold, select the Alarm Severity drop-down list and select a severity to set for the alarm issued when a response time rule violation occurs.

In the Alarm Description text box, specify a description for the issued alarm:

Click the Create button to create the rule.

The rule displays in the Validation Rules list in the Validation tab.

In the Validation tab, provide information for the following HTTP content that returns from Web server and can be validated:

Select the Regular Expression check box if case does not matter. The regular expression entered is used to validate the syntax.

Select the Allow redirects check box to allow page redirects without failing the test. For example, assume the HTTP code is set to 200 and this check box is selected. The test does not fail if, through the gathering of URL assets, there are one or more redirects that have a code of 302.

Click the Create button to create the step.

The Create Step dialog box closes and the step definition displays in the Steps list in the Create Scenario dialog box.

Because steps occur in the order in which they display, you can click the Move Up and Move Down icons to reorder selected steps:

Click the Create button to create the scenario.

The new scenario displays under the Shared Scenarios element in the Explorer pane.

In the Create Scenario dialog box, click the Validation tab to display the Validation tab.

Click the New Rule icon to open the Create Rule dialog box:

Select the Rule Type drop-down list and select one of the following:

In the Name text box, type the page field name or cookie field name.

In the Value text box, type the cookie or content value.

Select the following check boxes as needed:

Click the Create button to create the rule.

The rule displays in the Validation tab:

In the Validation tab, type information for the following HTTP content that returns from Web server and can be validated:

Select the Regular Expression check box if case does not matter. The regular expression entered validates the syntax.

Select the Allow redirects check box to allow page redirects without failing the test. For example, assume the HTTP code is set to 200 and this check box is selected. The test does not fail if, through the gathering of URL assets, there are one or more redirects that have a code of 302.

Click the Create button to create the scenario.

The new scenario displays under the Shared Scenarios element in the Explorer pane.

Create a class file that extends the Experience Manager Monitor’s methods.

Continue with Creating a Java File to Implement the Test.

Create a Java file with a class that imports:

com.mcode.agent.test.thirdparty.*;

Verify that the class extends:

com.mcode.agent.test.thirdparty.ThirdPartyTest

Verify that the following abstract protected method is included:

protected void runTest() throws java.lang.Exception
{
  //perform your test
}

The parent class gathers the response time.

To access the parameter data, add one of the following methods:

To include additional data in the alarm properties, call the following method:

public void addDetail(Detail detail);
//To create a new Detail object
public class Detail
{
 private String name;
 private String value;
 public Detail(String name, String value)
 {
  this.name=name;
  this.value=java.net.URLEncoder.encode(value);
 }
}

In the alarm properties, each value pair is represented as a name value pair.

To access the log object, add one of these methods:

Compile the code using the thirdpartytest.jar located in the /OperationsCenter_ExperienceManager_install_path/tests/thirdpartyexamples directory.

A .class file is created for the Java file.

Create a .jar file.

Add this new .jar file to the /OperationsCenter_ExperienceManager_install_path/html/bem/monitor directory.

This alerts the Experience Manager Monitor to add the file into its classpath.

It is not necessary to add the thirdpartytest.jar because it is already included in the manager.jar file.

Add this new .jar file as an application resource to /OperationsCenter_ExperienceManager_install_path/html/bem/monitor.jnlp.

Restart the Experience Manager Monitor to download the new binary file.

In the Create Scenario dialog box, select the Type drop-down list, then click Third Party.

On the Third Party page, type the Class Name.

Provide a fully qualified class in order to call the test. It is not necessary to add the .class extension to the class name.

Click the New Parameter icon to add name/value pairs as required for the third-party test scenario.

Click the Create button to create the scenario. The new scenario displays under the Shared Scenarios element in the Explorer pane.