Use this page to define the event providers for your areas
and zones.
Note: Currently location event providers are the only type of supported
event provider. Location event providers provide Location Awareness Services for WebSphere® Sensor Events with
tag location data.
Click Add to
define a new event provider or click Delete to delete an existing
provider. Click Edit to edit details for an existing event
provider.
Add new event provider
Complete the following
fields to define a new event provider.
Note: You need to have defined
an area before you can relate a event provider to it.
- Hub Base Parameters: These parameters are used to define
the event provider.
- Name*: Enter a name for the event provider.
- ID: This field is read-only. It is the internal ID used
by the simulator configuration properties or by the location events
coming from the adapter framework.
- Description: Enter a description of the event provider.
- Related App Server ID: Enter the IP address for the related WebSphere Application Server. This
field is required if you choose a connectivity type other than JMS
Gateway.
- Connectivity:
- Input
Event Conversion: If your connection type is something other than JMS
Gateway, then you can choose an input event conversion
method from the list of available methods. If JMS Gateway is
selected, the Input Event Conversion fields are not available.
Input event conversion methods transform provider-specific events
into Location Awareness Services for WebSphere Sensor Events internal
events. Different event providers require different conversion methods.
- Implementation Name: Select the name of the event conversion
implementation to use. The other fields are pre-populated when you
select an implementation name. The default implementation name is LAS for Location Awareness Services for WebSphere Sensor Events.
- Implementation Class: This value is populated based on
your selection of an implementation name. This is the Java™ implementation class used for conversion.
- Parameters: This value is pre-populated based on your selection
of an implementation name; however, you have to instantiate the template
by replacing placeholder values with valid values.
All
event converters shipped with Location Awareness Services for WebSphere Sensor Events support
the optional parameter IDPrefix=string.
This parameter can be used for making tag IDs unique across a multi-event
provider installation. The provider tag IDs are prefixed by the value
specified in the IDPrefix parameter throughout Location Awareness Services for WebSphere Sensor Events.
The com.ibm.atlas.event.conversion.LASEventConverter implementation
class supports the following parameters:
- ignoreTagIDs=name of file containing tag IDs -
For this parameter, enter the name of a file that contains tag IDs
that should be ignored.
- providerLocale=ISO-639 code - This parameter
is relevant if the actual locale is different from the default locale
and, for example, numeric values need to be converted.
Parameters in square brackets ([parameter])
in the parameter template are optional. In general, parameters are
keyword-value pairs separated by semi-colons (;).
Note: Whenever
you add real values to the parameter template, remember to remove
the square brackets.
Note: Contact your IBM® Services
representative in order to use a custom implementation.
- Transformation options: These parameters
are used to convert the coordinates returned by the event provider
into appropriate coordinates for the area, and therefore to transform
the area displayed on the Spatial Management Client.
You can shift or displace the area, change its scale, rotate it, or
juxtapose its position.
- X Offset: Enter a value to offset the area on the X-axis.
The offset value can be negative or positive and is 0.0 by
default, indicating no offset.
- Y Offset: Enter a value to offset the area on the Y-axis.
The offset value can be negative or positive and is 0.0 by
default, indicating no offset.
- Z Offset: Enter a value to offset the area on the Z-axis.
The offset value can be negative or positive and is 0.0 by
default, indicating no offset.
- Scaling: Enter a value greater than 0 to change the scale
of the area. The default value is 1.0, or no scaling.
- Horizontal Rotation: Enter a value between 0 and 360 to
rotate the area. This value specifies an angle in degrees and has
a default value of 0, or no rotation.
- X-Y Permutation: Select this box to switch the X and Y
coordinates.
- Smoothing Algorithm: No default smoothing
algorithm is selected when you create a new provider. Instead, the Implementation
Name field is pre-filled with a value of None,
indicating that no smoothing is applied.
- Implementation Name: Select the name of the smoothing algorithm
implementation to use. The other fields are pre-populated when you
select an implementation name. For example, you can choose between
the following types:
- None - The default value; no smoothing is applied.
- WeightedUpdate - The new position of a tag is calculated
based on its previous position maintained by Location Awareness Services for WebSphere Sensor Events, and
the new position is reported by the external event provider. The new
position is calculated as follows: newX = averagingFactor
* currentX + (1.0 - averagingFactor) * oldX, and similarly
for the other coordinates.
- MovingAverage - The new tag position provides position
estimates computed according to a moving average algorithm. It accepts
as properties the length of the time series on which to operate and
the weights for each element in the series. The sum of the weights
must be equal to one.
- HammingWindow - This is a special version of the MovingAverage
smooting algorithm, where the length of the time series on which to
operate is specified. The weighting of the positions is done according
to the HammingWindow algorithm.
- Implementation Class: This value is populated based on
your selection of an implementation name.
- Parameters: This value is pre-populated based on your selection
of an implementation name; however, you can modify the value. These
are the customization parameters for the smoothing algorithm. Specify
them in the keyword=value;keyword=value format.
- WeightedUpdate: AveragingFactor=0..1,
where 0..1 is replaced with a decimal i between
zero (0) and one (1), for example, 0.5.
- MovingAverage: TimeSeriesLength=n;Weights=0.x,0.x,0.x,
where n is replaced by a number greaters than one
(1), and 0.x,0.x,0.x is replaced by values between
zero (0) and one (1) which sum up to one (1). You can also specify Weights=equal,
where each position in the series is counted as the same length.
- HammingWindow: Hamming=true;TimeSeriesLength=n,
where n is replaced by a number greater than zero
(0).
- Start Options: If the Auto-start box is selected,
communication with the RTLS system behind the event provider definition
is started automatically as soon as WebSphere Application Server is
started.
Note: If communication with the RTLS system is through an
external adapter, this adapter has to be up and running at this time.
Otherwise, communication with the RTLS system cannot start.
- Associated Areas: Select one or more areas you want to
associate with the event provider. If no area is selected, the location
events coming from this event provider will not result in any booking
of tags to an area.
After you switch to this area in the Spatial Management Client,
you might still see tags moving around – even after you have removed
the association between an area and a event provider instance. This
can happen even if there is no longer an association between the area
and a event provider instance. An internal cleanup is made when you
delete the area; however, this strange effect cannot be suppressed
due to the manner in which Location Awareness Services for WebSphere Sensor Events internally
maintains tag-to-area associations.
Click Save to save your settings or click Cancel to
exit without saving your changes. Click Reload to refresh the
options that are available from the menus and to reset the fields
to their original state.
Note: Fields marked with an asterisk (*) are required. All other fields
are optional.