Starting UAF Agents and Plug-ins

You must manually start the UAF agent for each RAP component for the component to be visible in, and controlled by Operations Console.

  1. If the JINI server has been shut down, restart it by changing to $RAP/OpsConsole/ua/bin and running:
    ./startJini
  2. If the Operations Console has been shut down, restart it by changing to $RAP/OpsConsole and running:
    startOpsConsole.sh
    The RAPCache and RAPStore servers should already be running.
  3. For each component you want to see in the Operations Console:
    1. Change to $RAP/component_dir/ua/bin where component_dir is the name of the component.
      For example, component_dir can be demo feed handler, demo subscriber, FAST feed handler, RAPCache subscriber, or RAPStore subscriber.
    2. Run Either:
      ./agentd start
      or
      ./uafstartup.sh
      The & starts a background process that continues to run after you exit the terminal window.
  4. Start the RAPStore agent:
    1. Change to $RAP/RAPStore/IQ-15_2.
    2. Source the environment variables using either: source IQ-15_2.csh or . ./IQ-15_2.sh.
    3. Change to $RAP/RAPStore/ua/bin.
    4. You can run either:
      ./agentd start
      or
      ./uafstartup.sh
  5. Start the RAPCache agent:
    1. Change to $RAP/RAPCache/.
    2. Source the environment variables: source SYBASE.sh.
    3. Change to $RAP/RAPCache/UAF-2_5/bin.
    4. You can run either:
      ./agentd start
      or
      ./uafstartup.sh

When you log in to Operations Console, the RAP components with running agents are now visible.

Plugins at runtime are stored in ua/nodes/<nodename>/plugins. At agent startup, the UAF checks for the ua/nodes folder. If it does not exist, the UAF will create ua/nodes and copy the ua/plugins into ua/nodes/<nodename>/plugins. If ua/nodes exists, the UAF will not copy the ua/plugins into ua/nodes/<nodename>/plugins.