IceCool Event Server Documentation

Steps to run the samples

Caveat

Running the sample applications require that your computer has JDK 1.4.x installed. If you do not already have JDK 1.4 already on your computer download one from Sun's Java site .


		Make sure javac and java are in your %PATH% variable.

Extract zip file contents referred to as (install_dir), which by default is ES-1.0.

Set up quartz tables:

		 You will find database scripts for different database types under (install_dir)\samples\dbTables directory.
		 Run the the script for your database type - i.e. for oracle database, you will run the 'tables_oracle.sql' script. This will create tables that quartz needs to store your job information. Note that all quartz table names begin with _QRTZ. Do not change this.
			
	
Edit only the following properties in quartz.properties found under (install_dir)\conf. Under the section 'Configure Datasources' , change values as required to reflect properties for your database.

Modify (install_dir)\samples\es-sample.xml as required. Refer the section below on structure of es-sample.xml file

To run, edit (install_dir)\samples\run.bat to change ES_HOME variable to point to your installation of Icecool Event Server.




Structure of configuration file


The different flows consisting of different flow elements are defined. Each flow consists of atleast three flow elements (one of each type). 

Each flow element is one of 3 types: source, sink, router; that is specified by the <type> element. Also, each flow element is given a unique name within the configuration file, represented by the 'name' attribute. The name of the implementation class for that flow element is specified by the element <className>. The various other configuration settings that may be required by the class (for example database connection properties etc.) can be set as name and value attributes in different <property> elements for that flow element.

To use EventServer1.0 - change the database properties, and insert appropriate query. Optionally, the number of sources can be increased to define more queries. The database queries are scheduled to execute after regular intervals specified by the quartz Cron trigger expression (element <expression>). These expressions are strings that describe details of the schedule and are made up of six sub-expressions, that represent: Seconds, Minutes, Hours, Day-of-Month, Month, Day-of-Week respectively. For example, an expression (0/15 * * * * ?), represents a trigger that fires every 15 secs.  

Through the router flow element, one can apply the desired webmacro template for the email to be sent out; for a database event triggered. The <template> element points to the .wm template file. The source and sink for the router are specified by the 'source' and 'sink' property element values.

The sink flow element specifies properties for sending an email. The host, username and password for the network from which email will be sent is represented by the <host>, <user> and <password> elements respectively. The "to", "from" and "subject" fields of the composed email are represented by the <to>, <from>, and <subject> elements.


   

   
  
  
(c) 2005 IceCool.com