...
| Warning | ||
|---|---|---|
| ||
With the JBoss version 6 and above there is the problem with the logging when an agent that uses the java.util.logging is started with the JBoss. Please relate to JBoss 6.x and , JBoss 7.x, JBoss 8.x or WildFly 8.x.x - 10.x.x pages for information on how to overcome this problem when starting JBoss / WildFly with inspectIT Agent. |
Instrumentation
There are two possibilities how to set-up and use inspectIT with the JBoss application server. The first solution is to start the JBoss application server stand-alone with a start-up script. The second one is to integrate inspectIT in the start-up process, integrated in the eclipse development environment.
Stand-alone solution
JBoss provides the file run.sh in the /bin directory to set the environment for starting up JBoss. inspectIT can be easily integrated within this file. A best practice is to define variables holding the references to the inspectIT installation and configuration folders.
| Code Block |
|---|
set INSPECTIT_AGENT_HOME="[path-to-inspectit-agent]"
export INSPECTIT_AGENT_HOME
set INSPECTIT_CONFIG_HOME="$[path-to-config-folder]"
export INSPECTIT_CONFIG_HOME
set INSPECTIT_JAVA_OPTS="-Xbootclasspath/p:${INSPECTIT_AGENT_HOME}/inspectit-agent.jar -javaagent:${INSPECTIT_AGENT_HOME}/inspectit-agent.jar -Dinspectit.config=${INSPECTIT_CONFIG_HOME}"
export INSPECTIT_JAVA_OPTS
# integrate inspectit java options with the java options of JBoss
set JAVA_OPTS="${INSPECTIT_JAVA_OPTS} ${JAVA_OPTS}"
|
Eclipse
To integrate inspectIT into the startup-process of the JBoss Applicationserver you have to edit the launch configuration of the JBoss application server. Please ensure that you have installed the JBoss server tools which you can find in the specific repository.
...