Skip to Content

Changes for page Deployment-Book

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

Summary

Details

Page properties
Content
... ... @@ -9,9 +9,7 @@
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.
13 -[[WO:WO 5.4 Getting Started]]
14 -[[WO:Running Through Apache - Leopard & Snow Leopard Client - Summary]]
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)
15 15  
16 16  == Why Deployment at the Beginning? ==
17 17  
... ... @@ -83,14 +83,61 @@
83 83  
84 84  == SSL Configuration ==
85 85  
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]].
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:
87 87  
88 88  {{code}}
89 89  
90 -Deployment Components: JavaMonitor, Wotaskd and javawoservice
88 +# sudo openssl genrsa -out /etc/apache2/localhost.key 2048
91 91  
90 +# sudo openssl req -new -key /etc/apache2/localhost.key -out /etc/apache2/localhost.csr
91 +Country Name (2 letter code) [AU]: <your country code, eg: CA, US, etc.>
92 +State or Province Name (full name) [Some-State]: <full name of province or state>
93 +Locality Name (eg, city) []: <full city name>
94 +Organization Name (eg, company) [Internet Widgits Pty Ltd]: <your name>
95 +Organizational Unit Name (eg, section) []:
96 +Common Name (eg, YOUR name) []:localhost
97 +Email Address []: <your email address>
98 +
99 +# sudo openssl x509 -req -days 365 -in /etc/apache2/localhost.csr -signkey /etc/apache2/localhost.key -out /etc/apache2/localhost.crt
100 +
101 +# sudo chmod 600 /etc/apache2/localhost.key
102 +
92 92  {{/code}}
93 93  
105 +You know have a self-signed certificate that will be valid for 365 days. When your certificate expires, you only need to run the last command to generate a new one, no need to recreate a key or certificate request.
106 +
107 +Now, let's add that certificate to Apache configuration. Edit /etc/apache2/httpd.conf, and at the end, add:
108 +
109 +{{code}}
110 +
111 +Listen 127.0.0.1:443
112 +NameVirtualHost 127.0.0.1
113 +<VirtualHost 127.0.0.1:443>
114 +DocumentRoot "/Library/WebServer/Documents/"
115 +ServerName localhost
116 +<Directory "/Library/WebServer/Documents/">
117 +allow from all
118 +Options +Indexes
119 +</Directory>
120 +SSLEngine on
121 +SSLProtocol +SSLv3 +TLSv1
122 +SSLCertificateFile /private/etc/apache2/localhost.crt
123 +SSLCertificateKeyFile /private/etc/apache2/localhost.key
124 +</VirtualHost>
125 +
126 +{{/code}}
127 +
128 +And restart Apache:
129 +
130 +{{code}}
131 +
132 +apachectl configtest
133 +apachectl restart
134 +
135 +{{/code}}
136 +
137 +== Deployment Components: JavaMonitor, Wotaskd and javawoservice ==
138 +
94 94  == Setting up JavaMonitor ==
95 95  
96 96  == Editing spawnofwotaskd.sh ==