Skip to Content
Last modified by Pascal Robert on 2012/07/21 20:39
From version 26.1
edited by Kieran Kelleher
on 2007/12/10 22:18
Change comment: There is no comment for this version
To version 29.1
edited by Kieran Kelleher
on 2007/12/10 22:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -60,26 +60,16 @@
60 60  * Self-contained deployment bundles - all required frameworks are embedded - minimal dependency on target server configuration and versions. For example, there is no need to install Wonder frameworks on your deployment server since the ones you developed and tested with are embedded in the deployment bundles. Experience has shown that this improves consistency of deployment reliability.
61 61  * Compressed gzipped tar archives of both application and webserver bundles are created, ready for copying to target server(s)
62 62  ** This is easily decompressed on the server using
63 -** $ sudo tar xvzf bundle.tar.gz
63 +** $ sudo tar --xvzf bundle.tar.gz--
64 64  
65 65  == Anatomy of Embedded Split Install Bundles produced by this Ant Script ==
66 66  
67 -{{info title="The Deployment Files"}}
68 -
69 -The two compressed "ready-to-deploy" bundles are highlighted below
70 -!build_artifacts.jpg!
71 -
72 -{{/info}}
73 -
74 74  The notable aspects of the embedded build structure are shown below.
75 75  
76 76  === Application Bundle ===
77 77  
78 78  {{info title="Embedded Application Bundle Layout"}}
79 -
80 -!app_bundle_layout.jpg!
81 -* Opening the app executable (command line script at bundle root having the application name as its name) and looking at the end will reveal that the WOFrameworksBaseURL references the frameworks inside the webserver embedded bundle.
82 -* Examining the Contents/MacOS/MacOSClassPath.txt file will reveal that the java classpath refers to all the jars inside the embedded bundle.
72 + !app_bundle_layout.jpg!
83 83  
84 84  {{/info}}
85 85