Skip to Content

Changes for page Your First Deployment

Last modified by Pascal Robert on 2013/04/21 13:53
From version 10.1
edited by Pascal Robert
on 2012/01/08 08:06
Change comment: There is no comment for this version
To version 8.1
edited by Pascal Robert
on 2012/01/08 07:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,7 +10,7 @@
10 10  
11 11  We will focus on the classic tools since this is the method that the majority of the community use. The classic deployment tools consists of:
12 12  
13 -* wotaskd. A daemon that act as a watchdog to send lifeboat to the applications its manage + launching and stopping applications. Source code is available and it's actually a Project Application application
13 +* wotaskd. A daemon that act as a watchdog to send lifeboat to the applications its manage + launching and stopping applications. Source code is available and it's actually a Project Application application!
14 14  
15 15  * Module for your Web server software (Apache or IIS). If a module don't exist for your preferred Web server, you can use a CGI.
16 16  
... ... @@ -20,29 +20,29 @@
20 20  
21 21  = Building the "products" =
22 22  
23 -When you run your projects inside Eclipse, they use the incremental builder and the "internal builds" are not ready for deployment (e.g. don't use the build from the "build" folder of the project, it's not a complete build). You need to use Ant or Maven to actually build a full "product". Let's focus on Ant because, again, this is what the majority use. You can also use Jenkins, but Jenkins will need to call Maven or Ant to build the projects anyway.
23 +When you run your projects inside Eclipse, they use the incremental builder and the "internal builds" are not ready for deployment (e.g. don't use the build from the "build" folder of the project, it's not a complete build!). You need to use Ant or Maven to actually build a full "product". Let's focus on Ant because, again, this is what the majority use. You can also use Jenkins, but Jenkins will need to call Maven or Ant to build the projects anyway.
24 24  
25 25  One important thing to remember is that you need to build and install the frameworks before your build your applications. Building your applications will NOT add the frameworks to the product if you didn't build the frameworks first. So let's build and install the **BlogCommon** framework first.
26 +
27 +In Eclipse, right-click on the **BlogCommon** project, and select **WOLips Ant Tools** -> **Install**.
26 26  
27 -In Eclipse, right-click on the **BlogCommon** project, and select **WOLips Ant Tools** > **Install**.
29 +By calling this, Eclipse will call Ant to build the framework and install it in (on OS X) **/Library/Frameworks**, so the framework should be at **/Library/Frameworks/BlogCommon.framework**.
28 28  
29 -By calling this, Eclipse will call Ant to build the framework and install it in (on OS X) **/Library/Frameworks**, so the framework should be at **/Library/Frameworks/BlogCommon.framework**.
31 +You are now ready to build the applications. The procedure is the same as for frameworks, so right-click on the **BlogRest** project, and select **WOLips Ant Tools** -> **Install**. The application will install itself in (on OS X) **/Library/WebObjects/Applications/**. But there's a difference with a build for a framework: building an application will build three products:
30 30  
31 -You are now ready to build the applications. The procedure is the same as for frameworks, so right-click on the **BlogRest** project, and select **WOLips Ant Tools** > **Install**. The application will install itself in (on OS X) **/Library/WebObjects/Applications/**. But there's a difference with a build for a framework: building an application will build three products:
32 -
33 33  * a .woa (in our case: **BlogRest.woa**) that is a regular application bundle.
34 34  * a tar+gzip archive of the application (in our case: **BlogRest-Application.tar.gz**)
35 35  * a tar+gzip archive of the Web server resources (the files that are in the **WebResources** folders of your projects). That file is name **<ApplicationName>-WebServerResources.tar.gz** (so in our case, **BlogRest-WebServerResources.tar.gz**).
36 36  
37 -The tar archive exists to make it faster to copy the application to your deployment server because it's two files instead of hundred and they are compressed.
37 +The tar archive exists to make it faster to copy the application to your deployment server because it's two files instead of hundred and they are compressed.
38 38  
39 39  = Installing the deployment tools =
40 40  
41 -We are now ready to install the deployment tools. The wiki have installation instructions for many platforms, so jump over to the instructions for your deployment platform. Running the deployment tools (at least wotaskd and the Apache module) is also useful on your development machine.
41 +We are now ready to install the deployment tools. The wiki have installation instructions for
42 42  
43 -* [[Installing on Mac OS X>>WO:Deploying on Mac OS X Server]]
44 -* [[Installing on Linux>>WO:Installing WebObjects 5.4 on Linux]]
45 -* [[Installing on Windows>>WO:Deploying on Windows]]
46 -* [[Installing on FreeBSD>>WO:Deploying on FreeBSD 8.2 and WebObjects 5.4.3]]
43 +* Installing on Mac OS X
44 +* Installing on Linux
45 +* Installing on Windows
46 +* Installing on BSD
47 47  
48 48  = Configuring the applications with JavaMonitor =