Created On:  2009-11-19

Problem:

There is no direct integration, and official testing and support for integration between IntelliJ and DevPartner for Java.

Resolution:

If  the Java IDE Add-in Manager cannot be used to integrate DevPartner Java Edition,  you may be able to invoke DevPartner Java Edition from within IntelliJ by adding the -Xrun or -agentlib argument to the JVM Arguments section in IntelliJ .
Application
1. You will need to modify the application configuration profilile used when launching the Application that the application is deployed or create a confguration profile especially designed for this purpose
2. Select Run, then Edit Configurations from the Menu, and select the appropriate configuration.
3. In the Create, manage and run configurations dialog box, create a new launch configuration
4. Do one of the following:

If you are using JVMPI (JDK 5.0 or below), add the -Xrun argument to the VM parameters text box, as described in Using -Xrun to Invoke the Profiler in the online help.  A sample string is listed below.
-XrundpjCore:NM_ANALYSIS_TYPE=performance:NM_CONFIG_NAME=test
Note: This is one string without a newline character inserted.

If you are using JVMTI (JDK 5.0 or above), add the -agentlib argument to the VM parameters, as described in Using -agentlib to Invoke the Profiler in the online help. A sample string is listed below.
-agentlib:dpjJvmtiCore=NM_ANALYSIS_TYPE=performance,NM_CONFIG_NAME=test
Note: This is one string without a newline character inserted. Also note the comma delimiter prior to NM_CONFIG_NAME.
Server
1. You will need to modify the server confiuration profilile used when launching the Application server that the application is deployed or create a confguration profile especially designed for this purpose.
2. Select Run, then Edit Configurations from the Menu, and select the appropriate configuration. 
3. Do one of the following:

If you are using JVMPI (JDK 5.0 or below), add the -Xrun argument to the VM parameters text box, as described in Using -Xrun to Invoke the Profiler in the online help.  A sample string is listed below.
-XrundpjCore:NM_ANALYSIS_TYPE=performance:NM_CONFIG_NAME=test
Note: This is one string without a newline character inserted.

If you are using JVMTI (JDK 5.0 or above), add the -agentlib argument to the VM parameters, as described in Using -agentlib to Invoke the Profiler in the online help. A sample string is listed below.
-agentlib:dpjJvmtiCore=NM_ANALYSIS_TYPE=performance,NM_CONFIG_NAME=test
Note: This is one string without a newline character inserted. Also note the comma delimiter prior to NM_CONFIG_NAME.
4. Click OK. Launch the Application server.
When you include the -Xrun or -agentlb argument in the settings, the program is compiled. redeployed, and run under the Application Server  but with DevPartner Java Edition profiling enabled. 
5. If your IDE test server is already running, you must stop and restart that IDE test server with DevPartner Java Edition in order for DevPartner Java Edition to properly hook into the IDE test server and profile your application.