404 of the Tomcat startup project in Eclipse, starting normally

Problem Description:
After adding Tomcat in Eclipse, after startup, after accessing the Tomcat address, return 404, but starting Tomcat alone can access the page.

Problem Troubleshooting:
Since Tomcat is not a problem, it only means that there is a problem with the eclipse configuration, and the dual-hit open tomcat configuration can be seen

The default selection is the first
Analyze the meaning of this configuration page
Server locations understands where to perform the service
Specifies the path to the service and the path to the deployment, and the service after the publication should not be modified

Use workspace metadata (does not modify TOMCAT installation)
Working with workspace metadata (do not modify Tomcat)

Use Tomcat installation (takes control of Tomcat installation)
Using Tomcat installation (Operation Tomcat)

Use custom location (does not modify Tomcat insallation)
Use a custom location (do not modify Tomcat)

View the location of the default workspace. metadata.plugins\org.eclipse.wst.server.core\tmp0
It's just that eclipse copied a tomcat out to run the project
After you publish a project, you find that:

Directory structure is basically the same as Tomcat except for Wtwebapps inconsistencies

I always feel that it is inconvenient to publish items like this so I choose the second, that is, a practical locally installed Tomcat for the project release, if now Tomcat has released the project, where the path is not modified, you need to delete the item, you can reset the path, use the second after the start of access to normal, You can access the project normally.

Summary of questions:
In the past, this kind of problem will go to Tomcat, but often ignore the immediate configuration, the basic configuration of the error or record is better, for the next deployment time lookup.