Optimize 10.5 | webMethods Optimize Documentation | Administering webMethods Optimize | For Developers | Configuring and Using the Web Service Data Collector | Sending Event and Dimensional Data
 
Sending Event and Dimensional Data
 
addEvent (event) and addEvents (events)
addEventWithCallback
addStronglyTypedEvent (event) and addStronglyTypedEvents (events)
addDimension (dimension) and addDimensions (dimensions)
addStronglyTypedDimension (dimension) and addStronglyTypedDimensions (dimensions)
The recommended method for publishing monitor data into Optimize is to use the Web Service Data Collector's dimensionalData interface that is described in this section. The Web Service Data Collector contains web services for sending data as events and dimensions, where events capture metric data and dimensions capture metadata about the metric data. For more information, see Configuring KPIs.
The addEvent (event) and addEvents (events) methods pass data as event types and a list of details about the event types, presented as a series of key/value data pairs.
The following table provides an example of the metadata that the event passes.
Data
Value
Event type
OrderProcess
Key/value pairs
Revenue = 500
Customer = 9
Product = 71
OrderID = 123456
The addStronglyTypedEvent (event) and addStronglyTypedEvents (events) methods are included only for backward compatibility.
The addDimension (dimension) and addDimensions (dimensions) methods pass metadata for the event data as a dimension type, or name, and a list of details about the dimension type presented as a series of key/value data pairs.
The following table provides an example of the metadata that the event passes.
Data
Value
Dimension 1
Name
Customer
Key/value pairs
ID = 9
Name = ABC Corp
Region = Central
Dimension 2
Name
Product
Key/value pairs
ID = 71
Name = Widget
The addStronglyTypedDimension (dimension) and addStronglyTypedDimensions (dimensions) methods pass metadata for the event data as a dimension type, or name, and a list of details about the dimension type presented as a series of key/value data pairs.
The following table provides an example of the metadata that the event passes.
Data
Value
Dimension 1
Name
Customer
Pairs
ID = 9
Name = ABC Corp
Region = Central
Dimension 2
Name
Product
Pairs
ID = 71
Name = Widget
Note:
The methods of this interface use the classes contained in the bam-wsdc.jar file in the Optimize_directory/dataCollector/lib directory.