# How Do I: Debug an Application on a Remote Production Server?

You can debug an application running on a remote server, even if that server is not running WebLogic Workshop.

The following procedure explains how to debug an application that is deployed to a server running WebLogic Server in production mode or a server that is not running WebLogic Server.

#### Start the server in production mode

1. On Windows, open a command shell and cd to the server's root directory.
2. Use the following command to start the server:

        startWebLogicServer production notestconsole noiterativedev

For detailed information on starting WebLogic Server in production mode see startWebLogic Command.

#### Deploy the target application to the remote production mode server

- See How Do I: Deploy a WebLogic Workshop Application to a Production Server? for detailed instructions.

#### Open a Copy of the Application in WebLogic Workshop and Set Debugging Options

1. In WebLogic Workshop, open an exact, local copy of the remotely deployed application you wish to debug in WebLogic Workshop.
2. Right-click the project you wish to debug and select Project Properties.
3. In the Project Properties dialog, select Debugger.
4. Under Debugging options, select Non Workshop Server.
5. Under Non Workshop Server settings, enter the Http Port and Server values for your remote server. (If the remote server is not running WebLogic Server, also set the Debugging Port.)

Note: Stopping debugging in the IDE will stop the remote server. To avoid the inconvenience of having to stop and restart the server, press Ctrl-Shift B to disable breakpoints and Ctrl-B to re-enable them.
Note: You can only debug Java-based files (JWS, JPF, etc.) using this procedure.

Note: When you debug an application on a non-Workshop server, you cannot get Stream data when debugging JSP's nor can you do script (jsx) debugging.

To learn more about debugging with WebLogic Workshop, see Debugging Your Application.

Related Topics

Debugging Your Application