Changes for page Development Tools-Running Through Apache

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Programming__WebObjects-Development Tools-Running Through Apache
	1	+Development Tools-Running Through Apache

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.mschrag
	1	+XWiki.kieran

Content

...	...	@@ -1,21 +1,33 @@
1		-If you are accessing your application with URLs that look like http:~/~/localhost:45437/cgi-bin/WebObjects/AppName.woa/ (with the xxx:portnum instead of xxxx/-portnum) ... then you are using the [[Evil Direct Connect>>Programming__WebObjects-Web Applications-Development-Direct Connect]]. See that page for why you don't want to be using Direct Connect. See this page for how to stop.
	1	+If you are accessing your application with URLs that look like [[http://localhost:45437/cgi-bin/WebObjects/AppName.woa/]] (with the xxx:portnum instead of xxxx/-portnum) ... then you are using the [[Evil Direct Connect>>Web Applications-Development-Direct Connect]]. See that [[page>>Web Applications-Development-Direct Connect]] for why you don't want to be using Direct Connect. See this page for how to stop.
2	2
3		-== Turn on Apache ==
	3	+A summary of the following steps that applies specifically to MacOS X 10.5.5 can be found here: [[Running Through Apache - Leopard Client 10.5.5 - Summary]]
4	4
5		-Go to **System Preferences -> Sharing -> Services** and turn on **Personal Web Sharing** if it is not already on.
	5	+= Turning on Apache =
6	6
	7	+Go to **System Preferences > Sharing > Services** and turn on **Personal Web Sharing** if it is not already on.
	8	+
	9	+When you turn on your web server, Apache will listen on the network interfaces that were configured when it starts. If you change networks, you may need to manually restart apache. You can do this by either stopping and restarting Personal Web Sharing, or you can run "apachectl restart" from the commandline as the root user. Because this can get annoying if you are working on a laptop, or periodically using VPN's, there are a couple ways to make this process easier.
	10	+
	11	+= Optional Extra Configuration: Explicitly Setting Your Hostname =
	12	+
7	7	{{info title="Useful Information"}}
8	8
9		-The following changes to your webserver are only required if you want your hostname to be stable across network changes. While this simplifies many aspects of development, it causes problems if you need to be able to access your webserver from a remote machine, including if you need to be able to test your web app from a Parallels VM.
	15	+The changes in this section are only required if you want your hostname to be stable across network changes. While this simplifies many aspects of development (like testing cookies and https), it may cause problems with those specific aspects (cookies, https, etc.) if you need to be able to access your dev machine from a remote machine, including if you need to be able to test your web app from a Parallels VM.
10	10
	17	+Bonjour Delays: Apparently the procedure here is also useful for preventing "Bonjour" delays when you launch the browser to test your app on your development machine.
	18	+
11	11	{{/info}}
12	12
13		-== Edit Apache Config ==
	21	+== Edit Apache Config ==
14	14
15		-Note: **Do NOT try to use the Bonjour / Rendezvous name of your machine in this step.** It will cause you grief. Accept this and don't even try. You have been warned.
	23	+{{warning title="Bonjour, comment ça va? .... Trés bien, merci!"}}
16	16
17		-Edit **/etc/httpd/httpd.conf**, find the line containing **ServerName** and change it to this:
	25	+*Do NOT try to use the Bonjour / Rendezvous name of your machine in this step.* It will cause you grief. Accept this and don't even try. You have been warned.
18	18
	27	+{{/warning}}
	28	+
	29	+Edit **/etc/httpd/httpd.conf**, find the line containing **ServerName** and change it to this. If you use Leopard (OS X 10.5), the file is at **/etc/apache2/httpd.conf**.
	30	+
19	19	{{code}}
20	20
21	21	ServerName localhost
...	...	@@ -22,16 +22,68 @@
22	22
23	23	{{/code}}
24	24
25		-That line may be commented out by default. You can simply uncomment it (remove the leading pound sign) and then restart apache:
	37	+That line may be commented out by default. You can simply uncomment it (remove the leading pound sign). You will also need to find this block
26	26
27	27	{{code}}
28	28
	41	+# First, we configure the "default" to be a very restrictive set of
	42	+# features.
	43	+#
	44	+<Directory />
	45	+ Options FollowSymLinks
	46	+ AllowOverride None
	47	+ Order deny,allow
	48	+ Deny from all
	49	+</Directory>
	50	+
	51	+{{/code}}
	52	+
	53	+And modify like so:
	54	+
	55	+{{code}}
	56	+
	57	+# First, we configure the "default" to be a very restrictive set of
	58	+# features.
	59	+#
	60	+<Directory />
	61	+ Options FollowSymLinks
	62	+ AllowOverride None
	63	+# Order deny,allow
	64	+# Deny from all
	65	+</Directory>
	66	+
	67	+{{/code}}
	68	+
	69	+Got to the very end of **/etc/apache2/httpd.conf** and add :
	70	+
	71	+{{code}}
	72	+
	73	+Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf
	74	+
	75	+{{/code}}
	76	+
	77	+Then restart apache:
	78	+
	79	+{{code}}
	80	+
29	29	sudo apachectl restart
30	30
31	31	{{/code}}
32	32
33		-== Tell wotaskd to Use Localhost Too ==
	85	+== Tell the adaptor to use localhost ==
34	34
	87	+Edit **/System/Library/WebObjects/Adaptors/Apache2.2/apache.conf** to make sure that your enabled/uncommented WebObjectsConfig property looks like this:
	88	+
	89	+{{code}}
	90	+
	91	+WebObjectsConfig http://localhost:1085 10
	92	+
	93	+{{/code}}
	94	+
	95	+(Note on Tiger, aka OS X 10.4.X, replace **Apache2.2** with **Apache** in the path above)
	96	+
	97	+== Tell wotaskd to Use Localhost Too ==
	98	+
35	35	Edit **/System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/Properties**
36	36
37	37	Add this line after the **WOPort=1085** one:
...	...	@@ -44,6 +44,8 @@
44	44
45	45	Now you need to restart wotaskd:
46	46
	111	+===== OS X Tiger 10.4 =====
	112	+
47	47	{{code}}
48	48
49	49	sudo systemstarter stop "WebObjects Services"
...	...	@@ -53,10 +53,36 @@
53	53
54	54	or
55	55
56		-restart wotaskd and womonitor with launchctl if your WebObjects install launches that way.
	122	+===== OS X 10.5 Leopard (where launchd is used to control wotaskd) =====
57	57
58		-== Finally, Configure your Application ==
	124	+{{code}}
59	59
	126	+sudo launchd stop com.webobjects.wotaskd
	127	+
	128	+{{/code}}
	129	+
	130	+launchd should automatically start wotaskd again for you if configured properly.
	131	+
	132	+You can check for whether wotaskd is running as a launchd job by typing
	133	+
	134	+{{code}}
	135	+
	136	+sudo launchctl list | grep webobjects
	137	+
	138	+{{/code}}
	139	+
	140	+which will give something like this:
	141	+
	142	+{{code}}
	143	+
	144	+43 - com.webobjects.wotaskd
	145	+
	146	+{{/code}}
	147	+
	148	+(In 10.5 it appears to be necessary to launch with launchctl. See [[Running Monitor and wotaskd on Mac OS X 10.5 "client">>WO 5.4 Getting Started||anchor="javamonitor"]]
	149	+
	150	+== Finally, Configure your Application ==
	151	+
60	60	Add or edit these launch parameters:
61	61
62	62	{{code}}
...	...	@@ -71,3 +71,25 @@
71	71	The WOPort is optional, but useful if you want consistent URLs for bookmarks and such. You can use any number you want, but it needs to be unique for each application you launch (or rather, you can only run one app instance on a given WOPort at a time). In WOLips, WOPort, WODirectConnectEnabled, and WOAdaptorURL already exist and just need to be updated. WOHost does not, and needs to be added. The dash in front of the name ("-WOHost") is important and must be in the name for the setting to work properly.
72	72
73	73	You may want to set this in your global WOLips settings so you don't have to set it every time you make a new launch configuration. You will need to go back and modify existing launch configurations with these settings even if you set it globally. Global settings only apply to newly created launch configurations.
	166	+
	167	+= Apache Restart =
	168	+
	169	+{{info title="Why would I need this?"}}
	170	+
	171	+If you have a laptop and you get an "Application cannot be found" or some such error in the browser after auto-switching networks (for example going from a work network to a home network), restarting apache can resolve the error condition most of the time. A script is shown below to do that.
	172	+If you already implemented the "localhost" explicit hostname setup above, then you will probably not need to bother with this section.
	173	+
	174	+{{/info}}
	175	+
	176	+== Making a restart script ==
	177	+
	178	+Create a script named /usr/local/bin/restartApache and set the contents to:
	179	+
	180	+{{code}}
	181	+
	182	+#!/bin/bash
	183	+/usr/sbin/apachectl stop
	184	+sleep 1
	185	+/usr/sbin/apachectl start
	186	+
	187	+{{/code}}