Deploying a Java web application on the Cloud Foundry, the default will use Cloud Foundry own Java - buildpack to pack to deploy the web application, in the use of Java - buildpack stage app, will start the Tomcat, Tomcat will then to automatically scan the deployment directory of the war file, deploy and start the web application, because the application instance is running in the warden in the container, only through the warden's outside DEA virtual machine IP: port to access on the application of the container (through DNAT will DEA IP: port into a warden container IP: port), so, if I'm going to visit in the external Tomcat server deployment applications homepage and Tomcat web console, can not access, please everyone a great god, if I need this to deploy Tomcat console application, external visit should be how to do?

CodePudding user response:

CloudFoundry is want users only need to pay attention to the code itself, and to reduce the cost of the management of a variety of middleware, app to deploy on cf, to be able to run up, for developers with respect to ok, will need to do the cf to complete in the center, so whether based on tomcat or IBM's buildpack liberty, don't want the user to go directly to manage the middleware, or want the user to simply don't care about his application is how to run,

CodePudding user response:

Because I want to monitor the deployment to the Cloud Foundry the operation situation of the application of PaaS, directly through the Tomcat Web console can see very clearly, so, now thinking about how to Tomcat console from the outside to visit the vessel,

CodePudding user response:

Can not directly monitor the warden?
Don't know the building Lord finally is what kind of plan do application monitor

CodePudding user response: