SeFetion部署

 SeFetion 部署

1，  SeFetion介绍

SeFetion 是jiangwx 使用开源项目MapleFetion飞信项目再次封装而成的短消息报警器，目前适合使用于个人系统报警，或消息警报，系统运行通知，服务器主机网络连接报告，在不久的将来将会免费提供web接口，方便广大程序爱好者调用。

2，  SeFetion 目录结构

       

 

说明：

Bin：SeFetion启动的可执行文件，现在文件夹为空，以后会拓展

Cjar：此文件夹是程序开发时使用，里面包含快速生成jar包的脚本

Conf：包含配置文件

Lib：SeFetion核心jar包存放处

Logs：SeFetion运行日志

Service：SeFetion以服务方式启动的脚本与可执行文件

3，  配置文件

  

 

说明：配置文件共有3个

Logging.properties:系统日志相关的配置文件

Se.properties : SeFetion 系统配置

Wrapper.conf:服务方式启动的配置文件

4，  部署方式

进入service文件夹，修改3_install_wrapper.bat脚本，修改2个地方

1)         set _WRAPPER_BASE=wrapper  #此处设置wrapper.exe文件名称

2)         set _WRAPPER_CONF_DEFAULT=../conf/wrapper.conf  #设置配置文件名称

 

进入conf文件夹，修改wrapper.conf文件，修改n个地方

1)         wrapper.java.command=java  #此处设置java.exe 路径，如果设置了环境变量，则可直接填写 java

2)         wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperJarApp  #此处填写程序入口类，此处有3种方式填写：详情请看附件1

3)         wrapper.java.classpath.1=../lib/wrapper.jar  #此处填写各种jar包，有多少个jar包就填多少个，填写方式如下

wrapper.java.classpath.1=../lib/wrapper.jar

wrapper.java.classpath.2=../lib/SeFetionClient-1.0.1.jar

4)         wrapper.java.library.path.1=../lib #填写wrapper.dll 所在路径

5)         wrapper.app.parameter.1=../lib/SeFetionClient-1.0.1.jar #根据wrapper.java.mainclass配置填写的参数，填写方式请看附件1

在本程序中就是填写入口jar包，jar包中的manifest文件设置了main-calss:

程序加载时就会从这里进去

6)         服务配置

# Name of the service

wrapper.name=SeFetion

 

# Display name of the service

wrapper.displayname=SeFetion

 

# Description of the service

wrapper.description=simple msg

 

# Service dependencies.  Add dependencies as needed starting from 1

#wrapper.ntservice.dependency.1=

 

# Mode in which the service is installed.  AUTO_START, DELAY_START or DEMAND_START

wrapper.ntservice.starttype=AUTO_START

7)         还有更多的参数请查看wrapper.conf文件

5，  配置好之后可以执行3_install_wrapper.bat 安装服务，届时，SeFetion部署完毕

  

附件1：

                       i.              wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

Main Class

The final component of the command used to launch JBoss is the main class, org.jboss.Main. The main class executed by Java when launched is specified by using the wrapper.java.mainclass property. As mentioned above however. Because the JBoss main class does not know how to communicate with the Wrapper, we will set the main class to be the full class name of WrapperSimpleApp. The JBoss main class is then specified as the first application parameter below.

 

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

 

Application Parameters

Application parameters are set using the wrapper.app-parameter.<n> properties. Application parameters appear in the Java command line directly after the main class. While JBoss does not have any such parameters, it is still necessary to set one of these properties. This is because we are using the WrapperSimpleApp helper class and as described above, its first parameter is the main class name of the application being run. in this case, org.jboss.Main:

 

wrapper.app.parameter.1=org.jboss.Main

 

                     ii.              wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp

Main Class

The next component of the command used to launch Tomcat is the main class, org.apache.catalina.startup.Bootstrap. The main class executed by Java when launched is specified by using the wrapper.java.mainclass property. As mentioned above however. Because we are making use of the WrapperStartStopApp helper class to start and stop Tomcat, we will specify that class's full name as the main class. The Tomcat main classes are then specified as application parameters below.

 

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp

 

Application Parameters

Application parameters are set using the wrapper.app-parameter.<n> properties. Application parameters appear in the Java command line directly after the main class.

 

When using the WrapperStartStopApp helper class, a lot of information needs to be provided about both the "start" and "stop" classes. This information includes each classes' full name, the list of parameters passed to their main methods, and a flag instructing the helper class whether or not it should wait for all non-daemon threads to exit before causing the JVM to exit.

 

To make it clear how all of this information is encoded, we will start by presenting the property values for the Tomcat application several comments have been added above what is normally in the wrapper.conf file to make it clearer what the properties mean. We suggest adding these comments to your configuration file wrapper.conf as well.

 

# The first application parameter is the name of the class whose main

# method is to be called when the application is launched.  The class

# name is followed by the number of parameters to be passed to its main

# method.  Then comes the actual parameters.

wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap

wrapper.app.parameter.2=1

wrapper.app.parameter.3=start

 

# The start parameters are followed by the name of the class whose main

# method is to be called to stop the application.  The stop class name

# is followed by a flag which controls whether or not the Wrapper should

# wait for all non daemon threads to complete before exiting the JVM.

# The flag is followed by the number of parameters to be passed to the

# stop class's main method.  Finally comes the actual parameters.

wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap

wrapper.app.parameter.5=TRUE

wrapper.app.parameter.6=1

wrapper.app.parameter.7=stop

 

The start and stop class names should be fairly clear. The first parameter count is required to locate the stop class in the parameter list. The second count is there for consistency.

 

The flag at parameter #5 above is used to control the behavior of the WrapperStartStopApp helper class when it is shutting down the JVM. When the Wrapper sends a JVM shutdown request, WrapperStartStopApp responds by calling the main method of the "stop" class with the configured parameters. The flag above controls what happens when that main method returns. If the flag is FALSE then System.exit(0) will be called immediately. When TRUE, WrapperStartStopApp will wait until all non-daemon threads have completed before calling System.exit(0). The latter is the behavior which produces the cleanest shutdown for Tomcat. If TRUE is specified, but one or more Daemon threads do not complete, the Wrapper will forcibly kill the JVM after its Shutdown Timeout has expired. This defaults to 30 seconds.

 

Non-daemon threads are counted by iterating over all threads in the system and counting those whose isDaemon method returns FALSE. Unfortunately, this count will never actually reach "0" (zero) on most JVMs because of the existence of system threads. In most Sun JVMs, there will be one non-daemon system thread. To make the shutdown work correctly, this system thread count needs to be correct. It can be set by defining a org.tanukisoftware.wrapper.WrapperStartStopApp.systemThreadCount system property. The default value is "1 thread".

 

                    iii.              Wrappper.java.mainclass=org.tanukisofeware.wrapper.wrapperjavaapp

Main Class

When using the Wrapper and the WrapperJarApp helper class, Java is not executing the jar directly. It is necessary to specify the helper class as the main class of the application. The main class executed by Java when launched is specified by using the wrapper.java.mainclass property as follows:

 

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperJarApp

 

Application Parameters

Application parameters are set using the wrapper.app-parameter.<n> properties. In this case, the command line to launch Hudson does not specifiy any application parameters, but it is nessary to tell the WrapperJarApp helper class which jar to execute. This is done as follows:

 

wrapper.app.parameter.1=C:\Hudson\lib\hudson.war