Summit Application Setup

This document explains how to install the Summit Application, and a description of the scenario used for testing. It is assumed that you are familiar with configuring Forms.

Setup the Development Environment

  1. Expand the ZIP file. This document uses C:\summit as the destination.
  2. Create a user called SUMMIT in your database:

    SQL> connect system/manager
    SQL> create user summit identified by summit;
    SQL> grant resource, connect to summit;

  3. From the command line, import the Summit data:

    imp userid=summit/summit@<connect_string> file=summit.dmp full=y

  4. Put C:\summit in the FORMS_PATH in your .env file
  5. Compile the application. The file GEN.BAT will generate the files under Microsoft Windows.

Setup the Runtime Environment

  1. Add the following virtual directory to your web server configuration files. This example is for Apache and can be placed in HTTPD.CONF.

    Alias /summit/ "C:\summit/"

    If you are using iDS to view the Summit application, you need to set it in OC4J's config file: $ORACLE_HOME\j2ee\DevSuite\application-deployments\forms\formsweb\orion-web.xml

    <virtual-directory virtual-path="/summit" real-path="C:\summit" />
  2. If you want to start the application from a config section, add the following to your FORMSWEB.CFG file, and go to step 6. Otherwise go to step 3.

    [summit]
    archive=frmall.jar,oracle.forms.demos.RoundedButton.class
    userid=summit/summit@<connect_string>
    form=customers
    pageTitle=Summit
    splashScreen=no
    lookAndFeel=oracle
    separateFrame=false
    width=994
    height=582

    Don't forget to replace <connect_string> with your connect string. You way also need to add the plugin variables to the summit config section so the correct plugin in picked up. The following is an example of how to get Sun's plug-in v1.6 to be picked up:

    baseHTMLJInitiator=basejpi.htm
    jpi_classid=java:oracle.forms.engine.Main
    jpi_mimetype=application/x-java-applet;version=1.6.0
    jpi_codebase=http://java.sun.com/products/plugin/autodl/jinstall-1_6_0-windows-i586.cab#Version=1,6,0,10

  3. Add oracle.forms.demos.RoundedButton.class to your archive (or archive_jini if youa re using Jinit) parameter in the formsweb.cfg file.

  4. Modify your registry file ($ORACLE_HOME/forms/java/oracle/forms\registry\registry.dat) so that Forms can find the icons for the Summit application:

    default.icons.iconpath=summit/web

  5. Copy the file RoundedButton.class to a new directory that you name demos in $ORACLE_HOME/forms/java/oracle/forms so that Forms can find the class file.
  6. If it is not already there, add C:\summit to your FORMS_PATH.
  7. Run the Form, either from the Builder or by adding config=summit to theURL that starts Forms on the AS server.

Workload Scenario

The following two scenarios describe the workloads used during scalability testing.

Data Entry

  1. Locate the sales rep in the navigator tree of the customers.fmx form.
  2. Choose different ordering of the customers by clicking on the name and phone button in the M/R-block.
  3. Choose one customer in the navigator tree.
  4. Verify address and phone number of the customer and quickly click through the other tabs of the customer detail block.
  5. Double click on the customer to go to the ORDER.fmx form.
  6. Scroll through the first five orders using the cursor key.
  7. Press the "create record" key (CTRL-DOWN).
  8. Insert a new order.
  9. Insert a new item for this order, choosing it through the LOV on the product id item.
  10. Verify, that the product is on stock by clicking on the STOCK button and press EXECUTE QUERY key (CTRL-F11). Then close the STOCK window immediately.
  11. Do the same for three more items.
  12. Press the SAVE iconic button to save the order in the database.
  13. Now delete all the items, press the save key (CTRL-S), delete the order and press the save key again. (This is required so that we do not generate millions of orders during the performance tests).
  14. Now enter a new order with only three items following the same steps as above.
  15. Delete this order as well.
  16. Exit the order form.

The scenario takes approximately 10 minutes. If an order entry is completed faster, wait until the 10 minutes were completed. This was done 3 times, so that the resulting script had a duration of 30 minutes.

Query

  1. Look for a sales person in the navigator tree.
  2. Order his customers using the buttons in the customer M/R block.
  3. Choose a customer in the navigator.
  4. Examine the customer detail information on each tab-folder.
  5. Do the above operation for 5 minutes with plenty time for reading through the information on the customer tab.
  6. After 5 minutes double click on a customer node in the navigator tree.
  7. For 5 minutes use different queries to select orders and scroll through the result sets.
  8. Take time to read the order and item information.
  9. Exit the order form.

The above steps were performed for 30 minutes.