WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Configuring the dispatcher application

This topic describes how to configure the dispatcher application.

Before you begin
Before using the standalone dispatcher application, make sure that each location event provider is defined in the Location Event Provider portlet.
About this task

This topic explains how to configure Location Awareness Services for WebSphere® Premises Server ports to use the standalone dispatcher. When using Location Awareness Services for WebSphere Premises Server with the standalone dispatcher, not directly connected to the location event provider, you must configure a provider definition for each Location Awareness Services for WebSphere Premises Server port. These definitions must be identical except for the provider port number, which varies as specified for the dispatcher. All definitions must point to the same provider IP address, and the same areas must be assigned to all provider ports. For more information about the dispatcher, refer to Using the dispatcher.

Procedure
  1. Copy the contents of the LAS_HOME\samples\AtlasStandaloneDispatcher directory to a separate directory on your system.
  2. Make a backup of the sample Dispatcher.bat file.
  3. Edit the Dispatcher.bat file, providing the following parameters for each location event provider:
    • TagIDPosition - Specify the position of the tag ID in the input event. The default is 3.
    • Separator - This is the separator between units of information in the input event. The default is ; (a semi-colon).
    • HubIP - Specify the IP address of the machine hosting the location event provider.
    • HubPort - Specify the port number that the location event provider listens on. Typically, the port is 5117.
    • AtlasPorts - Specify a list of the ports that the dispatcher listens to. Separate each port number with a comma.
    • Logging - This parameter is optional. Specify on to enable logging or off to disable logging. By default, this parameter is set to off. If logging is enabled, the output is logged in the SysOut file. Only enable logging for debugging purposes.
    • Algorithm - This parameter is optional. Specify the dispatching algorithm that you want to use. By default, this parameter is set to MODULO.
    Note: Look over the parameters to ensure that they comply with these guidelines:
    • Parameter keywords and the predefined values are case-sensitive.
    • Keywords and values cannot contain any blank spaces.

    If you start the dispatcher without entering any parameters, a usage message is displayed. You can also enter ?, help, or h to display the usage statement. If you enter incomplete or erroneous parameters, you receive an error message.

  4. Start the dispatcher application by running the Dispatcher.bat file from a command line.
  5. Stop the dispatcher by typing stop or s from a command line.

Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.