Using an application with DPJ that is not automatically integrated



What can be done if your application is ‘unsupported’ or there is no DPJ plug-in available


If your application does not have a plug-in associated with it, you can use one of the command line utilities. One in particular is the nmshell application. We will use BEA WebLogic 6.0 SP2 as an example.

  1. Find the file startManagedWebLogic.cmd located at bea_install_dir/config/mydomain/ and open it in a text editor.
  2. Add your admin password (that way you do not have to type it in every time). Look for the following set WLS_PW= entry:
    echo * To start WebLogic Server, use the password     * 
    echo * assigned to the system user. The system        * 
    echo * username and password must also be usedto      * 
    echo * access the WebLogic Server console from a web  * 
    echo * browser.                                       * 
    echo ***************************************************
    @rem Set WLS_PW equal to your system password for no password prompt server startup. 
    set WLS_PW=( We like to use adminpass1 so I will never forget it)
  3. After you edit the file, then you can start the server using nmshell. We have found that the best combination is the following:
    nmshell -nmv -batch -mem -config BEA60SP2 -exec startManagedWebLogic.cmd
    nmshell command Comments
    -nmv A recommend command. Turns verbosity on; best for troubleshooting if something were to fail.
    -batch Runs the DevPartner in the background or batch mode. This way, the browser will not open automatically. When you go to the Active Sessions tab, you will see it there.
    -mem Allows you to use the type of coverage you require (mem Memory Analysis, cov- Code Coverage or perf Performance Analysis).
    -config This will create a configuration under the name you give it.
    -exec The command that you would need to use to start your application server. In our case, the startManagedWebLogic.cmd starts the server.

    This will (on Win32) open a new command prompt window where the application starts. Once you see that it is fully started (in this case , it will say listening on port 7001 or what port you have it configured), you can then open the DevPartner Java application and look for your application on the Active Sessions screen.

Old KB# 11117
Comment List
Related Discussions