You must manually start the UAF agent for each RAP component
in order for the component to be visible
in and controlled by Operations Console.
-
Start the JINI server by changing the directory to $RAP/OpsConsole/ua/bin and running the command ./startJini.
The ./startJini script is started during the installer, and only needs to be executed if it has been shutdown.
-
Start the Operations Console by changing the directory to $RAP/OpsConsole and running the commandstartOpsConsole.sh.
The startOpsConsole.sh script is started during the installer, and only needs to be executed if it has been shutdown.
The RAPCache and RAPStore servers should already be running.
-
Start the agent for each component that you want to
see on the Operations Console. Repeat this step for each component.
-
Change directory to $RAP/<component_dir>/ua/bin
where <component_dir> is the name
of the component.
For example, <component_dir> can
be DemoFeedHandler, DemoSubscriber, FASTFeedHandler, RAPCacheSubscriber,
or RAPStoreSubscriber.
-
Run the command ./agent &
The & starts a background process that continues to run
after you exit the terminal window.
-
Start the RAPStore agent.
-
Change to the
$RAP/RAPStore/IQ-15_1directory.
-
Source the environment variables:source IQ-15_1.csh or
../IQ-15_1.sh.
-
Change to the
$RAP/RAPStore/ua/bindirectory.
-
Run:
./agent &.
-
Start the RAPCache agent.
-
Change
to the
$RAP/RAPCache/directory.
-
Source the environment variables:source SYBASE.sh.
-
Change to the
$RAP/RAPCache/UAF-2_0/bindirectory.
-
Run:
./agent &.
When you log into Operations Console, the RAP components
whose agents are running are visible.