...
Note |
---|
The version numbers indicated below are from the version of the quickstart distribution as of the last time this page was edited. The version numbers will most likely be diffrent depending on which version you have downloaded |
What is included?
The uPortal-only distribution is downloaded as a zip file which extracts to directory called uPortal_rel-2-5-1.zip
. The directory contains the following...
...
What do you need to know?
Use of this distribution requires knowledge of J2EE environments and the Ant tool from the Apache Jakarta project.
...
- The Java Development Kit (JDK) version 1.4 or higher must be installed. For version 2.5.1 and later JDK 1.5 is preferred. JDK version 1.4 is preferred for earlier versions of uPortal.
- JAVA_HOME environment variable must be set.
- The Jakarta-Ant build tool (version 1.6.2 or later).
- A web application environment such as Tomcat or IBM Websphere
- An SQL database such as HypersonicSQL, Oracle, or PostgreSQL
...
Compiling and deploying uPortal is managed using the Jakarta Ant build environment. It is highly recommended that anyone implementing uPortal or developing channels become familiar with the Ant build tool. Documentation for Ant is available at Jakarta-Ant web site
Warning | ||
---|---|---|
| ||
Do not blindly run the ant build against a production database. There are Ant targets in this build Do not blindly run the ant build on a production system. There are Ant targets in this build which Backup your work before running builds. |
For detailed instructions on how to compile and deploy uPortal go to the documentation page at:
Initial Deployment
You must run the initportal target before uPortal is started the first time.
This target will take care of compiling, deploying, database population and
other initial tasks. Running initportal again is similiar to hitting a reset
button on the portal. Any saved configuration in the portal is lost and a clean
version of the portal is configured.
Setting up A Database
The uPortal system can be deployed such that a database from several different vendors may be used. Installation and configuration information about databases can be found on the:
05 Database Configuration page.
Complete the Installation
Once you have compiled and deployed uPortal and setup a database for it to utilize, you still need to publish the channel fragments and internationalize the database. This can be done in one step by issuing the `ant initportal` command. Once this command completes without errors, your uPortal instance should be fully functional.
Logging
The ant build copies /properties/Logger.properties to the root of the classes directory so that the resulting log4j.properties file will be available on the classpath for Commons Logging / log4j to find. You'll need to either change that configuration in Logger.properties before the build or to change it in /WEB-INF/classes/ afterwards. You can configure the logging level, where the file should be, or even choose a different logging approach (log via XML to a ChainSaw instance, say).
Tip |
---|
The Logger.properties file comes configured such that the portal.log file is written in a directory relative to where to web application server was started. You may wish to modify the following line such that it references an absolute file page: log4j.appender.R.File=portal.log |
Issues and known problems
...