MyEclipse Application Service connector (bottom)

In the Application Service connector (above) article, the small section describes the service connector in MyEclipse, how the service connector works, and the configuration of the connector. The next small series will continue to introduce the other two sections of the content, we hope to help everyone.

4. Server View

The server view provides a comprehensive view of configuring the state of the Application Service connector. This view is a standard part of the MyEclipse default view. To open the server view, select Window>show view>servers.

Note : If you have an open view that causes the server view to disappear from the menu, select Other, expand MyEclipse Java Enterprise, and select the server.

The Server View toolbar and the right-click menu contain server controls, and the following table describes the capabilities of each tool.

Server to view highlighted toolbar controls

The server view is displayed when the server is out of sync. You can synchronize the running and stopping of the application server with the server.

Server Status "republishing"4.1 Access server configuration

When you configure the server, you can open the Server Configuration Editor by double-clicking the server in the server view, or by right-clicking the server and choosing open Access configuration from the menu. You can access the server configuration settings when you add them, and you can also adjust the publish settings and time-out settings.

Access server Configuration

The default publishing settings are automatically released when resources change, which is also known as hot-sync ' ing. The published interval represents the amount of time the server spends waiting for resource changes or building events. A timeout indicates the maximum time allowed for a server operation to complete. To view the metadata for the Tomcat server (or possibly a third-party server), open the Server View Profile node.

Other tomcat meta-data files5. Jee Project Deployment

MyEclipse can deploy Web, EJB, and enterprise application projects on any myeclipse-enabled application server. MyEclipse supports two deployment modes: Expand Archive deployment and encapsulate archive deployment.

• Expand Archiving Deployment : This is a development-centric, not a standard JEE application encapsulation deployment model. Similar to encapsulating deployment, the application's deployment resources are organized to conform to a standard JEE folder/file structure. However, instead of creating and deploying a single archive file, the structure of the entire application resource, including folders and files, is replicated through the application Service connector to the special deployment location of the server. The MyEclipse deployment service uses "synchronous on demand" technology to keep all source code changes synchronized for all MyEclipse projects deployed in their respective projects.

Note : Deployment deployments do not support the JEE standard, and all application servers are not supported.

• Encapsulated Archive Deployment : This is the JEE Standard application encapsulation deployment model for production-centric. It includes resources for packaged applications and a single zip archive with an internal Jee-standard file structure. The resulting single archive file is then deployed to the Application Service connector's target application server. An encapsulated archive deployment does not support incremental or automatic archive updates. As a result, the encapsulation deployment becomes unsynchronized and its source project is edited for project resources. The latest version of the MyEclipse Project source code periodically publishes the state of the application that needs to be resynchronized.

Use the vendor of your application server to query the mode supported by the application server.

For a project, you can specify the server that you always want to run the project to prevent you from choosing Run As>myeclipse Server application each time you select a server. You can also set the default deployment mode for the project.

To specify the server for the project, right-click the project and select Properties. Expand MyEclipse and select Server deployment. At the appropriate time, the running project always uses the specified server and deployment mode.

Server Deployment Project Properties5.1 Flexible deployment with deployment components

Flexible deployment support allows you to deploy a single subset of source folders, where the deployed path does not exist in the project's workspace, and typically deviates from the fixed project structure, where everything resides in the Webroot folder of your project. For enterprise-class projects, you can also control the compression file name and deployment of utility projects.

Configure the deployment component, right-click a project, and select Properties from the menu. Expand MyEclipse, and select Deployment Assembly. Please refer to MyEclipse Deployment Assembly for more information.

Expand a component's Web project to expand components5.2 Deployment to server

Deploying the project to the server is simple and requires only one project to be added to the server.

Add Project to Server

When a service connector is supported, once you move it to the configuration column at deployment time, you can use the mode next to the drop-down list to change the default deployment mode. The icon next to the module indicates the deployment mode.

After a project is added to the server, it appears in the server name below the server view.

The server view shows the deployed application

MyEclipse official Chinese online line, welcome to download Communication!

MyEclipse Application Service connector (bottom)