The tutorial in this chapter introduces you to IBM WebSphere Portlet Factory and IBM WebSphere Portal. It provides step-by-step instructions to give you a complete end-to-end experience from development to production. You will develop and test two portlets in a development environment using IBM WebSphere Portlet Factory, and then you will deploy/manage the portlets in a production environment using IBM WebSphere Portal.
End-to-End on Developing, Testing, and Deploying of a Portlet
The tutorial is based on a scenario about a company called PetCompleteServices building their portal Web site. PetCompleteServices is all about pets. It provides information and services for pets, including pet travel insurance, pet travel carrier, pet sitting, and lots more. Victoria is responsible for architecture and technology at PetCompleteServices. In her SOA plan for the company, the first step is to start with a portal. It is in PetCompleteServices' long-term plan to integrate with airline companies to provide travel services for pets. Claire is from the airline company HelloWorldAir and is always looking to work with new partners to provide first of a kind services for her customers to stay on top of the competition. Victoria and Claire have started working on the integration proposal.
The tutorial is divided into three parts (Tutorials 7.1, 7.2, and 7.3):
In Tutorial 7.1, you will develop and test a simple portlet, called PetTravelInfo, which is expected to have the look and feel shown in Figure 7.1. This portlet displays static text.
Figure 7.1 Look and feel of PetTravelInfo
The focus of this part of the tutorial is the basics of IBM WebSphere Portlet Factory. It covers projects, models, builders, portlets, testing of a model, and building the WAR file for deploying in production. If your intention is to have a hands-on end-to-end experience from development to production of a portlet, you can choose to follow only Tutorials 7.1 and 7.3.
In Tutorial 7.2, you will develop and test a portlet, called ListPetTravelCompany, which is expected to have the look and feel shown in Figure 7.2. This portlet retrieves information from a database and displays the results in a simple table.
Figure 7.2 Look and feel of ListPetTravelCompany
The focus of this part of the tutorial is a well-designed SOA WebSphere Portlet Factory application. It covers service provider and service consumer models.
In Tutorial 7.3, you will put PetTravelInfo and ListPetTravelCompany in a production environment. The result is shown in Figure 7.3. You will install the portlets in IBM WebSphere Portal and then add them to portal pages. Finally, you will grant permission to a new user to use the portlets.
Figure 7.3 PetTravelInfo and ListPetTravelCompany in production
The focus of this part of the tutorial is on using tools to build a portal, including installing portlet application, creating portal pages, adding portlets to portal pages, and editing portal page layout; using tools to manage a portal, including giving access to users on new portlets; and single login to a portal website rather than to individual application.
- Tutorial 7.1: Create and Test a Simple Portlet
- Step 1: Create a project in IBM WebSphere Portlet Factory
- Step 2: Create and test a simple portlet
- Tutorial 7.2: Create and Test a Portlet That Accesses a Database
- Step 1: Create a service provider model
- Step 2: Create a service consumer model
- Tutorial 7.3: Deploy a Portlet
- Step 1: Install a portlet in IBM WebSphere Portal
- Step 2: Add a portlet to a WebSphere portal page
- Step 3: Access a portlet as a new user
- Step 4: Set access permissions for a portlet
The tutorial has been developed with the following products and environment.
- IBM WebSphere Portlet Factory version 6.1
- An application server is needed for testing the model. The WebSphere Application Server instance WebSphere_Portal in the WebSphere Portal installation can be used.
- IBM WebSphere Portal version 6.1
- IBM DB2 Enterprise Server Edition version 9.1.4
- This product is required for Tutorial 7.2. Your WebSphere Portal installation should be configured with DB2.