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

SQL Source Properties

When you create an SQL 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 SQL 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 SQL Source .
Connection	Select the connection name to which you want to associate the source. You must create a JDBC connection before you create an SQL source.
Topic	The topic to which the RulePoint posts the events. Select the topic name that corresponds to the source.
SQL	The SQL query to run against the target database. Use double angle brackets (chevrons) surrounded column names (<<column name>>) to identify the substitution parameters in the SQL statement. Each column name becomes a topic property. The topic property name is the SQL column name and the topic property value is the SQL column value.
Update SQL	Optional. You can run the UPDATE statement for each record extracted from the query and published to RulePoint. You can parameterize the SQL statement with SQL query column names.
Transaction Size	The frequency to update the parameters with data from the most recently processed records. The frequency is measured in numbers. When you input a SQL UPDATE statement, the transaction size is the number of UPDATE statement invocations allotted for each transaction based on the number of records published. An SQL source calls an update query as per the specified transaction size. You can set the following transaction sizes: 0. Update query is called at the end of the publish cycle. 'n' (1 <= n < Number of records). Update query is called after every n events published by the source. 'n' (n >= Number of records). Update query is called at the end of the publish cycle.
Buffer Result	It determines whether to maintain a buffer of the result sets to publish to the topic. Used only when defining a SQL source service. Select from the following options: Yes to publish each event separately. No to publish all events from the result set at the same time. The default is No.
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 .
Parameters	Optional. The parameters to use in the SQL query. Enter the parameters separated by comma. Parameters are a set of name value pairs to substitute as values to the parameters in the SQL query. The field has values if the SQL query has parameters. Parameters sent to the SQL query are empty strings for empty fields.
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

SQL Source Properties

SQL Source Properties