Jetspeed Learning Notes

Recently to the portal's Open source Project Jetspeed Web page to see his introduction, by the way to write down these jetspeed learning materials,

Jetspeed Learning Jetspeed requires beginners to understand the Apache MAVEN Project management tool and the Apache Ant Packaging Scripting tool. The project needs to be configured as follows: Ant1.5 or change the version Maven1.0.2 or higher java1.4.2_02 or higher Servlet2.4 work engine: tomcat5.5.x Jetty Websphere6.0 Geronimo JBoss Weblogic get maven needs to get the appropriate version of the MAVEN selection database in the http://maven.apache.org/Web site jetspeed security mode requires the database to authorize users to obtain basic user information. This safe mode requires that JDBC2.0 and above versions of the driver be required to run. The following databases are tested and can be used: Derby hsqldb-hypersonic SQL MySQL Oracle Postgres DB2 Sybase SQL Server jetspeed Project The default deployment database is configured as Derby. The selection of the database will be determined during the Jetspeed installation process. If you do not want to use the Derby database, you can select a different database during the installation process. Servlet engine Theoretically, the Jetspeed second-generation portals can run in any servlet container that supports servlet2.4 specifications. The servlet engines that have successfully deployed jetspeed two-generation portal applications are as follows: Tomcat5.5.8 or higher Jetty Websphere Geronimo JBossTomcat Configuration ProcessJETSPEED2 can manage portlet applications with Tomcat application managers, in order to be able to do this, users who require Tomcat administrator identity are ${org.apache.jetspeed.server.home}/conf/ Tomcat-users.xml in the file. Reference sample Tomcat-user.xml <tomcat-users> <role rolename= "manager"/> <user username= "J2deployer" XXXXXX "roles=" manager "/> </tomcat-user> username and password attribute values must conform to ${ Org.apache.jetspeed.services.autodeployment.user} and the specified value expressed in ${org.apache.jetspeed.services.autodeployment.user}.Windows Tomcat5.5.9 the deploymentFor proper redeployment and uninstall, in Windows Tomcat5.5.9 you need to set the global context property "Antijarlocking" as true reference ${org.apache.jetspeed.server.home}/ The Conf/context.xml configuration is as follows: <context antijarlocking= "true" > ... </Context>jetty- a servlet for fast test environments and products ContainerJetty is used for the deployment of a product, but it is more often used to quickly test the client, and it does not itself hinder the product's servlet container. It does not require any special configuration. Install Jetspeed from source or installation files you need to choose a type to install the Jetspeed, either the installation file, or the file with the source code, depending on what you want to do. If you modify the core functionality of Jetspeed or donate jetspeed development projects, you will need source code files. If you just use it to build your own personalized Enterprise Portal, you can choose the binary version of the jetspeed. Most people choose to install files. Jetspeed Build Your installation instructions will depend on whether you select a source code file or an installation file or binary fileJetspeed-2 the source of learning 1. naming habits and basic norms Code base specification Unless otherwise specified, you should run all the MAVEN build commands from the Jetspeed directory or from your personal portal file. In addition, in *nix or Windows systems, you must use "/" as the separator for the file. For example: C:/windows,/home naming convention The following is a list of commonly used naming conventions in this document. Variables are represented by ${some_variable}. This represents a setting in jetspeed or a representation in your environment. The properties file describes the meaning of these variables in detail. For example, the ${org.apache.jetspeed.server.home} variable either represents a more well-defined property in a property file or a variable name defined in the build process, or a variable name that is defined by other build files in the Jetspeed. ${user_home}: Represents the user's root directory, in Windows, which means that c:/documents and settins/${username},${username} represent the name you used to log on to Windows. ${user. Home} represents the same meaning as ${user_home} in this article. ${catalina_home}: This is the path to your Tomcat installation. For example: C:/tomcat. Source code Control (SVN) Subversion (SVN) is used to manage source code files in the Jetspeed project. SVN is similar to CVS. For those who prefer not to command lines for Windows systems, we recommend using TORTOISESVN, which can be used to plug into your Windows browser, and for those who use Eclipseide, Subclipse plug-ins are available for SVN. MAVEN is installed in this document, we don't discuss the details of maven. However, there are some standard Maven jargon that we feel we need to let you know. In this document, when you install MAVEN, the maven/directory will be created in your ${usre_home} directory, and you will see some of the content mentioned in the Maven knowledge base. In the maven/directory, you'll see a repository directory that Maven uses to store all of the downloaded jar files when you run your build file command. It's also where Maven places your jar files and war files. They will be stored in a directory-structured format: The jar file is ${groupid}/${projected}/jars/${projected}-${version}.jar, and the warThe file is ${groupid}/${projectid}/wars/${projectid}.war. Where ${groupid},${projectid} and ${version} variables will be discussed later in this file. Jar files and war files will also be created in your project/target directory.2.Jetspeed Construction and Maven-plugin the PropertiesAt the beginning of the period, you need to set several attributes: You can easily create your own portal with the Maven-plugin provided by Jetspeed2. It is also used when you build Jetspeed projects from source code. In fact, the jetspeed-2 build process is a personalized portal configuration and installation process. Jetspeed-2 's Maven-plugin defines the default value for most properties. When you download or verify the jetspeed-2 source tree, in the root file, you will see that it contains a project's property file. However, pre-announced: not all attributes provide a default value, you must specify the default values for some properties, and of course you will reassign the values of some other attributes. Take a look at the following instructions to set or reset the constructed or Maven-plugin properties in your ${user_home}/build.properties file. The portal properties that must be set are:

The full name of the

