Installation
Before you install the software, make sure you meet the following requirements:
You have at least a few GB of storage for
Serverdata.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:
# dpkg -i flopsar-server-X.Y.Z.debFor Red Hat based distributions you can install it by executing one of the following commands:
# rpm -ih flopsar-server-X.Y.Z.rpm
# zypper install flopsar-server-X.Y.Z.rpm
# yum install flopsar-server-X.Y.Z.rpmYou 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:
$ flopsarYou should see the Flopsar banner similar to the one below:
*******************************************************
* ______ _ ____ _____ _____ _____ *
* | ____| | / __ \| __ \ / ____| /\ | __ \ *
* | |__ | | | | | | |__) | (___ / \ | |__) | *
* | __| | | | | | | ___/ \___ \ / /\ \ | _ / *
* | | | |___| |__| | | ____) / ____ \| | \ \ *
* |_| |______\____/|_| |_____/_/ \_\_| \_\ *
* *
*******************************************************
Version: 3.0.0
Build: 3.0.0
Released on: (release date)
Copyright (C) 2012-present by Flopsar Technology
http://flopsar.com
*******************************************************Installation Example
In this example, we use the standalone architecture.
Create a new environment:
$ flopsar init /opt/flopsar-serverCopy the license file:
$ cp license.key /opt/flopsar-server/Accept the EULA:
$ export FLOPSAR_EULA_ACCEPT=YESStart the server:
$ flopsar start /opt/flopsar-server
Agent
In order to install Agent, follow carefully the instructions below:
copy the agent file
flopsar-agent-X.Y.Z.jarto your server machine.create a directory (we call this directory as Flopsar home directory) and
extsubdirectory for the agent data.configure the agent.
optionally put all your agent plugins into the
extdirectory.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
extdirectory:$ mkdir /opt/flopsar $ mkdir /opt/flopsar/extCopy the agent file:
$ cp flopsar-agent-X.Y.Z.jar /opt/flopsar/Copy some plugins:
$ cp my-plugin.jar /opt/flopsar/ext/Update JVM start options:
-Dflopsar.id=MyApp \ -Dflopsar.home=/opt/flopsar \ -Dflopsar.manager=A.B.C.D:port \ -javaagent:/opt/flopsar/flopsar-agent-X.Y.Z.jarRestart your application. If the installation was successful, a log file
/opt/flopsar/MyApp.0.logshould appear.
Last updated