Preface
RulePoint
RulePoint Concepts
- RulePoint Concepts Overview
- Understanding RulePoint Entities
Using RulePoint
RulePoint Objects
- RulePoint Objects Overview
- State of RulePoint Objects
Working with Topics
Working with Connections
Working with Sources
Working with Responders
Working with Responses
Working with Watchlists
Working with Analytics
- Analytics Overview
- Analytic Types
- Creating an Analytic
- Copying an Analytic
- Editing an Analytic
- Deleting an Analytic
- Viewing Related Objects
- Predefined Analytics
  - abs
  - average
  - ceil
  - charat
  - clean
  - compareto
  - concat
  - confidence
  - correlation
  - count
  - current
  - date
  - datedifference
  - endswith
  - even
  - floor
  - getcurrentdate
  - getdatefrommillis
  - getdateinmillis
  - geodistance
  - geoinbound
  - geoinsidearea
  - geointersect
  - geooutbound
  - geooutsidearea
  - geopassthru
  - indexof
  - integer
  - isblank
  - isholiday
  - isnum
  - istext
  - isweekday
  - isweekend
  - large
  - list2vars
  - lower
  - max
  - min
  - mod
  - mode
  - mround
  - odd
  - parse
  - past
  - percentile
  - power
  - proper
  - range
  - regex
  - replace
  - round
  - rounddown
  - roundup
  - sign
  - small
  - startswith
  - stdev
  - stringequals
  - stringindexof
  - stringlastindexof
  - stringlength
  - substring
  - sum
  - trim
  - truncate
  - upper
  - xpath
- Predefined Operators
  - contains
  - equalsSet
  - has
  - in
  - match
  - notMatch
  - search
  - unique
  - group by
  - distinct
  - unmatched
- Using the distinct, group by, and ummatched Filters
DRQL
Working with Rules
Working with Alerts
Setting Access Controls
Troubleshooting RulePoint Issues
Connecting to an Ultra Messaging Application
Creating an Ultra Messaging JMS Source

User Guide

6.1.2
- 6.2
- 6.1

Back Next

Event Generator Source Properties

When you create an Event Generator source, you enter the name and the configuration details for the source through the RulePoint user interface.

The following table describes the configuration properties of an Event Generator source:

Property	Description
Name	Name of the source. The source name must be unique.
Description	Optional. The description of the service. Make the description intuitive so that other users can relate to the use of this service.
Type	Type of source. Select Event Generator .
Topic	The topic to which RulePoint posts the events. Select the topic name that corresponds to the source. You can attach multiple topics to an event generator source. An event is read from the input event file, and the source publishes the event to only those of the attached topics that are listed in the event.
Date Format	The format used to parse the date and time. You can parse the date format if an event in the generator file specifies that you must include the CURRENTTIME , CURRENTDATE , or CURRENTTIMESTAMP function as a property in a generated event. The default format uses the Java API date format specified in the user preferences. The RulePoint default date format is EEE, d MMM yyyy HH:mm:ss Z .
Rate	The number of events posted to the topic as a single block of events. Default is 1.
Iterations	The number of times to publish the file before the service terminates. Default is 1. For example, if the number of iterations is two, RulePoint publishes the set of events twice before terminating the service. The generator loops over the file and feeds events from the beginning to end again for each additional iteration. For example, the file contains three events, A, B, C, and the number of iterations is two. The generator feeds the events into the system as A, B, C, A, B, C.
Delay	Optional. The number of milliseconds to delay between publishing blocks of events to the topic. Default is -1, that is, use the delay specified in the event xml file.
Post Processing Action	Disposition of event files after processing. Select one of the following options: archive files. Moves the files to the archive directory, RULEPOINT_HOME\archive . delete files. Deletes the files. do nothing. Leaves the files untouched. The default post processing action is to do nothing.
Event File or Directory	Optional. The name of the XML file that contains the simulation data. The XML data file(s) must conform to the RulePoint EventGenerator XSD schema file. Place this file in the following directory path: [RulePointHome]\data If you specify a file name, RulePoint uses the file name as the source of the XML. If you specify a directory, RulePoint uses all the files in that directory. RulePoint processes the files in ascending order by file name.
Marker ID	Optional. The name to assign to the marker. This is the batch name that the sever associates with all published events. Avoid using multiple batch names as the system treats them as a single string. Specify one batch name for each source. When you configure a marker ID in the source, it demarcates a set of events between the marker_begin and the marker_end event. For more information, see "Markers" in the RulePoint Administration Guide .
Property Metadata Map	Optional. The unique name-value pairs of static metadata or additional information about this service that becomes part of the event properties. Do not use a null value for any property. Do not include space in the name of the metadata property. The name-value pairs appear in every event published by this source service. Format for Property Metadata: Name=Jane Doe, Age=10 If you input an entry that contains a delimiter, such as a comma or a semicolon, you must place the entry into a quote. Putting a numeric entry into quotes makes it a string or non numeric. You cannot do math computation with a non numeric entry.
Marshaller Class Name	Class name of the marshaller. The marshaller class is responsible for converting or enriching the source event properties. It must include the full class name including the classpath. You must add the jar containing this class into the RulePoint library.
Marshaller Properties	Properties of the marshaller. You must pass the properties as key value pairs, separated by a comma, to the marshaller class. For example, property1=value1,property2=value2.

Rename Saved Search

Table of Contents

User Guide

User Guide

Event Generator Source Properties

Event Generator Source Properties