Build commands Build and deployment configuration In the previous steps you generated a custom portal project and learned about the structure of the generated project. Before you can build and deploy the portal, you need to set a few configuration parameters. Configure application server and database locations The file jetspeed-mvn-settings. The generated project is configured to use Tomcat as application server, and Derby as database.
|Published (Last):||6 February 2013|
|PDF File Size:||14.61 Mb|
|ePub File Size:||16.88 Mb|
|Price:||Free* [*Free Regsitration Required]|
Maven Apache Maven is a "software project management and comprehension tool". In this tutorial we use it to manage the portal build and deployment. Technically it is not required to use Maven to build a custom Jetspeed portal. But it gives you much more control over your build, dependency and release management, and generally makes your life easier. You will need Maven version 2. Tomcat Apache Tomcat is an application server. You need to install it on your system.
Generally this involves nothing more than downloading and unzipping the Tomcat distribution in a location of your choice. Jetspeed can be deployed in other application servers, such as Websphere, but in this tutorial we use Tomcat. You will need Tomcat version 5. Derby Apache Derby is a lightweight relational database.
You do not need to install Derby, it is embedded in the Jetspeed portal and is automatically set up and populated. Eclipse Eclipse is an integrated development environment for Java. The use of an IDE is highly recommended as it speeds up development, compiling and debugging. We used Eclipse 3. Next You are now ready to start the tutorial! An archetype is a template that you can use to generate a boilerplate project.
Technically it is not required to use Maven, but it is recommended because it will give you more control over your build and release management.
Also the generated project will keep your customizations clearly separated from core Jetspeed functionality, and will make updates to newer Jetspeed version easier. To create a new custom portal named jetexpress, enter the following command in a location of choice: mvn org. In addition you specify a number of parameters that will be used by Maven to uniquely identify your project: a name artifactId and group groupId , a package name package , and a version version. Maven will ask you to confirm the groupId, artifactId, version and package for your project: Confirm properties configuration: groupId: org.
A directory named jetexpress will have been created. Notice that jetexpress will be the name of your portal, not jetspeed. The idea is that you can create a customized portal based upon Jetspeed, but with a different name, customized to meet your organization requirements. What files and folders were generated, and what are they for? Previous - Next jetspeed-tutorial jetspeed-tutorial Project structure In the previous step you generated a custom portal project using the Jetspeed Archetype for Maven.
It consists of a simple parent project, and two submodules: jetexpress-portal and jetexpress-pa. The parent project does not produce any artifact by itself, but it lists its submodules and defines some project wide settings and properties, such as versions of dependencies.
The jetexpress-portal submodule provides a Jetspeed portal. It contains the configuration of the portal, its pages and decorators. This is where you do any portal-wide customizations. The jetexpress-pa submodule provides a portlet application. The generated project comes with one sample portlet, MyPortlet. The parent project as well as its submodules each have a pom.
Configuration The file jetspeed-mvn-settings. This file needs to be adapted to your local environment before you can build and deploy the portal. We will do this in the next step.
Previous - Next jetspeed-tutorial Build and deployment configuration In the previous steps you generated a custom portal project and learned about the structure of the generated project. Before you can build and deploy the portal, you need to set a few configuration parameters.
Configure application server and database locations The file jetspeed-mvn-settings. The generated project is configured to use Tomcat as application server, and Derby as database. All you have to do is set the correct location for both. Find the org. The Jetspeed Deployment Guide [FIXME insert link] describes in detail how to deploy your portal to different application servers, and how to configure different databases.
Because this is not a standard Maven plugin, you need to specify its fully qualified Maven name groupId:artifactId:version each time you use it. In case of the Jetspeed Maven Plugin this is org. Luckily you can add the Jetspeed Maven Plugin to the standard Maven plugins, so you can use jetspeed:mvn instead. Maven has global configuration file called settings.
If the file does not exist on your system, you can create it yourself and copy paste in to it the XML below. If it does exist, it probably already has some configuration in it. Add the pluginGroup for Jetspeed as below. Previous - Next jetspeed-tutorial Building and Deploying a Custom Jetspeed Portal Now that you have completed the build and deployment configuration of your custom portal, you are ready to build the portal.
Note: for finer grained build and deploy commands see the Build Commands Reference. Next Now that you have built and deployed the portal, lets start up the application server.
Previous - Next jetspeed-tutorial Running a Custom Jetspeed Portal In the previous step you built and deployed your portal project. You can now start your application servers and log in to your portal. To start up the portal, go to the bin directory of your Tomcat installation.
If you are using a Unix system, run:. Wait for the message that the server has started up, e. You will be prompted to change the admin password. The portal design, or skins, are known in Jetspeed as decorators and themes. With decorators and themes, you can customize the portal experience to the branding of your organization.
In this tutorial, we will simply change a few images, CSS styles and colors to get you on your way. It is important to note that all of the changes made in this section are made in the build environment.
For example, you can drop a decorator or theme into the portal while its running. Jetspeed will pick it up automatically. Or, to customize a page, you can use the portlet customizer or desktop customizer, portlet selector, and site manager: all administrative portlets that work on your live portal. However, the point of configuring everything in a Maven build is to be able to easily reproduce portal environments for development, testing, and new deployments.
This section of the tutorial covers customizing:? Portal Skins or Decorators. We replace the default logo, colors, and page header and footers with our own. Portal Themes. Same as Portal Skins, but themes apply to the Jetspeed Desktop. Configuring the default portal page to use these new decorators and themes Next Lets get started with customization of the default portal page decoration. Previous - Next jetspeed-tutorial Page Decorators Each Jetspeed page can be associated with a different page decoration.
Page decorations control some important aspect of a portal page:? The colors, images, CSS styles that skin this page The header portion of the page The page margins The footer portion of the page Menus displayed on the page Action buttons displayed on the window Decorators do not control the placement of portlets.
That is handled by layouts. Jetspeed comes with several page decorations out of the box. The default page decorator for most pages is simply called jetspeed. It looks like this: We are going to create a new decorator for this tutorial. This will save you the trouble of creating all the logo images and CSS definitions. Inside it, create a directory layout. From jetspeed-tutorialresources. Jetspeed does support JSP-based decorators. However no one has contributed one yet.
We could spend a lot of time teaching you about all the macros available. But lets just concentrate on changing the logos first. Besides the images, the header. In fact we simply copied the default decorator to get us started. This gives you a good start of customizing the page.
Jetspeed Menus are built from a collection of portal resources known as the Portal Site. The portal site is a content tree like a file system of portal resources. The site can be stored in the file system or in a database. Resources can be a page, folder, or link. Lets look at some of the available macros for displaying menus on your page. Used to define the page tabs above the portal. You can also define your own menus not covered in this tutorial.
JETSPEED TUTORIAL PDF
Project Directory Overview Welcome to the Jetspeed-2 Tutorial with Ant and Eclipse This Jetspeed-2 tutorial is a step-by-step set of instructions and source code for creating a custom Jetspeed-2 Portal from scratch using Ant and Eclipse. When starting a new Jetspeed-2 portal project, we strongly recommend that you create a new portal project using the working JetExpress as a base. Do not edit the Jetspeed-2 source and resources directly. As your project progresses, you may want to look at the Jetspeed-2 sources to answer questions or for hints on how to implement additional functionality in the Portal framework. It is not a bad idea to download them into a separate Eclipse project for ease of access. Goal of the Tutorial This tutorial will guide you through the steps to create your own sample portal based on a working portal called JetExpress. The goal of this tutorial is to show you how to create your own custom Jetspeed-2 portal, complete with your own set of portal pages, your company logos and text, your own set of portlet applications, and any special integration required to run your portlets inside Jetspeed
Maven Apache Maven is a "software project management and comprehension tool". In this tutorial we use it to manage the portal build and deployment. Technically it is not required to use Maven to build a custom Jetspeed portal. But it gives you much more control over your build, dependency and release management, and generally makes your life easier.
Fauzilkree There are also new concepts introduced by the portlet standard. See the How to Ask page for help clarifying this question. The programming API is completely changed. Please clarify your specific problem or add additional details to highlight exactly what you need. If you ar going to be creating portlet applications, check out this fine e-book for an overall guide to tjtorial portlets: The Jetspeed Tutorial uttorial portals. I have already consulted http: This process is defined online at Apache.