Upgrade - Java Agent Controller on Azure App Services for Dynamic Analysis

Overview

The vFunction Dynamic Analysis Controller can be configured for a manual or automatic installation.

In a manual installation, the vFunction Dynamic Analysis Controller is always staged. But, it it only running when an Administrator runs the installation script in the Azure App Services Console. This means that, if a new version of the Application is deployed to Azure App Services or if the Application is restarted, the vFunction Dynamic Analysis Controller will need to be manually installed again.

In an automatic installation, the vFunction Controller process is added to the repository of the Application. As part of the Application’s startup process in Azure App Services, the vFunction Dynamic Analysis Controller is launched when the Application is deployed. This means that the vFunction Dynamic Analysis Controller will always be running with the Application in Azure App Services.

Manual Upgrade

  1. Download the vFunction Controller Windows Installation ZIP
  2. Open the App from the Azure Portal
  3. From the left-hand sidebar, open the Development Tools > Advanced Tools > Go to launch the Kudu Console
  4. On the Menu Bar, open the Debug Console > PowerShell editor
  5. Drag-and-drop the vFunction Controller Windows Installation ZIP into C:\home\
  6. Unzip the Installation ZIP
Expand-Archive -Path C:\\home\vfunction-controller-windows-installation.v4.2.1723.zip -DestinationPath C:\\home -Force
  1. In PowerShell, run the upgrade
powershell -NoProfile -ExecutionPolicy unrestricted -Command "C:\home\vfunction\controller-installation\upgrade.ps1 -instance default-java -scriptMode true"
  1. Optional: if upgrading from a starting version of the vFunction Agent below 4.2, modify the vFunction Startup Parameters to remove irrelevant flags:
  1. From the left-hand sidebar, select Settings > Environment Variables
  2. Edit a new Environment Variable
Name: JAVA_OPTS
Value: -agentpath:C:\\home\\vfunction\\agent\\JVMTIAgent.dll=conf=C:\\home\\vfunction\\config\\agent\\instances\\default-java\\native-conf.json -javaagent:C:\\home\\vfunction\\agent\\runtime-agent.jar=ConfigLocation=C:\\home\\vfunction\\config\\agent\\instances\\default-java\\vfunction-runtime-override.properties --add-opens java.base/java.lang=ALL-UNNAMED -Dcom.vfunction.logging.logFile=C:\\home\\vfunction\\log\\instances\\default-java\\vfagent.log
  1. Save and apply the Environment Variable changes. This will automatically restart the Azure App Service’s instance
  1. Optional: If you did not modify the Environment Variables, you will need to restart the Application in order for the new version of the Application to pick up the new version of the vFunction Agent
  2. In the vFunction Server UI, confirm that the Agent is Status: Up and Start Learning

Updated on 19 May 2026