2 Using the Admin Console to Model Data and Create Users

Restrictions and Recommendations For Oracle BPEL Process Manager Sensors

The following topics describe restrictions and recommendations on using Oracle BPEL Process Manager sensors that will be captured by Oracle BPEL Process Analytics:

• Only Activity Sensors Are Supported

• Activity Sensors Can Be Associated with messageType Variable Only

• Database Sensor Action Can Be Used for Debugging Sensor Output

• Designing a Sensor for Oracle BPEL Process Analytics

• Define Sensors for End Events Last

• Process Versioning Is Not Supported

For complete information about defining and deploying activity sensors, see Oracle BPEL Process Manager Developer's Guide.

<variable name="inputVariable" messageType="client:pcshopRequestMessage"/>
<variable name="outputVariable" messageType="client:pcshopResponseMessage"/>

<variable name="finalresult" type="xsd:string">
<variable name="resultReason" type="xsd:string">

Database Sensor Action Can Be Used for Debugging Sensor Output

The Oracle BPEL Process Manager database sensor action results in the sensor data being displayed in the Oracle BPEL Process Manager Console. This is useful for debugging and to check that sensors are being fired as expected. The Oracle BPEL Process Manager administrator must add the database sensor action when defining sensors, to enable the display of sensor data in the Oracle BPEL Process Manager Console. Figure 2-4 shows the Oracle BPEL Process Manager Designer window used for defining the database sensor action.

Figure 2-4 Database Sensor Action

Description of the illustration dbsensoraction.gif

Designing a Sensor for Oracle BPEL Process Analytics

Follow these steps to create an Oracle BPEL Process Manager sensor for Oracle BPEL Process Analytics to monitor:

1. Create the sensor actions

   The JMS Queue sensor action is required. The Database sensor action is optional, but is helpful for debugging purposes. See "Database Sensor Action Can Be Used for Debugging Sensor Output" for more information.

2. Create the desired sensors.

   When you create the sensor, select Completion for the evaluation time, as shown in Figure 2-5.

   Be aware that sensors must be defined on messageType variables. See "Activity Sensors Can Be Associated with messageType Variable Only" for more information.

   Choose only the part name from the Variable XPath Builder, as shown in Figure 2-6. Do not select attributes; the attributes are selected when the sensor is modeled in the Oracle BPEL Process Analytics Admin Console.

3. Add the sensor actions to the sensors.

4. Save the sensors and sensor actions.

5. Deploy the sensors.

Figure 2-5 Create Activity Sensor

Description of the illustration createactsensor.gif

Figure 2-6 Variable XPath Builder

Description of the illustration variablexpath.gif

Oracle BPEL Process Manager Event Source Configuration Values

For Oracle BPEL Process Analytics to capture events from an Oracle BPEL Process Manager event source, the Oracle BPEL Process Manager administrator must insert sensors that capture the events of interest and then publish those events to a Java Message Service (JMS) queue. Oracle BPEL Process Analytics connects to the JMS queue to capture the events and uses the Web Services Description language (WSDL) URL to browse the event metadata.

See "Restrictions and Recommendations For Oracle BPEL Process Manager Sensors" for information about the types of sensors Oracle BPEL Process Analytics supports.

<BaseCubeSessionBean::logError> Error while invoking bean "process manager": 
Cannot find process content file. Cannot find the content file "sensor.xml" for process "TaskActionHandler" (revision ""). 
Please check that the path "sensor.xml" is correct and refers to a file that has been included as a part of the deployment archive.

Table 2-1 describes the values Oracle BPEL Process Analytics requires to create the JMS queue and form a connection.

Generic Event Source Configuration Values

For Oracle BPEL Process Analytics to capture events from a generic event source, the administrator for the event source must specify the connection parameters and publish the events of interest to one of the following types of queues:

• An Oracle Java Message Service (OJMS) queue preconfigured by Oracle BPEL Process Analytics, called bam_genericmonq.

  Table 2-2 describes the connection parameter values Oracle BPEL Process Analytics requires to specify a generic event source using the bam_genericmonq queue.

• A user-specified OJMS queue.

  Table 2-3 describes the connection parameter values Oracle BPEL Process Analytics requires to specify a generic event source using a user-specified OJMS queue.

