/
standalone.apt.vm
196 lines (140 loc) · 6.89 KB
/
standalone.apt.vm
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
------
Installing Continuum Standalone
------
Emmanuel Venisse
------
2010-02-19
------
Installing Continuum Standalone
~~%{toc|section=0}
* {Download and Configuration}
* Download the standalone version from the {{{http://continuum.apache.org/download.html} Download page}}
* Extract the file
* Set a <<<JAVA_HOME>>> environment variable which use a jdk >= 1.5
** {Defining JNDI Resources}
*** {Mail server configuration}
Before you start Continuum, you must configure your SMTP configuration for mail notification. In many servers, the
default of delivering to localhost with no authentication will be properly relayed. However, if you need to
configure a different SMTP server, the configuration is in <<<$CONTINUUM_HOME/contexts/continuum.xml>>>:
%{snippet|id=mail|url=http://svn.apache.org/repos/asf/continuum/trunk/continuum-jetty/src/main/contexts/continuum.xml}
*** {Database configuration}
By default, Continuum use an embedded {{{http://db.apache.org/derby}Derby}} database. If you want to use a different
database, you can modify the JNDI configuration in <<<$CONTINUUM_HOME/contexts/continuum.xml>>>:
%{snippet|id=datasources|url=http://svn.apache.org/repos/asf/continuum/trunk/continuum-jetty/src/main/contexts/continuum.xml}
Please refer to the documentation for your JDBC driver for the correct settings to use. You may need to alter the
<<<validationQuery>>> to one that can successfully execute on your database (or remove the setting if you do not
want to validate connections before using them).
You must ensure the JDBC driver is available in the classpath, by copying it to the <<<$CONTINUUM_HOME/lib>>>
directory and updating <<<$CONTINUUM_HOME/conf/wrapper.conf>>> to ensure it is listed instead of the Derby JAR.
Refer to the {{{http://commons.apache.org/dbcp/} Commons DBCP}} documentation for more advanced configuration of the
connection pool.
More information on supported databases is available in the Administrator's Guide on
{{{../administrator_guides/external-db.html} External Databases}}.
** Testing the Configuration
Start Continuum from the console in the <<<$CONTINUUM_HOME/bin/>>> directory:
----
continuum console
----
If it appears to be working correctly, it is a good idea to set it up as a service so that it will run in the
background under a suitable role account, and can be set to start whenever the server has started.
* {Installing as a Windows Service}
* Go to <<<$CONTINUUM_HOME/bin/>>> and run the following command:
------------------
continuum.bat install
------------------
* Edit the <<Apache Continuum>> service
* To see the services that are on your computer go to <Start>|<Run> and enter <<<services.msc>>>.
* Select the <<Startup Type>>
* Go to the <<Log On>> tab and select a real user. A real user is required because you'll need a home directory for Maven repository and some other things
* Validate your changes
* {Installing as a Linux Service}
Since the Continuum Linux script <<<bin/continuum>>> understands the same arguments as Linux boot scripts, there is no need to write a particular
startup script to add Continuum to the Linux boot process. All you need to do, as root, is:
------------------
ln -s /usr/local/continuum-[VERSION]/bin/continuum /etc/init.d/continuum
------------------
This will allow you to run <<<service continuum start>>> and other commands.
To have the service start on boot, follow the instructions below for your particular family of operating system.
** {On a Debian-based system}
At this point you have Continuum ready to be symlinked from different runlevels. Debian GNU/Linux comes with a very
handy utility to create these links, just run as root:
------------------
update-rc.d continuum defaults 80
------------------
If you run this command, you will see something like this:
------------------
Adding system startup for /etc/init.d/continuum ...
/etc/rc0.d/K80continuum -> ../init.d/continuum
/etc/rc1.d/K80continuum -> ../init.d/continuum
/etc/rc6.d/K80continuum -> ../init.d/continuum
/etc/rc2.d/S80continuum -> ../init.d/continuum
/etc/rc3.d/S80continuum -> ../init.d/continuum
/etc/rc4.d/S80continuum -> ../init.d/continuum
/etc/rc5.d/S80continuum -> ../init.d/continuum
------------------
What you see is the symlinks that would be created.
** {On a RedHat-based system}
Configuring Continuum on a RedHat-based system (like Fedora Core) is slightly different. Instead of running
<<<update-rc.d>>>, you need to add a new service using the <<<chkconfig>>> command.
------------------
chkconfig --add continuum
chkconfig continuum on
------------------
* {Installing as a Mac OS X Service}
On OS X, you can use <<<launchd>>> to run a service. Create the following
as root in <<</Library/LaunchDaemons/org.apache.continuum.plist>>>:
+----+
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>org.apache.continuum</string>
<key>ProgramArguments</key>
<array>
<string>/Applications/Continuum/apache-continuum-${project.version}/bin/continuum</string>
<string>console</string>
</array>
<key>Disabled</key>
<false/>
<key>RunAtLoad</key>
<true/>
<key>UserName</key>
<string>continuum</string>
<key>StandardOutPath</key>
<string>/Applications/Continuum/apache-continuum-${project.version}/logs/launchd.log</string>
<!-- Optional - store data separate from installation -->
<key>EnvironmentVariables</key>
<dict>
<key>CONTINUUM_BASE</key>
<string>/Users/continuum/Library/Continuum</string>
</dict>
<!-- Optional: force it to keep running
<key>KeepAlive</key>
<true/>
-->
</dict>
</plist>
+----+
To install the service, run the following:
+----+
$ sudo chown root:wheel /Library/LaunchDaemons/org.apache.continuum.plist
$ sudo launchctl load -w /Library/LaunchDaemons/org.apache.continuum.plist
+----+
Start and stop the service with:
+----+
$ sudo launchctl start org.apache.continuum.plist
$ sudo launchctl stop org.apache.continuum.plist
+----+
To uninstall the service:
+----+
$ sudo launchctl unload -w /Library/LaunchDaemons/org.apache.continuum.plist
+----+
You can follow the same steps to install build agents as a service by
replacing the appropriate paths, and changing <<<org.apache.continuum>>> to
<<<org.apache.continuum.buildagent>>> in the label and <<<plist>>> filename.
* {Installing with Puppet}
If you use Puppet to manage your infrastructure, you can use a third-party Puppet module to install Continuum. This
will take care of adding the required users, databases and configuration based on official release tarballs.
* {{{https://github.com/maestrodev/puppet-continuum} Puppet module for Apache Continuum and Continuum build agents}}