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® Premises Server 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 location event provider to it.
- Hub Base Parameters: These parameters are used to define
the event provider.
- Name*: Enter a name for the event provider.
- Description: Enter a description of the event provider.
- Related App Server ID*: Enter the IP address for the related WebSphere Application Server.
- Connectivity:
- Input
Event Conversion: Choose an input event conversion method from
the list of available methods. Input event conversion methods transform
provider-specific events into Location Awareness Services for WebSphere Premises Server internal
events. Different event providers require different conversion methods.
- Implementation Name: Location Awareness Services for WebSphere Premises Server is
the default implementation name. Select Custom to use your
own implementation name.
- Implementation Class: This value is pre-populated based
on your selection of an implementation name. This is the Java™ implementation class used for conversion.
The default class is com.ibm.atlas.event.conversion.LASEventConverter.
If
you selected Custom as the implementation name, you can enter
the name of your own implementation class. Your class must be in the was_root\lib\ext directory
on your Location Awareness Services for WebSphere Premises Server server.
- 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 Premises Server 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 Premises Server.
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 location 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 other than Custom. Select Custom to
use your own smoothing algorithm.
- Implementation Class: This value is pre-populated based
on your selection of an implementation name; however, you can modify
the value. This is the Java implementation
class used by the smoothing algorithm. The default class is com.ibm.atlas.smoothing.SmoothingMovingAverage.
Leave the field empty if you do not want to specify a smoothing algorithm.
If
you selected Custom as the implementation name, you can enter
the name of your own implementation class. Your class must reside
in the was_root\lib\ext directory
on your Location Awareness Services for WebSphere Premises Server server.
- 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.
For com.ibm.atlas.smoothing.SmoothingMovingAverage,
specify the following parameters:
- TimeSeriesLength=value - This value specifies the
amount of historical time that is taken into consideration and must
be an integer greater than 0.
- Weights=values - These values allow you to weight
past positions when calculating a new position. They must be decimal
values between 0 and 1 that are comma-separated. The sum of the values
must be 1.
For example, TimeSeriesLength=5;Weights=0.10, 0.15,
0.20, 0.25, 0.30. In this example, 5 seconds are taken into
consideration and the greatest weight is given to the most recent
second.
- Associated Areas: Select the areas you want to associate
with the transformation.
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 location event provider instance.
This can happen even if there is no longer an association between
the area and a location 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 Premises Server 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.