Skip to Content

Changes for page Deployment-Book

Last modified by Aaron Rosenzweig on 2012/01/23 04:38
From version 11.1
edited by Pascal Robert
on 2011/05/08 23:01
Change comment: There is no comment for this version
To version 7.1
edited by Pascal Robert
on 2011/05/08 23:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,7 +9,9 @@
9 9  * wotaskd
10 10  * JavaMonitor
11 11  
12 -For a deployment-like environment on your deployment box, JavaMonitor is not needed, but you do need wotaskd, the Web server and the module. (link to apache setup in the wiki)
12 +For a deployment-like environment on your deployment box, JavaMonitor is not needed, but you do need wotaskd, the Web server and the module.
13 +[[WO:WO 5.4 Getting Started]]
14 +[[WO:Running Through Apache - Leopard & Snow Leopard Client - Summary]]
13 13  
14 14  == Why Deployment at the Beginning? ==
15 15  
... ... @@ -81,10 +81,14 @@
81 81  
82 82  == SSL Configuration ==
83 83  
84 -It's useful to create a https configuration on your deployment-like setup. By doing that, you can try out switching between SSL and non-SSL and make sure that switching is working well. On your development box, no need to purchase a SSL certificate, you can create a self-signed certificate for free. To create a self-signed certificate on OS X, do the following:
86 +It's useful to create a https configuration on your deployment-like setup. By doing that, you can try out switching between SSL and non-SSL and make sure that switching is working well. On your development box, no need to purchase a SSL certificate, you can create a self-signed certificate for free. To create a self-signed certificate on OS X, check [[this page>>http://wiki.objectstyle.org/confluence/display/WO/Development-SSL+requests+via+https+protocol]].
85 85  
86 -== Deployment Components: JavaMonitor, Wotaskd and javawoservice ==
88 +{{code}}
87 87  
90 +Deployment Components: JavaMonitor, Wotaskd and javawoservice
91 +
92 +{{/code}}
93 +
88 88  == Setting up JavaMonitor ==
89 89  
90 90  == Editing spawnofwotaskd.sh ==
... ... @@ -104,7 +104,7 @@
104 104  
105 105  The first thing to do when an application doesn't launch by JavaMonitor/wotaskd is to launch it by command line. To do so, open a command line shell, logging as the "appserver" and start the launch script manually. For example, if you have an application named "MyApp.woa" in /Library/WebObjects/Applications, do the following commands:
106 106  
107 -* sudo --s--
113 +* sudo s
108 108  * su - appserver
109 109  * cd /Library/WebObjects/Applications/MyApp.woa
110 110  * ./MyApp
... ... @@ -119,7 +119,7 @@
119 119  
120 120  Using a continuous build system is useful. Many people in the community don't even build their applications on their development boxes anymore, they use a continuous build system to build projects from a source control repository. This is even more useful if you have more than one developer working on your projects, by centralizing builds, you can detect source merge problems, etc. You can even run unit tests and do deployments from a build system.
121 121  
122 -The most popular continuous build system is Jenkins. It's an open source project build in Java, with many useful plugins.
128 +The most popular continuous build system is Jenkins. It's an open source project build in Java, with many useful plugins.
123 123  
124 124  == Using a staging server ==
125 125