<< PREVIOUS

 

 

MANUAL INSTRUMENTATION

 

This section describes the steps involved when Auto-Instrumentation method is not possible for Probe installation. (Domain Mode Deployment). Follow either Method 1 or Method 2 described below

 

Method 1: Script based startup:

  1. Shut down Wildfly Server (if it is running)

  2. 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

     

  3. Save the modified file standalone.conf

  4. Start the Wildfly Server

Method 2: Services based Startup:

  1. Log in to Virtual Machine where WildFly is installed

  2. Stop the Wildfly service if it is running

  3. 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:

    image5

    After Change:

    image6

     

    NOTE:

    Ensure that <AppCollectiveID> mentioned above is replaced with the App Collective ID in the CMS Application Configuration section

     

  4. Start the Wildfly service using the below command

    1. $WildFly_Home/bin/standalone.sh

       

       

  5. Application Deployment Folder

    1. Log in to the Virtual Machine where WildFly is installed

    2. Utilize the below path as Application Deployment Folder

      $WildFly_Home/domain

    3. Example: /opt/wildfly-21.0.1.Final/domain

  6. Startup Script File Path

    1. 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

 

<< PREVIOUS