C H A P T E R 3 - Distributed RFID Event Manager Environment

C H A P T E R 3

Distributed RFID Event Manager Environment

This chapter includes the following topics:

General Distributed Installation Considerations

Custom Installation

General Distributed Installation Considerations

RFID Event Manager Execution Agents communicate and gather information from the RFID Readers. A single Execution Agent is capable of controlling and collecting information from multiple RFID Readers. In a large deployment, you can install a copy of the Event Manger Execution Agent on multiple hosts in the network. Each Execution Agent can then manage and communicate with a subset of the RFID Readers. Which readers communicate with a particular Execution Agent is specified by the RFID Event Manager. Deploying multiple Execution Agents enhances the availability of the system, since each Execution Agent is capable of carrying out the workload of other Execution Agents if a particular one becomes unavailable. You use the Configuration Manager to define Configuration Objects that encapsulate how to process the data received from the readers. The Control Station provisions the Configuration Objects to the Execution Agents as units of work.

Execution Agents and their Control Station need to share a common Jini Group in order to communicate with each other. At installation time, you are asked to define a group name for your deployment. This name needs to be the same across the set of multiple Execution Agents you want to communicate with a single Control Station. Use the same name for all of your Execution Agents as you use for the Control Station. You can change the Control Station's group name after installation by invoking the Configuration Manger. The only way to change the group name for the Execution Agents is to reinstall them, so be careful when defining the group name.

Note - All of your deployment information is managed from the Control Station. No configuration information is lost by reinstalling an Execution Agent.

Custom Installation

Use Custom Installation to create distributed installations where the Execution Agent components are located on separate machines that are remote to the Control Station machine. See the Sun Java System RFID Software 2.0 Installation Guide for more information on creating a distributed installation for your RFID Software.

Distributed Installation Component Scripts

Sun Java System RFID Software includes script files designed to run or stop various software components. When a distributed installation is created, the Control Station and Execution Agents can be started separately by invoking their individual startup scripts (note that these scripts also include a "restart" option for use with their respective components). The same is true for stopping the components separately.

Note - The Control Station must be started before the Execution Agent can be started. Starting the Execution Agent when no Control Station is present results in an error. You need to stop and restart the Execution Agent after the Control Station has been started.

Starting and Stopping Control Station

If the Control Station components are installed as part of a Custom installation, the script station stored in /install_dir/bin is used.

To use the script, change to the specified directory and type one of the following, as needed:

To start the Control Station in this instance:

# station start

To stop the Control Station:

# station stop

To show the status of the Control Station:

# station status

To show the version of the Control Station:

# station version

Starting and Stopping Execution Agent

Similarly, on hosts where the Execution Agent Components are installed without the Control Station, you can find the script agent installed in /install_dir/bin.

To use the script, change to the specified directory and type one of the following, as needed:

To start the Execution Agent:

# agent start

To stop the Execution Agent:

# agent stop

To show the status of the Execution Agent:

# agent status