Changes for page Your First Deployment

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.kiddyr
	1	+XWiki.btriller

Content

...	...	@@ -12,11 +12,11 @@
12	12
13	13	We will focus on the classic tools since this is the method that the majority of the community use. The classic deployment tools consists of:
14	14
15		-* wotaskd. A daemon that act as a watchdog to send lifeboat to the applications its manage + launching and stopping applications. Source code is available and it's actually a Project Wonder application
	15	+* wotaskd. A daemon that acts as a watchdog to send lifebeat to the applications its manage + launching and stopping applications. Source code is available and it's actually a Project Wonder application
16	16
17		-* Module for your Web server software (Apache or IIS). If a module don't exist for your preferred Web server, you can use a CGI.
	17	+* Module for your Web server software (Apache or IIS). If a module doesn't exist for your preferred Web server, you can use a CGI.
18	18
19		-* JavaMonitor. A Web GUI to manage wotaskd configuration (which is a XML file). It's optional, and you can manage multiple instances of wotaskd with a single JavaMonitor installation. JavaMonitor also have REST APIs so that you can manage the configuration by command-line or by a JavaScript app.
	19	+* JavaMonitor. A Web GUI to manage wotaskd configuration (which is a XML file). It's optional, and you can manage multiple instances of wotaskd with a single JavaMonitor installation. JavaMonitor also has REST APIs so that you can manage the configuration by command-line or by a JavaScript app.
20	20
21	21	But first, we need to actually make our projects ready for deployment.
22	22
...	...	@@ -40,12 +40,12 @@
40	40
41	41	= Installing the deployment tools =
42	42
43		-We are now ready to install the deployment tools. The wiki have installation instructions for many platforms, so jump over to the instructions for your deployment platform. Running the deployment tools (at least wotaskd and the Apache module) is also useful on your development machine.
	43	+We are now ready to install the deployment tools. The wiki has installation instructions for many platforms, so jump over to the instructions for your deployment platform. Running the deployment tools (at least wotaskd and the Apache module) is also useful on your development machine.
44	44
45		-* [[Installing on Mac OS X>>WO:Deploying on Mac OS X Server]]
46		-* [[Installing on Linux>>WO:Installing WebObjects 5.4 on Linux]]
47		-* [[Installing on Windows>>WO:Deploying on Windows]]
48		-* [[Installing on FreeBSD>>WO:Deploying on FreeBSD 8.2 and WebObjects 5.4.3]]
	45	+* [[Installing on Mac OS X>>Deploying on Mac OS X 10.6 (Snow Leopard)]]
	46	+* [[Installing on Linux>>Deploying on Linux]]
	47	+* [[Installing on Windows>>Deploying on Windows]]
	48	+* [[Installing on FreeBSD>>Deploying on FreeBSD 8.2 and WebObjects 5.4.3]]
49	49
50	50	= Configuring the applications with JavaMonitor =
51	51
...	...	@@ -52,7 +52,7 @@
52	52	Before adding the application into JavaMonitor, you have to copy the applications on the deployment server. You can use any tools that you usually use to copy files on the remote server (scp, rsync, CyberDuck, etc.). Usually you need to copy the application to the following remote directory:
53	53
54	54	* /Library/WebObjects/Applications (on OS X)
55		-* /opt/Local/Library/WebObjects/Applications (on other UNIX systems than OS X, like Linux, BSD or Solaris)
	55	+* /opt/Local/Library/WebObjects/Applications (on UNIX systems other than OS X, like Linux, BSD or Solaris)
56	56
57	57	Copy the **BlogRest-Application.tar.gz** archive into the correct directory from the above list and uncompressed it (//tar zxf BlogRest-Application.tar.gz//). This will create a new directory named **BlogRest.woa**.
58	58
...	...	@@ -67,7 +67,7 @@
67	67	Usually, the Web server resources goes to:
68	68
69	69	* /Library/WebServer/Documents/WebObjects (on OS X)
70		-* /opt/Local/Library/WebServer/Documents/WebObjects (on other UNIX systems than OS X, like Linux, BSD or Solaris)
	70	+* /opt/Local/Library/WebServer/Documents/WebObjects (on UNIX systems other than OS X, like Linux, BSD or Solaris)
71	71
72	72	Copy the **BlogRest-WebServerResources.tar.gz** archive into the correct directory from the above list and uncompressed it (//tar zxf BlogRest-WebServerResources.tar.gz//). Doing this command will result in a new directory called **BlogRest.woa**.
73	73
...	...	@@ -78,7 +78,7 @@
78	78	You will get to a page where you need to specific the path to the launch script inside the application bundle. If the development server is on OS X, the path will be:
79	79
80	80	{{code}}
81		-/Library/WebServer/Documents/WebObjects/BlogRest.woa/BlogRest
	81	+/Library/WebObjects/Applications/BlogRest.woa/BlogRest
82	82	{{/code}}
83	83
84	84	Put that path in the text field next to the **MacOSX** label.
...	...	@@ -86,7 +86,7 @@
86	86	On other UNIXs, the path is:
87	87
88	88	{{code}}
89		-/opt/Local/Library/WebServer/Documents/WebObjects/BlogRest.woa/BlogRest
	89	+/opt/Local/Library/WebObjects/Applications/BlogRest.woa/BlogRest
90	90	{{/code}}
91	91
92	92	Put that path in the text field next to the **Unix** label.
...	...	@@ -108,7 +108,7 @@
108	108	{{code}}
109	109
110	110	sudo su - appserver
111		-cd /Library/WebServer/Documents/WebObjects/BlogRest.woa/
	111	+cd /Library/WebObjects/Applications/BlogRest.woa/
112	112	./BlogRest
113	113
114	114	{{/code}}
...	...	@@ -118,7 +118,7 @@
118	118	{{code}}
119	119
120	120	sudo su - appserver
121		-cd /opt/Local/Library/WebServer/Documents/WebObjects/BlogRest.woa/
	121	+cd /opt/Local/Library/WebObjects/Applications/BlogRest.woa/
122	122	./BlogRest
123	123
124	124	{{/code}}