Running event sequences
When the event sequence is complete, you can submit the event sequence to a running development server.
About this task
Running a .eseq file against a server is a quick way to validate that your solution is working as expected. Each event sequence emits an event sequence that uses the properties defined in the testdriver.properties file in the Test Client project. You can run various event sequences to the server, and you can easily modify and run the event sequence again if necessary.
You can run a single event sequence, as described in the following procedure, or you can run multiple event sequences by creating and running a test scenario.
Note: The test epoch property is set or cleared according to the first event in the test sequence.
Any previous settings of the test epoch property are overridden when the event sequence file is
run.
Procedure
- Start the development server to which you intend to deploy your event sequence. You can start cisDev from the Samples console.
- Open the Event Sequence folder in the test client project and locate the .eseq file that contains your event definitions.
- Right-click the .eseq file and click . The Run Options wizard opens the first time that you run your event sequence to the server.
- In the Test Client wizard, confirm that the test client project and event sequence are selected.
- Optional: Click Enable Recording to record the events running on the server. If you select this option, you can later review the behavior of your events in Insight Inspector.
- Optional: Click Reset Solution State to reset the rule agent history, cached engines, time triggers, pending changes, and global aggregates on your server.
- Optional: If you want to clear all existing entities from the server, select Reset Solution State and Delete all entities. If you chose this option, ensure that the entities are created during your test.
- Click Run. The event sequence is submitted to the server.