• A user-specified Java Message Service (JMS) queue

  Table 2-4 describes the values Oracle BPEL Process Analytics requires to specify a generic event source using a user-specified JMS queue.

Details about publishing events for the generic monitor are described in Chapter 7.

java:comp/resource/BAM/QueueConnectionFactories/qcf

java:comp/resource/BAM/Queues/bam_genericmonq

com.evermind.server.rmi.RMIInitialContextFactory

java:comp/resource/JMS-provider/QueueConnectionFactories/qcf

java:comp/resource/JMS_provider/Queues/OJMS-queue-name

com.evermind.server.rmi.RMIInitialContextFactory

jms/QueueConnectionFactory

jms/JMS-queue-name

com.evermind.server.rmi.RMIInitialContextFactory

Event Simulator Configuration Values

For Oracle BPEL Process Analytics to capture events generated by an event simulator, you must set up an event simulator as described in Chapter 8"Simulating Events".

Table 2-5 describes the values Oracle BPEL Process Analytics requires to capture events generated by an event simulator.

Viewing Existing Composite Events and Composite Event Groups

You might find it useful to review existing composite events and composite event groups as you proceed with data modeling. You can view composite events and composite event groups, as well as access details about them from the Composite Events and Groups page. See the following topics for more information:

• Viewing a List of Existing Composite Events and Groups

• Viewing Details About a Composite Event Group

• Viewing Details About a Composite Event Within a Composite Event Group

• Viewing Details About a Composite Event

Viewing a List of Existing Composite Events and Groups

1. In the Admin Console, click Modeling to open the Modeling page.

2. Click Composite Events to open the Composite Events and Groups page.

This page displays the name, type (the event source for the composite event, or in the case of a composite event group, the value Group), and the administrator-specified description for each composite event and each composite event group.

Viewing Details About a Composite Event Group

To view details about a composite event group:

1. In the Admin Console, click Modeling to open the Modeling page.

2. Click Composite Events to open the Composite Events and Groups page.

3. In the Composite Event and Groups page, click the name of a composite event group to display the list of composite events contained in that group.

4. Click Show Properties to display the following composite event group properties:

   • Name of the composite event group

   • Administrator-defined description of the composite event group

   • Timeout value for the composite event group, expressed in seconds

   • Dimensions defined on the composite event group

   • Composite events in the composite event group

   • End events for the composite event group

Viewing Details About a Composite Event Within a Composite Event Group

To view details about a composite event within a composite event group:

1. In the Admin Console, click Modeling to open the Modeling page.

2. Click Composite Events to open the Composite Events and Groups page.

3. In the Composite Event and Groups page, click the name of a composite event group to display the list of composite events contained in that group.

4. Click the name of a composite event to view details about the composite event.

Viewing Details About a Composite Event

To view details about a composite event:

1. In the Admin Console, click Modeling to open the Modeling page.

2. Click Composite Events to open the Composite Events and Groups page.

3. In the Composite Event and Groups page, click the name of the composite event to view these composite event details:

   • The name of each event included in the composite event

   • Which event or events are the end events for the composite event

   • The composite event group to which the composite event belongs, if applicable

   • The attribute used to correlate the events

   • Each dimension associated with the composite event and the event attribute to which it is mapped

4. Select an event to view these details about that event's attributes:

   • The administrator-specified alias for each event attribute

   • The administrator-specified type for each event attribute

   • The XPath to each event attribute

Creating Composite Events

You must create one or more composite events before you can create KPIs or metrics.

To create a composite event:

1. In the Admin Console, click Modeling.

2. Click Composite Events to open the Composite Events and Groups page.

3. Click Add Composite Event. The Modeling – Create Composite Event page opens.

4. Select the row containing the event source name and event source type for which you want to create a composite event, then click Create. The Create Composite Event Wizard opens.

5. Follow the steps through the wizard. If you need help using a wizard page, click the Help link on that page.

Be aware that he first time you create a composite event using a generic event source, an exception such as the following is logged to the monitor.log file. This exception is harmless and can be safely ignored; the composite event will be created as expected.

