El desconocimiento como síntoma y los mediadores como ejes de periodización

You need Read and Write permission on the business activity.

Note: Deleting a business activity deletes its contained scenarios and all of the scenario’s objects.

➤ To delete a business activity:

1. Open the Scenario Modeler.

2. In the tree view, select the Business Activities folder.

3. In the list of business activities, select the activity to remove. 4. Click Delete Business Activity.

Attribute Description

Name Identifies the business activity. The name can contain letters and numerals only. This name must be unique among business activities and users; you cannot have a user with the same name as a business activity. See “Object Namespace” on page 248 for details.

Status Specifies if the business activity is enabled (receiving new event information) or

disabled. When an activity is disabled, all of the objects it contains are also disabled, including the rules, alerts, and reportlets.

43

6

Context

Context supports event processing by providing meaningful information about the event. Contexts are the business information stored in databases, data warehouses, or are provided by Web Services. Context tables receive data from Agents that know how to communicate with information sources. When you define a context table, you also instruct the agent how to identify the information from the source.

➤ In this Chapter:

● “How It Works” on page 44

● “Creating Context Tables” on page 45

● “Editing Context Tables” on page 46

● “Context Column Limitations in Queries” on page 46 ● “Caching Context Queries” on page 48

Adobe LiveCycle ES Context

Business Activity Monitoring Server Reference How It Works 44

How It Works

When a business view requires context information, it does so based on some information already in the view. For example, a view that is processing a purchase order might have received a product identification number along with the event data. If the view also requires the suppliers of that product, it would retrieve the supplier names from a context table that contains the names that matches the ID. In the view

definition, a WHERE clause would join the context table to the event, similar to the following:

WHERE event.product_id = context.suppliers_of_product_id

When the view performs this join, it passes the ID from the event to the context table. If the matching supplier data are already in the context cache, the table uses that data and passes it to the business view. If the data are not already in memory, the ID is passed — either as an SQL query or by value for a stored procedure — to an agent, which sends data to the DBMS or Web service for processing. The result of the query is then loaded into the context table and subsequently included in the business view.

The context source may be databases accessed through a JDBC or business applications accessed through

Web Services. For details about these type of sources, see “JDBC Tables” on page 217, or “Web Service Context” on page 366.

Business view

Data for query

Context Result

Context cache

Agent Event

The context table contains data that match some ID in the view. The data comes from a cache, which originally comes from some external source, such as a DBMS.

Query for the context Context source

Adobe LiveCycle ES Context

Business Activity Monitoring Server Reference Creating Context Tables 45

Creating Context Tables

Every context table has a name, description, status attribute, and agent. These are defined in the following table.

Before creating a context table, you must have Create permission for tables (see “Creating Permission” on page 258), and Read Only access permission on the agent that will feed the table.

➤ To create a context table:

1. Open the BAM Workbench tab. 2. Click New Context…

3. Choose the source type, each type has its own specific attributes. For details, see:

● “JDBC” on page 216

● “Web Services” on page 362

4. Fill in the fields in the New Context form.

Save the table as enabled and it will immediately be ready to receive context.

Attribute Description

Name Identifies the table and is the name accessed by the Business Views that depend on this table. This name must be unique among views, events, context, and consolidated events. See “Object Namespace” on page 248 for details. Description (optional) Description of the table.

Status Whether or not the object is enabled (able to receive and pass data) or disabled

(not receiving or passing data).

Agent The agent that retrieves the context information, and passes the data to the event or context object. See “Agents” on page 23 for information about agent types. Disable context

after errors

Count of consecutive errors to receive before the system disables this context. Once disabled, a context must be re-enabled manually.

Adobe LiveCycle ES Context

Business Activity Monitoring Server Reference Editing Context Tables 46

Editing Context Tables

Editing the attributes of a context table causes the object to lose state, and possibly invalidates dependant views. For example, if you remove a column, any view or rule that references that column becomes invalid. (However, if you redefine the column in the table, the dependant views are automatically revalidated.) Before editing a context table, you must have Read and Write permission for tables (see “Accessing Permissions” on page 255), and Read Only access permission on the agent that feeds the table.

➤ To edit a context table:

1. Open the BAM Workbench tab. 2. Select the event or context object. 3. Chose Edit This Context.

4. Change the definitions in the Edit Context form. Note that each type has its own specific attributes. For details, see

● “JDBC” on page 216

● “Web Services” on page 362

Save the table as enabled and it will immediately be ready to receive events or context.