1. Introduction Xiaobian recommended "MyEclipse crack version download" This is an advanced tutorial about discussing configuration and debugging applications running on the application server without using the MyEclipse server startup connector, regardless of MyEclipse Run on the same computer or on a different computer. For applications that are generally easy to configure and debug, it is highly recommended that the MyEclipse service connector be used for all server operation detailed tutorials in the application server. Please read it carefully before proceeding with this tutorial. Sometimes it is inconvenient to use the MyEclipse connector to launch the application server. For example, you might need to remotely debug an instance in an integrated development environment; or your server startup script might be modified or decided to be part of the development process, so you can't change the management of the external server at all, and finally MyEclipse might Servers that require specific debugging are not supported at all. If you are facing such problems, this tutorial will tell you if you do the following: configure your server for remote debugging to deploy the application to the server. Use a custom Eclipse startup configuration to communicate with your server on all servers. Debug your Java code to debug JSP-compatible servers in JSR-045 2. Configure remote debugging of the server To debug your external boot server with MyEclipse, you need to configure the application and then start the server to enable the external debugger to be controlled via JPDA. it. This section describes how to configure any application server for remote debugging, and provides several concrete examples to illustrate the basics of the server. To configure a Java application (including a server) for remote debugging, some additional Java virtual machine options must be specified. So the complete documentation and definitions and examples of remote debugging options are available directly from Sun. In summary, the virtual machine must know the mode in which to start debugging and the debugger connection to listen on a particular port. An example of the command line options required is shown below. 2.1 WebLogic Server Start a weblogic.cmd or startweblogic.sh script based on your operating system platform as an application instance launched from the command line. The script reads the environment variable named JAVA_OPTIONS and adds specifed as the parameter setting when starting the WebLogic call script. In Windows, this can be done by opening cmd.exe and issuing the following command: cd serverbinsetJAVA_OPTIONS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n.startWebLogic.cmd with your The path above the actual location of the BEA home folder is replaced, and other versions of WebLogic can be launched in a similar manner. Once the server has been fully booted, it can be connected and controlled into MyEclipse, as described in Section 3. 2.2 Tomcat Server According to your operating system platform, call a script named catalina.bat or catalina.sh to start the Tomcat instance on the command line. When launched in debug mode, the script will read the JPDA_TRANSPORT and JPDA_ADDRESS environment variables and add specifed to start Tomcat's parameter settings. In Windows, this can be done by opening cmd.exe and issuing the following command: cd binset JPDA_TRANSPORT=dt_socketset JPDA_ADDRESS=8000catalina.bat jpda start is replaced with the path above the actual location of the Tomcat installation folder, other versions of Tomcat It can be started in a similar way. Once the server has been fully booted, it can be connected and controlled into MyEclipse, as described in Section 3. 2.3 Sun Java System Application Server 8. x version According to your operating system platform, call a script named asadmin.bat or asadmin.sh to start the Sun Java System Application Server version 8 instance on the command line. If your server domain name is started, a configuration file named domain.xml will be read. The domain.xml contains other JVM startup options that can be manually set to start remote debugging. Edit the domain.xml file as shown below, then start the server and start remote debugging with an administrator command. Editing domain.xml for remote debugging Once the server is fully started, it can be connected and controlled into MyEclipse, as described in Section 3. 2.4 The JBoss server calls a run.bat or run.sh script as a JBoss instance from the command line, depending on your operating system platform. The script reads the environment variable named JAVA_OPTS and adds the parameter settings specified when starting the JBoss call script. In Windows, this can be done by opening cmd.exe and issuing the following command: cdbinsetJAVA_OPTS=-Xdebug-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n.run.bat with JBoss installation files The path above the actual location of the clip is replaced, and other versions of JBoss can be launched in a similar manner. Once the server has been fully booted, it can be connected and controlled into MyEclipse, as described in Section 3. 3. Deploy to a remote server MyEclipse provides an integrated deployment management tool that wraps and deploys any file system of your application while developing the system. The basics of application deployment are covered in the Web Development and Enterprise Development Quick Start, as this is an advanced tutorial, assuming you are familiar with the detailed deployment of these tutorials. When deployed to a standard MyEclipse startup application server, the deployment location is automatically set by MyEclipse based on the server type and deployment method. For remote server deployment, there is a "" server type that allows a full specification of the deployment location. After the remote deployment location is configured, the remote deployment behaves the same as the standard configuration, so the changes in the exploded deployment and project resources continue to be automatically synchronized. Keep in mind that because you are deploying to a custom location, it is your responsibility to ensure that your application server is loading the application at the selected location. Once the application deployment and server remote debugging are configured, you can start the server at any time. 4. Debugging the remote server MyEclipse provides a special debug launch configuration — MyEclipse external boot server is designed to connect to remote application servers and support full application debugging. Create a launch configuration for your external server, click the drop-down arrow for the corresponding icon on the debug toolbar, and select the Debug Configuration menu. Open the debug configuration window, select the MyEclipse external boot server, and click the New Launch Configuration icon to create a debug launch configuration for connecting to the application server. Creating a New Remote Debug Configuration The following figure shows a sample JBoss 4 remote debug configuration, similar to any server setup. Configuration of the JBoss example When the source lookup path defaults to your debug project, you can add locations for other source lookups from the configured source page. Configuring the Source Lookup Path After configuring the new launch configuration, if your remote server is already running and listening for debug connections, you can turn it off and use the click "Debug" button. After the application server and external debug configuration are started, a new debug process will be displayed in the debug view. Note: The debug view is not automatically displayed, so you will need to switch to the perspective of debugging or open it manually. Connecting to an External Debug Server At this point, if you use the built-in MyEclipse service connector to start a local server, the debugging application will be the same.