Created On:  2010-02-02

Problem:

There are cases in which a profiling session cannot be started on an Application Server from the DevPartner Java Edition User interface.

Resolution:

The nmshell utility in the home directory acts as a wrapper for the Windows Command shell or *nix shell.
The syntax for nmshell is:
nmshell -config Configuration-name {-perf, -mem, -cov} [-batch] [-nmv] [-help] –exec <command>

The –exec command switch will the enable the command passed as a parameter to be invoked immediately on a child process that is populated with the necessary variables that will cause the insertion of the DevPartner Java Edition profiling core into the first instance of a JVM encountered.  Without this switch, a child shell will be spawned in which the environment is populated with the following variables that will cause the insertion of the DevPartner Java Edition profiling core into the first instance of a JVM encountered. The command to start the server, or the command that eventually accesses the entry point to the java application, server, applet, or Rich Client Platform can be entered in the child shell that is spawned.
Sample syntax : nmshell –perf –config test –exec [d:\tomcat\bin\startup.bat | /usr/tomcat/bin/startup.sh]

For an explanation of the various switches please consult the online help facility.