Installation - Java Linux Agent on a JBoss Application Server

JBoss Compatibility

vFunction supports RedHat JBoss 7.2 and later.

Installation Wizard

To help with the installation process, vFunction offers an Installation Wizard. This Wizard provides additional information about the Prerequisites as well as the Required and Optional Settings for installing the vFunction Server and Agents. This Wizard also walks you through each step in the Installation process.

Please contact support@vfunction.com or your vFunction Contact(s) for the password to start using this Wizard.

Installation Workflow

  1. Ensure Prerequisites are met
  2. Download the vFunction Sudoless Controller Installation TGZ
  3. SSH to the Linux VM as the user who runs the Application / Application Server
  4. Move the Installation TGZ to the location on the Linux VM where vFunction should run
  5. Extract the vFunction Installation Package
### Replace VERSION with the actual value
tar -xvzf vfunction-controller-sudo-less-installation.vVERSION.tgz
  1. Add Environment Variables for the vFunction Dynamic Agent
# See description in https://kb.vfunction.com/installations/configurable-settings/mono-dynamic-agent/java/linux
export VF_CONTROLLER_DEFAULT_JAVA_CONTROLLER_NAME="CHANGE_ME"
export VF_CONTROLLER_DEFAULT_JAVA_CONTROLLER_HOST="CHANGE_ME"
export VF_CONTROLLER_DEFAULT_JAVA_CONTROLLER_ORG_ID="CHANGE_ME"
export VF_CONTROLLER_DEFAULT_JAVA_CONTROLLER_APP_ID="CHANGE_ME"
export VF_CONTROLLER_DEFAULT_JAVA_CONTROLLER_CLIENT_ID="CHANGE_ME"
export VF_CONTROLLER_DEFAULT_JAVA_CONTROLLER_CLIENT_SECRET="CHANGE_ME"
export VF_CONTROLLER_DEFAULT_JAVA_CONTROLLER_INSTANCE_ID="CHANGE_ME"
export VF_CONTROLLER_DEFAULT_JAVA_AGENT_APPLICATION_SERVER="CHANGE_ME"
export VF_CONTROLLER_DEFAULT_JAVA_AGENT_APPLICATION_JAVA_VERSION="CHANGE_ME"
  1. Run the installation script
### Replace the BASE_DIR with the actual value, such as /tmp/
bash BASE_DIR/vfunction/opt/vfunction/controller-installation/install.sh -i default-java
  1. Find and note the base path to your JBoss Application Server
### This should return the location of the bin/standalone.conf which should be in the JBoss base path
find / -name 'standalone.conf' -type f 2&>/dev/null
  1. Find and note the location and version of the wildfly-common-VERSION.jar on your JBoss Application Server
### This should return the location of the bin/standalone.conf which should be in the JBoss base path
find / -name wildfly-common*.jar -type f 2&>/dev/null
  1. Find and note the location and version of the jboss-logmanager-VERSION.jar on your JBoss Application Server
### This should return the location of the bin/standalone.conf which should be in the JBoss base path
find / -name jboss-logmanager-*.jar -type f 2&>/dev/null
  1. Open the vFunction JBoss startup parameters in a text editor
### Replace BASE_DIR with the actual value where vFunction was installed
vi BASE_DIR/vfunction/etc/sysconfig/vfunction/agent/instances/default-java/vmargs-examples/wildfly

### Modify the JAVA_OPTS
### Change the YOUR-WILDFLY-BASE-PATH to be relevant for your environment
### Change the wildfly-common-VERSION.jar to be relevant for your environment
### Change the jboss-logmanager-VERSION.jar to be relevant for your environment
  1. Add the startup parameters to your JBoss Application Server’s JAVA_OPTS:
### Replace the BASE_DIR with the location where vFunction was installed
### Replace YOUR_WILDFLY_BASE_PATH below with the actual values
cat BASE_DIR/vfunction/etc/sysconfig/vfunction/agent/instances/default-java/vmargs-examples/wildfly >> YOUR_WILDFLY_BASE_PATH/bin/standalone.conf
  1. Restart the JBoss instance
  2. Confirm that the Application comes up and functions as expected. If any issues arise:

Updated on 14 Feb 2025