Configuring YourKit profiler to Remote Websphere instance

This post is a step by step guide to manually configure YourKit Profiler to an WebSphere App server.
The specific versions that i am using are  YourKit version 8.0.30 and Websphere Application Server 6.1 (yes , its EOL but should serve our purpose) .

The YourKit setup provides a variety of  platform specific agents .These are usually in the 'bin'  directory. Identify the version specific for your platform .Its 'linux-x86-64'  in my case.

1.Copy the agent file 'libyjpagent.so'  to a location on your remote App server ,'/app/custom/java/profilingagent/' in my case.

2.Configure the agent to the jvm process. The easier way to do this would be from  the Websphere admin console.

a.go to the Application Servers menu.

b.select the node that needs to be profiled
 
c.The java process setting are  defined in the 'Java and Process Management' section.


d. Go to the 'Process Definition' sub menu


e.And then Click on the 'Java Virtual Machine' option in 'Additional Properties'

f.Here you should be able to add the jvmagent  path as part of the 'Generic JVM arguments' . The parameter name is "-agentpath" .The format will be something like
-agentpath:'location of the agent file' . In my case it will be  -agentpath:/app/custom/java/profilingagent/libyjpagent.so  . Apply the setting and restart the server.




3.Configure the yourkit profiler  to connect to the server .The default port is 10001 . In-case the port is already in use ,the value will be auto incremented.


And we are finally connected