Property	description	default
org.apache.jetspeed.portal.home	maven-plugin Create or update folders for your portal MAVEN project structure (with goal J2:port Al.conf.project). It will be the place where you carry out all portal development For example:/home/myportal/	not default
ORG.APACHE.J Etspeed.portal.groupId	is the abbreviation for your portal project group. This value is used as the location identifier for the MAVEN Library folder store. Example: MyProjects	no default
org.apache.jetspeed.portal.artifactId	the abbreviation for your portal project, which is used as the Web application context name for the Portal war file. Example: Myportal	no default
org.apache.jetspeed.portal.name	Portal project. The This value is used to produce the title name of Javadoc. For example: my Test Portal	no default
org.apache.jetspeed.portal.currentVersion	The current version of your portal project. This value is used in the suffix of the file name generated by maven. Example: 1.0	no default

Optional Portal Configuration PropertiesThe following properties are all of the subfolders specified by ${org.apache.jetspeed.portal.home}, which are basically defined as follows:

Property	Description	Default Value
Org.apache.jetspeed.portal.conf.dir	The folder where the Maven-plugin'll generate and copy application server specific configuration files as a tomcat appli cation context descriptor. This folder and its contents are created or updated by plugin goal J2:portal.conf.tomcat.	Target/portal-conf
Org.apache.jetspeed.portal.sql.dir	The folder where the Maven-plugin would generate and copy portal and database server specific SQL DDL and DML scripts. This folder and its contents are always (re) created by plugin goal j2:portal.conf.sql.	Target/portal-sql
Org.apache.jetspeed.portal.db.dir	The folder where the Maven-plugin would create its build-in HSQLDB database (s). This folder and its contents are created or updated by plugin goal J2:start.production.server or j2:start.test.server.	Target/portal-db
Org.apache.jetspeed.portal.webapp.dir	The folder where the Maven-plugin would copy the standard Jetspeed Web application resources. This folder and its contents are created or updated by plugin goal J2:portal.copy.webapp.	Target/${org.apache.jetspeed.portal.artifactid}
Org.apache.jetspeed.portal.target.dir	The folder where the Maven-plugin would generate and copy runtime Portal configuration files. These configuration files contain values derived from Build/plugin properties for the portal and OJB. This folder and its contents are created or updated by plugin goal J2:portal.conf.jetspeed and goal.	Target/${org.apache.jetspeed.portal.artifactid}

properties of the required application serverNote: Maven-plugin now supports only Tomcat servers 5.0.x or 5.5.x.

Property	Description	Default Value
Org.apache.jetspeed.server.home	The root folder of your Tomcat server installation. Example: ${catalina_home}/.	Not default
Org.apache.jetspeed.server.shared	The location of the the shared jars in your Tomcat installation. Example: ${org.apache.jetspeed.server.home}/shared/lib/	Not default
Org.apache.jetspeed.deploy.war.dir	The location of Web applications in your Tomcat installation. Example: ${org.apache.jetspeed.server.home}/webapps/	Not default
Org.apache.jetspeed.services.autodeployment.user	A Tomcat user with the manager role. Used to access the Tomcat Manager application from within the portal, explained below.	Not default
Org.apache.jetspeed.services.autodeployment.password	The password of the Tomcat user above. Used to access the Tomcat Manager application from within the portal, explained below.	Not default
Org.apache.jetspeed.catalina.version.major	The major version of the TOMCAT server you are Using:5 or 5.5 example:5.5	Not default

Optional database server Properties Jetspeed-2 and its maven-plugin provided and used default database is HSQLDB, if you want to use a different database, you need to overwrite the following attributes;

Property	Description	Default Value
Org.apache.jetspeed.production.database.default.name	The type of database you are using. Used for SQL script generation with Torque. Currently supported databases (with corresponding Torque target database name): •         Hsql (Hypersonic) ·         Oracle (Oracle) ·         MySQL (MySQL) ·         Postgres (Postresql) · MSSQL (MSSQL)	Hsql
Org.apache.jetspeed.production.database.url	The JDBC Connection URL	jdbc:hsqldb:hsql://127.0.0.1:9001
Org.apache.jetspeed.production.database.user	The database user name to connect with.	Sa
Org.apache.jetspeed.production.database.password	The database user its password to connect with.	Empty
Org.apache.jetspeed.production.database.driver	The JDBC Driver class name	Org.hsqldb.jdbcDriver
Org.apache.jetspeed.production.jdbc.drivers.path	A Java classpath style path to the JDBC driver classes or jar (s) needed for connecting to the database. Example:/lib/ojdbc14.jar;/lib/nls_charset12.jar	Empty

One example: a miniature portal the configuration You must first determine that you have defined the required attributes as described above in your ${user_home}/build.properties file. The miniature Portal configuration uses the HSQLDB database, and its properties are described as follows: # Required Portal Configuration properties           org.apache.jetspeed.portal.home       =/home/myportal/ org.apache.jetspeed.portal.groupid     = MyProjects Org.apache.jetspeed.portal.artifactId     = Myportal org.apache.jetspeed.portal.name       = My Test Portal Org.apache.jetspeed.portal.currentVersion = 1.0   # required Application Server properties org.apache.jetspeed.server.home     = ${catalina_home}/org.apache.jetspeed.server.shared     = ${org.apache.jetspeed.server.home}/shared/lib/org.apache.jetspeed.deploy.war.dir     = ${org.apache.jetspeed.server.home}/webapps/org.apache.jetspeed.services.autodeployment.user      = J2deployer Org.apache.jetspeed.services.autodeploymenT.password = xxxxx org.apache.jetspeed.catalina.version.major            =