Skip to Content

Changes for page Your First Deployment

Last modified by Pascal Robert on 2013/04/21 13:53
From version 12.1
edited by Ray Kiddy
on 2012/01/10 11:23
Change comment: grammar
To version 18.1
edited by Bastian Triller
on 2013/04/21 13:53
Change comment: Migrated to Confluence 5.3

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +Getting Started
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kiddyr
1 +XWiki.btriller
Tags
... ... @@ -1,0 +1,1 @@
1 +tutorials
Content
... ... @@ -1,10 +1,10 @@
1 1  {{warning}}
2 -Work in progress\!
2 +Work in progress!
3 3  {{/warning}}
4 4  
5 5  \\
6 6  
7 -{{toc}}{{/toc}}
7 +{{toc/}}
8 8  
9 9  = Introduction =
10 10  
... ... @@ -12,25 +12,25 @@
12 12  
13 13  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:
14 14  
15 -* 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 Wonder application
15 +* wotaskd. A daemon that acts as a watchdog to send lifebeat to the applications its manage + launching and stopping applications. Source code is available and it's actually a Project Wonder application!
16 16  
17 -* 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.
17 +* Module for your Web server software (Apache or IIS). If a module doesn't exist for your preferred Web server, you can use a CGI.
18 18  
19 -* JavaMonitor. A Web GUI to manage wotaskd configuration (which is a XML file). It's optional, and you can manage multiple instances of wotaskd with a single JavaMonitor installation. JavaMonitor also have REST APIs so that you can manage the configuration by command-line or by a JavaScript app.
19 +* JavaMonitor. A Web GUI to manage wotaskd configuration (which is a XML file). It's optional, and you can manage multiple instances of wotaskd with a single JavaMonitor installation. JavaMonitor also has REST APIs so that you can manage the configuration by command-line or by a JavaScript app.
20 20  
21 21  But first, we need to actually make our projects ready for deployment.
22 22  
23 23  = Building the "products" =
24 24  
25 -When you run your projects inside Eclipse, it uses 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.
25 +When you run your projects inside Eclipse, it uses 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.
26 26  
27 27  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.
28 28  
29 -In Eclipse, right-click on the **BlogCommon** project, and select **WOLips Ant Tools** > **Install**.
29 +In Eclipse, right-click on the **BlogCommon** project, and select **WOLips Ant Tools** -> **Install**.
30 30  
31 31  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**.
32 32  
33 -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:
33 +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:
34 34  
35 35  * a .woa (in our case: **BlogRest.woa**) that is a regular application bundle.
36 36  * a tar+gzip archive of the application (in our case: **BlogRest-Application.tar.gz**)
... ... @@ -40,12 +40,12 @@
40 40  
41 41  = Installing the deployment tools =
42 42  
43 -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.
43 +We are now ready to install the deployment tools. The wiki has 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.
44 44  
45 -* [[Installing on Mac OS X>>WO:Deploying on Mac OS X Server]]
46 -* [[Installing on Linux>>WO:Installing WebObjects 5.4 on Linux]]
47 -* [[Installing on Windows>>WO:Deploying on Windows]]
48 -* [[Installing on FreeBSD>>WO:Deploying on FreeBSD 8.2 and WebObjects 5.4.3]]
45 +* [[Installing on Mac OS X>>doc:documentation.Deploying on Mac OS X 10\.6 (Snow Leopard)]]
46 +* [[Installing on Linux>>doc:documentation.Deploying on Linux]]
47 +* [[Installing on Windows>>doc:documentation.Deploying on Windows]]
48 +* [[Installing on FreeBSD>>doc:documentation.Deploying on FreeBSD 8\.2 and WebObjects 5\.4\.3]]
49 49  
50 50  = Configuring the applications with JavaMonitor =
51 51  
... ... @@ -52,7 +52,7 @@
52 52  Before adding the application into JavaMonitor, you have to copy the applications on the deployment server. You can use any tools that you usually use to copy files on the remote server (scp, rsync, CyberDuck, etc.). Usually you need to copy the application to the following remote directory:
53 53  
54 54  * /Library/WebObjects/Applications (on OS X)
55 -* /opt/Local/Library/WebObjects/Applications (on other UNIX systems than OS X, like Linux, BSD or Solaris)
55 +* /opt/Local/Library/WebObjects/Applications (on UNIX systems other than OS X, like Linux, BSD or Solaris)
56 56  
57 57  Copy the **BlogRest-Application.tar.gz** archive into the correct directory from the above list and uncompressed it (//tar zxf BlogRest-Application.tar.gz//). This will create a new directory named **BlogRest.woa**.
58 58  
... ... @@ -67,11 +67,11 @@
67 67  Usually, the Web server resources goes to:
68 68  
69 69  * /Library/WebServer/Documents/WebObjects (on OS X)
70 -* /opt/Local/Library/WebServer/Documents/WebObjects (on other UNIX systems than OS X, like Linux, BSD or Solaris)
70 +* /opt/Local/Library/WebServer/Documents/WebObjects (on UNIX systems other than OS X, like Linux, BSD or Solaris)
71 71  
72 72  Copy the **BlogRest-WebServerResources.tar.gz** archive into the correct directory from the above list and uncompressed it (//tar zxf BlogRest-WebServerResources.tar.gz//). Doing this command will result in a new directory called **BlogRest.woa**.
73 73  
74 -Everything on the file system is ok, the next step is to add the application to JavaMonitor. If the development tools have been installed correctly, JavaMonitor will run on port 56789 on your deployment server. For example, if the DNS name of your deployment server is my.host.com, the URL will be [[http://my.host.com:56789]]
74 +Everything on the file system is ok, the next step is to add the application to JavaMonitor. If the development tools have been installed correctly, JavaMonitor will run on port 56789 on your deployment server. For example, if the DNS name of your deployment server is my.host.com, the URL will be [[http:~~/~~/my.host.com:56789>>url:http://my.host.com:56789||shape="rect"]]
75 75  
76 76  After the **Add Application Named** label, enter **BlogRest** into the text field and click **Add Application**.
77 77  
... ... @@ -78,7 +78,7 @@
78 78  You will get to a page where you need to specific the path to the launch script inside the application bundle. If the development server is on OS X, the path will be:
79 79  
80 80  {{code}}
81 -/Library/WebServer/Documents/WebObjects/BlogRest.woa/BlogRest
81 +/Library/WebObjects/Applications/BlogRest.woa/BlogRest
82 82  {{/code}}
83 83  
84 84  Put that path in the text field next to the **MacOSX** label.
... ... @@ -86,7 +86,7 @@
86 86  On other UNIXs, the path is:
87 87  
88 88  {{code}}
89 -/opt/Local/Library/WebServer/Documents/WebObjects/BlogRest.woa/BlogRest
89 +/opt/Local/Library/WebObjects/Applications/BlogRest.woa/BlogRest
90 90  {{/code}}
91 91  
92 92  Put that path in the text field next to the **Unix** label.
... ... @@ -97,7 +97,7 @@
97 97  
98 98  The next step is to click on the **Push All** button, which saves the application configuration. Now, we can add instances of the application. To do so, click on the **Detail View** link.
99 99  
100 -You will see a section saying Add: 1 instance(s) on host: . Click the **Add** button. That will add one instance of the application. It's possible to run multiple instances of an application, mainly to load balance requests and also to have other working instances in case an instance is going AWOL. But for now, running one instance is enough.
100 +You will see a section saying _Add: 1 instance(s) on host: _. Click the **Add** button. That will add one instance of the application. It's possible to run multiple instances of an application, mainly to load balance requests and also to have other working instances in case an instance is going AWOL. But for now, running one instance is enough.
101 101  
102 102  If the application launches successfully, a link on the application name will appear after 30 seconds in JavaMonitor. If a link does not appear after a minute and the status is still **STOP**, something is wrong. Check the log that was created in /tmp (the log should be /tmp/WOCommunity-1) to check for any errors.
103 103  
... ... @@ -108,7 +108,7 @@
108 108  {{code}}
109 109  
110 110  sudo su - appserver
111 -cd /Library/WebServer/Documents/WebObjects/BlogRest.woa/
111 +cd /Library/WebObjects/Applications/BlogRest.woa/
112 112  ./BlogRest
113 113  
114 114  {{/code}}
... ... @@ -118,7 +118,7 @@
118 118  {{code}}
119 119  
120 120  sudo su - appserver
121 -cd /opt/Local/Library/WebServer/Documents/WebObjects/BlogRest.woa/
121 +cd /opt/Local/Library/WebObjects/Applications/BlogRest.woa/
122 122  ./BlogRest
123 123  
124 124  {{/code}}