Applications are the basic units in EDAS management. EDAS provides a complete life cycle management process for applications, including application creation, deployment, startup/stop, and deletion.
Application publishing includes application creation, deployment, startup, and stop.
Application creation and deployment are usually performed consecutively. After creating an application, you will need to deploy it. The ways for creating and deploying regular and Docker applications are different.
Publish a regular application: Create an EDAS container on your ECS instance and deploy the WAR package of the application to the container. The process is as follows:
Publish a Docker application: You can use either of the following ways to publish a Docker application:
- Upload a WAR package: Create Docker instances on the specified ECS instance in the specified Swarm cluster, create an EDAS container in each Docker instance, and deploy the WAR package of the application in the EDAS container of each Docker instance.
- Use images: Locally prepare a Docker image using the Docker and EDAS basic images (including the EDAS container) and the WAR package of the application, and upload it to the image repository.
The process for publishing a Docker application is as follows:
Management of regular and Docker applications is different. Main operations include:
- Roll back an application: After the rollback version is specified, applications can be automatically rolled back by group and by batch.
- Application scale in or out : You must add an ECS instance to scale up the application, or stop and deactivate the ECS instance to scale down the application.
- Delete an application: You must stop the application, put the ECS instance out of service and then delete the application.
- Manage instances：Manage the instances where the application is deployed.
After a regular or Docker application is deployed, you must start it before using the application.
Settings may include intranet and Internet load balancing, container configurations, JVM parameters, health check and basic information, and the health check URL.
- You can deploy, scale up, roll back, reset, and configure an application when the application is running or stopped.
- After the parameters of the Tomcat container and JVM are configured and saved, the related configuration files are modified. The changes take effect only after you restart the application.