Linux: Multiple Tomcat service, unified installation Deployment unifyDeploy0.2 release

: unifyDeploy0.1 Version

unifyDeploy0.2 version

1 Introduction

Based on the Java Development project, with more and more services, the configuration file is more dazzling, every time do not know because the configuration problem is wasted time, but also do not know because the configuration problem has a number of problems. Multiple servers to switch back and forth, if the service needs to rely on, startup is a problem.

1.1 Purpose

One modification, unified installation, simple operation, practical and efficient.

1.2 Range

The scope of use of this project includes:

• Java-based development projects
• Wide range of project-related services
• Service startup has dependencies

1.3 Readers

The reader or other document stakeholders of this requirements specification are platform directors, product managers, project directors, project managers, developers, testers, UX designers, and so on.

2 overall Project description

2.1 System General function framework

2.2 List of system functions

Number	Module	Function	Description
unifydeploy_0.1	Exec	Build trust, initial command	Initial
unifydeploy_0.2	Tools	Provide a list of services and services	Scan to provide a list of services, get configuration information
unifydeploy_0.3	Conf	Auto get need to modify configuration	Automatically generated
unifydeploy_0.4	Bin	Execute script	Provides total execution with a single execution script
unifydeploy_0.5	New	Storing the modified configuration file	inversely proportional to bak retention file
unifydeploy_0.6	Bak	Storing the original configuration file	Easy problem Analysis
unifydeploy_0.7	Temp	Storing temporary files	Temporary files will be deleted without any redundancy
unifydeploy_0.8	Workapp	Storing War Packages	Upload War Package

3 Function Description

3.1 Getting the configuration file

It is very simple to get the configuration file through this system, only the user provides a list of services, other need not operate. The list of services is as follows:

Name           IP                 serve service name       192.168.0.1          /home/tomcat_ Service Name Service name       192.168.1.2          /home/tomcat_ Service Name Service name       192.168.1.2          /home/tomcat_ service Name

Noun Explanation:

Name: The name of the service, which must match the name of the war package. IP       : Server IP address. Serve:tomcat the deployment path.

Execute the script, ".. /unifydeploy/conf "Automatically generate the user needs to modify the configuration file, the profile is generated through filtering, so a service no matter how many files to configure, here only one, easy to modify and manage.

3.2 Automated Unified Installation Deployment

Automated unified installation deployment, including: Upload the Decompression War package, synchronization configuration, start services, monitoring services and so on.

list.sh  one.sh  pass.war  startup.sh  syn.sh  two.sh

Deployment supports unified installation in a distributed installation, and each script can be split into any combination, such as:

1) A new set of environments Tomcat has not yet deployed the service, only need to adjust the Upload War package script sequence, after the first upload war, follow-up operation normal execution.

2) Iteration Update, the function is slightly modified, the original configuration item does not need to modify, also only need to adjust the Upload War package script order, first obtains the original configuration, then uploads the update war package, the subsequent operation normal execution.

3.3 Description of advantages and disadvantages

Advantage Description:

1) for unified installation deployment, also for standalone service installation deployments.

2) retain the original backup, easy to deploy before and after configuration comparison.

3) Simple operation and strong demand expansion capability.

Insufficient Description:

1) temporarily only applies to Tomcat-based server projects.