Creating a Destination and Event Using the Wizard for AS
TIBCO Channel Wizards provide an option to create a destination and event for a specific ActiveSpaces channel.
Procedure
- In BusinessEvents Studio Explorer, select the ActiveSpaces channel for which you need to create a destination and event. From the menu, select File > New > Other > TIBCO Channel Wizards > ActiveSpaces Destination and Event and click Next.
- The Select Space dialog lists the available spaces for every ActiveSpaces channel in the project.
-
On the New SimpleEvent and Destination dialog, enter the values to configure the simple event and destination for the selected channel and space.
Configuring an ActiveSpaces Destination and Event Field Name Description Simple Event Name Name of the simple event to be created. The default name is of the format <spaceName>Event. Destination Name Name of the destination to be created. The default name on the screen is of the format <spaceName>Dest. Default Event The default event for the destination. This is set to the SimpleEvent specified to be created by the wizard. Serializer/Deserializer The serializer used to map tuples in ActiveSpaces to simple events in TIBCO BusinessEvents. The default value is com.tibco.cep.driver.as.serializers.ActiveSpacesSerializer.
See ActiveSpacesSerializer for more information.
Space Name Name of the space which the destination connects to. This space is selected in the Select space dialog. See Space for more information about spaces in TIBCO ActiveSpaces.
Distribution Role The level of participation of the space member: seeder or leech. See Distribution role for more information.
Filter String specified to evaluate tuples and refine the set of tuples to work. A filter string can be seen as what would follow the where clause in a select * from Space where… statement. See Filters for more information.
Consumption Mode Specifies the consumption mode for the ActiveSpaces event as one of: - Event Listener - listens for specific events to occur, and invokes a callback function from TIBCO ActiveSpaces.
- Entry Browser - can listen and retrive tuples from the space using the Get, Take, or Lock & Take methods.
- Router - feeds the events to only the specified listener. This way, the application benefits from having multiple listener processes running.
See Consumption mode for more information.
Browser Type Available only when the consumption mode is Entry Browser. Specifies the browser type used to retrieve tuples from a space. You can choose either Get, Take, or Lock & Take.
The difference between the Get and Take browsers is that Get retrieves a copy of the tuple from the space and Take retrieves the tuple from the space, and there is no trace of the tuple in the space after the Take event.
Using the Lock & Take option, you can acquire a lock on the tuple key. The event is consumed or taken in post-RTC ensuring successful processing of the event. The Take action does not occur if abortRtc() is called in preprocessor or rules.
Note: The lock owner is the process. Make sure the Lock Scope is defined as a process in the ActiveSpaces space definition.
DistributionScope The distribution scope for the ActiveSpaces event. This field is active only when the Consumption Mode is Event Listener or Entry Browser.
When Consumption Mode is Entry Browser, the field specifies the possible ways to browse for events in a Space based upon where entries are stored in the space. The values are:TimeScope The time scope for the ActiveSpaces event. This field is active only when the Consumption Mode is Event Listener or Entry Browser.
When Consumption Mode is Entry Browser, the field specifies the possible ways to browse for entries in a Space based upon the time at which entries were stored in the space relative to the Browser creation time. The values are:- ALL - The browser iterates through all of the entries stored in the space at creation time and continues to iterate as changes occur in the space.
- NEW - The browser skips iterating through the entries stored in the space at creation time and only iterates through new changes that occur in the space.
- SNAPSHOT - The browser only iterates through entries stored in the space at creation time.
The values when Consumption Mode is Event Listener are:- ALL - The listener starts with all of the tuples currently in the space at creation time, which will be presented as an initial site of PUT events and then is continuously updated according to changes in the space.
- NEW - The listener starts empty and is updated only with events related to new or updated tuples in the space.
- SNAPSHOT - The listener contains only PUT events corresponding to the tuples stored in the space at creation time.
- NEW_EVENTS - The listener starts empty and is updated with all of the events that occur in the space after creation time.
Put Event Available only when the consumption mode is Event Listener. When selected, the Event Listener listens for any Put events on the space and invokes a callback function when such an event occurs.
Take Event Available only when the consumption mode is Event Listener. When selected, the Event Listener listens for any Take events on the space and invokes a callback function when such an event occurs.
Expire Event Available only when the consumption mode is Event Listener. When selected, the Event Listener listens for any Expire events on the space and invokes a callback function when such an event occurs.
Prefetch Available only when the consumption mode is Entry Browser. Set the value in field to attain optimum performance. The default value is -1 (prefetch all).
- Click Finish to create the destination and the simple event.