In this step you will create a Portal and import two web applications into the Portal.
The tasks in this step are:
In this step you will create a Portal file, an XML file with the .portal file extension. The .portal file is the central defining file of a Portal. It refers to all of the major components of the portal: the desktops, books, pages, portlets, etc. When users visit the Portal, they will point their browsers at this file: http://localhost:7001/PortalProj/my.portal.
When
you create a .portal file, a visual representation of the Portal is displayed
in the main work area. The picture to the right shows the main visual components
of a Portal.
A desktop is a user-specific view of the Portal content. A Portal can support many desktops. A single Portal might support an employee-specific desktop, a customer-specific desktop, and others, where each desktop exposes different kinds of users to different sets of content. For example, a employee-specific desktop would probably be a wider view of the Portal content compared to a customer-specific view. The employee desktop might include access to sensitive information that the company wouldn't want in the hands of customers or rival companies. Any part of a Portal can be included or excluded from a desktop, including a book, a page, a specific application, or an individual link.
Desktops can also define the look and feel attributes of a Portal. Desktops can be associated with a particular skin which defines the color scheme, fonts, and images used. Desktops also contain a header and footer: you can place images, text, or any web content in these areas to give consistency to the look and feel of a desktop.
A book gives you a way to organize your content and navigation in a hierarchical manner. Books can contain other books or pages. In a browser, a book is rendered as a set of tabs or links. Each Portal contains a main book called by default "Main Page Book".
A page consists of a set of columns and/or windows that organize the actual content of your Portal. You navigate to a page by clicking on an individual tab or a link.
In this step you will add a second page to the Portal's main book. When the Portal is rendered in a browser, the two pages will appear as two clickable tabs. You add a new page by dragging and dropping the new page into the main work area. You will also set properties on the new page using the Property Editor.
In this task you will import the source code for two applications into your Portal Project. These two applications are web applications built using WebLogic Workshop's Page Flow technology. To learn more about Page Flow web applications see the Getting Started Tutorial: Web Applications.
In the Import Files to Project 'PortalProj' dialog navigate to and select the portlets folder located in [BEA_HOME]/weblogic81/samples/platform/tutorial_resources/GettingStarted_Portal.
Portlets are windows that surface web applications and other web content. A Portlet can contain content that is as simple as an HTML file or as complex as a large web application. In the following step you will add two Portlets to your Portal, one will surface the login application, the other will surface the favorite color application.
Note that Portlets are automatically created for you whenever you drag and drop new content into the Portal.
You now have a Portal that surfaces two web applications.
In this task you will test the Portal using the Workshop Test Browser. The Workshop Test Browser can be used to test any web application you build with WebLogic Workshop.
There are two things to note as you test the behavior of the Portal at this point:
In the next step of the tutorial you will correct both of these problems. You will make the favorite color application accessible only to logged in users and you will provide a way for the favorite color application to store a user's favorite color while the user is logged out.