| Hi Mark, Couple of things to note. You've mentioned that you're embedding all frameworks, in which case you don't need to put the Wonder frameworks into /Library/Frameworks on the deployment machine, in fact you want not to. If you're embedding all frameworks, you can include different versions of the frameworks in different applications deployed on the same server. You also can update the Wonder frameworks in one application without having to rebuild and test all the other applications deployed on the same server. Second - when building from Eclipse (I'm assuming you're building from Eclipse with WOLips), right click on the build.xml file in the WOExplorer view, and choose WOLips Ant Tools -> Install... Confirm that any required packages are included (for example, of your application includes several custom frameworks, make sure they are all checked), and the application will be built into your local Library/WebObjects/Applications directory in several parts. YourApp-Applications.tar.gz - this is the .woa application bundle that should be copied to Library/WebObjects/Applications and expanded on the deployment machine YourApp-WebServerResources.tar.gz - this is the .woa bundle with only the WebServerResources contained in it, and this should be coped to Library/WebServer/Documents/WebObjects/ on the deployment server. NOTE: This assumes that Library/WebServer/Documents/ is the root for the domain your application is hosted from, for example - we host multiple sites on a deployment server, each having their own root directory, so each has their own nested WebObjects directory containing the web server resources for the app for that domain. Library/WebServer/Documents/_clientOne/WebObjects/clientOneApp.woa [containing just the web server resources] Library/WebServer/Documents/_clientTwo/WebObjects/clientTwoApp.woa Have a look in Server Admin on the deployment machine at the site configuration for the domain you're accessing the application through. If the Web folder: setting is anything deeper than/Library/WebServer/Documents, you'll need to move the /WebObjects/YourApp.woa - web server resources there too. The Ant build script sets the right permissions on everything for a default install, so you shouldn't have to change that. The only other thing that may throw you is that accessing the application through the link on WOMonitor may use a different URL path than the one you'll normally use, and may appear to not be working only because of the way you are accessing it. For example, if you've configured Java WOMonitor to use the server's IP address, then clicking an application link in WOMonitor to launch the app will use an URL of http://IP_Address/cgi-bin/WebObjects/YourApp to access the application, and if that path isn't configured on the server to access the same document root as http://Your_Domain/cgi-bin/WebObjects/YourApp - you'll get the application, but the relative URL's to the web server resources won't resolve properly. Be sure to test the application with the URL you intend to use for actual deployment to be sure it's actually not working before you try to fix it. Best,  On Aug 29, 2009, at 6:27 AM, Mark Ainge wrote: I have successfully deployed a webobjects app onto a OS 10.4 Server. The app launches and runs fine, but associated style sheets and images are not loaded. I have checked apaches logs and can see 404's for the images and stylesheet. |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
