1. Getting Started with Application Management Pack for Siebel
  2. About Siebel Transactions

5 About Siebel Transactions

This chapter provides procedures for the following topics:

Typical Siebel Transactions

A Siebel transaction is a series of user actions on a Siebel application. In Enterprise Manager, each user action is referred to as a step. Each step can contain multiple related steps.

A typical Siebel transaction might consist of the following steps:

  1. Open a browser and enter the URL for the service you want to access.
  2. Click the Sign In link. The Sign In page is displayed.
  3. Enter a user name and password, and click OK.

    At this point the application performs a series of actions that range from authenticating your credentials to verifying the privileges you have.

    The application displays the functionality available for you.

  4. Log out.

Note:

Enterprise Manager Cloud Control creates a test named "Login Test" after the service discovery is complete. By default, this default test is designed to use siebel as the operating system username and siebel as password. If you do not have an account with siebel and siebel as the credentials on the beacon host, create the account. Alternatively, edit the default test to set credentials that match with an existing account on the beacon host.

If the operating system credentials provided are incorrect, the test appears in a pending state.

Recording Transactions and Testing Availability and Performance

You can record the steps of a particular transaction and store them in the repository. You can then run them to test the availability and performance of your Siebel application.

For example, you can create a transaction using the preceding steps and call it Typical Login. You can then program the appropriate components to run the transaction automatically. The beacon, a component of the Agent, acts as a client robot and is used to run your recorded transactions at predefined time intervals from strategic locations across your Wide Area Network (WAN).

Beacons are not installed automatically on the Management Agents; they have to be created. For monitoring Siebel High Interactive Applications, the administrator needs to create a beacon on an Oracle Windows Agent.

The availability and performance data that beacons collect during service tests include whether a test is successful and the application is available, and the response time of application screens during a given service test.

Adding a Siebel HI Test with Transaction Groups to an Existing Service

Before proceeding, ensure that you have already added the Siebel service using the instructions in Adding a Siebel Service for a Siebel Application.

Besides recording the steps of a transaction, you can also group them to create a separate, logical entity. If you do not group the steps, Enterprise Manager groups them automatically under the "Generic" category.

To record transactions with groups, follow these steps:

  1. In Enterprise Manager Cloud Control, click Targets,then click Siebel.
  2. On the Siebel page, from the View list, select Application Service. Enterprise Manager lists all the Siebel services being monitored.
  3. Click the name of a Siebel Call Center Service, Siebel Sales Service, or a Siebel Marketing Service. Enterprise Manager displays the Home page of the selected service.
  4. Click the Monitoring Configuration tab.
  5. On the Monitoring Configuration page, click Service Tests and Beacons.

    The Service Tests and Beacons page is displayed, as shown in Figure 5-1.

    Figure 5-1 Service Tests and Beacons Page


    Service Tests and Beacons

  6. In the Service Tests section on the Service Tests and Beacons page, from the Test Type list, select ATS Transaction and click Add.
  7. On the Create Service Test page, enter a name and description for the service test, and specify the collection frequency of the test run (in minutes).

    Figure 5-2 Create Service Test Page


    Create Service Test

  8. In the ATS Zip Archive section select From Local Machine in the drop-down box and click Select.
  9. Navigate to the ATS test file in your system and add the file for the service test.
  10. In the Variables section, select the variable option for the service test.
  11. Enter details in the Script Info section as necessary and click Verify Service Test.

    The test results are displayed in the Results table.

  12. Click Continue.
  13. In the Service Tests and Beacon page, from the Service Test section, select the new service test and click Enable to enable the service test.

    The status of the service test is displayed in the table.

Using OATS to Record and Playback Siebel Transactions

For details on how to create ATS load testing scripts, see Oracle Functional Testing OpenScript User's Guide.

For other important reference links, see the following: