root/tags/release-0.13.32/pfixcore/INSTALL

Revision 3851, 5.1 KB (checked in by smarsching, 4 years ago)

Updated required Ant version in INSTALL file

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1
2This file describes how to get the package up and running.
3
4Prerequisites:
5
6        * A unixoid OS.  Yes, Java should be platform independent.
7          Unfortunately portions of the build environment and code
8          require a unix-like shell. Running Pustefix on Windows might
9          work using Cygwin, but we haven not tried yet. If you succeed
10          in running Pustefix on Windows, we would like to hear.
11
12        * A Java installation.  Version 1.5 is required and version 1.6
13          is recommended. The environment variable JAVA_HOME must be
14          set to the root directory of your java installation.
15         
16        * Apache Ant, the Java-based build tool in version 1.7.0 or higher.
17          If you have really large projects consider increasing the memory
18          for the java vm ant runs in: To do this set the ANT_OPTS
19          environment variable to something like "-mx200m". This variable
20          is evaluated within the ant start script contained in the ant
21          distribution.
22
23        * If you want to use Pustefix with the Apache HTTP daemon, either
24          mod_proxy_ajp or mod_jk have to be installed and loaded.
25          However, you can simply run Pustefix without Apache by setting
26          the standalone.tomcat property to true when running "ant".
27          Tomcat will listen for incoming HTTP connections on port 8080
28          and for HTTPS connections on port 8443.
29         
30          If you are using Apache, name-based virtual servers have to be
31          enabled for the default address of your machine.
32         
33          Note that there have been problems with the order of
34          inclusion of mod_rewrite and mod_jk in the Apache configuration
35          file. It seems that mod_jk needs to be loaded
36          BEFORE mod_rewrite. If you experience problems, try changing
37          the order of these two modules.  Other problems that have
38          been experienced are related to a changed regexp syntax
39          between different versions of mod_rewrite. You may have to
40          customize the relevant regexps in the file core/build/create_apacheconf.xsl.
41         
42        * You should have a "* entry" for your machine in DNS (This means that
43          a lookup to NAME.HOSTNAME.DOMAIN should resolve to HOSTNAME.DOMAIN no
44          matter what NAME is). If you don't have DNS configured like this you can
45          still supply the names (e.g. "cms.HOSTNAME.DOMAIN" or
46          "sample1.HOSTNAME.DOMAIN") via your /etc/hosts file.
47         
48        * NOTE: you don't need a external installation of Tomcat,
49          everything you need is contained in this package.  We suggest
50          that even if you have your own Tomcat setup already,
51          start by using the supplied versions, and, if all goes
52          well, you can try to move the configuration into your own
53          installation.
54
55        * NOTE2: you don't need any additional jar files or classes besides
56          what is supplied with your java installation and this package.
57 
581)  Type "ant" to generate all neccesary files and compile all classes.
59
602)  You may want to type "ant generate" for pre-processing all the templates
61    up-front. This speeds up the first hit of a page in the sample
62    applications as the page doesn't need to be build from scratch then.
63
643)  Put something  like the following
65
66        NameVirtualHost HOSTNAME.DOMAIN:80
67        # uncomment if you want to use SSL
68        # NameVirtualHost HOSTNAME.DOMAIN:443
69
70        # config for mod_jk
71        Include <your path to this directory>/projects/servletconf/tomcat/jk.conf
72
73        # virtual hosts:
74        Include <your path to this directory>/projects/servletconf/tomcat/apache.conf
75
76    into your Apache configuration. Don't forget to restart apache.
77    Modern apache installations often have a httpd.conf.d directory where
78    to put links to config files that should be included automatically.
79    In this case you can link the two files there instead of including them
80    via your http.conf
81
824)  Start Tomcat with the following command:
83
84        ./startTomcat.sh
85
86    Note: For stopping Tomcat, just press Control-C to interrupt the script.
87       
885)  To see if everything works, you can try to open the editor
89    application. Point your browser to
90       
91        http://cms.HOSTNAME.DOMAIN
92
936)  You will find some basic applications in the example.tar.gz.
94    Just unpack the file with "tar xvzf example.tar.gz" in your skel/projects
95    directory and take a short look to the README_EXAMPLES.txt included in the
96    tar afterwards.
97   
987)      Creating your own pustefix project is really simple. If you're in
99        the skel dir just type in "./newproject.sh"
100        and follow the command-line
101        instructions.
102        Afterwards run ant, restart apache, restart tomcat and type in
103                http://myprojectname.HOSTNAME.DOMAIN
104               
105        To see how it works you should take a short look in
106        de.schlund.pfixcore.util.basicapp.
107        If you start with InitNewPfixProject.java (in the package basics) it should
108        be easy to understand the way to go
109   
110    Have Fun.
111
112
113FINAL NOTE:
114
115You can now start building your own applications. Some tutorials as well as the
116reference documentation can be found on http://www.pustefix-framework.org/.
117
Note: See TracBrowser for help on using the browser.