------ body content display, start to learn new knowledge ------
The functions are as follows:
Support one-click start Spring boot project. tomcat built-in project tomcat standalone project
I. Introduction
The Spring boot project only needs a JDK environment to deploy successfully.
Tomcat built-in projects require Tomcat to be installed in order to deploy successfully.
Tomcat standalone projects require Tomcat to be installed in order to deploy successfully. One project with one Tomcat running independently of each other will not affect other tomcat projects.
Deploying the Springboot projectThe JDK needs to be present on the system.]
The test here is to use jenkins from the jenkins official website to download the 2.344 version of the war package
https://ftp.belnet.be/mirror/jenkins/war/2.344/jenkins.war
The file is placed under /www/jar.
Support one-click start Spring boot project. tomcat built-in project tomcat standalone project
I. Introduction
The Spring boot project only needs a JDK environment to deploy successfully.
Tomcat built-in projects require Tomcat to be installed in order to deploy successfully.
Tomcat standalone projects require Tomcat to be installed in order to deploy successfully. One project with one Tomcat running independently of each other will not affect other tomcat projects.
Deploying the Springboot projectThe JDK needs to be present on the system.]
The test here is to use jenkins from the jenkins official website to download the 2.344 version of the war package
https://ftp.belnet.be/mirror/jenkins/war/2.344/jenkins.war
The file is placed under /www/jar.
After the selection is complete. It will automatically populate the startup command for you. If you need to change the startup commands you can do so at will The default startup command is as follows: [Note that jenkins does not support server.port listening on ports]. /usr/local/btjdk/jdk8/bin/java -jar -Xmx1024M -Xms256M /www/jar/jenkins.war -server.port=6192Copy CodeStartup Commands Explained Path to /usr/java/jdk1.8.0_281/bin/java JDK -Xmx1024M -Xms256M Limit maximum memory to 1024M Minimum memory 256M -server.port=6192 Started port You can change the startup commands and parameters as you like. For example, I changed it to start as follows /usr/local/btjdk/jdk8/bin/java -jar -Xmx1024M -Xms256M /www/jar/jenkins.war -httpPort=6312Copy Code After the submission is complete, you will see a page to see if the project was launched successfully. Ports will not be displayed when they are first started. You need to wait for the project to start up completely before you can display the started ports. Access items ip:port If you need 80 access. You need to add a domain name and enable external mapping as follows: When it's turned on successfully, visit and test it. Deploying Tomcat built-in projects 2.1 Built-in Project Introduction The built-in project allows you to set up multiple projects. The disadvantage is that multiple projects may cause conflicts between them. Support for Tomcat7 tomcat8 tomcat9 Ubuntu and Debian do not support Tomcat7 only Tomcat8 Tomcat9 Centos7 Centos8 support tomcat7 tomcat8 tomcat9 Install Tomcat as follows: Just click to install After the installation is complete, you can see the startup status and port information of Tomcat. 2.2 New built-in project Submit to start the project After the startup is complete, you can see the specific occupancy information of the project 2.3 Uploading a war or uploading a web archive Here's a test with two cases. 2.3.1 Testing index.jsp Test access to test.com Test jenkins.war on tomcat. https://ftp.belnet.be/mirror/jenkins/war/2.312/jenkins.war After downloading. Put it in the root directory of my website. Then unzip it. After decompression is complete. Delete the current war package. Or move it to another directory. You need to restart Tomcat before you can access the project. Visit the website afterward. Deploying Tomcat standalone project 3.1 Introduction Standalone project You can start a Tomcat in a separate project. Pros: Separate resource. Does not affect other projects Cons: Takes up more resources than the built-in program Ubuntu and Debian do not support Tomcat7 only Tomcat8 Tomcat9 Centos7 Centos8 support tomcat7 tomcat8 tomcat9 Install Tomcat as follows: Just click to install After the installation is complete, you can see the startup status and port information of Tomcat. 3.2 Creating stand-alone projects After creation, you can see the CPU and memory information of the current project. 2.3 Uploading a war or uploading a web archive Here's a test with two cases. 2.3.1 Testing index.jsp A single index.jsp project does not require a project restart. Direct access is available The access was successful as follows: 2.3.2 Testing jenkins.war First you need to upload the WAR package to the website with the directory. Then unzip it Remember to restart the current project after the decompression is complete as follows: Visit the site after the reboot is complete IV. Summary of issues 4.1 Issue 1: If you don't have a domain name and only want to use IP+Port for project deployment You can decompress the war package by placing it in the tomcat webaps directory. The following is an example of how to do this: The tomcat installation directory and port are as follows: tomcat7 installation directory in /usr/local/bttomcat/tomcat7 port number 8231 tomcat8 installation directory /usr/local/bttomcat/tomcat8 port number 8232 tomcat9 installation directory /usr/local/bttomcat/tomcat9 port number 8233 4.1.1 Deploying jenkins without a domain name on Tomcat8 [I First you need to go to /usr/local/bttomcat/tomcat8/webapps Then create a new directory. Then upload your war package. Remember to delete that WAR package after unzipping. After decompression, restart tomcat to access the project. Then access Ip:8232/the directory you created Example. My IP is 192.168.1.72 My new directory is test Then the URL is as follows: http://192.168.1.72:8232/test 4.1.2 Deploying jenkins without a domain name on Tomcat8 [II Deploying a project using Tomcat manager Tomcat has a built-in manager for project management. Here's how it works Opened DetailstutorialsBelow: https://blog.csdn.net/feinifi/article/details/80704564 4.1 Issue 2: Why did the project start-up fail? Please read more about the error message 4.3 Question 3: How is SSL supported? The new version of the Java project supports one-click SSL certificate application. 4.3 Question 4: Why is it suddenly 502? There are a variety of problems with the 502. Most of them are back-end issues. It could be that the port of your project is incorrectly filled in. It is also possible that the Java back-end service hangs. There are many aspects of the problem. |
Warm Tip:
This article was last updated on
2024-07-13 11:08:30
Please note that some articles are time-sensitive, so if there are any errors or if they are no longer valid, please check below.leave a messageor contactHootSuite OfficialThe
本站所有系统源码请合法合规使用,严禁从事违法犯罪,侵权等任何非法活动,违法犯罪毁三代,且行且珍惜!
© copyright statement
THE END
No comments