Installation
Before you install the software, make sure you meet the following requirements:
You have at least a few GB of storage for
Server
data.Your networking environment does not block TCP connections between components.
Server
There are two packages available for installation: flopsar-server-X.Y.Z.deb
and flopsar-server-X.Y.Z.rpm
. For Debian based distributions you can install it by executing the following command:
For Red Hat based distributions you can install it by executing one of the following commands:
You will not be able to run Flopsar unless you accept the Flopsar End User License Agreement (EULA). In order to accept the license, you have to set the environment variable FLOPSAR_EULA_ACCEPT
to YES
.
You can verify if the Flopsar has been installed successfully by executing the command:
You should see the Flopsar banner similar to the one below:
For either standalone
or manager
modes you must have a valid license file inside your environment directory. For database
mode, the license file is not required.
Installation Example
In this example, we use the standalone architecture.
Create a new environment:
Copy the license file:
Accept the EULA:
Start the server:
Agent
In order to install Agent
, follow carefully the instructions below:
copy the agent file
flopsar-agent-X.Y.Z.jar
to your server machine.create a directory (we call this directory as Flopsar home directory) and
ext
subdirectory for the agent data.configure the agent.
optionally put all your agent plugins into the
ext
directory.restart your application.
When the agent starts for the first time it does not have any configuration deployed. It just registers itself to the manager, after a successful connection, and does not instrument anything.
Installation Example
In this example we assume there is already a Server
instance running and listening on A.B.C.D:port
socket address.
Create a Flopsar home directory along with the
ext
directory:Copy the agent file:
Copy some plugins:
Update JVM start options:
Restart your application. If the installation was successful, a log file
/opt/flopsar/MyApp.0.log
should appear.
Last updated