| Oracle® Business Activity Monitoring Architect User's Guide 10g (10.1.3.1.0) Part Number B28992-01 |
|
|
View PDF |
| Oracle® Business Activity Monitoring Architect User's Guide 10g (10.1.3.1.0) Part Number B28992-01 |
|
|
View PDF |
This chapter contains the information needed to create and manage data objects, including assigning permissions, managing folders, creating security filters, and adding dimensions and hierarchies.
This chapter contains the following topics:
This section contains the folowing topics:
Data objects contain the information that displays in reports created in Active Studio. You can design data objects to be used in certain types of views such as KPIs, gauges, or columnar reports.
The data objects you define are based on the types of data available from enterprise message sources. You must define fields in the data object. The data object contains no data when you create it. You must load or stream data into data objects using Plans.
When a data object is viewed while creating a report in Active Studio, the data object fields are displayed in alphabetical order regardless of the order that fields were added to the data object.
WARNING:
Do not read or manipulate data directly in the database. All access to data must be done using Architect or the ADC API.
To define a data object:
Select Data Objects from the Architect function list.
Click Create Data Object.
Enter a name for the data object.
Enter the path to the location in the folder tree where the data object will be stored. Click Browse to use the Select a Folder dialog.
Optionally, enter a description of the data object.
If this data object will be using an External Data Source select the checkbox and configure the following:
Select an External Data Source from the list. External Data Sources are configured on the External Data Sources screen. See Chapter 4, "External Data Sources" for more information.
Enter the External Table Name.
Add fields to the data object using the Add a field or Add one or more lookup fields options.
See "Adding Fields" and "Adding Lookup Fields" for more information.
Click Create Data Object when you are finished adding fields or lookup fields.
To add fields to a data object:
In a data object you are creating or editing, click Add a field.
Specify the field name, data type, maximum size (scale for decimal fields), whether or not it is nullable, whether or not it is public, and tip text.
If you are adding a field in a data object based on an External Data Source you must also supply the External field name.
The data types include:
String. Text fields containing a sequence of characters.
Integer. Numeric fields containing whole numbers from -2,147,483,648 to 2,147,483,648.
Float. Double-precision floating point numbers.
Decimal. Integers including decimal points with scale number defined, containing up to 17 digits. The number is stored as a string which uses a character for each digit in the value.
DateTime. Dates and times combined as a real number.
Boolean. Boolean fields with true or false values.
Auto-incrementing integer. Automatically incremented integer field.
Timestamp. Date time stamp generated to milliseconds. See "Adding Time Stamp Fields" for more information.
Calculated. Calculated field generated by an expression and saved as another data type. See "Adding Calculated Fields" for more information.
Keep adding fields using Add a field and Add one or more lookup fields until all the required fields are listed. Click Remove to remove a field in the data object.
Click Save changes.
You can add lookup fields to a data object. This performs lookups on key fields in a specified data object to return fields to the current data object. You can match multiple fields and return multiple lookup fields.
To add a lookup field to a data object:
In a data object you are creating or editing, click Add one or more lookup fields.
The Define Lookup Field dialog displays.
Select the data object to use for the lookup.
Select the lookup fields from the data object. You can select one or more fields by holding down the Shift or Control key when selecting. Selecting multiple fields will create multiple lookup fields in the data object. These are the fields you want to return.
Select the field to match from the lookup data object.
Select the field to match from the current data object. You must have already created other fields in this data object so that you have a field to select.
Click Add.
The matched field names are displayed in the list. You can click Remove to remove any matched pairs you create.
You can repeat steps 4 through 6 to create multiple matched fields. This is also known as a composite key.
Click OK to save your changes and close the dialog.
The new lookup fields are added to the data object. Click Modify Lookup Field to make changes to a lookup field. Multiple selection of return fields is possible when defining a new lookup but not when modifying an existing one.
You can click Remove to remove any lookups you create.
Note:
Oracle Business Activity Monitoring supports two types of schema models: unrelated tables or Star Schemas. Any other kind of schema that does not conform to these models may result in performance issues or deadlocks. Snowflake dimensions (daisy-chained lookups) are not supported.Supported:
Table 1 (with no lookups to any other tables) Table 1 > Lookup > Table 2
Not supported:
Table 1 > Lookup > Table 2 > Lookup > Table 3
When creating calculated fields in a data object you can use the operators and functions shown in the following tables combined with field names to produce a new field.
WARNING:
If you enter a calculated field with incorrect syntax in a data object, you could lose the data object definition.
Table 2-1 Describes the operators you can use to build calculated fields.
This section provides the syntax and examples for expressions you can use in a calculated field.
returns the average of all values for the given field. Avg can accept one field parameter of type Integer, Float, or Decimal.
Syntax:
Avg(Number)
Example:
Avg(Revenue)
returns the largest integer greater than or equal to the value of the specified value. Ceiling(2.9) returns 3 and Ceiling(-2.3) returns -2. Ceiling can accept one field parameter of type Integer, Float, or Decimal or a numeric value may be entered.
Syntax:
Ceiling(Number)
Examples:
Ceiling(Total) Cieling(3.7)
concatenates two strings into one. Concat can accept two field parameters of type String, or string values may be entered.
Syntax:
Concat(String,String)
Example:
Concat(Description," overstock")
returns a count of all non-null values. Count can accept one field parameter of any type.
Syntax:
Count(Field)
Example:
Count(SaleComplete)
returns a count of distinct values in a field. CountDistinct can accept one field parameter of any type.
Syntax:
CountDistinct(Field)
Example:
CountDistinct(Salesperson)
adds an offset to the field value. The first parameter for DateAdd must be a field of type DateTime, and the last seven parameters maybe a field of type Integer or an integer value. Zeros may be used where no offset is needed.
Syntax:
DateAdd(DateTime, Years, Months, Days, Hours, Minutes, Seconds, Milliseconds)
Example:
DateAdd({Last Modified}, 0, 0, 7, 0, 0, 0, 0)
//adds 7 days to the Last Modified value
DateAdd({Last Modified}, 0, 0, DaysToFollowup, 0, 0, 0, 0)
//adds DaysToFolowup number of days to the Last Modified value
returns the day name for a date. DayName accepts one field parameter of type DateTime.
Syntax:
DayName(DateTime)
Example:
DayName({Last Modified})
returns the day of the month for a date, in the range 1 to 31. DayOfMonth accepts one field parameter of type DateTime.
Syntax:
DayOfMonth(DateTime)
Example:
DayOfMonth({Last Modified})
returns the day of the week for a date, in the range 1 to 7. DayOfWeek accepts one field parameter of type DateTime.
Syntax:
DayOfWeek(DateTime)
Example:
DayOfWeek({Last Modified})
returns the day of the year for a date, in the range 1 to 366. DayOfYear accepts one field parameter of type DateTime.
Syntax:
DayOfWeek(DateTime)
Example:
DayOfWeek({Last Modified})
returns the largest integer less than or equal to the value of the specified field. Floor(2.9) returns 2 and Floor(-2.3) returns -3. Floor can accept one field parameter of type Integer, Float, or Decimal or a numeric value may be entered.
Syntax:
Floor(Number)
Examples:
Floor(Sales) Floor(46.75)
returns the hour value in the range 0-23. Hour accepts one field parameter of type DateTime.
Syntax:
Hour(DateTime)
Example:
Hour({Last Modified})
creates an If-Then-Else statement. If can accept fields, expressions, and values of any type as parameters.
Syntax:
If(x) Then(y) Else(z)
Example:
If(Sum(Quantity) > Max(Total)) Then(1) Else(2)
returns a specified value, y, if the test value, x, is null. IfNull accepts two parameters that can be fields of any type or values of any type.
Syntax:
IfNull(x,y)
Example:
IfNull(Quantity, 0)
returns the length of the string. Length accepts one parameter that can be a field of type String, a string value in quotes, or an expression containing strings or fields of type String.
Syntax:
Length(String)
Example:
Length(Description)
Length("string")
Length(Concat(Description,"Description"))
converts the string to lowercase letters. Lower accepts one parameter that can be a field of type String, a string value in quotes, or an expression containing strings or fields of type String.
Syntax:
Lower(String)
Example:
Lower(Description)
Lower("Description")
Lower(Concat(Description,"Description"))
returns the maximum value of the specified field or expression. Max accepts one field parameter of any type, or another valid expression.
Syntax:
Max(x)
Example:
Max(Quantity) Max(Concat(Description," overstock"))
returns the minimum value of the specified field or expression. Min accepts one field parameter of any type, or another valid expression.
Syntax:
Min(x)
Example:
Min(Quantity) Min(Concat(Description," overstock"))
returns the minute value in the range 0-59. Minute accepts one field parameter of type DateTime.
Syntax:
Minute(DateTime)
Example:
Minute({Last Modified})
returns the month value for a date in the range 1-12. Month accepts one field parameter of type DateTime.
Syntax:
Month(DateTime)
Example:
Month({Last Modified})
returns the month name for a date. MonthName accepts one field parameter of type DateTime.
Syntax:
MonthName(DateTime)
Example:
MonthName({Last Modified})
returns the current date and time. Now does not accept any parameters.
Syntax:
Now()
Example:
DateAdd(Now(), 0, 0, 7, 0, 0, 0, 0)
returns the percent the value represents of the total values for the specified field. PercentOfTotal accepts one field parameter of type Integer, Float, or Decimal.
Syntax:
PercentOfTotal(Number)
Example:
PercentOfTotal(Quantity)
.returns one value, x, raised to the power of the second value, y. Power accepts two parameters that can be fields of type Integer, Float, or Decimal, or they can be numeric values.
Syntax:
Power(Number,Number)
Example:
Power(Quantity, 2)
returns the quarter value in the range 1-4. Quarter accepts one field parameter of type DateTime.
Syntax:
Quarter(DateTime)
Example:
Quarter({Last Modified})
repeats a string for the specified number of times. Repeat accepts two parameter, the first of which may be a string value or a field of type String, the second of which may be an integer value or a field of type Integer. Either parameter can use an expression that returns a string for the first parameter and an integer for the second value.
Syntax:
Repeat(String,Integer)
Example:
Repeat("string", 5)
Repeat(Description, 2)
Repeat(Description, Quantity)
Repeat(Concat(Description," overstock"),Quantity+2)
returns a string, x, with all occurrences of the string, y, replaced by the string z. Replace accepts three field parameters of type String, or string values.
Syntax:
Replace(String,String,String)
Example:
Replace(Description, "ing", "tion")
rounds the specified value in the first paraemter to the number of decimal places specified in the second parameter, rounding up if the number in the N+1 decimal place is 5 or greater, and rounding down otherwise. Round accepts two parameters that can be fields of type Integer, Float, or Decimal, or numeric values.
Syntax:
Round(Number,N)
Example:
Round(Sales,2)
In this example, if Sales value is 12.345, it will be rounded to 12.35.
returns the second value in the range 0-59. Second accepts one field parameter of type DateTime.
Syntax:
Second(DateTime)
Example:
Second({Last Modified})
returns a substring z characters long from string x, starting at position y. Substring requires three parameters, the first of which must be a string value, or a field of type String, and the second and third of which must be an integer or field of type Integer.
Syntax:
Substring(String,Integer,Integer)
Example:
Substring(Description, 3, 5)
returns a summation of all values for the specified field. Sum accepts one field parameter of type Integer, Float, or Decimal.
Syntax:
Sum(Number)
Example:
Sum(Total)
creates a Switch statement. Switch can accept fields, expressions, and values of any type as parameters.
Syntax:
Switch(w) Case(x):(y) Default(z)
Example:
trims the whitespace characters (space, tab, carriage return, line feed, page feed, form feed, and so on) from the end of the string. TrimEnd accepts one field parameter of type String. You can also enter an expression that returns a string value.
Syntax:
TrimEnd(String)
Example:
TrimEnd(Description) TrimEnd(Concat(Description,Subcategory))
trims the whitespace characters (space, tab, carriage return, line feed, page feed, form feed, and so on) from the beginning of the string. TrimStart accepts one field parameter of type String. You can also enter an expression that returns a string value.
Syntax:
TrimStart(String)
Example:
TrimStart(Description) TrimStart(Concat(Description,Subcategory))
converts a string to uppercase letters. Upper accepts one parameter of type String. You can also enter an expression that returns a string value.
Syntax:
Upper(String)
Example:
Upper({License Plate Number})
returns the week for a DateTime value, in the range 0 to 53, since there might be the beginning of a week 53, where Sunday is the first day of the week. Week 1 is the first week with a Sunday in this year.
For example, in the year 2006, January 1st is a Sunday, so there is no week 0. The year starts with week 1 and continues to week 53. Week 53 of 2006 includes only one day, which is December 31st (also a Sunday). The Monday through Saturday following this (January 1-6 of 2007) are in week 0 of 2007.
Syntax:
Week(DateTime)
Example:
Week({Last Modified})
You can add permissions for users and groups on data objects. When users have at least a read permissions on a data object they can choose the data object when creating reports.
To add permissions a data object:
Select Data Objects from the Architect function list.
Select the data object.
The general information for the data object displays in the right frame.
Click Permissions.
Click Edit Permissions.
Alternatively you can copy permissions from another data object. See "Copying Permissions from Other Data Objects" for more information.
Click the Restrict access to Data Object to certain users or groups checkbox.
The list of users and groups and permissions displays.
You can choose to display the following by clicking the radio buttons:
Show all users and groups
Show only users and groups with permissions
Show users only
Show groups only
You can set permissions for the entire list by clicking the buttons at the top of the list. The permissions are Read, Update, and Delete. You can set permissions for individual users or groups in the list by clicking the checkbox in the permission column that is next to the user or group name.
After indicating the permissions with selected checkboxes, click Save changes.
A message displays to confirm that your changes are saved.
Click Continue to display the actions for the data object.
Users assigned to the Administrator role have access to all data objects. The Administrator role overrides the data object permissions.
To add a group to the list:
Click Add a group to the list.
Type the Windows group name in the field. The group must already exist as a domain group.
Click OK.
The group is added to the list.
You can copy the permissions from another data object and then make additional changes to the permissions before saving.
In Architect for a data object, click Permissions and then click Copy from. Select the data object that contains the permissions to copy and click OK. You can edit the copied permissions and click Save changes.
To copy permissions from another data object:
Select Data Objects from the Architect function list.
Click the data object to add a security filter to.
The general information for the data object displays in the right frame.
Click Permissions.
Click Copy from.
The Choose Data Object dialog displays.
Select the data object that contains the permissions to copy and click OK.
If the data object previously had no permissions assigned, select the Restrict access to Data Object checkbox.
You can edit the copied permissions or add a group to the list.
Click Save changes.
This section describes how to view information about data objects. It contains the following topics:
The general information of a data object displays the owner, when it was created, when it was last modified, and a row count.
To view the general information of a data object:
Click the data object in the list.
If you are already viewing the layout or contents of a data object, click General.
The general information displays in the right frame. It contains the following information:
Created. Date and time the data object was created.
Last modified. Date and time the data object was last modified.
Row count. Numbers of rows of data in the data object.
Location.
Type.
Data Object ID. The ID used to identify the data object. This is based on the name although the ID is used throughout the system so that you can edit the name without affecting any dependencies.
Note:
If the row count is over 500,000 rows, an approximate row count is displayed in the General information for increased performance purposes. The approximate row count is accurate within 5-10% of the actual count. If you want to view an exact row count instead of the approximation, click Show exact count. The exact count is displayed. This could take a few minutes if the data object has millions of rows.The layout describes the fields in a data object. The fields are described by name, field ID, data type, maximum length allowed, scale, nullable, public, calculated, text tip, and lookup.
To view the layout of a data object:
Select the data object.
The general information displays in the right frame.
Click Layout.
The layout information displays in the right frame. It contains the following information:
Field name. Name of the field
Field ID. Generated by the system
External name. External field name from the External Data Source (only appears in data objects based on External Data Sources)
Field type. Data type of the field
Max length. Maximum number of characters allowed in field value
Scale. Number of digits on the right side of the decimal point
Nullable. Whether or not the data type can contain null values
Public. This setting determines whether or not the field will be available in Active Studio to use in a report. If the box is unchecked, the field will not appear in Active Studio. This is useful for including fields for calculations in data objects that should not appear in reports.
Lookup. Displays specifics of a lookup field
Calculated. Displays the expression of a calculated field
Tip Text. Helpful information about the field
You can view the rows of data stored in a data object by viewing the data object contents. You can also edit the contents of the data object.
To view the contents of a data object:
Select the data object.
The general information displays in the right frame.
Click Contents.
The first 50 rows of the data object display in the right frame.
Click Next, Previous, First, and Last to navigate to other rows of data displayed 50 at a time.
Rows are listed with a Row ID column. Displaying only Row ID provides faster paging for large data objects. Row IDs are assigned once in each row and maintain a continuous row count when you clear and reload a data object.
You can click Show row numbers to display an additional column containing a current row count starting at 1. Click No row numbers to hide the row count column again.
Click Refresh to get the latest available contents.
This section contains the following topics:
You can organize data objects by creating folders and subfolders for them. When you create a folder for data objects, you can assign permissions by associating users and actions with the folder.
You can create new folders for organizing data objects. Then you can move or create data objects into separate folders for different purposes or users. After creating folders, you can set folder permissions to limit which users can view the data objects it contains.
To create a new folder:
Select Data Objects from the Architect function list.
The current data object folders display in a tree hierarchy.
Click Create subfolder.
A field for naming the new folder displays.
Enter a name for the folder and click Create folder.
The folder is created as a subfolder under the Data Objects folder and a message displays confirming that the new folder was created.
Click Continue to view the folder.
To open a folder:
Expand the tree of folders by clicking the + (plus sign) next to the Data Objects folder.
The System subfolders contain data objects for running Oracle Business Activity Monitoring. For more information about these data objects see "System Data Objects".
Click the link next to a folder to open it.
The folder is opened, and the data objects in the folder are shown in the list underneath the folder tree. The general properties for the folder display in the right frame and the following links apply to the current folder:
View. Displays the general properties of this folder such as name, date created, date last modified, user who last modified it. View is selected when you first click a folder.
Create subfolder. Creates another folder within the selected folder.
Delete. Removes the selected folder and all the data objects it contains.
Rename. Changes the folder name.
Move. Moves this folder to a new location, for example, as a subfolder under another folder.
Permissions. Sets permissions on this folder.
Create Data Object. Creates a data object in this folder.
When you create a folder, you can set permissions on it so that other users can access the data objects contained in the folder.
To set permissions on a folder:
In the Data Objects folder, select the folder to change permissions on.
Click Permissions.
Click Edit permissions.
Select the Restrict access to Data Object to certain users or groups checkbox.
The list of users and groups and permissions displays.
You can choose to display the following by selecting one of the radio buttons:
Show all users and groups
Show only users and groups with permissions
Show users only
Show groups only
You can set permissions for the entire list by clicking the column headers at the top of the list. The permissions are Read, Update, and Delete. You can set permissions for individual users or groups in the list by selecting the checkbox in the permission column that is next to the user or group name.
After indicating the permissions with selected checkboxes, click Save changes.
A message displays to confirm that your changes are saved.
Click Continue to display the actions for the data object.
To add a group to the list:
Click the Add a group to the list link.
Type the Windows group name in the field. The group must already exist as a domain group.
Click OK.
The group is added to the list.
To move a folder:
Select the folder to move.
Click Move.
Click Browse to select the new location for the folder.
Click OK to close the dialog.
Click Move folder.
The folder is moved.
Click Continue.
To rename a folder:
Select the folder to rename.
Click Rename.
Enter a new name and click Rename folder.
The folder is renamed. You must assign unique folder names within a containing folder.
Click Continue.
When you delete a folder, you also delete all of the data objects in the folder.
To delete a folder:
Select the folder to delete.
Click Delete.
A message displays to confirm that you want to delete the folder and all of its contents.
Click OK.
The folder is deleted.
Click Continue.
You can add security filters to data objects so that only specific users can view specific rows in the data object. This can be useful when working with data objects that contain sensitive or confidential information that is not intended for all report designers or report viewers.
Security filters perform a lookup using another data object, referred to as a security data object, containing user names or group names. Before you can add a security filter, you must create a security data object containing the user names or group names and the value in the column to allow for each user name or each group name. Security data objects cannot contain null values.
To add a security filter to a data object:
Select Data Objects from the Architect function list.
Select the data object to add a security filter to.
The general information for the data object displays in the right frame.
Select Security Filters.
If the data object includes security filters, the filter name and a plus sign displays so that you can expand and view the information.
Click Add filter.
The fields for defining the security filter display.
Enter the following information:
Name of this Security Filter. Type a name for this filter.
Security Data Object. Select the name of the security data object containing the mapped columns.
Type of identification. Select either By user or By group from the dropdown list. The security data object must already include either domain or local users or groups mapped to values in the identification column.
Identification column in Security Data Object. Select the name of the column for containing user names or group names.
Match column in Security Data Object. Select the column to match in the security data object.
Match column in this Data Object. Select the name of the column to match in this data object.
Click Add.
For example, to add a security filter to the following data object, you need a security data object containing Region information to perform the security lookup.
Example data object:
| User | Region | Sales |
|---|---|---|
| John Smith | 1 | $55,000 |
| Bob Wright | 1 | $43,000 |
| Betty Reid | 2 | $38,000 |
Security data object:
| Login | Region ID |
|---|---|
| DomainName\jsmith | 1 |
| DomainName\jsmith | 2 |
| DomainName\bwright | 1 |
| DomainName\breid | 2 |
When the bwright account views a report that accesses the data object with a security filter applied based on Region ID and Region, it is only able to access information for jsmith and bwright. It is not able to view the breid information because it is not able to view data for the same region. On the other hand, the jsmith account is set up to view data in both region 1 and 2.
You can copy security filters from another data object and apply them to the data object you are editing.
To copy security filters from another data object:
Select Data Objects from the Architect function list.
Select the data object to add a security filter to.
The general information for the data object displays in the right frame.
Select Security Filters.
If the data object includes security filters, the filter name and a plus sign displays so that you can expand and view the information.
Click Copy from.
The Choose Data Object dialog displays.
Select the data object that contains the security filters to copy and click OK.
You can make changes to the security filters by viewing the filter details and clicking Edit.
Click Save.
In Architect, you can add dimensions to data objects to define drill paths for charts in Active Studio. Dimensions contain fields in a hierarchy. When a hierarchy is selected in chart, the end user can drill down and up the hierarchy of information. When a user drills down in a chart, they can view data at more and more detailed levels within a specific value.
Hierarchies are an attribute of a dimension in a data object. Multiple dimensions can be created in each data object. Each field in a data object can belong to one dimension only. You can create and edit multiple, independent hierarchies.
To use hierarchies as drill paths in charts, the report designer must select the hierarchy to use as the drill path. To create a dimension, you must select multiple fields to save as a dimension. Then you organize the fields into a hierarchy.
An example dimension and hierarchy:
| Dimension | Hierarchy |
| Sales | Category |
| Brand | |
| Description |
To add a dimension and hierarchy:
Select Data Objects from the Architect function list.
Select the data object to add a dimension to.
The general information for the data object displays in the right frame.
Select Dimensions.
Click Add a new dimension.
Enter a dimension name.
Enter a description for the dimension.
Select the field names that you want to include in the dimension. An example is Sales, Category, Brand, and Description.
The field names are moved from the Data Objects Fields list to the Dimension Fields list to show that they are selected.
Click Save.
Click Continue.
The new dimension is listed. You must still define a hierarchy for the fields.
Click Add new hierarchy.
Enter a hierarchy name.
Enter a description for the hierarchy.
Select the field names that you want to define as attributes for the dimension. An example is Sales remains in the Dimension Field list, and you click Category, Brand, and Description to arrange them in a general to more specific order. The order that you click the fields is the order that they are listed in the Hierarchy Field list. Arrange the more general grouping field at the top of the Hierarchy Fields list and the most granular field at the bottom of the Hierarchy Fields list.
Click Save.
Click Continue.
The new hierarchy is listed. You can edit or remove hierarchies and dimensions by clicking the links. You can also continue defining multiple hierarchies for the dimension or add new dimensions to the data object.
If your dimension contains a time date data type field, you can select the time levels to include in the hierarchy.
To select time levels:
In a dimension containing a time date data type field, add a hierarchy.
Select the time date data type field. If you are editing existing time levels, click Edit Time Levels.
The Time Levels Definition dialog opens.
Click the levels to include in the hierarchy. The levels include:
Year. Year in a four digit number.
Quarter. Quarter of four quarters starting with quarter one representing January, February, March.
Month. Months one through 12, starting with January.
Week of the Year. Numbers for each week starting with January 1st.
Day of the Year. Numbers for each day of the year starting with January 1st.
Day of the Month. Numbers for each day of the month.
Day of the Week. Numbers for each day of the week, starting from Sunday to Saturday.
Hour. Numbers from one to twenty four.
Minute. Numbers from one to 60.
Second. Numbers from one to 60.
Click OK to close the dialog.
You can rename and move a data object without editing or clearing the data object. If you only want to change the data object name or description, use the Rename option.
To rename a data object:
Select Data Objects from the Architect function list.
Select the data object to rename.
The general information for the data object displays in the right frame.
Select Rename/Move.
Enter the new name, tip text, and description for the data object.
Click Save changes.
To move a data object:
Select Data Objects from the list.
Select the data object to rename.
The general information for the data object displays in the right frame.
Select Rename/Move.
Click Browse to enter the new location for the data object.
Click Save changes.
Indexes improve performance for large data objects containing many rows. Without any indexes, accessing data requires scanning all rows in a data object. Scans are inefficient for very large data objects. Indexes can help find rows with a specific value in a column. If the data object has an index for the fields requested, the information is found without having to look at all the data. Indexes are most useful for locating rows by values in columns, aggregating data, and sorting data.
You can add indexes to data objects by selecting fields to be indexed as you are creating a data object. You cannot add indexes after loading the data object unless you edit and clear the data object.
To add an index:
Select Data Objects from the Architect function list.
Click the data object to add an index to.
Select Indexes.
Click Add Index.
The Add Index dialog opens.
Enter a Name and Description for the index
Add as many fields as needed to create an index for the table.
Click a field in the list on the right to remove the field from the index.
Click OK.
The index is added and is named after the fields it contains. You can create more than one index. To remove an index you created, click Remove Index next to the Index name.
You might want to clear a data object before loading it. Clearing a data object removes the current contents without deleting the data object from the ADC.
To clear a data object:
Select Data Objects from the Architect function list.
Select the data object to clear.
The general information for the data object displays in the right frame.
Click Clear.
When deleting data objects, make sure that no Plans are accessing the data objects. You should also edit or delete reports and alerts referring to the data object that you want to delete.
To delete a data object:
Select Data Objects from the Architect function list.
Click the data object to delete.
The general information for the data object displays in the right frame.
Click Delete.
The System data objects folder contains data objects used to run Oracle Business Activity Management. You should not make any changes to these data objects, except for the following:
Custom Parameters lets you define global parameters for Action Buttons.
Action Form Templates lets you define HTML forms for Action Form views.
Chart Themes lets you add or change color themes for view formatting.
Matrix Themes lets you add or change color themes for the Matrix view.
Util Templates lets you define templates that are used by Action Form views to transform content.
For more information about matrix and color themes, Action Buttons, and Action Forms see Oracle Business Activity Monitoring Active Studio User's Guide.
