MyEclipse Application Service connector (top)

1. Service Connector in MyEclipse

The MyEclipse Enterprise Edition platform provides developers with the ability to seamlessly deploy, execute, and test myeclipse JEE applications in dozens of different application servers. These application servers include:

• geronimo
• Glassfish
• jboss/wildfly
• jetty
• jonas
• jrun
• liberty profile
• oracle
• orion
• resin
• springsource
• sun
• tomcat
• tomee
• weblogic
• websphere

Although many of the ready-made service connectors are available in MyEclipse, you must also download and install a third-party service connector to complete your project work as if it were included in the MyEclipse IDE.

For rapid deployment and testing, MyEclipse includes a specially installed Tomcat 7 and MyEclipse Derby database as part of the integration sandbox.

2. How the Service connector works

The interaction between MyEclipse and a local application server instance is achieved by using the Web Tools Project (WTP) framework of an app service connector. MyEclipse provides a server-managed central server operation and integration control in its Workbench toolbar and context menu, allowing you to:

• Start a run, debug, or pattern analysis of an application server
• Redirect to the console view of the MyEclipse by monitoring the standard output log messages that are run by the application server
• Test deployed applications with your custom test client and Web browser
• Executing the Hot-swap Java debugging code for the deployed application
• Perform JSP source-level debugging in an Jsr-045-compliant application server (such as tomcat5.x or later to stop executing an application server)
• Publisher, and deploy all projects to the server synchronously

The deployed application is displayed in the server view

When you instruct the connector to start its application server, the connector uses server configuration information to create a startup configuration, and then uses the connector to start an external JVM when the application server executes. Depicts the interaction between the connector and the application server.

Note : The connector is able to start and interact only with the file system that is installed on-premises access. WebSphere support is provided to WebSphere servers in MyEclipse.

Connector-server interaction Diagram

You can configure as many supported server instances as you need, whereas a typical environment requires only a small subset of connectors to be activated. If you need to test various configurations, you can configure multiple server instances.

3. Connector configuration

Configure the connector to enter from a server view or a running Server window and use the New Server Wizard. The process of configuration is straight forward, but you must be familiar with the installation and startup details of the server.

Note : A common mistake in the configuration process is when a full JDK JVM is started, and the server launches the Java JRE instead. The problem is that JEE application servers need access to the JDK compiler to support dynamically processed JSPs and EJB proxies. The JDK contains the required compilers, while the JRE does not.

New Server Wizard

The requirements for MYECLIPSE application Server support are:

• myeclipse app Service connector requires direct access to the application server's installation folder. Therefore, the application server must be installed on a file system that MyEclipse operates natively.
• in order to support JSP source-level debugging, the application server must support debugging of non-Java source code for the JSR-045 specification.
• hot-swap debugging requires the launch of a virtual machine with a JDK 1.4.x or later application server. If you are using an old application server with the JDK 1.3 debugger, breakpoints are supported, but it is not possible to modify the Hot-swapping code in the MyEclipse Workbench because 1.3 JVMs does not support the JPDA specification.
• The service connector for the application should configure a full JDK environment (containing javac) to start the application server and not use the JRE. The entire JDK is required because it provides a Java compiler to meet the needs of all application server compiling JSP pages to dynamically process and deploy EJBS. A complete JDK of your platform can be downloaded from the http://java.sun.com/j2se/downloads/index.html page of Sun Microsystems.

Only the MyEclipse Jee project type (Enterprise, Ejb,web) can deploy MyEclipse deployment Services. MyEclipse does not support direct deployment of basic Java projects. For more information about the Java project-based MyEclipse Web project and its deployment, see Web Project Tutorial.

3.1 Customizing the deployment server

If your application server is not under MyEclipse control (that is, you start and stop the server using an external tool or a shortcut to the server), you can use a custom deployment server configuration when you deploy the Hot sync resource.

When you define a new server window, expand Basic and select a custom deployment server. You can set up like any other connector, but beyond that, you must specify the deployment location of the MyEclipse resource.

Configure a custom Deployment server

MyEclipse official Chinese online line, welcome to download Communication!

MyEclipse Application Service connector (top)