Here is for Profiling
Java Application from the WSAD help document:
Profiling an application
You must be in the Profiling perspective (Perspective > Open > Other > Profiling) in order to profile your Java, Web, or
EJB applications. If you are working in other perspectives such as the Java, Server, or the Debug perspectives, you automatically enter the Profiling perspective when you use the Profile button , which is available on the main toolbar.
Profiling an application is possible either on your local host, or on a remote host, or even in stand-alone mode (that is, from the command line). The Profiling tools are used primarily to profile applications in the WebSphere test environment, which is the complete run-time environment of WebSphere Application Server. They are also used to profile applications both locally and remotely using the WebSphere Application Server.
When you profile an application, you can specify the methods, classes, or packages you are interested in by setting filters for the agent.
Warning: Profiling too much data can significantly slow down your application.
Default filters are set in Window > Preferences > Profiling and Logging > Profiling, and they exclude some IBM, Java, and Sun packages. You can change these filters.