Add the instrumented JAR files to your application classpath. If you are already using open source Spring Framework, replace each Spring Framework JAR in your application with the corresponding instrumented JAR in the dist directory. These jars are named org.springframework.<module>.instrumented-<version>.jar. See Mapping Maven Central JAR Names to EBR JAR Names if you originally obtained your non-instrumented Spring JAR files from the Maven Central repository.

	Note
	You cannot use both an instrumented JAR file and its open source equivalent. You must remove the open source JAR and add the corresponding instrumented JAR in its place.

For each instrumented JAR that you add to your application, include the matching instrumentation JAR, com.springsource.management.instrumentation.springframework.<module name>-<version>.jar. These instrumentation jars contain the aspects and Java classes used to manage and monitor the components in the instrumented JAR. Make sure you include com.springsource.management.instrumentation.springframework.applicationcontext.jar. It must be present to enable auto-discovery.

Some instrumentation JARs are shared among the instrumented Spring modules. For example, subclasses of AbstractPlatformTransactionManager exist in multiple jars. As such, all of these JARs may have a dependency on the com.springsource.management.instrumentation.springframework.transaction.manager.jar. When in doubt, consult the Import-Packages statement of the instrumented jar Manifest for the required dependencies.

Include the following Management API jars:

Include one of the following, depending on whether you are instrumenting a standalone application or a web application:

Add the instrumented JAR files to your application classpath. If you are using open source versions of these products, replace the JARs in your application with the corresponding instrumented jars in the dist directory of the Instrumented Spring Web Flow, Web Services, and Security components. These jars are named org.springframework.<module>.instrumented-<version>.jar. See Mapping Maven Central JAR Names to EBR JAR Names if you originally obtained your non-instrumented Spring JAR files from the Maven Central repository.

	Note
	You cannot use both an instrumented JAR file and its open-source equivalent. You must remove the open-source JAR and add the corresponding instrumented JAR in its place.

	Note
	The latest Instrumented Spring Security (2.0.6) does not include instrumented versions of all jars distributed with open source Spring Security 3.0.x. Use the open source Spring Security 3.0 instead of instrumented Spring Security if you need these additional jars. (Spring Security 3.0.x requires Spring Framework 3.0.x.)

For each instrumented JAR that you add to your application, include the matching instrumentation JAR, com.springsource.management.instrumentation.<instrumentedproduct>.<module name>-<version>.jar. These instrumentation jars contain the aspects and Java classes used to manage and monitor the components in the instrumented JAR.

Typically, when you write your Spring applications, you obtain the Spring JAR files from one of the following two repositories:

However, it is important to note that each repository uses a different naming scheme for the JAR files. The Spring instrumented JAR files are all based on the naming in EBR. This means that if you originally obtained your non-instrumented Spring JAR files from Maven Central, and now want to replace them with instrumented JAR files, you will need to translate the JAR names appropriately.

For example, if your application uses the non-instrumented JAR file from Maven Central called spring-webmvc-version.jar and you want to replace it with the instrumented JAR, you would replace it with the following file: org.springframework.web.servlet.instrumented-version.jar.

The following table lists the most common Spring JAR names, first using their Maven Central names and then their corresponding EBR name.