MANUAL INSTRUMENTATION
This section describes the steps involved when Auto-Instrumentation method is not possible. Follow either Method 1 or Method 2 described below
Method 1:
-
Shut down Wildfly Server (if it is running)
-
Add the content below to file standalone.conf in the directory %WildFly_HOME%\bin:
export JAVA_TOOL_OPTIONS="$JAVA_TOOL_OPTIONS -javaagent:/opt/virsec/iae-java/instrumentation.jar -DVSP_HOME=/opt/virsec -Dvirsec_appcontextpath=<AppCollectiveID>"
NOTE:
Ensure that <AppCollectiveID> mentioned above is replaced with the App Collective ID in the CMS Application Configuration section
-
Save the modified file standalone.conf
-
Start the Wildfly Server
Method 2:
This method can be used for VSP instrumentation in Domain Mode deployment
-
Log in to Virtual Machine where WildFly is installed
-
Stop the Wildfly service if it is running
-
Modify the file $WildFly_Home\domain\configuration\host-slave.xml to include the following underlined entries for the server to be instrumented
In this example, arguments are configured for JVM “server-one”
Before Change:
After Change:
NOTE:
Ensure that <AppCollectiveID> mentioned above is replaced with the App Collective ID in the CMS Application Configuration section
-
Start the Wildfly service using the below command
-
$WildFly_Home/bin/standalone.sh
-
-
Application Deployment Folder
-
Log in to the Virtual Machine where WildFly is installed
-
Utilize the below path as Application Deployment Folder
$WildFly_Home/domain
-
Example: /opt/wildfly-21.0.1.Final/domain
-
-
Startup Script File Path
-
As the VSP-JVM arguments are configured manually, create a dummy file and provide the file path as Start Up Script File Path in the CMS
-