Note that in the example, the time zone is Eastern Daylight Time (EDT). The time zone included in the log file is the time zone where the system running Oracle BPEL Process Analytics is running.

2005/06/06 16:01:32.781 EDT ERROR:1 MF/MF: [Generic Monitor] Error loading generic event definitions java.io.FileNotFoundException: C:\OraAs10g\integration\bam\config\GenericEventDefinitions.xml(The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at oracle.tip.bam.monitor.generic.GenericEventDefinition.loadEventDefinitions(
GenericEventDefinition.java:137)
at oracle.tip.bam.monitor.generic.GenericEventDefinition.<init>(GenericEventDefin ition.java:92)
at oracle.tip.bam.monitor.generic.GenericMetadata.<init>(GenericMetadata.java:57).
at oracle.tip.bam.monitor.generic.GenericMonitor.getESMetadata(GenericMonitor.java:351)
at oracle.tip.bam.monitor.fw.MonitorFramework.startMonitors(MonitorFramework.java:346)
at oracle.tip.bam.monitor.fw.MetadataListenerImpl.metadataUpdated(MetadataListenerImpl.java:73)
at oracle.tip.bam.metadata.repos.GenerateReposEvent.run(GenerateReposEvent.java:1 43)

See "Locating Oracle BPEL Process Analytics Log Files" for more information about the monitor.log file.

Creating Composite Event Groups

To correlate events that span event sources, you must first create at least one composite event for each event source, and then create a composite event group to correlate these individual composite events.

To create a composite event group:

1. In the Admin Console, click Modeling.

2. Click Composite Events to open the Composite Events and Groups page.

3. In the Composite Events and Groups page, click Add Group to open the Create Composite Events Group Wizard.

4. Follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

Modifying Composite Events

If you find that an existing composite event is not configured as you need it, then you can modify it by following these steps:

1. In the Admin Console, click Modeling.

2. Click Composite Events to open the Composite Events and Groups page.

3. Click the pencil icon corresponding to the composite event that you want to modify.

4. A page opens to confirm that you want to modify the composite event. Click Yes to proceed; click No to cancel the operation. If you click Yes, then the Update Composite Event Wizard opens; if you click No, then the Composite Events and Group page opens with no changes made.

5. If you clicked Yes in the previous step, then follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

Modifying Composite Event Groups

If you find that an existing composite event or composite event group is not configured as you need it, then you can modify it.

Be aware that you can remove a composite event from a composite event group, but doing so will result in the entire composite event group being deleted. (You will be asked to confirm the operation before the composite event group is deleted.)

To modify a composite event group:

1. In the Admin Console, click Modeling.

2. Click Composite Events to open the Composite Events and Groups page.

3. Click the pencil icon corresponding to the composite event group that you want to modify. A confirmation page opens.

4. Click Yes if you want to continue; otherwise click No. If you click Yes, then the Update Composite Events Group Wizard opens; if you click No, then the Composite Events and Group page opens with no changes made.

5. If you clicked Yes in the previous step, then follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

Deleting Composite Events and Composite Event Groups

If you decide that a previously created composite event or composite event group is no longer needed, then you can delete it. When you request that an object be deleted, Oracle BPEL Process Analytics presents a list of other objects that will also be deleted before proceeding with the operation. The delete operation will not take effect until you confirm it.

To delete a composite event or composite event group:

1. In the Admin Console, click Modeling.

2. Click Composite Events to open the Composite Events and Groups page.

3. In the Composite Events and Groups page, click the trash can icon corresponding to the composite event or composite event group that you want to delete. A confirmation page opens.

4. In the confirmation page, click Yes, if you are sure you want to continue with the delete operation; otherwise, click No.

To delete a composite event that is one of multiple composite events in a composite event group, you must first modify the group to remove the composite event. See "Modifying Composite Event Groups" for information about modifying a composite event group.

Viewing Metrics

You can view a list of previously created metrics, as follows:

1. In the Admin Console, click Modeling.

2. Click Metrics. The Metrics page opens and displays all previously created metrics.

3. If desired, click a metric name. The Metrics Detail page opens and presents these details about the selected metric:

   • The metric name

   • The administrator-defined description of the metric

   • The metric value type

   • The composite event on which the metric is based

   • The expression that defines the metric

   • The constraints, if any, defined on the metric

   When you are done viewing metric details, click Return to List to return to the Metrics page.

Creating Metrics

Before you create a metric, you must first create one or more composite events or composite event groups (as described in "Modeling Composite Events and Composite Event Groups").

To create a metric:

1. In the Admin Console, click Modeling.

2. Click Metrics to open the Metrics page.

3. In the Metrics page, click Create to open the Create Metric Wizard.

4. Follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

Modifying Metrics

After you define a metric, you may find you need to adjust it. You can change all characteristics of a metric, except the name and the composite event on which it is based.

To modify a metric:

1. In the Admin Console, click Modeling.

2. Click Metrics to open the Metrics page.

3. Click the pencil icon corresponding to the metric that you want to update.

4. In the confirmation page, click Yes if you want to continue; click No if you do not. If you click Yes, then the Update Metric Wizard opens. If you click No, then the Metrics page opens.

5. Follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

Deleting Metrics

If you decide that a previously created composite event is no longer needed, then you can delete it.

To delete a metric:

1. In the Admin Console, click Modeling.

2. Click Metrics to open the Metrics page.

3. Click the trash can icon corresponding to the metric you want to delete.

4. In the confirmation page, click Yes if you want to delete the metric; click No if you do not. If you click Yes, then the metric is deleted and the Metrics page opens. If you click No, then the metric is not deleted, and the Metrics page opens.

Viewing Key Performance Indicators

To view previously created KPIs:

1. In the Admin Console, click Modeling.

2. Click KPIs to open the KPI page. The following properties are displayed:

   • The KPI name

   • The name of the composite event on which the KPI is based

   • The administrator-specified description of the KPI

3. Click the name of a KPI to view these additional details about that KPI:

   • The KPI value type, which is the type to which the KPI evaluates

   • The aggregation type of the KPI, which is the type of aggregation applied to the event attributes to arrive at the KPI value

   • The expression, which defines the KPI value

4. Click View Target Data to open the KPI Target Detail page.

   See "Viewing Key Performance Indicator Target Values" for information about using the KPI Target Detail page.

Creating Key Performance Indicators

To create a KPI, you must first create one or more composite events, as described in "Modeling Composite Events and Composite Event Groups", then to create a KPI, follow these steps:

1. In the Admin Console, click Modeling.

2. Click KPIs to open the Key Performance Indicators (KPI) page.

3. Click Create to open the Create Key Performance Indicator Wizard.

4. Follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

Modifying Key Performance Indicators

To modify a KPI:

1. In the Admin Console, click Modeling.

2. Click KPIs to open the KPI page.

3. Click the pencil icon corresponding to the KPI you want to modify. A confirmation page opens.

4. In the confirmation page, click Yes if you want to continue; click No if you do not. If you click Yes, then the Update Key Performance Indicator Wizard opens. If you click No, then the KPI page opens.

5. Follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

Deleting Key Performance Indicators

If you decide that a previously created KPI is no longer needed, then you can delete it.

To delete a KPI:

1. In the Admin Console, click Modeling.

2. Click KPIs to open the KPI page.

3. Click the trash can icon corresponding to the KPI that you want to delete.

4. In the confirmation page, click Yes if you want to continue; click No if you do not. If you click Yes, then the Update Key Performance Indicator Wizard opens. If you click No, then the KPI page opens.

Defining Key Performance Indicator Target Values

A KPI target value is the goal value for a KPI that you specify. Target values are sometimes referred to as budget values.

If you specify target values for a KPI, then you can configure the actual and target values into the same Dashboard chart. This allows a Dashboard user to see, at a glance, how aspects of the business are performing relative to goals.

In addition, specifying target values is a prerequisite, along with specifying KPI performance bands, for presenting data in a radar chart and cause/effect tables. See "Understanding Key Performance Indicator Performance Bands" for more information.

To specify target values for a KPI:

1. In the Admin Console, click Modeling.

2. Click KPIs to open the Key Performance Indicators (KPI) page.

3. Click the name of a KPI for which you want to specify target values. The KPI Detail page opens.

4. Click Prepare New Target Data. The KPI Target Data Wizard opens.

5. Follow the steps through the KPI Target Data Wizard. If you need help using a wizard page, then click the Help link on that page.

6. After you complete the KPI Target Data Wizard, click Process Prepared Data to generate a SQL*Loader file from the target data you prepared. The KPI Target Data page opens to display a list of files for use with SQL*Loader files.

7. At the command line (outside of the Oracle BPEL Process Analytics Console), run SQL*Loader to load the target data into the BAM schema.

Suppose, for example, the KPI Target Data page appears as shown in Figure 2-8. If your current directory is C:\OraHome3\integration\bam\config\data, and the database in which the BAM schema is located is db1, then the SQL*Loader command to load the data is:

sqlldr control=target_loanFlowHDim.ctl, DATA=target_loanFlowHDim.dat USERID=bam/bam@db1
 

SQL*Loader returns messages, such as the following:

SQL*Loader: Release 10.1.0.3.0 - Production on Wed Mar 23 09:31:12 2005
 
Copyright (c) 1982, 2004, Oracle.  All rights reserved.
 
Commit point reached - logical record count 64
Commit point reached - logical record count 128
Commit point reached - logical record count 192
Commit point reached - logical record count 256
Commit point reached - logical record count 320
Commit point reached - logical record count 384
Commit point reached - logical record count 448
Commit point reached - logical record count 512
Commit point reached - logical record count 576
Commit point reached - logical record count 640
Commit point reached - logical record count 704
Commit point reached - logical record count 744

See Oracle Database Utilities for more information about using SQL*Loader.

Figure 2-8 Sample KPI Target Data Page

Description of the illustration kpitargetprep.gif

Viewing Key Performance Indicator Target Values

KPI target values are the goal values for a KPI that you specify, as described in "Defining Key Performance Indicator Target Values". To view previously defined KPI target values:

1. In the Admin Console, click Modeling.

2. Click KPIs to open the Key Performance Indicators (KPI) page.

3. Click the name of the KPI for which you want to view target values. The KPI Detail page opens.

4. Click View Target Data. The KPI Target Data page opens.

5. If the amount of target data is large, then you can specify a subset of the target data you want to view, as described in the following list, and then click View Target Data again.

   • Time Grain – Select the time grain for which you want to view KPI target values. If you specify a time grain of Day, for example, then daily target values are displayed.

   • Time Period Start – Optionally, enter the start time for the time period using one of the following forms, depending on the time grain you specified:

     • yyyy, for example 2004, if the time grain is Year

     • yyyymm, for example 200401 for January 2004, if the time gain is Month

     • yyyymmdd, for example 20040121 for January 21, 2004, if the time grain is Day

     The values are inclusive, if specified.

   • Time Period End – Optionally, enter the end of the time period, using one of the forms as described for Time Period Start.

   • Dimension Columns – Select the dimension columns for which you want to view target values.

   • Dimension Value – Select the dimension values for which you want to view target values.

Viewing Dimensions

To view dimensions that have been previously specified:

1. In the Admin Console, click Modeling.

2. Click Dimensions. The Dimensions page opens and displays all previously created dimension names.

3. If desired, click a dimension name to view these dimension properties:

   • Names of columns in the dimension

   • Primary key for the dimension

   • Data type of each column in the dimension

   • Hierarchy rank of each column in the dimension

     A hierarchical dimension is one that uses ordered levels as a means of organizing data. For example, in a time dimension, the hierarchy organizes data at the year level (hierarchy 1), the month level (hierarchy 2), or the day level (hierarchy 3).

Viewing Dimension Values

To view the values for a dimension:

1. In the Admin Console, click Modeling.

2. Click Dimensions. The Dimensions page opens.

3. Click the name of the dimension for which you want to view dimension values. The Properties page opens.

4. Click View Data. The Dimension Data page opens and displays the current dimension values.

Creating Dimensions

To specify a dimension:

1. In the Admin Console, click Modeling to open the Modeling page.

2. Click Dimensions to open the Dimensions page.

3. In the Dimensions page, click Create to open the Create Dimension Wizard.

4. Follow the steps through the Create Dimension Wizard. If you need help using a wizard page, then click the Help link on that page.

Note that once a dimension is created, it can neither be modified nor deleted.

Adding Dimension Values

Oracle BPEL Process Analytics provides two methods for adding dimension values. One method enables you to add dimension values one set at a time, the other method enables you to bulk load dimension values.

• To add dimension values one set at a time:

  1. In the Admin Console, click Modeling.

  2. Click Dimensions. The Dimensions page opens.

  3. Click the name of the dimension for which you want to add dimension values. The Properties page opens.

  4. Click View Data. The Dimension Data page opens and displays the current dimension values.

  5. Click Add. The Dimension Data page reopens and displays a table of columns and values.

  6. Enter the desired column values, then click Submit.

• To bulk load dimension values:

  1. In the Admin Console, click Modeling.

  2. Click Dimensions to open the Dimensions page.

  3. Click the name of a dimension for which you want to specify values. The Dimension Properties page opens.

  4. Click Prepare New Data. The Dimension Data page opens.

  5. Enter the new dimensional data, and then click Submit. An informational message is presented.

  6. Click Done.

  7. Click Process Prepared Data to generate a SQL*Loader file from the dimension data you prepared. The Dimension Data page opens to display a list of SQL *Loader files.

  8. At the command line (outside of the Oracle BPEL Process Analytics Console), run SQL*Loader to load the target data into the BAM schema.

     Suppose the following, for example:

     This page shows the following values:

     • Dimension: CarMakeModel

     • Control File: C:\OraHome3\integration\bam\config\data\dim_CarMakeModel.ctl

     • Data File: C:\OraHome3\integration\bam\config\data\dim_CarMakeModel.dat

     • The database in which the BAM schema is located is db1.

     The SQL*Loader command to load the data is:

     sqlldr CONTROL=dim_CarMakeModel.ctl, DATA=dim_CarMakeModel.dat USERID=bam/bam@db1
     
     

Specifying and Loading Dimension Values

To specify and load values for a dimension:

See "Defining Key Performance Indicator Target Values" for an example of using SQL*Loader to load data into the BAM schema.

See Oracle Database Utilities for more information about using SQL*Loader.

Viewing User Accounts

To view existing user accounts:

1. In the Admin Console, click User to open the User page.

2. Click the pencil icon corresponding to the desired user to view the user information and gain access to the other property pages you can view for the user:

   • Click Properties to view the privileges assigned to the user.

   • Click KPIs to view the KPIs assigned to the user.

   • Click Metrics to view the metrics assigned to the user.

   • Click Alerts to view the alerts created for the user.

   • Click Delivery Channels to view the methods by which alerts are currently designed to be delivered to the user.

3. Click OK when you are finished reviewing the properties for the selected user account.

Creating User Accounts

To create a user account:

1. In the Admin Console, click User to open the User page.

2. Click Create User to open the Create User Wizard.

3. Follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

Modifying User Accounts

To update an existing user account:

1. In the Admin Console, click User.

2. Click the pencil icon associated with the user account that you want to modify.

3. By clicking one of the following links, you can modify some of the attributes associated with the user:

   • Properties

     See "Modifying a User's Account Password or Privileges" for information.

   • KPIs

     See "Modifying Key Performance Indicators Assigned to a User" for information.

   • Metrics

     See "Modifying Metrics Assigned to a User" for information.

   • Alerts

     See "Modifying Alerts Assigned to a User" for information.

   • Alert Delivery Channels

     See "Modifying the Alert Delivery Channels Assigned to a User" for information.

Modifying a User's Account Password or Privileges

To modify a user's account password or privileges:

1. In the Admin Console, click User.

2. Click the pencil icon corresponding to the user that you want to update. The Edit User: Properties page opens.

3. In the New Password and Confirm Password fields, enter the new password.

4. Select Admin User or Normal User, as desired to specify the privilege.

5. Click Update.

A user for whom you have modified the account password will not be able to log in using this password until you change the JAAS Provider password. See "User Management for Oracle BPEL Process Analytics Console Access" for more information.

Understanding Key Performance Indicator Performance Bands

By default, when you create a KPI, its performance bands are defined, using the NormalBenefitsBand template, which is defined as follows:

• Weak performer: 50% or more below the target value (exclusive)

• Under performer: Between 50% to 20% below the target value (inclusive)

• Normal: Within 20% of the target value (exclusive)

• Over performer: Between 20% and 50% above the target value (inclusive)

• Strong performer: 50% or more above the target value (exclusive)

Oracle BPEL Process Analytics provides templates for six performance bands, all of which you can modify, if desired.

You specify custom KPI performance bands when you create or modify a user account, rather than when the KPI is modeled, because different users may have different definitions of what constitutes a weak, under, normal, over, and strong performer for the same KPI.

Defining target values and KPI performance bands enables you to configure radar charts, gauges, and cause/effect tables in the Dashboard. See Figure 1-5 for an example of a radar chart. See Figure 4-22 for an example of a cause/effect table.

Modifying Key Performance Indicators Assigned to a User

To modify the KPIs assigned to a user:

1. In the Admin Console, click User.

2. Click the pencil icon corresponding to the user that you want to update. The Properties page opens.

3. Click KPIs to open the KPIs page.

4. On the KPIs page, you can either add a KPI to the user, or remove an existing KPI assigned to the user, as follows:

   • To add a KPI to the user:

     Click Add KPI to open the Add KPI for User Wizard, then follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

   • To remove a KPI from the user:

     Click the trash can icon corresponding to the KPI that you want to remove, and then review the other objects that will be deleted if you delete this KPI. Click Yes in the confirmation page to commit the delete operation; click No to cancel it.

Modifying Metrics Assigned to a User

To modify the metrics assigned to a user:

1. In the Admin Console, click User.

2. Click the pencil icon corresponding to the user that you want to update. The Properties page opens.

3. Click Metrics to open the Edit User: Metrics page.

4. On the Metrics page, you can either add a metric to the user, or delete a metric currently assigned to the user, as described in the following list. You cannot modify the definition of a metric assigned to the user.

   • To add a metric to the user:

     Click Add Metrics to open the Metrics page, select the metrics that you want to associate with the user, click Apply, then click OK.

   • To remove a metric from the user:

     Click the trash can icon corresponding to with the metric that you want to remove, and then review the other objects that will be removed from the user if you remove this metric. Click Yes in the confirmation page to commit the operation; click No to cancel it.

Modifying Alerts Assigned to a User

To modify the alerts assigned to a user:

1. In the Admin Console, click User.

2. Click the pencil icon corresponding to the user that you want to update. The Properties page opens.

3. Click Alerts to open the Alerts page.

4. On the Alerts page, you can add an alert to the user, modify an existing alert assigned to the user, or remove an alert currently assigned to the user, as follows:

   • To add an alert to the user:

     Click Add Alert, and then follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

   • To modify an alert assigned to a user:

     Click the pencil icon corresponding to the alert you want to modify, and then follow the steps through the wizard. If you need help using a wizard page, then click the Help link on that page.

   • To remove an alert assigned to a user:

     Click the trash can icon corresponding to the alert that you want to remove. A confirmation page opens. Click Yes in the confirmation page to commit the remove operation; click No to cancel it.

Modifying the Alert Delivery Channels Assigned to a User

To modify the alert delivery channels assigned to a user:

1. In the Admin Console, click User.

2. Click the pencil icon corresponding to the user that you want to update. The Properties page opens.

3. Click Delivery Channels to open the Delivery Channels page.

4. Click the pencil icon corresponding to the delivery channel that you want to modify to open the Update Delivery Channel page.

5. Update the Description field, if desired.

6. Update the delivery channel parameters, if desired.

7. Click Submit.

There is no strict format for specifying delivery channels that include a number, such as a phone number. You can use any of the following characters:

• Integers between 0 and 9, inclusive

• Space

• Dash (-)

• Parentheses ( )

• Plus sign (+)

Deleting User Accounts

If a user account is no longer needed, you can delete it.

To delete a user account:

1. In the Admin Console, click User.

2. Click the trash can icon that corresponds to with the user account that you want to delete.

3. Review the additional objects, if any that will be deleted if you delete this user account.

4. Click Yes to confirm the delete operation, click No to cancel it.

5. Click Submit.