Objects are abstract entities defined by attributes. Although objects of the same type possess a common structure and behavior, the object attributes contain data that is unique to each object. As the data values for an object vary over time, the object structure and attributes remain constant, and the object history becomes an accumulated record of these effects.
To successfully implement a business activity monitoring strategy, you must identify the objects and attributes that you want to monitor and determine any calculations you want to perform on each monitored attribute.
To analyze object structure and attributes:
Identify the objects you want to monitor.
Identify the object attributes that you want to monitor.
Typically, a total or a cumulative change to an object attribute is monitored.
Determine the calculations you want to perform on each object attribute that is monitored.
Example
An account is a commonly monitored object. It contains attributes such as an account number, account name, account type, and a numeric value measured in dollars or quantity. In this example, the business goal is to monitor the liquidity of account objects, so the numeric value representing the account balance and its associated account number are monitored.
As message transactions that affect the account object are processed, the cumulative total of the balance field represents its liquidity. Additionally, transaction messages that debit the account add to the balance, and transaction messages that credit the account subtract from the balance. Each time a message is processed that affects the cumulative balance, the monitored object is updated.
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com