3.7 Debugging an Oracle Tuxedo ATMI Server Application

You must use the following procedure only if you have built the ATMI server application using the Debug configuration for your project.

To debug a server that has not been booted, follow these steps:

1. At any Windows command prompt, type tmboot -n -d 1 -s servername to display the command-line options used by tmboot(1) to start servername.
2. Execute the tmboot -M command to boot the BBL. (If necessary, boot additional application servers or machines.)
3. In msdev, select Project → Settings.
4. In the Program Arguments field of the Debug page, type the command-line options used in step 1.
5. Start the debugger and start debugging the server application.

   Note:

   Because Oracle Tuxedo libraries are not built with debugging information and source code is not provided, you cannot access the Oracle Tuxedo code directly.
6. To end the debugging session, type tmshutdown at any Windows command prompt.

   WARNING:

   Do not stop the server by selecting Debug → Stop; the Oracle Tuxedo system may subsequently attempt to restart the server.

   To debug a server that is already running, type msdev -p nnn at any Windows command prompt, replacing nnn with the server’s process ID (represented by a decimal number).