Skip to Content

Changes for page Overview

Last modified by Pascal Robert on 2012/12/05 12:01
From version 23.1
edited by smmccraw
on 2007/07/08 09:45
Change comment: There is no comment for this version
To version 24.1
edited by Pascal Robert
on 2007/09/03 21:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Programming__WebObjects-Web Applications-Deployment-Overview
1 +Web Applications-Deployment-Overview
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.smmccraw
1 +XWiki.probert
Content
... ... @@ -12,38 +12,37 @@
12 12  
13 13  For the application server:
14 14  
15 -{{panel}}
15 +{{code}}
16 16  
17 - MyProject.woa
18 - MyProject - a Unix shell script to which control is initially passed and which sets up the execution environment under Unix
19 - MyProject.CMD - a DOS command script to which control is initially passed and which sets up the execution environment under DOS/Windows
20 - WOBootstrap.jar - a jar file containing a single class called JavaArchiveFilter that implements the java.io.FilenameFilter interface
21 - Contents - a directory containing all of the files necessary to support the execution of the WO app
22 - Info.plist - a property list file for the application
23 - MacOS/
24 - MyProject - a Unix shell script identical to that of the same name at the top level of the project directory
25 - MacOSClassPath.txt - text file containing the derived Java ClassPath for the project
26 - PkgInfo - a text file containing the four letter package type (APPL = application) and the application's four letter file types
27 - Resources/ - a directory containing the WOComponents and other resources in the Resources group of the Groups & Files pane
28 - UNIX/ - a directory similar to the MacOS directory but used for deployment on Unix systems
29 - Windows/ - a directory similar to the MacOS directory but used for deployment on Windows systems
30 - pbdevelopment.plist - an XML file with a single element whose key is PBXProjectSourcePath and whose value is implied by the name.
17 + MyProject.woa
18 + MyProject - a Unix shell script to which control is initially passed and which sets up the execution environment under Unix
19 + MyProject.CMD - a DOS command script to which control is initially passed and which sets up the execution environment under DOS/Windows
20 + WOBootstrap.jar - a jar file containing a single class called JavaArchiveFilter that implements the java.io.FilenameFilter interface
21 + Contents - a directory containing all of the files necessary to support the execution of the WO app
22 + Info.plist - a property list file for the application
23 + MacOS/
24 + MyProject - a Unix shell script identical to that of the same name at the top level of the project directory
25 + MacOSClassPath.txt - text file containing the derived Java ClassPath for the project
26 + PkgInfo - a text file containing the four letter package type (APPL = application) and the application's four letter file types
27 + Resources/ - a directory containing the WOComponents and other resources in the Resources group of the Groups & Files pane
28 + UNIX/ - a directory similar to the MacOS directory but used for deployment on Unix systems
29 + Windows/ - a directory similar to the MacOS directory but used for deployment on Windows systems
30 + pbdevelopment.plist - an XML file with a single element whose key is PBXProjectSourcePath and whose value is implied by the name.
31 31  
32 -{{/panel}}
32 +{{/code}}
33 33  
34 34  For the Web Server:
35 35  
36 -{{panel}}
36 +{{code}}
37 37  
38 - MyProject.woa
39 - Contents - a directory containing all of the files necessary to support the execution of the WO app
40 - WebServerResources/
41 - Hierarchy of files and folders containing static web resources.
38 + MyProject.woa
39 + Contents - a directory containing all of the files necessary to support the execution of the WO app
40 + WebServerResources/
41 + Hierarchy of files and folders containing static web resources.
42 42  
43 -{{/panel}}
44 44  
44 +{{/code}}
45 +
45 45  Although the packages are very different, they are identically named, have similar structures and are merged in development. They are typically ONLY separated like this for a split install. You typically put the application server package in /Library/WebObjects/Applications (or a local equivalent) and you typically put the WebServer package in /Library/WebServer/Documents/WebObjects.
46 46  
47 47  You can create these packages independently in various ways. I've found it easier, recently (because of various examples of Xcode intransigence) to simply build the project as I would for development and physically separate the two for deployment. Other people have various incantations to make a split install work reliably and I'm sure they will chime in here.
48 -
49 -Category:WebObjects